MediaType's IsSubsetOf does not work as expected

public IActionResult Index()
{
    var mt1 = new MediaType("text/plain");
    var mt2 = new MediaType("text/plain; charset=utf-8");
    return Content(mt1.IsSubsetOf(mt2).ToString());
}

The above action returns False
Where as mt2.IsSubsetOf(mt1) returns True. This is incorrect, right?

Old Web API behavior is the same as 1. here:
https://github.com/aspnet/AspNetWebStack/blob/29ded53ad9d8beb5e867150f51a201085aa46e93/test/System.Net.Http.Formatting.Test/Formatting/MediaTypeHeaderValueExtensionsTests.cs#L123
I looked at the current tests and the behavior is as 2.
https://github.com/aspnet/Mvc/blob/dev/test/Microsoft.AspNetCore.Mvc.Core.Test/Formatters/MediaTypeTest.cs#L133
@dougbu

Your test shows IsSubsetOf() is working correctly for both (1) and (2). IsSubsetOf() is not commutative.
Old Web.API had / has a few bugs in this area.

Right, the current behavior appears to be correct. Discussed in person with everyone.


k html copy

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as your webpack version, Node.js version and Operating System.

do not mind this post. I failed typing... sorry


Fix scripts to work with paths that have ".../" in their names

Running housekeeping.sh (need to fix in tasks.sh):
Archive "Travel Man: 48 Hours in... - S07E04 - [HDTV-720p].mkv"
"/Volumes/Media/Originals/TV Shows/Travel Man: 48 Hours in.../Season 07/Travel Man: 48 Hours in... - S07E04 - [HDTV-720p].mkv" doesn't exist!

Maybe fix by replacing ".." or "..." in any filename when importing?

Also fix colons in filenames (:)


gap between quote lines

The quotation marks are making the bottom line have a bigger gap. Thanks Jo

Fixed


Change versioning of initial server and client tags

We tagged initial OSS server with version 1.0.4 and client with 1.5.0, because this were the versions used inside the former internal project.
But having multiple changes in API in next future (downward compatible but still changes) and still wanting to support only API v1.0 at the moment and wanting to show that sechub is still in development we decided to change back the initial versions:
rename v1.0.4-server -> v0.10.4-server
rename v1.5.0-client -> v0.15.0-client
SecHub is ready to use with 3 products only currently. It works, but there is still much to do!
So this will represent more the current situation
So inside this issue, we will remove the old tags and replace them with new ones

This will be done by following commands
git tag v0.10.4-server v1.0.4-server
git tag -d v1.0.4-server
git push origin :refs/tags/v1.0.4-server
git tag v0.15.0-client v1.5.0-client
git tag -d v1.5.0-client
git push origin :refs/tags/v1.5.0-client
git push --tags


Add allocator support to promise, packaged_task and friends

C++11 requires for std::promise to have allocator support. This is a very useful feature for us to optimize certain use cases of creating futures.

This was fixed by merging #2604.


Roll engine 74e68ff8b108..c8755d74c17e (1 commits)

https://github.com/flutter/engine/compare/74e68ff8b108...c8755d74c17e
git log 74e68ff8b108..c8755d74c17e --no-merges --oneline
c8755d74c Update FlutterFrontendCompiler.rejectLastDelta to match the signature in CompilerInterface (flutter/engine#6426)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry @liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Auto-roller completed checks. About to merge.


update badges to only give them to confirmed attendances

Updates the new badges to only give them to users who actually attended a class. Also added spec examples to cover unconfirmed attendances.
The new specs run a bit slow as I'm making a ton of db records, seems OK for now.

+1


Tilt Cloud Team: homepage and blog post

cc @nicks per https://windmill-eng.slack.com/archives/C01259BDMDJ/p1587413736041500?thread_ts=1587412283.035900&cid=C01259BDMDJ

@dbentley — I just pushed a commit with this proposed layout:

@dbentley : Please squash and merge when you are ready to.


add status page

https://github.com/CachetHQ/Cachet

:+1:, that looks super cool!
On (Jan-29-16|23:57), Antonio Gonzalez wrote:

https://github.com/CachetHQ/Cachet

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/issues/1627


Moving relationships out of "Reputation"

Status
Ready/In Progress/In Hold (Reason for hold)
Description
Moving the documentation for relationships to a more correct location.
Screenshots
Paste here any images that will help the reviewer

@Ni-Knight Doc review completed.

@ShirleyDenkberg - committed suggestions (Not my changes, just moved text location) :)


How to do E2?

Hey,
Thanks for your great work!
I'm trying to do E2, specifically filling a room with furniture as you show in your example.
Is that under "Style preserving edits"? I notice there's no input image on those.
Also I should provide boxes for the furniture? Or can that be skipped so it just follows the overall structure?

E2 requires heavier computation (SVD of Jacobian of ControlNet) than a simple forward pass, making it infeasible for a demo. The code is more involved which will take time to clean up.
However, for filling a room with furniture, you can also use our Scene Boundary Control (C1), which is to be released very soon.

E2 requires heavier computation (SVD of Jacobian of ControlNet) than a simple forward pass, making it infeasible for a demo. The code is more involved which will take time to clean up.
However, for filling a room with furniture, you can also use our Scene Boundary Control (C1), which is to be released very soon.

Hey there,
I hope this message finds you well. I was just curious if there are any plans in the works to release the Scene Boundary Control feature? Thank you kindly!


async considerations

So the other night I was wondering if anyone had thoughts on async vs sync methods. I am doing some research on how this could benefit certain math calculations, but was curious if anyone had any thoughts

parallelism should only really be considered when dealing with large problems, e.g. incredibly large matrix-matrix multiplication. the problem with this is that these are CPU-intensive tasks, which Node is not built for. for small tasks, there would be too much overhead for it to be worth it.


Add "enable-bar-scroll" to "hypr/workspaces"

sway/workspaces has an option called enable-bar-scroll that lets you scroll through workspaces anywhere on the bar, not just while hovering over the workspaces.
I have a very wide monitor, so I was a heavy user of this.
Could we have this option on hypr/workspaces as well?
Alternatively, would it be possible to add a on-scroll-{up|down} on the bar itself, so we could bind anything to it?

I've made a simple patch for this. Could you test if it works with named and persistent workspaces since I only used numbered ones. my fork

for everyone finding this Issue and if the fork is not yet merged:
Waybar has a note on this topic in their wiki https://wiki.hyprland.org/Useful-Utilities/Status-Bars/#scrolling-through-workspaces
I hope, you find it useful.

I've made a simple patch for this. Could you test if it works with named and persistent workspaces since I only used numbered ones. my fork

Sorry for the slow reply, just tested this now and it seems to work! :grin:
I just checked if you had opened a PR and I happened to find this one from 2019: https://github.com/Alexays/Waybar/pull/322
It makes it sound like scrolling on the entire bar surface should already be working, strange :thinking:

@Hubro that PR only has the hook implemented for Sway.

@VAWVAW I rebased your patch: https://github.com/Craeckie/Waybar
It seems to work. Would you be willing to create a PR?

I opened #3088.


Missing requirements?

Is there any missing requirements on this page?
I tried to run the following example:
docker run --isolation=process --device="class/86E0D1E0-8089-11D0-9CE4-08003E301F73" mcr.microsoft.com/windows/servercore:1809
Even with 86E0D1E0-8089-11D0-9CE4-08003E301F73 being a supported GUID as documented.
and got the following error (even with all the requirements):
docker: class/86E0D1E0-8089-11D0-9CE4-08003E301F73 is not an absolute path.

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

ID: 058ed20d-48f8-1269-2f91-47b4c158076e
Version Independent ID: 8f41fab5-682a-389a-78d1-b6dcf8906d0f
Content: Devices in containers on Windows
Content Source: virtualization/windowscontainers/deploy-containers/hardware-devices-in-containers.md
Service: windows-server
Sub-service: windows-containers
GitHub Login: @sethmanheim
Microsoft Alias: sethm

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


ALB support

Adding ALB Support for those who wish to avoid APIGW pricing and/or any other reason to use ALB instead of APIGW(Automatic Health check makes ourlambdas always hot  :)).
PS: This PR also needs to consider the https://github.com/hoaproject/Fastcgi/pull/28 that enables Responder class to process multi headers(that we must enable in our target group on ALBs).

Has SAM / CloudFormation included support for Lambda in the Target Group of a Load Balancer Listener or are you defining it just on AWS Web Console?

@deleugpn AFAIK they did not. I Did it on Console

@mnapoli I Updated from master and added the new code for Hoa's multi header.
I Dont know why the codes are not passing if you can take a look will be great.
All failed test cases are the same for what i checked.

@mnapoli Updated the PR to use Hollodotme.
The getHeaders function is necessary while Hollodotme dont fully support multiheaders, but we have no reason to wait for that because we can parse ourselves.
Please take a look :+1:

@mnapoli i changed the ToApiGateway method as it does not makes sense anymore (it serves also for ALB) please take a look, it does makes more sense now, and the PR should be "Adding Multiheaders Support (ALB)". I've tested in a working environment and all was good..

Maybe a little off topic here. But I saw today that there is an option for the ALB Target group to switch between using multi or single values for headers.
Don't know if its new or not.

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html#enable-multi-value-headers
https://www.terraform.io/docs/providers/aws/r/lb_target_group.html#lambda_multi_value_headers_enabled
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticloadbalancingv2-targetgroup-targetgroupattribute.html

@hmazter In this last refactor that i did, it takes into account in every request if it is Multi Valued or not it does not check if the request comes  from APIGW or ALB

Thanks @atrope, in order to simplify the review and move forward I've opened #338 that includes your PR and adds the tests.

This is not obvious by the message about but for anyone reading this in the future: this has been merged via #338


chmod: changing permissions of 'var/lib/postgresql/data': Permission denied

I have slightly extended the official postgres Image in the following way (only the COPY is really important, to do some stuff to use SonarQube with Postgres):
Version: 1.0.0
FROM postgres:9.5
MAINTAINER Wolfgang Grossinger<EMAIL_ADDRESS>COPY sonarqube.sql /docker-entrypoint-initdb.d
RUN localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8
ENV LANG en_US.utf8
ENV POSTGRES_PASSWORD=postgres
ENV POSTGRES_USER=postgres
RUN chmod 777 /var/lib/postgresql/data
After building the image I try to start it with the following command:
sudo docker run --name postgres_sonar -p 5432:5432 -v /data:/var/lib/postgresql/data wogro/postgres_sonar
I get the following error message:
chmod: changing permissions of ‘/var/lib/postgresql/data’: Permission denied
I don't know what the reason is (probably it's me), but it is something i would never expect from an official image (I just would expect that mounting a volume works :-))

Hi,
Today I run official  postgres:9.5 image without any changes under kubernetes and I got the same problem:
# kubectl logs my_pod -p
chmod: changing permissions of ‘/var/lib/postgresql/data’: Permission denied

If you are using MacOSX or Windows with the Vbox shared folders, then this is a duplicate of https://github.com/docker-library/postgres/issues/28

Hey, guys!
I have the same issue with running postgres on OSX.
docker run \
  --name my-postgres \
  -e POSTGRES_USER=admin \
  -e POSTGRES_PASSWORD=password \
  -e POSTGRES_DB=some_db_dev \
  -v $PG_LOCAL_DATA:/var/lib/postgresql/data \
  -d postgres:9.5.1

My output is the following:
* Starting PostgreSQL
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are enabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
initdb: could not create directory "/var/lib/postgresql/data/pg_xlog": Permission denied
initdb: removing contents of data directory "/var/lib/postgresql/data"

Versions of docker, docker-machine, virtualbox and boot2docker are:
docker-machine version 0.6.0, build e27fb87
Docker version 1.10.2, build c3959b1
VirtualBox Version 5.0.16 r105871
boot2docker 1.10.3

I saw many publications about this topic but the most of them are outdated. I had tried do the same solution as for mysql but it did not help.
Maybe somebody can updated me: does some solution exist to run postgres container with data volumes through docker-machine?
Thanks!

Any workarounds for this?

I'm experiencing the same error when trying to run the latest image on OpenShift Enterprise. The error occurs whether the container has or does not have a mounted volume:
chmod: changing permissions of ‘/var/lib/postgresql/data’: Permission denied

Hi,
Found this for solving the chmod issue:
http://stackoverflow.com/questions/24288616/permission-denied-on-accessing-host-directory-in-docker
Check here too for the selinux security issue :
https://docs.docker.com/engine/tutorials/dockervolumes/#/volume-labels
I fixed my docker-compose file by adding a :z at the end of the volume command
volumes:      - /media/dataDemo/db:/var/lib/postgresql/data:z
Hope it will help.

I'm noticing that the /var/lib/postgresql/data group permission is root. That doesn't seem correct to me.

@collinpeters, it looks like we only chown to the user in the entrypoint.

any news about this issue?

My issue appears like that of @sergio1990 except that I am using "Docker for Mac" instead of "Docker Toolbox". I resolved my case by changing ownership of the host file system to be used by the PostgresQL container to the $USER who will run that container. In doing so it appeared that the container relies upon the credentials cache resulting from the ownership change: sudo chown -R $USER $POSTGRESQLFS then docker run.

I have been trying to apply the :z and :Z options in my kubernetes deployment configuration. However it fails with following error.
Failed to start container with docker id b323b283a475 with error: Error response from daemon: {"message":"SELinux relabeling of /var/lib/kubelet/pods/13a57233-0b02-11e7-bb55-0050560107db/volumes/kubernetes.io~nfs/sonar-data is not allowed: \"operation not supported\""}
Error syncing pod, skipping: failed to "StartContainer" for "sonar-postgres" with RunContainerError: "runContainer: Error response from daemon: {\"message\":\"SELinux relabeling of /var/lib/kubelet/pods/13a57233-0b02-11e7-bb55-0050560107db/volumes/kubernetes.io~nfs/sonar-data is not allowed: \\\"operation not supported\\\"\"}"
Back-off restarting failed docker container

Note that I have tried the mountPath with both :z and :Z in the following configuration. Without these it fails with the chown error mentioned by you guys.
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: sonar-postgres
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: sonar-postgres
        tier: backend
    spec:
      containers:
        - name: sonar-postgres
          image: postgres:9.6
          resources:
            requests:
              cpu: 100m
              memory: 100Mi
          env:
            - name: POSTGRES_USER
              valueFrom:
                secretKeyRef:
                  name: sonar-postgres
                  key: user
            - name: POSTGRES_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: sonar-postgres
                  key: password
          ports:
            - name: postgresport
              containerPort: 5432
          volumeMounts:
            - name: sonar-postgres-data
              mountPath: /var/lib/postgresql/data:z
      volumes:
        - name: sonar-postgres-data
          persistentVolumeClaim:
            claimName: sonar-postgres
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: sonar-postgres
  labels:
    app: sonar
    tier: backend
spec:
  capacity:
    storage: 500Mi
  accessModes:
    - ReadWriteMany
  nfs:
    server: x.x.x.x
    path: /kubernetes/volumes/sonar/postgres
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: sonar-postgres
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 500Mi

Altough the home directory of postgres user is /var/lib/postgresql, the owner is root.

@marcofranssen have same issue with kubernetes deployment. :z does not help really. Have you tried to fix this?

For anyone still experiencing this (I am, using Docker for Windows. This is my first google result for the permissions error), I discovered a workaround that works for my case (I'm using it for an end-to-end test so I don't need to persist data, unsure how this workaround interacts with volumes).
All I'm doing is setting the PGDATA environment variable to a path that's not in /var, which seems to have fewer permissions issues for whatever reason. After that, postgres starts fine.
docker run -e PGDATA=mypgdata postgres

FYI:
You can't have your db in /var/lib/postgres/data/whatever.
Change that path by /var/lib/postgres/whatever and it will work.
See https://stackoverflow.com/questions/50916801/kubernetes-pod-which-encapsulates-db-is-crashing

I want to update this issue because I think people are still hitting it via google. I don't think you should add "no_root_squash" to your exports. The answer is in https://hub.docker.com/_/postgres.

PGDATA: This optional variable can be used to define another location - like a subdirectory - for the database files. The default is /var/lib/postgresql/data, but if the data volume you're using is a filesystem mountpoint (like with GCE persistent disks), Postgres initdb recommends a subdirectory (for example /var/lib/postgresql/data/pgdata ) be created to contain the data.

So if you set the environment variable PGDATA to /var/lib/postgresql/data/pgdata and your mountPath stays as /var/lib/postgresql/data then all is well.
Your container will mount /var/lib/postgresql/data and create the pgdata directory. All of the chown operations will work because it's not trying to chown the base directory (which is the nfs mount).

@shewless don't work in OKD 3.11 with psql 11

For anyone still get this issue. I get the "permission deined" whilt mapping volume in docker using kubernestes. I tried so many ways to fix this like "chmod , chown ..." , but nothing works.
Then i mount the directory under my user path on the host machine and anything works perfectly . Hope this workaround can help someone.

I received this error message "fixing permissions on existing directory /var/lib/postgresql/data ... initdb: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted".
Reason: Mount path of my volume and PGDATA was both set to /var/lib/postgresql/data
Obviously, postgres was trying to chown the volume mount path for which postgres user 999 did not have permissions.
When i changed PGDATA to /var/lib/postgresql/data/mydata the issue was resolved.
Just followed the recommendation from https://hub.docker.com/_/postgres for PGDATA

The default is /var/lib/postgresql/data, but if the data volume you're using is a filesystem mountpoint (like with GCE persistent disks), Postgres initdb recommends a subdirectory (for example /var/lib/postgresql/data/pgdata ) be created to contain the data.

This is still very much broken. I tried setting PGDATA=someotherpath, and this still fails if that path is shared with the host.

Still experiencing errors while using Docker Desktop for MacOS for PostgreSQL.
The compose file looks like
version: "3.7"

services:
  db:
    image: postgres:12
    environment:
      POSTGRES_PASSWORD: password
      POSTGRES_DB: db
      PGDATA: /var/lib/postgresql/data/pgdata
    volumes:
      - /home/docker/volumes/db:/var/lib/postgresql/data
    networks:
      - backend
    ports:
      - 5432:5432
    deploy:
      placement:
        constraints: [node.role == manager]

Notice /home/docker/volumes is a folder shared from the host of docker machine and /home/docker/volumes/db is a empty folder already exist before mounted.
The error reports:
wbc_db.1.dzbprm4atz26@wbc-manager    | The files belonging to this database system will be owned by user "postgres".
wbc_db.1.dzbprm4atz26@wbc-manager    | This user must also own the server process.
wbc_db.1.dzbprm4atz26@wbc-manager    |
wbc_db.1.dzbprm4atz26@wbc-manager    | The database cluster will be initialized with locale "en_US.utf8".
wbc_db.1.dzbprm4atz26@wbc-manager    | The default database encoding has accordingly been set to "UTF8".
wbc_db.1.dzbprm4atz26@wbc-manager    | The default text search configuration will be set to "english".
wbc_db.1.dzbprm4atz26@wbc-manager    |
wbc_db.1.dzbprm4atz26@wbc-manager    | Data page checksums are disabled.
wbc_db.1.dzbprm4atz26@wbc-manager    |
wbc_db.1.dzbprm4atz26@wbc-manager    | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
wbc_db.1.dzbprm4atz26@wbc-manager    | initdb: error: could not create directory "/var/lib/postgresql/data/pgdata/pg_wal": Permission denied
wbc_db.1.dzbprm4atz26@wbc-manager    | initdb: removing contents of data directory "/var/lib/postgresql/data/pgdata"
wbc_db.1.x70r9no7asev@wbc-manager    | The files belonging to this database system will be owned by user "postgres".
wbc_db.1.x70r9no7asev@wbc-manager    | This user must also own the server process.
wbc_db.1.x70r9no7asev@wbc-manager    |
wbc_db.1.x70r9no7asev@wbc-manager    | The database cluster will be initialized with locale "en_US.utf8".
wbc_db.1.x70r9no7asev@wbc-manager    | The default database encoding has accordingly been set to "UTF8".
wbc_db.1.x70r9no7asev@wbc-manager    | The default text search configuration will be set to "english".
wbc_db.1.x70r9no7asev@wbc-manager    |
wbc_db.1.x70r9no7asev@wbc-manager    | Data page checksums are disabled.
wbc_db.1.x70r9no7asev@wbc-manager    |
wbc_db.1.x70r9no7asev@wbc-manager    | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
wbc_db.1.x70r9no7asev@wbc-manager    | initdb: error: could not create directory "/var/lib/postgresql/data/pgdata/pg_wal": Permission denied
wbc_db.1.x70r9no7asev@wbc-manager    | initdb: removing contents of data directory "/var/lib/postgresql/data/pgdata"

Looking forward to your many helps.

On the off-chance that someone else is struggling with this ... I'm running inside Vagrant, and I had endless problems mounting postgres with a data volume explicitly set. Turns out it's Vagrant.

@shukriadams Could you please explicitly explain what you did to fix?

@Dhanabalan89 Could you please post your docker command?

On the off-chance that someone else is struggling with this ... I'm running inside Vagrant, and I had endless problems mounting postgres with a data volume explicitly set. Turns out it's Vagrant.

@shukriadams Could you please explicitly explain what you did to fix?

Just make sure your postgres data volume directory does not sit within a directory shared with the host (ie, the /vagrant folder or below). I provision up a throwaway postgres container + volume mount in ~/. For persistant data I use a remote postgres instance. So, not a fix, just a workaround.

Try this command "sudo /etc/init.d/postgresql start" to start postgres
Do let me know if still issue is there.

I got this issue while using Docker Desktop for Windows, with WSL2 backend. The error occurs if you mount a directory under Windows file system.
$ docker run -v "/mnt/c/Users/jH/Desktop/psql/data:/var/lib/postgresql/data" postgres
chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

The error is gone when host path is in WSL filesystem.
$ docker run -v "/home/hylw/mydata:/var/lib/postgresql/data" postgres

@hylowaker , correct, it worked with me, seem we have to use system file of WSL

@hylowaker @dwthien The same is true for shared folders when working inside a Virtualbox VM. The path must be set to an internal device.

I want to update this issue because I think people are still hitting it via google. I don't think you should add "no_root_squash" to your exports. The answer is in https://hub.docker.com/_/postgres.

PGDATA: This optional variable can be used to define another location - like a subdirectory - for the database files. The default is /var/lib/postgresql/data, but if the data volume you're using is a filesystem mountpoint (like with GCE persistent disks), Postgres initdb recommends a subdirectory (for example /var/lib/postgresql/data/pgdata ) be created to contain the data.

So if you set the environment variable PGDATA to /var/lib/postgresql/data/pgdata and your mountPath stays as /var/lib/postgresql/data then all is well.
Your container will mount /var/lib/postgresql/data and create the pgdata directory. All of the chown operations will work because it's not trying to chown the base directory (which is the nfs mount).

Unfortunately the same page at https://hub.docker.com/_/postgres says:

The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:

Create a data directory on a suitable volume on your host system, e.g. /my/own/datadir.
Start your postgres container like this:
$ docker run --name some-postgres -v /my/own/datadir:/var/lib/postgresql/data -e POSTGRES_PASSWORD=mysecretpassword -d postgres:tag
The -v /my/own/datadir:/var/lib/postgresql/data part of the command mounts the /my/own/datadir directory from the underlying host system as /var/lib/postgresql/data inside the container, where PostgreSQL by default will write its data files.

So it seems to contradict itself...

On the off-chance that someone else is struggling with this ... I'm running inside Vagrant, and I had endless problems mounting postgres with a data volume explicitly set. Turns out it's Vagrant.

Same issue with Vagrant. How did you do it?
Thanks a lot!

So with WSL 2 you can actually use chmod -R 777 (or something more sane) on Windows directories and these permissions are also reflected in the container.

my solution in virtualbox under windows 10 with mounted NTFS disk
`
#!/bin/bash
DB_PASS=admin123
DB_USER=admin
DB_NAME=objects
PG_DATA="$(pwd)/postgres-data"
docker stop postgresql && docker rm postgresql
docker volume create pgdata
docker run -d --name postgresql
-e POSTGRES_PASSWORD=$DB_PASS
-e POSTGRES_USER=$DB_USER
-e POSTGRES_DB=$DB_NAME
-e PGDATA=$PG_DATA
-v $PG_DATA:/var/lib/postgresql/data
postgres:11.5-alpine
`

I tried pretty much everything that has been mentioned here but was still unable to initialize postrges pod with data files stored in a PVC (nfs) mounted folder.
What finally did the trick for me was the following addition in the PVC yaml annotations:
metadata:
  annotations:
    volume.beta.kubernetes.io/mount-options: "dir_mode=0777,file_mode=0777,uid=1000,gid=1000"

For example:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: postgres-pvc
  labels:
    app: postgres
  annotations:
    volume.beta.kubernetes.io/storage-class: "storage-class-name"
    volume.beta.kubernetes.io/mount-options: "dir_mode=0777,file_mode=0777,uid=1000,gid=1000"
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 5Gi

Using Minikube locally with --vm=true you will get all sorts of issues similar to this that I put quite some time into trying to figure out but ended up just using the default Minikube install and all mounted correctly. Looks like my issues were centered around Vagrant.

I had the same issue working on Docker, the solution was
docker volume rm $(docker volume ls -q)

@iserranoe, warning that the following will not be saving any data in the mounted path unless you also set PGDATA=/var/lib/postgresql/pgdata; otherwise is will still be placing all data in the anonymous volume that contains /var/lib/postgresql/data.

   volumes:
      - ./data/pgdata:/var/lib/postgresql/pgdata

@yosifkit, yeah, you're right :'( However, if I set PGDATA=/var/lib/postgresql/pgdata I get the same error:
Attaching to postgres
postgres  | chmod: changing permissions of '/var/lib/postgresql/pgdata': Operation not permitted
postgres  | The files belonging to this database system will be owned by user "postgres".
postgres  | This user must also own the server process.
postgres  |
postgres  | The database cluster will be initialized with locale "en_US.utf8".
postgres  | The default database encoding has accordingly been set to "UTF8".
postgres  | The default text search configuration will be set to "english".
postgres  |
postgres  | Data page checksums are disabled.
postgres  |
postgres  | fixing permissions on existing directory /var/lib/postgresql/pgdata ... initdb: error: could not change permissions of directory "/var/lib/postgresql/pgdata": Operation not permitted
postgres exited with code 1

With configuration:
services:
  db:
    image: postgres
    container_name: postgres
    volumes:
      - ./data/pgdata:/var/lib/postgresql/pgdata:wr
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - PGDATA=/var/lib/postgresql/pgdata

The following fixed the problem for me:
I'm using docker-windows and I was trying to start a postgresql container. I also encountered
chmod: changing permissions of var/lib/postgresql/data: Permission denied
After I changed user: postgres
into
user: ${POSTGRES_UID}:${POSTGRES_GID}
the container started successfully
here's my old docker-compose.yml:
version: '3.5' services:   postgresdb:     image: postgres:13.3-buster     user: postgres     container_name: postgresdb-cdw     ports:
version: '3.5' services:   postgresdb:     image: postgres:13.3-buster     user: ${POSTGRES_UID}:${POSTGRES_GID}     container_name: postgresdb-cdw     ports:.............

你好，
发现这个用于解决 chmod 问题：http : //stackoverflow.com/questions/24288616/permission-denied-on-accessing-host-directory-in-docker
在这里也检查 selinux 安全问题：https : //docs.docker.com/engine/tutorials/dockervolumes/#/volume-labels
我通过在 volume 命令的末尾添加一个 :z 来修复我的 docker-compose 文件 volumes: - /media/dataDemo/db:/var/lib/postgresql/data:z
希望它会有所帮助。

感谢!在docker中成功了

Hi, i had got the same error
i solved this way:
added PG_DATA environment to docker-compose.yaml file
environment:       PG_DATA: /var/lib/pg_data
the other configurations your choice

@FatihMert1 PG_DATA is not a variable that's actually used by anything in the image -- I think you meant PGDATA?

Hi, i had got the same error i solved this way: added PG_DATA environment to docker-compose.yaml file
environment: PG_DATA: /var/lib/pg_data the other configurations your choice

This got it to work in my WSL2 environment. But obviously, it should have been PGDATA.
Here's my yaml:
db:
    container_name: pg_container
    build:
      context: ./postgres
      dockerfile: $PWD/postgres/postgresql_dockerfile
    restart: always
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: root
      POSTGRES_DB: mydb
      PGDATA: /var/lib/pg_data
    ports:
      - "5433:5432"
    volumes:
      - ./postgres/data:/var/lib/postgresql/data

This got it to work in my WSL2 environment. But obviously, it should have been PGDATA.

But in your yaml - in a env PGDATA there is a different path, unlike the connected volume - and volume created empty, i think it work because pginit work not correct with volume connectend in windows (I used WSL too)

  db:
    container_name: pg_container
    build:
      context: ./postgres
      dockerfile: $PWD/postgres/postgresql_dockerfile
    environment:
      PGDATA: /var/lib/pg_data
    volumes:
      - ./postgres/data:/var/lib/postgresql/data

(focused yaml from https://github.com/docker-library/postgres/issues/116#issuecomment-1047329546 above)
:point_up: Just a quick word of caution. Although I don't know what is happening in the used Dockerfile, if this is based upon any of the postgres images, then the data would not be persistent. Since the data would be stored in /var/lib/pg_data, but the volume mounted to the host is /var/lib/postgresql/data.

On macos changing the  PGDATA to  /var/lib/pg_data fixed the issue.

http://stackoverflow.com/questions/24288616/permission-denied-on-accessing-host-directory-in-docker

This worked for me..GREAT..ur rockstar

Using 'mountPath: /var/lib/postgresql/data:z' in k8s yaml made it create a path of '/var/lib/postgresql/data:z', instead of 'mountPath: /var/lib/postgresql/data' with right permissions.

Re: k8s mounts and selinux labels: https://stackoverflow.com/a/51026623/433558

tried few suggestions I saw in this thread.
In my case it seems to bug some bug in WSL2.0 ( I have no clue how to prove it) but I can explain what happens.
In my environment I have Windows 10 Enterprise, Version: 22H2, Build:19045.2251
I have Ubuntu 20.04 LTS on WSL 2.0
I have a directory in my C drive called data so "C:\data"
This directory is mounted in WSL as "/data" but you can access it on "/mnt/c/data" and i tend to work in WSL on this Windows based directory, which overall in WSL2.0 seems like a bad idea.
If i have any data transfer intensive work I get strange error (i have none on record at the moment) but usually something like a file not found, or i can for instance nano a docker-compose.yml file and it will show new file (but i know there is data in it and i can list it) when i run wsl --shutdown and reopen wsl, all seems fine for a bit.
But what i found with this exact erros "[chmod: changing permissions of 'var/lib/postgresql/data': Permission denied]" in my postgres compose mounted the pgdata to a directory and not a volume map (which for this test i wanted to do that) to no avail, and as soon as i moved the docker-compose-data directory i tried to mount posgres into, to eg. my wsl user home directory "~/" and i ran docker compose up the db init script ran with no errors till completion.

What worked for me
First get the user you use to run the docker compose
echo "Current user id is"
user=$(id -u)
echo $user
echo "Current group id is"
group=$(id -g)
echo $group

Now copy paste those values inside of the docker compose.
For example, if you got user=50 and group=80, it should look like this
user: 50:80

Nice
I have tried many solutions but only yours works.

I'm using docker-windows(wsl2) and I was trying to start a postgresql container. I also encountered chmod: changing permissions of var/lib/postgresql/data: Permission denied
The following fixed the problem for me: here's my original docker-compose.yml
services:
  postgresdb:
    image: postgres:13.3-buster
    user: postgres
    container_name: postgresdb-cdw
    ports:..........

and here's my modified docker-compose.yml that fixed my problem
services:
  postgresdb:
    image: postgres:13.3-buster
    user: ${POSTGRES_UID}:${POSTGRES_GID}
    container_name: postgresdb-cdw
    ports:....................

In my docker-compose.yml, after I changed user: postgres into user: ${POSTGRES_UID}:${POSTGRES_GID} the container started successfully

Nice
I have tried many solutions but only yours works.

For me, with my docker-compose.yml file having:
volumes:
       - pgdata:/var/lib/postgresql/data

I was just missing the
volumes:
  pgdata:

Section/volume definition at the end.

Hitting the same error still. I'm following the instruction for PGDATA from https://hub.docker.com/_/postgres to try mounting my local dir (${PWD/tmp}) to the $PGDATA path on the container:
❯ docker run -d \
        --name some-postgres \
        -e POSTGRES_PASSWORD=mysecretpassword \
        -e PGDATA=/var/lib/postgresql/data/pgdata \
        -v "${PWD}/mount:/var/lib/postgresql/data" \
        postgres
fc351129b480a4a7b84d5b9eebcf0b7ec05845d72da9febf4a15818b55498c83
docker: Error response from daemon: error while creating mount source path '/Users/janexing/my_path/tmp/mount': chown /Users/janexing/my_path/tmp/mount: permission denied.

❯ ls -la
total 0
drwxrwxrwx@  3 janexing  staff    96 Dec  7 14:57 .
drwxr-xr-x  48 janexing  staff  1536 Dec  7 14:32 ..
drwxr-xr-x@  2 janexing  staff    64 Dec  7 14:57 mount

❯ chmod 777 ./mount

❯ ls -la
total 0
drwxrwxrwx@  3 janexing  staff    96 Dec  7 15:00 .
drwxr-xr-x  48 janexing  staff  1536 Dec  7 14:32 ..
drwxrwxrwx@  3 janexing  staff    96 Dec  7 15:01 mount

❯ docker run -d \
        --name some-postgres \
        -e POSTGRES_PASSWORD=mysecretpassword \
        -e PGDATA=/var/lib/postgresql/data/pgdata \
        -v "${PWD}/mount:/var/lib/postgresql/data" \
        postgres

❯ docker logs some-postgres -f
chown: changing ownership of '/var/lib/postgresql/data/pgdata': Permission denied

Oddly, if I try to bind /tmp/some_folder with -v "/tmp/some_folder:/var/lib/postgresql/data". However, I can't actually access the local /tmp/some_folder, or it was created somewhere else?
❯ ls /tmp | grep some_folder
(base)

OS: MacOS 13.6.1 (22G313)
Docker server: 23.0.6
Docker client: 24.0.6-rd

I would suggest setting the UID/GID of the container to match the one on your host (--user 1000:1000 or whatever your host UID/GID is).

I encountered the following error as well:

chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted

In my case, I resolved it by fixing the volume path from:
volumes:
  - "./pg-data/:/var/lib/postgresql/data"

to:
volumes:
  - "/pg-data/:/var/lib/postgresql/data"

I'm sharing this here in case it might help someone else.

I made it work for mac + minikube with this
minikube setup
# it doesn't work without the --uid and --gid params
$ minikube mount ./my-app/postgres-data:/postgres-data --uid=999 --gid=999

yml
apiVersion: v1
kind: PersistentVolume
metadata:
  name: postgres-pv
spec:
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 10Gi
  hostPath:
    path: /postgres-data
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: postgres-pvc
spec:
  accessModes:
    - ReadWriteOnce
  volumeName: postgres-pv
  storageClassName: ""
  resources:
    requests:
      storage: 10Gi
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: postgres
spec:
  serviceName: postgres
  replicas: 1
  selector:
    matchLabels:
      app: postgres
  template:
    metadata:
      labels:
        app: postgres
    spec:
      containers:
        - name: postgres
          image: postgres:16
          imagePullPolicy: "IfNotPresent"
          ports:
            - containerPort: 5432
          resources:
            limits:
              memory: "512Mi"
              cpu: "500m"
            requests:
              memory: "64Mi"
              cpu: "500m"
          env:
            - name: POSTGRES_USER
              valueFrom:
                secretKeyRef:
                  name: postgres-secret
                  key: POSTGRES_USER
            - name: POSTGRES_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: postgres-secret
                  key: POSTGRES_PASSWORD
            - name: PGDATA
              value: /var/lib/postgresql/data/pgdata
          volumeMounts:
            - name: postgres-data
              mountPath: /var/lib/postgresql/data
      volumes:
        - name: postgres-data
          persistentVolumeClaim:
            claimName: postgres-pvc

FYI:
You can't have your db in /var/lib/postgres/data/whatever.
Change that path by /var/lib/postgres/whatever and it will work.
See https://stackoverflow.com/questions/50916801/kubernetes-pod-which-encapsulates-db-is-crashing

Unfortunately that didn't work for me as well:
chown: changing ownership of '/var/lib/postgresql/timotest': Permission denied
chown: changing ownership of '/var/lib/postgresql/timotest/pgdata': Permission denied
chown: changing ownership of '/var/lib/postgresql/timotest/data': Permission denied

I want to update this issue because I think people are still hitting it via google. I don't think you should add "no_root_squash" to your exports. The answer is in https://hub.docker.com/_/postgres.

PGDATA: This optional variable can be used to define another location - like a subdirectory - for the database files. The default is /var/lib/postgresql/data, but if the data volume you're using is a filesystem mountpoint (like with GCE persistent disks), Postgres initdb recommends a subdirectory (for example /var/lib/postgresql/data/pgdata ) be created to contain the data.

So if you set the environment variable PGDATA to /var/lib/postgresql/data/pgdata and your mountPath stays as /var/lib/postgresql/data then all is well.
Your container will mount /var/lib/postgresql/data and create the pgdata directory. All of the chown operations will work because it's not trying to chown the base directory (which is the nfs mount).

Thank you, it worked :)


Mobile/Tablet Support

We want to get the UI working on tablets.
There is some early support already in there for touch events, but it is not complete. For example, you can start to drag a new link between nodes, but it doesn't end properly.
The layout could also do with being optimised.
Function Changes

[x] enable dragging out of palette
[x] prevent native zoom
[x] enable pinch-zoom in workspace ( PR coming from @TJKoury )
[x] unable to wire nodes together (a3dea6ec0dc92ae2880a035b2fb4361b697f3ad0)
[x] double tap to edit rather than long-touch (ec5985eaa32066c34ecd39bc1099aeb6d6a16e64)
[x] how to delete a node (radial menu: e524393d8792e4cd75b6520b727e65b803457792)
[x] how to undo change (radial menu: e524393d8792e4cd75b6520b727e65b803457792)
[x] how to group select (lasso) - long-touch to disable scroll/enable lasso? (0e8f0735cc207c1503f1ef91a7a9c43604a802c7)
[ ] import flow placement - click to place, needs a visual cue to touch as you don't drag the nodes
[ ] pinch zoom deselects current selection
[x] pinch zoom triggers radial menu (2fa82d9)
[x] trigger radialMenu on long-touch with link selected

Mobile-specific UI changes

[ ] decide on server-side or client-side mobile detection (ie serve mobile.html, or insert mobile specific css/javascript adaptations)
[x] mobile-only tool bar to enable delete/undo/other? actions (not needed due to radialMenu)
[x] sidebar resize target needs to be more obvious (aa4bf4d64060dab47d75c5dfc00dc4dd06429e23)
[x] sidebar drag in from RH side (aa4bf4d64060dab47d75c5dfc00dc4dd06429e23)
[ ] drop-down menu changed to be slide-in menu
[ ] palette drag in from LH side

Is this currently on hold since there hasn't been any comments for quite some time? I wound up here while looking for a way to remove a connection without cut & paste a node. I've found using the editor othrrwise quite feasible for some small edits on a 10" tablet but this is the most frustrating issue for me.
I have some ideas:
Since it's already possible to select a connection, would it be possible to add support for long tap menu with the option to remove (after the connection is selected)? Or possibly long click to remove directly as that'd probably be the only thing you could do. Another option would be to add an X icon next to the selected connection for removing.

@ristomatti there has been much demand for this and I very rarely use NR on touch screens, so it simply hasn't been a priority.
The issue with deleting wires is one of the main outstanding basic issues for touchscreens. See my comment above on what needs doing - we already have a radial menu that appears on long-touch of nodes. It 'just' needs enabling for long-touch of wires.

@knolleary ah sorry somehow missed it! Are there any plans when this would be implemented or is this perhaps something open for pull requests?

A pull request that enabled the existing radial menu on wires would be welcome!

When you are working on a subflow the connection between a node with input and output (e.g. function) you are not able to connect it to an output. I tested this on an ipad with safari, chrome and firefox. I am using node-red 0.20.7.

I spent a bunch of time fixing up basic touch support in the editor for the 1.1.x release.
I don't think there's much value having this issue sit in the open state. If there are specific bugs with the touch support, they can be raised and addressed as such. If there are larger feature enhancements needed, they can also be addressed in the usual way.


Export your historical Fitbit data for free

If you can code, you're welcome to send me a pull request on GitHub.
I am new swift developer still learning and I would like to get the food log data to import into my glucose app, thus I would like to send you a pull request, it would be great if I can get that food log data in a CVS file or JSON format, therefore I can somehow import it into my app periodically.
thank you in advance
Edison

This app uses JavaScript and NodeJS, so you'd have to learn that to send a PR. But I'm happy to review something that you send me. :smile:


Show output of completed job

Is it possible to add the result (json) of a completed job into the dashboard to see what the output was?

hey @WichardRiezebos, thanks for opening the issue 👋
this is possibly duplicate to #72 so I'll close your issue!
(currently, it's not possible but I'm looking into making this available)


ci: extend formatting to docs, proxy

That was fast!

Haha, and thanks for the fast review! I'm absolutely loving this CI pipeline we're working towards.
I had one commit failure in a job, which passed on the second run. I'm not sure if it was a one-off error, or the first of many occasional concurrency failures. 🤷🏼♂ Either way, I'll keep my eye on it and look into a solution if the problem continues.


affiliation economics

Need to develop some new mathematics to describe the interaction of multiple economies in the same game. This will cause all sorts of magical things to happen automatically through the freely chosen interaction of the players, rather than imposed top-down through system rules. (Not that the proposed system rules are bad in any way, just, if you can take advantage of free will, that's always a good thing.)

One way to approach this could be to identify a basic model of what it means for two economies to interact.

I.e., whenever a choice between two or more options conveys rewards or penalties in two or more value systems.

That's a good definition. I think there should be a way to determine whether a participant is participating in two economies if the others are only participating in one?

Everyone participates in multiple economies. The trick is to identify which economies the person knows they are participating in. Basically, don't trust billionaires, and bob's your uncle. You can trust Bill Gates though, he's a good egg.


psst: add wmclass to desktop file

Description of changes

Added startupWMClass to psst's desktop file to allow for Gnome Wayland (and probably other DE's) to correctly match its icon in the dash and elsewhere when running.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

It doesn't seem to be needed on KDE, where the icon shows up correctly in the task manager without this patch, but of course if it makes things better for GNOME, LGTM!


Update card model

Update card model to include subtype and add dto to return in controller.

Card dto has been updated.


Prop row is undefined in Cell when searching from 2nd page using Toolkit & Pagination.

@AllenFang
I can reproduce the bug #495 & #839  in the latest version:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>In addition, I have a related issue.
To reproduce:

Create a table that has at least 2 pages.
Search for something on the 2nd page which returns some result.

This will give a warning in the console that prop row is required in Cell but its value is undefined. If you use a formatter for any cell the app will crash as the parameter row passed in formatter function is undefined.
I would really appreciate your help with this. And thank you for this library.
I have created a demo on codesandbox.io for your reference. You can check it here

Hello,
I confirm this bug , it's really disgusting as an issue since when using formatter to format Data in table , this causes page to crash , you have to type slowly in order to avoid this problem or avoid formatter :( .
Good Luck fixing it and thx for this amazing DataTable 👍  .

Sorry for lately reply, i will check this out, thanks you guy's support !!

@eyle  @brohera You have to render PaginationProvider as child of ToolkitProvider  then you will fix this issue:
<ToolkitProvider>
  {() => {
    <PaginationProvider>
    { .... }
    </PaginationProvider>
  }}
</ToolkitProvider>

sorry about this issue, I will mention this tricky part in official docs.
Let me know if you guys still have questions, thanks

Can't figure this out.  The row param is always undefined in my formatter function

Hello,
I actually resolved this issue by checking if the row is undefined , if it's true , i return empty String depending on type.
But What really happen , it get's reupdated again  and React  update the view with the row containing the data, you won't even notice the difference at all.
I suggest you to check for Row variable as well as other variable if you need them , and return empty data , The row will get updated just after that and your data will always be present(Without even noticing it).
That's the only way i could prevent this issue.
Hope i did help you.

@eyle I am facing the same issue. Could you please post a gist of your solution?


Upgrading dependencies causes react-grid-layout Responsive to crash with babel-loader error

Describe the bug
I've upgraded many dependencies in my project and react-grid-layout - WidthProvider(Responsive) started crashing my app.
this is the error
node_modules/react-grid-layout/build/utils.js 203:74
Module parse failed: Unexpected token (203:74)
File was processed with these loaders:
 * ../../node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|  */
| function childrenEqual(a /*: ReactChildren*/, b /*: ReactChildren*/) /*: boolean*/{
>   return (0, _fastEquals.deepEqual)(_react.default.Children.map(a, c => c?.key), _react.default.Children.map(b, c => c?.key)) && (0, _fastEquals.deepEqual)(_react.default.Children.map(a, c => c?.props["data-grid"]), _react.default.Children.map(b, c => c?.props["data-grid"]));

The only "solution" I found online was setting browserslist in package.json but that didn't fix it.
I am using react-scripts + customize-cra to start the app. I don't plan on ejecting the application from cra. Is there some kind of babel plugin that has to be added and fixes everything? Really can't find a fix for this.
Your Example Website or App
www.codesandbox.io
Steps to Reproduce the Bug or Issue

upgrade deps
crash

Expected behavior
not crash
react-grid-layout library version
^1.4.4
Operating System Version
linux
Browser
Chrome
Additional context
No response
Screenshots or Videos
No response

Duplicate of #2037

Hi @cristianghita24 , tried 1.4.2 ?

Hi @cristianghita24 , tried 1.4.2 ?

Fixing version to 1.4.2 fixed the issue. You have no idea how much time and stress you saved me, thank you so much!


Get-DSCSplattedResource with Multiple Resource Instances

https://github.com/gaelcolas/DscInfraSample/blob/9df38c608dc1d7229621884ed648696e48617625/RootConfiguration.ps1#L22
@gaelcolas can I check my understanding of how this works please?
If using Datum, there is a use case where configurations get merged for a node. In such a case, there might be multiple instances of a confiiguration for example where all nodes have an agent that runs as a service, then the role of the node added a service for the application.
In the line, I've referenced above, Get-DSCSplattedResource, would use the Configruation name "Service" as the resourceID when the MOF is created. In such cases, where there are multiple instanced the MOF would fail to compile since you may only have a since resourceID of "Service" Is my understanding here correct?
If my understanding here is correct, is the correct way to handle such situations to include another key in the properties described within the Datum tree, for example matching the "Title" and "Name" concept of Puppet?

You need to make sure that the ResourceID is always unique. The name is assigned to a config item in the configurations (composite resources).
A more comprehensive approach of using Datum is the DscWorkshop. It uses the configurations published in CommonTasks.
For services, the ResourceId is generated here. It is the 'ExecutionName' $service.Name. While writing this I think that using just the service name may generate conflicts with other resources so it might be a good idea to change it to "xService_$($service.Name)".
So in our samples the ResourceId is not part of the config data but generated during compilation.

What @raandree said ;)
Technically you can use resources directly, but using configuration (composites) is better, and avoid the key issue.

Thanks - hadn't considered composites.


New tests to demonstrate #1424

This presumes that only the before filter should run when an
unsupported method is called on an endpoint, and that other filters
(before_validation, after_validation, and after) should be skipped.
It also demonstrates that the before filter is called more than
once in that case.

Closed via https://github.com/ruby-grape/grape/pull/1465.


MWPW-140112 Preflight link check

Enhancement to preflights link checking.

All links on a page are now checked.
Broken links show up in a table under SEO tab.
Detects off origin and local links.
Lists URL that is checked.
Lists where the link is located on the page
Lists status of link
Highlights link with status on page - preflight modal closed

Resolves: MWPW-140112
Notes
Each consumer will need to have the API added to their ./milo/config
BACOM is currently set up.
Test URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/rclayton/test-template?martech=off
After: https://preflight-404s--milo--adobecom.hlx.page/drafts/rclayton/test-template?martech=off

BACOM Test URLs

Before: https://main--bacom--adobecom.hlx.page/?martech=off
After: https://main--bacom--adobecom.hlx.page/?milolibs=preflight-404s&martech=off

I will circle back to check on unit tests. Should be good to start testing.


namespace: Add check to make sure PID namespace is not received

The runtime should clear the PID namespace from the config
before sending it to the agent. Add a check in the agent to make
sure PID namespace is not recieved in the configuration.
Information about PID namespace is conveyed by means of a flag instead.
Fixes #285
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>

lgtm

@bergwolf @grahamwhaley PTAL

From 16.04 CI, I think you may have hit the gocyclo limit:
/tmp/jenkins/workspace/kata-containers-agent-ubuntu-16-04-PR/go/src/github.com/kata-containers/agent/protocols/mockserver
grpc.go:533::error: no formatting directive in Errorf call (vet)
grpc.go:523::warning: cyclomatic complexity 16 of function (*agentGRPC).CreateContainer() is high (> 15) (gocyclo)

lgtm

lgtm

Stderr: E: Unable to determine file size for fd 11 - fstat (2: No such file or directory)

The CI failure does look like the guest kernel is missing the 9pfs hack. Let's ignore it and merge since fedora and ubuntu CI all passed.


Update bindgen #102

Just updated bindgen in the bindings_generator folder and fixed some deprecated things.  Did wasm_bindgen need to be updated?

Thanks!
I've figured out how to squash my commits locally.  Should I push that out?
I've tried running cargo build, but I don't have libclang, so I didn't get very far.  I can set it up tomorrow and let you know.

Sure, you can force push the squashed commit to this branch (i.e. git push origin update-bindgen --force). Sounds good!

fwiw, I do git push -f origin HEAD (which does the same in our case)

When I try to run cargo run --bin bindings_generator from the root directory, I get this error:
error: error reading '/root/spirv_cross/../spirv_cross/src/wrapper.hpp'
thread 'main' panicked at 'TranslationUnit::parse failed', src/libcore/option.rs:1190:5
So, I haven't been able to generate bindings.  I can't figure out why it's putting the .. in there.

Oh ok, it relies on the current directory being bindings_generator (we could probably improve that). So I don't run it from the root directory, I just cd into bindings_generator and use cargo run

Okay, before I was getting an error from running cargo run in the bindings_generator directory, but I tried it today and it generated bindings.  Do you want me to attach the files?

@metaphorshear sorry, I didn't see your message until now. It would be great if you could commit the files in this PR, otherwise we can merge it as is and I can update it later :+1:

Okay, I committed the files


Raven.captureException() not capturing metadata

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
With this code:
Raven.config(sentryUrl, {tags: {test0: 'test'}}).install();

  Raven.setUserContext({
           test1: 'test',
        });
        Raven.setTagsContext({ test2:'test' });
        Raven.setExtraContext({  test3:'test' });
        Raven.captureException(err.reason, { logger: 'my.module', extra: 'extra', tags: { test4:'test' } });
 Raven.captureMessage(err.reason, { level: 'warning', extra: 'extra', tags: { test5:'test' } });

A warning and an error are logged. The warning has all the specified meta data, the error only test0.
What is the expected behavior?
That captureException captures the same metadata, the same way as captureMessage.
Which versions of Raven.js, and which browser and OS are affected by this issue?
Are you using the CDN (http://ravenjs.com)?
I used both raven-js version 3.23.1 with webpack and
Tested on Chrome Version 64.0.3282.186 on Windows 10
Did this work in previous versions of Raven.js?
Don't know, first time user.
Are you using hosted Sentry or on-premises? If on-premises, which version (e.g. 8.7.0)?
Using https://sentry.io (paid account)

Not sure if related but isn't extra suppose to be an object?

I just tested it using your code sample, without any modificaitons, and it's all where it should be :)
captureException

captureMessage

As @SimonSchick mentioned, extra in your captureX calls should be an object, otherwise, it's treated as an array of single character values (see screenshot).
Can you post paste link to the broken events or screenshots of them?

Hi @kamilogorek
There seems to be a problem with the type of error
I'm using react and this is my code

  public render() {
        throw new Error('test8a');
  }

public componentDidCatch(error: any, info: any) {
Raven.captureException(error, { tags: {test4: 'test' } });
Raven.captureException(new Error('test_error'), { tags: {test4: 'test' } });

this.setState({ hasError: true, sentryEventId: Raven.lastEventId() });
}

The first one ignores the tag, while the order does log it:

Looking at the POST to sentry, there seems to be a difference:
{"project":"xxx","logger":"javascript","platform":"javascript","request":{"headers":{"User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36","Referer":"http://localhost:8080/patients"},"url":"http://localhost:8080/patients"},"exception":{"values":[{"type":"Error","value":"test8a","stacktrace":{"frames":[{"filename":"http://localhost:8080/scripts/app.js","lineno":44494,"colno":37,"function":"response.json.then","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":140827,"colno":18,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219058,"colno":18,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":44471,"colno":9,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":140827,"colno":18,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219061,"colno":16,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219028,"colno":29,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":144360,"colno":18,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":81984,"colno":7,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":81678,"colno":16,"function":"Connect.onStateChange","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":120259,"colno":16,"function":"Connect.Component.setState","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":127891,"colno":7,"function":"Object.enqueueSetState","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132368,"colno":12,"function":"scheduleWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132411,"colno":11,"function":"scheduleWorkImpl","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132557,"colno":7,"function":"requestWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132646,"colno":7,"function":"performWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132693,"colno":24,"function":"performWorkOnRoot","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132045,"colno":7,"function":"renderRoot","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122117,"colno":27,"function":"invokeGuardedCallback","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122260,"colno":16,"function":"Object.invokeGuardedCallbackDev","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":107334,"colno":21,"function":"HTMLUnknownElement.wrapped","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122221,"colno":14,"function":"HTMLUnknownElement.callCallback","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":131967,"colno":26,"function":"workLoop","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":131903,"colno":16,"function":"performUnitOfWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":129904,"colno":16,"function":"beginWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":129529,"colno":12,"function":"updateClassComponent","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":129552,"colno":31,"function":"finishClassComponent","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":208871,"colno":15,"function":"PatientsList.render","in_app":true}]}}]},"culprit":"http://localhost:8080/scripts/app.js","trimHeadFrames":0,"extra":{"session:duration":572},"breadcrumbs":{"values":[{"timestamp":1520860418.832,"type":"http","category":"fetch","data":{"method":"GET","url":"/api/session","status_code":200}}]},"event_id":"xxx"}

{"project":"xxx","logger":"javascript","platform":"javascript","request":{"headers":{"User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36","Referer":"http://localhost:8080/patients"},"url":"http://localhost:8080/patients"},"exception":{"values":[{"type":"Error","value":"test_error","stacktrace":{"frames":[{"filename":"http://localhost:8080/scripts/app.js","lineno":44494,"colno":37,"function":"response.json.then","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":140827,"colno":18,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219058,"colno":18,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":44471,"colno":9,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":140827,"colno":18,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219061,"colno":16,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":219028,"colno":29,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":144360,"colno":18,"function":"?","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":81984,"colno":7,"function":"dispatch","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":81678,"colno":16,"function":"Connect.onStateChange","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":120259,"colno":16,"function":"Connect.Component.setState","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":127891,"colno":7,"function":"Object.enqueueSetState","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132368,"colno":12,"function":"scheduleWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132411,"colno":11,"function":"scheduleWorkImpl","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132557,"colno":7,"function":"requestWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132646,"colno":7,"function":"performWork","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132696,"colno":42,"function":"performWorkOnRoot","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":131729,"colno":9,"function":"commitRoot","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122117,"colno":27,"function":"invokeGuardedCallback","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122260,"colno":16,"function":"Object.invokeGuardedCallbackDev","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":107334,"colno":21,"function":"HTMLUnknownElement.wrapped","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":122221,"colno":14,"function":"HTMLUnknownElement.callCallback","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":131635,"colno":9,"function":"commitAllLifeCycles","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":132289,"colno":18,"function":"commitErrorHandling","in_app":true},{"filename":"http://localhost:8080/scripts/app.js","lineno":95172,"colno":32,"function":"UnconnectedCatchingComponent.componentDidCatch","in_app":true}]}}]},"culprit":"http://localhost:8080/scripts/app.js","trimHeadFrames":0,"tags":{"test4":"test"},"extra":{"session:duration":645},"breadcrumbs":{"values":[{"timestamp":1520860418.832,"type":"http","category":"fetch","data":{"method":"GET","url":"/api/session","status_code":200}},{"timestamp":1520860419.011,"category":"sentry","message":"Error: test8a","event_id":"","level":"error"},{"timestamp":1520860419.056,"message":"The above error occurred in the <PatientsList> component:\n    in PatientsList (created by RouterContext)\n    in UnconnectedCatchingComponent (created by Connect(UnconnectedCatchingComponent))\n    in Connect(UnconnectedCatchingComponent) (created by AppNext)\n    in div\n    in Unknown (created by AppNext)\n    in IntlProvider (created by AppNext)\n    in AppNext (created by Connect(AppNext))\n    in Connect(AppNext) (created by AppSwitcher)\n    in AppSwitcher (created by Connect(AppSwitcher))\n    in Connect(AppSwitcher) (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router\n    in Provider\n\nReact will try to recreate this component tree from scratch using the error boundary you provided, UnconnectedCatchingComponent.","level":"error","category":"console"}]},"event_id":"xxx"}

@wwwouter two things. Make sure that your actual ErrorBoundry is catching what it should (eg. don't trigger error from the same component that implements it - it won't work).
However, more important is that React does bubble all the errors in development mode and this is what happens in your case.
The first event, that doesn't have tags is triggered using global error handler and only second one is yours. It took me a while to debug as it's not obvious, but this is how React works. It doesn't happen in production.
const BadComponent = () => {
  throw new Error("BadComponent");
};

class ErrorBoundary extends React.Component {
  componentDidCatch(error) {
    Raven.captureException(error, {
      tags: {
        something: "awesome"
      }
    });
    Raven.captureException(new Error("foo"), {
      tags: {
        something: "awesome"
      }
    });
  }

  render() {
    return this.props.children;
  }
}

ReactDOM.render(
  <ErrorBoundary>
    <BadComponent />
  </ErrorBoundary>,
  document.getElementById("main")
);

Here are two screenshots of the output
Development

Production

Hope it helps.

So if I understand it correctly, in development mode the first captureException is ignored?

Well, not really ignored. It's correctly caught by Raven, as it's a proper error. It's React that bubbles it up to the global error handler in development, where, in production, it doesn't.

It is also caught in componentDidCatch, so if it's bubbled, shouldn't that result in the logging of 3 exceptions, with two that have the something:awesome tag?

That's exactly what happens. See my first screenshot :)

Sorry if this is becoming more of on-boarding than an actual issue, but if I look at my dashboard I see only one event. Shouldn't there be two for test8a?
So if one has a tag and the other hasn't, does this result in 1 issue with 2 events? If so, should't the tag be visible? Or should there be 2 issues, with both 1 event?

No worries :) Ok, so there are 2 things going on.

Shouldn't there be two for test8a?

Not in this scenario:
  componentDidCatch(error) {
    Raven.captureException(error, {
      tags: {
        something: "awesome"
      }
    });
    Raven.captureException(new Error("foo"), {
      tags: {
        something: "awesome"
      }
    });
  }

When configured like this, notice that first captureException is exactly the same error as the one caught by the global handler. This means that they are duplicates. If you set Raven.debug = true, then you can see that it's being dropped, as we calculate duplicates based on the exception itself and a stacktrace, which in this case are the same.

If you change the order, so it's:

global hander for thrown error
your custom error, eg. new Error('foo')
captureException for didCatchException

Then it's not treated as a duplicate, as 2 consecutive exceptions are never the same. In this case, we send all 3 of them.

So if one has a tag and the other hasn't, does this result in 1 issue with 2 events?

That's correct. As mentioned above, events are calculated based on exception and stacktrace value, and tags are associated to the specific event.

If so, should't the tag be visible? Or should there be 2 issues, with both 1 event?

If we'd do that, it'd be very noisy. We try to group them as much as possible and assume that the same exception with the same stacktrace will always have the same tags, as it's basically thrown in the same place.

🥇 Thanks for the detailed explanation!


sap.m.Input with suggestions, nonexistent in suggestions initial key

OpenUI5 version:
1.52.9
Browser/version (+device/version):
Chrome
Any other tested browsers/devices(OK/FAIL):
IE(FAIL)
URL (minimal example if possible):
http://jsbin.com/pibuqib/7/edit?html,output
Steps to reproduce the problem:

Run example with JS
Result: "key=, text=text0"
Change used OpenUI5 version to 1.44.8 (or open http://jsbin.com/pazonap/2/edit?html,output)
Run example with JS
Result: "key=id0, text=text0"

What is the expected result?
key=id0, text=text0
What happens instead?
key=, text=text0
Not existed in suggestions key was changed to null
Any other information?
Item with "nonexistent" key is needed, when Input is used as autocomplete element with dynamic suggestions, and this element has default value initially.

Hi,
This was fixed with ff84285d9cf51f066443a52d5b94d600613e8522 and its available at the master
Regards,
Stefan


ServerException instead of ProxyServerError

Steps to reproduce the problem:
>>> from libmproxy.proxy.server import ProxyServer
>>> from libmproxy.proxy.config import ProxyConfig
>>> ProxyServer(ProxyConfig(port=80))
(...)
ServerException: Error starting proxy server: error(13, 'Permission denied')

What is the expected behavior?
According to the documentation:
>>> ProxyServer?
Type:            type
String form:     <class 'libmproxy.proxy.server.ProxyServer'>
File:            /usr/lib/python2.7/dist-packages/libmproxy/proxy/server.py
Init definition: ProxyServer(self, config)
Docstring:       <no docstring>
Init docstring:  Raises ProxyServerError if there's a startup problem.

the expected behavior is
>>> ProxyServer(ProxyConfig(port=80))
(...)
ProxyServerError: Error starting proxy server: error(13, 'Permission denied')

What went wrong?
Maybe the documentation is wrong?
Any other comments?
Nope.

Mitmproxy Version: 0.15-2
Operating System: Debian Sid.

Thanks. It looks like your mitmproxy is outdated. Could you please upgrade an try again?

I think the docstring is still there:
https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/proxy/server.py#L39

Thanks. Could you please send a quick PR that updates the docstring?


reverse-scroll

This pr adds reverse scroll effect to the list.

Thanks, Prakhar, for the PR. Could you please attach a GIF for the working demo of this PR? Also, please add an example in the Usage section of the ReadMe.


test(button-dropdown): add testcase

PR Checklist

[x] Fix linting errors
[x] Label has been added

Change information

Codecov Report

Merging #104 into master will increase coverage by 3.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #104      +/-   ##
==========================================
+ Coverage   23.48%   26.56%   +3.08%
==========================================
  Files         156      156
  Lines        2040     2040
  Branches      451      472      +21
==========================================
+ Hits          479      542      +63
+ Misses       1561     1496      -65
- Partials        0        2       +2

Impacted Files
Coverage Δ

components/utils/collections.ts
41.79% <0.00%> (+29.85%)
:arrow_up:

components/utils/use-click-away.ts
66.66% <0.00%> (+55.55%)
:arrow_up:

components/button-dropdown/icon.tsx
100.00% <0.00%> (+66.66%)
:arrow_up:

...omponents/button-dropdown/button-dropdown-item.tsx
94.11% <0.00%> (+82.35%)
:arrow_up:

components/button-dropdown/button-dropdown.tsx
100.00% <0.00%> (+84.61%)
:arrow_up:

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 9d497f6...f322fd0. Read the comment docs.


docs: add grpc common ACL docs to sdk specific page

References https://github.com/lightbend/kalix-docs/issues/1665
Dependent on https://github.com/lightbend/kalix-docs/pull/1670

I guess CI complaining about https://docs.kalix.io/security/acls.html missing will sort itself soon?

I guess CI complaining about https://docs.kalix.io/security/acls.html missing will sort itself soon?

yeah, thanks Johan. I think I will release the docs first and then re-run/merge this.


Selected on mobile

Thank you for updated! v0.98.1.
I downloaded and tested on my site. But seems not good.
The value is changed but the text not show. It seems is overlayed.

Please add a codepen example

Hi acburst,
Sorry. It only does not show on mobile. I tested on Iphone 4,5.
It does not show text (placeholder and changed value), always blank. But when i submited it still send new value.
I hope you can understand. :)

Are you talking about the select component? I'm not really sure which component we are talking about.

Hi acburst ,
I updated the latest css code. It is working fine.
Sorry for that and thank you so much!

This is still kind of an issue to me. iPhone 5s IOS 9.3.4


Documentation rework - part 2: Updates and corrections

@GLS-SSV What's the status of this one?

This ticket/branch is to bring the documentation up to date (having been converted to LaTeX in the previous ticket).
I've listed some issues to correct and things that need checking to confirm that the documentation matches the implementation, but it needs more eyeballs looking at this.
I can help, but before that I'd like to finish some work in SSV (and I can't even do that right now as I'm currently in a hospital waiting room)

From: Matthew W Hume @.>
Sent: Saturday, August 17, 2024 5:25:41 AM
To: orbitersim/orbiter @.>
Cc: GLS-SSV @.>; Mention @.>
Subject: Re: [orbitersim/orbiter] Documentation rework - part 2: Updates and corrections (PR #459)
@GLS-SSVhttps://github.com/GLS-SSV What's the status of this one?
—
Reply to this email directly, view it on GitHubhttps://github.com/orbitersim/orbiter/pull/459#issuecomment-2294620153, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVCP4TBSG2CUMVAHL576GMLZR3GEDAVCNFSM6AAAAABH3UQOAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGYZDAMJVGM.
You are receiving this because you were mentioned.Message ID: @.***>

Hey GLS,
I hope everything okay.
I'll take a look at what I can do to help on my end.
Best regards,
Matt
On Sat, Aug 17, 2024, 13:53 GLS-SSV @.***> wrote:

This ticket/branch is to bring the documentation up to date (having been
converted to LaTeX in the previous ticket).
I've listed some issues to correct and things that need checking to
confirm that the documentation matches the implementation, but it needs
more eyeballs looking at this.
I can help, but before that I'd like to finish some work in SSV (and I
can't even do that right now as I'm currently in a hospital waiting room)

From: Matthew W Hume @.>
Sent: Saturday, August 17, 2024 5:25:41 AM
To: orbitersim/orbiter @.>
Cc: GLS-SSV @.>; Mention @.>
Subject: Re: [orbitersim/orbiter] Documentation rework - part 2: Updates
and corrections (PR #459)
@GLS-SSVhttps://github.com/GLS-SSV What's the status of this one?
—
Reply to this email directly, view it on GitHub<
https://github.com/orbitersim/orbiter/pull/459#issuecomment-2294620153>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AVCP4TBSG2CUMVAHL576GMLZR3GEDAVCNFSM6AAAAABH3UQOAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGYZDAMJVGM>.
You are receiving this because you were mentioned.Message ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/orbitersim/orbiter/pull/459#issuecomment-2294926708,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYP36F2NDNSIOSUYFY2BTZR6EZHAVCNFSM6AAAAABH3UQOAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHEZDMNZQHA
.
You are receiving this because you commented.Message ID:
@.***>


The issue for the NASFPN module

In your recent NASFPN moule, I found the netwok type is RetinaNet. Have you ever tried the two-stage methods?  Also,the epoch in the configs is set 50. This parametre is solid or can be changed as 1x or 2x?

We do not have enough time and resource to try various settings and just reproduce the results in the paper. It can produce the possibility for users to further investigate it.

I have fix it.

@keetsky

I have fix it.
interesting! what do you fix?
constrain of square resolution?


Ability to run eslint on single files

Is your feature request related to a problem? Please describe.
Linting all files all the time is much slower than linting a single file when it changes.
Describe the solution you'd like
Would be nice if vite-plugin-checker would:

lint all files when starting the dev server
lint all files when building
lint single files when they're changed

Something like
type EslintConfig =
  | false
  | {
      /**
       * lintCommand will be executed at build mode, and will also be used as
       * default config for dev mode when options.eslint.dev.eslint is nullable.
       */
      lintCommand: string | ((file?: string) => string)
      dev?: Partial<{
        /** You can override the options of translated from lintCommand. */
        overrideConfig: ESLint.Options
        /** which level of the diagnostic will be emitted from plugin */
        logLevel: ('error' | 'warning')[]
      }>
    }

would let people write
vitePluginChecker({
  eslint: {
    lintCommand: (file) => {
      const fileOrAllFiles = file ? file : './src/**/*.{ts,tsx}'
      return `eslint "${fileOrAllFiles}"`
    }
  }
})

Describe alternatives you've considered
There is eslint_d, but the nature of the command built by vite-plugin-checker still lints all files.
Additional context
I'm willing to work on this.
Validations

[X] Read the docs.
[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.

Having this problem with a large project and a lot of eslint rules. It takes a lot of time to get feedback in vite due to it rescanning all files. Anything we can do to help?