Add filebeat 5.4.0

Update docker image to the current version

@andreausu any chance for latest version to get merged/pushed to dockerhub?

Thank you and sorry about the late response, I will soon add this and 5.5.x as well


Duplicated links in documentation

Duplicated links in the documentation:
Page:
https://docs.microsoft.com/en-us/dynamics365/supply-chain/landed-cost/landed-cost-vs-tms#intercompany-reports
Snippet:
The following reports don't work in conjunction with the goods in transit feature that Landed cost provides:
Intercompany goods in transit totals report
Intercompany goods in transit totals report
Regards,
hpvanzyl
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f85f0889-baee-fce5-c546-1fee78ef0c84
Version Independent ID: 71b3e524-bd5a-d155-01b7-449c249189a9
Content: Landed cost vs. Transportation management - Supply Chain Management | Dynamics 365
Content Source: articles/supply-chain/landed-cost/landed-cost-vs-tms.md
Service: dynamics-365-supply-chain
Product: ****
Technology: ****
GitHub Login: @sherry-zheng
Microsoft Alias: chuzheng

@hpvanzyl, Thank you for this feedback.
@sherry-zheng, please review and update as needed.

Closing as won't fix.


debugfont.png should be specifiable

At the moment loadAll in gbox.js has a specific relative path ("akihabara/debugfont.png") for the debug font. It would be nice to have a way to override just this path to, for example, work on Akihabara games with jsFiddle, or more generally in situations where the page isn't on the same server as Akihabara.

@kesiev, @polm submitted this patch on the new repository. Can you close this one?

Well ideally, if you created a 'debug' class, you would load whatever font image/tileset you wanted to use separate from the maingame loop. This would remove that issue altogether. And 'font' would just be the font used by the maingame and would not change as it would be used for consistency.

@foofoobar Look at the new repository https://github.com/Akihabara/akihabara. This code was applied and we're working on the new Akihabara major version. Feel free to help on the development :)

This looks to be a fork and not maintained by Darius/Kesiev. Is he still
involved in this?
Owen Rubel
415-971-0976
<EMAIL_ADDRESS>On Wed, Feb 22, 2012 at 8:15 AM, Willian Molinari <
<EMAIL_ADDRESS>
wrote:

@foofoobar Look at the new repository
https://github.com/Akihabara/akihabara. This code was applied and we're
working on the new Akihabara major version. Feel free to help on the
development :)

Reply to this email directly or view it on GitHub:
https://github.com/kesiev/akihabara/issues/14#issuecomment-4107228

@foofoobar Darius was not maintaining Akihabara and @kesiev don't have time to work with it anymore. I talked to @kesiev   and started working on Akihabara new version. He helped me on the milestones and ideas for the new version and actually he is one of the organization owners: https://github.com/akihabara.
We added an information about the new repository on the this repository README: https://github.com/kesiev/akihabara/blob/master/README.markdown
Anyway, feel free to contribute to the new version :)

fair enough. Will take a look and check it out. I've been developing alot on older version to make it more client/server oriented. Will have to see what you have so far. Does it run as is?

pulled down source. do you have example of how to implement? Ran test but that LITERALLY was just a test :)
Nice one too. Want to start hacking and pulling stuff apart and building classes. Got any examples? Can the existing stuff port?

@foofoobar Yes. We have a demo running on it: http://akihabara.github.com/experimental-demo-tlos/
As you can see this is unstable and the code is changing a lot nowadays to fit right on the new version.
If you want more information send it to the mailing list and I'll do my best to introduce you to the new code.

Excellent. Sign me up for mailing list. What is it? :)

@foofoobar http://groups.google.com.br/group/akihabara-engine

Honestly in my efforts I'm finding that the shmup/sidescroller/topview are
all the same game with objects using different functions. Those functions
are shared at times; for instance fireBullet can be shared by all jump CAN
be shared but doesn't do anything for shmup/topview except to provide a
visual effect or possibly dodge objects (see classic 'bump-n-jump' arcade
game). In effect, topview/shmup/sidescroll make no difference and what
should be being separated are
'player.js','enemy.js','trigger.js','container.js','object.js','hud.js','menu.js','dialog.js',etc
The components that make the game are what should be separated and the
games themselves should have all functions built into the objects that are
the components. Thus when making a sidescroller, that then becomes a
topview that then becomes a shmup... you can recycle all components and
just do a transform with different tilesets if need be.
On Wed, Feb 22, 2012 at 9:00 AM, Willian Molinari <
<EMAIL_ADDRESS>
wrote:

@foofoobar Yes. We have a demo running on it:
http://akihabara.github.com/experimental-demo-tlos/
As you can see this is unstable and the code is changing a lot nowadays to
fit right on the new version.
If you want more information send it to the mailing list and I'll do my
best to introduce you to the new code.

Reply to this email directly or view it on GitHub:
https://github.com/kesiev/akihabara/issues/14#issuecomment-4108316

@foofoobar mailing list, please.


Bump kubernetes version to  v1.20.2

Changes
Fix issue: https://github.com/shipwright-io/build/issues/721

Bump kind node version to v1.20.2;
Bump all relative k8s packages to v0.20.2;
Update docs to reflect we support kube v1.20.2;
Update dependencies;

Submitter Checklist

[ ] Includes tests if functionality changed/was added
[x] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Bump kubernetes version to `v1.20.2`

The check list complains about the old Kube v1.19.7 jobs did not complete (like e2e (1.15.x, ubuntu-latest, v1.19.7)). This might be configured somewhere in the openshift ci part, or GitHub stumbled. Let me close and reopen the PR to rerun checks to see if that resolves.

Okay, that does not go away. @adambkaplan where are these required v1.19.7 checks configured?

Repository settings have been updated so integration and e2e tests aren't required.
TODO - need to re-add this validation and allow our k8s/golang versions to float on a "latest"


Doc WS-Federation provider specifically for core

Is there any way to Autenticate using Ws Federation  in ASP.Net Core 2.1 MVC using the existing WIF Implemented Ws Federation Provider in .Net Framework.
Which seems to be not working, I didnt find any helpful document to work on this thing.

@blowdart Do you know?

No, there's no way. Which is why there's a WS-Federation provider specifically for core. Which I guess we haven't documented. https://github.com/aspnet/Security/tree/dev/src/Microsoft.AspNetCore.Authentication.WsFederation

@blowdart  who can outline this?

Oh wait, it is there https://docs.microsoft.com/en-us/aspnet/core/security/authentication/ws-federation?view=aspnetcore-2.1

@blowdart
No It isn't applicable for my scenario as mentioned below,
I have a ASP.Net application (WIF) consuming the Ws federation Services for the authentication. So that other applications can Utilize this Federation Provider for authentication and authorization.
How can we use this existing Federation Provider Application in another application build on ASP.Net Core 2.x for authentication and authorization.

When you say you're consuming this indicates (to me) that you have a WS-Fed provider elsewhere. So you'd configure core in the way that documentation details, which would call out to the WS-Fed provider, then use cookies to create the identity that persist between calls. So what is missing here?

@blowdart i have few more questions where should we configure the thumbprint in the core application?

Code Snippet for configuring WS-Federation is as follows.
services
.AddAuthentication(sharedOptions =>
{
            sharedOptions.DefaultScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            sharedOptions.DefaultSignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            sharedOptions.DefaultChallengeScheme = WsFederationDefaults.AuthenticationScheme;
        })
        .AddWsFederation(WsFederationDefaults.AuthenticationScheme, WsFederationDefaults.DisplayName, options =>
        {

            options.Wtrealm = "https://localhost:44338/";

            //For Bypassing Metadata Address
            options.MetadataAddress = string.Empty;

            options.Configuration = new Microsoft.IdentityModel.Protocols.WsFederation.WsFederationConfiguration
            {
                TokenEndpoint = Configuration["SSOSettings:WIFFederationProviderAddress"],
                Issuer = "FP"

            };

            options.RequireHttpsMetadata = false;

            options.TokenValidationParameters.ClockSkew = TimeSpan.FromMinutes(5);

            options.ClaimsIssuer = Configuration["SSOSettings:WIFFederationProviderAddress"];

            options.TokenValidationParameters.ValidateIssuer = true;
            options.TokenValidationParameters.ValidateLifetime = true;

            options.TokenValidationParameters.ValidateAudience = true;
            options.TokenValidationParameters.ValidateTokenReplay = false;
            options.TokenValidationParameters.RequireSignedTokens = true;

            options.CallbackPath = new PathString("/signin-wsfed");
            options.SkipUnrecognizedRequests = true;

        })
        .AddCookie();

Then you haven't configured your provider correctly. In WS-Fed that would be the Relying Party protocol URL. The return URL is configured in the identity provider.

And the thumbprint comes from the metadata endpoint, which allows for cert rotation.

@blowdart I tried either way but the result was the same.

I'm afraid there's not a lot more I can offer. It worked in our testing, when the provider was configured correctly. I'd suggest talking to your federation provider at this point.

Federation Provider is configured in such a way that it cross checks the Thumbprints(from the receiving end and fed provider) in order to authenticate.

Not this one. Nor did the Owin implementation. WIF is 10+ years old. The standard is to get the metadata and use that, because it allows for certificate rotation. We moved away from thumbprints over 5 years ago.

Can you please provide the link with the full-example for the WS-Fed using Core along with the Federation Provider implementation in order to get the over all view of it.
So that i can point it in the Right direction.

https://github.com/aspnet/Security/tree/dev/samples/WsFedSample
And as this isn't a docs issue I'm going to close this issue.


Deepstack declaring wrong objects ?

Hello!
I am searching for "person" objects on my security camera. Deepstack just returned the following two "person" objects:

Is there any further information you would need for investigating this ? I.E.:  I can try to find the original snapshot from my video storage and send it to you so you can further analyze locally how did DeepStack ended up labelling this as two "person" objects ?

@euquiq  Deepstack actually did not detect two people but rather it detected a "human being" and a "bicycle". It means the bounding boxes are for the human and bicycle respectively. You might need to explicitly inform deepstack to detect just humans.

@AbimbolaOO As I stated, Deepstack declares that both objects are "human beings"

Hello @euquiq Can you share the full json response from DeepStack including the predicted labels?

Sorry, no, I did erase it. The software we made parsed that json, and boxing in green al objects of type "person" (it's a condition for the boxing to occur, that Deepstack labels the object as "person").
I think I stored the still images that caused this, in case you want to input these into Deepstack (it was configured in high).
Also when calling deepstack, if I correctly recall, the parameter I can pass thru is "minimum confidence". Is there a way to also limit Deepstack to "person" objects (and would this accelerate deepstack process ?)
Thanks!


[boost-asio] Add package option to enable io_uring support

Is your feature request related to a problem? Please describe.
The next boost asio (version 1.78) has an option for enabling io_uring. It must be compiled with BOOST_ASIO_HAS_IO_URING and BOOST_ASIO_DISABLE_EPOLL
Proposed solution
An installation option to enable uring
Describe alternatives you've considered
The two options could also be enabled/disabled to selectively enable uring, epoll, or both.
Additional context
Boost 1.78 is out: https://www.boost.org/doc/libs/1_78_0/doc/html/boost_asio/history.html

Boost.Asio is header only library. You can add these defines in your application.

@yurybura As far as I know changing options would change the interface requirement for boost asio, which would apply to all packages using it. Simply using a define because it's header only don't cut it. If you have a dependency that use boost asio and you define those keyword in your project, you'll have ODR violation. The package manager should take care of that.

The Boost packages are compatible with built-in CMake targets:
    find_package(Boost REQUIRED [COMPONENTS <libs>...])
    target_link_libraries(main PRIVATE Boost::boost Boost::<lib1> Boost::<lib2> ...)

vcpkg doesn't provide any other exported CMake target.
Due to boost-asio doesn't have binary files I think you can simply build your own application like this:
    find_package(Boost REQUIRED)
    target_link_libraries(main PRIVATE Boost::boost)
    target_compile_definitions(main
        PRIVATE
            BOOST_ASIO_HAS_IO_URING=1
            BOOST_ASIO_DISABLE_EPOLL=1
    )

If other vcpkg package will use io_uring during the build this package must define have similar CMake code in portfile.cmake.

I don't think this issue should be closed simply because there was no comments. I think it would be valuable to have a port feature for boost asio to enable io_uring. It is a header only library yes, but I don't think it's really relevant for this issue. If consistency, avoiding ODR violations and one day enable C++20 module builds is something vcpkg users want, it should be port feature.


Cookie consent

We need to provide info about cookies, usage of Firebase analytics and probably not call firebase.analytics() until cookie consent is not given.

For the moment it's easier to state that the cookies are required.


Change info about accessing assets files, GitHub as CDN

Close in favor of https://github.com/trustwallet/developer/pull/178


dev-dtvf-config-url

Brings in the ability to pass in a custom URL for the visualisation's data configuration file, along with the ability to call this functionality multiple times.
This will allow more experienced developers to add custom controls that can be used to build/determine the location of the config file to use. Once controls are added, simply use the code snippet below (also seen in the Mapbox example visualisation) to reload the visualisation with a new config file.
// Load the data definitions
let configURL = "./data.json"
manager.loadDefinitionsFromURL(configURL).then(function() {

    // Plot the data
    manager.plotData();
});

Note that this PR is a draft as the version of the DTVF has been set to 3.6.0. It will remain a draft until PR #744 has been merged.

I've tested this locally with both the Mapbox and Cesium examples. It works as designed and does not effect existing functionality. As the code changes are relatively small, I'm merging this in now rather than letting it go stale.


[Roadmap] E2E Testing

Is your feature request related to a problem? Please describe.
In order to improve the testing of Liqo, we would like to add testing on real Liqo Deployments
Steps

[x] Handle cluster lifecycle

[x] Create different clusters for different PRs
[x] Delete the right VMs

[x] Create a feedback loop to build clusters:

[x] Deploy one cluster + Liqo Install
[x] Get the feedback loop*

[x] Add Assertions

Closing. Fixed by #80.


how to detect a message that have been sent via a bot?

I've tried to detect a message that has been sent via a bot (not my bot)
cause some of the spammers are using this type of message with a long list of keyboard buttons,
but it seems there is no way to detect that
is there a way to detect this type of messages?

@abbddo no, no way. Bots can't see messages by other bots.

@GingerPlusPlus
there is a diffrence between by and via.
so do you mean "Bots can't see messages via other bots."?

@abbddo I mean, bots can't see messages sent by other bots

@GingerPlusPlus
ok, what about messages sent via other bots?

@abbddo You mean, via inline bot?

@GingerPlusPlus
yes , via inline bot

@abbddo I was at vacation, I was offline.
I don't think it's possible to check that, at least I can't find anything in docs, and using /jsondump.
One thing that may be suitable for your use-case, you can restrict people from using inline bots.

What messages will my bot get?

All bots, regardless of settings, will receive:

All service messages.
All messages from private chats with users.
All messages from channels where they are a member.
2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

Bots with privacy mode enabled will receive:

Commands explicitly meant for them (e.g., /command@this_bot).
General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
Messages sent via this bot.
Replies to any messages implicitly or explicitly meant for this bot.
Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.
### Why doesn't my bot see messages from other bots?
Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

I believe this has been sorted out.


fix(generator): apply nullish? operator in schema.ts

Status

READY
Description
fixes https://github.com/anymaniax/orval/issues/259 . I don't know if this is a "proper" fix but it solves the example reproduction case in the issue body.
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog Entry (unreleased)

Steps to Test or Reproduce
see issue for details. the files specified will fail yo

actually, this fixes the example case but in my spec (it's proprietary) I get only interfaces generated, and no hooks/methods/mocks even though the generation succeeds.

converting to draft, need a better solution.

reopening as I experienced 2 related bugs, this fixes the first.

Hey @Talor-A, mmh weird this case shouldn't happen I need to investigate that more. Will have time this weekend normally

ok no problem. I've pulled this commit into my fork as it fixes it for my situation, but I don't doubt there's a better solution. thanks for the response!

thanks fixed with an other pull request


Less intrusive problems' statusbar item

This is what my problems' statusbar item looks like most of the times:

I think the counter and icon about warnings shouldn't be rendered if there aren't any warnings at all. Same with errors. As a consequence if the problems pane is empty there shouldn't be a statusbar item wasting space in my statusbar just so that when I click it I can stare at an empty pane.
Also by showing the statusbar item only when there are actually some warnings/errors it'll be easier not to miss them.

I actually disagree with it since it makes a less stable UI.
I will keep it open to see if other see it the same way.

Good point, but maybe it wouldn't be that much of a distraction after all 🤔
Maybe there could be a setting for enabling this behavior?


Update shader list after saving gdshaderinc file

Fixes https://github.com/godotengine/godot/issues/94657

Thanks!


Link Git models with general models

Description
This PR provides the functionality to add an existing git repository to a model. When adding a git repository, there are different cases to consider. In general, you can distinguish between the case where at least one base model source is specified in the settings and the case where no model sources are specified. In both cases, you must provide credentials if you want to access a private repository, and then you can select the branch or tag from those available. Below, I describe the two cases for providing a repository url.
No model sources specified in the settings
In this case, the user can enter any Git repository (i.e. without any restrictions), and the selection field for the base integration url is hidden. The only requirement in this case is that the input has a valid url prefix (i.e. http:// or https://) and does not contain certain sequences that are not allowed (i.e., ".." and "%").
At least one model source specified in the settings
In this case there is an additional selection input where you have to select one of the available git settings. The resulting repository url then has the url from the selected git settings as a prefix (e.g. if only https://github.com is specified in the git settings, you can only access repositories that have this url as a prefix). In the second text entry field, one can then specify the relative path starting from the url from the selected git settings (the relative path must start with "/"). This means that the resulting repository url is the selected git settings url followed by the relative path specified in the text input field.
To allow the user to also copy and paste URLs, the text input can also be given an absolute url, and the git setting will then automatically be set to the one with the longest matching prefix.
Summary of the possible behaviors

the revision is required in all cases
the revision must match a revision retrieved from the backend
in any case, it is not allowed to have blacklisted sequences in the url
if at least one git setting exists, one must select one and the resulting url must have the git setting url as prefix
if no git setting exists, the selection input should not be visible and required
when entering an absolute url, the git setting with the longest prefix match should be automatically selected (if available)

Resolves #222
Checklist

[x] My code follows the guidelines of this project: CONTRIBUTING.md
[x] I updated the documentation with the new functionality
[x] I went through the code and removed all print statements, breakpoints and unused code
[x] Error handling for all possible scenarios has been implemented
[x] I've add logging for all relevant operations
[x] I added the appropriate labels to this PR (enhancement/bug/documentation, effort, priority)

The additional comments are addressed and resolved in #311, as this branch is far behind and therefore there is no point in working on it.


[Bug][force-success] force success add end time

Purpose of the pull request

fix:#15142
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Codecov Report

Merging #15144 (925e1e7) into dev (2622685) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

:exclamation: Current head 925e1e7 differs from pull request most recent head a41d532. Consider uploading reports for the commit a41d532 to get more accurate results

@@             Coverage Diff              @@
##                dev   #15144      +/-   ##
============================================
- Coverage     38.17%   38.09%   -0.08%
+ Complexity     4682     4661      -21
============================================
  Files          1281     1281
  Lines         45347    45269      -78
  Branches       4941     4923      -18
============================================
- Hits          17312    17247      -65
+ Misses        26148    26136      -12
+ Partials       1887     1886       -1

Files
Coverage Δ

...uler/api/service/impl/TaskInstanceServiceImpl.java
48.34% <100.00%> (+0.34%)
:arrow_up:

... and 58 files with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Feature/apply plandefinition without encender

applying Plan Definition to generate care plan without encender as I have not been able to build the encender code successfully.
the logic for determining which questionnaire(s) to serve depends on the CQL expression(s) specified in the plan definition

@achen2401  before you progress this further, let's talk about options Wednesday. I'd like to have a common understanding of the challenges w/ encender before we bail on it. I have my dev environment set up now and have been tinkering with https://github.com/uwcirg/asbi-screening-app/pull/46 , though I don't have much to show for it yet.
I do appreciate what you're proposing here, all the same!


Bump inmanta-dev-dependencies[async,extension,pytest] from 2.67.0 to 2.68.0 (#394)

Pull request opened by the merge tool on behalf of #394

Merged in 9259d01b8f80c72da71abb4d4308a7b4d6f310b5


have problem with tensorflow.keras.layers.LSTM

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Ubuntu 18.04.3 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):binary
TensorFlow version (use command below):v2.0.0-rc0-199-g0bd29e2 2.0.0
Python version:3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
ROCm/MIOpen version:2.9.6
GPU model and memory:Radeon vii 16GB

met some bug when I was using keras.layers.LSTM

2019-11-18 04:36:20.298226: W tensorflow/core/framework/op_kernel.cc:1622] OP_REQUIRES failed at cudnn_rnn_ops.cc:1491 : Unimplemented: createRnnDescriptor is unimplemented
2019-11-18 04:36:20.298246: W tensorflow/core/common_runtime/base_collective_executor.cc:216] BaseCollectiveExecutor::StartAbort Unimplemented: createRnnDescriptor is unimplemented

I replace it with tf.compat.v1.keras.layers.LSTM or tf.keras.layers.RNN(LSTMCell), it worked fine ,except it was very slow,actually as slow as training on a CPU, and I deeply doubt that the program was running on CPU.
here is a comment on https://tensorflow.google.cn/api_docs/python/tf/keras/layers/LSTM?hl=en

Based on available runtime hardware and constraints, this layer will choose different implementations (cuDNN-based or pure-TensorFlow) to maximize the performance. If a GPU is available and all the arguments to the layer meet the requirement of the CuDNN kernel (see below for details), the layer will use a fast cuDNN implementation.

Code to reproduce the issue
`import tensorflow as tf
model = tf.keras.Sequential()
model.add(tf.keras.layers.Embedding(10, 16, mask_zero=True))
model.add(tf.keras.layers.LSTM(16, return_sequences=True, return_state=False, recurrent_dropout=0.1))
model.add(tf.keras.layers.Dense(10))
def gen():
for i in range(10):
yield ([i] * i, [i] * i)
ds = tf.data.Dataset.from_generator(
gen, (tf.int64, tf.int64), (tf.TensorShape([None]), tf.TensorShape([None])))
ds = ds.padded_batch(
batch_size=4,
padded_shapes=tf.compat.v1.data.get_output_shapes(ds),
drop_remainder=False
)
def crossentropy_loss(labels, logits):
return tf.keras.losses.sparse_categorical_crossentropy(labels, logits, from_logits=True)
model.compile(optimizer='adam', loss=crossentropy_loss)
model.fit(ds, epochs=3)
`
Other info / logs

Hi @wellhowtosay , I see you have been using 2.0.0RC0 whl package, can you try the latest releases inside the following docker container:
`rocm/tensorflow:rocm2.9-tf2.0.0-dev

Hi @wellhowtosay , I see you have been using 2.0.0RC0 whl package, can you try the latest releases inside the following docker container:
`rocm/tensorflow:rocm2.9-tf2.0.0-dev

Hi @wellhowtosay , I see you have been using 2.0.0RC0 whl package, can you try the latest releases inside the following docker container:
`rocm/tensorflow:rocm2.9-tf2.0.0-dev

thank you,I tried tensorflow.keras.layers.LSTM, and this time it works with no bug report. But,I didn't see any performance improvement. So I tried tf.compat.v1.keras.layers.CuDNNLSTM, and I received following exception
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/keras/engine/training_arrays.py", line 143, in model_iteration
model, inputs, steps_per_epoch, epochs=epochs, steps_name=steps_name)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/keras/engine/training_utils.py", line 1650, in infer_steps_for_dataset
size = K.get_value(cardinality.cardinality(dataset))
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/keras/backend.py", line 3164, in get_value
return x.eval(session=get_session((x,)))
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/keras/backend.py", line 486, in get_session
_initialize_variables(session)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/keras/backend.py", line 903, in _initialize_variables
[variables_module.is_variable_initialized(v) for v in candidate_vars])
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/client/session.py", line 956, in run
run_metadata_ptr)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/client/session.py", line 1180, in _run
feed_dict_tensor, options, run_metadata)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/client/session.py", line 1359, in _do_run
run_metadata)
File "/usr/local/lib/python3.5/dist-packages/tensorflow_core/python/client/session.py", line 1384, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: No OpKernel was registered to support Op 'CudnnRNNV2' used by node cu_dnnlstm/CudnnRNNV2 (defined at /usr/local/lib/python3.5/dist-packages/tensorflow_core/python/framework/ops.py:1748) with these attrs: [dropout=0, seed=0, T=DT_FLOAT, input_mode="linear_input", direction="unidirectional", rnn_mode="lstm", seed2=0, is_training=true]
Registered devices: [CPU, XLA_CPU]
Registered kernels:
device='GPU'; T in [DT_DOUBLE]
device='GPU'; T in [DT_FLOAT]
device='GPU'; T in [DT_HALF]
 [[cu_dnnlstm/CudnnRNNV2]]

@jerryyin , can you take a look here?

@wellhowtosay does the tf.test.is_gpu_available return False? If that's the case, then it means the GPU is not configured correctly. Also, the error message somehow indicating that the GPU device is not there: Registered devices: [CPU, XLA_CPU].

@jerryyin tf.test.is_gpu_available returned Falses, and I ignored following error report
2019-12-03 14:01:23.802669: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libhip_hcc.so
2019-12-03 14:01:23.803516: E tensorflow/stream_executor/rocm/rocm_driver.cc:1031] could not retrieve ROCM device count: HIP_ERROR_NoDevice
2019-12-03 14:01:23.803534: E tensorflow/stream_executor/rocm/rocm_driver.cc:1031] could not retrieve ROCM device count: HIP_ERROR_NoDevice

@sunway513 Could you help point to resources to setup his GPU correctly? Based on the conversation this is not a problem of LSTM module.

@wellhowtosay , were you able to execute the rocminfo in your environment?
/opt/rocm/bin/rocminfo
If not, please review the following ROCm document and make sure your ROCm software stack is properly configured:
https://github.com/RadeonOpenCompute/ROCm.git
For questions regarding ROCm configuration, please open an issue on the ROCm main repository.


Not clear how this QA Mode can be used with Server Side Batch Delivery API

Issue in ./help/c-activities/c-activity-qa/use-qa-mode-with-server-side-delivery.md
The documentation is unclear on how the QA Mode can be used with the Server Side Batch Delivery API

Thanks for the feedback, Bennet. Can you please ask this question in the PM Office Hours wiki?
https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=ACS&title=Target+Product+North+America+Office+Hours
It seems that your issue spans PMs (Siddharth and David) and this will be the best way to get to the bottom of it.

Thanks Mark. Will do.
On Wed, 12 Jun 2019 at 08:50, mtalbot29<EMAIL_ADDRESS>wrote:

Thanks for the feedback, Bennet. Can you please ask this question in the
PM Office Hours wiki?
https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=ACS&title=Target+Product+North+America+Office+Hours
It seems that your issue spans PMs (Siddharth and David) and this will be
the best way to get to the bottom of it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AdobeDocs/target.en/issues/45?email_source=notifications&email_token=AEW72VMGIUURM4W76QO7CGTP2DWI3A5CNFSM4HXB2452YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQJQ3I#issuecomment-501258349,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEW72VP2A5BKTTE43GJBNWLP2DWI3ANCNFSM4HXB245Q
.

--
Regards
Bennet Roy Joseph
New York,
USA


Grammar/spelling

Made some grammar and spelling fixes, with a little rewording in places.
Fixes point 2 on #196
For what it's worth, your written English is very good for a non-native speaker :+1:

Great! Thanks for the work and for kind words...


Linting 2

Everything but libmachine & drivers (except inline documentation).
Is on top of the drivers cleanup.

On-top of #2074

Second step to fix #1887
See https://github.com/docker/machine/pull/2074#issuecomment-150729020 for context

LGTM

@dmp42 Can you rebase please?


Delete profile picture functionality

Description
I add a checkbox in editprofile.ejs form. If this checkbox checked and form submit. Then the profile pic removed from data base. You can verify in attached video.

This PR does the following:

Updates ... profile/edit route & editprofile.ejs file to implement remove profile picture feature.

Related Issues
Link any related issues using the format Fixes #issue_number.
This helps to automatically close related issues when the PR is merged.

Placeholder: "Fixes #285 "

Screenshots (if applicable)
Add any screenshots that help explain or visualize the changes.
https://github.com/user-attachments/assets/60f094dc-556d-4336-8ad3-af02563d9a3c
Checklist
Make sure to check off all the items before submitting. Mark with [x] if done.

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I am working on this issue under GSSOC

@Soujanya2004   Marge it. And don't forget to add all the labels as per ISSUE #285

@Suvadip-sana since #333 and #334 has similar functionality i have given label 2 and 3 respectively
even if i give label 3 each the program incharge will reduce it

@Soujanya2004   yaa yaaa sure.


Avoid recursive link in components when re-running make install.

@lesters
This fixes the infinite directory recursion.

👍


Add Grafana dashboards suitable for Astra Streaming exposed metrics

Astra Streaming only exposes a subset of the Pulsar metrics for external integration purposes. The existing example Grafana dashboards are not really suited for this purpose because:

Some dashboards include metrics that are not exposed
Some dashboards contains labels that are not available in the exposed AS metrics.

This PR includes 3 Grafana dashboards that are tailored for AS metrics external integration:

Overview
Namespace
Topic

It also includes an improvement that allow metrics aggregation over parent topic names (for partitioned topics).

@zzzming @NadirJ can you please review


Use pip list --format=json when pip is sufficiently new?

It looks like pip >= 9.0.0 also supports --format=json, which is probably more reliable than parsing the column output. Thoughts?

I can't recall at this point if there was a reason I chose --format=columns. I suspect both will be equally reliable but I wouldn't be opposed to switching to --format=json if they are equivalent.
FWIW, pip-api already differentiates between < and >= 9.0.0:
https://github.com/di/pip-api/blob/e6305c0af25a3f638bab4233e45b3fc678a10e36/pip_api/_installed_distributions.py#L82-L85

I can't recall at this point if there was a reason I chose --format=columns. I suspect both will be equally reliable but I wouldn't be opposed to switching to --format=json if they are equivalent.

Yep, from some local testing they look equivalent. Here's both run on a contrived environment:
$ pip list --format=columns
Package         Version
--------------- --------
appdirs         1.4.4
black           21.5b2
click           8.0.1
cmakelang       0.6.13
flake8          3.9.2
mccabe          0.6.1
mypy-extensions 0.4.3
pathspec        0.8.1
pip             21.1.2
pycodestyle     2.7.0
pyflakes        2.3.1
regex           2021.4.4
setuptools      49.2.1
six             1.16.0
toml            0.10.2

$ pip list --format=json | jq
[
  {
    "name": "appdirs",
    "version": "1.4.4"
  },
  {
    "name": "black",
    "version": "21.5b2"
  },
  {
    "name": "click",
    "version": "8.0.1"
  },
  {
    "name": "cmakelang",
    "version": "0.6.13"
  },
  {
    "name": "flake8",
    "version": "3.9.2"
  },
  {
    "name": "mccabe",
    "version": "0.6.1"
  },
  {
    "name": "mypy-extensions",
    "version": "0.4.3"
  },
  {
    "name": "pathspec",
    "version": "0.8.1"
  },
  {
    "name": "pip",
    "version": "21.1.2"
  },
  {
    "name": "pycodestyle",
    "version": "2.7.0"
  },
  {
    "name": "pyflakes",
    "version": "2.3.1"
  },
  {
    "name": "regex",
    "version": "2021.4.4"
  },
  {
    "name": "setuptools",
    "version": "49.2.1"
  },
  {
    "name": "six",
    "version": "1.16.0"
  },
  {
    "name": "toml",
    "version": "0.10.2"
  }
]

If the columnar format is sufficiently stable, then I see no reason to switch! My only thought there was that the JSON form is more defensive against small changes to pip list, e.g. them adding another header line 🙂

My only thought there was that the JSON form is more defensive against small changes to pip list, e.g. them adding another header line

Agreed, although the test suite for this project should easily identify any subtle changes like that.

Agreed, although the test suite for this project should easily identify any subtle changes like that.

Makes sense! Does the test suite include checks against pip's current development/stable head? I can foresee an edge case where pip-audit calls into pip_api, which then shells out to a future version of pip that hasn't been added to the test matrix yet and has made a change to the columnar format. That would get caught by the time the next pip release is made, but in the mean time it would break every install of pip-audit until we push a version with a bumped dependency.

Does the test suite include checks against pip's current development/stable head?

It does not. A daily cron workflow that checks this across supported Python versions would probably be worthwhile to add.

Sounds good. I'll also go ahead with the JSON approach, since that'll also be defensive against that (unlikely) edge case.

Another thing I noticed: pip list -v --format=json produces even more detail, like so:
  {
    "name": "appdirs",
    "version": "1.4.4",
    "location": "/Users/william/.pyenv/versions/3.9.4/lib/python3.9/site-packages",
    "installer": "pip"
  },

...so I'll use that to fill in the location as well. There's also the installer field, which could also be useful in the context of pip-audit, although that doesn't need to be addressed directly here.


StepTrigger leaks deleted entities

Like device lists this spams pvs errors.

me when the simple act of walking makes PVS hallucinate:

As far as I can tell step trigger should remove all entities, assuming that entity deletion raises collision-end events. If the events just aren't being raised it might be related to #21734 / space-wizards/RobustToolbox/issues/4578


Updated Search box

@PrimalPimmy @osBins I have updated CSS of search box.

Looks nice @SachinMittal1766! Can you make the placeholder say "Search..." with three dots instead of two, like it is right now (it's somewhat of a convention).
Also, can you remove the border and outline (on click) and add a similar border as the messages container to the 'search' box?
The border radius looks fine.

Going good so far @SachinMittal1766! Can you make the remaining changes and pull changes from the main branch to update your repository? It seems to be behind by a few commits.

Looks good to me now! However there's still a border/outline coming on clicking the search box. Can you remove that?

@osBins completed all the updates.

Awesome! Merging your PR.


We should provide feedback on longrunning Intellisense

Some type of 'loading' indicator in places where we can't get it any quicker.

With the inclusion of this, we should also remove the 'Intellise... Complete' in the status bar.

Related to #41

When we implement this, we should remove the polling introduced with https://github.com/Microsoft/poshtools/pull/399


Add Search for Scopes, Collection and Document Ids

In the plugin tree, the user should be able to search for a scope, collection and when possible, document ids. The search should be done via shortcut, and should not be always visible.
Please check how datagrip search works for more:
https://www.youtube.com/watch?v=U5SOD-eeK50&ab_channel=JetBrains

maybe we could get that integrated into the IDE's search


[Multitenancy] inbound message relay

Update for the multitenancy branch.

add inbound message relay (not finished, but working)
also supports relay for new didexchange / oob features
fixed alice/faber demo

Two tests are failing because of changes to the responder. Andrew made similar changes to his profile PR, so I’ll resolve those once that branch is merged
@ianco

Alice/faber demo is failing on the initial connection when running in "normal" mode (i.e. no multitenancy), faber callback throws the following error:
Faber      | 2020-12-03 16:51:11,647 aiohttp.server ERROR Error handling request
Faber      | Traceback (most recent call last):
Faber      |   File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 418, in start
Faber      |     resp = await task
Faber      |   File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_app.py", line 458, in _handle
Faber      |     resp = await handler(request)
Faber      |   File "/home/indy/aries_cloudagent/transport/inbound/http.py", line 98, in inbound_message_handler
Faber      |     recipient_keys = self.wire_format.get_recipient_keys(body)
Faber      | AttributeError: 'NoneType' object has no attribute 'get_recipient_keys'

... and also got the same error on the initial connection with starting with --multitenant option

Whoops! Forgot to run the demo after my last changes.
I triple checked this time.


Feature/serialize gltf

Hi,
Here is the current state of the serialization code.
It currently writes a .gltf with it's .bin in the same directory, with the same base name.
Please note that the following features are not supported yet:

embedded images
binary glTF output
embedded buffers
multi buffers
(and I probably missed some of them)

The code is not ready to be merged yet but I'm opening the PR in case you want to do some tests.
Feel free to share your comments on it
(btw, would it be possible to add a few labels so that contributors can qualify and tell a bit about the state of the PRs ?

I have merged this PR into devel branch.
I will refactor code and write some tests for serialization.

(btw, would it be possible to add a few labels so that contributors can qualify and tell a bit about the state of the PRs ?

That would be nice! But I don't know how to add custom labels on github(e.g. gltf20 label). Will investigate how to add custom labels.

I will close this branch.
I have renamed filename/class in devel branch.  Please open another PR against devel if you have further modification.


app.env?

app.env seems to be undocumented on expressjs.com.

AFAIK There is no env property that we set on app. Do you mean app.get('env')?

If so, the documentation is here: http://expressjs.com/4x/api.html#app.settings.table :)

oh yeah I guess it used to be app.env. thanks


METRON-2034: REST endpoint for getting all parser topology status should return group name

Contributor Comments
This PR fixes a bug in the REST application that fails to convert a parser topology id to a group name when calling the http://node1:8082/api/v1/storm endpoint.  The StormStatusServiceImplTest was also updated to included this case.
Testing
This has been tested in full dev:

Spin up full dev and verify data is flowing to Elasticsearch.
Define a group name for the OOTB bro, snort, yaf parser topology that is included in full dev:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
    "name": "group1",
    "description": "group1",
    "sensors": [
      "bro",
      "snort",
      "yaf"
    ]
  }' 'http://user:password@node1:8082/api/v1/sensor/parser/group'

Request a storm status summary for all topologies:

curl -X GET --header 'Accept: application/json' 'http://node1:8082/api/v1/storm'

The bro__snort__yaf Storm topology should be returned with the name set to group1:
{
    "id": "bro__snort__yaf-4-1556557869",
    "name": "group1",
    "status": "ACTIVE",
    "latency": 2751.941,
    "throughput": 6.045,
    "emitted": 3710,
    "acked": 3627
  }

Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

@merrimanr I've tested it with full dev and now the UI is able to display if a group of sensors is running or not properly. So this is fine but there's another issue. The reason why it has become a blocker for the latest release candidate is that bro, snort, and yaf is already aggregated.
And the topology info for the three of them coming back from the storm endpoint is just fine. It says it's ACTIVE but since the UI doesn't get any information about their "group", it's unable to render the three sensors as they are grouped together.
So currently, the name of the topology item regarding the three aforementioned sensors is "bro__snort__yaf" but there is no group with the same name so the UI can't figure it's a group and the three sensors belong to it.

You're correct @ruffle1986.  The group should already be added when full dev spins up rather than having to add it in a separate step.  I am testing a change that should fix this and will push it out once that's done.

The latest commit should setup the parser group in full dev automatically.

@merrimanr now that https://github.com/apache/metron/tree/feature/METRON-1856-parser-aggregation is under way, do we have enough detail to bridge the gap between what the UI needs and the backend piece, in particular the documentation? I'm not completely sure if global config is the best place for it or not, since this only really seems to be leverage by REST application (ie, it's not used globally), but I don't have a particularly excellent alternative to recommend currently.

We are not at a point in the review where we can spin up or test anything.  Agreed, documentation belongs in the REST README.

Let's hold off on this item until the end, or whenever we can reasonably start doing some validation with the actual UI components in this feature branch. It sounds like this may have come from some offline collaboration and testing, so we should make sure that this accomplishes the desired results now that the aggregation feature is going through review.

I filed this as a bug back in March based on feedback from the contributors working on the parser aggregation feature branch.  This fix is required for that feature to work correctly, which is why I think we should move documentation to a follow on Jira.

Can you link to what you're describing? I'm not seeing much on the ticket - https://issues.apache.org/jira/browse/METRON-2034

Are you saying you want a more detailed description the bug as it relates to the UI?  This might be easier to demonstrate when the UI part is further along.

Are you saying you want a more detailed description the bug as it relates to the UI? This might be easier to demonstrate when the UI part is further along.

I'm not seeing where the "based on feedback from the contributors working on the parser aggregation feature branch" interaction happened. Was that a private message/interaction? All I'm saying is that if there was a comment on another PR, or a discuss thread, or a convo in Slack - just add it here for context.

It was a Slack conversation.  @ruffle1986 was testing and noticed group names were not working for the endpoint that gets status for all topologies (vs the endpoint that gets status for a single topology).  He brought it to my attention and I created this fix as a result.

I filed this as a bug back in March based on feedback from the contributors working on the parser aggregation feature branch. This fix is required for that feature to work correctly, which is why I think we should move documentation to a follow on Jira.

I'm not sure I see the point of splitting up a documentation task here - seems like extra overhead with an unclear benefit, but if that's your preference, you're welcome to add a sub-task to the master  feature branch Jira that would need to be checked off before the FB is completed.


Qt: Insert spaces for consistence

Reasons for making this change:
Inserted two spaces to make the comments look consistent. That's it :)

@tim-sueberkrueb thanks!


Patch XMLHttpRequest.send for ArrayBuffer & ArrayBufferView.

XMLHttpRequest 2 can send ArrayBuffer and ArrayBufferView data.
But the previous version of MinXmlHttpRequest is not supported, so we need patch it, it is very useful. For example:
Using this patch, we can use hprose-html5.js in cocos2d-js directly on every platform.

Thank you for your contribution, can you add a test case for it ? (In the `samples/js-tests/src/XHRTest test case)
We can't merge feature PR without a test case

Tested and succeed on Mac, thanks @andot

:+1: :100:


add dynamic dataset

for comparing model performance on senorium2023 data

this also requires implementing neuron motor coordinates and unit id as properties (experiment.device.coord and experiment.device.unit_ids)

for the track of records - we agreed on linear interpolation for sequence interpolator and to add the concept of valid times and flag if we want to return nans or non


Add files via upload

@rstoweb First stage of verification passed, official domain is gymstr.cz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@rstoweb Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Issue In Media Manager

Hi,
I am installing the media manager module, but it gives some error after installation "Unauthenticated" , I have followed the
all README file steps , Please check the issue.
Thanks

Please make sure elfinder.php must exist under the config folder. Run the below command to publish this config file.
php artisan vendor:publish --provider='Ridhima\MediaManager\Providers\MediaManagerServiceProvider'

Or you can manually copy bagisto-mediamanager/src/Config/elfinder.php to app/config folder.

Almost 6 days and didn't receive any feedback from your side. So, I am closing this issue. You can re-open this if you face the same issue again.


Gaps sometimes visible between filled paths which share an edge

Greetings, and thank you for sharing Pixie!
I am not sure if this is to be expected or not (or even whether cairo shows similar behavior), although there are inconsistencies within pixie's behavior at minimum. Here is a 4x2 grid showcasing the behavior. Each cell is essentially filled with two white triangles, and sometimes a gap is visible between them even though their shared edge is specified from the same points. In case it is not obvious which cells due to monitor dpi or brightness:
|--------|-----------|-----------|--------|
| no gap | light gap | light gap | no gap |
|--------|-----------|-----------|--------|
|   gap  | light gap | light gap |   gap  |
|--------|-----------|-----------|--------|

For the top row, cw, and ccw refers to whether a triangle's path was specified in a clockwise or counter-clockwise manner. Each top row example is a single filled path.
For the second row, each example left to right:

Two paths separately filled (one for each triangle).
The same two paths added to another path which is filled.
The triangles defined in a single SVG string which is filled.
Each triangle filled from a separate SVG string.

Vertical and horizontal fills don't seem to exhibit this behavior, only diagonals.
The code which produced this image:
import pixie

var
  image = newImage(800, 400)
  cwcw, cwccw, ccwcw, ccwccw, p1, p2, p = newPath()
  font = readFont("Hack-Regular.ttf")

font.size = 18
image.fill("black")

#[ ROW 1 ]#

# cw, cw: no gap visible
cwcw.moveTo(0.0, 0.0)
cwcw.lineTo(200.0, 0.0)
cwcw.lineTo(200.0, 200.0)
cwcw.lineTo(0.0, 0.0)
cwcw.moveTo(200.0, 200.0)
cwcw.lineTo(0.0, 200.0)
cwcw.lineTo(0.0, 0.0)
cwcw.lineTo(200.0, 200.0)
image.fillPath(cwcw, "white")
image.fillText(font.typeset("cw, cw", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(0, 100)))

# cw, ccw: light gap visible
cwccw.moveTo(0.0, 0.0)
cwccw.lineTo(200.0, 200.0)
cwccw.lineTo(0.0, 200.0)
cwccw.lineTo(0.0, 0.0)
cwccw.moveTo(200.0, 200.0)
cwccw.lineTo(200.0, 0.0)
cwccw.lineTo(0.0, 0.0)
cwccw.lineTo(200.0, 200.0)
image.fillPath(cwccw, "white", translate(vec2(200, 0)))
image.fillText(font.typeset("cw, ccw", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(200, 100)))

# ccw, cw: light gap visible
ccwcw.moveTo(0.0, 0.0)
ccwcw.lineTo(0.0, 200.0)
ccwcw.lineTo(200.0, 200.0)
ccwcw.lineTo(0.0, 0.0)
ccwcw.moveTo(200.0, 200.0)
ccwcw.lineTo(0.0, 0.0)
ccwcw.lineTo(200.0, 0.0)
ccwcw.lineTo(200.0, 200.0)
image.fillPath(ccwcw, "white", translate(vec2(400, 0)))
image.fillText(font.typeset("ccw, cw", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(400, 100)))

# ccw, ccw: no gap visible
ccwccw.moveTo(0.0, 0.0)
ccwccw.lineTo(0.0, 200.0)
ccwccw.lineTo(200.0, 200.0)
ccwccw.lineTo(0.0, 0.0)
ccwccw.moveTo(200.0, 200.0)
ccwccw.lineTo(200.0, 0.0)
ccwccw.lineTo(0.0, 0.0)
ccwccw.lineTo(200.0, 200.0)
image.fillPath(ccwccw, "white", translate(vec2(600, 0)))
image.fillText(font.typeset("ccw, ccw", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(600, 100)))

#[ ROW 2 ]#

# p1, p2
# clear gap visible
p1.moveTo(0.0, 0.0)
p1.lineTo(0.0, 200.0)
p1.lineTo(200.0, 200.0)
p1.lineTo(0.0, 0.0)
p2.moveTo(200.0, 200.0)
p2.lineTo(0.0, 0.0)
p2.lineTo(200.0, 0.0)
p2.lineTo(200.0, 200.0)
image.fillPath(p1, "white", translate(vec2(0, 200)))
image.fillPath(p2, "white", translate(vec2(0, 200)))
image.fillText(font.typeset("p1, p2", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(0, 300)))

# p
# light gap visible
p.addPath(p1)
p.addPath(p2)
image.fillPath(p, "white", translate(vec2(200, 200)))
image.fillText(font.typeset("p", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(200, 300)))

# 1 SVG string
# light gap visible
image.fillPath(
  """
    M 0.0 0.0
    L 200.0 200.0
    L 0.0 200.0
    L 0.0 0.0
    M 200.0 200.0
    L 200.0 0.0
    L 0.0 0.0
    L 200.0 200.0
  """, "white", translate(vec2(400, 200)))
image.fillText(font.typeset("1 SVG string", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(400, 300)))

# 2 SVG string
# clear gap visible
image.fillPath(
  """
    M 0 0
    L 200 200
    L 0 200
    L 0 0
  """, "white", translate(vec2(600, 200)))
image.fillPath(
  """
    M 200 200
    L 200 0
    L 0 0
    L 200 200
  """, "white", translate(vec2(600, 200)))
image.fillText(font.typeset("2 SVG string", vec2(200, 100), hAlign = CenterAlign, vAlign = MiddleAlign), translate(vec2(600, 300)))

image.writeFile("fillIssue.png")

In an image full of filled paths, this behavior makes it look as though strokes were applied when they were not. For example:

If you look closely, there are a few spots in the above image where 'strokes' seem to be missing. These are areas where shared edges are closely vertical or horizontal.
I assume this has everything to do with AA of fills. Thanks for taking a look.

Wow a very good bug report! I want to look at this more in what Cairo or Context do. I want to see if this issue can be fixed. Some on the edge of our fills with AA is not quite right.

I  only have a minute to reply but the short version is that this is two separate issues:
For when there are two paths (or two SVG strings), the issue is premultiplied alpha compositing, this is basically unavoidable due to Pixie storing premulitplied alpha color values. I think filling each separate path into separate images and then compositing those images may produce better output but I would need to test.
For CW-CCW alternation, this is intersection floating point values not perfectly matching and thus having tiny tiny tiny gaps leading to non-255 coverage.
Both are extremely hard or impossible without changing internal things to Pixie.
These are basically the antagonistic cases for complex path filling.
One quick example I could find https://graphicdesign.stackexchange.com/questions/65058/image-looks-embossed-when-converted-to-svg

Upon a quick test, I could not see a difference with either compositing onto a black backing image, or drawing each shape into a separate image composited into one, and then onto black. But indeed those are good practices, and I will play around more.
While I don't know anything about Pixie's internals, I'm wondering if something like Fast Robust Predicates for Computational Geometry may be of any use around the floating point issues. I recently ported Mapbox's Delaunator to Nim, and it uses a ported version to achieve robustness around degenerate input. A tough problem indeed.
For a possibly imprecise solution, here is the above image with added strokes at a width of 1.5, composited shape by shape as suggested above:


Rancher CLI doesn't allow context switching from environment variables or flags

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

Run kubectl commands with the CLI rancher kubectl ...
Expect commands to allow switching contexts on a per context basis e.g. rancher --context "c-123456:p-12345" kubectl ...

(kubectl is an example here, this holds true for all of the Rancher CLI commands)
Result:
Commands aren't able to be run with a command specific context!
Other details that may be helpful:
The Rancher v1 CLI included the ability to set an environment on every call, as well as reading from environment variables. As far as I can tell the Rancher v2 CLI only supports reading from the config written to disk.
We are setting up a deploy pipeline using the Rancher CLI and we may have several projects deploying at the same time which introduces a race condition in our deploys that could cause our Rancher commands to write to incorrect contexts.
This is similar to #15195 however I would love specific environment variable overrides and Rancher CLI flags.
Environment information

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

+1. Notice the old Rancher CLI for Rancher v1.6:
schuylr@schuylr-ThinkPad-P52s:~$ rancher inspect --help
View details for service, container, host, environment, stack, volume, secret

Inspect resources by ID or name in the current $RANCHER_ENVIRONMENT.  Use '--env <envID>' or '--env <envName>' to select a different environment.

Example:
  $ rancher inspect 1s70

Usage: rancher [global options] inspect [OPTIONS] [ID NAME...]

Options:
   --type value    Restrict restart to specific types (service, container, host, stack)
   --links         Include URLs to actions and links in resource output
   --format value  'json' or Custom format: '{{.kind}}' (default: "json")

And the new one:
schuylr@schuylr-ThinkPad-P52s:~$ rancher2 inspect --help
View details of resources

Inspect resources by name or ID in the current context. If the 'type' is not specified inspect will search: cluster, node, project, secret, namespacedSecret, workload, persistentVolume, storageClass, namespace
Examples:
  # Specify the type
  $ rancher inspect --type cluster clusterFoo

  # No type is specified so defaults are checked
  $ rancher inspect myvolume

  # Inspect a project and get the output in yaml format with the projects links
  $ rancher inspect --type project --format yaml --links projectFoo

Usage:
  rancher2 inspect [OPTIONS] [RESOURCEID RESOURCENAME]

Options:
   --links         Include URLs to actions and links in resource output
   --type value    Specify the type of resource to inspect
   --format value  'json', 'yaml' or Custom format: '{{.kind}}' (default: "json")

For some reason, support for flag-defined contexts/environments was not preserved between Rancher 1.6 and Rancher 2+ support, and I'm having a hard time migrating since my deployment automation tools run in parallel with the Rancher CLI, which can use several clusters at the same time. The --env flag was extremely useful and without it, I'll have to scrape by using cURL instead.


Query parameters for speed and mode

Request from @thakkaha to add URL Query/Search parameters to set speed and mode - enables sharing a link that ensures everyone has the same settings. Useful for a class/abhiyaanam.

Implemented in https://github.com/avinashvarna/audio_alignment/commit/b4b39df2bd105d482324a756c664fc29804616da


Plan to update for swift 2.0?

Any plan to update for swift 2.0?

Yes, I will try and do that over the labor day weekend.

about swift 3.0?


[bug] UnicodeDecodeError during server startup

Describe the bug
(venv) PS T:\Python Projects\ProjectTestEndstone> endstone
[2024-06-24 22:17:52.610 ERROR] [endstone._internal.bootstrap] 'utf-8' codec can't decode byte 0x88 in position 13: invalid start byte
Traceback (most recent call last):
  File "T:\Python Projects\ProjectTestEndstone\venv\Lib\site-packages\endstone\_internal\bootstrap\__init__.py", line 27, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "T:\Python Projects\ProjectTestEndstone\venv\Lib\site-packages\endstone\_internal\bootstrap\__init__.py", line 74, in cli
    exit_code = bootstrap.run()
                ^^^^^^^^^^^^^^^
  File "T:\Python Projects\ProjectTestEndstone\venv\Lib\site-packages\endstone\_internal\bootstrap\base.py", line 196, in run
    self._create_process()
  File "T:\Python Projects\ProjectTestEndstone\venv\Lib\site-packages\endstone\_internal\bootstrap\windows.py", line 106, in _create_process
    self._add_loopback_exemption()
  File "T:\Python Projects\ProjectTestEndstone\venv\Lib\site-packages\endstone\_internal\bootstrap\windows.py", line 97, in _add_loopback_exemption
    if sid not in ret.stdout.decode():
                  ^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x88 in position 13: invalid start byte

To Reproduce
Steps to reproduce the behavior:
Execute command: pip install endstone
After: endstone
Expected behavior
Running code
Screenshots

Details (please complete the following information):

OS: Windows 10 Home
Endstone Version: IDK Sorry (i imagine if latest)

Thanks for reporting this. I suspect this might be a bug on systems whose default encoding scheme isn't UTF-8.
Can you please execute the following Python commands and provide the output? Thanks.
import sys
print(sys.stdout.encoding)

This issue should be fixed by https://github.com/EndstoneMC/endstone/commit/f5202796895ce911faf4d27f1c82dc2da6857b47.


Unhandled 'error' event when watchman hasn't been installed

It took me a while to figure this out but after running npm start -s the startup process would be terminated and the following error:

Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1033:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1375:11)

I did a bit of searching and I found out that this is a watchman issue. After discovering this I ran brew install watchman and ran npm start -s again and everything worked.
It may be worthwhile adding this to the readme as one of the troubleshooting options.
Node version:
7.7.2
npm version:
4.1.2
Operating system:
MacOS Sierra
Command line used:
iterm
Steps to reproduce:
npm run setup
npm start -s

Did you make any changes to slingshot before this issue occurred of was this with a fresh clone of slingshot?
I am not using node v7, so that is another potential cause.

@atainton, just following up on this. Are you still having the issue and if so, as @kwelch asked, are you using a fresh clone of react-slingshot?

Had the same issue. MacOS. Thanks

@AntonyBaasan  Was this a fresh clone? What node/npm version are you running?

I run into the same issue today when I clone slingshot, which didn't happen before.
npm version: 5.2.0
node version: 6.10.1
Operating system: MacOS Sierra

@AntonyBaasan Are you saying the steps outlined by @atainton resolved your issue?

Im using a fresh clone and had the same issue.
Without -s flag I see this log
npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "test" "--" "--watch"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test: `jest "--watch"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script 'jest "--watch"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sl-cloud package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     jest "--watch"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs sl-cloud
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls sl-cloud
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/s.tkachenko/Desktop/work/sl-cloud/npm-debug.log

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/bin/npm-cli.js" "run" "test:watch"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test:watch: `npm run test -- --watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:watch script 'npm run test -- --watch'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sl-cloud package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run test -- --watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs sl-cloud
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls sl-cloud
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/s.tkachenko/Desktop/work/sl-cloud/npm-debug.log
ERROR: "test:watch" exited with 1.

npm ERR! Darwin 16.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `npm-run-all --parallel test:watch open:src lint:watch`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm-run-all --parallel test:watch open:src lint:watch'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the sl-cloud package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all --parallel test:watch open:src lint:watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs sl-cloud
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls sl-cloud
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/s.tkachenko/Desktop/work/sl-cloud/npm-debug.log

I looked up the jest docs and it appears that by default it uses watchman to crawl through the files.
It is possible to disabled this feature by passing the --no-watchman to the jest command, or install watchman.
I agree with @atainton  that this may be a documentation point, but it is not a bug of slingshot (directly)
A PR to add this to the docs would be appreciated 👍, but for now (unless someone see otherwise) I am going to close this.

Here's a link to the relevant docs: https://facebook.github.io/jest/docs/troubleshooting.html#watchman-issues

Thanks, I had that issue in my clipboard, but apparently it was a little late and I forgot 😅


Exclude chart-operator with resourceFilters

Related issue: https://github.com/giantswarm/giantswarm/issues/27202

Tested on gremlin, I deleted the pods and also the deployment and it was able to re-create without any exceptions.

Wouldn't policies with auto-gen or those specifically targeting e.g. Deployments still catch chart-operator?

Yes, just checked and you are right. Will add the deployment too, or would you like to just do any kind in the namespace?

Added another resource that needs to be excluded.


Perform flattening in DSL pass

Motivation
Add a syntactic transformation pass near the end of the DSL pass that flattens methods, which will allow us to avoid full expression traversals on later passes.
Test plan

See included automated tests.

This works and runs over the monorepo (with some small errors resulting from a particular use of Class.new that can be easily fixed there) but does not yet get rid of the later flatten pass (which still flattens classes, but does not need to flatten methods) nor does it actually speed up anything yet.

Question: have you tested this change on pay-server?

I'll work on simplifying this, but I do want to mention more than half the things you pointed out are things I borrowed directly from the existing flattening pass, as I wanted to try to stick pretty close to the existing implementation to start with. For example, the way that it adds space in a queue and stores an index in the preTransformMethodDef and only fills in that queue in the postTransformMethodDef is exactly what we already do in flatten (c.f. here, although we just use a raw stack of indices instead of a stack of structures that include an index), and similarly, the data structures are almost identical to just the method-specific portions of the existing flattening structures (c.f. here).

is exactly what we already do in flatten
(c.f. here, although we just use a raw stack of indices instead of a stack of structures that include an index)

exactly, it was surprising for me that the datastructures became much more complex as part of this migration.

Several of the data structures will become even simpler once I do the follow-up PR that changes the scoping logic, but effectively all the extra complexity here (relative to the initial flatten implementation) is because this pass now needs to maintain scoping logic that was previously determined by the namer and could be entirely ignored by the older flattening pass.

What I've ended up doing is cleaning up the data structures a bit but largely encapsulating the logic inside of them, which also cleans up some of the logic elsewhere immensely. For the parts that are contentious (e.g. the empty emplace_backs and the indices) I've added much longer explanatory comments and done some renaming. For the specifics of why I kept the indices and the emplace_back as used by the previous flattener, you can read the comments attached to MethodData.

This looks good to me. I see that dmitry is reviewing it right now: @DarkDimius feel free to either approve or request comments—i've left all i wanted to leave.

I had to merge over the dsl-to-rewriter change, hence the big force-push. I double-checked and there's a single instance of something on pay-server that'll need to change (a constant in a deprecated class that uses instance_eval doesn't resolve the same way it used to) so I'm going to go ahead and merge, with a few much smaller changes as follow-on PRs.


Fixed typo

Fixed a typo from what it's possible to what is possible.

Coverage remained the same at 78.189% when pulling 4691c3c95b0c58e4eb458f9fdc40d22d8b4cb48c on Gouravchawla:patch-1 into 8007ce3d2faff541eb2d1e7efba9df615a26649e on divio:develop.

Why is the CI build failing? @evildmp

Merged into #6612


Switch to StaticPicker as a default component

Currently, the Picker component uses virtual scroller for additional performance, although it also is a source of issues (#50, #57, #77).
At the same time, as I remember, it didn't add significant performance boost, so it should be OK if the default Picker was "static" (not using the virtual scroller) and we could keep and additional VirtualScrollPicker component as a more performant option, for the cases where this is really needed.

In some scenario, from which I couldn't isolate the impacting components, using Picker also causes a permanent CPU load (reported as "Medium impact" by Firefox) as long as the tab is visible, even when the picker is not open yet. I guess there's something with the DynamicScroller that might work in the background.
See https://github.com/nextcloud/spreed/issues/4501
It was not reproducible in other simpler page embedding scenarios, so I didn't raise an issue for it.

Done and released in v8.0.1.

Done and released in v8.0.1.


[Enhancement] Get Both Letter to Mama rewards in one cycle

This removes the need to go through the Anju and Kafei sidequest twice to get both of the mutually exclusive rewards from delivering the Letter to Mama. Now the player can either get the Postman's Hat when hand delivering the letter to Madame Aroma or get the Chateau Romani from the Postman after he delivers the letter.
https://github.com/HarbourMasters/2ship2harkinian/assets/7004497/4163b202-450a-4255-ba93-35d57f6a5ac7
https://github.com/HarbourMasters/2ship2harkinian/assets/7004497/93015751-3211-4381-8e08-314373277898
I filed this under Time Cycle, since it doesn't strictly allow the player to circumvent any requirements needed to get either item, with one edge case exception. Getting the Chateau Romani requires Romani's Mask only if it's after 10 P.M., while the Postman can be interacted with at any time on the night of the final day. Madame Aroma is, however, normally reachable without the mask if done so before 10 P.M.
This will require another look when randomizer considerations are on the table. I made each actor mirror the other's conditions when deciding whether to give their rewards. This made me realize that the Postman himself doesn't check any persistent flags when deciding on whether to give his hat to the player; he checks the player's inventory directly for the hat. A persistent flag does exist in the Bomber's Notebook (WEEKEVENTREG_BOMBERS_NOTEBOOK_EVENT_RECEIVED_POSTMANS_HAT), but the Postman does not check that when deciding on whether to give the Postman's Hat.

Build Artifacts

2ship-linux.zip
2ship-mac.zip
2ship-windows.zip

What about instead of having each NPC check and grant both rewards, we could just make the Priority Mail persist in the players inventory?
This way players would still need to interact with both NPCs in the expected way/at the correct times, but the player can do both in the same cycle. No item replaces the Priority Mail item in it's slot, so there shouldn't be any conflicts there. Probably would simply future rando handling as we don't have to worry about if the player has "access" to the NPCs.
Curious what others think. Personally I would lean towards this.

That sounds like a good idea to me yea, not too familiar with all the mechanics behind these things, but if its only checking for the item being shown to them that sounds good

No item replaces the Priority Mail item in it's slot, so there shouldn't be any conflicts there.

The Room Key uses that same slot. In vanilla this isn't a problem because the letter replaces it anyway, and all the key grants access to is an optional cutscene and a rupee chest. However, depending on whatever a rando would do, persisting the letter could present a problem. If there were a seed where one of these characters gave the Room Key, but it got replaced with the letter again due to this setting, the player would be unable to access whatever reward the Knife Chamber might have.
This does not matter right now, and whether we go with what is currently here or persist the letter, this setting will need another once-over when that time comes. I do like the idea of making things simpler, but as it is, this does mirror existing logic and seems clearer to me.

That sounds like something the way adult trade in OoT is handled would solve.


More instructions

Hello,
can you provide more instructions about plugin?
For example, how to make menu work. I add @click="moveTo(2)", but no action and I receive error (method "moveTo" is not defined on the instance but referenced during render).
It is not clear how to fix this.

Do you define moveTo in methods?https://github.com/river-lee/vue-fullpage/blob/master/examples/index.html#L137


datepicker issue

i Have a filed with a datepicker.
i have 2 problems with this element.
See this link http://prntscr.com/h40onf when i click on the year i wan it to open like this http://prntscr.com/h40qcv and not the way it shows
Second problem is that i want it to open if the user clicks on the textbox or on the calendar icon
Using this but not working
$('#dateofbirth').datepicker(
{
allowInputToggle: true
})
Using this code on html

                                            Date

                                                    <input type="date" class="form-control" ng-model="client.dateofbirth" ng-required="true" />

i'm using  AdminLTE v2.3.8
And i like the today button so i want it to stay
Sorry but i dont see a way to upload images

For your first issue, you might lodge a question/issue over at the repo for datepicker:
https://github.com/uxsolutions/bootstrap-datepicker
...as that would be a customization of the display of that dependancy.
For your second issue, you are binding .datepicker() to #dateofbirth but i do not see an id of #dateofbirth in your provided markup.


rancher-compose ps

@fentas wrote in rancher-compose repo:
I am wondering. It's not really possible to figure out how many container are currently running with rancher-compose.
The only 2 possible ways to figure this out (I know of) are rancher/server api or within a managed container per rancher-metadata.
Now it would be nice if
$ rancher-compose scale web

would return current scale or
$ rancher-compose scale web=+1 # +/-number

would scale service relative to current state.
@ibuildthecloud and @fentas decided on creating a rancher-compose ps for his request.

I feel this is super weird when you are just starting out with rancher that you can't list services with rancher-compose :(

Instead of adding this into Rancher Compose, we recommend using the new Rancher CLI which supports rancher ps.

@deniseschannon That is not really helpful as it list every container with their long name, as not like docker-compose does, only shows it with their short name.

@kevinsimper I'm not exactly sure what you mean.
$ docker-compose ps
      Name                Command          State        Ports
------------------------------------------------------------------
nginx_1         nginx -g daemon off;   Up      443/tcp, 80/tcp

# Show services in Rancher environment
$ rancher ps
ID           TYPE      NAME           IMAGE            STATE     SCALE     ENDPOINTS   DETAIL
1s722     service   Default/test   ubuntu:14.04.3   healthy   1
# Show containers in Rancher environment
$ rancher ps -c
ID        NAME                 IMAGE                           STATE     HOST      IP             DOCKER         DETAIL
1i4       Network Agent        rancher/agent-instance:v0.8.3   running   1h1       <IP_ADDRESS>    5f82e2b70f7f
1i5       Network Agent        rancher/agent-instance:v0.8.3   running   1h2       <IP_ADDRESS>   a39a33cc7b23
1i6       Network Agent        rancher/agent-instance:v0.8.3   running   1h3       <IP_ADDRESS>    647b99844e2c
1i322     test314373_test1_1   ubuntu:14.04.2                  running   1h3       <IP_ADDRESS>   aef400cae9fb
1i1759    Default_test_1       ubuntu:14.04.3                  running   1h1       <IP_ADDRESS>    7f400f0f03c4


Integration tests: tracking issue

Right now, we have travis-ci and a smattering of unit tests.

Integration with Kubernetes is also important, but we should be able to lean on the e2e and other tests already written there, so we can just do the CI work for those, not have to write the tests too.

[x] Unit tests are run for each PR
[ ] Integration tests for rktlet -> rkt

[ ] Integration test framework exists for doing common setup/teardown to make writing tests easy
[ ] Tests with basic coverage exist
[ ] A CI system capable of running containers is chosen/configured (i.e. not Travis)
[ ] Tests run against master
[ ] Tests run on each PR

[ ] Integration tests for Kubernetes -> rktlet

[ ] Tests have been run successfully locally (#52)
[ ] Tests run against each revision of master

cc @lucab


Suggestion to optimize callback function allocation when using useSignalEffect

Hello,
I have a little suggestion for you to change useSignalEffect a bit. From my understanding useSignalEffect will usually be used like in code below:
function MyComponent() {
    const localSignal = useSignal(0);
    // I think this will be the most common usage - creating a callback inside `useSignalEffect`
    useSignalEffect(() => {
        console.log(localSignal.value);
    });

   return
value: {localSignal}
;
}

This code has one drawback: it will allocate () => { console.log(someSignal.value) } every time MyComponent rerenders even when the callback is always the same (or maybe I am incorrect and it needs to be recreated every time, then please make me aware of this). So it would be nice if we could do something like this:
function MyComponent() {
    const localSignal = useSignal(0);
    useSignalEffect()?.with(() => {
        console.log(localSignal.value);
    });

   return
value: {localSignal}
;
}

Which with a little change to useSignalEffect can be implemented like that:
export function useSignalEffect(cb?: () => void | (() => void)) {
    const callback = useRef(cb);

    if (cb) {
        callback.current = cb;
    }

    useEffect(() => {
        return effect(() => callback.current?.())
    }, []);

    return !callback.current ? { with: (cb: () => void | (() => void)) => callback.current = cb } : null;
};

The reasoning behind it is that in useSignalEffect()?.with(...) expression we are using ?. which will invoke a function only if non null or undefined value is returned. With this in mind we can return from useSignalEffect an object with with() function (with is just example name) which will set callback.current value OR if callback.current is already set then we return null. Essentialy this achieves that the callback in MyComponent will be only allocated in first render and never again, because code after ?. when returned values is null will never be executed by JavaScript.
The change in useSignalEffect is also backwards compatible. When using useSignalEffect(() => {...}) without ?.with(...) it will function exactly the same as it used to.
I hope this idea is not confusing you, but this really could improve the performance of components which have lots of useSignalEffect usages and also rerenders quite frequently. The same problem exists in reacts useCallback which can be used like this useCallback(() => { ... }, []) and it also will always allocate callback again and there is no way around it. But with useSignalEffect there is no need to specify dependencies which makes it an ideal candidate for such optimization.
Please let me know what you think about it.

I think there are good reasons behind of this idea, but it's overcomplicates API.
I actually thought about this problem and decided that its enough to just write (useSignalEffectOnce)[https://github.com/XantreGodlike/preact-signals/blob/c2adf4abc5255f7270377cdb92d3614984f050ba/packages/utils/src/hooks/utility.ts#L53-L60]. Because it is reusing
the clojure - it can be JIT-ed more easily. Closure that have created on each component render will be clean with minor GC, because has short live (i suppose), so there shouldn't be big problem

Wouldn't the given solution allocate the callback anyway + 1 in useEffect + 1 in effect( () => ?

My solution creates two callbacks, but they will live in minor heap and will be deallocated with the next Minor GC.
Maybe it will be good to create our own collection of standard hooks to pass params with ?. and benchmark it against standard ones

it will allocate () => { console.log(someSignal.value) } every time MyComponent rerenders even when the callback is always the same

The cost of this should be negligible in all real-world scenarios. You'd have to be rerendering multiple times per second, continually, likely with a more complex closure in order to run into trouble. At which point our advice would be, in all likelihood, to not do that.
Deviation from this API is a deviation from the (p)react "feel", if you will, so I don't think it'd be received very well.

I hope this idea is not confusing you, but this really could improve the performance of components which have lots of useSignalEffect usages and also rerenders quite frequently.

Have an example with a benchmark to back this up? I don't think you're going to run into a real scenario where the cost of creating a closure causes issues, and I don't think we're really that keen on benchmark-driven development.

To re-iterate what @rschristian said, moving away from inline closures would deviate from the common way to use (p)react hooks, so without a very compelling reason/data, I don't think we'll change our API for now.
As you've demostrated though, it's not hard to implement this in user land though, so feel free to continue with that, and feel free to continue sharing what you find with that exploration with us here :) Thanks for sharing!


935 axe accessibility testing v1

Context
Proof of concept, axe accessibility testing.
Changes proposed in this pull request
CI

integrate https://github.com/dequelabs/axe-core-gems
an unauth test
an auth test
a crawler that tests against all the view components

Guidance to review
Concept code only, not for production
You need Firefox install
bundle exec rspec spec/axe
https://github.com/DFE-Digital/register-trainee-teachers/runs/1792348690?check_suite_focus=true

 [SPIKE] Run axe in CI

 [SPIKE] Run axe in CI

end of spike


updated marathon to version 1.4.0-RC9

High Level Description

Fixed problem with plugin resolving of RC8
Added PATCH semantic to /v2/apps
Updated marathon ui

Related Issues

Fixes #5198 - converts iterator to seq (Johannes Unterstein)
Add support for PATCH updates to apps in 1.4 (#5183) (Matthias Eichstedt)
Mark tests as unstable ... (#5202) (Matthias Eichstedt)
Links fixed in REST API documentation page. (#5060) (Armand Grillet)
Default values for query parameter need to be of type String. (Matthias Veit)
Fixes #5137 by assigning a name to the default port and refining validation logic for resource changes of resident apps. (Matthias Veit)
Use the latest stable Marathon UI build (#5181) (Orlando Hohmeier)
Fixes #4901 by removing the short circuit for root group changes. (#5179) (Matthias Veit)

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): https://github.com/mesosphere/marathon/releases/tag/v1.4.0-RC9
[x] Test Results: https://teamcity.mesosphere.io/viewLog.html?buildId=563769&tab=buildResultsDiv&buildTypeId=Oss_Marathon_Packages
[ ] Code Coverage (if available): n/a

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

Dropping in favor of https://github.com/dcos/dcos/pull/1502


Issue on servers (RLcraft)

Hi, I just started playing with friends on an RLcraft private server. When trying to fish, we get the message 'There doesn't seem to be biting anything here.' It's working on non-server. We also set up bait traps and tried putting in raw meat, carrots (as seen on YouTube), but we get a message that it's not a valid bait. We tried toggling flying on and off (left it on). Is there any way to fix this?
Edit: We tried it in rivers, shallows, oceans and it doesn't seem to be working, we tried to dig up 3x3 with baiting box inside which didn't help too. Tried different rods with differend bobbers and still same issue. Combining rod + bait in crafting doesn't work too. Tracker doesn't find anything too.

I think it would help more if you Link the config files located in your server and latest.log.

Hi again!
I just contributed to the localization, so I'm not too deep in the mechanics, but...
Just in case,
In fishingmadebetter.cfg :
Have you tried reseting:
"Tracking Time" to 5
"Fish Regeneration Time" to 60
If I remember correctly, "Tracking Time" must not be too low, so 5 should be the sweet spot.
About "Fish Regeneration Time", you can try lowering its value little by little until you find the desired sweet spot.
I hope it helps!
If the problem persists, can you post the latest.log instead of the crash report?


Dev

Doplnil jsem ti ten readme.md v admpwd.e v dev branchi:

doplněné poslední dva commandy
vyhozené zobrazení gpmc
drobné opravy

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


Fundle completions rely on fish-completion-helpers

The fundle completions rely on your fish-completion-helpers (https://github.com/tuvistavie/fish-completion-helpers) for both __fish_prog_needs_command and __fish_prog_using_command however they're not mentioned in the readme. Perhaps there should be a section in the readme for the completions mentioning the requirement on fish-completion-helpers?
I personally solved this by just installing fish-completion-helpers with fundle.

You are perfectly right, I forgot to mention it.
I just updated the readme, thanks!