Set the LANG when invoking cocoapods

Description
When invoked from the command line, this is fine, but when invoked from an IDE the $LANG env var isn't set by the IDE.  We could remove this is Coco
Related Issues
https://github.com/google/flutter-desktop-embedding/issues/586
https://github.com/CocoaPods/CocoaPods/issues/9347
Tests
I added the following tests:
Updated tests to expect this variable is set.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

Ok, so I tested this with:
cd examples/flutter_gallery
flutter clean
LANG= flutter run -d macos -v

But it didn't work... After some fiddling, I found that it has to be UTF-8 (note the dash) and that the first part needs to be en_GB and not en-GB (as given by Dart).
So this worked:
'${platform.localeName.replaceAll('-', '_')}.UTF-8'

I can't find any info on these formats (eg. why it needs to be an underscore there, yet Dart has a dash) 🤷♂

On macOS, the command line VM doesn't use LANG to compute Platform.localeName. See: https://github.com/dart-lang/sdk/blob/master/runtime/bin/platform_macos.cc#L190

Is there any chance that we just want to always force this to en_US.UTF-8?

Is there any chance that we just want to always force this to en_US.UTF-8?

🤷🏼♂
I'm not all that familiar with CocoaPods. I can't think of anything obvious it might do differently based on language, and if we used the existing env variable first and only set that if it wasn't already set, I think that limits the scope (and gives a way for people to force it back if required).

I'm not all that familiar with CocoaPods. I can't think of anything obvious it might do differently based on language, and if we used the existing env variable first and only set that if it wasn't already set, I think that limits the scope (and gives a way for people to force it back if required).

It's using https://docs.ruby-lang.org/en/2.1.0/Encoding.html to check for a Encoding::UTF_8 ("UTF-8") match.

I'll keep using the (massaged) platform encoding.  I'm just thinking the Podfile is always going to be en_US encoded.

Tested with the update and it seems to work fine, so LGTM once the tests pass (which seems to be because of a null for localeName somewhere).

That will probably resolve my test issue as well.  I'm going to do that for now.  We can fix it later if we determine that you ever want a non en_US locale for pod.

As long as this passes CI, going to look to land on red since it seems like it should fix the redness.

@dnfield Thanks! Tested this on master and it now works both from CLI and VS Code 👍


Number of Questions vs Number to Pass comparison is broken for double digit numbers

When a quiz has 10 or more questions, Number to Pass can be higher than Number of Questions if selecting 10 or more

:+1:


[emoji-picker] Store boost preferences per user in database [EMO-9]

I guess that this JsonPreference model is fairly similar to the concept of this gem: https://github.com/ledermann/rails-settings .


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^17.1.0 remove ^17.0.8 (devDependencies.semantic-release)

:tada: This PR is included in version 9.9.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add callbacks section to manual

Things I have yet to finish:

[x] Equation-specific callbacks like GlmSpeedCallback or LBMCollisionCallback
[x] References to example elixirs that showcase each callback
[x] Include an image like the one on slide 30 here to illustrate how callbacks work

I've added links to some example elixirs, however they currently point to the elixirs from the main branch. Therefore, if these elixirs are modified, the documentation for old versions might be broken. I did not find a workaround for this (except omitting the links altogether).

Thanks, this looks good to me +1
I see two possibilities how to handle hard-coding the names of the example files.
1. Hard-code the `main` branch and remember to change this part of the docs when the examples are updated (current approach).

2. Hard-code a specific version of Trixi, e.g. https://github.com/trixi-framework/Trixi.jl/blob/v0.3.13/examples/2d/elixir_advection_restart.jl.

The second possibility will ensure that the links remain valid, but they will not point to the latest versions. Hence, I think I prefer the current version.

Thanks for the analysis and the review! I agree - it is not perfect, but I'd also rather have links to the most up-to-date elixirs.

@lchristm Once you've applied the suggested changes, I will merge this PR.

Figure for the documentation:


Node driver stuck in downloading state when a new node driver is added pointing to an invalid download url

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Go to Driver page. Select Node Drivers.
Click on Add Node Driver.
Enter Download URL and Whitelist Domains
Click on Create.

Expected Result:
The driver must be created and should become Active
Actual Result:
The driver is created but is stuck in Downloading state
Note:
Also seen in 2.2.4-rc1, v2.1.10-rc1 and v2.0.15-rc1
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher: master
Installation option (single install/HA): single install

@sowmyav27 Could you also post information from logs?

Cannot reproduce, tried with images for 2.2.4-rc1, v2.1.10-rc1, v2.0.15-rc1. This behavior could happen if you attempt to download a driver for the wrong architecture but otherwise I'm not sure why this would happen with a valid driver. I'm testing with linode linux driver.

@deniseschannon @cjellick Reopening this issue.
The node driver is seen in Downloading state when provided with an invalid download URL (verified on master-head)
Error in logs:
2019/08/19 18:38:27 [INFO] Download x.x.x.x
2019/08/19 18:38:27 [ERROR] NodeDriverController nd-9mg7m [node-driver-controller] failed with : Get x.x.x.x: unsupported protocol scheme ""
2019/08/19 18:38:27 [ERROR] Returning previous error: Get x.x.x.x: unsupported protocol scheme ""

Do we need a fix in the UI to show the error message?

This is fine for now. I'm going to move this to unscheduled. I don't think we'll be addressing this anytime soon.


after insert into, be is closed every time

Steps to reproduce the behavior (Required)

create table tag_list(
idcard varchar(50) not null
)
ENGINE = olap
PRIMARY KEY(idcard)
DISTRIBUTED BY HASH(idcard) BUCKETS 32
PROPERTIES (
"replication_num" = "1"
);

// success
alter table tag_list ADD column tag1 varchar(200);
// success
alter table tag_list ADD column tag2 varchar(200);
// failed
alter table tag_list ADD column tag3 varchar(200);
the tip is "[42000][1064] tablet 4056758 has few replicas: 0", the tip show often

insert into tag_list(idcard, tag1) values ("001", "男性");
the tip is "[42000][1064] Execute timeout"，and after that be is closed

after i start the be, i run the sql "insert into tag_list(idcard, tag1) values ("001", "男性");", the same error occurs, and be closed
the be.info is below:
I1123 17:07:00.248281 29250 tablet_manager.cpp:739] Found the best tablet to compact. compaction_type=cumulative tablet_id=94722 highest_score=2
I1123 17:07:01.275981 29250 tablet_manager.cpp:739] Found the best tablet to compact. compaction_type=cumulative tablet_id=94720 highest_score=2
I1123 17:07:02.147642 29331 internal_service.cpp:242] exec plan fragment, fragment_instance_id=b8a8c6fc-4c3c-11ec-8238-0242661cf74d, coord=TNetworkAddress(hostname=<IP_ADDRESS>, port=9020), backend=0
I1123 17:07:02.147706 29331 plan_fragment_executor.cpp:67] Prepare(): query_id=b8a8c6fc-4c3c-11ec-8238-0242661cf74c fragment_instance_id=b8a8c6fc-4c3c-11ec-8238-0242661cf74d backend_num=0
I1123 17:07:02.148025 29331 plan_fragment_executor.cpp:126] Using query memory limit: 2.00 GB
I1123 17:07:02.148150 29331 exec_node.cpp:577] exec node: UNION_NODE, use vectorized:1
I1123 17:07:02.148363 29223 plan_fragment_executor.cpp:235] Open(): fragment_instance_id=b8a8c6fc-4c3c-11ec-8238-0242661cf74d
I1123 17:07:02.148948 29223 plan_fragment_executor.cpp:691] Fragment b8a8c6fc-4c3c-11ec-8238-0242661cf74d:(Active: 90.934us, non-child: 30.87%)

AverageThreadTokens: 0.00
MemoryLimit: 2.00 GB
PeakMemoryUsage: 32.00 KB
PeakReservation: 0
PeakUsedReservation: 0
RowsProduced: 1
BlockMgr:

BlockWritesOutstanding: 0
BlocksCreated: 0
BlocksRecycled: 0
BufferedPins: 0
BytesWritten: 0
MaxBlockSize: 8.00 MB
TotalBufferWaitTime: 0.000ns
TotalReadBlockTime: 0.000ns
DataBufferSender (dst_fragment_instance_id=b8a8c6fc-4c3c-11ec-8238-0242661cf74d):
AppendBatchTime: 13.710us

ResultRendTime: 1.497us
TupleConvertTime: 5.313us

NumSentRows: 1
UNION_NODE (id=0):(Active: 62.866us, non-child: 69.13%)
PeakMemoryUsage: 0
RowsReturned: 1
RowsReturnedRate: 15.91 K/sec
I1123 17:07:02.200824 29331 internal_service.cpp:242] exec plan fragment, fragment_instance_id=b8b0b640-4c3c-11ec-8238-0242661cf74d, coord=TNetworkAddress(hostname=<IP_ADDRESS>, port=9020), backend=0
I1123 17:07:02.200858 29331 plan_fragment_executor.cpp:67] Prepare(): query_id=b8b0b640-4c3c-11ec-8238-0242661cf74c fragment_instance_id=b8b0b640-4c3c-11ec-8238-0242661cf74d backend_num=0
I1123 17:07:02.200909 29331 plan_fragment_executor.cpp:126] Using query memory limit: 2.00 GB
I1123 17:07:02.200953 29331 exec_node.cpp:577] exec node: UNION_NODE, use vectorized:1
I1123 17:07:02.201341 29223 plan_fragment_executor.cpp:235] Open(): fragment_instance_id=b8b0b640-4c3c-11ec-8238-0242661cf74d
I1123 17:07:02.202054 29328 tablets_channel.cpp:60] Opening tablets channel=(id=b8b0b6404c3c11ec-82380242661cf74c,index_id=4056757) tablets num=32 timeout=300 vectorized=1
I1123 17:07:02.202484 29408 tablet_sink.cpp:1485] Exiting consumer thread, no running channel
F1123 17:07:02.202828 29306 column_aggregate_func.cpp:599] Check failed: false bad agg method NONE for column: tag1
I1123 17:07:02.308646 29250 tablet_manager.cpp:739] Found the best tablet to compact. compaction_type=cumulative tablet_id=94716 highest_score=2

StarRocks version (Required)
1.18.5

Primary Key is a test feature in StarRocks-1.18.5.
The problem has already fixed in 1.19.x
It's better to upgrade to 1.19.2 (https://github.com/StarRocks/starrocks/tree/1.19.2)


[CLI} - Should tell me what to do to upgrade to a new version

right now the CLI tells me there is a new version but doesn't tell me what to do to get to a new version:
Checking for newer versions of static_shock_cli...
New version of static_shock_cli is available: 0.1.0-dev.49 -> 0.0.1-dev.5

it should tell me, e.g.
Checking for newer versions of static_shock_cli...
New version of static_shock_cli is available: 0.1.0-dev.49 -> 0.0.1-dev.5
Run `shock upgrade` to upgrade to the latest version.

Done.


HSEARCH-2521 Clarify if error HSEARCH000278 could be caused by the entity not being a managed entity

https://hibernate.atlassian.net/browse/HSEARCH-2521

merged


(maint) Relax win32-dir

Allow bundler to install win32-dir 0.7.2 that contains the ASLR fix.
This change affects bundler and the runtime dependencies for the win32
specific versions of the puppet gem. It is important to continue accepting
win32-dir 0.4.9, because that is what we ship in the puppet-runtime.
Since win32-dir 0.7.2 only supports ruby 2.4 and up, this change drops the ruby
2.3 and windows rspec combination. Ruby 2.3 went EOL March 28, 2018.
The change to ruby-prof was due to bundler pulling in a a version that wasn't
compatible with older ruby versions. So restrict that to ruby >= 2.5. It's only
needed when running the memory related benchmarks.

I guess this is also happening because of ASLR, now when you're getting the object_id of an object_id(which is an integer), the values are stored at different address.
# before ASLR:
 > a = "123"

 > a.object_id.object_id
 => 25561
 > a.object_id.object_id
 => 25561

# with ASRL:
> a = "123"

> a.object_id.object_id
=><PHONE_NUMBER>340
> a.object_id.object_id
=><PHONE_NUMBER>220

Just a thought: I think the issue here manifests only on Ruby 2.5.9 provided by RubyInstaller. I found this on the MSYS2 homepage (which is used in RubyInstaller) and I think it might be the culprit. ASLR was enabled by default in MSYS2 at the end of January 2021, which means that all RubyInstaller builds that come after that date are impacted by this change. To outline, the issue is with the RubyInstaller MSI, not with the OS configuration, as we were also able to reproduce this internally.
Since all rubies 2.5 and older went EOL, we can probably assume that there won't be any new versions of those rubies, and no affected RubyInstaller ASLR MSIs. So we might get away with your change @joshcooper, and still keep Ruby 2.3 in the GH Actions matrix if we want. I assume that by relaxing the version, bundler on Ruby 2.3 will get the last win32-dir version with Ruby 2.3 support (it shouldn't matter if it contains the ASLR fix or not, as the RubyInstaller builds of Ruby 2.3 don't have ASLR on), and bundler on Ruby 2.4 and higher will get version 0.7.2 of the gem (which has the fix).


[Current] Agenda for 1st AllERCDevs Meetup 2023-05-16 UTC2300

Hi all, as per our time poll, we will have our first AllERCDevs Meetup on
2023-05-16 UTC 2300-2359 Tuesday, which translates to

19:00-19:59 on 2023-05-16 Tuesday in US Eastern Time.
07:00-07:59 on 2023-05-17 Wednesday in Singapore.
16:00-16:59 on 2023-05-16 Tuesday in US Pacific Time.

The event will be hosted on Zoom, a link will be posted on "all-erc-devs" channel on this Discord Server
Agenda will be updated and please feel free to comment to signup your agenda items.
Agenda
Main Session (1h)

(15-20min) Featured Talk:  How EIP program started and why it matters, by Hudson Jameson (@Souptacular)
(10min) Demo Show & Tell (5-10min per slot)

(5m) TurboEth by @kamescg
TODO add second demo

(30min) ERC Peer Review Requests (5-10min per slot)

(5-10m) ERC-6982 Efficient Default Lockable NFTs and EIP6454 by @sullof
(5-10m) ERC-7007 zkML AIGC NFTs by @ socathie
(5-10m) ERC-5269 ERC Discovery Interface by @xinbenlv

Social Hour (30m)

TODO decide social hour topics

Please feel free to signup the agenda slot by commenting Below.

Please add to the agenda for an intro to ERC-5453 Endorsement

I may talk about EIP6982 Efficient Default Lockable NFTs and EIP6454 which move in the same space, but with different targets in mind.

We would like to request to present for the peer review slot for EIP-7007 zkML AIGC NFTs.

We would like to request to present EIP-6900 in the peer review section.


$service-worker files exclusion improvements. Make it automatic and Configurable.

Is your feature request related to a problem? Please describe.
.gitkeep file available in assets/some-dir is available in $service-worker.files causing this file to be requested unnecessarily(and surprisingly).
Describe the solution you'd like
Here I see that only one file .DS_STORE is excluded from $service-worker.files. I would suggest the following

All hidden files might be excluded from here by default. There might be other hidden files like vim swap and swo files
An option to toggle the above flag using Svelte config file, just in case someone wants to have complete control.
A list of files/glob patterns to specify the list of files that you would want to be excluded. This exclusion can also be helpful when you have certain files present which you are not using currently anywhere. Those files probably exist because you are experimenting with something or maybe someone just forgot to remove the file but he removed the actual usage. One more reason can be Open Graph meta tags using an image that isn't used on the website directly but is served from the website when requested.

Describe alternatives you've considered
For the time being, I have excluded .gitkeep in service-worker.ts which works for me but increases service-worker.js file size unnecessarily.
How important is this feature to you?
This is not super important. But I would love to contribute if you can provide the next step here.
Additional context
It shows a .gitkeep file being requested from service-worker

Based off the discussion in https://github.com/sveltejs/sapper/pull/1095 I'm guessing that we might not want to ignore hidden files by default. But it sounds reasonable to provide an option that lets you filter which files are included / ignored

@benmccann Thanks for pointing me to the sapper issue. I searched for a similar issue in Sveltekit but couldn't find it there. I didn't think about looking into sapper issues.
I have done the changes not sure if I am in the right direction.

This is now configurable through the serviceWorker option, thanks for the PR!

Hello, just a little improvement request : on my Mac it's DS_Store and not DS_STORE  as in default kit config


vte-ng: 0.50.2.a -> 0.54.2.a

Motivation for this change
Made it possible to have undercurl working in my terminal (termite).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] 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)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build termite


GDScript Inheritance Breaks Exports w/Binary Resources

Godot version: 3.0.2-stable (custom build from 2ff3b08583766c975d76d8c39ba0937a5c9bf064)
OS/device including version: Gentoo Linux, Kernel 4.14.12, KDE 5, NVidia GTX 1080 with NVidia proprietary drivers 390.12
Issue description: Using the extends directive in GDScript to derive from another GDScript class will cause the Export feature to generate broken builds if converting resources to binary is enabled.
Although GDScript code gets packaged as bytecode, it appears that the path behind the extends directive gets stored verbatim. Thus, the export template executable will attempt to load the uncompiled, original GDScript source file (which is not present in the .pck file, of course).

Steps to reproduce:

Create a Godot project and add 2 GDScript (.gd) files to it
Make one GDScript class inherit the other: extends "res://Other.gd"
Use the derived GDScript class in an arbitrary scene that is included during export
Configure the project for binary export

Export and try to run the resulting build.

After investigating this further, it seems this issue is just a follow-up of another issue:
Resources referenced only in GDscript are not identified as build dependencies. So whether a script uses extends "res://some_other_script.gd" or preload("res://game_over.wav").
A possible workaround is to create a never-loaded scene that references all such resources like this:

Anyway, I believe this is a known issue, but I could find no other bug mentioning it (i.e. Issue Search: gdscript dependencies.


Option to see how long the task was waiting in the queue before being handled

Is there an option to see how long the task was waiting in the queue before being handled with the exporter metrics?

I don't think so, but if celery_queue_length is larger than 0 it's guaranteed to be put on hold.

Thanks for the quick answer :), there is a plan to add it in the future?
because I see [here], that they have done here something that can be relevant to that

Feel free to open a pull-request :-)

I need this too!
Are you working on this @matancarmeli7 ?


Don't start initial VMs on the server side.

Please do not merge.
Needs to go in with https://github.com/AppScale/appscale-tools/pull/547

Build: https://ocd.appscale.com:8080/job/Daily Build/2227/

Build: https://ocd.appscale.com:8080/job/Daily Build/2252/

Build: https://ocd.appscale.com:8080/job/Daily Build/2274/


failed to build with Visual Studio

fails with the following error:
         c:\.conan\oxrcs2xw\1\source_subfolder\include\sqlpp11\container\sort_order.h(53): error C2977: 'sqlpp::sort_order_t': too many template arguments [C:\.conan\oxrcs2xw\1\build_subfolder\source_subfolder\tests\SqlppStlSampleTest.vcxproj]
         c:\.conan\oxrcs2xw\1\source_subfolder\include\sqlpp11\container\sort_order.h(54): error C3203: 'sort_order_t': unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type [C:\.conan\oxrcs2xw\1\build_subfolder\source_subfolder\tests\SqlppStlSampleTest.vcxproj]
         c:\.conan\oxrcs2xw\1\source_subfolder\include\sqlpp11\container\sort_order.h(52): error C3211: 'sqlpp::interpreter_t<sqlpp::container::context_t,int,void>': explicit specialization is using partial specialization syntax, use template <> instead [C:\.conan\oxrcs2xw\1\build_subfolder\source_subfolder\tests\SqlppStlSampleTest.vcxproj]

Thanks for the hint.
This is rather experimental code that will only really come to fruition if and when there will be compile time reflection including construction like with Metaclasses. Thus it is not regularly tended.
I pushed change to develop that should make it compile again, though (at least it compiles on my machine using clang).

@rbock thanks for the update
it did the trick, just one more minor fix is needed for:
expression.h(88): error C2039: 'logical_and': is not a member of 'std'

adding the <functional> include, and it builds fine.
is it possible to make 0.5 release with these changes?

0.5 is tagged and pushed.
Thanks for looking into sqlpp11 in conan, btw., very much appreciated!


Canvas Drawing

I wish to transmit an image from the server to the front end and then draw a circle on the image where a user clicks on it.
My current solution is using a callback and to redraw the image on the server and re-transmit the image. This is very slow. Is there a better solution?

There are different possible solutions. Two possible solutions are:

Use Svg widgets to show the image and add other svg objects to draw geometrics;
Draw on the image with opencv and trigger an image refresh;

The best solution depends on the kind of project. What you want to do exactly?

Thank you for responding so quickly.
I want to display many images in a grid from a remote server to a consumer and draw circles on the all the images from where the user clicked. Here is a demo of what I have so far. I have been able to speed it up by using high JPEG compression but I suspect it will slow down much farther when I start to display many more images.
Sample.zip
I have already implemented back-end rendering using OpenCV and refresh but I would prefer to do it on the front end for lower latency. I might be rendering tens of images.
Could you provide more details or point to an example of how I could do your first suggestion? I was not able to find an example of how to show the image inside a svg widget and then draw on top.
Thank you.

Here is a really simple example made with the editor:
# -*- coding: utf-8 -*-

from remi.gui import *
from remi import gui
from remi import start, App

class untitled(App):
    def __init__(self, *args, **kwargs):
        #DON'T MAKE CHANGES HERE, THIS METHOD GETS OVERWRITTEN WHEN SAVING IN THE EDITOR
        if not 'editing_mode' in kwargs.keys():
            super(untitled, self).__init__(*args, static_file_path={'my_res':'./res/'})

    def idle(self):
        #idle function called every update cycle
        pass

    def main(self):
        return untitled.construct_ui(self)

    @staticmethod
    def construct_ui(self):
        #DON'T MAKE CHANGES HERE, THIS METHOD GETS OVERWRITTEN WHEN SAVING IN THE EDITOR
        vbox0 = VBox()
        vbox0.attr_class = "VBox"
        vbox0.attr_editor_newclass = False
        vbox0.css_align_items = "center"
        vbox0.css_display = "flex"
        vbox0.css_flex_direction = "column"
        vbox0.css_height = "540.0px"
        vbox0.css_justify_content = "space-around"
        vbox0.css_left = "20px"
        vbox0.css_position = "absolute"
        vbox0.css_top = "20px"
        vbox0.css_width = "645.0px"
        vbox0.variable_name = "vbox0"
        svg0 = Svg()
        svg0.attr_class = "Svg"
        svg0.attr_editor_newclass = False
        svg0.css_height = "450px"
        svg0.css_order = "124983688"
        svg0.css_position = "static"
        svg0.css_top = "20px"
        svg0.css_width = "450px"
        svg0.variable_name = "svg0"
        svgimage0 = gui.SvgImage('https://interactive-examples.mdn.mozilla.net/media/examples/grapefruit-slice-332-332.jpg')
        svgimage0.onmousedown.do(self.on_mousedown_svgimage)
        svgimage0.attr_class = "SvgImage"
        svgimage0.attr_editor_newclass = True
        svgimage0.attr_height = 225.0
        svgimage0.attr_width = 420.0
        svgimage0.attr_x = 15.0
        svgimage0.attr_y = 15.0

        svgimage0.variable_name = "svgimage0"
        svg0.append(svgimage0,'svgimage0')
        vbox0.append(svg0,'svg0')
        self.svg0 = svg0

        self.vbox0 = vbox0
        return self.vbox0

    def on_mousedown_svgimage(self, emitter, x, y):
        circle = gui.SvgCircle(x, y, 20)
        circle.set_fill('transparent')
        circle.set_stroke(1, 'black')
        self.svg0.append( circle )

#Configuration
configuration = {'config_multiple_instance': True, 'config_address': '<IP_ADDRESS>', 'config_start_browser': True, 'config_enable_file_cache': True, 'config_project_name': 'untitled', 'config_resourcepath': './res/', 'config_port': 8081}

if __name__ == "__main__":
    # start(MyApp,address='<IP_ADDRESS>', port=8081, multiple_instance=False,enable_file_cache=True, update_interval=0.1, start_browser=True)
    start(untitled, address=configuration['config_address'], port=configuration['config_port'],
                        multiple_instance=configuration['config_multiple_instance'],
                        enable_file_cache=configuration['config_enable_file_cache'],
                        start_browser=configuration['config_start_browser'])

Thank you @dddomodossola,
I have set the SvgImage object css_width and css_height to be 100% rather than in pixels. How can I get the current widget's height in pixels if the css is defined in percentage?
The function width_in_pixels() and height_in_pixels() are the parts that I am missing.

    x_percentage = x / emitter.width_in_pixels()
    y_percentage = y / emitter.height_in_pixels()

There are different possible solutions. Two possible solutions are:

Use Svg widgets to show the image and add other svg objects to draw geometrics;
Draw on the image with opencv and trigger an image refresh;

The best solution depends on the kind of project. What you want to do exactly?

Hi,i wish to dispaly my camera which is being processed by opencv but i don‘t know how to do it with remi.Could you provide more details or point to an example of how I could do your first suggestion?Thank you.

You can use the Editor. It contains opencv video widget.
Take a look at this https://www.youtube.com/watch?v=WqwWrETtLfU
In this example it is used an opencv image widget. You should instead use the Video.

You can use the Editor. It contains opencv video widget.

Thank you,it help me a lot.


fix: polling for app subscription delete

Purpose
This PR adds the missing polling in case of a delete (unsubscribe) for the resource subaccount_subscription
Does this introduce a breaking change?
[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?
[X] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code

go test ./...

What to Check
Verify that the following are valid

Tests succeed

Other Information
n/a

Test Coverage of new code below 80% (overall coverage estimated after merge 87.3%): missing coverage comes from error branches in destroy that cannot be easily triggered via plugin test framework afaik. As coverage is still above 85% after merge the merge of the PR should be acceptable


strings.Split traverse the string twice when split?

go 1.5.2 linux x86
in src/strings/strings.go genSplit
when n < 0, called by strings.Split n=-1
first count sep, traversed once
then do split, traversed once more, it sees low efficiency.
if we could estimate N, use strings.SplitN is ok, but if we couldn't get N ?

How could we estimate N without much
memory overhead?

I don't see an actionable bug report here, so closing.  If you want to discuss this, please use one of the forums; see https://golang.org/wiki/Questions .  Thanks.

use a slice with estimated N as a hint, but if there is more splits than N, the slice will automatic grow, this seems more reasonable?

The problem is how to estimate N. Too small an
estimate, and you will end up reallocate the slice
a few times and incur much bigger overhead, and
too big an estimate you will just waste memory.
The minimum and maximum is different enough that
I don't think we can estimate N accurately without
traversing the string once.
Anyway, if you think you can do better, perhaps
you should write an implementation that only
traverse the string once and do some benchmark
to show it's superior than the current implementation.
It's better than arguing here without any concrete
benchmark numbers.


esp32-devkitc:wamr_wasi_debug kconfig maintainance

Summary

disable too verbose wamr options.

enable CONFIG_SCHED_WAITPID. because async execution on nsh prompt sometimes confuses me.

enable toywasm. it's sometimes convenient to have another interpreter.
note: wasm3 in nuttx apps doesn't have wasi enabled.

Impact
Testing
tested on esp32-devkitc, with https://github.com/apache/nuttx-apps/pull/1442
nsh> mount -t littlefs /dev/esp32flash /mnt
nsh> iwasm /mnt/test.wasm
hello
nsh> toywasm --wasi /mnt/test.wasm
hello
nsh>

a fix for the ci failure: https://github.com/apache/nuttx-apps/pull/1443


Improve CSV schema validation with filename patterns

This commit introduces filename pattern validation to the CSV schema, which allows increased data consistency checks. It also extends the capability to include additional columns to the schema, providing a more flexible structure. Enhancements were also made to error handling, introducing a quick-stop feature to expedite error discovery.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

19 of 21 (90.48%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 95.364%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Csv/CsvFile.php
18
20
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
576

Relevant Lines:
604

💛  - Coveralls


Build fails as remote theme

Hi, excellent theme that I've used successfully in the past (using local Gems build), but I'm trying to get it to work simply as a remote_theme. I have a repo with only a README and a _config.yml that fails to build.
Environment

remote theme version: remote_theme:  mmistakes/minimal-mistakes
Git repository URL: https://github.com/thedukeoflemington/thedukeoflemington.github.io
GitHub Pages hosted (if yes provide URL to site): https://thedukeoflemington.github.io

Expected behavior
Builds without errors :)
Steps to reproduce the behavior
I have a repo with only a README and a _config.yml that fails to build.
GitHub Pages failed to build your site.
The tag include_cached on line 15 in /_layouts/default.html is not a recognized Liquid tag.

See this note in the README and documentation:

Note: The theme uses the jekyll-include-cache plugin which will need to be installed in your Gemfile and added to the plugins array of _config.yml. Otherwise you'll throw Unknown tag 'include_cached' errors at build.


Better data source tagging

Improved the data source handling:

new simple data source schema (event source doesn't exist anymore)
tagged a lot of detections which supported data sources
data_source.csv and data source lookup
data source field is part of annotations

skipping results of unit-testing as no searches were changed!


connection from ycsb to dynamoDB not working

Hi team,
We are trying to use ycsb to connect to dynamodb to perform some benchmarking.
In our environment we are only allowed to use AWS STS service to get access and secret key, when i pass this in AWSCredentials file, the connection is failing with error security token invalid.
It seem STS functionality is missing from ycsb to connect to dynamoDB.
Also in AWSCredentials file, only access and secret variables are given to pass the value but there is not option to pass security token which is kind of mandatory in our aws environment.

I had the same issue with session security token not being recognized. I was able to get it to work with a minor code modification.
In dynamodb/src/main/java/site/ycsb/db/DynamoDBClient.java delete five lines:
22,23d21
< import com.amazonaws.auth.AWSStaticCredentialsProvider;
< import com.amazonaws.auth.PropertiesCredentials;
32d29
< import java.io.File;
84d80
<     String credentialsFile = getProperties().getProperty("dynamodb.awsCredentialsFile", null);
147d142
<           .withCredentials(new AWSStaticCredentialsProvider(new PropertiesCredentials(new File(credentialsFile))))
With those lines deleted, AWS client defaults to inspect the credentials chain, so it will look for credentials in environment variables or ~/.aws/credentials or instance metadata. This modification doesn't allow me to specify an AWS profile, only to use the default profile. But that was enough for me.
Also with this modification, there's no need to specify the AWS credential file in the ycsb properties.

I have the same problem. The AWS SDK's PropertiesCredentials, which YCSB uses, for some unknown reason (I would consider it a bug in the SDK...) only allows a key and secret, and not the third "session token" needed for STS-returned credentials.

you need too make chhangs in how is authenticated.
On Tue, Sep 6, 2022 at 7:26 PM nyh @.***> wrote:

I have the same problem. The AWS SDK's PropertiesCredentials, which YCSB
uses, for some unknown reason (I would consider it a bug in the SDK...)
only allows a key and secret, and not the third "session token" needed for
STS-returned credentials.
—
Reply to this email directly, view it on GitHub
https://github.com/brianfrankcooper/YCSB/issues/1496#issuecomment-1238188423,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLVIWVEKLRYXJUEBN3VS7LV45ER5ANCNFSM4U6FPIZQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@nyh @billkarwin
Seems like this PR also address this issue (and do few other things):
https://github.com/brianfrankcooper/YCSB/pull/1624
It also remove the credentials file property, I don't think anyone using AWS would actually welcome such a change.

Bump - still hurts!


Support for *BSDs

Basically the title.
I'm curious if there were any plans in the past to support FreeBSD/OpenBSD/NetBSD, and if we can expect support in the future.
Before creating this issue, I read:

#10260
https://github.com/mulander/openbsd-dart

At this point we have not revisited our decision from before of not actively supporting *BSD.

Hi @a-siva @mraleph  please can you think again about your decision to not support *BSD ? please

@EliphazBouye what is your use case? FreeBSD market share is almost nonexistent (well below 1%) so I don't think we can ever provide a first party support for it.

@mraleph  ok but on the 1%  must developers like me want to continue to make our Dart/Flutter application on *BSD too

This is something we're receiving substantial requests for in Dart Sass, even given the fact that we support running the compiled-to-JS version from Node.js as a workaround. See https://github.com/sass/dart-sass/issues/2325 and https://github.com/sass/dart-sass/issues/1173, and in turn https://github.com/sass-contrib/sass-embedded-host-ruby/issues/228, https://github.com/sass-contrib/sass-embedded-host-ruby/issues/227, https://github.com/nanoc/nanoc/issues/1710, https://github.com/jekyll/jekyll/issues/9462, and https://github.com/jekyll/jekyll/issues/9493 which are downstream of us.

//cc @mit-mit for your opinion on the above request.

@mraleph what is your use case?

hosting on freebsd.

At this point we don't have the resources to support *BSDs


Add 'debugging' section to Metaprogramming lesson

This new section should allow simpler debugging and look into the result of macro-related actions. This may also give a small insight into Elixir, as things like 'if is a macro' are expanded.

This is great @brain-geek!  Could you also do the RU translations for this?

Sure, @doomspork . But I guess that translation should be in separate PR after this one is merged.

Thanks for the feedback, @doomspork !
I've applied all changes you suggested. Can you look through this PR again?
Thanks!

@brain-geek I left two more pieces of feedback, neither is a must.  This is good to go for me either way 👍

Thanks for new feedback, @doomspork . I've applied both and merging.


Move global args to a class/object/non-global

At the moment the constant calling to:
from src.utils.arguments import args
Is causing the code to have complexity that makes it impossible to:

Write additional code without causing a dependency issue (this is visible when debugging/running unit-tests)
Warnings shown when args is accessed as it doesn't know which arguments exist/don't exist
No type checking when accessing the variables stored inside args
Multiple times args = parser.parse_args() code is called and parameters are init

I suggest to move the arguments.py code so that is not all sitting in the 'global' rather inside a class, init once when the code starts, stores the variables inside a dict rather than args or inside self values of this class, pass this newly created class around to whoever needs it or still use it as a global (but prevent its init from being called on every import)

This code change will also allow writing unit-test, today you cannot call this:
src.attacks.rfi.test_rfi('http://localhost:4280/vulnerabilities/fi/?page=PWN', post='')
To preform a test, as it uses args which are coming from parsing the cmdline, which doesn't exist in unitest

I can provide a PR for these changes (moving args into a class, and fixing all the code that accesses that information)

@nrathaus Yeah, agreed on this. It would be nice if we can write simple tests like this? You can create a PR if you have the time, I will review it and hopefully merge it, if everything checks out! Thanks again!

I created a PR https://github.com/hansmach1ne/LFImap/pull/97
There are some conflicts due to my branch not being in sync with yours when I created it
I tried to fix most of them to make it easier to compare the changes

https://github.com/hansmach1ne/LFImap/pull/98


use application context for WebView initialization

To know it works: open app on android-21 emulator. Without it we have Inflation Error.

Ok, I'll try it out.
Just for reference, this pull request is about issue #419.

So this seems to be an issue with androidx.appcompat version 1.1.0. I think the best solution is to wait for the Android team to fix it.
In the meantime this is a temporary solution.


Add a Note | Addresses #6461

What's changed, or what was fixed?

Added a note, based on feedback from the requestor
minor grammar update

Fixes: #6461
Target Live Date: YYYY-MM-DD

[ ] This has been reviewed and approved by (NAME)
[x] I have run npm test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

@kaycebasques - any updates on this?


ESP32-C6 Unable to join Phlips Hue zigbee network (IDFGH-11616)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Using ESP-IDF v5.1.2, ESP32-C6 N8 dev board connected via USB to a Macbook.
Using "HA_on_off_light" sample code from the esp-zigbee-sdk, my Hue bridge does not see the light, and I get repeating console messages like this
" ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: ESP_FAIL)"
Is ESP32-C6 generally compatible with Philips Hue Zigbee bridge?

Hello @Paveldeg
This issue will be handled here. please close this one.

The issue was addressed by this comment: https://github.com/espressif/esp-zigbee-sdk/issues/168#issuecomment-1952370582


Not possible to use DocString and Datatable with multistep definition

Hi,
Right now, godog does not allow to use gherkin.DocString and gherkin.DataTable with a multisteps definition.
For instance this piece of code will not work:
Then I launch the following steps:
"""
*the container @centos is running
*the container @nginx is running
"""

s.Step(`^I launch the following steps:$`,func () ILaunchTheFollowingSteps(d *gherkin.DocString) godog.Steps {
 	steps := strings.Split(d.Content, "*")[1:]

 	for i, s := range steps {
 		steps[i] = strings.TrimRight(s, "\n")
 	}

 	return godog.Steps(steps)
 })

Godog will complain that the function ILaunchTheFollowingSteps expects one argument.
One possible way to fix this issue is to modify the method maybeUndefined :
func (s *Suite) maybeUndefined(step *gherkin.Step, text string) (undefined []string) {

	def := s.matchStepText(text)

	if nil == def {
		undefined = append(undefined, text)
		return
	}

	if !def.nested {
		return
	}

        // This has been added
	if def != nil && step.Argument != nil {
		def.args = append(def.args, step.Argument)
	}

	for _, next := range def.run().(Steps) {
		undefined = append(undefined, s.maybeUndefined(nil, next)...)
	}

	return
}

Another issue is the substeps can not have any gherkin.DocString or gherkin.Datatable.
For instance this will not work (as the step.Argument is different to the args of the StepDef):
Then I launch the following steps:
"""
*I launch a container and tag it as @centos with the options:
    | type          | docker|
    | image        | centos |
    | labels        | name=centos1 |
"""

right, good point, thanks @Dogild
We cannot support multi line nested steps, the reason is that, they do not come from a gherkin.Step definition parsed from a feature file.
In order to support such a feature, we would need to match and parse argument as a table or content body. But gherkin parser does not provide such a feature so far, to parse some other gherkin node apart from feature file itself. I'm not sure when I may have a look at gherkin parser for such a task, it may be lot of refactoring there.
Anyway, concerning the step argument, when step is inspected for undefined nested steps, this is fixed, we now pass an argument.
Currently it will produce an error when a nested step is multi line. Later we may parse it using gherkin parser if that change will be feasible.
Leaving it is a low priority task, but something to be as a remainder later.

closing, nested steps will not be allowed to have DocString or DataTable arguments, solution would be too ugly


Fix getting PID from empty PID file

What did you implement:
I found that getPID() and checkPID() functions does not work as expected. checkPID() does not remove PID file if PID file exists but it is empty. So I have tried to fix it.
How did you implement it:

Added extra check to getPID() function. It is not necessary, but it makes source code more readable and clear.
Fixed if-condition: force remove PID file with empty PID even if it does not exists. Otherwise we should check if running process is a Unicorn process.

How can we verify it:

Run Anicorn with Unicorn
Truncate PID file.
Restart Anicorn.

After these steps we should be able to run Anicorn with deleted PID file.
Is this ready for review?: Yes
Is it a breaking change?: No

Thanks!


Retry if the reference objects are not properly label with backup

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/lgtm

/lgtm


Demo isn't working, state change not causing a re-render

Expected Behaviour
After a lot of troubleshooting and attempting to use this package in my own project I couldn't seem to get the component to re-render when the store values are updated. I decided to go back to basics and try the demo code in the README to see if I was missing something simple but I can't even seem to get the sample to work. 😞 Am I missing something here?
Actual Behaviour
The component is mounting but it isn't updating state at all when the increment function is called
Reproduce Scenario
I created a stackblitz with a reproducible example

Interesting, this looks right at first glance, perhaps something broke in usage with the recent lit 2 rc release. Thanks for bringing this to our attention!

I'm just happy to hear I'm not crazy haha 😅  I found this package yesterday and spent the better half of 3 hours trying to figure it out with my own code before I finally just tried the demo code. Thanks for looking into it!

Ah, you're using mobx 6, and I think the demo is only written for mobx 5.
It does however work with mobx 6:
https://stackblitz.com/edit/vite-twrhjq?file=my-element.ts

Awesome, thank you for the quick reply on this and the example link! I am brand new to Mobx but so far it seems like it's going to be a perfect fit for my project using Lit.
Side note: I might even do a YouTube tutorial on this package because it's one of the best state management solutions I've found for Lit.

Sounds good! Mobx and lit do work pretty well together indeed. I will close this ticket out, and maybe file an issue later to rework our demos for both v5 and v6 at some point.

Thankyou!!
Kind reminder to update the demo for mobx 6

it seems the magic needed is makeObservable in the constructor for mobx 6 to work.
// create a mobx observable
class Counter {
	@observable
	public count = 0;

	@action
	public increment() {
		this.count++;
	}

	public constructor() {
		makeObservable(this); // has to have this!
	}
}

this is how to get the decorator syntax working


Update how-to-write-links.md

Adding Commonmark / Markdig, since OPS supports both.

@BillWagner should I bother you to review, or ping Jim?


Scaffold the movie model failed when referring to the link below

I followed the link below to auto generate the code using scaffold process. But those files are not generated as expected. I got an error during the process. Error message: there was an error running the selected code generator 'Install the package Microsoft.VisualStudio.Web.CodeGeneration.Design and try again'. I am using VS2019.
Pages/Movies: Create, Delete, Details, Edit, and Index.
Data/RazorPagesMovieContext.cs
https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/model?view=aspnetcore-3.1&tabs=visual-studio

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Part 2, add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Follow the instructions in the error message.

It does not work. I figured out the root cause. I have net5.0 installed which has this issue. When I use dedicated .detcore SDK version 3.1.302 through global.json file, then it works.

I've been using .NET 5 RC1, and it does work. The error message explained the problem.


NIFI-4382: Adding support for Apache Knox SSO

NIFI-4382:

Adding support for KnoxSSO.

High Level Description
This PR facilitates Apache Knox SSO. It can support both cases where the users directly access NiFi and simply use Knox SSO for authentication and where Knox is proxying access to NiFi.
In the direct access case when an unauthenticated user attempts to go to NiFi, NiFi will redirect the user to Knox log in. After successfully logging in, Knox will generate a JWT and put it in an HTTP Cookie and redirect back to NiFi. NiFi will consider the JWT and verify it by validating the signature, audience, and expiration. The signature is validated using a configured public key from Knox. Acceptable audiences can also be configured but are not required. If the JWT is validated, the user identity is extracted from the token.
In the proxying case when an unauthenticated user attempts to go to NiFi through Knox, Knox will redirect the user to Knox log in. After successfully logging in, Knox will generate a JWT and put it in an HTTP Cookie and redirect back to NiFi through Knox. If the requests from Knox to NiFi are made over two-way SSL the JWT in the HTTP Cookie is validated at Knox and the user identity will be placed in the proxied entities chain. When the requests from Knox to NiFi are made over one-way SSL, the Knox Cookie is relayed to the request to NiFi allowing NiFi to validate it with the same logic described above in the direct access case.
For the proxying case, the only new capabilities introduced here are also part of the direct access case (JWT token validation). Because of this, all of the capabilities should be able to be tested using direct NiFi access with Knox SSO.
Testing
To test Knox SSO when directly accessing NiFi, install both Knox and NiFi. Knox SSO configuration is described here [1]. In NiFi four new properties have been introduced:
#nifi properties example
nifi.security.user.knox.url=https://localhost:8443/gateway/knoxsso/api/v1/websso
nifi.security.user.knox.publicKey=<path-to>/gateway-identity.pem
nifi.security.user.knox.cookieName=hadoop-jwt
nifi.security.user.knox.audiences=

These properties assume that Knox is running locally on 8443 and NiFi is secured and running on another port. The publicKey can be exported from Knox using the following command:
<knox-install-dir>/bin/knoxcli.sh export-cert
The cookieName property would need to align with what is configured in Knox. The audience property is used to only accept tokens from a particular audience. The audience value is configured as part of Knox SSO [1].
[1] http://knox.apache.org/books/knox-0-13-0/user-guide.html#KnoxSSO+Configuration+Parameters

I just ran a test with audiences set in Knox, and if there's a space after one of the commas in the KnoxSSO config, it will end up sending that space as part of the audience value.  For example,
        <param>
           <name>knoxsso.token.audiences</name>
           <value>foo,bar, baz</value>
        </param>

With that config, NiFi will see three audiences, "foo", "bar", and " baz".  Notice the space in front of baz.

Add "/access/oidc/**" to webSecurity.ignoring().antMatchers in NiFiWebApiSecurityConfiguration.java

I did not see the nifi.security.user.knox.* properties in the conf/nifi.properties file when I built this branch.

A new commit has been pushed that addresses the comments received thus far. Thanks for reviewing @jtstorck and @alopresto!

@alopresto I just rebuilt and the properties in conf/nifi.properties start on line 167. Can you please double check for them?

@mcgilman the nifi.properties values are there; I was looking at the wrong file. Sorry for that.
I am encountering these checkstyle warnings though (they cause a build failure):
[INFO] --- maven-checkstyle-plugin:2.15:check (check-style) @ nifi-web-security ---
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[103] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[133] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[134] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[149] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[177] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
[WARNING] src/main/java/org/apache/nifi/web/security/knox/KnoxService.java[218] (javadoc) NonEmptyAtclauseDescription: At-clause should have a non-empty description.
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:03 min
[INFO] Finished at: 2017-09-26T13:13:37-07:00
[INFO] Final Memory: 269M/2017M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check (check-style) on project nifi-web-security: You have 6 Checkstyle violations. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :nifi-web-security

Ok, here are my thoughts on this PR:

I got test failures on TestListenUDP when running the full build. I am assuming nothing here changed that so it's unrelated and I won't count it against this PR, but making a note here because I had not seen it on master.
There are checkstyle issues I noted above.
I validated the following use cases:

Normal positive flow
Bad username/password fails
The Knox user authenticates but has no access policies on the canvas
The Knox user JWT has no audiences and NiFi does not require any
The Knox user JWT has no audiences and NiFi requires one
The Knox user JWT has the wrong audience (i.e. not one required by NiFi)
The Knox user JWT has the correct audience as required by NiFi
The Knox user is logged in with one browser and another user is logged in via client certificate in another

Issues found:

No way to logout of the Knox user through the NiFi UI (treated same as client certificate)

Workaround: Use browser to delete hadoop-jwt cookie

If Knox SSO is configured to provide the wrong/insufficient audiences, the login UX simply immediately redirects to the Knox login UI with no error message

Workaround: the NiFi User Log (logs/nifi-user.log) contains a helpful error message

To me, neither issue is a blocker for this PR but I do think they should be resolved in a future release. +1, LGTM (with the checkstyle violation resolutions pending).

Do you think that we should support logout in this case? If yes, I’ll need to figure out the best way to handle this as currently logging out is entirely client side and I believe this would require some server side action.

Yeah, I don't have deep enough Knox familiarity to judge the best use case for communicating back that the logout command has occurred. If we treated receiving the hadoop-jwt token from Knox the same way we did the credential check for LDAP or Kerberos, and issued our own JWT, deleting the local JWT would trigger re-validating the hadoop-jwt cookie. If we update the local key store to indicate that that specific JWT is no longer valid, I believe we could trigger a redirect to the Knox service. However, my understanding is that we cannot simply delete the hadoop-jwt cookie because other services rely on it for SSO, and I do not know what the Knox API is like to trigger a logout remotely. At this time, I do not have a good suggestion for this scenario.

Thanks again @alopresto for the review. I had observed the same behavior where the user is redirected back to the login page when the token could not be validated. I think a good path forward here may be to support multiple login mechanisms concurrently (ldap, oidc, and knox for instance). When this is the case, the NiFi login page would likely offer buttons for the user to initiate the desired SSO login sequence. The reason this is awkward currently is because the redirection happens automatically. This could also give us an opportunity to provide some sort of error message to the end user. Let's consider this option and the logout concern is separate follow on JIRAs.

Thanks Matt. I agree that a "multiple login option splash page" would be a good feature when necessary -- old Stack Overflow comes to mind for me. Looking forward to this code getting in and the follow-on enhancements.

JIRAs for logout [1] and login splash screen [2].
[1] https://issues.apache.org/jira/browse/NIFI-4430
[2] https://issues.apache.org/jira/browse/NIFI-4431

@mcgilman Merged your PR to master.  Thanks for the contribution!  Also, thanks to @alopresto for reviewing!


Question on the GraphEncoderLayer code.

What is q in the following line? It is not defined for the forward_pre function.
https://github.com/Nmegha2601/activitygraph_transformer/blob/234112c47b72e4542c90fc67bbd23e0ceca8a23d/src/models/transformer.py#L164

try this?
q = k = self. with_pos_embed(src2, pos)


"password authentication failed" on PostGraphQL Forum Example

I'm trying to follow the example at https://github.com/postgraphql/postgraphql/tree/master/examples/forum.  I followed these instructions to get postgresql installed on a Linux VM: https://www.digitalocean.com/community/tutorials/how-to-install-and-use-postgresql-on-ubuntu-16-04.
My db and my user/role are both called "mikey".  When I setup the mikey id within postgresql, I did not specify a password.  My OS-level Linux ID is also called mikey, and of course has a password.
At the postgraphql --schema forum_example step, the example code is throwing the following error:

error: password authentication failed for user "mikey"
at Connection.parseE (/home/mikey/.npm-global/lib/node_modules/postgraphql/node_modules/pg/lib/connection.js:572:11)
at Connection.parseMessage (/home/mikey/.npm-global/lib/node_modules/postgraphql/node_modules/pg/lib/connection.js:396:17)
at Socket. (/home/mikey/.npm-global/lib/node_modules/postgraphql/node_modules/pg/lib/connection.js:132:22)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at TCP.onread (net.js:561:20)

Did I miss a step somewhere?

My guess is that this is because the postgres role doesn't have a password. You may also want to check your pg_hba.conf to make sure login is enabled.
This may help: https://stackoverflow.com/a/7696398

Thanks for the response.
My pg_hba.conf has the following entries, which are, I think, what the SO post is referring to:
local   all             postgres                           peer
local   all             all                                     peer

It seems to be connecting to the db all right though. Before it throws the error that I posted, the postgraphql --schema forum_example commands the the connection info below:

PostGraphQL server listening on port 5000 🚀
‣ Connected to Postgres instance postgres://localhost:5432
‣ Introspected Postgres schema(s) forum_example
‣ GraphQL endpoint served at http://localhost:5000/graphql
‣ GraphiQL endpoint served at http://localhost:5000/graphiql

error: password authentication failed for user "mikey"

Do I need to switch to the postgres ID first?  I've setup my test database under my mikey ID, following the Digital Ocean tutorial linked above (although their use is called "sammy").

I believe Postgres is trying to login with your current user. The username matches, but since there is no password in Postgres the authentication fails. Did you try setting a password for the Postgres role? If not, give it a shot.
ALTER USER mikey WITH PASSWORD 'password';

Thank you again, @sjensen85.
I'm making some progress now.  I changed the mikey ID's password, as per your advice.  So postgraphql -c "postgres://localhost:5432/mikey" still fails with the password authentication error, but postgraphql -c "postgres://mikey:password@localhost:5432/mikey" seems to connect okay.
My postgraphql --schema forum_example still fails with that authentication error though.  How do I pass it the postgres password for the mikey ID?

Hey just for anyone in the future getting this error on windows, note that if you don't use double quotes around the db url it doesn't recognise it and tried to log you in via your username.
npx postgraphile -c "postgres://username:pass@localhost:5432/db" --watch --enhance-graphiql --dynamic-json

Hmmm scratch this - it's now failing again. Not sure what's different (might be node - I'm on version 15.1.0)
c:\Users\karl\one-off-data-scripts\graphile-migration>npx postgraphile -c "postgres://postgres:password@localhost:5432/prices_graphile" --watch --enhance-graphiql --dynamic-json

PostGraphile v4.9.2 server listening on port 5000 🚀

  ‣ GraphQL API:         http://localhost:5000/graphql
  ‣ GraphiQL GUI/IDE:    http://localhost:5000/graphiql
  ‣ Postgres connection: postgres:///postgres:password@localhost:5432/prices_graphile (watching)
  ‣ Postgres schema(s):  public
  ‣ Documentation:       https://graphile.org/postgraphile/introduction/
  ‣ Join Dovetail in supporting PostGraphile development: https://graphile.org/sponsor/

* * *

A serious error occurred when building the initial schema. Exiting because `retryOnInitFail` is not set. Error details:

error: password authentication failed for user "karlp"
    at Parser.parseErrorMessage (C:\Users\karlp\AppData\Local\npm-cache\_npx\1b80421a9ae535da\node_modules\pg-protocol\dist\parser.js:278:15)
    at Parser.handlePacket (C:\Users\karlp\AppData\Local\npm-cache\_npx\1b80421a9ae535da\node_modules\pg-protocol\dist\parser.js:126:29)
    at Parser.parse (C:\Users\karlp\AppData\Local\npm-cache\_npx\1b80421a9ae535da\node_modules\pg-protocol\dist\parser.js:39:38)
    at Socket.<anonymous> (C:\Users\karlp\AppData\Local\npm-cache\_npx\1b80421a9ae535da\node_modules\pg-protocol\dist\index.js:10:42)
    at Socket.emit (node:events:327:20)
    at addChunk (node:internal/streams/readable:304:12)
    at readableAddChunk (node:internal/streams/readable:279:9)
    at Socket.Readable.push (node:internal/streams/readable:218:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:192:23)

npm ERR! code 34
npm ERR! path c:\Users\karl\one-off-data-scripts\graphile-migration
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c ""postgraphile" "-c" "postgres:\postgres:password@localhost:5432\prices_graphile" "--watch" "--enhance-graphiql" "--dynamic-json""

npm ERR!      C:\Users\karlp\AppData\Local\npm-cache\_logs\2020-11-24T09_42_34_723Z-debug.log

Yup - bizarrely if I switch to node 14.15.0 (I'm using windows nvm https://github.com/coreybutler/nvm-windows) it works!
c:\Users\karl\one-off-data-scripts\graphile-migration>nvm use 14.15.0
Now using node v14.15.0 (64-bit)

c:\Users\karl\one-off-data-scripts\graphile-migration>npx postgraphile -c "postgres://postgres:password@localhost:5432/prices_graphile" --watch --enhance-graphiql --dynamic-json
npx: installed 125 in 16.496s

PostGraphile v4.9.2 server listening on port 5000 🚀

  ‣ GraphQL API:         http://localhost:5000/graphql
  ‣ GraphiQL GUI/IDE:    http://localhost:5000/graphiql
  ‣ Postgres connection: postgres://postgres:[SECRET]@localhost/prices_graphile (watching)
  ‣ Postgres schema(s):  public
  ‣ Documentation:       https://graphile.org/postgraphile/introduction/
  ‣ Join Mark Rapoza in supporting PostGraphile development: https://graphile.org/sponsor/

* * *

Subtle, but in the first one:

‣ Postgres connection: postgres:///postgres:password@localhost:5432/prices_graphile (watching)

In the second one:

‣ Postgres connection: postgres://postgres:[SECRET]@localhost/prices_graphile (watching)

Note the extra slash in the first one? Also the fact that it says "karlp" in the error but you're using "postgres" as the username indicates that the connection string is not being parsed correctly (that and the password was not masked out); at the moment it thinks that your database name is postgres:password@localhost:5432 and it's connecting with default username, password, hostname, etc.

Ah thanks @benjie I didn't catch that!


fix: pull request template trimmed

Summary
Key Changes

Implemented [feature/new-module]
Fixed issue with [bug/issue-name]
Updated documentation for [feature/update-docs]

Related Issues
Closes #54

Type of Change

[ ] 🐛 Bug fix
[ ] ✨ New feature
[x] ⚙ Enhancement/Improvement
[ ] 📚 Documentation update
[x] 🔧 Refactoring (non-breaking change with no new features or fixes)
[ ] 🚨 Breaking change (changes that break backwards compatibility)

Checklist (select as many as applicable)

[x] I have thoroughly tested my changes.
[ ] The code follows the style guidelines of this project.
[x] I have added/updated relevant documentation (if applicable).
[ ] I have added tests that prove my fix is effective or my feature works (if applicable).
[x] All new and existing tests pass.
[x] This pull request is ready to be merged and reviewed.

Detailed Description
How Has This Been Tested (select as many as applicable)?

[ ] Unit tests
[ ] Integration tests
[ ] End-to-end tests
[ ] Manual testing on [platform/browser]
[ ] Verified using [CI pipeline]

Screenshots (if applicable)

Additional Information
trimmed pr template

@fishonamos

@fishonamos Ready for review


error importing sam2/_C.so when running the video_predictor_example.ipynb

I am getting the following error when I run the line of code that says:
labels = np.array([1], np.int32)
_, out_obj_ids, out_mask_logits = predictor.add_new_points(
    inference_state=inference_state,
    frame_idx=ann_frame_idx,
    obj_id=ann_obj_id,
    points=points,
    labels=labels,
)

The main import error message is:
ImportError: /content/segment-anything-2/sam2/_C.so: undefined symbol: _ZN3c1015SmallVectorBaseIjE8grow_podEPKvmm
This is the entire error:

ImportError                               Traceback (most recent call last)
 in <cell line: 8>()
6 # for labels, 1 means positive click and 0 means negative click
7 labels = np.array([1], np.int32)
----> 8 _, out_obj_ids, out_mask_logits = predictor.add_new_points(
9     inference_state=inference_state,
10     frame_idx=ann_frame_idx,
4 frames
/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py in decorate_context(*args, **kwargs)
113     def decorate_context(*args, **kwargs):
114         with ctx_factory():
--> 115             return func(*args, **kwargs)
116
117     return decorate_context
/content/segment-anything-2/sam2/sam2_video_predictor.py in add_new_points(self, inference_state, frame_idx, obj_id, points, labels, clear_old_points, normalize_coords)
219             # Clamp the scale of prev_sam_mask_logits to avoid rare numerical issues.
220             prev_sam_mask_logits = torch.clamp(prev_sam_mask_logits, -32.0, 32.0)
--> 221         current_out, _ = self._run_single_frame_inference(
222             inference_state=inference_state,
223             output_dict=obj_output_dict,  # run on the slice of a single object
/content/segment-anything-2/sam2/sam2_video_predictor.py in _run_single_frame_inference(self, inference_state, output_dict, frame_idx, batch_size, is_init_cond_frame, point_inputs, mask_inputs, reverse, run_mem_encoder, prev_sam_mask_logits)
808         # potentially fill holes in the predicted masks
809         if self.fill_hole_area > 0:
--> 810             pred_masks_gpu = fill_holes_in_mask_scores(
811                 pred_masks_gpu, self.fill_hole_area
812             )
/content/segment-anything-2/sam2/utils/misc.py in fill_holes_in_mask_scores(mask, max_area)
221     # (background regions are those with mask scores <= 0)
222     assert max_area > 0, "max_area must be positive"
--> 223     labels, areas = get_connected_components(mask <= 0)
224     is_hole = (labels > 0) & (areas <= max_area)
225     # We fill holes with a small positive mask score (0.1) to change them to foreground.
/content/segment-anything-2/sam2/utils/misc.py in get_connected_components(mask)
59               components for foreground pixels and 0 for background pixels.
60     """
---> 61     from sam2 import _C
62
63     return _C.get_connected_componnets(mask.to(torch.uint8).contiguous())
ImportError: /content/segment-anything-2/sam2/_C.so: undefined symbol: _ZN3c1015SmallVectorBaseIjE8grow_podEPKvmm
Can you please help out with this issue. It would enable me to proceed with the project. Not sure how to fix it.

!python setup.py build_ext --inplace worked for me

I'm having the same issue.Pls have you solved it？

@vanamagautam24 thanks! it works for me!

Hi, we have added INSTALL.md as an installation FAQ.
Regarding this error:
This is usually because you haven't run the pip install -e ".[demo]" step above or the installation failed. Please install SAM 2 first, and see the other issues if your installation fails. (You may also try python setup.py build_ext --inplace in the repo root as others suggested in https://github.com/facebookresearch/segment-anything-2/issues/77)

Thank you, What worked for me was running these commands:
%cd /content/segment-anything-2
!python setup.py build_ext --inplace
Run the above commands after building the relevant sam2 model


iodevice error fix for xsens

Status
PRODUCTION / DEVELOPMENT
Description
This PR fixes the xsens iodevice error. https://github.com/CPFL/Autoware/issues/940
Related PRs
List related PRs against other branches:
Steps to Test or Reproduce
On develop:

Check out autoware
Go to Autoware/ros/src/sensing/drivers/imu/packages/xsens/src/xsens_driver/src
Run: ./mtdevice.py. You should see an error similar to below:

Traceback (most recent call last):
  File "./mtdevice.py", line 1024, in <module>
    main()
  File "./mtdevice.py", line 979, in main
    mt = MTDevice(device, baudrate)
  File "./mtdevice.py", line 23, in __init__
    writeTimeout=timeout)
  File "/usr/lib/python2.7/dist-packages/serial/serialutil.py", line 180, in __init__
    self.open()
  File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 311, in open
    self._update_dtr_state()
  File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 605, in _update_dtr_state
    fcntl.ioctl(self.fd, TIOCMBIS, TIOCM_DTR_str)
IOError: [Errno 22] Invalid argument

To test fix: check out this branch and follow the same instructions. No error should be thrown, instead verbose output should be printed.
@amc-nu @dejanpan FYI

this fix was suggested here: https://github.com/xsens/xsens_mti_ros_node/issues/21#issuecomment-315996807

I'll test with a real IMU later today, please wait for a while.

ok, we'd appreciate if it can happen today

@dejanpan @christopherho-ApexAI
Cannot replicate the error. Executing mtdevice.py immediately starts to show data coming from the IMU

@amc-nu are you also running 16.04 ubuntu and kinetic?

No, I'm testing on 14.04 and Indigo. I'll switch.

Error confirmed on Ubuntu 16.04 and Kinetic. Fix also confirmed.

Fix doesn't break Indigo node


Adds info about commands requiring Flutter-bundled dart

Adds info about dome commands requiring Flutter-bundled dart.

@stuartmorgan Let me know if this phrasing and location makes sense for this information.


New version: ImageMagick.Q16-HDRI version <IP_ADDRESS>

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

How come I still get an error after this PR was merged? Is there a delay? Do I need to refresh something?
> winget install ImageMagick.ImageMagick
Found ImageMagick Q16-HDRI [ImageMagick.ImageMagick] Version <IP_ADDRESS>
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://imagemagick.org/archive/binaries/ImageMagick-7.1.1-41-Q16-HDRI-x64-dll.exe
An unexpected error occurred while executing the command:
Download request status is not success.
0x80190194 : unknown error

This is updating another package than you are referencing. The ImageMagick team is not maintaining the packages with id ImageMagick.ImageMagick*. Our packages have the following ids: ImageMagick.Q16-HDRI, ImageMagick.Q16 and ImageMagick.Q8.

Oh thank you that works with "ImageMagick.Q16-HDRI"!
I assumed ImageMagick.ImageMagick was a kind of shortcut pointing to the default package but that's confusing if it's a different one altogether.

We did not take over the other package name because that uses a different kind of installer and is also not using the static version of ImageMagick.


Logs per workload

Make logging available per workload
Why is this needed:
Most deployments have more than a single pod, usually, when searching for something, or making some test, it's not always known in which exact pod the request will end up, so it's really useful to tail the logs from all the pods of a workload
It would actually be really nice if it could have all the options that stern has, for example, like filtering per container or allowing to specify exclusions
Environment you are Lens application on:

Kubernetes distribution: GKE, Rancher and EKS, but I don't think it matters
Desktop OS: macOS

+1

Agree, it would be a killer feature!

Even a quick way to switch between pods (within a deployment) when viewing logs would be a great help - having to backtrack to the deployment, scroll back down to the list of pods and then drill into the next one and hit the logs again isn't ideal, especially since the list of pods doesn't seem to have a stable sort order.  If your pod names are long enough that they get truncated, it's easy to end up checking the same pod twice instead of checking the next one.

The one thing I really miss from Kubernetes Dashboard is being able to switch between logs within a deployment.
For example, here we have the dashboard view of logs for our datadog agent deployment:

We can choose between the specific named containers from within the deployment:

And then easily flick between the logs for a specific container instance:

For what it's worth I am also very interested in that feature.

Related to #430

+1 for this.  Aggregated logs across all pods in a deployment (or even namespace) would be fantastic.  I just tried out some other offerings that have this feature and it was very easy to see that one pod wasn't co-operating like it should.

+1 for this. Aggregated logs across all pods in a deployment (or even namespace) would be fantastic. I just tried out some other offerings that have this feature and it was very easy to see that one pod wasn't co-operating like it should.

I'm missing the aggregated logs across all pods in a deployment, but sounds like having it flexible enough to go from pod all the way up to workload/namespace depending on the need is a winner.
Just need to keep it fast, as I use k9s, which allows for logging a deployment, and logs can get a bit delayed behind real-time and it's both literally and physically a drag.

+1 for this. Aggregated logs across all pods in a deployment (or even namespace) would be fantastic. I just tried out some other offerings that have this feature and it was very easy to see that one pod wasn't co-operating like it should.

I'm missing the aggregated logs across all pods in a deployment, but sounds like having it flexible enough to go from pod all the way up to workload/namespace depending on the need is a winner.
Just need to keep it fast, as I use k9s, which allows for logging a deployment, and logs can get a bit delayed behind real-time and it's both literally and physically a drag.

+1.
Please

+1.
Please

Any news on this? That would be very useful when dozens of replicas exist for a given Deployment object.

main reason I use aptakube and not this


Add logging that (hopefully) works on CallbackServer exceptions

It looks like ex.printStackTrace() didn't log in the narrative -- this changes it to use cbLog on a string of the stack trace, which I think has a better chance of working.
I'm still shooting blind as I don't yet have a great way to run any of this locally. It all compiles though :p.

Looks fine to add


module:migrate gives error!

SQLSTATE[HY000]: General error: 1005 Can't create table DBNAME.#sql-171c_54 (errno: 150 "Foreign key constraint is incorrectly formed")
asgard version: 1.14.1
Also gives this error: Class 'Modules\Core\Composers\BaseSidebarViewComposer' not found
How can I remove a module from AsgardCMS?

Hello,
sorry this module was never finsihed, I will remove it from packagist.
To remove it from asgard, the best is to ask help from asgard community itself


Use F.matmul instead of F.batch_matmul in memnn example

This PR fixes the memnn example to use F.matmul rather than F.batch_matmul, which is deprecated now. With F.matmul, the memnn example can work in FP16 mode.

Jenkins, test this please.

Jenkins CI test (for commit 061062e028736ee2da40611da65b72d2ab4864f8, target branch master) succeeded!


os/user: add non-cgo version GroupIds

This is slightly more complicated than the pure Go versions of LookupGroup, Lookup, LookupId, LookupGroupId, I think.
On Darwin machines, /etc/group does not contain a full or partial accounting of a user's groups. Instead the definitive information is stored in opendirectoryd and I'm not quite sure how to access that, apart from C libraries that we don't have access to.
If we wanted to do this in Go we would do:

loop over every entry in /etc/group.
If the group name starts with a plus or minus, ignore it.
If the group mentions the username in the secondary group list, or if the user's Gid matches the gid, add it to an array.
return the array.

But this would miss many groups on Darwin and possibly any extensions that glibc also lets you check, which might be a more relevant concern when you are asking for all groups instead of just the primary user/group.
I think that exec.Command("groups", u.Username).Output() would give the right answer, but the overhead is likely too high, a user's machine might not have groups or be able to run a subprocess, &c &c.

Why? Why not use cgo?

The common place I run into errors here is cross compiling; compiling for a Linux target from my Mac laptop.
I run into problems with user.LookupGroup and user.Lookup much more frequently than GroupIds(). I added non-cgo versions of those in recent CL's. For completeness I thought I would try to add this one as well.

CLs still welcome, of course.

OK. I think it's probably better to leave unimplemented than to return a response that may be only partially correct.
I think it was OK to add cgo-free versions of Lookup(), LookupId() and friends because Mac/Linux may not use /etc/passwd, /etc/group as a source of truth but they at least try to keep them up to date for the purpose of id <=> name mappings. It seems like they're not reliable enough for "list a user's groups," though.


as to ensure that the git repository has Dependabot

and it's enabled for Docker images and the relevant package
ecosystem (e.g. Bundler)
ref.:
https://docs.github.com/en/github/administering-a-repository/configuration-options-for-dependency-updates

:lock: Prisma Cloud scan details - vulnerabilities :warning:

:white_check_mark: Passed shipment_tracker:latest   Vulnerabilities found. Total: 31, critical: 0, high: 17, medium: 13, low: 1.

Severity
Package
CVE
Fix version

:red_circle: high
openldap:2.4.50-r1An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).
CVE-2020-36221  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.
CVE-2020-36222  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).
CVE-2020-36223  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in denial of service.
CVE-2020-36224  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.
CVE-2020-36225  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.
CVE-2020-36226  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.
CVE-2020-36227  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.
CVE-2020-36228  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.
CVE-2020-36229  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:red_circle: high
openldap:2.4.50-r1A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.
CVE-2020-36230  Date published: 2021-01-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.4.57-r0

:orange_circle: medium
sqlite:3.32.1-r0In SQLite before 3.32.3, select.c mishandles query-flattener optimization, leading to a multiSelectOrderBy heap overflow because of misuse of transitive properties for constant propagation.
CVE-2020-15358  Date published: 2020-06-27 12:15:00 +0000 UTC
Vendor status: fixed in 3.34.1-r0

:yellow_circle: low
curl:7.69.1-r3A malicious server can use the FTP PASV response to trick curl 7.73.0 and earlier into connecting back to a given IP address and port, and this way potentially make curl extract information about services that are otherwise private and not disclosed, for example doing port scanning and service banner extractions.
CVE-2020-8284  Date published: 2020-12-14 20:15:00 +0000 UTC
Vendor status: fixed in 7.74.0-r0

:orange_circle: medium
ruby:2.5.8-r1An issue was discovered in Ruby 2.5.x through 2.5.7, 2.6.x through 2.6.5, and 2.7.0. If a victim calls BasicSocket#read_nonblock(requested_size, buffer, exception: false), the method resizes the buffer to fit the requested size, but no data is copied. Thus, the buffer string provides the previous value of the heap. This may expose possibly sensitive data from the interpreter.
CVE-2020-10933  Date published: 2020-05-04 15:15:00 +0000 UTC
Vendor status: fixed in 2.6.6-r0

:red_circle: high
ruby:2.5.8-r1The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent.
CVE-2020-10663  Date published: 2020-04-28 21:15:00 +0000 UTC
Vendor status: fixed in 2.6.6-r0

:red_circle: high
ruby:2.5.8-r1Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows code injection if the first argument (aka the \"command\" argument) to Shell#[] or Shell#test in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method.
CVE-2019-16255  Date published: 2019-11-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.6.5-r0

:orange_circle: medium
ruby:2.5.8-r1Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows HTTP Response Splitting. If a program using WEBrick inserts untrusted input into the response header, an attacker can exploit it to insert a newline character to split a header, and inject malicious content to deceive clients. NOTE: this issue exists because of an incomplete fix for CVE-2017-17742, which addressed the CRLF vector, but did not address an isolated CR or an isolated LF.
CVE-2019-16254  Date published: 2019-11-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.6.5-r0

:red_circle: high
ruby:2.5.8-r1WEBrick::HTTPAuth::DigestAuth in Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 has a regular expression Denial of Service cause by looping/backtracking. A victim must expose a WEBrick server that uses DigestAuth to the Internet or a untrusted network.
CVE-2019-16201  Date published: 2019-11-26 18:15:00 +0000 UTC
Vendor status: fixed in 2.6.5-r0

:orange_circle: medium
ruby:2.5.8-r1Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 mishandles path checking within File.fnmatch functions.
CVE-2019-15845  Date published: 2019-11-26 17:15:00 +0000 UTC
Vendor status: fixed in 2.6.5-r0

:red_circle: high
ruby:2.5.8-r1An issue was discovered in Ruby through 2.5.8, 2.6.x through 2.6.6, and 2.7.x through 2.7.1. WEBrick, a simple HTTP server bundled with Ruby, had not checked the transfer-encoding header value rigorously. An attacker may potentially exploit this issue to bypass a reverse proxy (which also has a poor header check), which may lead to an HTTP Request Smuggling attack.
CVE-2020-25613  Date published: 2020-10-06 13:15:00 +0000 UTC
Vendor status: fixed in 2.7.2-r0

 moderate
jquery:1.7.2jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove \"\", which results in the enclosed script logic to be executed.
CVE-2020-7656  Date published: 2020-05-19 21:15:00 +0000 UTC
Vendor status: fixed in 1.9.0

:red_circle: high
jquery:1.7.2jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
CVE-2015-9251  Date published: 2018-01-18 23:29:00 +0000 UTC
Vendor status: fixed in 3.0.0

 moderate
jquery:1.7.2Versions of `jquery`  prior to 3.4.0 are vulnerable to Prototype Pollution. The extend() method allows an attacker to modify the prototype for `Object` causing changes in properties that will exist on all objects.   ## Recommendation  Upgrade to version 3.4.0 or later.
CVE-2019-5428  Date published: 2019-04-23 15:59:10 +0000 UTC
Vendor status: fixed in 3.4.0

 moderate
jquery:1.7.2jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
CVE-2019-11358  Date published: 2019-04-20 00:29:00 +0000 UTC
Vendor status: fixed in 3.4.0

 moderate
jquery:1.7.2In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing  elements from untrusted sources - even after sanitizing it - to one of jQuery\'s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11023  Date published: 2020-04-29 21:15:00 +0000 UTC
Vendor status: fixed in 3.5.0

 moderate
jquery:1.7.2In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery\'s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022  Date published: 2020-04-29 22:15:00 +0000 UTC
Vendor status: fixed in 3.5.0

:red_circle: high
jquery:1.7.2jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the \'<\' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the \'<\' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
CVE-2012-6708  Date published: 2018-01-18 23:29:00 +0000 UTC
Vendor status: fixed in 1.9.0

:red_circle: high
jquery:1.12.4jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.
CVE-2015-9251  Date published: 2018-01-18 23:29:00 +0000 UTC
Vendor status: fixed in 3.0.0

 moderate
jquery:1.12.4Versions of `jquery`  prior to 3.4.0 are vulnerable to Prototype Pollution. The extend() method allows an attacker to modify the prototype for `Object` causing changes in properties that will exist on all objects.   ## Recommendation  Upgrade to version 3.4.0 or later.
CVE-2019-5428  Date published: 2019-04-23 15:59:10 +0000 UTC
Vendor status: fixed in 3.4.0

 moderate
jquery:1.12.4jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
CVE-2019-11358  Date published: 2019-04-20 00:29:00 +0000 UTC
Vendor status: fixed in 3.4.0

 moderate
jquery:1.12.4In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing  elements from untrusted sources - even after sanitizing it - to one of jQuery\'s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11023  Date published: 2020-04-29 21:15:00 +0000 UTC
Vendor status: fixed in 3.5.0

 moderate
jquery:1.12.4In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery\'s DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
CVE-2020-11022  Date published: 2020-04-29 22:15:00 +0000 UTC
Vendor status: fixed in 3.5.0


[BUG]v2.6.5-rc10版本，rancher上无法查看pod的log

v2.6.5-rc10版本，不知道做了什么操作，无法查看pod的log了，点击有报错，bug是跟账号走的，不是机器的问题，不同机器登录同一个账号，也会发生这个bug。

I'm going on the assumption that this is the same bug as https://github.com/rancher/dashboard/issues/5984, therefore closing as a duplicate.
If this is not the case, please comment (in English) and we can look in to it.


add "text/x-template" as type

add "text/x-template" as type of script
<script type="x-template">

as suggested here https://vuejs.org/v2/api/#template

This would be great for us who us the template option.
Does this also match just the shorthand <script type="x-template"> or only <script type="text/x-template">? I can't tell in the PR right away.
Wonder if a maintainer might look at this and consider merging? From a quick cursory glance other people are looking for Vue syntax highlighting of these templates on Stack Overflow and other forums.

@dmyers I added missed x-template type. Now supports
<script type="x-template">

and
<script type="text/x-template">

From reading up on it quickly, this seems not that relevant for an SFC .vue file, because the <script type="text/x-template"> syntax is supposed to be used in html files and thus would requre extending the default HTML syntax with one that recognizes this template syntax to then include the vue template syntax there. It can be done, but considering how using the x-templates feature is discouraged in the Vue 2 docs and I wasn't able to find a mention of it in the Vue 3 docs, I presume this is not all that relevant.


Tag "Forth"

Please create a "forth" tag and ... for this project. (Label "Manage topic" in open project)

done :)