pkg/dds/test/sse_smoke_test flaky on mac due to ChromeDriver version

There are new test failures on Report DUPLICATE_DEFINITION for 'values' in enums..
The tests
pkg/dds/test/sse_smoke_test RuntimeError (expected Pass)

are failing on configurations
unittest-asserts-release-mac

Based on the history it seems to have started flaking more since February 3rd, 2022.
Most recent logs
  SessionNotCreatedException (500): session not created: This version of ChromeDriver only supports Chrome version 91
  Current browser version is 97.0.4692.99 with binary path /opt/s/w/ir/cache/builder/sdk/third_party/browsers/chrome/Google Chrome.app/Contents/MacOS/Google Chrome

@athomas @whesse Did we upgrade our chrome versions on the bot?
@bkonyi FYI

This error happens from time to time for a long time. Duplicate to https://github.com/dart-lang/sdk/issues/43743.

Popped up again, approving.


Enhancement - Autocomplete of use statements

A really nice feature that PHPStorm has that nearly every other PHP autocomplete (including my favourite, Komodo) lacks, is autocomplete fuzzy matching of use statements.
An example:
<?php
use Twig

That would give the autocomplete list, and show every class that has the word Twig in it in. Does that make sense? It is a small but amazingly useful feature once you're used to it being there!
Cheers,
Josh

Today the fuzzy is working on the full namespace of every classes.
So every classes with "Twig" should be in your suggestions as you ask for here no?

It doesn't appear to be working in this Symfony project, no. I'm going to turn off a couple other plugins to see if it's being caused by something else and get back to you!
Sent from my iPhone

On 21 Sep 2015, at 3:01 pm, Axel Anceau<EMAIL_ADDRESS>wrote:
Today the fuzzy is working on the full namespace of every classes.
So every classes with "Twig" should be in your suggestions as you ask for here no?
—
Reply to this email directly or view it on GitHub.

I'm using this plugin on symfony2 projects everydays and it works like that.
If you have autocomplete in your PHP files, the problem could come from somewhere else, if you don't, it's perhaps a misconfiguration of the plugin itself.

I agree, which is why I thought it's possibly caused by another plugin :) I'll take a look at verify what's causing it tomorrow and get back to you
Sent from my iPhone

On 21 Sep 2015, at 11:00 pm, Axel Anceau<EMAIL_ADDRESS>wrote:
I'm using this plugin on symfony2 projects everydays and it works like that.
If you have autocomplete in your PHP files, the problem could come from somewhere else, if you don't, it's perhaps a misconfiguration of the plugin itself.
—
Reply to this email directly or view it on GitHub.

I'll take the fact that there has been no response as a good thing, meaning that this is no longer an issue ;-). Feel free to open a new ticket or ask for help if this is still a problem.


Dynamic discriminator

I have an OData Endpoint that handles batch operations via /$batch. To differentiate between responses, the discriminator odata.metadata can be used. Unfortunately, this discriminator is tied to the API's base URL and varies depending on that URL. How can we handle a dynamic discriminator?
Schema
openapi: 3.0.0
info:
  title: OData Batch
  version: 1.0.0

paths:
  /v1.0/$batch:
    post:
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BatchRequest'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BatchResponse'

components:
  schemas:
    BatchRequest:
      type: object
      description: 'A JSON batch request body consists of a single JSON object with one required property: requests. https://learn.microsoft.com/en-us/graph/json-batching#request-format'
      properties:
        requests:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              method:
                type: string
                enum:
                  - GET
                  - POST
                  - PATCH
                  - DELETE
              url:
                type: string
              body: # Proper schema definition left out for brevity
                type: object
                properties:
                  value:
                    type: object
                    additionalProperties: true
    BatchResponse:
        type: object
        description: 'The response format for JSON batch requests is similar to the request format. https://learn.microsoft.com/en-us/graph/json-batching#response-format'
        properties:
            responses:
            type: array
            items:
                type: object
                properties:
                id:
                    type: string
                status:
                    type: integer
                body:
                    oneof:
                     - $ref: '#/components/schemas/FooResponse'
                     - $ref: '#/components/schemas/BarResponse'
                    discriminator:
                      propertyName: odata.metadata # NOTE: This is the discriminator property

    FooResponse:
      type: object
      description: 'OData Variant Foo response'
      properties:
          odata.metadata:
              type: string
          value:
              type: array
              items: # Proper schema definition left out for brevity
                  type: object
                  additionalProperties: true

    BarResponse:
      type: object
      description: 'OData Variant Bar response'
      properties:
          d:
              type: object
              properties:
                  results:
                      type: array
                      items: # Proper schema definition left out for brevity
                          type: object
                          additionalProperties: true

Example Request
{
  "requests": [
    {
      "id": "1",
      "method": "GET",
      "url": "/foo",
    },
    {
      "id": "2",
      "method": "GET",
      "url": "/bar",
    }
  ]
}

Example Response
{
  "responses": [
    {
      "id": "1",
      "status": 200,
      "body": {
        "odata.metadata": "https://example.com/v1.0/$metadata#foo", // NOTE: This is the discriminator property
        "value": [
          {
            "id": "1",
            "name": "foo"
          }
        ]
      }
    },
    {
      "id": "2",
      "status": 200,
      "body": {
        "odata.metadata": "https://example.com/v1.0/$metadata#bar", // NOTE: This is the discriminator property
        "value": [
          {
            "id": "1",
            "name": "bar"
          }
        ]
      }
    }
  ]
}

Hi @dotjpg3141
Thanks for using kiota and for reaching out.
This should already be supported by kiota today:

The batch response will generate a union type wrapper
Deserialization to the right member type will be handled thanks to the discriminator mapping

What's missing from your description is the mapping property under the discriminator object as described in the specification.
Let us know if you have further questions.

The value of the discriminator changes based on the base URL of the server.
If I generate the client based on a Swagger document on a.example.com, then this would be the schema:
body:
  oneof:
    - $ref: '#/components/schemas/FooResponse'
    - $ref: '#/components/schemas/BarResponse'
  discriminator:
    propertyName: odata.metadata
    mapping:
      https://a.example.com/v1.0/$metadata#foo: FooResponse
      https://a.example.com/v1.0/$metadata#bar: BarResponse

If I deploy this client to b.example.com, then the discriminator would change. Consequently, deserialization would fail, wouldn't it?
body:
  oneof:
    - $ref: '#/components/schemas/FooResponse'
    - $ref: '#/components/schemas/BarResponse'
  discriminator:
    propertyName: odata.metadata
    mapping:
      https://b.example.com/v1.0/$metadata#foo: FooResponse
      https://b.example.com/v1.0/$metadata#bar: BarResponse

Thanks for the additional information.
So is it essentially the same service deployed at different "places" ? Why would you have different odata metadata/type value then?
If you take the example of Microsoft Graph, which is deployed to a number of different clouds with different hostnames, the OData Type value doesn't vary based on the host. (in fact, only the fragment is advertised like #microsoft.graph.user)

So is it essentially the same service deployed at different "places" ?

Exactly

(in fact, only the fragment is advertised like #microsoft.graph.user)

Intersting to know. I'll have to check the Microsoft OData examples. My current implementation returns an absolute path.


Set ARCH in s390x-linux triplet

Fixes https://github.com/microsoft/vcpkg/issues/34973

This issue sets the ARCH environment variables to s390x on s390x-linux and s390x-linux-release triplets
The original idea was to fix the specific port where we hit the particular issue , ie. opentelemetry-cpp. But then found that fixing the triplet itself will be beneficial to build all the ports on s390x

Closing this PR for now because it hasn't been updated in a few months, if you are still working on it, feel free to make a new PR. Thanks!

Has there ever been review feedback?


chore(deps): update deps

Update some outdated deps, this is an attempt to reduce the list of outdated dependencies tracked by https://github.com/kubewarden/kubewarden-controller/pull/306

This is odd, golangci didn't fail on my computer (tm)!
I'll look into that


kubespy: init at 0.5.1

Motivation for this change
A tool to observe Kubernetes resource in real time
closes #92196
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

figuring out build issue upstream: https://github.com/pulumi/kubespy/issues/73

/marvin opt-in

/status awaiting_reviewer

Reviewed points

[x] package path fits guidelines
[x] package name fits guidelines
[x] package version fits guidelines
[x] package build on Darwin
[x] executables tested on Darwin
[x] meta.description is set and fits guidelines
[x] meta.license fits upstream license
[x] meta.platforms is set
[x] meta.maintainers is set
[x] build time only dependencies are declared in nativeBuildInputs
[x] source is fetched using the appropriate function
[x] phases are respected
[x] patches that are remotely available are fetched with fetchpatch

Possible improvements
Comments
Tested only execution of kubespy with no arguments, it prints help for the command.

@ludovicc thank you anlot for this review on my first PR to nicpkgs.
/status needs_merger

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/215

Minor nitpick: this PR added two extra spaces in an otherwise empty line in pkgs/top-level/all-packages.nix. This isn't the case anywhere else in this file.

@Luflosi Thanks for hinting, looks like I might need to tweak my nix-lsp.


SCORE_THRESH in pointpillar.yaml

Hi
Nice work.
I want to konw how to set the SCORE_THRESH  in pointpillar.yaml, because the results corresponding to different SCORE_THRESH are not the same. When the SCORE_THRESH is set low, many redundant boxes will be predicted.
Dataset： Kitti.
    POST_PROCESSING:
        RECALL_THRESH_LIST: [0.3, 0.5, 0.7]
        SCORE_THRESH: 0.1
        OUTPUT_RAW_SCORE: False

        EVAL_METRIC: kitti

        NMS_CONFIG:
            MULTI_CLASSES_NMS: False
            NMS_TYPE: nms_gpu
            NMS_THRESH: 0.01
            NMS_PRE_MAXSIZE: 4096
            NMS_POST_MAXSIZE: 500

Thanks.

It's a hyper-parameter and you could adopt grid-search to explore the value of it under different requirements.


Which TensorFlow-Slim is the "real" one?

I have found 3 TensorFlow-Slim in repo tensorflow/tensorflow and tensorflow/model

(tensorflow/tensorflow) tensorflow.contrib.slim
(tensorflow/model) model.slim
(tensorflow/model) model.inception.inception.slim

Among these places, there are some duplicated codes.
e.g.

(tensorflow/tensorflow) tensorflow/tensorflow/contrib/slim/python/slim/nets/overfeat.py
(tensorflow/model) slim/nets/overfeat.py

Question:

What are these 3 slim packages used for? What's the differences?
In the future, which one may be deprecated? Or which one will be the future.

cc @nathansilberman @lukaszkaiser @sguada

Use tensorflow.contrib.slim for all the core functionality.
Use tensorflow/model/slim for the models and nets.
This one is deprecated: (tensorflow/model) model.inception.inception.slim

@sguada Thanks for your explanation!


"Transient parent has another exclusive child." when exporting Android Gradle build

Godot version
4.0.rc2.official
System information
Mageia 9, Linux
Issue description
Users have been accustomed to our "Transient parent has another exclusive child." errors, some occurrence of which got fixed following #67122. But it still happens in some circumstances, so we should keep track of those and ideally fix them.
This even became meme material :) https://www.reddit.com/r/godot/comments/10zhq56/i_love_when_the_editor_speaks_in_tongues/
If anything, I think we could make this error verbose only, as it doesn't seem to affect the use of the editor and end users can't do anything about it.

So I noticed one occurrence when exporting to Android with "Use Gradle Build" enabled, which shows another exclusive popup with the gradle build output.
Here's a stacktrace:
(gdb) bt
#0  Window::set_visible (this=0x1be64380, p_visible=true) at scene/main/window.cpp:748
#1  0x00000000083c6e98 in Window::popup (this=0x1be64380, p_screen_rect=...) at scene/main/window.cpp:1546
#2  0x00000000083c6b69 in Window::popup_centered_ratio (this=0x1be64380, p_ratio=0.800000012) at scene/main/window.cpp:1508
#3  0x00000000074ec562 in EditorNode::execute_and_show_output (this=0xe40c430, p_title=..., p_path=..., p_arguments=..., p_close_on_ok=true, p_close_on_errors=false) at editor/editor_node.cpp:6524
#4  0x00000000070d2dab in EditorExportPlatformAndroid::export_project_helper (this=0xf30e8f0, p_preset=..., p_debug=true, p_path=..., export_format=0, should_sign=true, p_flags=0)
    at platform/android/export/export_plugin.cpp:2903
#5  0x00000000070cf9bb in EditorExportPlatformAndroid::export_project (this=0xf30e8f0, p_preset=..., p_debug=true, p_path=..., p_flags=0) at platform/android/export/export_plugin.cpp:2671
#6  0x00000000079c18dd in ProjectExportDialog::_export_project_to_path (this=0x1020c630, p_path=...) at editor/export/project_export.cpp:1021
#7  0x00000000079d0e4e in call_with_variant_args_helper<ProjectExportDialog, String const&, 0ul> (p_instance=0x1020c630,
    p_method=(void (ProjectExportDialog::*)(ProjectExportDialog * const, const String &)) 0x79c16ae <ProjectExportDialog::_export_project_to_path(String const&)>, p_args=0x7fffffff8c80, r_error=...)
    at ./core/variant/binder_common.h:293
#8  0x00000000079d06b0 in call_with_variant_args<ProjectExportDialog, String const&> (p_instance=0x1020c630,
    p_method=(void (ProjectExportDialog::*)(ProjectExportDialog * const, const String &)) 0x79c16ae <ProjectExportDialog::_export_project_to_path(String const&)>, p_args=0x7fffffff8c80, p_argcount=1, r_error=...)
    at ./core/variant/binder_common.h:407
#9  0x00000000079ce306 in CallableCustomMethodPointer<ProjectExportDialog, String const&>::call (this=0x10665dc0, p_arguments=0x7fffffff8c80, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:104
#10 0x000000000a08033d in Callable::callp (this=0x7fffb8003de8, p_arguments=0x7fffffff8c80, p_argcount=1, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:50
#11 0x000000000a3b6214 in Object::emit_signalp (this=0x104fa740, p_name=..., p_args=0x7fffffff8c80, p_argcount=1) at core/object/object.cpp:1046
#12 0x0000000006376a0c in Object::emit_signal<String> (this=0x104fa740, p_name=...) at ./core/object/object.h:869
#13 0x00000000073a359c in EditorFileDialog::_action_pressed (this=0x104fa740) at editor/editor_file_dialog.cpp:489
#14 0x00000000073c2122 in call_with_variant_args_helper<EditorFileDialog>(EditorFileDialog*, void (EditorFileDialog::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x104fa740,
    p_method=(void (EditorFileDialog::*)(EditorFileDialog * const)) 0x73a2570 <EditorFileDialog::_action_pressed()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:293
#15 0x00000000073c0a01 in call_with_variant_args<EditorFileDialog> (p_instance=0x104fa740, p_method=(void (EditorFileDialog::*)(EditorFileDialog * const)) 0x73a2570 <EditorFileDialog::_action_pressed()>,
    p_args=0x0, p_argcount=0, r_error=...) at ./core/variant/binder_common.h:407
#16 0x00000000073bf464 in CallableCustomMethodPointer<EditorFileDialog>::call (this=0x105ace50, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:104
#17 0x000000000a08033d in Callable::callp (this=0x22e1ee38, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:50
#18 0x000000000a3b6214 in Object::emit_signalp (this=0x104fa740, p_name=..., p_args=0x0, p_argcount=0) at core/object/object.cpp:1046
--Type <RET> for more, q to quit, c to continue without paging--
#19 0x0000000005852765 in Object::emit_signal<>(StringName const&) (this=0x104fa740, p_name=...) at ./core/object/object.h:869
#20 0x00000000084bd405 in AcceptDialog::_ok_pressed (this=0x104fa740) at scene/gui/dialogs.cpp:127
#21 0x00000000084c5b19 in call_with_variant_args_helper<AcceptDialog>(AcceptDialog*, void (AcceptDialog::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x104fa740,
    p_method=(void (AcceptDialog::*)(AcceptDialog * const)) 0x84bd3a4 <AcceptDialog::_ok_pressed()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:293
#22 0x00000000084c5204 in call_with_variant_args<AcceptDialog> (p_instance=0x104fa740, p_method=(void (AcceptDialog::*)(AcceptDialog * const)) 0x84bd3a4 <AcceptDialog::_ok_pressed()>, p_args=0x0, p_argcount=0,
    r_error=...) at ./core/variant/binder_common.h:407
#23 0x00000000084c48b0 in CallableCustomMethodPointer<AcceptDialog>::call (this=0x10508a70, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:104
#24 0x000000000a08033d in Callable::callp (this=0x22f3add8, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:50
#25 0x000000000a3b6214 in Object::emit_signalp (this=0x10503e80, p_name=..., p_args=0x0, p_argcount=0) at core/object/object.cpp:1046
#26 0x0000000005852765 in Object::emit_signal<>(StringName const&) (this=0x10503e80, p_name=...) at ./core/object/object.h:869
#27 0x00000000083f9e39 in BaseButton::_pressed (this=0x10503e80) at scene/gui/base_button.cpp:138
#28 0x00000000083fa353 in BaseButton::on_action_event (this=0x10503e80, p_event=...) at scene/gui/base_button.cpp:172
#29 0x00000000083f9aae in BaseButton::gui_input (this=0x10503e80, p_event=...) at scene/gui/base_button.cpp:69
#30 0x000000000848d14f in Control::_call_gui_input (this=0x10503e80, p_event=...) at scene/gui/control.cpp:1746
#31 0x000000000837a12b in Viewport::_gui_call_input (this=0x104fa740, p_control=0x10503e80, p_input=...) at scene/main/viewport.cpp:1389
#32 0x000000000837b3b6 in Viewport::_gui_input_event (this=0x104fa740, p_event=...) at scene/main/viewport.cpp:1659
#33 0x0000000008382b0c in Viewport::push_input (this=0x104fa740, p_event=..., p_local_coords=false) at scene/main/viewport.cpp:2834
#34 0x00000000083c5ce1 in Window::_window_input (this=0x104fa740, p_ev=...) at scene/main/window.cpp:1370
#35 0x00000000083f3baa in call_with_variant_args_helper<Window, Ref<InputEvent> const&, 0ul> (p_instance=0x104fa740,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x83c58ea <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc8c8, r_error=...) at ./core/variant/binder_common.h:293
#36 0x00000000083f06a1 in call_with_variant_args<Window, Ref<InputEvent> const&> (p_instance=0x104fa740,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x83c58ea <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc8c8, p_argcount=1, r_error=...) at ./core/variant/binder_common.h:407
#37 0x00000000083ec71a in CallableCustomMethodPointer<Window, Ref<InputEvent> const&>::call (this=0x104fba40, p_arguments=0x7fffffffc8c8, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:104
#38 0x000000000a08033d in Callable::callp (this=0x7fffffffc870, p_arguments=0x7fffffffc8c8, p_argcount=1, r_return_value=..., r_call_error=...) at core/variant/callable.cpp:50
#39 0x000000000523e70f in DisplayServerX11::_dispatch_input_event (this=0xc1e6c40, p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:3546
#40 0x000000000523e487 in DisplayServerX11::_dispatch_input_events (p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:3517
#41 0x000000000a01f8a3 in Input::_parse_input_event_impl (this=0xbb86930, p_event=..., p_is_emulated=false) at core/input/input.cpp:690
--Type <RET> for more, q to quit, c to continue without paging--
#42 0x000000000a020cac in Input::flush_buffered_events (this=0xbb86930) at core/input/input.cpp:940
#43 0x000000000524343b in DisplayServerX11::process_events (this=0xc1e6c40) at platform/linuxbsd/x11/display_server_x11.cpp:4614
#44 0x000000000522302e in OS_LinuxBSD::run (this=0x7fffffffd1a0) at platform/linuxbsd/os_linuxbsd.cpp:876
#45 0x000000000521a500 in main (argc=2, argv=0x7fffffffd708) at platform/linuxbsd/godot_linuxbsd.cpp:73

For the record, here's the stack of windows when this happens (actually some time after, I had to continue so the windows are visible):

The same error happens a second time at the end of the export, with the exact same stacktrace aside from frame 4 being platform/android/export/export_plugin.cpp:2933 instead of platform/android/export/export_plugin.cpp:2903.
Steps to reproduce

Create new project
Install Android build template
Add Android export preset
Select "Use Gradle Build"
Export - when you press "Save", the gradle log output show up in a window and the error is raised

Minimal reproduction project
Empty project.

getting same issue exporting entire project to IOS


fix: undefined validation, jquery3 compatible

This pull request includes a

[X ] Bug fix
[ ] New feature
[ ] Translation

The following changes were made

fix: Cannot read property 'toString' of undefined
fix: error JQMIGRATE: jQuery.fn.offset() requires an element connected to a document for jQuery3

If this is related to an existing ticket, include a link to it as well.

@waitingsong Add some unit test. After it, the PR is ok for merge


Check g function list for validity

Make sure:

The function names being used are valid
The t parameter is >= 0
The start index is before the end index
The indices don't go out of bounds
The indices between g functions don't overlap?

Implemented in 4d205b5. Not checking to make sure the g functions don't overlap, though.


Terraform resource naming to match Bicep resource naming

Benefit/Result/Outcome
Provide consistent resource naming between Terraform and Bicep so that the Terraform deployment output looks similar to the Bicep deployment.
Description
The resource names created by Terraform are not consistent with resource names created by the Bicep deployment. We want to make the names as consistent as possible, allowing for differences when Terraform features do not allow the same implementation as Bicep.
The resourcePrefix and resourceSuffix parameters should be consistent with Bicep, having resourcePrefix as a required parameter.

NOTE: The Bicep templates have a specific way of implementing naming conventions by using a parameter/variable combination with string replacements. We do not have to implement the same pattern if Terraform makes it difficult. We want the same resource names produced by the template regardless of how it's implemented in Terraform.

Acceptance Criteria

The Terraform deployment makes the resourcePrefix parameter required.
The Terraform deployment uses the resourcePrefix and resourceSuffix parameters in a way that is consistent with the Bicep deployment.
Resources created by the Terraform deployment have names consistent with the Bicep deployment, as much as possible.

The resource prefix parameter in Bicep is used to calculate unique names, using logic that is different than what was implemented in Terraform. The naming conventions are also different between MLZ Bicep and Terraform. Therefore I think that we should consider implementing all of the Bicep naming logic in Terraform rather than just requiring the resourcePrefix parameter, which would have small additional value.
Let's start with #679 to document all of the major differences between the Bicep and Terraform deployments and then decide which things we want to implement in Terraform.

I updated the title and description.

We will not be updating the terraform code and will be deprecating the terraform code on June 30, 2024.


Question about conditional relationship tuples

Hi all,
I saw your blog post about conditional relationship tuples, pretty excited about it as this is a functionality we were really looking for! I just have a question about the way I can use it in a use case I already described in another ticket (if I can use it...).
Let say I have the following authorization model, where users own houses and houses belong to quarters, helping me getting residents of a quarter.
model
    schema 1.1
type user
type house
    relations
        define owner: [user]
        define resident: [user] or owner
type quarter
    relations
        define belong_to: [house]
        define resident: resident from belong_to

Now, the use case would be something like :
I want to declare a relation supervisor between user and quarter as far as the user has the relation resident with the quarter.
With the help of your conditional relationship tuples, I thought about defining a condition to check the user actually has the resident relation with the quarter before being added as supervisor. This would lead to the following authorization model.
model
    schema 1.1
type user
type house
    relations
        define owner: [user]
        define resident: [user] or owner
type quarter
    relations
        define belong_to: [house]
        define resident: resident from belong_to
        define supervisor: [user with quarter_resident]

condition quarter_resident(user_id: string, quarter_id: string) {
  // Do stuff here
}

As you can see, I absolutly have no idea if conditional relationship tuples can help me with my use case, and event worse, I absolutly no idea how to implement it... Can you please let me know if thise would work, and if so, how can it work?
Cheers!

Hi @geoffroybraun
Do you want to prevent the supervisor relationship to be added if the user is not in the quarter? If so, you can't enforce that constraint in the model, you'll need to call check(user:x, resident, quarter:y) before adding the relationship.
If you want to make sure that if the relationship was added by mistake, calling check(user:x, supervisor, quarter:y) returns allowed : false, you can define the supervisor relationship as
define supervisor: [user] and resident
Does this make sense, or did I misunderstand the problem you want to solve?

Hi @aaguiarz,
thank you very much for the more than quick reply!
The idea is to block the ability to add a user as supervisor if he/she has not a resident relation with the targeted quarter. I understand I should check the user is resident of a quarter before adding him/her as supervisor on our side, I was just wondering if this was possible within the authorization model to avoid checking multiple relations.
If not, fair enough, we will do it from code.
Thanks!

Alright, that seems fine for me. Just for the record, the define supervisor: [user] and resident line is really helpful and unlocks another use case we have, so even tho I can't use conditional relationship tuples, you still helped for another topic without knowing it, so thank you very much for that.
Wishing you a nice WE in advance!

Glad it helped, have a nice weekend too! :)


Add terminate to pup.schema.json

Thanks for all of your work on this! :raised_hands:

Oh, i missed this. Thanks 🥇


cloud_name is not passed to "netlify-cms-media-library-cloudinary" module

cloud_name is not passed to "netlify-cms-media-library-cloudinary" module
Bug/Issue:
When using "netlify-cms-media-library-cloudinary" with "@staticcms/core" with the bundling integration approach. It seems "cloud_name" (and possibly the "api_key") are not passed down from the init config to the netlify-cms-media-library-cloudinary module.
Code
  import CMS from '@staticcms/core';
  import cloudinary from 'netlify-cms-media-library-cloudinary';

  const config = {
    media_folder: '/cms/media',
    media_library: {
      name: 'cloudinary',
      config: {
        cloud_name: 'xxx',
        api_key: 'xxx',
      },
    },
    collections: [
    ...
    ]
  }

  CMS.init({ config });
  CMS.registerMediaLibrary(cloudinary);

Versions

@staticcms/core: 1.0.0-beta.8
netlify-cms-lib-util: 2.12.3
netlify-cms-media-library-cloudinary: 1.3.10

This feature (really all of the external media library options) have not been fully tested yet, so it doesn't surprise me that this is broken. I'll hopefully get around testing out it out in the next month.

@KaneFreeman I think this issue can be closed as Static CNS dropped external media libraries

Static CMS no longer supports cloundinary.

Static CMS no longer supports cloudinary. If you really need it in your project, might I suggest Decap as an alternative CMS: https://decapcms.org/docs/cloudinary/


sttate in change event

Hi!
<input type="checkbox" data-on-color="info" data-off-color="warning" class="switch" name="type" value="something" checked="checked" data-on-text="on" data-off-text="off" >
$(".switch").bootstrapSwitch();
$('.switch').on('switchChange.bootstrapSwitch', function(event, state)
{
console.log(state); //return: undefined
}).trigger('switchChange.bootstrapSwitch');
switch is on but state is undefined!
why? It's undefined!?

I'm having the same problem.
The original checkbox isn't being checked or unchecked which basically makes this UI component useless.
When I have to capture the state manually it's undefined.
Massive deal breaker :(


SAP on Oracle update

Docs Build status updates of commit a052d31:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/virtual-machines/workloads/sap/get-started.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#sign-off

#sign-off

#sign-off


Built-in Auth System

It is possible to install canvas without its built-in auth system or make its password hashing the same as jetstream hash? I use laravel 8 with jetstream, and when I log in to my own admin dashboard I can't directly access canvas, this feel bit awkward when I have to re-enter my email and password which are the same to access canvas. Thank You

At this point in time, no. While Canvas used to work off of Laravel's base login system, it was changed in v6 to allow more flexibility to the package.
That being said, I believe there's more than likely a way to implement this. I'll keep this in mind moving forward, and see if it's a viable feature in an upcoming release.

well, thank you..

I think Canvas having its own auth system does not encourage flexibility considering anyone can include auth quickly and without any problem in Laravel.

I think Canvas having its own auth system does not encourage flexibility considering anyone can include auth quickly and without any problem in Laravel.

You're right @marvinhosea, but then there's a problem of different auth systems having various underlying properties. Canvas relies quite a bit on the packages' User model now so that it can access various relationships.
The flexibility actually increases having the new auth system, since prior to it there could be a situation like such as this:
Your auth system doesn't use id as it's primary key, or there isn't a Post relationship. And most assuredly, not every auth system is going to have a summary, avatar, etc.
That being said, what would you add to the auth scaffolding that would increase the flexibility in your eyes?

You're right @marvinhosea, but then there's a problem of different auth systems having various underlying properties. Canvas relies quite a bit on the packages' User model now so that it can access various relationships.
The flexibility actually increases having the new auth system, since prior to it there could be a situation like such as this:
Your auth system doesn't use id as it's primary key, or there isn't a Post relationship. And most assuredly, not every auth system is going to have a summary, avatar, etc.
That being said, what would you add to the auth scaffolding that would increase the flexibility in your eyes?

Sorry for replying to this late but all that can be included in the config and in case there is no avatar you can avatar the name initials.
I will PR when I get time for approval. Thanks


Bump Jetty from 9.4.54 to 9.4.56

:mag: Description
Issue References 🔗

This pull request fixes #
Describe Your Solution 🔧

to fix CVE-2024-8184 reported in https://github.com/apache/kyuubi/security/dependabot/75

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (c6212d0) to head (1e8fee5).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6742   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         684     684
  Lines       42281   42281
  Branches     5768    5768
======================================
  Misses      42281   42281

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Does seata have to work with jpa? Under mybatis, no undolog is generated.

Does seata have to work with jpa? Under mybatis, no undolog is generated.

All support.
I think it is a configuration problem,such as DataSourceProxy.
Please join the dingding group 23171167 to discuss.

Does seata have to work with jpa? Under mybatis, no undolog is generated.

The table undo_log should be created manually.
-- the table to store seata xid data
-- 0.7.0+ add context
-- you must to init this sql for you business databese. the seata server not need it.
-- 此脚本必须初始化在你当前的业务数据库中，用于AT 模式XID记录。与server端无关（注：业务数据库）
-- 注意此处0.3.0+ 增加唯一索引 ux_undo_log
drop table `undo_log`;
CREATE TABLE `undo_log` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `branch_id` bigint(20) NOT NULL,
  `xid` varchar(100) NOT NULL,
  `context` varchar(128) NOT NULL,
  `rollback_info` longblob NOT NULL,
  `log_status` int(11) NOT NULL,
  `log_created` datetime NOT NULL,
  `log_modified` datetime NOT NULL,
  `ext` varchar(100) DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `ux_undo_log` (`xid`,`branch_id`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;


No UI during trade screen

Describe the bug
Every time I open the trade screen with CQUI enabled I get the leader displayed but no other UI. None of the UI responds and I need to kill Civ 6 from task manager.
I have never run a mod before. I'm running no other mods. I have vanilla + gathering storm via Epic Games store.
This is on the February Update patch and I'm using mod version 2.3.
To Reproduce
Steps to reproduce the behavior:

Start a new game
Find any civ
Open diplomatic screen
Select "Make Deal"

Attached save has Hungary ready to talk to Japan.
Expected behavior
Trade screen displayed.
Screenshots
If applicable, add screenshots to help explain your problem.
General informations

OS: Windows 10 Home
Version: <IP_ADDRESS>
Expansion: Gathering Storm
Mods: Just CQUI

Save game and logs
MATTHIAS CORVINUS 11 3600 BC.zip
Additional context
None

latest mod version seems to be 2.4. Try after updating the mod.

Try downloading the mod from here if you haven't already: https://steamworkshopdownloader.io/download/2115302648
That site seems to have the up-to-date version.  Steamworkshop.download or whatever it is doesn't seem to get an updated one, its weird.

Yes, that fixed it. Thanks. Yes, I downloaded the latest from steam workshop and it was 2.3.


Unable to follow symbolic link for README to README.md

See https://github.com/dryruby/rack-throttle/blob/master/README
/usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/possible_license_file.rb:16:in `binread': No such file or directory @ rb_sysopen - /usr/local/lib/ruby/gems/2.3.0/gems/rack-throttle-0.5.0/README (Errno::ENOENT)
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/possible_license_file.rb:16:in `binread'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/possible_license_file.rb:16:in `text'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/possible_license_file.rb:12:in `license'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/license_files.rb:19:in `block in find'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/license_files.rb:19:in `reject'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/license_files.rb:19:in `find'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/packages/license_files.rb:9:in `find'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/package.rb:145:in `license_files'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/package.rb:131:in `licensing'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/package.rb:125:in `activations'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/package.rb:121:in `licenses'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/decision_applier.rb:47:in `with_approval'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/decision_applier.rb:30:in `block in apply_decisions'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/decision_applier.rb:30:in `map'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/decision_applier.rb:30:in `apply_decisions'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/decision_applier.rb:6:in `initialize'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/core.rb:58:in `new'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/core.rb:58:in `decision_applier'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/lib/license_finder/cli/main.rb:38:in `action_items'
	from /usr/local/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
	from /usr/local/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
	from /usr/local/lib/ruby/gems/2.3.0/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
	from /usr/local/lib/ruby/gems/2.3.0/gems/license_finder-3.0.1/bin/license_finder:5:in `<top (required)>'
	from /usr/local/bin/license_finder:23:in `load'
	from /usr/local/bin/license_finder:23:in `<main>'

I was going to report exactly the same, this happens when the destination of the symbolink link (for one reason or another) doesn't exists.

Funny. The symlink does point to a file that exists:
https://github.com/dryruby/rack-throttle/blob/master/README.md

I am able to reliably reproduce this by removing the target of a symlink. It looks like License Finder is currently assuming candidate files are readable.

PR #404 includes a fix that warns about dangling symlinks, but does not error out.


Remove support for --k8s-1.15 flag from generate-manifest.sh

Describe what you are trying to solve
This flag was introduced at the end of 2020 to support generating an Antrea YAML manifest which would work for K8s 1.15 clusters. In particular, this flag would ensure that CRDs were registered using the admissionregistration.k8s.io/v1beta1 API, instead of the admissionregistration.k8s.io/v1 API. See https://github.com/antrea-io/antrea/pull/1664 for more information.
The issue is that we have never validated this flag in CI, and as a result I believe that usage of this flag is currently broken and has probably been broken since the v1.0 Antrea release. Notice how the script only handles the legacy versions of the Antrea CRDs: https://github.com/antrea-io/antrea/blob/3f30d848ba3fbb0be8e242130825d0fc6d5c0f45/hack/generate-manifest.sh#L585-L601
Describe the solution you have in mind
My suggestion is to remove support for this flag altogether. The rationale for adding it in December 2020 was (IIRC) that some enterprise users may still be using K8s 1.15 or older. But as of now, K8s 1.16 has been released more than 2 years ago. Moreover, the flag has been broken for a while (as explained below), and the fact that no one has complained suggests that the flag is not actively being used with recent Antrea versions.

@jianjuns @tnqn @guesslin @marcusschiesser any concern?

Make sense to me.

I have no concern.


Middleman fails with error when adding bower_components folder inside source/assets/vendor

When adding a bower_components folder with serveral assets like bootstrap, font-awesome middleman crashes..
/sites/gems/tilt-1.4.1/lib/tilt/template.rb:144:in `require': cannot load such file -- less (LoadError)
I have rebuild a complete site adding and removing files untill this cause showed up.
Why is it not possible to store bower_components inside the source folder, its the ideal way to manage external dependencies. I use middleman 4 latest version in a clean rvm bundle and did a clean middleman init.
Full trace
from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt/template.rb:144:in `require_template_library'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt/css.rb:59:in `initialize_engine'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt/template.rb:56:in `initialize'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt.rb:98:in `new'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt.rb:98:in `block in []'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt.rb:96:in `each'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/tilt-1.4.1/lib/tilt.rb:96:in `[]'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:322:in `strip_extensions'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:310:in `record_file_change'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:257:in `block in update'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:256:in `each'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:256:in `update'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources/source_watcher.rb:204:in `poll_once!'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources.rb:239:in `block in poll_once!'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources.rb:239:in `each'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources.rb:239:in `reduce'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/sources.rb:239:in `poll_once!'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/core_extensions/file_watcher.rb:50:in `before_configuration'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/callback_manager.rb:57:in `instance_exec'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/callback_manager.rb:57:in `block in execute'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/hamster-3.0.0/lib/hamster/vector.rb:1316:in `each'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/hamster-3.0.0/lib/hamster/vector.rb:1316:in `traverse_depth_first'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/hamster-3.0.0/lib/hamster/vector.rb:431:in `each'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/callback_manager.rb:57:in `execute'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_reference.rb:43:in `send_to'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/call_with.rb:76:in `call_with'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/contracts-0.13.0/lib/contracts/method_handler.rb:138:in `block in redefine_method'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/callback_manager.rb:28:in `block in install_methods!'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-core-4.1.7/lib/middleman-core/application.rb:282:in `initialize'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-cli-4.1.7/bin/middleman:48:in `new'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/gems/middleman-cli-4.1.7/bin/middleman:48:in `<top (required)>'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/bin/middleman:23:in `load'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/bin/middleman:23:in `<main>'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/bin/ruby_executable_hooks:15:in `eval'
	from /Users/me2/.rvm/gems/ruby-2.3.1@sites/bin/ruby_executable_hooks:15:in `<main>'

bower_components simply has too many files for Middleman to watch. It also, often, includes files you don't want to compile, like your dependencies' source files in .less.
bower_components and node_modules belong in the root of the project. Use either middleman-sprockets or the import_path command to integrate these files with your project.
Sprockets will allow you to require whichever components you need into JS and CSS.
import_path will simply make those files available as if they were in your source folder, but, without watching the files for changes.

Ok thank you my bad then, i think i have to reread the manuals for 4 then.

I'm not sure that we explicitly talk about bower in relation to Middleman... too many possible combinations of different techs.

How would one use the import_path ?
Could not find it in the documentation thank you

Like line #3 of this test: https://github.com/middleman/middleman/blob/master/middleman-core/fixtures/import-app/config.rb#L3
We don't really document little-used features until enough folks need them. Trying to keep the docs slimmed down to the common use cases.


No base href error

When setting up routing I had to add the following or the app would not run:
import { APP_BASE_HREF } from '@angular/common';
then in the @NgModule annotation:
providers: [{provide: APP_BASE_HREF, useValue: '/'}]

Do you have in your index.html this line in the head section?
<base href="/">

I was able to get around it.  I just wanted to point out that the tutorial does not mention this step.
I didn't use the index.html way of resolving, my solution is in the original comment.  Seems like what you said would be a bit simpler though.

@scottseeker You are right. The tutorial never say anything about router and base href. You should read this:
https://angular.io/docs/ts/latest/guide/router.html#!#base-href :)

:)
closing since this was rewritten with the CLI


New custom https redirect port

When using a proxy or port redirection, I don't want Jira to add the port 8443 to the url. So I need Jira to redirect to port 443 even if the tomcat https port is 8443 and then I manage the 443 myself to redirect to 8443. Simple change and defaults is the same as before.
In my case: $tomcat_native_ssl = true and $tomcat_redirect_https_port       =  443
We can discuss how to require native_ssl if redirect_https_port is set?

i'm confused about lack of tomcat_redirect_http_port, but then again, i suppose we want to encourage secure installations.

as far as native_ssl goes, i'd add validation:
if $tomcat_redirect_https_port {
  validate_integer($tomcat_redirects_port)
  unless ($native_ssl) {
    fail("reasoning…")
  }
}

Thanks for the validation code! 👍
In my case, I configured Jira to redirect in https. So when I first hit 80 -> 8080, is goes to ssl 443. I'm not sure if the URL is changed to jira:8080. I think there is no redirect option in configuration for a normal http port. Maybe I'm wrong but a default config doesn't include a redirect option for normal http.


Feat: Modify core for SolidJS

Solid will only re-render the DOM if it detect signal values that being used via their accessor functions in the DOM are changed via their corresponding setter functions.
Options that being changed are options that intended to possibly be controlled by the users such as data, column, and state. By allowing them to be accessor functions, any instance method that calls accessor functions inside it will also be treated as an accessor function. Therefore, those three options can be correctly controlled by the user.
Without this change, user has no way to change data, column, or state directly (via signal setter function) in runtime (changes after initialization) that should have been re-render the table.
Options that not intended to be directly controllable by the user at runtime are not changed to accept accessor function.
The tests hasn't been written yet. But, you can manually test by running the examples that being prefixed with solid- in solid-table branch of my react-table repository fork. Here is the repository branch. The simplest way to try it is to run that repo branch in Github Codespace.
Already working examples:

[x] basic
[x] column-ordering
[x] column-pinning
[x] column-sizing
[x] column-visibility
[x] expanding
[x] filters
[x] fully-controlled
[ ] grouping
[x] pagination
[x] row-selection
[x] sorting

Files that need to be modified for examples to work:

[x] core.tsx
[x] features/ColumnSizing.ts
[x] features/Expanding.ts
[x] features/Filters.ts (no change needed)
[ ] features/Grouping.ts
[ ] features/Headers.ts
[x] features/Ordering.ts (no change needed)
[x] features/Pagination.ts (no change needed)
[x] features/Pinning.ts (no change needed)
[x] features/RowSelection.ts (no change needed)
[x] features/Sorting.ts
[x] features/Visibility.ts (no change needed)

e.persist call is only available in React that comes from SyntheticEvent. So, I checked it first before calling it.

Closed in favor of #3798 and a separate PR that focus on removing or isolating React only types and logic  from the core.


simplescreenrecorder: 0.3.11 -> 0.4.2

Motivation for this change
https://github.com/MaartenBaert/ssr/releases/tag/0.4.2
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 102362 run on x86_64-linux 1

1 package built:

simplescreenrecorder

Result of nixpkgs-review pr 102362 run on x86_64-linux 1

1 package built:

simplescreenrecorder

Any news?

Result of nixpkgs-review pr 102362 run on x86_64-linux 1

1 package built:

simplescreenrecorder

gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.


add more seatbelts for electron

enforce bitcoin or zcash type as an RPC param

r? @chrisnojima

r? @patrickxb
cc: @chrisnojima

Cool

C/I failure due to windows clock-skew gregor bug :(


Stiff transition when using position absolute with transform

Hi,
I want to use Skrollr on absolute positioned elements in combination with transform. I basically want to create some kind of parallax.
However, absolute positioned elements and transform doesn't seem to match, see example, it behaves really stiff.
Is there any way to make this behave more fluid?
Update: Safari performance is stiff, Chrome doesn't even move the elements at all.

All numeric values have to have the same unit, even 0 needs a unit. It's not possible to animate from 5% to 100px. skrollr won't complain, but results are undefined.

https://github.com/Prinzhorn/skrollr#limitations

@Prinzhorn That does the trick, thanks!


CRAM support feasibility

An initial quick hack seems to imply that CRAM support might be quite easy to add. The only difficult bit is probably ensuring that the required references are present, and telling htslib where to find them. We will need to support CRAM at some point, so it would be good to do a quick feasibility analysis to see what we would need to do.
@andrewjesaitis or @dcolligan, would either of you like to take a look at this? The CRAM data from 1000 Genomes mapped to GRCh38 seems like a good place to start, e.g.,
ftp://ftp.1000genomes.ebi.ac.uk/vol1/ftp/technical/method_development/cram/lossy-bins-no-BQ-tag/HG01242
If it works out OK, we'd like to add support for CRAM to the server and update the download_data script to include some CRAM data and the corresponding reference information. Updating the headers to point to the new reference subset will be essential I think.

Sure. I can take a look at supporting CRAM. I imagine it will be pretty similar to BAM files, just reading via htslib?

If you run into any trouble supporting CRAM using pysam, please reach out
to Andreas and me.  We're happy to rapidly address any problems that you
may find.
On Fri, Feb 12, 2016 at 10:05 AM, Andrew Jesaitis<EMAIL_ADDRESS>wrote:

Sure. I can take a look at supporting CRAM. I imagine it will be pretty
similar to BAM files, just reading via htslib?
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/server/issues/928#issuecomment-183414706.

Thanks @andrewjesaitis, that would be great. My initial playing with it suggests that nearly everything should 'just-work' by adding '*.cram' to the file lists when creating a HtslibReadGroupSet, but there were a few quirks.
Thanks @bioinformed, we'll keep you posted if we hit any issues.

So I got this hacked in this morning. Turned out to be really simple, just had to make the server look for the cram files and make sure that pysam opens them with the c flag.
I do get an AssertionError from the pagination code, that I think has to do with unmapped read handling. This occurred when I started querying over explicit genomic ranges.
By far the biggest difficulty was getting the data set up correctly. I'm sure some of this is my inexperience with cram files, but it seems that due to the querying and caching that htslib is doing under the hood the CRAM headers are extremely fragile. This posed a bit of a problem since the server expects the reference to be broken into a fasta per chromosome and the 1kg reads data was aligned against a single fasta (hs37d5.fa). Since I was only using reads on chr20,  I subsetted the fasta to the single chromosome and I needed to update the header to point at the subsetted fasta. I couldn't modify the header in a way that samtools would accept. Eventually, I gave up and realigned the reads against my single chromosome fasta. After converting this BAM to CRAM, I was able to place it in the the datarepo and get things working.
Also, it's good to note that the cram files in the 1kg directory linked above were unreadable by htslib/pysam. I get a ValueError: file header is empty (mode='rc') - is it SAM/BAM format? when I try to read them. Ultimately I just grabbed a BAM and converted it to CRAM using samtools. I also tested converting using the cramtools and that worked too.

Excellent, thanks @andrewjesaitis. OK, so I think a pre-requisite for CRAM support will be allowing references be stored in single FASTA files.  I've opened issue #955 for this.
It would be good to know why the above CRAMs were unreadable in pysam. Would you mind digging into this a little bit more, and maybe opening an issue upstream if the problem persists? Converting to BAM and back won't really be an option if we want to deploy on the entire 1kg dataset!

Turned out to be really simple, just had to […] make sure that pysam opens them with the c flag.

When opening for reading with plain "r", the underlying HTSlib auto-detects SAM/BAM/CRAM,¹ so you shouldn't have needed to do this part.  IMHO this is a pysam bug: its read mode auto-detection has not been updated for HTSlib auto-detection, and to my mind it doesn't need the highlighted lines.
Or with the existing pysam, you should be able to get HTSlib'a auto-detection and not need to check the file extension just by writing mode explicitly: return pysam.AlignmentFile(dataFile, 'r').
¹ Or VCF/BCF if you're opening a variants file, etc

I agree it would be nice to know a bit more about why CRAM support was failing in conditions other than having to provide an alternative reference file.  @AndreasHeger is preparing the next pysam release, so any details would be very timely.

The lines that @jmarshall identified can definitely go, they were used to auto-detect SAM or BAM in early versions of samtools. Will do this before the - very imminent - release.

Just tried reading a cram with various flags using pysam 0.8.4. Seemed that only 'rc' worked. With no flag, 'r', and 'rb' I get a ValueError: fetch called on bamfile without index.
Currently are opening bam files right now without passing a flag, but if it auto-detected using just a 'r' flag that would be sufficient. I don't see a case were we are writing back to the bam file, is that right @jeromekelleher?
I think the deal with those 1kg files are that they simply don't have a header. Since the @SQ lines are so central to CRAM format, I think this is really an issue with how those files were generated. I'm not sure how widespread the issue is. The files I looked at were:
HG01242.chrom11.ILLUMINA.bwa.PUR.exome.20111114_lossy-bins-no-BQ-tags.bam.cram
HG01242.chrom11.ILLUMINA.bwa.PUR.exome.20111114_lossy-bins-no-BQ-tags.bam.cram
from:
ftp://ftp.1000genomes.ebi.ac.uk/vol1/ftp/technical/method_development/cram/lossy-bins-no-BQ-tag/HG01242

Currently are opening bam files right now without passing a flag, but if it auto-detected using just a 'r' flag that would be sufficient. I don't see a case were we are writing back to the bam file, is that right @jeromekelleher?

Yep, we have no intention of writing to the BAM/CRAM files ever as far as I can tell.


Multiple allocation queues create too many SLURM jobs

In the current setup multiple allocation queues are used (at least two - one to determine the model names and one for each model). It seems like whenever HQ decides to add a new allocation to meet the current demand, all allocation queues create a new SLURM job. The result is that more SLURM jobs/HQ workers are created than necessary.
It might be best to have one shared allocation queue for all models to avoid wasting resources.

Low priority at the moment, but would be nice to fix in the future for better performance.

Should be enough to only start hyperqueue and allocation queue once at load balancer start, right?


any open open source group channels?

Hi,
I tried to signup via https://ironfunctions.slack.com/signup but since I don't have a samsung or iron account I wasn't allowed in.  Is this an open source project or something else?  If we're open source why not use an open forum platform like IRC?
Respectfully , JN

John!  It should definitely be an open Slack channel and I'm trying to figure out how to make it open as we speak :)


Timepicker in 24h mode not working correct

When the timepicker works in 24h mode, clicking on "00h" correctly puts "00:00" in the input box, but in the upper field of the widget where the complete time is, there is (not correct) "12:00". Clicking on "12h" correctly puts "12:00" in the input box, and in the upper field of the widget where the complete time is, there is also (correctly) "12:00".
edit:
Actually, inner circle in 24h mode have to start with "12", not with "00", and outer circle have to start with "00"!

I fix this problem.

In gijgo.js change (line: 15934)
// update the numbers visualHour = (data.mode === 'ampm' && hour > 12 ? hour - 12 : (hour == 0 ? 12 : hour));
to
// update the numbers visualHour = (data.mode === 'ampm' && hour > 12 ? hour - 12 : (hour));
To lead zero need update (line: 15948)
$header.find('[role="hour"]').text(visualHour);
to
$header.find('[role="hour"]').text(parseInt(visualHour) < 10 ? "0" + visualHour: visualHour);
I was create fixed.min.js file if some one needed https://drive.google.com/file/d/1oJO0ZwoECW4GJBM5sJYPlwQRKEHe1aLr/view?usp=sharing


docs: add configure StorageGRID collector section

https://netapp.github.io/harvest/configure-storagegrid/

Hi @cgrinds, just wanted to let you know this is something that a lot of customers would appreciate, including me. :)
Regards
Erik

Looks great so far @cgrinds! Are there any plans on documenting how to do that on NAbox? I managed to get it working on NAbox but I think it is a different way to do it there compared to just Harvest.

@ybizeul can you include these steps to NAbox's documentation?

See nabox release notes StorageGRID dashboards and initial support for adding clusters is available as of v3.3b1


image.image_gradients error "Duplicate node name in graph: 'stack'"

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10.0.17134
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v2.0.0-rc2-26-g64c3d382ca 2.0.0
Python version: 3.7.7
CUDA/cuDNN version: Running on CPU
GPU model and memory:
Exact command to reproduce:

Describe the problem
When trying to use tf.image.image_gradients, get an error: "ValueError: Duplicate node name in graph: 'stack'", when trying to predict the model.
Source code / logs
The source code can be found below:
from tensorflow import image
from tensorflow.keras import layers, Model
import tensorflow as tf
from tensorflow.keras import backend as K
import numpy as np

myInput = layers.Input(shape=(4, 4, 1))

[deltaP_t_i, deltaP_t_j] = image.image_gradients(myInput[:, :, :, 0:1])
loss_grad = tf.norm(deltaP_t_i, axis=(1, 2)) + tf.norm(deltaP_t_i, axis=(1, 2))
loss_grad = K.mean(loss_grad, axis=-1)

myModel = Model(inputs=[myInput], outputs=[loss_grad])

x = np.array([[1, 2, 3, 4],
                [5, 6, 7, 8.1],
                [9, 10, 11, 12],
                [13, 14, 15, 16]])

x = np.reshape(x, (1, 4, 4, 1))

out1 = myModel.predict([x])

and the output is below:
2020-04-27 18:50:11.221070: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
Traceback (most recent call last):
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\ops.py", line 1610, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Duplicate node name in graph: 'stack'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:/test/TestPhysicalLossToReport.py", line 9, in <module>
    [deltaP_t_i, deltaP_t_j] = image.image_gradients(myInput[:, :, :, 0:1])
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\ops\image_ops_impl.py", line 3456, in image_gradients
    shape = array_ops.stack([batch_size, height, 1, depth])
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\util\dispatch.py", line 180, in wrapper
    return target(*args, **kwargs)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\ops\array_ops.py", line 1165, in stack
    return gen_array_ops.pack(values, axis=axis, name=name)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\ops\gen_array_ops.py", line 6303, in pack
    "Pack", values=values, axis=axis, name=name)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\op_def_library.py", line 793, in _apply_op_helper
    op_def=op_def)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\func_graph.py", line 548, in create_op
    compute_device)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\ops.py", line 3429, in _create_op_internal
    op_def=op_def)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\ops.py", line 1773, in __init__
    control_input_ops)
  File "C:\Users\emiliocoutinho\AppData\Local\Continuum\anaconda3\lib\site-packages\tensorflow_core\python\framework\ops.py", line 1613, in _create_c_op
    raise ValueError(str(e))
ValueError: Duplicate node name in graph: 'stack'

Process finished with exit code 1

@emiliocoutinho
i ran the code shared by you and there is no error faced, please find the gist here
please refer to these links with similar error:
link1
link2
link3

@Saduf2019, thanks for this feedback. Using the tf-nightly version works fine. I was previously using TensorFlow 2.0.0. This problem also happens with version 2.1. With the nightly version, works.


Add support for choosing the endpoint over fcgi

The recently added support for fcgi socket in #23 is very nice but forcing /status is really not ideal for us, this adds support for choosing the endpoint. With this you can basically keep the old config (assuming your nginx was using the same url as pm.status_path) and add --fastcgi:
$ php-fpm-exporter --addr="<IP_ADDRESS>:8080" --endpoint="http://<IP_ADDRESS>:9000/-/php-status?text" --fastcgi="tcp://<IP_ADDRESS>:9000"
I had to clean the vendor folder as a followup to #29 because it doesn't get populated properly on a non clean environment, it should only exist in the docker build container.

Thanks for the submission!  There's a lot going on here, so it may take me a bit to review it.  Looks good overall at first glance, though.

@Meroje please take a look at https://github.com/bakins/php-fpm-exporter/pull/35/files which is a different approach but requires fewer changes to code.
I cleaned up the modules in https://github.com/bakins/php-fpm-exporter/pull/34
As no one has volunteered to take over ownership, I'm planning a major reorg of the code, so I don't want to inject more changes than needed right now.

As no one has volunteered to take over ownership, I'm planning a major reorg of the code, so I don't want to inject more changes than needed right now.
Fine with me, please let me know if there are chores/issues you need help/time with.

This has gone stale and we switched to another exporter in the meantime, I'm going to close this but feel free to take over.

This has gone stale and we switched to another exporter in the meantime, I'm going to close this but feel free to take over.


refactor: use undici fetch instead of axios and got

Please describe the changes this PR makes and why it should be merged:
Prepare for releas of fetch in node 18.0, also descrease package size.
Package
create-discordx

why? I see no reason why we should change this. we will move to the built in fetch when we move to Node 18...

undici size is 802 kB, axios size is 398 kB
Since everyone will need time to use nodejs 18, it isn't time to move on yet. Sorry, but I need more reasons to choose undici over axios.

Yes, indeed, that is a bad argument. But you use two libs in this package instead of one, together they weigh almost as much as undici.
My main idea with this PR is that you don't need to rewrite the requests in the future, just remove the unnecessary import and delete the package. If this is not an argument for you, then close my PR.

your point for two http library is solid, I should use axios stream instead and remove got.

undici size is 802 kB, axios size is 398 kB
Since everyone will need time to use nodejs 18, it isn't time to move on yet. Sorry, but I need more reasons to choose undici over axios.

Yes, indeed, that is a bad argument. But you use two libs in this package instead of one, together they weigh almost as much as undici.
My main idea with this PR is that you don't need to rewrite the requests in the future, just remove the unnecessary import and delete the package. If this is not an argument for you, then close my PR.

can't we just use node-fetch instead? it's the closest relation to the fetch API

Alright, i figured out undici not really ready for production use, becuase it's creating some warning in console in runtime. Maybe it has point to replace it by node-fetch? because actually user api is the same, and when it will be ready for production we we'll just remove import and it will work.

Alright, i figured out undici not really ready for production use, becuase it's creating some warning in console in runtime. Maybe it has point to replace it by node-fetch? because actually user api is the same, and when it will be ready for production we we'll just remove import and it will work.

ideally, and correct me if i am wrong, we can just use node-fetch and when we move to 18, we can just change the import and everything should work as is because it all confirms to the fetch interface. it is also fully ESM compliant

Alright, i figured out undici not really ready for production use, becuase it's creating some warning in console in runtime. Maybe it has point to replace it by node-fetch? because actually user api is the same, and when it will be ready for production we we'll just remove import and it will work.

ideally, and correct me if i am wrong, we can just use node-fetch and when we move to 18, we can just change the import and everything should work as is because it all confirms to the fetch interface. it is also fully ESM compliant

Yea, that's what i described. I can done it in the same PR, if harry accept it.

see https://github.com/oceanroleplay/discord.ts/commit/0215090afafb357323ea05a684eec69d433f8999
removed got and now we are just using axios

However, the package size increase from 29.7 kB to 30.5 kB, probably axios is not lightweight like got

just occurred to me that, package size does not matter, dependencies does.
axios unpack size is 398 kB and got is 245 kB

my final call is https://github.com/oceanroleplay/discord.ts/commit/ae1b19699f0c8757f8354dc0dc948caafab8fd20
where compare to undici, axios final size is 398 kB+26.6 kB and undici is 802 kB. So I am choosing axios for now. removing got will improve overall installation by ~1mb, since got had so many deps.
Close this PR if there are no more arguments to discuss. Thank you for spotting this improvement.

my final call is ae1b196
where compare to undici, axios final size is 398 kB+26.6 kB and undici is 802 kB. So I am choosing axios for now. removing got will improve overall installation by ~1mb, since got had so many deps.
Close this PR if there are no more arguments to discuss. Thank you for spotting this improvement.

i feel @Satont did not make this PR because of filesizes, but rather to facilitate the ease of migrating to the fetch api when we move to node 18.
Filesizes should not be high due to tree-shaking anyway

my final call is ae1b196
where compare to undici, axios final size is 398 kB+26.6 kB and undici is 802 kB. So I am choosing axios for now. removing got will improve overall installation by ~1mb, since got had so many deps.
Close this PR if there are no more arguments to discuss. Thank you for spotting this improvement.

i feel @Satont did not make this PR because of filesizes, but rather to facilitate the ease of migrating to the fetch api when we move to node 18.
Filesizes should not be high due to tree-shaking anyway

True.


feat(eslint): update dependencies Fix package integrity issues in package-lock.json

This commit updates the dependencies in the project to ensure compatibility and security.
The following packages have been updated:

[List the updated packages and their new versions]

These updates address potential vulnerabilities and improve the overall stability of the project.

This commit updates the following packages to address potential vulnerabilities and improve overall stability:

Package1: v1.0.0 -> v1.1.0
Package2: v2.3.4 -> v2.4.0

Please review the changes and let me know if there are any concerns.

This commit updates the following packages to address potential vulnerabilities and improve overall stability:
Package1: v1.0.0 -> v1.1.0
Package2: v2.3.4 -> v2.4.0
Please review the changes and let me know if there are any concerns.


Added authorization for uploading extensions.

Fixes #25.
Specify an Upload.SecretKey property in appsettings.json to require authorization, then specify that secret key using the Bearer scheme in the Authorization HTTP header. For example:
{
   "Upload": {
        "SecretKey": "abcdefghij"
    }
}

curl --location --request POST 'https://localhost:5001/api/upload' \
--header 'Authorization: Bearer abcdefghij' \
--form '=@"/D://my-extension.vsix"'

Sweet


chore(release): also call make generate to update files

This allows us to also generate the README.md files automatically so that they contain correct references

What this PR does / why we need it
Which issue(s) this PR fixes

#990

I don't like this idea. All PRs should generate content. This potentially will leave a dirty branch or a dirty main that people don't expect. It could potentially could leave a branch with data that the developers are unaware of and had not committed or created.
I know that it's only generated data, nevertheless it's unexpected code that we potentially are unaware off. I don't like just plain committing generated code into the release especially if we had guards against merging prs that have ungenerated modifications in them.

For now, this is fine though. I realise that there are no other options in this case since the current automation will use the version as a stage point.
We'll figure something out. :D

Ill create a follow up because you still have a point. We need to make sure this generation doesnt fall on our face.


set block urgent before event starts

itt will be in urgent state until event ends

Thanks for the PR


Css file not found in node_modules

Hello Jacobs63,
Nice plugin thank you, but did you forget to upload the css file in the node_modules package? because I don't see it there, and yet its present  in this github repo under ./docs/resources/
Thank you for your reply

Hello,
CSS is not part of the package, as it is undesired - most CSS frameworks include tabs.
The docs are just an example implementation - you're free to copy the styles from the css file in the repository if you'd like to.
It will not be a part of the published package, as the package is not dependent on the demo, but vice-versa.


Add a field for setting a wiki-wide image file extension default

PNG is a nice standard to host across a whole wiki. We use JPG because that was what was practically available at the time the wiki started, but in recent times we've been trying to cover most of the wiki in PNG (and certainly all new content).
Rather than being stuck with...
Cover Art File Extension: png
Default Track Art File Extension: png

...duplicated across a growing volume of albums — all albums on custom wikis which use PNG from the get-go — we should add a new field to Wiki Info to set the default across the whole wiki. Something like Default Image File Extension!
It might take some infrastructure to work out how to display this in objects' own file extension properties or else fall back to in generateImage (which is probably the much cleaner solution).

As the last paragraph above notes, there's some trouble about making a global value stored in wikiInfo be inherited inside any usage of fileExtension (#composite/wiki-properties) — it's doable, but would require all Thing classes which use fileExtension to be supplied with a reference to wikiInfo. Maybe that's something we want to do later on, but at the moment it's a sort of awkward change for this feature alone.
But this is doable with the other suggested approach; since the issue was made, we've added and established a sprawl step (for content functions) that's often used to extract "feature" flags and other info from wikiInfo. We can use that to snag the default file extension in image (as it suggests) and use that as the default, when not specified on the data object. (fileExtension would compute as null when not specified, instead of 'jpg'.)
While we can implement this anytime, actually making use of it on HSMusic will involve either a lot of manual work or custom tooling to perform automatic YAML edits, which is still a ways off.


Forms Functionality: Be able to view forms and submissions

It was suggested in Issue #6 and I have added a new command and one subcommand to netlifyctl: $ netlifyctl form.
Running the forms command will list out every form a user has access to with the following fields: form name, form id, site id, and number of submissions.
As well, you can view basic details of form submissions as follows:
$ netlify form submissions --form-id <form-id string>

That will return a list of the submission timestamp, name, and body.

This is great @lannonbr! Thanks a lot.

I'm merging this, but I'm going to wait a few days to do a release, although the command should be available via go get before that.


[Loc] update to langpack source files for 2-22-2024

Will be port requested into release 1.48 once merged into main branch.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.001%) to 41.758%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.03%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
30828

Relevant Lines:
69082

💛  - Coveralls


Fix #10: Correctly count SASS/SCSS files in all dirs

Walks the directories counting only SASS/SCSS files

Hey, @melloware .
Thanks again for this contribution. I've rebased it and pushed the branch issue-15 to the repo. There are some edge cases that I could cover in the issue-15 branch (see fix commits) but others are still there related mainly to the lowercasing of the path, which may include false positives in the count in case-sensitive filesystems.
I'll check those later.

Hey, @melloware . I've gone ahead and tested the Dart Sass distribution available here and I see that the sass script doesn't compile one file ending in .SCSS unless I use one-to-one mode, which is not the mode used by this plugin. Can you please clarify which case would be covered by lowercasing the file names?

Nice work!  My thought was that .SASS and .sass and .Sass are all identical.   So if you only check for .sass you will be incorrectly counting files without lowercasing first.

Or ".CSS" ".cSs" etc.   Feels more bulletproof to lowercase before counting.

Did you check if the count logged by the plugin matches the actual processed file count in those cases (files ending with . SASS, Sass, etc) after the changes introduced by DS10 branch in your fork?

Let me give it a shot with your branch changes and I will let you know. I run on Windows and Linux but not MacOS so not sure if each OS will be different.

Oh! I must clarify that in this previous comment I used a Windows 11 VM running in Parallels Desktop to try to reproduce case-insensitive. :)
Also, the Dart Sass source code doesn't indicate that it will process allowed files regardless of the file extension case.

Ahh ok then feel free to pull the lowercase step if you have verified already!

@cleydyr Great work on this plugin. I have been using the other Ruby Sass plugin for years and I was about to sit down and write this exact plugin so I am glad I found yours!

Fixed in master. See https://github.com/cleydyr/dart-sass-maven-plugin/compare/49bf024...54c1a91

you rock!


fms 2022.02

FMS 2022.02 was released a few days ago ... need to add to spack package, test and make default if ok. Needs an additional cmake flag -DCONSTANTS=[GFS|...] (or something like that).

Well, a few weeks later and FMS 2022.03 was released, which includes the mixed-mode code that's needed for the UFS going forward. Here is the corresponding PR to the authoritative spack repo: https://github.com/spack/spack/pull/31901

This was addressed in a previous PR that updated our spack fork from the authoritative repository.


fix: update perception pipeline node diagram

Description

Update node_diagram as pipeline is update at https://github.com/autowarefoundation/autoware.universe/pull/7390 to solve the issue https://github.com/autowarefoundation/autoware.universe/issues/6785

Default perception/object_recognitioin pipeline after change:
(Orange node: added node)

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Hey, since it is possible for you to push something with pull requests here, would it be possible to at least move the groups from this pull request (https://github.com/autowarefoundation/autoware-documentation/pull/558) behind the elements of the groups itselfe (lidar sensing pipeline-, gnss sensing pipeline-, imu sensing pipeline- and parking-group)? [That's only work of a few minutes.]
If you did that, I would close my pull request, since it's probably not possible to merge that anyways...
I would highly appreciate that, so thanks a lot and have a nice day!


loading and unloading of specific cogs

I have added a reload cog feature to make use of the modularity that cogs provide. Basically one can make a change to a specific cog and then run the reload command to update the cog - without restarting the server.


Apparent type of unknown when strictNullChecks=false causes odd errors on property access

When strictNullChecks is disabled (as in JS code), destructuring a variable of type unknown produces the message:
Property 'foo' does not exist on type '{}'.(2339)

Whereas with it enabled, the error is:
Property 'foo' does not exist on type 'unknown'.(2339)

This behavior isn't actually tested anywhere, and was revealed in #47442.
When assigning unknown to a variable of some class type with properties, a similar error is produced:
Property 'prop' is missing in type '{}' but required in type 'A'.(2741)

Whereas strictNullChecks = true produces a more obvious error:
Type 'unknown' is not assignable to type 'A'.(2322)

This behavior (and other errors like it) is actually captured in a few tests.
This all seems to stem from the fact that getApparentType returns the empty object type as unknown's apparent type, which was added in #30637.
I would personally argue that the latter errors in the above examples make more sense than referring to {}, which doesn't actually appear in the code anywhere. Right now, this doesn't seem to be very visible (as people in JS are unlikely to see unknown), but with #47383 / #47442, this may become more visible.
const { foo } = {} as unknown;

function func({ foo }: unknown) {}

try {} catch ({ foo }) {}

class A {
    prop: number;
}

const a: A = {} as unknown;

Playground Link
Split off from https://github.com/microsoft/TypeScript/pull/47442#discussion_r785197785.

Now that I think a bit harder, this message won't show up in JS without checkJs, so maybe this isn't a huge deal after all, but it is a little awkward if anyones's running with strictNullChecks off.


'python3 toolchain.py build ffpyplayer' problem

###Versions

Python: python3 --version = 3.7.4
python --version = 2.7.10
OS: MacOs Mojave 10.14.4
Kivy: 1.11.1
installation method: pip3 install Kivy + python3 toolchain.py build python3 Kivy

my toolchain
Falks-iMac:~ falk$ cd kivy-ios
Falks-iMac:kivy-ios falk$ python3 toolchain.py status
toolchain.py:93: DeprecationWarning: ChromeDownloader style of invoking requests is deprecated. Use newer urlopen functions/methods
urlretrieve = ChromeDownloader().retrieve
audiostream  - Build OK (built at 2019-11-09 21:27:13.260709)
click        - Build OK (built at 2019-11-09 21:28:22.982370)
curly        - Not built
cymunk       - Not built
distribute   - Not built
ffmpeg       - Build OK (built at 2019-11-09 21:02:29.583414)
ffpyplayer   - Not built
flask        - Not built
freetype     - Build OK (built at 2019-11-09 18:07:43.773924)
host_setuptools - Not built
host_setuptools3 - Build OK (built at 2019-11-11 12:44:47.418326)
hostlibffi   - Not built
hostpython2  - Not built
hostpython3  - Build OK (built at 2019-11-09 18:30:40.252835)
ios          - Build OK (built at 2019-11-09 18:43:24.265093)
itsdangerous - Not built
jinja2       - Not built
kivent_core  - Build OK (built at 2019-11-09 23:10:21.945605)
kivy         - Build OK (built at 2019-11-09 18:56:42.312733)
libcurl      - Not built
libffi       - Build OK (built at 2019-11-09 18:20:18.488037)
libjpeg      - Build OK (built at 2019-11-09 21:16:05.597112)
libpng       - Not built
libzbar      - Not built
markupsafe   - Not built
numpy        - Not built
openssl      - Build OK (built at 2019-11-09 18:23:28.751778)
photolibrary - Not built
pil          - Not built
pillow       - Not built
pkgresources - Not built
plyer        - Build OK (built at 2019-11-09 21:26:02.872854)
pycrypto     - Not built
pykka        - Not built
pyobjus      - Build OK (built at 2019-11-09 18:44:55.299500)
python2      - Not built
python3      - Build OK (built at 2019-11-09 18:43:06.706068)
pyyaml       - Not built
sdl2         - Build OK (built at 2019-11-09 18:24:28.988308)
sdl2_image   - Build OK (built at 2019-11-09 18:31:40.260753)
sdl2_mixer   - Build OK (built at 2019-11-09 18:32:52.635991)
sdl2_ttf     - Build OK (built at 2019-11-09 18:33:09.353221)
werkzeug     - Not built
zbarlight    - Not built
Description
Hello I'm relative new with Kivy. When I try to build ffpyplayer I get this Log.
For useful answers thanks in advance. I try to answer so soon as possible (but I have to sleep sometimes(GMT+01) so sorry if I don't answer immediately).
With kind Regards Falk21 ...
Code and Logs
got an:
There was an error creating your Issue: body is too long (maximum is 65536 characters)
so just the last part:
[DEBUG   ] ffpyplayer/writer.pyx:569:17: Accessing Python attribute not allowed without gil
[DEBUG   ] 1: initwriter(void) -> initffpyplayer_writer(void)
[DEBUG   ] 2: PyInit_writer(void) -> PyInit_ffpyplayer_writer(void)
[DEBUG   ] 3: Pyx_NAMESTR("writer") -> Pyx_NAMESTR("ffpyplayer_writer")
[DEBUG   ] 4: "writer", -> "ffpyplayer_writer",
[DEBUG   ] ('rewrite', 'ffpyplayer/writer.c')
[INFO    ] Running Shell: /Users/falk/kivy-ios/dist/hostpython3/bin/python ('setup.py', 'build_ext', '-g') {'_env': {'CC': '/var/folders/p0/npxftvzd12sdrqt2sgbmrxkm0000gn/T/tmpt80w7vwr -I/Users/falk/kivy-ios/dist/include/x86_64/libffi', 'CXX': '/var/folders/p0/npxftvzd12sdrqt2sgbmrxkm0000gn/T/tmp20xlpxwd', 'AR': '/Users/falk/Downloads/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar', 'LD': '/Users/falk/Downloads/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld', 'OTHER_CFLAGS': '-I/Users/falk/kivy-ios/dist/include/x86_64/ffi -I/Users/falk/kivy-ios/dist/include/x86_64/openssl -I/Users/falk/kivy-ios/dist/include/x86_64/ffmpeg -I/Users/falk/kivy-ios/dist/include/x86_64', 'OTHER_LDFLAGS': '-L/Users/falk/kivy-ios/dist/lib', 'CFLAGS': '-O3 -miphoneos-version-min=8.0 -I/Users/falk/kivy-ios/dist/include/x86_64/ffi -I/Users/falk/kivy-ios/dist/include/x86_64/openssl -I/Users/falk/kivy-ios/dist/include/x86_64/ffmpeg -I/Users/falk/kivy-ios/dist/include/x86_64', 'LDFLAGS': '-arch x86_64 --sysroot /Users/falk/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator12.4.sdk -L/Users/falk/kivy-ios/dist/lib -lsqlite3 -miphoneos-version-min=8.0', 'KIVYIOSROOT': '/Users/falk/kivy-ios', 'IOSSDKROOT': '/Users/falk/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator12.4.sdk', 'LDSHARED': '/Users/falk/kivy-ios/tools/liblink', 'ARM_LD': '/Users/falk/Downloads/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld', 'ARCH': 'x86_64', 'SDL_INCLUDE_DIR': '/Users/falk/kivy-ios/dist/include/common/sdl2', 'FFMPEG_INCLUDE_DIR': '/Users/falk/kivy-ios/dist/include/x86_64/ffmpeg', 'CONFIG_POSTPROC': '0'}, '_iter': True, '_out_bufsize': 1, '_err_to_out': True}
[DEBUG   ]   File "setup.py", line 96
[DEBUG   ]     print 'Selecting %s out of (SDL, SDL2)' % sdl
[DEBUG   ]                                           ^
[DEBUG   ] SyntaxError: invalid syntax
Traceback (most recent call last):
File "toolchain.py", line 1568, in
ToolchainCL()
File "toolchain.py", line 1281, in init
getattr(self, args.command)()
File "toolchain.py", line 1322, in build
build_recipes(args.recipe, ctx)
File "toolchain.py", line 1158, in build_recipes
recipe.execute()
File "/Users/falk/kivy-ios/toolchain.py", line 729, in execute
self.build_all()
File "/Users/falk/kivy-ios/toolchain.py", line 84, in _cache_execution
f(self, *args, **kwargs)
File "/Users/falk/kivy-ios/toolchain.py", line 837, in build_all
self.build(arch)
File "/Users/falk/kivy-ios/toolchain.py", line 84, in _cache_execution
f(self, *args, **kwargs)
File "/Users/falk/kivy-ios/toolchain.py", line 811, in build
self.build_arch(arch)
File "/Users/falk/kivy-ios/toolchain.py", line 1112, in build_arch
_env=build_env)
File "/Users/falk/kivy-ios/toolchain.py", line 67, in shprint
for line in cmd:
File "tools/external/sh.py", line 565, in next
self.wait()
File "tools/external/sh.py", line 500, in wait
self.handle_command_exit_code(exit_code)
File "tools/external/sh.py", line 516, in handle_command_exit_code
raise exc(self.ran, self.process.stdout, self.process.stderr)
sh.ErrorReturnCode_1:
RAN: '/Users/falk/kivy-ios/dist/hostpython3/bin/python setup.py build_ext -g'
STDOUT:
File "setup.py", line 96
print 'Selecting %s out of (SDL, SDL2)' % sdl
^
SyntaxError: invalid syntax
STDERR:

Hi, this PR: https://github.com/kivy/kivy-ios/pull/403 should fix your issue. Let us know.
Also consider that it's more likely a kivy-ios issue than a kivy one :)

ffmpeg       - Build OK (built at 2019-11-24 17:02:53.021977)
ffpyplayer   - Build OK (built at 2019-11-24 19:58:52.403503)
sorry my fault, I will take this into consideration the next time;)
but for now, really big thank you for helping me, kind regards.


unencrypted http2 connections

Requires the service to support his.
Wait for https://github.com/OpenSlides/openslides3-autoupdate-service/pull/45

This project is closed


Prep for catapult release.

@jwngr PTAL?

One small comment. Back to you.

Change made and merged.  Thanks @jwngr!

:boar: looks good


XW-107: Search not working for subcategories

I looked at it, but there are repeating categories.

means? repeating categories?


Shap and interaction values differ with and without gpu

Shap and interaction values with and without gpu are different on xgboost.

@mahdi-ghelichi Can you post an example where this is the case?

from sklearn.datasets import load_iris
import xgboost as xgb
parameters = {"booster": "gbtree",
          "eval_metric": 'logloss',

          "eta": 0.5,

          "max_depth": 5,

          "nthread": 8,

          "objective": "binary:logistic",

          "seed": 42,

         "tree_method": "hist"}

if name=="main":
iris = load_iris()

data = iris['data']

label = iris['target']

label[label==2]=0

train = xgb.DMatrix(data=data, label=label)

model_no_gpu = xgb.train(parameters, train, num_boost_round=10)

shap_values_no_gpu = model_no_gpu.predict(train, pred_contribs=True, approx_contribs=True)

interactions_no_gpu = model_no_gpu.predict(train, pred_interactions=True)

parameters['tree_method'] = 'gpu_hist'

model_gpu = xgb.train(parameters, train, num_boost_round=10)

shap_values_gpu = model_gpu.predict(train, pred_contribs=True, approx_contribs=True)

interactions_gpu = model_gpu.predict(train, pred_interactions=True)

You will see that both shaps and interaction are different.

Which version of XGBoost are you using? GPU-enabled SHAP was introduced recently and is not part of 1.2.0 release.

It is 1.2.0 which is the latest.
So, it means till then we should not use shaps with gpu then.
Was wondering if we could get interactions with approx method? It returns all zero for other features when approx is True for interactions, except the diagonal. The approximation of interactions could speed things up.


Allow users to choice whether or not null keys should be dropped

Both Argonaut and Circe support dropping null keys from the JSON output. Althoguh, the current implementation of EncodeResponses from io.finch.argonaut._ and io.finch.circe._ is to keep nulls. What we can do is to provide an inner object dropNullKeys for both Argonaut and Circe that defines an implicit instance of EncodeResponse type class that actually drops null keys.

Given this question from @amartinsn, it might make sense to allow the user to provide a custom Printer (potentially for both Argonaut and circe).

Fixed by #456.


chore(messages.json): update translation messages

Update translation catalogs to accompany LDAP anonymous bind feature. (See DCOS-43815)
Testing
There should be no visual changes as a result of this PR.
Trade-offs
N/A.
Dependencies
This should be merged with mesosphere/dcos-ui-plugins-private#882

:tada: This PR is included in version 2.38.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: