[Snyk] Security upgrade nginx from 1.21 to 1.25.3

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

web-server/Dockerfile

We recommend upgrading to nginx:1.25.3, as this image has only 74 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

721
Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
Proof of Concept

721
Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
Proof of Concept

829
Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
Mature

733
Resource Exhaustion SNYK-DEBIAN11-NGHTTP2-5953384
Mature

714
OS Command Injection SNYK-DEBIAN11-OPENSSL-2933518
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Resource Exhaustion

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Patch HTTP method as option in Logger.log_request_info type sig

Reason for this PR
Adds support for PATCH requests to be passed to the Logger#log_request_info method
What this PR does

Updates the Sorbet type signature for the request parameter of the Logger#log_request_info method to allow Net::HTTP::Patch objects to be passed in.

Codecov Report

Merging #237 (468c05b) into dev (e4e4f79) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev     #237   +/-   ##
=======================================
  Coverage   97.69%   97.69%
=======================================
  Files          70       70
  Lines        1388     1388
=======================================
  Hits         1356     1356
  Misses         32       32

Impacted Files
Coverage Δ

lib/vonage/logger.rb
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.

Is this an optional parameter? Or is it a breaking change?

Not an optional param or a breaking change. Basically updating the type signature to allow Net::HTTP::Patch objects to be passed into the method invocation. Prior to this change you could only pass in Net::HTTP::Post, Net::HTTP::Get, Net::HTTP::Delete, or Net::HTTP::Put objects.

Is this an optional parameter? Or is it a breaking change?

Not an optional param or a breaking change. Basically updating the type signature to allow Net::HTTP::Patch objects to be passed into the method invocation. Prior to this change you could only pass in Net::HTTP::Post, Net::HTTP::Get, Net::HTTP::Delete, or Net::HTTP::Put objects.

Ohh I think I get it. You're saying the restrictions on types. I forget Ruby isn't strongly typed so you have to do this using some alternative way that I'm not familiar with (is it a comment? Annotation? Is it enforced by the compiler?)

Is this an optional parameter? Or is it a breaking change?

Not an optional param or a breaking change. Basically updating the type signature to allow Net::HTTP::Patch objects to be passed into the method invocation. Prior to this change you could only pass in Net::HTTP::Post, Net::HTTP::Get, Net::HTTP::Delete, or Net::HTTP::Put objects.

Ohh I think I get it. You're saying the restrictions on types. I forget Ruby isn't strongly typed so you have to do this using some alternative way that I'm not familiar with (is it a comment? Annotation? Is it enforced by the compiler?)

It's a typing library called Sorbet. It basically lets you add type annotations to method definitions. The block ({...}) following the sig invocation (just above the method definition) defines the type signature for that method. The params part defines the parameters and their types -- here there is one param (request) and the  use of T.any defines a union type (a type made up of other types), essentially here it is saying that the type of object passed in as request can be any one of those types passed to T.any. The .void bit at the end I guess is kind of the same as it would be in Java; it's basically saying here that the method has no useful return (i.e. we're not going to use the return value for anything, so we don't really care what it is). I say kind of, because the method still has a return value, we're just not concerned with it at the type level (in Ruby, all methods have a return value, even if it's implicit).


Prefix commands with plugin name suffix with action

I'm finding original commands names not very friendly for autocompleation user like me. Prefixing command with common name and suffixing with action is more autocompleation friendly.

In this PR 4 commands are added. TwoSlasheshQueries[Disable|Enable|Inspect|Remove]. To not introduce any breaking changes, original commands ([Disable|Enable|Inspect|Remove]TwoSlasheshQueries) are still accessible as a fallback.

@undg thank you for your contribution. I appreciate it very much 😊. I think your PR definitely makes sense. The commands you propose are more intuitive. I noticed that we have a problem with formatting the code, as there is no stylua configured yet. I would ask you to reset lua/twoslash-queries/init.lua because it looks like you haven't changed anything in it.

@marilari88 quick response, thats cool!

I would ask you to reset lua/twoslash-queries/init.lua because it looks like you haven't changed anything in it.

Yes, you are right. It should not be part of the same PR - reverted.
BTW I've updated README.md with new commands. I wasnt touching screencast thought.


meta: Miscellaneous clean-up of root repo directory

This commit makes a few changes:

Repo documentation (e.g. CODE_OF_CONDUCT.md and CONTRIBUTING.md) are moved to the .github/ directory to provide a consistent place to find repo-specific documentation and policies.
Add a file extension to the LICENSE file so some editors render it as a plaintext file.
Update .gitignore to include Windows, macOS, and Linux operating systems as well as popular text editors to avoid unrelated cruft sneaking into Pull Requests or other changes.

These changes are non-controversial, simple changes that clean up the root directory, and I think makes it easier to find more relevant information. This may lead to subsequent changes but I will drive this through discussion in a meeting or an issue.

Thanks @jwflory! :tada:

Thanks! I'm going to follow this up with another PR to move the archived meeting minutes from Google Drive into GitHub.


feat(compile): add customElement to options

This PR aims to add possibility to compile custom elements.

Yes please, I was just trying to achieve same :)

traction seems a little slow here :(

Thanks, and apologies for the slow response — this is released as 1.5.0.


Image storing in original but not new image

When uploading an image to s3 the image is copied to the /original/ folder but the new image is not written.  I get an accessed denied. Below is the log report and the permissions for the IAM. Do I need to set something on the bucket itself?
2019-02-14T14:08:22.903Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Parsing S3 event...
2019-02-14T14:08:22.926Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Downloading: example.jpg
2019-02-14T14:08:23.109Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Backing up to: ./original
2019-02-14T14:08:23.110Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Uploading to: original/example.jpg (121569 bytes)
2019-02-14T14:08:23.204Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Reducing to: ./
2019-02-14T14:08:23.525Z d2bfd419-6eb6-4580-9094-ad1fc36387e7 Uploading to: reduced-example.jpg (151811 bytes)
2019-02-14T14:08:23.577Z d2bfd419-6eb6-4580-9094-ad1fc36387e7
{
    "errorMessage": "Error processing example.jpg: AccessDenied: Access Denied"
}
END RequestId: d2bfd419-6eb6-4580-9094-ad1fc36387e7

Here are the permissions - changed some references to generic to not give out sensitive data
Function policy
{
  "Version": "2012-10-17",
  "Id": "default",
  "Statement": [
    {
      "Sid": "bucket_name-access-XXXXXX",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-east-1:XXXXXX:function:name",
      "Condition": {
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::bucket_name"
        }
      }
    },
    {
      "Sid": "bucket_name-access-XXXXXXX",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-east-1:XXXXXXXXXXXX:function:name",
      "Condition": {
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::bucket_name"
        }
      }
    },
    {
      "Sid": "bucket_name-access-XXXXXXXXX",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-east-1:XXXXXX:function:name",
      "Condition": {
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::bucket_name"
        }
      }
    },
    {
      "Sid": "bucket_name-access-XXXXXXXXXX",
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "lambda:InvokeFunction",
      "Resource": "arn:aws:lambda:us-east-1:XXXXXXXXXX:function:name",
      "Condition": {
        "ArnLike": {
          "AWS:SourceArn": "arn:aws:s3:::bucket_name"
        }
      }
    }
  ]
}

Execution role
{
  "roleName": "name",
  "policies": [
    {
      "document": {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
              "lambda:CreateFunction",
              "s3:GetObjectVersionTagging",
              "lambda:UpdateFunctionConfiguration",
              "s3:PutObjectVersionTagging",
              "lambda:GetFunctionConfiguration",
              "lambda:UpdateAlias",
              "lambda:UpdateFunctionCode",
              "s3:PutObject",
              "s3:GetObjectAcl",
              "s3:GetObject",
              "lambda:AddPermission",
              "s3:PutObjectVersionAcl",
              "s3:GetObjectVersionAcl",
              "s3:GetObjectTagging",
              "s3:PutObjectTagging",
              "s3:GetObjectVersionForReplication",
              "s3:PutObjectAcl",
              "s3:GetObjectVersion",
              "lambda:CreateAlias"
            ],
            "Resource": [
              "arn:aws:lambda:us-east-1:XXXXXXXXXXX:function:name",
              "arn:aws:s3:::bucket_name/*"
            ]
          }
        ]
      },
      "name": "name",
      "id": "XXXXXXXXXXXXXXXXXXX",
      "type": "managed",
      "arn": "arn:aws:iam::XXXXXXXXXX:policy/name"
    },
    {
      "document": {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Effect": "Allow",
            "Action": [
              "logs:CreateLogGroup",
              "logs:CreateLogStream",
              "logs:PutLogEvents"
            ],
            "Resource": "*"
          }
        ]
      },
      "name": "AWSLambdaBasicExecutionRole",
      "id": "XXXXXXXXXXXXXXX",
      "type": "managed",
      "arn": "arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole"
    }
  ],
  "trustedEntities": [
    "lambda.amazonaws.com"
  ]
}

Thanks in advance

So I tried to change around bucket policies and did manage to get the new processed image to write into the S3 bucket by changing the Public Access Setting of "Block new public ACLs and uploading public objects" to False.
Obviously this is not ideal so want to change the IAM role/user/function (not even sure which one) to the equivalent.
Any help would be much appreciated.

After on and off testing for about 2 weeks, finally found the issue. The acl was set to 'public-read' and this what was blocking the image from being written in the s3 bucket. Changed the acl to 'private' and it is now uploading the new reduced image. Interestingly, I did read about this issue and added 's3:PutObjectAcl' to the role and still it did not help. This is what I am now trying to understand.
Here is the thread that broke that lead to this discovery.

Thank you @Lunteer for your research. Could you update the readme with this information. I just spent a few hours doing the same thing..


Can't use the action on macos-12 executor

The new macos-12 executor is available as public beta for Github Actions. I'm experiencing issues setting up miniconda with this action.
Even though I didn't test it in an isolated environment, I believe this can be reproduced with the following workflow:
jobs:
  conda:
    runs-on: macos-12
    steps:
      - name: "Setup miniconda"
        uses: conda-incubator/setup-miniconda@v2
        with:
          auto-update-conda: true
          python-version: '3.7'
          auto-activate-base: true
          allow-softlinks: true

Log:
Run conda-incubator/setup-miniconda@v2
  with:
    auto-update-conda: true
    python-version: 3.7
    auto-activate-base: true
    allow-softlinks: true
    activate-environment: test
    remove-profiles: true
    architecture: x64
    clean-patched-environment-file: true
  env:
    PYTEST_ADDOPTS: --showlocals -vv --durations=10
    PY_COLORS: 1
    TOX_PARALLEL_NO_SPINNER: 1
    DOTNET_ROOT: /Users/runner/.dotnet
Gathering Inputs...
Creating bootstrap condarc file in /Users/runner/.condarc...
Ensuring installer...
  Can we use bundled Miniconda?
  ... will use bundled Miniconda.
Error: No installed conda 'base' enviroment found at

Hi @ljmf00 thanks for reporting the issue.

I'm experiencing issues setting up miniconda with

What seems to be the issue specifically?  Could you point us to the failing run?
Cheers!

The macos-12 runners do not provide a bundled conda
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md
vs
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md
You could overcome this issue by specifying a miniconda-version or a miniforge version so that the action installs a new one instead of trying to find an inexistent one.

Submitted this issue https://github.com/actions/virtual-environments/issues/5623

The macos-12 runners do not provide a bundled conda
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md vs https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md
You could overcome this issue by specifying a miniconda-version or a miniforge version so that the action installs a new one instead of trying to find an inexistent one.

Ah ok, makes sense to me. I'll try and give some feedback here, if worth it :blush: . Feel free to close this if you don't track the upstream issue.

@ljmf00 it seems the new machines have been updated, so everything should be working fine. Rerunning the test PR I opened to check.
If everything runs we can close this :)

Ok everything is working now as expected. Thanks a lot for flagging this @ljmf00


Add DAVID GROUP as a member

DAVID GROUP initial profile for PKI Consortium member request.
Thanks <3

Do you have an SVG logo that can be added?

Yes, transparent file logo can be accessed via this link https://davidgroup.co.id/davidgroup-logo.svg


commit: 5dfded3 "More pep8 fixes"  broke 'utils.py'

Hello,
I dont't understand completely why, but the function:
def contains_parent_dir(fpath, dirs)
from pygccxml/utils/utils.py
raise the following exception after the mentioned commit.
INFO GCCXML version - 0.9( 1.135 )
Traceback (most recent call last):
File "/home/carsten/src/bert/trunk/python/generate_pybert_code.py", line 297, in
generate(defined_symbols, options.extraIncludes, options.gimliBuild)
File "/home/carsten/src/bert/trunk/python/generate_pybert_code.py", line 181, in generate
, indexing_suite_version = 2)
File "/home/carsten/src/gimli/thirdParty/dist-GNU-4.8.3-64/pyplusplus/module_builder/boost_python_builder.py", line 95, in init
, indexing_suite_version)
File "/home/carsten/src/gimli/thirdParty/dist-GNU-4.8.3-64/pyplusplus/module_builder/boost_python_builder.py", line 153, in __parse_declarations
self.__apply_decls_defaults(decls)
File "/home/carsten/src/gimli/thirdParty/dist-GNU-4.8.3-64/pyplusplus/module_builder/boost_python_builder.py", line 177, in __apply_decls_defaults
self.__filter_by_location( flatten_decls )
File "/home/carsten/src/gimli/thirdParty/dist-GNU-4.8.3-64/pyplusplus/module_builder/boost_python_builder.py", line 163, in __filter_by_location
if pygccxml_utils.contains_parent_dir( fpath, self.__parsed_dirs ):
File "/home/carsten/src/gimli/thirdParty/dist-GNU-4.8.3-64/pygccxml/utils/utils.py", line 118, in contains_parent_dir
return bool(list(filter(fpath.startswith(dirs), dirs)))
TypeError: startswith first arg must be str, unicode, or tuple, not list
With the old version everything works perfectly.
There seems to be some more problems folllowing up and broke my toolchain with the current branch .. i will investigate and send it.
Bests and thanks for maintaining this great software,
Carsten

Hi. Thanks for reporting.
I'll have a look this week. This method is not checked by any test, so that's why I did not see any error while running the test suite. I'll see if I can write a test and fix the problem.

Hi again. I fixed the contains_parent_dir function in 24c2544378533de1d23a8011fffa8e71d0c9d750 .
I also added a test so that it won't break in the future.
Just a question, why are you needing this function ? It was previously used internally by pygccxml, but as of today it is not used anywhere. I am asking this because I don't know if I want to keep this function around or deprecate it (less code to maintain on my side). It depends of course on the functions utility and usage.

Quoting Michka Popoff<EMAIL_ADDRESS>
Hi again. I fixed the contains_parent_dir function in
24c2544378533de1d23a8011fffa8e71d0c9d750 .
I also added a test so that it won't break in the future.
Just a question, why are you needing this function ? It was
previously used internally by pygccxml, but as of today it is not
used anywhere. I am asking this because I don't know if I want to
keep this function around or deprecate it (less code to maintain on
my side). It depends of course on the functions utility and usage.

Reply to this email directly or view it on GitHub:
https://github.com/gccxml/pygccxml/issues/21#issuecomment-78157919

Hi again ..
I'm running pyplusplus for the automatic generation of the python
bindungs for my c++ project.
Pyplusplus is calling this method .. and a lot more I guess. I hope
removing spurious unused stuff will not break pyplusplus.
But of course I can help testing. Beside mine .. I know another big
project using both pygccxml and pyplusplus.
Bests,
Carsten

Okay at least I know I need to be careful when removing stuff, especially for pyplusplus. I'll leave the function in there then. Thanks.


Rename RGB vision streams to match YUV streams

I am going to take a look at issue https://github.com/commaai/openpilot/issues/23916 and noticed the confusion in the names.
Renaming VISION_STREAM_RGB_.. to match yuv names like VISION_STREAM_ROAD
The yuv stream names were changed after pr https://github.com/commaai/openpilot/pull/23071
VISION_STREAM_RGB_BACK -> VISION_STREAM_RGB_ROAD
VISION_STREAM_RGB_FRONT -> VISION_STREAM_RGB_DRIVER
Refactor also done in Cereal. Includes Cereal bump.

Great first step for #23916 :)
Can you open the matching cereal PR?

Nice first PR! Looking forward to the CARLA PR!

I had no experience in submodules pr's before. Thanks for merging the one in cereal

Hi @adeebshihadeh,  does this PR breaks the openpilot's integration with CARLA?


Undo version bump, use superset fields

The commits 4c6926204a87...6a364840ba05 introduce visual changes on linux. :mag_right: 2 changed

Changed: unlock_folders-Success (before) (after)

Changed: unlock_folders-No_paperkeys (before) (after)


Growing Pains Call Tweet reminder before meetup(recurring until ~June 2019)

zoom link/minutes (same location)   [ to be scheduled by John]  Thanks Jon! :)

Forum Thread

Growing Pain's draft v.01 public EDIT document

constant description, 2 different messages, 1 week before and a day before --  [later to be simple written :)] I will own the msg (Amelia)

design by @rstjames

@jclingan @kwsutter @aeiras
Who would like to provide the 2 different tweet message for this?
After I have this I will create a visual and schedule it all for the year.

me Ryan :) Just slight changes as we have done for the other recurring tweets.
This particular tweet won't go for the entire year, only half. :) still thinking on the dates.


Can't run getcap in steam-run (symbol lookup error: getcap: undefined symbol: cap_get_nsowner)

Describe the bug
A clear and concise description of what the bug is.

This makes SteamVR's vrstartup script think that no capability is set on vrcompositor-launcher which causes it to show a popup prompt on every SteamVR startup asking for superuser permissions and then an error message becasue of https://github.com/NixOS/nixpkgs/issues/69338.
To Reproduce
Steps to reproduce the behavior:

steam-run getcap

Expected behavior
A clear and concise description of what you expected to happen.
It should print usage and, when pointed at a file, the capabilities of the file.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
https://github.com/NixOS/nixpkgs/issues/71554
Notify maintainers

@abbradar
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 5.6.19, NixOS, 20.09pre233323.dc80d7bc4a2 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.6
channels(root): "nixos-20.09pre233323.dc80d7bc4a2, nixpkgs-mozilla, nixos-stable-20.03.2310.fb6c3a6831c, nixos-unstable-20.09pre231796.22a81aa5fc1"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

The linker error is caused by using nixpkgs getcap with libcap from steamrt.  Adding libcap to the steam FHS multiPkgs fixes this, but seems to break other things:
diff --git a/pkgs/games/steam/chrootenv.nix b/pkgs/games/steam/chrootenv.nix
index 56e1a09f36e..ea8cd3bc39c 100644
--- a/pkgs/games/steam/chrootenv.nix
+++ b/pkgs/games/steam/chrootenv.nix
@@ -111,6 +111,9 @@ in buildFHSUserEnv rec {
     libuuid
     libbsd
     alsaLib
+
+    # needed by getcap for vr startup
+    libcap
   ] ++ (if (!nativeOnly) then [
     (steamPackages.steam-runtime-wrapped.override {
       inherit runtimeOnly;
@@ -144,7 +147,6 @@ in buildFHSUserEnv rec {
     expat
     dbus
     cups
-    libcap
     SDL2
     libusb1
     dbus-glib

~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory

This made me think about RPATH / LD_LIBRARY_PATH / RUNPATH and the implications of getcap using RUNPATH instead of RPATH.
Fixing getcap gets rid of the popup if you manually setcap, but that causes other issues you've already discovered.
I'm going to leave this for now.  I just wanted to document my investigation.

This fixes the issue, I am now able to run the regular vrstartup.sh from steam-run without any popup after setting the cap manually (automatic setcap via SUID wrappers doesn't work because of https://github.com/NixOS/nixpkgs/issues/69338).
It does not fix the issue in Steam itself though oddly, not even when Steam is run from within steam-run.
Which are those "other things" your patch breaks? I was able to run SteamVR and Beat Saber without any issue (well, none that I didn't have before).
As for your shared library issue, that's fixed by #55973.

Which are those "other things" your patch breaks?

I was just referring to ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory

still important to me, @stalebot

still important to me, @stalebot

fixed by #114024


The Material property track does not work correctly when using the AnimationPlayer node, but it does in the editor

Tested versions
4.3 beta3
System information
Godot v4.3.beta3 - Windows 10.0.19041 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1060 3GB (NVIDIA; <IP_ADDRESS>12) - Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 Threads)
Issue description

It doesn't work after setting
Steps to reproduce
Does not work properly after setting material properties on an animation player node
Minimal reproduction project (MRP)
bug-test (2).zip

What doesn't work? Please explain what you expect to happen or how you expect it to behave, and then explain how it does actually behave, or in what way it doesn't behave correctly

You need to configure it for smooth transition, please see the documentation
You can't smoothly transition between two materials, you have to change the properties instead

No, not two materials.
I'm only transitioning one value of the shader in one material

No you are animating two different materials in your MRP, or did you upload the wrong file?

sorry，What is MRP，my English is poor，Can you explain？

There's only one track here, so what are two materials?

ok，I solved it.this problem.thanks，is not a bug，just my setting problem


Checkout failing brings back to first step without error message

I tried to access the complete.html.slim page by completing an order using the "4242424242424242" credit card, but when I click on "Place Order" I end up back to the first step of the checkout without any error message.
Is this caused by the credit card being rejected ? If so, is there a way to know that this is the reason to add an error message on the page ?

This is now fixed. The full error message is displayed in the checkout page.
Will be adding an error map, so that we can display more friendly messages.


Strategy Pattern C#

Fiddle here

@GuruCharan94 You submitted great PR. Would you like to help me maintain this project?

@aloisdg Sure :)

Nice!


Server: plugin_manager kills plugins when can't resolve the package

If I have a package which loads a third party package as a plugin, and a subpackage which does not reference the third party package, then the plugin crashes.
my_project/analysis_options.yaml
analyzer:
  plugins:
    angular

my_project/pubspec.yaml
dependencies:
  angular: any

my_project/lib/foo.dart
import "package:angular/angular.dart"
...

my_project/subproject/pubspec.yaml
dependencies:
  # none

It attempts to start plugins for each root, and since subproject since its own root which doesn't have its own analysis_options.yaml it inherits the outer options. However, it cannot resolve the package angular inside of subproject, and crashes the plugin for lib/foo.dart.

@bwilkerson do you want to take a look at this or do you want me to?

I'm happy to let you look into it.
I'm not entirely sure what the behavior ought to be, but I'm confident that crashing the plugin isn't the right behavior. I suspect that what it ought to do is not attempt to use the plugin to analyze anything in subproject because it doesn't know which version of the plugin would be appropriate.
If it isn't already doing so, server needs to communicate to the client that subproject should be excluded when analyzing my_project.
It would also be nice to produce a diagnostic that indicates the nature of the problem so that other users would have an easier time understanding why the plugin isn't analyzing files in subproject. I think the diagnostic should be reported against subproject/pubspec.yaml. But that might be more work than we can afford to do right now.


feat[SWA-133]:Contact information [UI]

The type of this PR is: feat
SWA-133
UI for Contact Information

This PR resolves []
Description

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[x] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 417711f9f4fe3f6ac0e8cb3849964ac151e45b22

this PR looks good to me so far.
I have 3 things in mind:
1- could you please also request review from @kiryl-zubarau and @iskounen?
2- did you test this PR in Android? (the accordion navigation doesn't seem to work in Android)
3- are you planning to implement the rest of the tasks as described in the ticket?
4- can we add tests for the changes?

this PR looks good to me so far.
I have 5 things in mind: 1- could you please also request review from @kiryl-zubarau and @iskounen? 2- did you test this PR in Android? (the accordion navigation doesn't seem to work in Android) 3- are you planning to implement the rest of the tasks as described in the ticket in this PR or another one? 4- can we add tests for the changes? 5- why are there some diff about mutations not related to this PR? 🤔

This is just the UI so that we can present tomorrow, still things to be added, under a different PR.

replaced by https://github.com/artsy/eigen/pull/6124

Replaced by https://github.com/artsy/eigen/pull/6124


Flatten ancestor lists for diag_spei.R and diag_spi.R.

Before you start, please read our contribution guidelines.
Please discuss your idea with the development team before getting started, to avoid disappointment later. The way to do this is to open a new issue on GitHub. If you are planning to modify an existing functionality, please discuss it with the original author(s) by tagging them in the issue.

Tasks

[x] Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
[x] Give this pull request a descriptive title that can be used as a one line summary in a changelog
[x] Make sure your code is composed of functions of no more than 50 lines and uses meaningful names for variables
[x] Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
[ ] Preferably Codacy code quality checks pass, however a few remaining hard to solve Codacy issues are still acceptable. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
[ ] Please use yamllint to check that your YAML files do not contain mistakes
[ ] (Only if really necessary) Add any additional dependencies needed for the diagnostic script to setup.py, esmvaltool/install/R/r_requirements.txt or esmvaltool/install/Julia/Project.toml (depending on the language of your script) and also to package/meta.yaml for conda dependencies (includes Python and others, but not R/Julia)
[ ] If new dependencies are introduced, check that the license is compatible with Apache2.0

New recipe/diagnostic

[ ] Add documentation for the recipe to the doc/sphinx/source/recipes folder and add a new entry to index.rst
[ ] Add provenance information

Modified recipe/diagnostic

[ ] Update documentation for the recipe to the doc/sphinx/source/recipes folder
[ ] Update provenance information if needed
[ ] Assign the author(s) of the affected recipe(s) as reviewer(s)

New data reformatting script

[ ] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[ ] Add the new dataset to the table in the documentation
[ ] Tag @mattiarighi in this pull request, so that the new dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

Modified data reformatting script

[ ] Test the CMORized data using recipes/example/recipe_check_obs.yml, to make sure the CMOR checks pass without errors
[ ] Tag @mattiarighi in this pull request, so that the updated dataset can be added to the OBS data pool at DKRZ and synchronized with CEDA-Jasmin

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.

Closes #1717

Not completely tested due to Mistral issues.

Not completely tested due to Mistral issues.

You still can run the recipe in interactive mode (better on mistralpp).
I can try it now.

Yes, I did that yesterday, but it took forever (and I forgot something). I can restart it also again in there.

Searching for ancestors in the R diagnostics returns this list:
> grep -r ancestors --include="*.R" .

./droughtindex/diag_spi.R:  ancestors = list(""),
./droughtindex/diag_spi.R:  xprov$ancestors <- modfile[mod]
./droughtindex/diag_spi.R:xprov$ancestors <- modfile
./droughtindex/diag_save_spi.R:  ancestors = list(""),
./droughtindex/diag_save_spi.R:   xprov$ancestors <- list(modfile[mod])
./droughtindex/diag_spei.R:  ancestors = list(""),
./droughtindex/diag_spei.R:  xprov$ancestors <- list(modfile1[mod], modfile2[mod])
./droughtindex/diag_spei.R:xprov$ancestors <- c(modfile1, modfile2)
./quantilebias/quantilebias.R:    ancestors = list(infile, ref_data_file),
./miles/miles_regimes.R:    ancestors = infile,
./miles/miles_eof.R:    ancestors = infile,
./miles/miles_block.R:    ancestors = infile,
./hyint/hyint.R:      ancestors = prov_info[[fname]]$ancestors,
./hyint/hyint_plot_trends.R:              ancestors = prov_info[[infile]]$ancestors
./hyint/hyint_plot_trends.R:              prov_info[[figname]]$ancestors <-
./hyint/hyint_plot_trends.R:                c(prov_info[[figname]]$ancestors,
./hyint/hyint_plot_trends.R:                  prov_info[[infile]]$ancestors)
./hyint/hyint_plot_trends.R:                ancestors = prov_info[[infile]]$ancestors
./hyint/hyint_plot_trends.R:          ancestors = prov_info[[infile]]$ancestors
./hyint/hyint_plot_maps.R:                ancestors = prov_info[[infile]]$ancestors
./hyint/hyint_plot_maps.R:                ancestors = list(prov_info[[infile]]$ancestors,
./hyint/hyint_plot_maps.R:                  prov_info[[ref_filename]]$ancestors)
./hyint/hyint_plot_maps.R:              ancestors = list(prov_info[[infile]]$ancesstors,
./hyint/hyint_plot_maps.R:                prov_info[[ref_filename]]$ancestors)
./hyint/hyint_plot_maps.R:            ancestors = prov_info[[infile]]$ancestors
./hyint/hyint_etccdi_preproc.R:    prov_info[[hyint_file]]$ancestors <-
./hyint/hyint_etccdi_preproc.R:          c(prov_info[[hyint_file]]$ancestors, etccdi_files)
./hyint/hyint_diagnostic.R:    ancestors = climofiles[model_idx],
./hyint/hyint_trends.R:    ancestors = prov_info[[infile]]$ancestors,
./extreme_events/extreme_events.R:    ancestors = as.list(infile),
./extreme_events/extreme_events.R:    ancestors <- sapply(setdiff(models_name, reference_datasets),
./extreme_events/extreme_events.R:    xprov <- provenance_record(ancestors)
./magic_bsc/extreme_index.R:            ancestors = list(projection_filenames, reference_filenames),
./magic_bsc/extreme_index.R:  ancestors = list(fullpath_filenames),
./magic_bsc/multimodel_products.R:  ancestors = list(fullpath_filenames),
./magic_bsc/weather_regime.R:    ancestors = list(fullpath_filenames[reference_files]),
./magic_bsc/weather_regime.R:  ancestors = list(
./magic_bsc/weather_regime.R:  ancestors = list(filencdf1, filencdf2),
./magic_bsc/capacity_factor.R:    ancestors = list(
./magic_bsc/combined_indices.R:xprov <- list(ancestors = list(fullpath_filenames),
./magic_bsc/extreme_spells.R:      ancestors = list(projection_filenames, reference_filenames),
./magic_bsc/toymodel.R:  ancestors = list(fullpath_filenames),
./magic_bsc/diurnal_temp_index.R:      ancestors = list(

Do you see anything that can be quickly fixed in a similar way?
Sorry if I can't help, but I don't speak R. :disappointed:

Tested successfully!

Merging this now.
Please open a new PR if you have the fixes for the other diags.

ok ,thanks!


Bug: can't use Python API

Describe the bug
Importing to use the python API fails.
 This must be done before importing other portions of archivebox, as they all depend on a Django db being present and valid.

I hadn't. Using archivebox.config first as you say does make it work.
This example from the API docs crashes at from archivebox.main import
https://docs.archivebox.io/en/latest/Usage.html
import os
DATA_DIR = f"{os.environ['HOME']}/archivebox"
os.chdir(DATA_DIR)

from archivebox.main import check_data_folder, setup_django, add, remove, server

check_data_folder(DATA_DIR)
setup_django(DATA_DIR)

Whereas this modification using archivebox.config works.
# This modification based on your mention of `archive.config` works.
import os
DATA_DIR = f"{os.environ['HOME']}/archivebox"
os.chdir(DATA_DIR)

from archivebox.config import setup_django
setup_django()

from archivebox.main import check_data_folder, setup_django, add, remove, server

Consider changing those docs if that's the intended usage.


Possibility to disable logging remote IP address

django-auditlog stores remote IP address to remote_addr field of LogEntry. However, IP address can be considered personal data, at least (according to GDPR)[https://gdpr-info.eu/issues/personal-data/]. An application that I'm developing uses django-auditlog to log data changes (who did what and when), but user IP address is not essential information, and therefore should not be stored.
Also, it's not very visible that audit log stores remote IP address at all. It's not visible in admin view for example.
Is there a way to disable storing remote address?

No, there is no way right now.
You can create a custom middleware inherited from AuditlogMiddleware and disable remote IP address and use it:
from auditlog.middleware import AuditlogMiddleware

class AuditlogMiddlewareWithoutIP(AuditlogMiddleware):
    @staticmethod
    def _get_remote_addr(request):
        return None

Also, we can add a config flag to disable this behavior by configuration

Thank you for a quick reply. I have to go with custom middleware for now. But a config flag would be very appreciated in future versions. :+1:

I have created a PR for this purpose : #620

Thanks @Nathan-Cohen  for fixing this


More sophisticated showMissing behaviour and reused more entity counts

Resolves #676
Resolves #752
No data issue are fixed for all visualizations (mosaic doesn't need it because only one stratification var), as well as the rationalisation of the back end entity count calls.
There is one remaining UX niggle, which will need some discussion and a future ticket: when viewing a faceted plot, cancelling a subsetting filter via the global filters popup changes the layout of the "skeleton spinners" to single un-faceted layout. When the data comes from the back end, the layout reverts again to faceted.  This is to do with waiting for facetedCounts to no longer be pending.

Ready for review please. Seems to work fine with latest merge from main.

I looked into the skeleton issue a little more and couldn't find a solution in the short time I spent on it. Let's go with this for now and revisit. I suspect the solution will involve ensuring filters and EntityCounts props that are passed to visualizations are consistent. It's late and I don't see an obvious way to do this, but I'm confident there is a solution.

Thanks both for reviewing.
I've added a ticket for the skeleton issue. Please change if you don't think it's low cost


Create vaadin.yaml

Fixes https://github.com/vaadin/quarkus/issues/105

/cc @mcollovati

Thank you very much @gastaldi

@gastaldi One additional question: in our starter project we usually do not depend directly on the extension runtime artifact, but on vaadin-quarkus-extension that is a Vaadin platform artifact that imports the Vaadin extension, the jandex index and the collection of UI components.
For the Quarkus catalog, is it mandatory to point to the runtime artifact or can we reference vaadin-quarkus-extension?

@mcollovati the vaadin-quarkus-extension is not a Quarkus extension, therefore it can't be included in the registry. The artifacts listed in this catalog all contain a JAR with a META-INF/quarkus-extension.yaml to be considered a valid extension. If you could include that YAML in the distribution maybe we could replace the existing artifact with this one

I'll discuss this with the team. Thanks for the information.

@gastaldi I did some test locally adding the quarkus-extension.yaml to vaadin-quarkus-extension jar and using this dependency with the create goal of quarkus-maven-plugin and it worked fine.
So, once we will have the new platform artifacts released, with the added file, I'll create a new PR to update info.yaml
/cc @manolo @mstahv


update license year

noticed this trivial change. feel free to close PR in favor of a general year update one.

Works for me. Thanks


Documentation not up-to-date for machine configuration

Azure Auto manage Machine Configuration for windows states that it is in audit mode only and nothing is mentioned about apply and autocorrect, while there is a blog posted announcing it: https://techcommunity.microsoft.com/t5/azure-governance-and-management/apply-cis-compliant-azure-security-baselines-through-azure/ba-p/3775763

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

ID: 69ae795c-78e7-fbdc-44f4-a8111ebf1e95
Version Independent ID: 538ba11a-bd3d-40be-bc2a-92d376add0fa
Content: Azure Automanage for Windows Server
Content Source: articles/automanage/automanage-windows-server.md
Service: automanage
GitHub Login: @mmccrory
Microsoft Alias: memccror

@DylandeJong
Thank you for bringing this to our attention.
I've delegated this to content author @mmccrory, who will review it and offer their insightful opinions.

#reassign: agrawalakanksha

@agrawalakanksha @mmccrory Please review it.

Thank you for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner, and we sincerely apologize for the delayed response. We are closing this issue for now and creating an internal work item to address it.
#please-close


HAWQ-1455. Wrong results on CTAS query over catalog

This reverts the previous fix for HAWQ-512, however to HAWQ-512, it looks like
we could modify the lock related code following gpdb to do a real fix. Those code
was probably deleted during early hawq development.

 For this specific bug, I have no doubt it works. But for lock mechanism, gpdb fix involves more than that. Not sure if there is potential issue in lock.

My guess is that we simplified the lock mechanism, i.e. we removed some
code from gpdb. That patch seems to be the whole gpdb patch against pg for
open source.
2017-05-10 17:14 GMT+08:00 zhenglin tao<EMAIL_ADDRESS>
Seems these codes comes from a bunch of bug fix involved from GPDB commit
6b0e52beadd678c5050af9c978c26d171ba86ae0. For this specific bug, I have
no doubt it works. But for lock mechanism, gpdb fix involves more than
that. Not sure if there is potential issue in lock.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-hawq/pull/1232#issuecomment-300423845,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHI5jJ1cITueX3x4Z_fYO19GnsvLxfl0ks5r4X_ngaJpZM4NRu03
.

Looks good to me. +1

+1 for the fix


more realistic Enchant glint

This PR redoes the way the glint is applied to enchanted items. The new system doesn't use any JS instead it uses an SVG filter applied with CSS.
This performance improvement allows the enchanted glint to be applied to animated textures.
This PR also makes the enchant glow look like it does in-game except for on the SkyLea theme which uses a glint in the style of the old system. In the future, an option can be added to the settings menu to allow users to choose their preferred glint style.
This PR also removes the glint from heads to match in-game.
This system also makes animated glints possible but that is outside the scope of this PR.
Note: This PR does not fix potion enchantment glints that will come in a future PR.
Before this PR:

Not Enchanted:

After this PR:

After this PR (Lea Theme):

I still think heads should also be enchanted :/


Getting modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like f(...) is deprecated

I am trying to do setup, following SETUP.MD file, getting an error while running make document-store
Error log seems to suggest modal Deprecation Error coming from markdown.py.
Error Log:
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Traceback (most recent call last):
  File "/pkg/modal/_container_entrypoint.py", line 463, in handle_input_exception
    yield
  File "/pkg/modal/_container_entrypoint.py", line 615, in run_inputs
    res = imp_fun.fun(*args, **kwargs)
  File "/root/markdown.py", line 69, in to_documents
    text = get_text_from(markdown_url)
  File "/pkg/modal/functions.py", line 1401, in __call__
    deprecation_error(
  File "/pkg/modal/exception.py", line 120, in deprecation_error
    raise DeprecationError(f"Deprecated on {date(*deprecated_on)}: {msg}")
modal.exception.DeprecationError: Deprecated on 2023-08-16: Calling Modal functions like `f(...)` is deprecated. Use `f.local(...)` if you want to call the function in the same Python process. Use `f.remote(...)` if you want to call the function in a Modal container in the cloud
Stopping app - uncaught exception raised locally: TypeError("'UserCodeException' object is not iterable").
╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /Users/ansumansingh/Downloads/ask-fsdl-main/etl/markdown.py:45 in main                           │
│                                                                                │
│    44 │   documents = (                                                                          │
│ ❱  45 │   │   etl.shared.unchunk(  # each lecture creates multiple documents, so we flatten      │
│    46 │   │   │   to_documents.map(                                                              │
│                                                                                │
│ /Users/ansumansingh/Downloads/ask-fsdl-main/etl/shared.py:66 in unchunk                          │
│                                                                                │
│    65 │   """Recombines a list of lists into a single list."""                                   │
│ ❱  66 │   return [item for sublist in list_of_lists for item in sublist]                         │
│    67                                                                                │
│                                                                                │
│ /Users/ansumansingh/Downloads/ask-fsdl-main/etl/shared.py:66 in <listcomp>                       │
│                                                                                │
│    65 │   """Recombines a list of lists into a single list."""                                   │
│ ❱  66 │   return [item for sublist in list_of_lists for item in sublist]                         │
│    67                                                                                │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
...

Thanks for the report, ansmuan!
This repo is no longer being actively maintained. But I believe you can resolve the issue by switching adding .remote to any call that triggers the deprecation warning.


attempting to build C or GOLANG programs on Raspberry PI

I’m trying to build the go metrics package on my pi with MQ but it’s failing in the build.   So, I tried to look for options to build amqsput and didn’t find specific options as in the KC for linux on RHEL.
same error for both:
pi@raspberrypimq:~ $ gcc  -march=armv7 -o amqsput_32 amqsput0.c -I $MQ_INSTALLATION_PATH/inc -L $MQ_INSTALLATION_PATH/lib -Wl,-rpath=$MQ_INSTALLATION_PATH/lib -Wl,-rpath=/opt/mqm/lib -lmqm
/usr/bin/ld: cannot find -lmqm
collect2: error: ld returned 1 exit status
pi@raspberrypimq:~ $
Looping back to this later tonight when I’m tired and my pi rebooted I’m more confused with the golang.   Has that been done?
cheers
Tom

Looks like linker can't find the dll library mqm.  From the knowledge centre ( https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q028480_.htm ) the command to build 32 bit single threaded is
gcc -m32 -o amqsputc_32 amqsput0.c -I MQ_INSTALLATION_PATH/inc -L MQ_INSTALLATION_PATH/lib
-Wl,-rpath=MQ_INSTALLATION_PATH/lib -Wl,-rpath=/usr/lib -lmqic

Note that mqic is specified as it is the C client. - https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.dev.doc/q025810_.html
Check that it does exist. It should be in /opt/mqm/lib. If it is does and then you may also need to add the library path to the environment variable LD_LIBRARY_PATH

What is $MQ_INSTALLATION_PATH set to? Where did you install the MQ package?

On our newer platforms (including for the Pi) we're preferring to only support the threaded libraries. The non-threaded libraries are somewhat an artifact of history rather than being necessary any more.


How to raise test coverage on parameters passed to NoOpLogger

I'm failing to meet 100% coverage requirements in a module because the call by name string inside a log effect never gets executed. Would it be reasonable to make the no-op logger execute the passed in strings or to provide an option that allowed it?

I ran into the same problem today. The solution proposed by @ChristopherDavenport seems sensible. Would a PR along these lines be acceptable?


Only get few posts

Hi, thanks for providing the new way to get the posts.
There are some problems show up:

If I set group parameter in get_posts funciton, it turns out error.

"""
File ~\anaconda3\Lib\site-packages\facebook_scraper\extractors.py:108 in init
self.scraper = kwargs['scraper']
KeyError: 'scraper'
"""

The problem above solved ffter I remove the parameter group and just type the groups ID. But even I set the pages parameter in the get_posts function to 20, I still only get 8 posts.
It seems like mbasic.facebook only display 8 posts in one pages. If I want to check more, I have to click the "see more posts" button.

Is there any other way to fix this problem? Thanks a lot.
Here is the code that I can only get 8 posts in a group:
from facebook_scraper import get_posts

for post in get_posts('817620721658179', base_url="https://mbasic.facebook.com/groups",
start_url="https://mbasic.facebook.com/groups/817620721658179?v=timeline",
                      pages=50,
 cookies = "www.facebook.com_cookies.txt"):

  print(post['text'][:50])

@Joshuahuang55 Thanks,
I have updated my repo (this one) to fix the error you mentioned with the KeyError. and found an issue with the page cursor having old regex. It should get all the pages now.

Still having only 8 posts on a private groupe after pip install --force-reinstall --no-deps git+https://github.com/moda20/facebook-scraper.git@master

@moda20 Thanks!! I can get all pages now. So appreciate!!
@Cartasiane You have to join the private group and adjust your code.
And then you need to assert "group" parameter to tell the code you want to scrap "group". So you can get more than 8 posts.
from facebook_scraper import get_posts

for post in get_posts(group = '817620721658179', base_url="https://mbasic.facebook.com/groups",
start_url="https://mbasic.facebook.com/groups/817620721658179?v=timeline",
                      pages=50,
 cookies = "www.facebook.com_cookies.txt"):

  print(post['text'][:50])

Ok, this work for me but even if I'm not in verbose mode the script is printing using extra page processor for every page... Might be nice to remove this!

@Cartasiane @Joshuahuang55 i am closing this issue since it's resolved


Error. Cannot connect to database: SQLSTATE[HYT00]

Driver version or file name
pdo_sqlsrv 5.2.0
SQL Server version
SQL Server 2017
Client operating system
Linux
PHP version
PHP Version 7.0.30
Microsoft ODBC Driver version
17
Problem description
When trying to connect to my database using the code below, I get the following error:

Error. Cannot connect to database: SQLSTATE[HYT00]: [unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired

I have installed all the necessary drivers including their most updated versions as can be seen here:
ODBC version 0x0380
PDO_ODBC
PDO_sqlsrv version 5.2.0
sqlsrv version 5.2.0
Expected behavior and actual behavior
I am expecting my code to connect to the database successfully. Instead I get the mentioned error.
Repro code
<?php

class DB_Connect {
    private $db;

    function construct() {
    }

public function connect() {
        require_once 'String.php';

        try {
              $this->db = new PDO('sqlsrv:Server=server,port; Database=database_name', 'username', 'password');
            return $this->db;
        } catch (PDOException $e) {
            return "Error. Cannot connect to database: " . $e->getMessage();
        }
    }
?>

Yes I have checked the FAQ and gone through the posts. However what I see different from the other posts is that the issue is not intermittent. It is always happening. Can you please check it out?

Hi @mlaferla,
Are you using named instance? If so, please check this page or #442.
Also, please tell me:

What are the output of running sqlcmd using the same credentials?
How did you install our drivers, using pecl as shown in our documentation?
Which linux platform?

For the time being I don't have access to run sqlcmd on the server from where I am calling the database, however when running sqlcmd from my local PC, I am able to connect successfully.
drivers are the latest (5.4.0) and were installed using pecl.
Linux Platform is Redhat 7

Hi @yitam. I found that the issue was a firewall one which was prohibiting the server from connecting to the database.
We reinstalled the drivers using pecl, as per your documentation and opened access for the server to access the database.
It works now :)
Thanks for your help.

Glad to hear that @mlaferla
Thank you for getting back to us.


If to open github.com/caddyserver/xcaddy/cmd/xcaddy@latest in browser, it returns 404.

If to open github.com/caddyserver/xcaddy/cmd/xcaddy@latest in browser, it returns 404.

That's not a real URL. It's a Go module path.
 What version of Go? Run go version to check. You should have at least 1.18 or ideally 1.19.

$ go version
go version go1.18.3 linux/amd64
Caddy is running on an Amazon Linux.

Works just fine for me:
$ go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest
go: downloading github.com/caddyserver/xcaddy v0.3.0

Not on AMI though. But you haven't shown us an error or anything, so we can't do much here.
You can just download the binary from the GitHub releases tab if you can't figure it out otherwise.


Add asyncio support

Oh .. wow!
Thanks for the pull request .. will try find some time for review. On first glance, looks functionally o.k. Just lots of duplicate code - maybe

Took me a while to figure out that my docker container in the unittests wouldn't run :D
I'll look into the stuff as soon as I got the unittests working

apparently, my local docker image for testnet was too old for the features in genesis.json :D

I really love how you deal with pytest.fixtures and bring in an entire bitshares backend into the unittests ... loving it

With pytest -v tests/testnet/aio/* , all tests are green (or skipped). However, including all other tests, I get a MissingKeyException. Probably unrelated to the aio code.


[Bug Report]: Fix trigger for ServiceFabric/Clusters

Describe the bug
Trigger for ServiceFabric/Clusters does not trigger in ADO, on changes to the modules files, as it is missing a relative folder path of /ARM/.
To reproduce

Connect the ADO pipeline for ServiceFabric/Clusters
Do a change in the module files
See that the CI pipeline for the module does not automatically trigger.

Code snippet
No response
Relevant log output
No response

Was resolved in PR #1601


Migrate to Checker Framework

This PR introduces the following changes.
Migration from JSR-305 to Checker Framework

The language level was set to Java 8.
@Nullable is used from the Checker Framework instead of javax.annotations.

Guava snapshot dependency
The project now uses Guava version: HEAD-jre-SNAPSHOT. This version is required for correct handling of @Nullable by NullPointerTester.
Error Prone introduction
The compiler is added to the Java build configuration.
Annotations for FormatString and FormatMethod were also used.
Removal of style check plugins
The right margin checker and Javadoc link plugins were removed (along with the abstract base) because they proved to be of very low or no value for that amount of code. The warnings these plugins
generated could not be handled (e.g. too long HTML links in Javadocs, or long static imports). The rest we spot via PR reviews.
Should such a need arise, we'd turn to automatic formatting during build time (instead of IDEA design time), or review other approaches without creating own solutions for such needs.
Plugin renamings
All tool modules moved under the tools directory (removing gradle-plugins sub-directory).
This layout follows the structure of tool modules that have Gradle-dependent code under the gradle sub-packages.
The following artifacts were renamed:

spine-javadoc -> spine-javadoc-filter
spine-protobuf-javadoc-plugin -> javadoc-prettifier.
spine-gcs-plugin -> spine-gcloud-storage.

Dependency changes

Guava -> HEAD-jre-SNAPSHOT (until next release)
Gradle -> 4.7
Protobuf Gradle Plugin -> 0.8.5

Spine version advances to 0.10.36-SNAPSHOT.

@armiol, PTAL.


Microsoft.AppConfiguration: Add 2020-07-01-preview API version

This PR has already been reviewed and approved in the private repo: Azure/azure-rest-api-specs-pr#1497
The PR adds new API version 2020-07-01-preview, which includes two changes comparing with version 2020-06-01.

Remove the listKeyValue API.
Add KeyValue proxy resource and GET/SET APIs for it.

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

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] 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

[ ] 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

[ ] 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

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@ChenTanyi Not sure why 'WaitForARMFeedback' label is added automatically. This PR actually has been approved by ARM team in the private repo.

@ZhijunZhao Thanks for figure out. It would be OK to merge. Please let me know when you want to merge it.

Cool. We plan to release next week. So, please hold on the merge.

/azp run automation - sdk

@ChenTanyi We've finished the deployment. Can this PR be merged?  As for the LintDiff error, it's a newly added rule. If we have to fix it, we need to make code change on our service side.

@ZhijunZhao Is it possible to add such list operation? Will it be a large effect?
I think that a get request doesn't has corresponding list operation is strange, for "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/keyValues/{keyValueName}"

/openapi sdkautomation

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@ChenTanyi Yes, it takes efforts to add such an API to RP. I'm surprised that ARM team didn't point this out when they review the PR.

@jianyexi Does it matter for the [Staging] Swagger LintDiff failure? It seems that it was added after the CI run last time.

@jianyexi Does it matter for the [Staging] Swagger LintDiff failure? It seems that it was added after the CI run last time.

It's a error from a new rule required by ARM , should also be fixed

It's a error from a new rule required by ARM , should also be fixed

@ZhijunZhao Could you fix this problem? Due to it is required from ARM.

It's a error from a new rule required by ARM , should also be fixed

@ZhijunZhao Could you fix this problem? Due to it is required from ARM.

Sure. Will work on it.

Reasons for asking suppression of violation R4015 - NestedResourcesMustHaveListOperation.
After GA, we received many customer requests that GET/SET key-values via ARM template should be supported. To achieve this, we introduce the key-value as a proxy resource so that ARM can make GET/SET key-value requests to RP and the requests are passed through to data plane.
We don't want to add the list operation for two reasons.

The introduction of keyValue resource is solely for ARM support. But there is no scenario that ARM could make list request for the keyValue resource. We don't want to add an API with no use case.
List key-values is supported by data plane. If we introduce this API to control plane, user might abuse it via management SDK. Even for GET/SET key-values, user should use the data plane SDK, instead of management SDK. We don't want to support a scenario that is not a good practice.

Reasons for asking suppression of violation R4015 - NestedResourcesMustHaveListOperation.
After GA, we received many customer requests that GET/SET key-values via ARM template should be supported. To achieve this, we introduce the key-value as a proxy resource so that ARM can make GET/SET key-value requests to RP and the requests are passed through to data plane.
We don't want to add the list operation for two reasons.

The introduction of keyValue resource is solely for ARM support. There is no scenario that ARM could make list request for the keyValue resource. We don't want to add an API with no use case.
List key-values is supported by data plane. If we introduce this API to control plane, user might abuse it via management SDK. Even for GET/SET key-values, user should use the data plane SDK, instead of management SDK. We don't want to support a scenario that is not a good practice.

@

Reasons for asking suppression of violation R4015 - NestedResourcesMustHaveListOperation.
After GA, we received many customer requests that GET/SET key-values via ARM template should be supported. To achieve this, we introduce the key-value as a proxy resource so that ARM can make GET/SET key-value requests to RP and the requests are passed through to data plane.
We don't want to add the list operation for two reasons.

The introduction of keyValue resource is solely for ARM support. There is no scenario that ARM could make list request for the keyValue resource. We don't want to add an API with no use case.
List key-values is supported by data plane. If we introduce this API to control plane, user might abuse it via management SDK. Even for GET/SET key-values, user should use the data plane SDK, instead of management SDK. We don't want to support a scenario that is not a good practice.

This rule is requested recently by ARM, @ravbhatnagar  could you confirm the suppression ?

@jianyexi Should you add a need-ARM-review label so that @ravbhatnagar don't miss our comment?

@ravbhatnagar could you confirm the suppression?

@ZhijunZhao - what about delete API? this keyvalue resource can be created via the control plane. support for deleting it via control plane is also required.

@ravbhatnagar these APIs are being added to our control plane purely for ARM template deployment support. There was no way to hook up the ARM template engine to our data plane. So we have to have get and create on the control plane.
For any other scenario that involves the manipulation of key-values users are strongly urged to use the data plane. We don't want to add APIs to our control plane for which we don't have any scenario that we would tell a user to use it for. In fact, if we added those APIs we would always ask any user not to use them. It seems counter-intuitive.
It seems that the ask here is based on a consistency point-of-view, but I think that in this case the ask would not result in a solid user story.

/azp run automation - sdk

Please fix the conflict first.

/azp run automation - sdk

/azp run automation - sdk

/azp run unifiedPipeline

#sign-off


[Snyk] Security upgrade serverless from 1.83.3 to 3.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

src/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

556/1000  Why? Recently disclosed, Has a fix available, CVSS 5.4
Open Redirect SNYK-JS-GOT-2932019
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: serverless
    The new version differs by 250 commits.

16c29da chore: Release v3.0.0
ad1faa3 chore: Bump dependencies
c150045 refactor: Rename `…nts/api-gateway/lib/method/requestParameters.test.js`
95e308d refactor: Rename `…s/package/compile/events/alb/lib/healthCheck.test.js`
358a1cf refactor: Rename `lib/plugins/aws/package/compile/events/eventBridge`
88b52ab test: Rename `test/integrationPackage`
3f8b1a1 refactor: Rename `…e/compile/events/api-gateway/lib/hack/updateStage.js`
93d1c29 refactor: Rename `…events/api-gateway/lib/hack/disassociateUsagePlan.js`
bb70c63 refactor: Rename `…kage/compile/events/websockets/lib/routeResponses.js`
bff4cc7 refactor: Rename `…/events/websockets/lib/pickWebsocketsTemplatePart.js`
20b90cb refactor: Rename `…kage/compile/events/api-gateway/lib/usagePlanKeys.js`
3ea8389 refactor: Rename `…/package/compile/events/api-gateway/lib/usagePlan.js`
04158ea refactor: Rename `…ws/package/compile/events/api-gateway/lib/restApi.js`
897fdfc refactor: Rename `…e/compile/events/api-gateway/lib/requestValidator.js`
44f48f5 refactor: Rename `…ws/package/compile/events/api-gateway/lib/apiKeys.js`
cb3518e refactor: Rename `lib/plugins/aws/package/compile/events/apiGateway`
98e454e refactor: Rename `…/aws/package/compile/events/alb/lib/listenerRules.js`
0b542a1 refactor: Rename `…s/aws/package/compile/events/alb/lib/targetGroups.js`
72624b0 refactor: Rename `…lugins/aws/package/compile/events/s3/configSchema.js`
6ee1a79 refactor: Rename `…package/compile/events/msk/getMskClusterNameToken.js`
f2a4f96 refactor: Rename `…compile/events/lib/ensureApiGatewayCloudWatchRole.js`
364e52a refactor: Rename `lib/plugins/aws/package/compile/events/httpApi.js`
ebe4035 refactor: Rename `…s/aws/package/compile/events/iotFleetProvisioning.js`
04f6318 refactor: Rename `…lugins/aws/package/compile/events/cognitoUserPool.js`

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Open Redirect

resolved by #92


Getting SignatureDoesNotMatch when trying to put objects with non-printable characters.

In our case, the exact file name that throws the error contains the left-to-right-mark character (wiki http://en.wikipedia.org/wiki/Left-to-right_mark).
We are able to upload the file from the aws console using chrome.
We are able to upload the file using boto3.
We are unable to upload the file using aws sdk v3 preview (<IP_ADDRESS>).

Thanks for the bug report, we'll investigate further.

The problem is in the way System.Uri handles characters that are not supposed to exist in a uri.
It simply strips them away even if they are url encoded. Try the lrm char and you will see exactly that.
The string AWSSDK signs includes the key name with url encoding. So lrm is encoded with chars starting with %, but the request which gets sent doesn't have the char at all. So when the S3 service signs what it received it obviously signs a different string, this complaining about not matching signatures.
You have to check MSDN pages for the way System.Uri does this. I am currently investigating how to adapt my code to this but I think AWSSDK should take this into consideration when signing the request string since System.Uri isn't going to change.

Thanks for the extra info; this wouldn't be the first time we've had to work around the behavior of System.Uri and encoded characters in a url.
How are you specifying the character in the original keyname that gets submitted to signing - using the  encoded character or by using the UTF-8 'E2 80 8E' character sequence?

I just assign the file's name to the PutObjectRequest.Key. So whatever FileInfo.Name returns already contains the lrm char for the file causing the problem.
But, I also tried creating a Uri from a string containing the encoded lrm char, that is containing the sequence %E2%80%8E and Uri strips it away once again.
Checking System.Uri source verifies that behavior. http://referencesource.microsoft.com/#System/net/System/URI.cs,4282

@theofanis as you correctly pointed out, System.Uri removes these characters from the final uri. This means that there is no way for a .NET application to send a request to S3 for a key containing bidirectional control characters.
It's possible to change the SDK (by signing a request where the key has no bidirectional control characters) to get this scenario to "work", but this would lead to unwanted behavior: a user will think they are working with key A, but actually will be working with key B. This will be confusing, and could lead to loss of user data.
At this point, I am inclined to say that this is not a change we want to make to the SDK. I am also thinking that the SDK should check for bidirectional control characters in key names and throw an exception, to clearly convey that the .NET SDK is unable to properly handle these characters.

Checking for those characters and throwing before creating the SDK request is not a bad thing. It would certainly help if it clarifies the situation, since it would save a developer from researching this more to find out what I found after putting some significant amount time to it.
Feel free to close this. Thanks for the reply.

We've made and released the change to the SDK to throw an exception if bidirectional control characters are detected in the resource path. Closing.


Limit Recording Time

When recording a live stream I just want to record 30mins then stop and convert, is it possible pyriscope can have strict recording time option.

Yes, very possible, and all thanks to ffmpeg! Since ffmpeg is at the heart of recording live streams and, as I just checked, has a -t argument, it's just a matter of capturing the -t argument in Pyriscope and passing it to ffmpeg when it is called to start recording....... which I have already done! It will be available in 1.2.5, which I will push soon.
The usage is:
pyriscope [url] -t <duration>

where duration is defined by https://www.ffmpeg.org/ffmpeg-utils.html#time-duration-syntax.


Allow to edit server meta context on SSR

Is your feature request related to a problem? Please describe.
This problem affects the two internationalization projects that currently exist in Leptos (leptos_i18n and leptos-fluent). Nowadays we are using the next dirty hack to set the lang (and in the case of leptos-fluent, the dir also) attribute(s) on SSR with Leptos v0.6:
leptos_meta::Html(
    leptos_meta::HtmlProps {
         lang: ...,
         dir: ...,
         class: ...,
         attributes: ...,
    }
);

Of course, the above code is a simplification. On leptos-fluent, I'm parsing the result of leptos_meta::use_head().html.as_string() to keep the previous values of lang, dir and class, altough attributes is not possible because is a private field. These values are possibly previously set by a previous invocation of an <Html/> component in the tree.
Describe the solution you'd like
I want that use_head() would return ServerMetaContext instead of MetaContext on SSR. These two types would need a refactor because are only exposing certain things when not on SSR, which IMO is really strange. And then, probably build an API to allow something like:
#[cfg(features = "ssr")]
{
    let context = use_head();
    let mut attrs = context.html().attributes();
    // ... manipulate the attributes
    context.html.set_attributes(attrs);
}

Describe alternatives you've considered
There is no alternatives currently.
Additional context
This is a blocking issue for the migration to Leptos v0.7. Note that a Provider implementation as suggested in #2780 is not possible because if an user wants to provide their own <Html/> before or after in the component tree they can't, we would be forcing users to give to our libraries (leptos-fluent and leptos_i18n) the ability to set their own <Html/> components in their code.
FYI @Baptistemontan

Is the issue that you do not want to override a lang attribute set by the user with a lang attribute set by the internationalization library?

The issue is that currently I don't want to override other attributes that are not lang neither dir. But, for sure, if the user has provided a <Html lang=.../> and/or <Html dir=.../> attribute, I at least want to display a warning on #[cfg(debug_assertions)] advicing that leptos-fluent will override these attributes.
From the conversation at #2780:

I would suggest that rather than an SsrHtmlTag component you have something like a FluentProvider component, which takes children and uses the Html component, then evaluates the children. This is a pretty typical pattern in component-based frameworks, and will ensure that modifying the <html> tag works as expected on any platform, rather than only using SSR.

I'm still very interested to know why the framework is providing a provide_meta_context or even provide_context functions but library authors are forced to use a <Provider/>, even when is not clear that resolves all the problems that a programmatic API would.

Thanks for the tag @mondeja!
I too would be interested in something like this, it would be greate to be able to do
let head = use_head();

let on_click = move || head.set_lang("en-GB");

Without having to deal with the <Html /> component, that in itself does'nt render to a view anyway.

The issue is that currently I don't want to override other attributes that are not lang neither dir.

See the example above. Using an <Html/> component to set lang and dir will not override user-set attributes that are not lang or dir.

I'm still very interested to know why the framework is providing functions like provide_meta_context and provide_context but library authors are forced to use a <Provider/>, even when is not clear that resolves all the problems that a programmatic API would.

Library authors are not forced to use a <Provider/>. I believe I wrote a pretty good description of the case for Provider vs provide_context in the other thread, but I am happy to clarify if you have further questions.

More context about the next fragment of code:
<I18n>
    ...
</I18n>

This will not work on leptos-fluent because all the code is generated from a macro. In any case, I would be forcing users to do this:
 #[component]
pub fn I18n() -> impl IntoView {
    leptos_fluent! {

    }
}

Because I need all the advantadges that macros provides to shrink unused code and other performance improvements at compile time. Which could be solved with components-as-proc-macros (<I18n! my_compile_time_option="a syn literal"), but that's another topic to discuss.

See the example above. Using an <Html/> component to set lang and dir will not override user-set attributes that are not lang or dir.

if the user has provided a <Html lang=.../> and/or <Html dir=.../> attribute, I at least want to display a warning on #[cfg(debug_assertions)] advicing that leptos-fluent will override these attributes.

How can I get values of previous <Html/> invocations on SSR? AFAIK is not possible.

It's a little hard for me to keep track of this thread because there are several different topics being raised. Apologies if I have missed something.

This will not work on leptos-fluent because all the code is generated from a macro. In any case, I would be forcing users to do this: ...

I have looked a bit at the macro code for leptos-fluent. It seems to me that by far the simplest API here is to adapt the macro's output slightly so that it is declarative, rather than imperative, by returning the attributes it needs to set. The user would write:
let attrs = leptos_fluent! {{
  translations: [TRANSLATIONS, TRANSLATIONS] + COMPOUND,
  locales: "./locales",
  ...
};

view! {
  <Html {..attrs}/>
  // ... the rest of the user's application
}

This makes it very obvious what is going on.

How can I get values of previous <Html/> invocations on SSR? AFAIK is not possible.

You are correct, this is not currently possible. (This kind of introspection of one part of the view tree from another is, in general, not supported.) I can think of several ways to make it possible at least to access which attribute keys have been set. There would be overhead to any of these approaches, but I guess it's fine in debug mode.
Is this only for the debugging purpose of warning the user when they have set their own lang or dir that are being overwritten?
For reference, the way this would end up being handled is that the framework would simply emit both the values into HTML, in the order they appeared in the application, and the browser would use one of them (I believe it's usually the first one, but am not sure if this is specified)
<html lang="en" lang="es">

======
I am not trying to be difficult here. It's just that exposing internals comes with a significant downside, including the fact that making internal changes becomes a breaking change. The core functionality you are trying to implement can be implemented without exposing these internals, so it is not likely that I will make the change to expose them.

Okay, your concerns and pretty reasonable. I'll implement the <Provider> + <Html/> expansion on the macro as it seems that the framework is being developed in that direction.

Is this only for the debugging purpose of warning the user when they have set their own lang or dir that are being overwritten?

Yes, that would make the whole implementation complete. But it's definitely not something that is in a hurry or completely necessary.
For my part this issue can be closed, at least in the way it is presented. Thanks for your patient and detailed explanations about Leptos' internals!

I'm going to leave the issue open as a reminder to myself to add the ability to get that debug info on which keys have been added! Let me know if you run into issues with the <Html/>-based approach.


No option to write custom shell script in a job

If I am correct, right now a job can only be told to run a shell script in the material. But what if I want to write a script that should be run in that job without committing it the VCS (like jenkins)?
Any possible way of doing this?

There are better chances of getting help on our gocd user mailing list.
Since you asked, there's convenience plugin that allows you to run a series of command. (Go supports this too without a plugin for e.g. using bash -c)


feat: defaults handler for Ingress, pods and pvcs

This Pull Request implements #610
Required some code refactoring to keep code as clean as possible.
Here's some notes for the review:

The assumption is always, that if a value for Default is defined, it's automatically allowed within a tenant. The default value does not have to be explicit allowed (Better User-Experience).
Patches are only mutated for Ingress. PVCs and Pods can not be patched on the relevant fields, which would cause a default mutation.
IngressClass only supported on API networking/v1. Feature supported for Ingress on networking v1 and v1beta1
StorageClass only supported on API storage/v1
PriorityClass only supported on API schedule/v1

PVCs and Pods can not be patched on the relevant fields, which would cause a default mutation.

I'm not getting the point here: if we define a mutating webhook for these fields, we should be able to respond with a mutating response that would be executed by the API Server, as we're doing with Namespaces.
Am I missing something else?


Support route where some methods are authenticated

Is your feature request related to a problem? Please describe.
I have an endpoint where the GET method is public but the PUT method needs authentication:
route("/item/{id}") {
  get {
    ...
  }
  authenticate {
    put {
      ...
    }
  }
}

If I install the NotarizedRoute next to the get method, it will not introspect the authentication, which will be wrong for the put method.
If I install the NotarizedRoute next to the put method, it -will- introspect the authentication, which will be wrong for the get method.
If I install the route both places, I get an error saying the route has already been registered.

Describe the solution you'd like
Make it possible to register the same route multiple times, as long as the methods do not overlap.

Hmmm... can't you just install the put documentation inside the authentication block?


[resolves #516] Verify that resource streams obtained from a class loade...

...r are closed properly

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/374/
Test PASSed.


[Snyk] Upgrade @govtechsg/tradetrust-ui-components from 2.21.0 to 2.21.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @govtechsg/tradetrust-ui-components from 2.21.0 to 2.21.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 3 months ago, on 2023-10-04.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Improper Input Validation SNYK-JS-POSTCSS-5926692
265/1000  Why? CVSS 5.3
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: @govtechsg/tradetrust-ui-components

2.21.1 - 2023-10-042.21.1 (2023-10-04)
Bug Fixes

postcss (#163) (c410af7)

2.21.0 - 2023-08-172.21.0 (2023-08-17)
Features

Endorsement Chain Provider Handling (#158) (c2fbb7d)

    from @govtechsg/tradetrust-ui-components GitHub release notes

Commit messages

Package name: @govtechsg/tradetrust-ui-components

c410af7 fix: postcss (#163)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Version installed


Sheet to Array of Array

Hi,
I love this lib.
Today there is a sheet_to_json.
I often need a sheet_to_aoa
That will return an array of array and not an array of json objects.
Is there an option to sheet_to_json that will return that?

header: 1 as described in https://docs.sheetjs.com/#json :
XLSX.utils.sheet_to_json(ws, {header:1});

Thanks for the answer - that's what I was looking for.
Maybe there is room to make it a bit more obvious in the doc there - I've
read that part several times before I wasted time creating my own version
of sheet_to_json.
I can see now that it states that in the "header is expected to be one of"
Unfortunately when I read it the first few times - I didn't find it (that
table didn't pop out to me)
I'm not sure if it's just me or something that can be improved in the doc -
your call :)
Thanks - very cool lib
On Fri, Oct 2, 2020 at 9:19 AM SheetJSDev<EMAIL_ADDRESS>wrote:

header: 1 as described in https://docs.sheetjs.com/#json :
XLSX.utils.sheet_to_json(ws, {header:1});
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SheetJS/sheetjs/issues/2124#issuecomment-702548676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD65PUYM4HBIWVDDUM6LRRLSIVWITANCNFSM4SBH6ZUQ
.

Docs are a work in progress.  Feel free to submit a PR or give a recommendation and we'll try to improve it!

thanks for this thread, and totally agreed on documentation needing improvement. is there a contribution guide? any way to get this scaffolded up can enable developers like myself to contribute more effectively. see this example

We've moved the docs to a new site https://docs.sheetjs.com/ .  Source for the site is https://github.com/SheetJS/docs.sheetjs.com .  The docz subfolder is the Docusaurus-powered structure and the build sequence moves the generated site to the docs subfolder.
https://docs.sheetjs.com/docs/miscellany/contributing is the contribution guide, let us know if anything else should be added.


Event log

A user should be able to see a stream of events  from the API.
https://github.com/epinio/epinio/issues/593

needs discussion with epinio team about event system


Implemantation of Issue #267: Custom Template for Group Labels

new directive uiSelectGroup for customizing the item groups header template.
if no custom group template is given, a default fallback to $group.name is used instead.
see examples/demo-groupby.html for further explanations

any interest in this?

I have interest on this, thank you very much for your work — I currently pulled it on my fork and playing with it. IMO, this is must have feature.
I've found one issue: for some reason ng-repeat directive does not work inside of ui-select-group directive (yeah, I'm crazy and I need to have group labels to be huge). And I do not know why.

Here is an example that illustrates problem with ng-repeat: http://plnkr.co/3fGeRhzjXl1CYHZhcDcO
By the way it's a nice example of custom templates for group labels, I think.

This needs rebasing, as well as unit tests.


New sheet for Matrons of Mystery

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: Matrons of Mystery  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: Savage Spiel (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: PBTA (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.