Not an issue, just a question regarding limiting verbosity

I really like your module and use it a lot in my apps. Usually I'm doing very verbose logging, also in order to simplify my life as developer later on in operation.
But sometimes it is not feasible to "tell everything to everyone". I think I know how to suppress all log outputs, but I'm currently looking for an elegant way to make them disappear at all (even from binary as texts), in case I'm setting a special environment variable at build time.
My attempts to replace your module by dummies failed so far and I don't want to mess up all my code with constructs like this:
if debug {
  log.Info("...")
}

Would you know an elegant but efficient way to achieve this? Silencing all logging, removing all log strings with a snip or trick?

Found it. After having messed with my own pre-processor, which went through all the go files and "sed" all the log entries out I found this neat project, which is pretty much of help here: https://github.com/pijng/go-ifdef


istioctl dashboard bind all addresses

Please provide a description for what this PR is for.
This is to fix this case: the host that running istioctl dashboard xxx  does not install a browser
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure

@esnible
I think istioctl dashboard is mainly a debug tool. We donot need to run it all the way. If you literally think it is worth adding a new flag, i can do that.

Yes, please at least add a new flag for this feature. Opening <IP_ADDRESS> instead of localhost by default is a security vulnerability.

Thanks, will do

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test lint_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test lint_istio

unit-tests_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test unit-tests_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test lint_istio

unit-tests_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test integ-galley-k8s-tests_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test unit-tests_istio

integ-galley-k8s-tests_istio
c40fe84ebf28025c1f66949e493909c611e2034c
link
/test integ-galley-k8s-tests_istio

lint_istio
763dd725639af494f143c497e42fc1bf8fe08c0a
link
/test lint_istio

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

I do not change any behavior, the localhost is the default value used by kubectl and istioctl.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test integ-local-tests_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test integ-local-tests_istio

unit-tests_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test unit-tests_istio

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

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test integ-local-tests_istio

unit-tests_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test unit-tests_istio

lint_istio
9e92907f484b90837b0a8910ee877f605143a5ac
link
/test lint_istio

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


Some simplification of the logic of the write operations

Here i try to reduce amount of code which should be read to understand write operations

This rather complex because we want to try to merge concurrent Put and Delete into single batch. This PR pretty much undo that.

When we try to put or delete single record, we wrap it into batch that can be merged to current write operation. https://github.com/syndtr/goleveldb/pull/246/commits/4469f287c68625e6fe21c7e40e0b7fe4d8f85551
It's looks like logic didn't change.

Sorry, i found where is my mistake. And I wrote benchmark for parallel putting and it shows that my commits increase allocations.
$ benchstat old new
name             old time/op    new time/op    delta
DBPutParallel-4    7.69µs ± 6%    7.92µs ± 6%      ~     (p=0.075 n=10+10)

name             old speed      new speed      delta
DBPutParallel-4  15.1MB/s ± 5%  14.6MB/s ± 6%      ~     (p=0.075 n=10+10)

name             old alloc/op   new alloc/op   delta
DBPutParallel-4     37.9B ± 5%     76.4B ± 2%  +101.72%  (p=0.000 n=8+10)

name             old allocs/op  new allocs/op  delta
DBPutParallel-4      0.00           1.00 ± 0%     +Inf%  (p=0.000 n=10+10)


SortPreservingMerge Special Case Single Column

Is your feature request related to a problem or challenge?
SortPreservingMerge currently always uses the arrow row format, this provides compelling benefits when sorting by a tuple of multiple columns. However, it is often the case that a sort is being performed on a single column. lexsort_to_indices which is used by SortExec detects this case and calls through to sort_to_indices which has specialised implementations for each column type. This significantly outperforms converting to the row format as it allows for fixed width comparisons, which are significantly faster
Describe the solution you'd like
I would like to be able to use a specialized, fixed width sort cursor within SortPreservingMerge
Describe alternatives you've considered
No response
Additional context
https://github.com/apache/arrow-datafusion/pull/5854 contained a POC implementation of this

cc @jaylmiller


Badly formatted json configuration file hangs the IDE

Steps to reproduce

Install Csharpier extension in Visual Studio (Community) or Jetbrains Rider on Windows 10
create the following configuration in the expected json file (both .csharpierrc or .csharpierrc.json will reproduce) but with a wrong format, i.e. notice the double quotes missing for properties:

{
    printWidth: 120,
    useTabs: false,
    tabWidth: 4
}

Set up csharpier to run on save
Save any file (triggers the formatting)

Expected
The formatting does not work, something tells us that the configuration file is badly formatted.
Actual
The IDE (either VS or Rider) completely hangs, nothing can be done except:

fixing the file (which un-hangs the IDE immediately)
killing the IDE in the task manager

I believe I fixed this problem in #1191, when the cli was throwing an exception the plugins would hang because the cli didn't send back a response indicating it was done trying to format.


Product implementation

Product entity
Category entity
implementation of adding an image
implementation of adding a product
implementation of adding a category by the admin
implementation of exception handler

added @NoArgsConstructor annotation at Image.java
modified the validation of credentials from UserService.java
modified exception password
added @requiredargsconstructor for CategoryService.java


Ghost Scheduled Messages, Continue to Post After Deletion

(Filling out the following details about bugs will help us solve your issue sooner.)
Reproducible in:
The slack_bolt version
slack-bolt==1.5.0
slack-cleaner==0.7.4
slack-sdk==3.5.1
slackclient==2.9.3
slacker==0.14.0
Python runtime version
python 3.8.5
OS info
#60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021
Steps to reproduce:
(Share the commands to run, source code, and project settings (e.g., setup.py))
Bot is a message scheduling bot, that automatically schedules positive messages to chat. In the app_home the user can select a channel to schedule messages to, remove messages, edit the messages dates and times, and reset and user changes made.

Bot is run on local machine
User selects channel to schedule messages to
User adds bot to that channel via slack
User selects a message pack, where messages are scheduled from. Messages are scheduled once very Monday, Wednesday, Friday
User edits a message, schedules a specific to be posted in 2-5 minutes of local time
User selects a new channel. (This step removes all current scheduled messages)
The old edited message will appear in the old channel

Expected result:
We expect the old edited message to not appear in the channel, since when the channel is reassigned. It first deletes all scheduled messages by the bot
(Tell what you expected to happen)
Actual result:
The message the user edited to schedule in the next 2-5 minutes will post even though all messages in that channel have been removed
(Tell what actually happened with logs, screenshots)
The edit message being scheduled is shown in the first step. Shown in scheduled messages and on the right we see the same scheduled message is shown in Slack API

We show that the bot is currently in #CS-1 channel

This action has occurred after the channel has been changed to #CS-2 channel (it's not reflected in the app_home because it hasn't been refreshed), we can see that remove scheduled messages has been called 11 times, and Slack API states that in the #CS-1 channel has no scheduled messages present

##Context
One thing to note is that when messages are being edited (deleted and rescheduled at a new time)
try:
  BOLT.schedule_message()
except slackapierror (invalid date/time):
  post_to_user(enter a valid time)
else:
  try:
    BOLT.delete_message()
  except SlackAPI Error (something went wrong with deleting a message)
    log(error)
  else:
    post_to_user("Congrats on rescheduling your message to the new time")

Some more context I performed an experiment where I schedule messages in time intervals of 5,10,20,30+ minutes, then change the channel, which again deletes all of the bots currently scheduled messages. This error only occurs for the message edited to be posted within 5 minutes, all messages edited to be scheduled for later do not post.
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @mu6-Abdullah, thanks for asking the question!
Honestly, I'm still unsure about what's happening in your app as the details like how you call the APIs are not shared here. On the assumption where your app correctly utilizes chat.scheduleMessage and chat.deleteSheduledMessage, the only thing I can guess is that your app might not do pagination for chat.scheduledMessages.list API call (you're calling this for fetching all the messages to delete, right?). In the case, some of the messages you wanted to delete may remain when there are more messages in the next page. Refer to https://api.slack.com/methods/chat.scheduledMessages.list for more details of pagination.
I hope this was helpful to you!

@mu6-Abdullah Also, I strongly recommend revoking the tokens in the screenshots.

👋 Hi @mu6-Abdullah, let us know if you need further help here. I will close this issue after waiting for your response for a while.


Fix python scripts to be able to run with python3

Fix python scripts to be able to run both with python2.7 and python3

I verified outputs for these scripts are same before and after this change.

Merged, thanks!


VR Support

this assets supports VR ? i tried to use with vr ambience but they render totally broken, without VR my setup work's correctly. is there a special config to work with VR ?

I haven't tried in VR, since I developer on Linux and the headsets aren't really supported. But I'm not surprised it doesn't work, as I'm doing some weird tricks with the viewport that likely cause conflicts. In any case, I'm not working on this anymore. Godot 4.0 supports FSR (and also bilinear interpolation) and I found the default options to be better than my add-on. FSR is a lot better at high resolution (though my shader looks a little better at very low resolution) and bilinear looks almost as good with better performance and less problems. For Godot 3.x it is still useful, but I think the setup is too much for larger game.


Describe how to visualize and query the stored state including actor state

These articles describes how to view/query the state data for both Redis and CosmosDB whether the state is stored via the /state call or via actors. Many people have asked what the schema is like and how to do the query.

Closing it as this is documented:
https://github.com/dapr/docs/blob/master/reference/api/actors_api.md#querying-actor-state-externally
https://github.com/dapr/docs/tree/master/concepts/state-management#querying-state-store-directly


didyoumean: 1.1.0 -> 1.1.3

Checklist

[X] Checked the nixpkgs master branch
[X] Checked the nixpkgs pull requests

Project name
nix search name: didyoumean
current version: 1.1.0
desired version: 1.1.3
Notify maintainers
maintainers: @evanjs
Note for maintainers
Version 1.1.3 comes with a man page as well as shell completions for a few shells (bash, zsh, fish, elvish). I'd like to have the script install these. I'm more than willing to do the actual update myself, but I'm very new to Nix, so I'll probably need some guidance, specifically on how to install these completions and the man page, and how to update the sha256 hash.
Thanks!

To update the sha256 hash, you can simply set sha256 = ""; and cargoSha256 = "";, and update them as suggested by nix build .#didyoumean. Having done it right, you'll have

  src = fetchFromGitHub {
    owner = "hisbaan";
    repo = "didyoumean";
    rev = "v${version}";
    sha256 = "sha256-hHl9PGNDFN7Dad2JOlAy99dz0pC9OmphwYMJHBBwx7Y=";
  };

  cargoSha256 = "sha256-rjkj9MO6fXVOk3fA87olGt/iIaJ8Zv/cy/Cqy/pg6yI=";

To install the man page and the shell completions, set

  nativeBuildInputs = [
    installShellFiles
  ];

  postInstall = ''
    installManPage man/dym.1
    installShellCompletion completions/dym.{bash,fish}
    installShellCompletion --zsh completions/_dym
  '';

You may also need to set doCheck = false; on some platforms (at least on aarch64-darwin?). Before doing this, feel free to make a pull request.

I'm running into some issues trying to test it to ensure it's doing what I want it to. I'm going to the directory with didyoumean/default.nix in it and running nix-build but I'm running into issues regarding installShellFiles being undefined:
error: undefined variable 'installShellFiles'

       at /home/hisbaan/projects/nixpkgs/pkgs/tools/misc/didyoumean/default.nix:34:25:

           33|
           34|   nativeBuildInputs = [ installShellFiles ];
             |                         ^
           35|   postInstall = ''

Any pointers? I wasn't able to find anything searching through the web

installShellFiles needs to be in the attrset at the top of the file for you to be able to use it.

As @winterqt explained, we need to add
, installShellFiles

at the top of the file.


fix: disable metrics endpoint if no port provided

Setting the metrics port under app.metrics_port as 0 disables the default endpoint and metrics collection for Prometheus.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 42 (0.0%)  changed or added relevant lines in 3 files are covered.
11 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 9.474%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/server.go
0
4
0.0%

cmd/serve.go
0
17
0.0%

pkg/server/server.go
0
21
0.0%

Files with Coverage Reduction
New Missed Lines
%

cmd/server.go
11
61.9%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
10263

Relevant Lines:
108332

💛  - Coveralls


MASS showing incorrect item playing on Google cast device if started playing from outside MASS

What version of Music Assistant has the issue?
2.2.2
What version of the Home Assistant Integration have you got installed?
2024.8.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
I am casting a story from Audiobookshelf to my Google cast device. The Google Cast integration correctly displays what is playing, but the MA one shows a random song.
I am pause and play using the MA one, so it just seems to incorrectly label the item, likely as it doesn't know what it is as it's not from within MA.
I presume this is a known issue, but I couldn't find any talk of it. Probably searching for wrong things.
Just wondering what I can do about this, if anything?

How to reproduce
Play media from Audiobookshelf of a Google cast device, check what is playing in MA
Music Providers
Native MA providers don't have this issue
Player Providers
Google Cast (only devices I have)
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.8.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

No you can’t do anything about this. MA has no visibility of third party applications streaming to supported players at this time. You will notice the same thing with Airplay.

P.S. nice post but if you want to save some time you can ask on Discord about this sort of thing

Ok cheers. Will head to discord to check if anyone has a solution as I can use visibility filters to only show MA media based players when x condition is true, and if false show standard / google cast ones... Or I live with having two media players showing (no biggie really).
Just a bit odd it is showing a random song? I would have thought it would have would blank or something.


feat(anthropic): streaming support

[x] add streaming support for completions
[ ] add streaming support for async completions
[x] add streaming support for messages
[ ] add streaming support for async messages
[x] add streaming support for tool calling response
[ ] resolve issues around assumptions about first content block in a message being a text output
[ ] resolve all other TODOs

@harrisonchu  Is this one ready for review, or do you want to wait till you get back from PTO?


Transmuxing Error for some HLS streams

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?

4.12.5, 4.9.2-caf3, 4.9.2-caf2
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Latest Chrome version, macOS
What are the manifest and license server URIs?
These streams are from Exoplayer's Cast demo app.
HLS (adaptive): Apple 4x3 basic stream (TS/h264/aac)
https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_4x3/bipbop_4x3_variant.m3u8
HLS (1280x720): Designing For Google Cast (TS/h264/aac)
https://commondatastorage.googleapis.com/gtv-videos-bucket/CastVideos/hls/DesigningForGoogleCast.m3u8
I don't use any extra configuration.
What did you do?

Tested casting the streams from the Exoplayer Cast Demo app and they gave an error like below.
{"type":"ERROR","detailedErrorCode":100,"severity":2,"error":{"shakaErrorCode":3018,"shakaErrorData":["https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_4x3/gear4/fileSequence1.ts"],"shakaErrorStack":"Error: Shaka Error 3018\n    at new T (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:66:296)\n    at HD.r.transmux (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:1498:205)\n    at Ea.h (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:412:359)\n    at Ha (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:21:299)\n    at Ja.next (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:22:91)\n    at https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:22:484\n    at new Promise (<anonymous>)\n    at Ka (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:22:377)\n    at P (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:23:22)\n    at vk (https://ajax.googleapis.com/ajax/libs/shaka-player/4.12.5/shaka-player.compiled.js:410:149)","shakaErrorSeverity":2}}

Also tested at https://shaka-player-demo.appspot.com but still produces errors like:
[Shaka Error MEDIA.TRANSMUXING_FAILED (https://commondatastorage.googleapis.com/gtv-videos-bucket/CastVideos/hls/designing_for_google_cast/fileSequence0.ts)](https://shaka-player-demo.appspot.com/docs/api/shaka.util.Error.html#value:3018)

What did you expect to happen?
These streams were working on Web Receiver if you dont opt-in with useShakaForHls: true and add a line like
loadRequestData.media.hlsSegmentFormat = cast.framework.messages.HlsSegmentFormat.TS;
However, after opting-in to use Shaka for HLS streams, they showed errors.
For versions of 4.12.5, 4.9.2-caf3, 4.9.2-caf2 they produce the transmuxing error.
Interestingly downgrading my Web Receiver's Shaka version to 4.3.4 makes the first HLS (adaptive): Apple 4x3 basic stream stream work. But, produces different error for the second stream like below:
[cast.framework.media.ShakaPlayer] category: 4
code: 4032
stack: undefined
severity: CRITICAL
data: []

Are you planning to send a PR to fix it?
It's probably beyond my level of understanding

https://commondatastorage.googleapis.com/gtv-videos-bucket/CastVideos/hls/DesigningForGoogleCast.m3u8 --> PR to fix it: https://github.com/shaka-project/shaka-player/pull/7813
https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_4x3/bipbop_4x3_variant.m3u8 --> I don't have a complete solution yet, but part of the solution is included in the other PR.


Build Java8-compatible release

Use the new options.release Gradle property to make sure builds are
compatible with Java 8, which is the runtime on Appengine.
This new property replaces sourceCompatibility, targetCompatibility, and
bootclasspath (wasn't previously set, which is the reason why we
couldn't detect Java9 api usage when building).

This change is

You have the following error when compiling:
> Task :docs:compileJava FAILED
error: exporting a package from system module jdk.compiler is not allowed with --release
error: exporting a package from system module jdk.compiler is not allowed with --release
error: exporting a package from system module jdk.javadoc is not allowed with --release
3 errors


[2.19.0] Private git repository stack update webhook failing

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
After successfully creating a stack from a private git repo, trying to pull and redeploy the stack using the GitOps webhook URL results in an authentication error despite the git credentials previously working to create the stack.
Expected Behavior
I send a POST request to the stack's Webhook URL and the Portainer pulls and redeploys the stack.
Actual Behavior
Sending a POST request to the webhook URL returns the below authentication error.
Steps to Reproduce

Create a stack using a private git repository
Enter git credentials or select saved git credentials
Enable GitOps updates with the Webhook option and Re-pull image enabled
curl the Webhook URL for the newly created stack

Portainer logs or screenshots
{"message":"Failed to update the stack","details":"failed to fetch latest commit id of stack:154: authentication failed, please ensure that the git credentials are correct"}
Portainer version
2.19.0
Portainer Edition
Business Edition (BE/EE) with Home & Student license
Platform and Version
Docker version 20.10.24+dfsg1, build 297e128
OS and Architecture
Debian 12
Browser
Firefox 117.0
What command did you use to deploy Portainer?
version: '3'
services:
    portainer:
        image: portainer/portainer-ee
        container_name: portainer
        restart: unless-stopped
        volumes:
            - '/var/run/docker.sock:/var/run/docker.sock'
            - 'portainer_data:/data'
        ports:
            - '9000:9000'
volumes:
    portainer_data:

Additional Information
Portainer is version 2.19.0

Same thing here. Pulling the stack works ok on the web UI, triple checked that the git credentials were correct, and were working.
Also getting: failed to fetch latest commit id of stack:6: authentication failed, please ensure that the git credentials are correct

I experience the same problem.

Same issue, Only on 2.19 - Downgraded back to 2.18.3 issue resolved, Please fix

I can confirm that too. Downgrading to version 2.18.x doesn't fix it for me.

I can confirm too. same issue on 2.19

same issue on 2.19

Same here, 2.19.0 too, Business Edition

Thanks for raising the issue and all the updates.
We are working on a fix and will be included in a patch release.

Uhm a update - I just tried to redeploy the stack and the issue with authentication required is suddenly gone - it deployed without issues... seems nothing was updated but still it fixed itself and I cannot figure out why... - but 2.19.1 does fix the Private Registry issue - so I think this can be closed, @Choff3

@ThaDaVos I still have the same issue on 2.19.1

@Choff3 I'll check my instance again tomorrow to make sure - maybe there's a difference in how the webhook fired which I missed - but I did try to UI before which was broken on 2.19.0 - which worked now
Like I said, I'll check again - if it works on my side - we may be able to diagnose the issue better (like it being a setting or something)

Same problem 2.19 businesss edition

Same probrem 2.19.1 BE. The webhook works fine for local stacks, but I get the error
{     "message": "Failed to update the stack",     "details": "failed to deploy a docker compose stack 17: an error occurred while running unpacker container with exit code 255: authentication required" }
For Stacks controlled by a Portainer agent.

I did another test. The problem happens either in the local environment or in an agent environment. What seems to trigger the error is to enable the Enable relative path volumes option. Creating a stack without a relative path volume seems to solve the problem.
But, there is an issue 7254 that describes that in order for agents to deploy a stack  using a git repository, adding a relative path volume is needed.

It seems the credentials for git aren't passed to the compose-unpackr container anymore - I have a command line helper to extract the information out of the container when it's started - I can share it here if needed - but I noticed the difference between the run commands 2.18.x and 2.19.1 - better said, the difference seemed to occur between 2.19.0 and 2.19.1 even - for some reason the credentials aren't passed to the container so it can no longer login to the private git repo to unpack it
And yes, it only happens when one uses the Enable relative path volumes as only then the compose-unpackr container is used

We believe this issue may be resolved as part of the fix for #10340 which has rolled out as part of 2.19.2.

Running 2.19.2 and webhook other than replying with 204 No Content does nothing :/

Running 2.19.2 and webhook other than replying with 204 No Content does nothing :/

This is a separate bug, and should now be resolved with the 2.19.3 release.

I just tested the webhook on 2.19.3 and it seems to be working.

The webhook still does not work on 2.19.3,
Failed to deploy a docker compose stack 234: an error occurred while running unpacker container with exit code 255: authentication required
Only manually redeploying in ui works.

Thank you for fix, it indeed works now. Also thank you for easy Portainer upgrades without needing to SSH into the server. It's really nice!

The webhook does not work on 2.19.3 for me as well.

It seems there's a split as to whether this has fixed the issue or not - those that are still experiencing the issue, are you able to provide feedback and more detail on your setups so we can figure out what's going on for you?

last tested in 19.2 - private github repository with hooks enabled. Calling the hook takes a few seconds but does not do anything

It seems there's a split as to whether this has fixed the issue or not - those that are still experiencing the issue, are you able to provide feedback and more detail on your setups so we can figure out what's going on for you?

We are running multiple nodes with portainer agents as docker containers on multiple servers, portainer itself is running as docker container as well on a different node.
Using the webhook gets me this message:
failed to deploy a docker compose stack 234: an error occurred while running unpacker container with exit code 255: authentication required
But clicking on repull and deploy in the ui does work and the webhook also works if the stack runs on the same server as portainer ui so it seems it may only be a problem with the agent.

It seems there's a split as to whether this has fixed the issue or not - those that are still experiencing the issue, are you able to provide feedback and more detail on your setups so we can figure out what's going on for you?

We are running multiple nodes with portainer agents as docker containers on multiple servers, portainer itself is running as docker container as well on a different node.
Using the webhook gets me this message: failed to deploy a docker compose stack 234: an error occurred while running unpacker container with exit code 255: authentication required
But clicking on repull and deploy in the ui does work and the webhook also works if the stack runs on the same server as portainer ui so it seems it may only be a problem with the agent.

We experience the same behaviour.

I have the same issue Invalid git credential: authentication failed, please ensure that the git credentials are correct.
Community Edition: 2.19.4
I propose a solution in the case of the above mentioned error messages.
In this case, Portainer GUI should provide an input field for "Personal Access Token" within the concerned Stack project.

Just hit this issue using Portainer EE. It's a stack deployed from GitHub with enable relative path volumes turned on. I can deploy the stack via the UI but when I try via the webhook I get this error:
{"message":"Failed to update the stack","details":"failed to deploy a docker compose stack 4: an error occurred while running unpacker container with exit code 255: authentication required"}

We believe this has been fixed in 2.20.0 - are those of you experiencing this perhaps able to update and confirm whether this has been resolved?

We believe this has been fixed in 2.20.0 - are those of you experiencing this perhaps able to update and confirm whether this has been resolved?

I'll give it a go in the next day or so!

I updated to 2.20.0 by pulling the new Docker image. I then enabled GitOps webhook for one of my existing stacks and tried to hit it with Postman. Result:
{
    "message": "Unable to find the stack by webhook ID",
    "details": "Object not found inside the database"
}

I've triple checked that I'm hitting the URL that the page provided me for the webhook.

I tried with another stack and got the same error.

That's a different error to what you were initially seeing (and what the fix was focused on). I've just tested here locally with the same steps I used to reproduce initially, and the webhook is now working for me without issue.
Do you see the same error if you create a new stack then try?

That's a different error to what you were initially seeing (and what the fix was focused on). I've just tested here locally with the same steps I used to reproduce initially, and the webhook is now working for me without issue.
Do you see the same error if you create a new stack then try?

I haven't tried a new stack yet. I can, but I also have many stacks I'd be using this for so recreating everything will be not fun 🥲

I haven't tried a new stack yet. I can, but I also have many stacks I'd be using this for so recreating everything will be not fun

Understandable. I'm trying to work out where the issue actually is.

Understandable. I'm trying to work out where the issue actually is.

Yep.
Stack re-created, hit the endpoint, which took long enough to respond that it was clearly pulling and restarting the stack. Seems to be working. I got back a "204 No Content" response, and the stack shows it's been running for "a few seconds".

Great, thanks - so it sounds like the issue is with existing stacks. I'll need to do a bit more testing here and consult with the team, but I'll come back to you once I learn more.

I haven't been able to reproduce this with an existing stack either... can you try disabling GitOps updates on one of your stacks, re-enabling it, then using the new webhook URL and trying again?

We believe this has been fixed in 2.20.0 - are those of you experiencing this perhaps able to update and confirm whether this has been resolved?

works for me, many thanks @jamescarppe!

I haven't been able to reproduce this with an existing stack either... can you try disabling GitOps updates on one of your stacks, re-enabling it, then using the new webhook URL and trying again?

I tried that a couple of times before my initial comment about the error.
Here's some additional details:

None of my stacks had GitOps enabled prior to updating
I did a git pull of :2.20.0 to get the latest version then restarted Portainer. I didn't stop any of my stacks prior to this
I enabled GitOps on a stack
I hit the webhook URL via Postman

When it didn't work I toggled GitOps and used the new resutling webhook URL and got the error again.


fixing date selection for daily monthly data

Using Zoe's data as test, some of the last changes break date selection instead of "0950" year is listed as "9500"

This is now fixed in 7838eb6cb146e9dbd04472f25b12fa2501fddf6a
generally handling of dates and interval is improved and oncistent across mop_setup and cli.py


[Question]

Checklist

[x] I'm asking a question
[ ] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE
i want to download dash fragment (mpd)  in allow-unplayable formats but there a lot of audio can i download one video and multi langauge or can i select audio by language auto? like lange=englsih?

-f bv,ba[language=en],ba[language=hi]
Read https://github.com/yt-dlp/yt-dlp#filtering-formats

-f bv,ba[language=en],ba[language=hi]
Read https://github.com/yt-dlp/yt-dlp#filtering-formats

can i download all audio ?

-f bv,all[vcodec=none]

Read https://github.com/yt-dlp/yt-dlp#filtering-formats

Read the documentation before asking questions


Can you add alphabetic sort of methods in structure panel?

C#?

yes

Fixed. Please use next time - C# repository https://github.com/consulo/consulo-csharp

sorry about that, and one more time thank you very muck for all your work.


Failed to import - rollup-plugin-cleanup requires --allow-env since v59

Failing module

GitHub: https://github.com/aMarCruz/rollup-plugin-cleanup
npm: https://www.npmjs.com/package/rollup-plugin-cleanup

import cleanup from "https://esm.sh/rollup-plugin-cleanup@3.2.1?pin=v59";

Error message
After running deno run --unstable I got this:
error: Uncaught PermissionDenied: Requires env access to "NODE_ENV", run again with the --allow-env flag
    Deno.env.set(String(prop), String(value));
             ^
    at Object.opSync (deno:core/01_core.js:149:12)
    at Object.setEnv [as set] (deno:runtime/js/30_os.js:59:10)
    at Object.set (https://deno.land/std@0.122.0/node/_process/process.ts:57:14)
    at https://cdn.esm.sh/v59/rollup-pluginutils@2.8.2/deno/rollup-pluginutils.js:2:95

When importing with ?pin=v58 it works fine.
Additional info

esm.sh version: v59 and later
Deno version: 1.17.0

To be clear, running with --allow-env is not an issue for me. I'm just wondering if something broke unintentionally.

i just switched the node(process) polyfill to https://deno.land/std/node/process.ts instead of browsers in latest update, so you need the --allow-env flag as deno secure protocol when you access to "NODE_ENV"


Tempered Mind

Listed in game as +125 to Accuracy Rating per 10 Intelligence on Unallocated Passives in Radius
Listed in POB as   +100 to Accuracy Rating per 10 Intelligence on Unallocated Passives in Radius
9/16/2019 Version 1.4.152

Fixed in PR #1764


[Bot Flow] Fix: static flow should not include disabled stories

To reproduce:

Create a configured story
Add a story rule to disable the story on All configurations
Open Blot Flow and switch to Static view
The story is visible

Enhancement: provide checkbox to include or not disabled stories in flow.


Add endpoint that enables parallel transfer for large files

Enhancement / Investigation
This issue is about providing users with a way to transfer large files through the REST API into an iRODS zone.
The interface can be modeled after the S3 API or something else. Before doing that, we need to know what is provided by an iRODS server as that will influence the design.
Basic Parallel Transfer Steps
For 4.2.11 and 4.3.0, parallel transfer (over port 1247) is accomplished by doing the following:

Open a stream using rc_replica_open().
Use the replica access token, returned by the previous API call, to open N additional streams to the same replica.
Transfer bytes across the streams.

Streams must not overlap.

When closing the streams, the first stream MUST be closed last.

This guarantees that policy is triggered correctly (i.e. replication resources, etc).
Use rc_replica_close() to close the streams.

Only the first stream should update the catalog (this improves performance by avoiding unnecessary catalog updates).

Things to Consider
Q. Should this be implemented as part of the /stream endpoint or as a separate endpoint?
Q. Should the REST API provide an endpoint for data transfer at all? Perhaps users should use a different API for transferring large amounts of data.
Q. Where should additional state (i.e. connections, streams) be managed? In the REST server or in the client?
Q. What happens if you have a large number of clients interacting with the REST server?
Q. Should things be implemented using a queuing system (i.e. pipelining)?

Another two usecases / considerations are

transfer restart/retry and
API restart

This is of interest to us and contemplating the client side of the questions:
Q. Should this be implemented as part of the /stream endpoint or as a separate endpoint?
R: the future increased buffers will be a good thing, but it would be great if we could just stream bytes and not have to manage chunking across multiple requests on the client side (unless we are doing something wrong)
Q. Should the REST API provide an endpoint for data transfer at all? Perhaps users should use a different API for transferring large amounts of data.
R:  A different API for large vs. small is very difficult to determine from the client side (we don't know how large the byte stream is when it starts)
Q. Where should additional state (i.e. connections, streams) be managed? In the REST server or in the client?
R: Generally - simpler clients are better unless there are specific overhead or performance reasons to manage things there.
Q. What happens if you have a large number of clients interacting with the REST server?
R: We fall into this category with our project, we will have potentially many dealing with large files.
Q. Should things be implemented using a queuing system (i.e. pipelining)?
R: with a simple client protocol, this probably makes sense to limit the concurrent from a single client (configurable probably)

This work has been incorporated / implemented in the new HTTP API.
https://github.com/irods/irods_client_http_api


Decrease log noise for event watch

Omit error logs for event watch requests that exceed their context
deadline. This reduces log noise when clients don't close watch requests properly.
Addresses #1956

The only reason I am hesitant about this change is that we had some watch context deadline exceeded errors previously that were symptoms of an actual issue. Are we confident that these deadline exceeded errors are not a problem?

Ditto what Donnie said. I think we might be missing another LongRunningResource.

The only reason I am hesitant about this change is that we had some watch context deadline exceeded errors previously that were symptoms of an actual issue. Are we confident that these deadline exceeded errors are not a problem?

Fair enough. I'll print the request headers to see if I can track down the source of the request and go from there.

@g-linville IIUC long running resources are specifically for custom sub-resources. I don't know of an instance where we set it for a "normal" resource like events.

I think that is what we typically use it for but I think it might be worth trying for events also, if mink will accept it for non-subresources. If the events take so long to stream that we hit the context deadline, then that seems like the most straightforward way to fix it, unless there is also a way to somehow make the event streaming faster.

I'm going to close this PR out since it's gone stale; @ibuildthecloud  has mentioned that he doesn't like the channel abstractions I'm using anyway, so I was already planning on refactoring this at some point -- maybe I'll spot something when I do.


Add how to send real emails to the README

Testing emails end to end was required for some of the features I'd been working on recently. This is a reminder to myself to remember to document how I got everything working.

Closing this as the profile archival project needs more work, and we should have an explicit step with all features to update documentation.


Formatting of results.json (DDA_quant) is not consistent and sometimes not a valid JSON

The formatting of the 2 files is not the same:
https://github.com/Proteobench/Results_Module2_quant_DDA/blob/main/results.json (used in main branch)
https://github.com/Proteobot/Results_Module2_quant_DDA/blob/main/results.json (used in testing branch)
We have 3 possible approaches:

"Proteobench" version uses fixed IDs (0,1,2,3,..) for each datapoint. The benefit is that it allows the identification of datapoint, however, it makes the structure hard to manage (e.g., if we delete a datapoint an ID would be missing).
The "Proteobot" version is JSON file generated by pandas, which is not a valid JSON object (such as {"A":"1"}{"A":"2"}), which makes it difficult to process the file with off-the-shelf tools (e.g., JSON formatters/viewers).
An alternative would be to have an equivalent to Proteobot which is a well-formatted JSON. For example, instead of having a JSON {"A":"1"}{"A":"2"} we could have it formatted as an array of objects [{"A":"1"},{"A":"2"}]

Regarding point 2. I have some custom code to create valid JSONs from Pandas... If I remember correctly they per default just export the numpy type.

I have had a look. I think this will fix the issue:
all_datapoints.to_json(         f,         lines=True,         orient="records"     )
See:
https://github.com/Proteobot/Results_Module2_quant_DDA/pull/53
Is now on this branch:
https://github.com/Proteobench/ProteoBench/tree/fix_json

As @vedran-kasalica mentioned I think we should now format it to an array.

Ok, I think we can address all issues with the following code:
all_datapoints.to_json(         f,         orient="records",         indent=2     )
See PR:
https://github.com/Proteobot/Results_Module2_quant_DDA/pull/54/commits/3df7832d9674d3caca8d0bcf1373ba444aceb6c4


portal.loganalytics.io non-functional

Earlier I could access all my workspaces' logs thru "portal.loganalytics.io". However, now the URL isn't working
Error: The URL is invalid.
Open your Application Insights resource in the Azure portal, and then click Analytics.
If that doesn't work, please let us know, quoting this correlation id: ecee8809-97fb-4df6-98fb-c2a54e7eb3e9

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

ID: 3a095ce2-9793-153f-59aa-6c6830ec8c92
Version Independent ID: 651187ab-40fa-ed37-2e2c-1e804fe40282
Content: Viewing and analyzing data in Azure Log Analytics
Content Source: articles/azure-monitor/log-query/portals.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

Hey, I am unable to open the  https://portal.loganalytics.io/demo#/discover. It shows me 502 bad gateway


mod.ts?

I stumbled over your neat discord lib and it sounds promising.
But why isn't the mod.ts exporting stuff from the module but instead calling Client()?
e.g. https://deno.land/std/async/mod.ts

@alex-vg Hi  👋
So the mod.ts file is just for debugging purposes that helps me easily add features and test them before i deploy them. It's never meant to be used. Once the library has been well tested and thoroughly completed i will remove the mod.ts file entirely. While we still need the --unstable flag for things inside deno I need to be able to easily test on the fly without pushing code then pulling it in my bot and etc...
When you use the lib to create the bot all you do is createClient(yourOptions). My advice is to check out one of the boilerplate/frameworks and you can get the base of a bot built for you to start with.
Hope that help clarifies it

Yeah, the mod.ts is for debugging purposes only. Me and Skillz use it :-)

I don't think removing the mod.ts is a great idea, since you have to import something from the lib and that's where people look take a look.
A lot of other libraries points out what to import by using the mod.ts and I would expect the createClient in the mod.ts if that's what I need to use.

i agree with @alex-vg here; mod.ts is the standard place for modules to export stuff so it would make sense to use that & all

I don't think removing the mod.ts is a great idea, since you have to import something from the lib and that's where people take a look.

I'm not entirely opposed to having a mod.ts file that exports everything. I just mean that it isn't entirely necessary imo. Realistically speaking, you can achieve the same result with a deps.ts file which you can add or have it in a boilerplate(which i plan to add). Until now everyone i know using this lib used the boilerplate and never had this issue. I do understand it could help i just thought exporting who knows how many things functions from mod.ts would be bad. The amount of types/interfaces/structures/modules/etc... It's just gonna make mod.ts be a mess and add duplicate code to maintain.
In my opinion, a better README explanation should suffice and tell people how to import createClient better

A lot of other libraries points out what to import by using the mod.ts and I would expect the createClient in the mod.ts if that's what I need to use.

I'm not sure about other libs as I haven't tested them myself yet but when you code with Discordeno and try to import something, it will auto-import everything whenever you need it. You won't really have trouble trying to go "which file do i import Message or Member from?". It's all automated. The only time this happens is with createClient but if you use one of the boilerplates all that is handled for you entirely. I suppose I should consider adding a section on the README about what to do to start a bot if you don't want to use the boilerplate which could explain this whole thing.

mod.ts is the standard place for modules to export stuff so it would make sense to use that & all

I do understand that part but it's just unnecessary and duplicate code in my opinion. I like to have DRY code. All of these exports are already being exported from their own files.

All that said if any of you want to send a PR to change it like I said above I am not entirely against it. I just feel it's unnecessary. But if it helps you all then go for it! I'll happily accept it.

it's not "duplicate code" to just... export x from "y" i feel
mod.ts is a standard and would be better especially if you dont have any readme showing where to import the main stuff from

...or export * from "y"

mhmm... importing a bunch of stuff from different places for a single module on the user end feels a lot more like "duplicate code"..

Our of curiosity why do you feel that exporting something that's already exported is not duplicate and redundant?

mhmm... importing a bunch of stuff from different places for a single module on the user end feels a lot more like "duplicate code"..

On the user end this is just deps.ts which will be part of the boilerplate

do you think
import { x } from "placeone"
import { y } from "placetwo"
import { z } from "placethree"
import { w } from "placefour"

instead of just...
import { x, y, z, w } from "oneplace"

on the user-end is worth having a little bit of "duplicate code" to export stuff from a single place?

@fox-cat That's a fair point but isn't that just a deps.ts 🤔

what?
also - sure, your module, you should handle exports how you want - but having a mod.ts that doesn't export anything on a module is confusing - if it's a test file, i would rename to test.ts or something

@fox-cat That's a fair point but isn't that just a deps.ts 🤔

Yeah, just another name, but mod.ts seems to be default in deno. But I could not find a best practice or anything.

deps.ts is what the user would use to import a bunch of stuff so they dont need janky links
(e.g. export.ts)
export { x, y, z } from "place"
export { w } from "place1"
export { h, j } from "place2""

then in their app.ts or whatever
import { x, y, z, w, h, j } from "./deps.ts"

mod.ts is what the default/ "standard" seems to be in deno for exporting stuff in modules, but it's just that, a standard, no need to conform to it

Isn't deps.ts for importing dependencies?

@alex-vg @fox-cat @Ryaangu Let me know if #41 is enough to help. I still feel it's a bit unnecessary. I am more than happy to support it if you all feel this way.
Just please be patient with me, like I said in the README this lib was made as a way for me to learn and try new things, it was built with my own tastes and my needs. If all of you feel this is useful to you when you use discordeno then 100% that is how it'll be 👍

as i mentioned before there's no need to conform to the standards;
it's just confusing having a mod.ts that exports nothing.
it also helps for documentation purposes (at least, with doc.deno.land) to have a single file that exports everything, however if you had a readme (or similar) that documented everything that was exported and such and where to import them from, that would suffice too
having a mod.ts that exports everything is an opinionated stance; and since this is your module, it's your opinion that should count most. i don't want you to feel like you're forced to do this because you're not - it's just an opinion and standard to have a single file export most things in a module, (namely, a mod.ts file)

For what it's worth though, not conforming to standards creates confusion such as this here. Where everywhere else uses mod.ts for a specific purpose, that is not followed and issues created to ask what's going on and this thread now exists. Unless there's a good reason to not conform, why not just do it?

@alex-vg @fox-cat @Ryaangu Let me know if #41 is enough to help. I still feel it's a bit unnecessary. I am more than happy to support it if you all feel this way.
Just please be patient with me, like I said in the README this lib was made as a way for me to learn and try new things, it was built with my own tastes and my needs. If all of you feel this is useful to you when you use discordeno then 100% that is how it'll be 👍

Awesome, that's what I need. Thank you!

Thought id share this here: A good read on why using mod.ts or deps.ts is a bad idea and bad practice
https://dev.to/wongjiahau/why-deps-ts-and-mod-ts-is-bad-in-deno-bjo


README.md's description is copy-pasted from orbit-db-eventstore

An append-only log with traversable history. Useful for "latest N" use cases or as a message queue.

This sentence is a copy-paste from orbit-db-eventstore and doesn't describe what orbit-db-kvstore is.

You're absolutely right @onionjake! Would you want to PR a more descriptive version of the text?


:sparkles: feat: worked on improving the appearance of the page

Description
Have been working on the appearance of the image that is aligned in row form with a text and header.
Reference the issue related to this PR as shown below. Every issue has it's own number you can find the issue numbers here.
Fixes # (4) - Example: Fixes #10, #20 NOTE: GitHub issue numbers should be prefixed with # to aid with issue tracking.
issue #4
Type of change
Please delete options that are not relevant.

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

Screenshot (optional

)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration: (optional)

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist

[ =] My code follows the style guidelines of this project
[ ] I have performed a self-review of my 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
[ ] Any dependent changes have been merged and published in downstream modules

Good attempt closing this pr as it is already done, please pick another issue


Run sudo with -i/--login so profiles are loaded.

Use Case
Currently when using Bolt to run commands/scripts and specifying run-as option to elevate the privileges sudo is used. By default, sudo doesn't run a login shell causing things placed into /etc/profile.d/* to not be loaded. This causes problems for things like puppet, rvm, etc (we have other examples of similar internally).
With the current implementation we need to do things like the following on Linux:
bolt command run '/opt/puppetlabs/bin/puppet xxx' --targets xxx

On Windows the PATH is setup and global so doing the following works out of the box:
bolt command run 'puppet xxx' --targets xxx

Describe the Solution You Would Like
Login shells can be invoked with sudo by passing in the -i/--login option, most likely right here: https://github.com/puppetlabs/bolt/blob/main/lib/bolt/shell/bash.rb#L343
Describe Alternatives You've Considered
We could also customize this by doing our own run-as-command, but i think this would be useful for others.
I wanted to put this up for discussion before creating a PR in case there was some reason we didn't want to start passing in -i/--login?

Hm, this would have at least a few side effects I can think of that might not be desirable:

It would cd to the sudo users home dir for the local transport, which currently executes in the directory you ran Bolt from.
This is very edge case, but "As a special case, if sudo's -i option (initial login) is specified, sudoers will initialize the environment regardless of the value of env_reset. The DISPLAY, PATH and TERM variables remain unchanged; HOME, MAIL, SHELL, USER, and LOGNAME are set based on the target user. On AIX (and Linux systems without PAM), the contents of /etc/environment are also included. On BSD systems, if the use_loginclass flag is enabled, the path and setenv variables in /etc/login.conf are also applied. All other environment variables are removed." (source). This is less compelling, but seems hard to debug if anything goes wrong.

I'm still open to it if other folks in the community want this by default, but I'm kind of leaning towards just documenting the run-as-command case on our troubleshooting page?
Another (I think worse...) option might be to have a preserve_path config setting that would append env 'PATH=$PATH to the sudo command, to address just the pathing issue. That seems useful for solving this without the side effects and providing a way to opt-in, but I'm not too keen to add even more configuration options...

Hm, this would have at least a few side effects I can think of that might not be desirable:

It would cd to the sudo users home dir for the local transport, which currently executes in the directory you ran Bolt from.
This is very edge case, but "As a special case, if sudo's -i option (initial login) is specified, sudoers will initialize the environment regardless of the value of env_reset. The DISPLAY, PATH and TERM variables remain unchanged; HOME, MAIL, SHELL, USER, and LOGNAME are set based on the target user. On AIX (and Linux systems without PAM), the contents of /etc/environment are also included. On BSD systems, if the use_loginclass flag is enabled, the path and setenv variables in /etc/login.conf are also applied. All other environment variables are removed." (source). This is less compelling, but seems hard to debug if anything goes wrong.

I'm still open to it if other folks in the community want this by default, but I'm kind of leaning towards just documenting the run-as-command case on our troubleshooting page?
Another (I think worse...) option might be to have a preserve_path config setting that would append env 'PATH=$PATH to the sudo command, to address just the pathing issue. That seems useful for solving this without the side effects and providing a way to opt-in, but I'm not too keen to add even more configuration options...


实际可视化效果差的问题

Hello,

Thank you for your interest in our project. In fact, we have also released weights on ViT and Resnet for reproducing the results. If you want to view the visualization results, you can set args.visualize to True. What's your input instruction and test image? Maybe you can try testing your cases with the released ckpt.


Clearing DB to fix specs

Fixes specs on master, hopefully :P
Pings:
@cheerfulstoic
@subvertallchris

[Current coverage][cc-pull] is 98.12%

Merging [#1241][cc-pull] into [master][cc-base-branch] will increase coverage by 0.75%

@@             master      #1241   diff @@
==========================================
  Files           187        187
  Lines         11213      11028   -185
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          10918      10821    -97
+ Misses          295        207    -88
  Partials          0          0

Powered by Codecov. Last updated by [a02bd7a...61db20b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/neo4jrb/neo4j/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/neo4jrb/neo4j/compare/a02bd7a126929783850d892b097bf6a39ac81192...61db20b248dca0aaea765f48fe2747b8c2a7f5b9?src=pr
[cc-pull]: https://codecov.io/gh/neo4jrb/neo4j/pull/1241?src=pr

Nice!  Merge ASAP and thanks!

👍 Merged!


json-loaded data is in original

The JSON doc (https://www.jstree.com/docs/json/) says "Keep in mind you will be able to access any additional properties you specify - jsTree won't touch them and you will be able to use them later on." That's true, but those properties are not available in the node data. You have to go into the "original" hash to get them. I can't find the word "original" anywhere in the docs. Like this, modified from a demo in the docs:
        console.log(data.selected);
        var i, j, r = [];
        if (data.selected.length == 1) {
            r.push(data.instance.get_node(data.selected[0]).original.v1);
        }
        $('#tab').html('

' + r.join('

') + '

');
    });

Thank you - I updated the docs.


Changed node-sass version to 6.0.0

Hi Rise
I was facing error due to node-sass version, I was using node version 16 and previous sass version was not compatible thus changed the sass version to 6.0.0

Hi MiniViper
Will do it as your said


Fix root URL override example

Using the code from the root URL override example, the URL would get prefixed multiple times because the $baseUrl we're prefixing can already be prefixed. This PR updates $baseUrl so that it's always env('APP_URL'), and updates the formatting of the block comment.

Codecov Report

Merging #1079 (2ceef46) into master (8b7862d) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##             master    #1079   +/-   ##
=========================================
  Coverage     89.71%   89.71%
  Complexity      575      575
=========================================
  Files           138      138
  Lines          1769     1769
=========================================
  Hits           1587     1587
  Misses          182      182

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add support for knockd one-time sequence files

I've added the support to my own fork: https://github.com/pro-src/knock
Generates sequences using a CSPRNG and saves them in a knockd compatible file
Reads one-time sequences from a file

Will you accept a PR for this?

Hi, so sorry for the delay, I don't even know how I missed this - I will look into it in the following days :)


Display version number as part of --help

Displaying the version number as part of --help could help to identify issues from different versions.

cobra generate help info automatically, but there must be a way to add version info there.

Yeah, not sure how to get it in - but would be neat to have it

Oh, I think this is already included in hostctl -v|--version also on the soon to be released hostctl info with a nice banner.

Oh yes. The updated version now includes the version number.


Add missing -noprompt parameter to prevent agent hangs

Small improvement to #155, the other commands already have the -noprompt parameter.

go build


[LinearProgress][CircularProgress] Add min and max props

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

LinearProgress and CircularProgress should accept min, max and value props.
When mode is 'determinate', the progress is calculated based on value between a scale of min to max.
If min and max are not supplied, they default to 0 and 100 respectively (original behavior).
inlineStyles.primary.transform = 'scaleX(' + ((value - min) / (max - min)) + ')';
Current Behavior

LinearProgress and CircularProgress accepts value prop.
When mode is 'determinate', the progress is calculated based on value between a scale of 0 to 100.
inlineStyles.primary.transform = 'scaleX(' + value / 100 + ')';
Context

This would simplify components that utilize LinearProgress and CircularProgress as parent components would no longer be responsible for scaling values between 0 and 100. I find it's pretty rare to have data already suitable for the progress components because it's not normally between 0 and 100.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16.0.0

I'm wondering is f(x) = (x - min) / (max - min) worth an abstraction? At least, it would be great to have a demo in the documentation. But I have some concern about bloating the component for this simple function.

I think the bloat is going to need to exist either way - either the developer consuming the progress component is going to have to bloat their component with scaling logic, or the progress component itself will do it.
I think it would be quite rare for someone using this component not to have to do scaling in order to get it working. Considering that scaling is going to be required in almost every situation, I think it makes sense for the progress component to do it itself.
When I look at the value prop now, unless there is a min and max prop to go with it I think it is confusingly named. Value by itself doesn't mean much in the context of a progress bar without being able to define where that value lies in relation to the start and end of the progress.
The end of the progress is currently arbitrary, why 100? Why not 1?
It's not a deal breaker since scaling logic is simple but I think from a usability point of view this change would definitely be positive.

@rshepp Thanks for the benchmark with the other libraries!
You can add react-native into the list:

[ ] Supports min
[ ] Supports max

I have added the waiting for users upvotes tag. I'm closing the issue as I'm not sure people are looking for such abstraction. So please upvote this issue if you are. We will prioritize our effort based on the number of upvotes.


bluetooth incar phone sync disabled

SMS backup+ was great at restoring to KitKat 4.4.4 phone after ROM reflashing, but had to be uninstalled before phone would again sync via Bluetooth the 'contacts' and 'call history' to the built-in car system. It seems that SMS backup+ somehow blocks the phone from transmitting the information, but does not block the bluetooth entirely as calls can still be made through the hands free car unit...
Any ideas?

very unlikely


Adding new api version to devops RP

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. Already live as preview (documentation is pending update hence this PR)
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run automation - sdk

Already approved on private branch. Recreated PR as per recommendation from ARM team

@chiragg4u Created new PR as per your recommendation here ->
https://github.com/Azure/azure-rest-api-specs/pull/11325

@suyash691 Let us know the approved private PR. That will save a lot of time.

@weidongxu-microsoft https://github.com/Azure/azure-rest-api-specs-pr/pull/1648 This is the private PR url

@suyash691
Thanks. Let me know when you plan to get this merged.
@pilor
This should be same as approved private PR Azure/azure-rest-api-specs-pr#1648 . Let me know if we can skip ARM review in this PR.

@weidongxu-microsoft The changes in production to support this API are live so whenever @pilor and @bishal-pdMSFT confirm their approval, you can go ahead with the merge

@weidongxu-microsoft Any updates on the merge?

/azp run

@suyash691
There is still no response from ARM. Let me know the urgency or when you want it get merged. I might go ahead.

/azp run

@akning-ms Would you help merge this PR? API already online. ARM review passes.
The problem is that "SDK python" CI fails on build_package.
I've checked with Yuchao that this is not RP problem. But I cannot merge it since "SDK python" CI is required.
autorest pass
01:21:36.082 info 	13 changed files after SDK generate:
01:21:36.083 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/__init__.py
01:21:36.084 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/_configuration.py
01:21:36.085 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/_dev_ops_client.py
01:21:36.085 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/models/__init__.py
01:21:36.086 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/models/_dev_ops_client_enums.py
01:21:36.087 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/models/_models.py
01:21:36.087 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/models/_models_py3.py
01:21:36.088 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/models/_paged_models.py
01:21:36.089 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/operations/__init__.py
01:21:36.089 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/operations/_operations.py
01:21:36.090 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/operations/_pipeline_template_definitions_operations.py
01:21:36.090 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/operations/_pipelines_operations.py
01:21:36.093 info 		sdk/devops/azure-mgmt-devops/azure/mgmt/devops/version.py
01:21:36.093 git 	Commit all the changes
01:21:36.209 endsection 	Commit generate result

fail after
01:21:58.146 command 	python ./build_package.py --dest sdk/devops/azure-mgmt-devops sdk/devops/azure-mgmt-devops
01:21:58.146 info 	Config: {"exitCode":{"showInComment":true,"result":"error"},"stderr":{"showInComment":true},"logPrefix":"buildPackage"}
01:21:58.190 cmderr 	[buildPackage] Traceback (most recent call last):
01:21:58.191 cmderr 	[buildPackage]   File "./build_package.py", line 33, in <module>
01:21:58.191 cmderr 	[buildPackage]     create_package(args.name, args.dest)
01:21:58.191 cmderr 	[buildPackage]   File "./build_package.py", line 21, in create_package
01:21:58.191 cmderr 	[buildPackage]     absdirpath = os.path.abspath(absdirs[0])
01:21:58.191 cmderr 	[buildPackage] IndexError: list index out of range

Looks there is cross API version breaking change detected:
[Staging] Cross Version BreakingChange (Base on preview version): 12 Warnings warning [Detail]

@akning-ms That is just a warning because the compact is not broken in the swagger spec but we have added new patterns to allow for inheritance/polymorphism which are flagging that. I do not think that should be breaking the python build

@akning-ms The python CI still fails at the same place, after autorest.

@akning-ms @weidongxu-microsoft That is just a warning because the compact is not broken in the swagger spec but we have added new patterns to allow for inheritance/polymorphism which are being flagged as warnings. I do not think that should be breaking the python build

Hi @suyash691, what I meant here is about API breaking change. Not python sdk build
compare with original: preview/2019-07-01-preview/devops.json <---> new: preview/2020-07-13-preview/devops.json
e.g repository rename to sourceRepository.
For python sdk build fail. @PhoenixHe-msft  to help take a look

@msyyc Please help to investigate the python build failure

@msyyc Yuchao Yan FTE Please help to investigate the python build failure

got it

/azp run

@weidongxu-microsoft @PhoenixHe-msft I added system data in the latest commit but still it is unable to detect system data in the response

@suyash691
I've added Jeffrey for guidance on cross api-version change.
For system data, I think it need to be directly under Pipeline model, not its properties property. E.g. https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-contracts.md#system-metadata-for-all-azure-resources

@suyash691
I've added Jeffrey for guidance on cross api-version change.
For system data, I think it need to be directly under Pipeline model, not its properties property. E.g. https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-contracts.md#system-metadata-for-all-azure-resources
Fixed the systemData related error
@weidongxu-microsoft  It seems that this time python CI didn't fail. Maybe the CI was has been patched to ignore cross version breaking changes (as it should) or does applying the "breakingchange" tag in the repo cause it to not run completely?

@suyash691
python CI build fail weeks ago is actually a bug on Swagger team. It is not your fault at all (that was why I pinged Arthur and Phoenix to merge/fix). I figure Swagger team fixed it last week.
The cross api-version validation is not very reliable, hence is reports as warning but not blocks the PR. We just being cautious on any removal of API/parameter/property. Since Jeffrey approved it you are OK to go.
Let me know when you need it merged.

You can merge it today, we are ready with the changes on our RP


TypeError: P.PHOTO_PICKER_QUALIFIED_EMOJIS is not iterable

Description
I imported wa.js in my Chrome extension. When a user clicks on the three-dot button in the top right corner of a group chat in web.whatsapp.com, the group info does not show up and an error is reported in the console. The error is as follows:
TypeError: P.PHOTO_PICKER_QUALIFIED_EMOJIS is not iterable
at t.default (lazy_loaded_low_priority_components.2eb74f3a79d43c7a730d.js:2:295311)
at wa (vendor1~app.93f2846fd0de96e2ec08.js:30:62964)
at _u (vendor1~app.93f2846fd0de96e2ec08.js:30:120158)
at vl (vendor1~app.93f2846fd0de96e2ec08.js:30:109100)
at pl (vendor1~app.93f2846fd0de96e2ec08.js:30:109028)
at hl (vendor1~app.93f2846fd0de96e2ec08.js:30:108891)
at nl (vendor1~app.93f2846fd0de96e2ec08.js:30:105698)
at ol (vendor1~app.93f2846fd0de96e2ec08.js:30:106087)
at Fi (vendor1~app.93f2846fd0de96e2ec08.js:30:46805)
at vendor1~app.93f2846fd0de96e2ec08.js:30:103606

Environment

**WA-JS version(s): 2.23.3
Browser: Chrome 111
OS: Windows X / OSX

Steps to Reproduce

Inject wppconnect-wa.js.
Click on a specific group on web.whatsapp.com.
Click on the More (three-dot) icon at the top right corner and select the first group info option.
An error is reported in the console.

Add any other context about the problem here. If applicable, add screenshots to help explain.

Please take a look for me, and thank you very much!

@yuzedong what is the WhatsApp version?

2.2316.6

I fixed it by injecting the js later, after authentication is ok.

Thanks @luiscuriel , I will try to reproduce it on my machine and try to figure out a way to avoid this

Thanks @luiscuriel , I will try to reproduce it on my machine and try to figure out a way to avoid this

When can this issue be fixed? tks.

It is still happening on some sessions for me...

Ok, Please fix it as soon as possible. Thanks!

I'm using the latest version 2.24.0, and the process remains the same as before. The previous console error has disappeared, but a new error has occurred. The error is as follows:


Build fails on latest material-dialogs:core:2.0.0-alpha03

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I understand that versions below 2.0.0 will no longer be supported for updates.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Material Dialogs version: 2.0.0-alpha03

Suspected Cause
appcompat-v7-28.0.0-rc01.aar in dependency is in alpha state and unstable.
Steps to Reproduce

On adding dependency:

dependencies {
implementation 'com.afollestad.material-dialogs:core:2.0.0-alpha03'
}
and repository:
maven { url "https://dl.bintray.com/drummer-aidan/maven/" }
Expected Result
Build Successful
Actual Result
Error:
AGPBI: {"kind":"error","text":"error: resource android:attr/dialogCornerRadius not found.","sources":[{"file":"C:\Users\abhiu\.gradle\caches\transforms-1\files-1.1\appcompat-v7-28.0.0-rc01.aar\a5a558333efe70a20c96b20a0f0decfc\res\values-v28\values-v28.xml","position":{"startLine":8,"startColumn":4,"startOffset":447,"endLine":11,"endColumn":12,"endOffset":684}}],"original":"","tool":"AAPT"}
AGPBI: {"kind":"error","text":"error: resource android:attr/dialogCornerRadius not found.","sources":[{"file":"C:\Users\abhiu\app\build\intermediates\incremental\mergeXenonDebugResources\merged.dir\values-v28\values-v28.xml","position":{"startLine":10}}],"original":"","tool":"AAPT"}
AGPBI: {"kind":"error","text":"error: resource android:attr/fontVariationSettings not found.","sources":[{"file":"C:\Users\abhiu\.gradle\caches\transforms-1\files-1.1\appcompat-v7-28.0.0-rc01.aar\a5a558333efe70a20c96b20a0f0decfc\res\values\values.xml","position":{"startLine":1303,"startColumn":4,"startOffset":70911,"endColumn":68,"endOffset":70975}}],"original":"","tool":"AAPT"}
AGPBI: {"kind":"error","text":"error: resource android:attr/ttcIndex not found.","sources":[{"file":"C:\Users\abhiu\.gradle\caches\transforms-1\files-1.1\appcompat-v7-28.0.0-rc01.aar\a5a558333efe70a20c96b20a0f0decfc\res\values\values.xml","position":{"startLine":1303,"startColumn":4,"startOffset":70911,"endColumn":68,"endOffset":70975}}],"original":"","tool":"AAPT"}

Just found this: https://stackoverflow.com/questions/48027019/how-to-manage-different-support-library-versions-for-3rd-party-deps-with-gradle
Issue:
appcompat-v7-28.0.0-rc01 is not compatible with my current target SDK 27.
Workaround:
put this in your Top-Level Gradle file:
ext {
supportlib_version = '27.1.1'
}
subprojects {
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex')) {
details.useVersion "$supportlib_version"
}
}
}
}

28.0.0-rc01 is a release candidate, yes. Material Dialogs 2.0 is also in alpha, which also isn't "stable".


Tko bug fixes november

PressKey: Support for "global hotkeys" by giving ${EMPTY} as locator
Bumped selenium version to 4.6.0 and Pillow to 9.3.0
Added offset arguments for locator in DragDrop keyword
Minor fix to checkboxes in salesforce

Closed. Changes will be included in Mikko's PR with typing fixes


Proof of concept of "buffer_description_api" and xarray reference API bridge

Given the idea of @bendichter and this gist
Here a very very early stage of a very very proof of concept of the "buffer_description_api" for analogsignal chunk.
The idea/goal is:

have a simple buffer description for analogsignal for binary or hdf5 cases (maybe more)
this description can be exported to json
this description can be easily transformed to the xarray/zarr reference external API
make so file cloud ready for streaming chunk of traces

See also kerchunk

Looks good!

Merci beaucoup @zm711  and @h-mayorquin for the review

@zm711 @h-mayorquin @alejoe91
This is OK on my side.
test are passing I think we can merge this soon.
we will be able to update stream and buffer on reader per reader basis later.

yeah!!
merci fois pour l'aide.


Support reusable slices

For hyper memory optimization, support a slice declaring itself as reusable so the slice factory can reuse instances rather than creating new ones each time.  The slice would return itself to the pool after it renders each time (slices are considered "dead" after rendering today).
This is a bit scary, but for some scenarios might be advantageous.

There's an initial spike implementation of this in https://github.com/DamianEdwards/RazorSlices/tree/ReusableSlices
To use, simply add @implements IRazorReusableSlice to the top of your slice .cshtml file. You can optionally implement the bool TryReset() method if your slice has instance-level state it needs to clear before reuse.
Some initial results from adding support for this:
This image of the Visual Studio profiler (.NET Object Allocation Tracking) shows that (after warmup) the only thing allocated when rendering a reusable slice to a string 1000 times is the final string itself:

Here's benchmark results comparing rendering the same template via a regular slice vs. a reusable slice:

Method
Mean
Error
StdDev
Ratio
Gen0
Allocated
Alloc Ratio

RazorSlicesHello
195.2 us
1.44 us
1.27 us
1.00
26.1230
484.38 KB
1.00

RazorSlicesReusableHello
177.4 us
0.74 us
0.69 us
0.91
16.1133
296.88 KB
0.61


WRITE_CONTACTS always denied on emulator/Samsung GS7

    @AfterPermissionGranted(PERMISSIONS_REQUEST_WRITE_CONTACTS)
    public void writeContact(String id) {
        String[] perms = { Manifest.permission.WRITE_CONTACTS, Manifest.permission.READ_CONTACTS};
        if (EasyPermissions.hasPermissions(this, perms)) {
            // Have permissions, do the thing!
            writeContact1(id);
        } else {
            // Ask for both permissions
            EasyPermissions.requestPermissions(this, getString(R.string.requestwriteperm),
                    PERMISSIONS_REQUEST_WRITE_CONTACTS, perms);
        }
    }

I want to insert a new contact but permission to write contact is always denied whereas read contacts works as supposed. The permission is denied even if I use "Ask for one permission" method. Another issue is R.string.requestwriteperm is never shown.

@Takha25 I would suggest asking this question on StackOverflow, you have not provided enough information here to do any debugging and it sounds like this may be device-specific.  EasyPermissions uses the same behavior for each permission,

Closing due to lack of activity.


Fix: Allow multiple IDynamicMessageProcessor instances to be registered

Quality checklist

[x] Your code complies with our Coding Style.
[ ] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

@bart-vmware Can you add some more context here - are you doing this to match the dependency retreival side. I realize it supports multiple processors but we never use it, but not clear whether this is needed or not. If Do we need to add a test for any breaking functionality?

This change was suggested by @TimHess. The consuming code injects IEnumerable<IDynamicMessageProcessor> and iterates over them when building the log message. This change allows Steeltoe consumers to add additional message processors, which we assumed to be the intended behavior.


Path and various fixes

Summary

It's easier for me to create a single PR so I can batch up a lot of these fixes since they're fairly simple and I have limited time to work on this stuff (during the week since I limit myself to the evenings).
Some of these fixes are cross-functional. I'll probably cut a release after I have a bunch of issues fixed.
Test Plan

Added tests where possible.

@sebmck let me know of you end up using the changelog script to also generate a change log with the next release. Happy to iron out any issues that may come up.

@bitpshr Sweet, I will! I'm not familiar though with how commits should be structured, which is something I'm happy to adapt to. Could you add something to CONTRIBUTING.md?
All we should need to do, is ensure that the commit messages on the squashed commit when merging PRs is correct, right? Does the changelog script support multiple messages?

@sebmck I added something in my PR https://github.com/romefrontend/rome/pull/1011

@sebmck the changelog script is pretty basic right now; it can only be run on the main branch and works off that commit history, so it side-steps having to deal with squashing or anything branch or PR-related since the main commit history should already be in the state we want. It also isn't a big deal if past or future commits are malformed since the script is fairly resilient: poorly-formatted (e.g. unclassifiable) commits are still added to the change log in a "Misc." section, and the script always generates a totally-fresh change log each run, so nothing should ever get lost.


Fix bug in znotify

Sibi found a bug where the znotify program will sometimes fail with errors when given the -t argument. Still investigating the root cause.

Reproduced on a fresh vagrant vm
$ sudo c_fs_monitor/znotify -tea /proc/2597/root /proc/2774/root
Error Occured Adding to Watch List: /proc/2597/root/usr/lib/x86_64-linux-gnu/libusb-0.1.so.4 No such file or directory


[reggen] Expose reset values to SW

@silvestrst: Is this the sort of thing you were imagining for #1977?
(Assuming so...), closes #1977.

@silvestrst: Ping!

@rswarbrick

@silvestrst: Ping!

My bad, I have answered in the corresponding issue:
https://github.com/lowRISC/opentitan/issues/1977#issuecomment-862481093
But forgoy to drop a comment herer


Update redux-form to 7.1.X

Hello,
We have some warnings on api-platform/admin due to redux-form.
Update redux-form to (at least) 7.1.0 resolves the problem (I used 7.1.1 because 7.1.0 had a problem with immutablejs).
According to your version policy, I kept tilde for version range.

I'm not sure we'll merge this, as we're limiting updates on the master branch.

I understand you want to be focus on next branch. But the warnings are very noisy: on Travis we have more "warning" lines than "legit" lines. Your project also has the problem but it is printed only once
We have only two possibilities:

run Jest with --silent flag.
force npm / yarn to retrieve a fixed version.

Unfortunately, these solutions are not acceptable.
This fix will give some time for all project that depending of admin-on-rest (like our project) to prepare the update to next version.
By the way, the problem is also present on next. If you wish, I can make another PR for next branch.

Thanks

Thank you for merging!


Scale and ScaleX are not valid on windows10.

Robotgo version (or commit ref): <IP_ADDRESS>8
Go version: 1.10.x
Gcc version: x.x
Operating system and bit: windows 10
Can you reproduce the bug at Examples:

[x] Yes (provide example code)
[ ] No
[ ] Not relevant

Provide example code:

Log gist:

Description
Set the zoom ratio to 125%, Scale and ScaleX get "dpi = 96" on windows10.

you can try add syscall.NewLazyDLL("user32.dll").NewProc("SetProcessDPIAware").Call() before Scale() and ScaleX().
it works on my project.

and win10 default DPI scaling level add 175%(168) and 225%(216), you can try use ScaleX() / 0.96 replace DPI map to support all DPI setting.

I added 175% and 225% to dpi-map. I will consider whether to implement this method on other system platforms, and refer to its display scale.


[Feature Request] Confirm PyThreadState_SetAsyncExc is ok on non-GIL threads

Describe the solution you'd like
Saw issue with Ruby, just want to confirm if we cancel a sync activity that is running non-GIL code that it's ok

Appears good enough in practice so far, not easy enough to add test cases for


Remove PCI app article

Purpose of this pull request
This pull request (PR) removes this article:
https://help.sumologic.com/docs/integrations/pci-compliance/setup/
Issue number: GitHub issue #3006

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Hey @kimsauce, this got put into the merge queue without any approvals! Do you know why?

@kimsauce, could you review this one when you get a chance?

Thanks, @kimsauce!


add pandas documentation

Copy pandas documentation files (#12)

@datapythonista. Got it, I am closing this one and creating the updated PR with the correct file structure.

this seems to have the correct file structure now


(Mostly for BSO) Add a toggle to clue buttons

🚀 Feature Proposal
This is mostly a BSO issue due to stackable clues but can be applied to OSB too.
When you get a clue in a trip, Patrons can click a button to complete it. However, it is easy to misclick and accidentally send a Grandmaster clue trip - which is annoying because players tend to save them for clue sessions w/ proper boosts equipped or to sell. A toggle would be a lifesaver for this and would only benefit the players in a convenient way

Would you prefer the toggle to be per tier? Or to stop all clue buttons showing?

This has been added with /config user toggle name:Disable Clue Buttons


[1.6] java.nio.file.InvalidPathException: Illegal char <:> at index 4: file:///D:/sbt16/ on Windows

steps
use windows
create play v2.8 project eg using sbt new playframework/play-scala-seed.g8
set sbt version to 1.6 eg using printf sbt.version=1.6.0-M1> project\build.properties
problem
assets task fails with [error] (Web-assets / assets) java.nio.file.InvalidPathException: Illegal char <:> at index 4: file:///D:/sbt16/play-scala-seed/public/javascripts/main.js
notes
sbt 1.5.8 works fine

@OlegYch Thanks for the report. Do you have a stacktrace on this? (last may display this)
This sound related to previous issues with Windows + Scalac returning fake positions:

https://github.com/sbt/sbt/issues/6720
https://github.com/sbt/sbt/issues/5994

@eed3si9n
[error] java.nio.file.InvalidPathException: Illegal char <:> at index 4: file:///D:/sbt16/play-scala-seed/public/javascripts/main.js
[error]         at sun.nio.fs.WindowsPathParser.normalize(Unknown Source)
[error]         at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
[error]         at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
[error]         at sun.nio.fs.WindowsPath.parse(Unknown Source)
[error]         at sun.nio.fs.WindowsFileSystem.getPath(Unknown Source)
[error]         at java.nio.file.Paths.get(Unknown Source)
[error]         at sbt.internal.inc.MappedVirtualFile$.toPath(MappedVirtualFile.scala:36)
[error]         at sbt.internal.inc.MappedFileConverter.toPath(MappedVirtualFile.scala:53)
[error]         at sbt.Sync$.$anonfun$convertFromVirtual$1(Sync.scala:175)
[error]         at sbt.internal.util.Relation$.$anonfun$switch$1(Relation.scala:58)
[error]         at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:286)
[error]         at scala.collection.immutable.HashMap$HashMap1.foreach(HashMap.scala:400)
[error]         at scala.collection.immutable.HashMap$HashTrieMap.foreach(HashMap.scala:728)
[error]         at scala.collection.TraversableLike.map(TraversableLike.scala:286)
[error]         at scala.collection.TraversableLike.map$(TraversableLike.scala:279)
[error]         at scala.collection.AbstractTraversable.map(Traversable.scala:108)
[error]         at sbt.internal.util.Relation$.switch(Relation.scala:56)
[error]         at sbt.Sync$.convertFromVirtual(Sync.scala:175)
[error]         at sbt.Sync$.readInfoWrapped(Sync.scala:168)
[error]         at sbt.Sync$.$anonfun$sync$1(Sync.scala:67)
[error]         at com.typesafe.sbt.web.SbtWeb$.syncMappings(SbtWeb.scala:537)
[error]         at com.typesafe.sbt.web.SbtWeb$.$anonfun$unscopedAssetSettings$40(SbtWeb.scala:293)
[error]         at scala.Function1.$anonfun$compose$1(Function1.scala:49)
[error]         at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:62)
[error]         at sbt.std.Transform$$anon$4.work(Transform.scala:68)
[error]         at sbt.Execute.$anonfun$submit$2(Execute.scala:282)
[error]         at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:23)
[error]         at sbt.Execute.work(Execute.scala:291)
[error]         at sbt.Execute.$anonfun$submit$1(Execute.scala:282)
[error]         at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:265)
[error]         at sbt.CompletionService$$anon$2.call(CompletionService.scala:64)
[error]         at java.util.concurrent.FutureTask.run(Unknown Source)
[error]         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
[error]         at java.util.concurrent.FutureTask.run(Unknown Source)
[error]         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[error]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[error]         at java.lang.Thread.run(Unknown Source)

Another report here: https://github.com/playframework/playframework/issues/11087

@OlegYch @eed3si9n @mkurz
Hi, I've tried reproducing this, but I can't get it to break using the steps described in this issue. If you have ideas of anything else I can try, please let me know. Thank you

looks like caches produced by sbt.Sync 1.5 were storing info in format incompatible with 1.6
the error is gone after clean

I have a project that uses a submodule, and sbt clean did not clean things out sufficiently to recover.
I had to manually go in and delete /target, /project/target, and /submodule/target to get it to work.
Perhaps we could add versioning information to sensitive files so that sbt can detect that it needs to rewrite them?


Split CPU and GPU packages into separate requirements files

Split CPU and GPU packages into separate requirements files

/retest


Additional Info for Wiki - Setting TLS to version 1.2 via PowerShell on Windows Server 2016

Overview
Great work on this provider! Just wanted to make a note of something I've seen in case it helps others. I wouldn't call it bug though.  After initial installation I get an SSL/TLS error when searching for github repositories using this provider. Setting my TLS version to 1.2 in PowerShell solved this.
Details
Installed provider using steps from README:
Install-PackageProvider GitHubProvider`
Import-PackageProvider GitHub

Initially, when searching for GitHub repositories I get this error:
Find-Package -ProviderName GitHub -Source "Microsoft"
WARNING: The request was aborted: Could not create SSL/TLS secure channel.

This would happen on any source I searched on. I've seen this error in the past when connecting to endpoint like DSC pull servers and the solution was the same.
I checked the security protocols being used via this command and verified the it was allowing SSL:
[Net.ServicePointManager]::SecurityProtocol
Ssl3, Tls

I then changed it to only allow TLS 1.2:
[Net.ServicePointManager]::SecurityProtocol = [Net.Securityprotocoltype]::Tls12

Now it works:
Find-Package -ProviderName GitHub -Source "Microsoft"

Name                           Version          Source           Summary
----                           -------          ------           -------
2LCS                           1.0              GitHub/Microsoft Lifecycle Services Companion App for administrators
3-in-1-dock                    1.0              GitHub/Microsoft
AADConnectConfigDocumenter     1.0              GitHub/Microsoft AAD Connect configuration
etc...

It's possible this won't affect every system as newer Windows 10 builds may have this enabled by default. The system I was running  on was Windows Server 2016, Datacenter Server Edition, Build 10.0.14393 AND in a docker container.
Would be interested to see if this shows up on other operating systems.

Thanks!