JAVA: Looping in JAVA documentation

Description 📜

Various Loops structures and implementations of Loops in JAVA

Domain of Contribution 📊

[x] Java_Domain

/assign

/assign

@Siddhartha-Dhar It is not allowed for contributors to create their own issue. This issue is being closed.


ZTE-SH-CN-define-environment-variable-container

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.8 Features: set Milestone to 1.8 and Base Branch to release-1.8
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: Please check the “Allow edits from maintainers” box (see image below) to
allow reviewers to fix problems on your patch and speed up the review process.

https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/tasks/inject-data-application/define-environment-variable-container.md

This change is

CC @zhangxiaoyu-zidif

@Bradamant3 @chenopis
LGTM
It seems that the lack of directory inject-data-application results in deploy failed

@chenopis

@chenopis
could you approve this PR?

Approving to clean up the queue -- it looks as though the changes that @chenopis requested were made.


When specfying tom_select_options on AsEntityAutocompleteField: errors Uncaught TypeError: this.getUrl is not a function

Hi,
If you define an AsEntityAutocompleteField as per the docs, but add some tom_select_options,

FoodAutocompleteField.php
<?php

// src/Form/FoodAutocompleteField.php
// ...

use Symfony\Bundle\SecurityBundle\Security;
use Symfony\UX\Autocomplete\Form\AsEntityAutocompleteField;
use Symfony\UX\Autocomplete\Form\ParentEntityAutocompleteType;

#[AsEntityAutocompleteField]
class FoodAutocompleteField extends AbstractType
{
    public function configureOptions(OptionsResolver $resolver)
    {
        $resolver->setDefaults([
            'class' => Food::class,
            'placeholder' => 'What should we eat?',
            'tom_select_options' => [
                'plugins' => ['dropdown_input'],
            ],
    }

    public function getParent(): string
    {
        return ParentEntityAutocompleteType::class;
    }
}

you will receive a javascript error when the ajax calls is made to load items:
Uncaught TypeError: this.getUrl is not a function

which comes from here:
https://github.com/symfony/ux-autocomplete/blob/6a1851b8ed5e51c0a285728b0e51522e62ae6fdd/assets/dist/controller.js#L286
This comment is suspicious:
https://github.com/symfony/ux-autocomplete/blob/2.x/assets/src/controller.ts#L178-L180
Thanks,
Ben

This appears to be because the plugins provided here override the default ones (virtual_scroll) during the config merge:
https://github.com/symfony/ux-autocomplete/blob/6a1851b8ed5e51c0a285728b0e51522e62ae6fdd/assets/src/controller.ts#L172

We probably need a way to ADD plugins instead of replacing.
But first, why exactly does clearing all of the plugins create this error? Why is “this” suddenly missing the getUrl()?

Adding plugins seems like a good idea, but it looks like to me that virtual scroll plugin should always be loaded if urlValue is defined. That would be the easiest fix for now

this can be worked around by specifying all the options
            'tom_select_options' => [
                'plugins' => ['dropdown_input', 'virtual_scroll', 'clear_button'],
            ],

yes

no

Would you like to try bringing a fix here ?


Marathon kill tasks due to NPE at mesosphere.util.BackToTheFuture

https://groups.google.com/forum/#!topic/marathon-framework/z2FvTvQqdcg
hi,
I am having an issue with Marathon.
The mesos-marathon stack were installed by following instruction at https://mesosphere.io/docs/mesosphere/getting-started/rpm-install/
Underlying, a single zookeeper server (installed via CDH of cloud era) is used for one mesos master and three slaves.
the applications launched by Marathon are ElasticSearch and Logstash. per the logging of these two applications, everything was normal when Marathon decided to kill them.
 (mesosphere.marathon.MarathonScheduler:167)
java.lang.NullPointerException
#011at mesosphere.util.BackToTheFuture$$anonfun$futureToFuture$1.apply(BackToTheFuture.scala:34)
#011at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
#011at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
#011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
#011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
#011at java.lang.Thread.run(Thread.java:745)

Installed Packages
Name        : mesos
Arch        : x86_64
Version     : 0.20.0
Release     : 1.0.centos64
Size        : 879 M
Repo        : installed
From repo   : mesosphere
Summary     : Cluster resouce manager with efficient resource isolation
URL         : http://incubator.apache.org/mesos/
License     : Apache-2.0
Description : Cluster resouce manager with efficient resource isolation
            : Apache Mesos is a cluster manager that offers efficient resource isolation
            : and sharing across distributed applications, or frameworks. It can run
            : Hadoop, MPI, Hypertable, Spark (a new framework for low-latency interactive
            : and iterative jobs), and other applications.

Name        : marathon
Arch        : x86_64
Version     : 0.6.1
Release     : 1.0
Size        : 45 M
Repo        : installed
From repo   : mesosphere
Summary     : Cluster-wide init and control system for services running on Apache Mesos
URL         : https://github.com/mesosphere/marathon
License     : Apache-2.0
Description : Cluster-wide init and control system for services running on Apache Mesos

Any idea what's going on here?
Regards,

just an update, after upgrade Marathon to 0.7.3 and Mesos 0.20.1, everything looks fine now. some long running services have been running happily for 2 months.

I guess this issue can be closed now. Please reopen if you disagree.


Feedback for: docker-cloud/getting-started/connect-infra.md

File: docker-cloud/getting-started/connect-infra.md
At To link your cloud provider accounts, first go to your Docker Cloud account dashboard.
There is a Broken link at  Docker Cloud account dashboard

Closed via #535


api: add support for security profiles

We define the basis for a profile-based security dispatch. We put
forward a model, based on existing --privileged flag that can be
extended in the future to support more complex workflows.
The first aspect is to allow the container runtime to select a security
profile, keyed by name. We introduce two profiles, "default" and
"privileged" corresponding to the currently available control we have
today. We will extend this model to support more complex scenarios, with
more granular control, in the future.
We balance this model with a Node security profile ACL that can select
which profiles can be run on a node. Users can add and remove items from
this ACL to control which security levels can run on a given node. We
define the empty list to be allowing the "Default" security profile.
To support future interaction, we also define that profiles are
additive. This means that the capability of a set of profiles is a union
of all the specified profiles.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>@mgoelzer @justincormack @icecrime @aluzzardi @crosbymichael

I don't think default should be a profile, it is a lack of a profile. We made this mistake about having meaningful defaults before. It should be fine to have nothing selected mean not privileged.

Current coverage is 56.29% (diff: 100%)

Merging #1722 into master will increase coverage by 0.46%

@@             master      #1722   diff @@
==========================================
  Files            96         93     -3
  Lines         14902      14796   -106
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           8321       8330     +9
+ Misses         5474       5379    -95
+ Partials       1107       1087    -20

Powered by Codecov. Last update b693657...939be4d

@justincormack How do we define that minimum set? To which mistake are you referring?

For this PR you don't need to specify anything, as the options are the empty set of privileges ∅ or the set {privileged}. default does not need to exist.
The mistake was capabilities, which we added a default set which corresponds to a lot of root capabilities (even if you are not root), which you then have to drop.

@justincormack Agreed.
Let's work this out:

Container Profiles
Node ACL
Operation
Allowed

∅
∅
∅ ⊆  ∅
Yes

{P ∪ ∅}
∅
(P ∪ ∅) ⊄ ∅
No

{P ∪  ∅
{P ∪  ∅}
{P ∪ ∅} ⊆ {P ∪  ∅}
Yes

{E  ∪ ∅}
{P ∪  ∅}
(P ∪ ∅) ⊄ (P ∪  ∅) | E   ⊄ P
No

{E  ∪ ∅}
{P ∪  ∅}
(P ∪ ∅) ⊆ (P ∪  ∅) | E   ⊆ P
Yes

P = privileged
E = example
∅ = default
Above, we have a table representing the requested profiles, node ACLs and the operations/equality to calculate whether a profile may run on a given node. We evaluate both with and without privileged, showing that the container profile must be a subset of the Node ACL to progress. We then have third profile, of unknown contents. We evaluate in conditions when the E is both a subset of P and when it is not.

@justincormack how do you want to represent the current configuration that we have today?

@crosbymichael I added the contents of the actual fields next to the set operations. Hopefully, that makes things a little more concrete.
He is saying that the "default profile", what we do today, is represented as the empty set, which is really a base set where all sets satisfy ∅ ⊆ S and S ⊆ ∅. We don't need to define it, since it is just the base runtime.
That said, to reduce permissions with this model, we do need to define operations that negate items in the base set, but I don't think that is too much of a stretch.

@crosbymichael specify them explicitly or specify them as defaults in the daemon config explicitly so that everyone gets them, but suggest people remove them from the config
@stevvooe negative capabilities dont work.

Could we have the base set be nothing, no caps, no syscalls, and the "default" docker profile adds these?  This way you don't have to know about what is in the base set and figureout what you have to remove/unset if you are building a new profile.

Should these be defined on the Node side or at the engine level?
What about cluster defaults?
How can this be automated (e.g. large set of nodes)?
Could this be provided at node join time (related to the first question of engine level as well)?
What about backward expectations?

/cc @icecrime @dnephin

@justincormack With a base set, how would one remove functionality from the "Default" profile?

Should these be defined on the Node side or at the engine level?

This depends on where we enforce the policy. Typically, a node may not actually know its own policy and there are implications to trusting that node. Under this proposal, we can do a set based model enforced on the managers.

What about cluster defaults?

We can make default ACLs on the global cluster config. We may need to control how these combine with existing ACLs (are they a union or do they replace?).

How can this be automated (e.g. large set of nodes)?

Of course.

Could this be provided at node join time (related to the first question of engine level as well)?

This really depends on the trust model we have for the security profiles. If we allow nodes to declare what they are willing to run, we need to think about how that works in practice.

What about backward expectations?

For upgraded clusters, the fields are empty (config and acl), so everything just continues working. We can add --privileged to achieve feature parity, but the user will need to take action to specify nodes can run --privileged or set as a cluster default.

What would custom profiles look like? In this PR we assume that the behavior is hardcoded in the profile name (e.g. "privileged" means privileged)

As long as they can be expressed as set semantics, there are no limitations. I think there are some examples in @justincormack's proposal, but we should work some examples out to make sure everything lines up.

Updated with feedback from @aaronlehmann and added a sub-message on nodespec and containerspec.

After some discussion, the idea came up that requiring an update to every Node's ACL would be expensive. It might be better to introduce an ACL object that specifies the profiles allowed and the nodes to which it applies, such that when new nodes come on line that can have the ACL automatically apply or be matched via some mechanism, such as labeling.

@stevvooe is there any ETA about the merge of this PR?

@galindro There are still some details to be worked out. The base concepts are likely to be similar but their needs to be ACL aggregation to make it easier to specify what can and cannot be run on an individual node.

@stevvooe is there an ETA for this?

@marcellodesales At this time, no.
We had discussed introducing an ACL object and moving the allowed_profiles from node to that. That would allow batch update of the configuration of a large set of nodes.
I think we may also be blocked on the details of representing a security profile.
@aluzzardi What is wrong with this proposal, other than the bulk update issue?

@stevvooe @aluzzardi any updates?

This PR allows ACL to be enforced/propagated per node, enabling only a subset of the security rights (Capabilities, SECCOMP, no-new-privileges, etc.).
But shouldn't this come after we actually have support for those security rights/features?
I'm thinking:
https://github.com/docker/swarmkit/issues/1030
https://github.com/docker/docker/pull/26849
https://github.com/docker/docker/issues/25885

This PR allows ACL to be enforced/propagated per node, enabling only a subset of the security rights (Capabilities, SECCOMP, no-new-privileges, etc.).

This is a narrow interpretation of the design proposed in this PR. The goal is to span the gap of priveleged support while not just having a bool. The idea would be to support richer profiles in the future based on this model.

@stevvooe any return about this feature? Is it almost completed or needs more discussion?

Actually, I think we can close this down in favor of https://github.com/moby/moby/issues/32801.


Set a default for dashGridOptions

We should set dashGridOptions={} in the default props
If the default is set, then don't need to check for None when updating it in a callback

I forgot that you can't access component defaults in a dash callback. :see_no_evil:
Closing this now.


fix event transmission to angular

Digest was not called when event is done. This PR fixes that.
Cheers

Hi,
I am unable to merge this PR due to conflicts. Could you please resolve the conflicts and commit again?

It should be ok now, can you please confirm ?

Yes. it is fine now. Thanks.


NIFI-11441 Removed OpenCypher client service because the core depende…

…ncy appears to be unsupported for quite some time.

Summary
NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for getting this started @MikeThomsen. It looks like there are still tests that need to be deleted as part of this PR.

@exceptionfactory removed the test.


Pulsar Functions add properties to result messages

Describe the solution you'd like
I'm looking for a way to add properties to message during function processing.

This is fixed by #4093


UV/5yr separated dynamic gsplot logic from static styles

Coverage increased (+0.2%) to 93.811% when pulling 4985435df87530f45726e6c175a8bd8662c36b83 on thongsav-usgs:master into 2844ba5e9dedc567b4aa491ea75711d4ffe050c2 on USGS-R:master.

@lindsaycarr will start moving from [[]] notation, which is now possible since dropping the downsampling stuff. I am intentionally saving documentation for last as the methods are still changing quite a bit. Will incorporate the low hanging fruit and get this merged sooner rather than later because some there is some utils-read changes pending that we should get merged for SRS/SVP work being done by @kmschoep-usgs.


ExecuteQueryRetry for exception existing connection was forcibly closed by the remote host

We are also experiencing the SocketException: existing connection was forcibly closed by the remote host
Added a catch block to perform retry in the SocketException scenario.
Full error stack is here:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

I wonder if retrying on SocketException is always guaranteed to be safe?
Is it possible for the call to clientContext.ExecuteQuery() in the try block to be partially completed before the SocketException exception is thrown? Then retrying might cause another unrelated exception to be thrown which might be hard to debug because the SocketException wasn't strictly throttling related.

Hi Ronnie,
I am not too sure but "underlying connection was closed", means there is a possibility of pool recycle or any related event which errors out in ExecuteQuery. In such scenarios ExecuteQuery after a wait time seems to be working in our situation.

We are seeing several different variants of this "underlying connection was closed", each with a different "main" exception type:
Example 1:
Unhandled Exception: System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Example 2:
Unhandled Exception: System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Example 3 (same as above except main exception type):
Unhandled Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Example 4 (different exception, but common is the "underlying connection was closed" message:
EXCEPTION: System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
We are currently handling this by catching Exception and looking for string underlying connection was closed or existing connection was forcibly closed in Exception.Message. Not exactly ideal but haven't found a better solution yet.

Yet another one that should probably handled in ExecuteQueryRetry is the timeout situation:
EXCEPTION: System.Net.WebException: The operation has timed out.
at System.Net.GZipWrapperStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.StreamReader.ReadBuffer()
at System.IO.StreamReader.Read()
at Microsoft.SharePoint.Client.TextPeekReader.Read()
at Microsoft.SharePoint.Client.JsonReader.DecodeString(Int32 tokenPosition, Boolean isName)
at Microsoft.SharePoint.Client.JsonReader.GetTokenPrivate()
at Microsoft.SharePoint.Client.JsonReader.ReadToken()
at Microsoft.SharePoint.Client.JsonReader.ReadString()
at Microsoft.SharePoint.Client.ContentType.InitOnePropertyFromJson(String peekedName, JsonReader reader)
at Microsoft.SharePoint.Client.ClientObject.FromJson(JsonReader reader)
at Microsoft.SharePoint.Client.JsonReader.ReadJsonObject(Type fallbackType)
at Microsoft.SharePoint.Client.JsonReader.ReadObject(Type fallbackType)
at Microsoft.SharePoint.Client.JsonReader.ReadObjectArray(Type fallbackElementType)
at Microsoft.SharePoint.Client.ClientObjectCollection`1.ReadChildItems(JsonReader reader)
at Microsoft.SharePoint.Client.ClientObjectCollection.InitOnePropertyFromJson(String peekedName, JsonReader reader)
at Microsoft.SharePoint.Client.ClientObject.FromJson(JsonReader reader)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb)
at Microsoft.SharePoint.Client.ClientRequest.ExecuteQuery()
at Microsoft.SharePoint.Client.ClientRuntimeContext.ExecuteQuery()
at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryImplementation(ClientRuntimeContext clientContext, Int32 retryCount, Int32 delay)
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryRetry(ClientRuntimeContext clientContext, Int32 retryCount, Int32 delay)
at Microsoft.SharePoint.Client.FieldAndContentTypeExtensions.GetContentTypeById(Web web, String contentTypeId, Boolean searchInSiteHierarchy)
at Microsoft.SharePoint.Client.FieldAndContentTypeExtensions.AddContentTypeToListById(List list, String contentTypeID, Boolean defaultContent, Boolean searchContentTypeInSiteHierarchy)

What are you doing CSOM-wise to make these exceptions occur? A single CSOM call with time in between or hammering SharePoint Online? I'm hammering the API from an Azure VM and have never encountered anything but HTTP 503 during site collection creation.
Perhaps it's a tenant/physical machine issue.

We have a console application which deploys quite a lot of items to O365. It e.g. deploys site columns, content types, page layouts, web part definitions etc, and then creates a hierarchy of sites.
We run the console application manually from a developer machine or from a team build on our build server, so we have used several physical client machines, and also several O365 tenants.
We don't see these "underlying connection was closed" issues every time, but often enough that we need some way of handling them. The timeout is very rare.

I see mostly System.Net.Sockets.SocketException nested inside System.IO.IOException or System.Net.WebException

@VesaJuvonen: let's find out why we the service throws "System.Net.WebException: The underlying connection was closed" exception. If this is a common thing then we'll need to have a look at how to mitigate this.
@nanddeepn: once we've more clarity we'll decide what to do with this PR, but thanks already for letting us now!

We've been discussing this PR with the Office365 product group and based on their recommendations we're not going to capture additional exceptions as part of the PnP throttling handling. The main problem with just simply retrying is that an executequery command processes a batch of actions...if the error is thrown in middle of batch then just retrying will result in unexpected behavior as part of the actions were already done.
In this case it's better to properly deal with the error and implement rollback logic and retry the complete batch. https://github.com/OfficeDev/PnP/tree/dev/Samples/Core.AppEvents.HandlerDelegation shows how this can be done.

Thank you for the update Bert!


handle panics

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

32 of 60 (53.33%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-16.4%) to 70.139%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

memoize.go
32
60
53.33%

Files with Coverage Reduction
New Missed Lines
%

memoize.go
1
77.17%

Totals

Change from base Build<PHONE_NUMBER>:
-16.4%

Covered Lines:
101

Relevant Lines:
144

💛  - Coveralls


LINK-1777 | Remove mandatory fields validation from contact person fields

Description
API doesn't support mandatory fields validation for contact person fields so remove it here as well
Closes
LINK-1777

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

Comparison is base (e2352fc) 99.61% compared to head (47ab1ca) 99.61%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #114   +/-   ##
=======================================
  Coverage   99.61%   99.61%
=======================================
  Files         188      188
  Lines        3631     3631
  Branches      595      595
=======================================
  Hits         3617     3617
  Misses         13       13
  Partials        1        1

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


Update index.js

improved link text, much more user Friendly.
closes #3358

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

@Aadarsh805 sure will remember next time.

Alright, thanks for the feedback @eddiejaoude.

I think issue is already been resolved here: https://github.com/EddieHubCommunity/LinkFree/pull/3276

Thank you @alokVerma749 for noticing 👍
Great collaboration everyone and thank you @HarshDeep61034 for the contribution, but this has now been superseded by a rewrite of the way links are done in the docs with a component - please have a look at see if we missed anything or if further improvements can be made


⚠ TorrentLeech has degraded performance

In 5895ff3, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 6528 ms

Resolved: TorrentLeech performance has improved in f90e1d6 after 6 minutes.


Creating a new notebook cell copies time metadata over.

VSCode Version: 1.47.0-insider (user setup) commit<PHONE_NUMBER>790f983c350905bd1fc5b754970a0a
OS Version: Windows 10

Steps to Reproduce:

Install the .NET Interactive Notebook extension.
Execute a cell with Console.WriteLine(1234);
Notice the cell execution time is displayed.
Add new cell.
The new cell has a time pre-populated.

Does this issue occur when all extensions are disabled?: N/A

@roblourens as we discussed this morning, execution related metadata has its own meaning, compared to other metadata. Maybe we want to extract them out from metadata and then copy/paste cells won't copy them over.

There was no copy/paste here though, is metadata cloned from somewhere when you create a new cell?

Doesn't seem to repro anymore.


Tweaks

:lipstick

:+1:
Espec. the resharper this. setting :heart:

I don't know why or how, but R# added it all on its own :stuck_out_tongue_closed_eyes:

Anyone? :stuck_out_tongue:


Make validation tool general

Previously validation tool is hardcoded for hms validation tool. Since it may also be used for other tools, this PR makes the ValidationToolRegistry and Factory more generalize.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10065/
Test FAILed.

Tests in error:
alluxio.server.ft.journal.TriggeredCheckpointTest.ufsJournal(alluxio.server.ft.journal.TriggeredCheckpointTest)
  Run 1: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout
  Run 2: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout

Tests in error:
alluxio.server.ft.journal.TriggeredCheckpointTest.ufsJournal(alluxio.server.ft.journal.TriggeredCheckpointTest)
Run 1: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout
Run 2: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout

alluxio-bot, test this please.

Jenkins, test this please

alluxio-bot, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10072/
Test FAILed.

00:05:47.915 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.4:install (default-install) on project alluxio-core-common: Failed to install metadata org.alluxio:alluxio-core-common:2.3.0-SNAPSHOT/maven-metadata.xml: Could not parse metadata /home/jenkins/.m2/repository/org/alluxio/alluxio-core-common/2.3.0-SNAPSHOT/maven-metadata-local.xml: in epilog non whitespace content is not allowed but got a (position: END_TAG seen ...\na... @21:2)  -> [Help 1]

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10067/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10073/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10083/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10082/
Test FAILed.

Failed tests:
alluxio.client.file.MetadataCachingBaseFileSystemTest.openFile(alluxio.client.file.MetadataCachingBaseFileSystemTest)
Run 1: MetadataCachingBaseFileSystemTest.openFile:121->verifyGetStatusThroughRPC:134
fileSystemMasterClient.getStatus(
/dir/file,

Tests in error:
alluxio.server.ft.journal.TriggeredCheckpointTest.ufsJournal(alluxio.server.ft.journal.TriggeredCheckpointTest)
Run 1: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout
Run 2: TriggeredCheckpointTest.ufsJournal:63->validateCheckpointInClusterRestart:124 » Timeout

Failures look unrelated. Merge this PR to not block following changes

alluxio-bot, merge this please


Localization

@JakeRadMSFT I think this can be closed? We've localized almost everything, and are just finding a few strings here and there


Azure App Service Settings - Remove required flag from Resource group

Task name: Azure App Service Settings
Description: If resource group is empty, then the typescript fetches this based on the web app name, so this should not be required for the user to complete
Documentation changes required: (Y/N)  N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) N
Checklist:

[x] Task version was bumped - please check instruction how to do it

[ ] Checked that applied changes work as expected

Still open


allow to reset the function in Fiber.reset

Should we allow the fiber to be reset if its state is not TERM?  Doing so would prevent the stack from being safely unwound, so any scope(exit) blocks, etc, would never be run.

Well you have the same issues when a Fiber is collected but I would not
explicitly allow this. It's a good thing that we don't have any Thread.kill
functions either.


add uuid format validator

Adds validation for string format "uuid".
Though it's not defined in the spec, it's referenced by the Swagger docs and will be a common use case for identifying API resources.

I'm not sure this is the repository for this code.  uuid is not an OpenAPI-specific format nor is it a standard JSON Schema format and since sway allows you to register your own validators, you could just as simply do it there.  Let me think on this a little.

whitlockjc,
I completely understand if you don't feel as though this format validation does not belong here.  Would you be able to provide any example code on how to register custom format validators?  I've been looking through the docs here, but must be missing something.

We currently have this being tracked in #74.  I will close this for now in favor of #74.  If you disagree, please reopen and we'll talk more about it then.

Sounds good to me.  I'll keep an eye on that issue.


improved blending support

Adds more blending options.

Doesn't change anything already present, and works exactly the same way.
Added matching GL defines for custom modes. (unsure of the names)
Added support to set factors for colors and alpha separately.

I didn't notice the core had a few blend functions until I was pretty much finished. I tried to think of a way to improve those, but unless we can add the blend defines over there I can't think of any way to make that work. Unless you want to use one of the predefined modes, they're kinda useless atm.
Seems to be working fine for me on vs2020, can't test on anything else.
Also, this is my first contribution ever, so let me know if I'm doing something wrong...

@tbfts I'm afraid I'm not adding this improvement. It seems intended for a specific use case.

I feel like it could be used for any combination of blending.
Is it too specific in that way ?
(not arguing against the decision, just want to understand it more)
But some background; the main reason for this was that I couldn't get glad to work with raylib, in the end it was just easier to implement it directly into raylib. I really needed to separate the color and alpha blend equations for what I was trying to do, and having the defines there are just qol.

It adds 6 new variables to the global data storage that I think most users won't ever need. It also adds a lot of defines that I think are not really needed. Maybe I can consider adding it on a future but at this moment I'm trying to focus efforts for raylib and its libraries in solving issues instead of adding more features.

Ok, I understand that.
What if there were no variables, and just a few functions that directly call the necessary gl blend commands ?
Say;
rlSetBlendFactorsSeparated(srcColor, dstColor, eqColor, srcAlpha, dstAlpha, eqAlpha)
rlSetBlendConstant(r,g,b,a)
The only difference is that using rlSetBlendMode would only revert the separated command, instead of activate it. But, I feel that difference may go against the design already in place, and might be more of a band aide for the lack of separated blend commands- which I think more of as an issue rather than of adding a new feature, or rather blending is an incomplete feature without it.
One more idea would be to just remove custom modes altogether, and have;
rlSetBlendModeCustom(srcFactor, dstFactor, equation) -removing rlSetBlendFactors
rlSetBlendModeCustomSeparated(srcColor, dstColor, eqColor, srcAlpha, dstAlpha, eqAlpha)
rlSetBlendConstant(r,g,b,a)
Again these would directly call the gl commands, and setting a mode would only revert it instead of activate it. This may also have the benefit of allowing us to remove all the blending variables altogether, only needing the currentBlendMode.
I have more ideas for it, but this post is might be getting long.. let me know if I've persuaded you, even if just a little :)
For the future, I will try to keep in mind the overall userbase, instead of the few who might use a feature.
~thanks for the consideration

@tbfts I'm closing this PR. The improvement in blending is clear but it's out of scope for raylib at this moment. I also think many users today could implement all those specific types of blending using a shader.


Unresolved RNN performance issue

My previous issue was closed without resolution: https://github.com/tensorflow/tensorflow/issues/3738#issuecomment-239050102
The tf RNN approach of running up to the maximum length seems to be fundamentally flawed compared to the pycnn approach.
Even when only calling the LSTM cell on the relevant steps like below the performance issue persists:
flat_state = nest.flatten(state)
    flat_zero_output = nest.flatten(zero_output)

    def select_relevant_state(state, mask):
        c = tf.boolean_mask(state[0], mask)
        h = tf.boolean_mask(state[1], mask)
        return (c, h)

    # Function to Perform at Each Time Step
    def time_step(time, output_ta, state):

        mask = (time < sequence_length)
        indices = tf.squeeze(tf.to_int32(tf.where(mask)))
        invert_indices = tf.squeeze(tf.to_int32(tf.where(invert_mask)))
        invert_indices = tf.to_int32(tf.where(invert_mask))
        input_t = tuple(ta.read(time) for ta in input_ta)

        # Restore Shape Information
        for input_, shape in zip(input_t, inputs_got_shape):
            input_.set_shape(shape[1:])

        input_t = nest.pack_sequence_as(structure=inputs, flat_sequence=input_t)

        # Select Only Relevant at This Time Step
        input_t = tf.boolean_mask(input_t, mask)
        state = select_relevant_state(state, mask)
        call_cell = lambda: cell(input_t, state)

        # Call Cell
        (output, new_state) = call_cell()

        # Fill Unprocessed Steps
        filler_output = tf.boolean_mask(zero_output, invert_mask)
        filler_state = select_relevant_state(state, invert_mask)

        output = tf.dynamic_stitch([indices, invert_indices], [output, filler_output])
        new_state_c = tf.dynamic_stitch([indices, invert_indices], [new_state[0], filler_state[0]])
        new_state_h = tf.dynamic_stitch([indices, invert_indices], [new_state[1], filler_state[1]])
        new_state = tf.pack([new_state_c, new_state_h], axis=0)

        # Pack State if Using State Tuples
        output = nest.flatten(output)

        output_ta = tuple(ta.write(time, out) for ta, out in zip(output_ta, output))

        return (time + 1, output_ta, new_state)

Bucketing is not a reasonable approach in this situation as a LSTM is applied to each token and then a higher level LSTM is applied across combined word and character embeddings for actual tagging. This means that the only available inputs at each training step are the tokens in the sentence and therefore bucketing is not possible.

Please do not file new issues just because I close old ones.  I am happy to reopen the old one, and am ready through it now; creating new issues just clutters up the tracker.


Onem 23137 allow to select interfaces r2

It is library size optimization for libWPEFrameworkMarshallings and libWPEFrameworkDefinitions.
By additional setup of CMake variables it is possible to create generated code only for subset of interfaces.
Example setup for bitbake receipe:
EXTRA_OECMAKE += "
-DINTERFACES_PATTERNS="Ids.h IMemory.h IBrowser.h IApplication.h IDRM.h IContentDecryption.h"
-DJSONRPC_PATTERNS="common.json TraceControl.json SecurityAgent.json Browser.json WebKitBrowser.json StateControl.json OCDM.json"
"
Without that variables definition all the interfaces are included (I*.h wildcard from interfaces directory, *.json wildcard from jsonrpc directory)

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 3 files pending identification.

Protex Server Path: /home/blackduck/github/ThunderInterfaces/137/rdkcentral/ThunderInterfaces

Commit: 09641fa359501abeb2e0ee7a1db604d397c98218

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: R2 - existing headers not being changed

Commit: 09641fa359501abeb2e0ee7a1db604d397c98218

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 3 files pending identification.

Protex Server Path: /home/blackduck/github/ThunderInterfaces/137/rdkcentral/ThunderInterfaces

Commit: f628d62fd35ed552c7fb15558db7887a5316aa6e

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: R2 - RDK headers remain

Commit: f628d62fd35ed552c7fb15558db7887a5316aa6e


add missed fields to employee_requests' list

https://github.com/edenlabllc/ehealth.api/issues/503

Changes Unknown when pulling 9ab3ca7724b6e9a881c32f62f9e0928a5d4545fe on add_fields_to_employee_requests_lists into ** on master**.


Progress Bar Animation not appearing as designed

When the user searches for a Book, the search query request is sent to the Google Books API and the response is parsed for the Books data. During this process of loading the books data, a custom progress bar will be displayed in the BookSearchActivity. This is implemented using the animation-list / AnimationDrawable. The animation-list has a total of 11 drawable items displayed with a time frame of 100ms (for each drawable in the list). These drawables are line drawables which has a line with solid background and a dashed line as its foreground, and each drawable item in the list varies its left padding for the dashed line. These drawable items look like these, in the same order as mentioned in progress bar.

Progress Bar Appearance in Android 7

As seen in the above GIF, there is no dashed appearance of the dash line used as a foreground in the layer list of the drawables. The left padding is shown successively to increase as expected.
Progress Bar Appearance in Android 5

As seen in the above GIF, there is no dashed appearance of the dash line used as a foreground in the layer list of the drawables and also no proper successive increase of left padding shown. Instead, the animation appears like a lightning bolt moving from left to right.
These are the test results obtained through Android Emulation of Nexus 5X with Android 7 and Android 5. Emulation was accelerated with Hardware acceleration.
Couple of things I would like to know on this -

Why there is a difference in the Animation shown on different Android versions?
Why there is no dashed appearance in the line drawables?
How to make this to work on all Android versions with proper animation like in the result of Android 7 along with the appearance of dashed line in the output?

This Progress bar animation is very dependent on device capability and also the Android version it is running on. In the latest Android devices, running with (probably) Android OS 9+, Progress bar animation works as expected in the same way as it is designed. Hence closing this issue for now.


Update instructions and code example in Step 49 of Calorie counter

Describe the Issue
We have had a few people on the forum be confused on how innerHTML works and what they need to do in step 49.
https://forum.freecodecamp.org/search?expanded=true&q=Step 49 Calorie counter %23javascript
A way to clear up this confusion, would be to update the code example for introducing innerHTML to use labels and inputs.
Also, the wording could be updated to make it more clear, what they need to do
Proposed changes
--description--
To see your new HTML content for the targetInputContainer, you will need to use the innerHTML property.
The innerHTML property sets or returns the HTML content inside an element. Here is an example of how to use it:
<form id="form">
  First name
  <input type="text">
</form>

const formElement = document.getElementById("form");
const formContent = `
  Last name
  <input type="text">
`;
formElement.innerHTML += formContent;

In the example, the innerHTML property is used to add a new label and input elements to the form element.
Use the addition assignment operator += to append your HTMLString variable to targetInputContainer.innerHTML.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-form-validation-by-building-a-calorie-counter/step-49
Your code
see explanation above
Expected behavior
see explanation above
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum


Updated the React lifecycle functions that were deprecated in 16.3+

It looks like most of the componentWillReceiveProps functions were safe to convert to componentDidUpdate with relevant changes (nextProps -> props, props -> prevProps, etc).

I think you have replaced nextProps with this.props which is not the same by the time both are applied.
What about getDerivedStateFromProps ?

getDerivedStateFromProps is invoked right before calling the render method, both on the initial mount and on subsequent updates. It should return an object to update the state, or null to update nothing.

See also https://hackernoon.com/replacing-componentwillreceiveprops-with-getderivedstatefromprops-c3956f7ce607

I actually did have a version that worked with getDerivedStateFromProps, but it ended up doing the same thing as componentDidUpdate. Moreover, getDerivedStateFromProps is static which means working with getDisplaySameSlide becomes much more complicated as it's counting the differences in the number of children the component has between prop changes - which it can't access without storing them in state.
Just for reference, here's my componentDidUpdate that I use locally which does work with my React 16.12 project - note that I set the index details after the state goes into effect. This fails the tests, but works correctly in my project whereas the one I committed in the PR passes the tests, but doesn't work for React 16.12 for me.
  componentDidUpdate(prevProps) {
    const { index } = this.props;

    if (typeof index === 'number' && index !== prevProps.index) {
      if (process.env.NODE_ENV !== 'production') {
        checkIndexBounds(this.props);
      }

      // eslint-disable-next-line react/no-did-update-set-state
      this.setState(
        {
          // If true, we are going to change the children. We shouldn't animate it.
          displaySameSlide: getDisplaySameSlide(prevProps, this.props),
          indexLatest: index,
        },
        () => this.setIndexCurrent(index),
      );
    }
  }

I based the changes on the migration guide from the React team: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html
Notably:

Sometimes people use componentWillUpdate out of a misplaced fear that by the time componentDidUpdate fires, it is “too late” to update the state of other components. This is not the case. React ensures that any setState calls that happen during componentDidMount and componentDidUpdate are flushed before the user sees the updated UI. In general, it is better to avoid cascading updates like this, but in some cases they are necessary (for example, if you need to position a tooltip after measuring the rendered DOM element).

I haven't had time to come back to this properly, but if someone can confirm what I was seeing that'd be a huge help.

What about just using the UNSAFE_ keyword for the componentWillReceiveProps method ?

That's the easier way, but it just delays the inevitable as the React team is eventually going to remove those UNSAFE_ items. I was trying to just "solve" the problem so it wouldn't catch up with me later.

I was reading on the react website about the migration path and they mention this:

17.0: Remove componentWillMount, componentWillReceiveProps, and componentWillUpdate . (Only the new “UNSAFE_” lifecycle names will work from this point forward.)

It would be nice to update the code to use proper lifecycle methods tho

Closing as duplicate of #616.


WS:Function: outmap1 formula description is different than formula

The descripton for G3 (outmap1) says "In calculations, if field inspection found an outlet, use 0". But the formula uses 1 if outlet found.

THE LATTER IS CORRECT. FIXED DESCRIPTION IN COLUMN H.
Edited


please use cronjob

hi please changed default time to
time + date and more option like cronjob

Hi @d0d04m3,
the node is constantly improving and receives new features all the time. I am currently not planning on adding a date since that would not be a recurring event. There is a possibility though that I'll add a selection for specific weeks or maybe months but that is still in the backlog.
This node was made to let users, even without technical background, schedule events at the frontend, therefore I won't add cron.
Please let me know if you need anything else.

Hi @d0d04m3,
the node is constantly improving and receives new features all the time. I am currently not planning on adding a date since that would not be a recurring event. There is a possibility though that I'll add a selection for specific weeks or maybe months but that is still in the backlog.
This node was made to let users, even without technical background, schedule events at the frontend, therefore I won't add cron.
Please let me know if you need anything else.

But
Thus, events had to be repeated every day at the appointed hour
What if the user does not want to execute the event on a certain date
Your graphic node allows users to control events graphically for those who don't have an angular background but your work needs a lot of improvement why not make your node can work with cron node


Datetime Picker not showing

Hello,
I was able to successfully use the Datetime Picker on pure HTML, but I'm not able to integrate this component to my Yii2 application (PHP) with the AppUI Backend template (by PixelCave).
When I try to click on the button, the date is placed on the input text but no popover appears. What could possibly be causing this problem?
All javascript files are being imported at the head section and in this order:
1st jQuery 2.1.3
2nd Moment.JS (with locales) 2.9
3rd Bootstrap 3
4th Bootstrap-Datetimepicker V4

I'm also importing Bootstrap-Datetimepicker's CSS.

Add to this situation the fact that nothing is being logged at the console, so no importion errors are happening.
Can this problem be generated by CSS conflicts with the AppUI template?
It's difficult for me to create a jsFiddle because the problem only occurs inside the framework itself.
Thanks in advance!

Can you setup a demo page somewhere and give me a link?
Have you checked your console log to make sure you aren't getting an error?


[5.3] Fix line breaks in plain text email

https://github.com/laravel/framework/pull/15108 broke the new-lines in the plain text email for notifications.
This PR fixes those line breaks.
For future PRs the importance of new-lines in plain text emails has been highlighted by only using echo statements in email-plain.blade.php.
CRLFs have been replaced by LFs, because SwiftMailer canonicalizes them anyhow.

Why do we have to manually echo "\n"... why not just put actual line breaks in the file like you would a Blade template?

@taylorotwell Because of the conditionals. We'd end up with weird blank lines in between sections.

HTML collapses vertical line breaks and even horizontal spaces. Plain text emails are more like Markdown.


[FEATURE REQUEST] - Have the ability to write to a local mapped folder/volume.

Hi
Just wanted to post the idea for this app to be enhanced so you have an option to write all generated emails/pdfs to a local/mapped folder/volume rather than directly to Paperless.

Hi
Just wanted to post the idea for this app to be enhanced so you have an option to write all generated emails/pdfs to a local/mapped folder/volume rather than directly to Paperless.

Hi, should this step happen together with the upload to Paperless or should the whole thing run completely without Paperless. In the latter case I would not be sure if a separate application would not be a better choice.

Hi @Skyleiger,
It can actually work in both scenarios, as the target folder could be set and the Paperless consume folder.
For me personally i like to have the option of sending things to a pre-consumption folder, a space which gives me the chance to make any changes i need to the document (i.e if a pdf, split, combine/merge etc.) before passing it on to Paperless.

Hi @Skyleiger,
It can actually work in both scenarios, as the target folder could be set and the Paperless consume folder.
For me personally i like to have the option of sending things to a pre-consumption folder, a space which gives me the chance to make any changes i need to the document (i.e if a pdf, split, combine/merge etc.) before passing it on to Paperless.

Oh yes, sure. That's a nice idea I think. I can see if I can implement such a feature.

Hi, version 1.1.0 is online including your suggestions. Have a look.

Thanks @Skyleiger , although I do have a similar question to my other post, how best do I set this up ?

Hi @nodecentral
The best solution is to map your paperless consume folder as a folder into the email-to-paperless container.
For example, if you map your consume folder to /usr/share/paperless/consume into the container, you have to simply set the environment variables
EMAIL_STORING_STRATEGY to FOLDER and
EMAIL_STORING_FOLDER to /usr/share/paperless/consume.
With that, you can remove all environment variables starting with PAPERLESS....


remove implicit style

Remove styles that are added automatically by the build system. cf. https://github.com/highlightjs/highlight.js/pull/4124#discussion_r1781871020

I can't tell what if anything you changed in the README, please revert all the unnecessary linting/spacing changes.
The other changes for the base16 styles seem to be correct. I'm thinking they ship "complete" from the Base16 repo they are copied directly from to allow people to use them "as-is" from that repo... where-as the themes here are not meant to be used until they are "cooked" and added to a distribution.
So I think this can be merged just as soon as we remove the unnecessary changes to the README.

I can't tell what if anything you changed in the README, please revert all the unnecessary linting/spacing changes.

You mean in VERSION_11_UPGRADE.md (aebf8d061ecf5a96b82dc3d5e99101cedb6e87a5)? I removed all the unnecessary extra/double spaces.

So I think this can be merged just as soon as we remove the unnecessary changes to the README.

You want me to add a new revert commit? Or do you prefer to drop this commit while squashing the PR?

You want me to add a new revert commit?

That'd be great.

Actually we may need more work here, but I'm not sure what to suggest.  It just clicked that these are actually assets copied directly from another build system.  So modifying them in our repo makes no sense - we'd need a script to make this repeatable.
Otherwise all this work will be lost when the Base16 themes are rebuilt and copied over whenever we decide to refresh these in the future.  I'm thinking it maybe best to leave these "as is" and clean up the duplication in our own build step.
Thoughts?

See last comment.  Closing this.  I feel like a tiny improvement to clean this up inside our CSS processing pipeline would be a different PR entirely - not a reuse of this one.


Restic restore ignores $RESTIC_REPOSITORY

Output of restic version
manager@srv1:~$ restic version
restic 0.7.0
compiled with go1.8.3 on linux/amd64

How did you start restic exactly? (Include the complete command line)
manager@srv1:~$ restic restore --target /var/data latest
Fatal: Please specify repository location (-r)

manager@srv1:~$ restic help restore
The "restore" command extracts the data from a snapshot from the repository to
a directory.

[...]

  -r, --repo string            repository to backup to or restore from (default: $RESTIC_REPOSITORY)

manager@srv1:~$ echo $RESTIC_REPOSITORY
/var/restic

What backend/server/service did you use?
All local
Expected behavior
No need for -r option
Actual behavior
Error when not specifying -r even if $RESTIC_REPOSITORY is set.
Steps to reproduce the behavior
See above.
Do you have any idea what may have caused this?
no.

Hey, thanks for raising this issue. I'm unable to reproduce it, though. Did you export RESTIC_REPOSITORY? You can check with:
$ sh -c 'echo ${RESTIC_REPOSITORY:-unset}'

Ah great, now I understand what export does ;) I guess restic had no chance.

Heh, glad we could find the issue. :)

Just leaving this here hoping that it might help another lost soul but my issue was having to use sudo because I didn't have permissions to restore the backup in the location I chose and I didn't realize that overrides previous variables with the root user's.
sudo -E restic restore ... was the solution in my case to prevent $RESTIC_REPOSITORY from being overridden, though if possible, you should probably just fix the permissions issue instead 🙂


Adding project files

This merge contains all the project files needed by the application.

Successfully added the Project Files.


feat: separate esm build for SDK

What's done
Next to existing CommonJS build, a new ESM build is also produced with Webpack.
This should ideally fix the issues experienced in:

https://github.com/featurevisor/featurevisor/pull/321
https://github.com/featurevisor/featurevisor/issues/312
https://github.com/featurevisor/featurevisor/issues/269

cc @meirroth
TODOs

[ ] Try it out locally against https://github.com/featurevisor/featurevisor-example-nodejs by doing import { createInstance } from "@featurevisor/sdk";

@meirroth: what you can do to help test it locally:

clone this repo
checkout sdk-esm branch (this PR)
Run make install and make build
(cd ./packages/sdk && npm link)

Then go to your Nuxt application, and do $ npm link @featurevisor/sdk. This will reference the locally built Featurevisor SDK.
Run your Nuxt application, and see if you experience the issue any more.

Thank you for taking initiative and working to fix these issues!
I tired in my project, following your steps and got this error on build (after removing the transpile fix):

And testing with featurevisor-example-nuxt, builds fine, but crashes when visiting the site after build:

When I leave the trasnpile fix in featurevisor-example-nuxt, the SSR Hydration mismatch issue is still present (#312):

I'm really not familiar with bundlers to know, but maybe there's an extra step to make Nuxt pick up the new ESM build?

thanks @meirroth for trying it out. really appreciate it.
have to look into the issue further before I can say anything :(

Taking it forward with https://github.com/featurevisor/featurevisor/pull/324


Avalon ST empty symbols

I've scoured the source code and the internet with no resolution, so I'm asking/submitting an issue here.
I'm using UVVM to test a system that has both an Avalon ST master and slave implementation. The implementation utilizes the "empty" field, which allows the system to express that some symbols in the word are invalid. I am using a symbol size of 8 bits and a word size of 4 symbols (32 bits). The valid value for "empty" is 0-3.
In the avalon_st_bfm_pkg.vhd file, empty symbols appear to be taken care of in the avalon_st_receive function (I am calling it via `avalone_st_expect'):
-- Check the number of empty symbols on the last data transfer
if c_symbols_per_beat > 1 then
    v_empty_symbols := to_integer(unsigned(avalon_st_if.empty));
end if;

However, the function can only end at a multiple of the symbols per beat, c_symbols_per_beat, since v_symbol_array has a length that is v_normalized_data'length*c_symbols_per_beat. By this time, v_sym_in_beat must be c_symbols_per_beat-1 and v_sym_count must be a multiple of c_symbols_per_beat (-1 for 0 indexing) due to how v_symbol_array is allocated. If v_empty_symbols is anything but 0, an error is thrown.
-- Finish receiving data when the symbol array ends
if v_sym_cnt = v_symbol_array'length - 1 then
    v_done := true;
    -- Check that empty signal is set on the last data transfer
    if v_sym_in_beat /= c_symbols_per_beat - 1 - v_empty_symbols then
        alert(error, v_proc_call.all & "=> Failed. Empty signal not set correctly for the last transfer. " & add_msg_delimiter(msg), scope);
    end if;
end if;

For my own testing, I changed if v_sym_cnt = v_symbol_array'length - 1 then to if v_sym_cnt = v_symbol_array'length - 1 - v_empty_symbols then and it is working great.
Am I missing something or is this an oversight in the design? There should also be checks to make sure that "empty" is 0 if it's not the last word in a packet.

On the flip (transmit) side, a similar issue arises. The empty signal is filled, but the function can only exit on a multiple of c_symbols_per_beat, and thus empty is set to 0 no matter what. I had to add an argument to tell the function how many symbols were acceptable instead of the default v_normalized_data'length*c_symbols_per_beat
Again, am I missing something or was this feature not fully developed?
Thanks!

Hi,
I assume you are using a data_array with an element size of 32 bits when calling the transmit and receive procedures, is that correct?
It might not be clear from the documentation, but when using packet-based transfers, you should use a data_array with the symbol size elements, i.e. t_slv_array(0 to n)(7 downto 0) for your case. This way you can send and receive the necessary symbols and the last transaction will have the correct empty value.
If you change the code in the receive procedure to exit on v_sym_cnt = v_symbol_array'length - 1 - v_empty_symbols I believe there is no way of telling which symbols are valid/invalid in the received data_array (for the last 32-bits), whereas if you use the symbol size elements, your received data_array will only contain valid symbols.
As for the request to check that empty is 0 if it's not the last word in a packet, the Avalon-ST specification mentions the following: The sink only checks the value of the empty during active cycles that have endofpacket asserted. So there is no need to check it except during the last cycle.

Sorry for the horribly long delay - I got pulled to some different projects at work, then I had some personal things come up.
I should actually be getting back to this in the next week or two. I'll let you know. Thanks again!

Hi,
Has this issue been resolved?

Unfortunately the project I was working on was scrapped and the projects I am now working on don't require those functions. Hopefully I can get back to it someday, but likely not soon.
Sent via the Samsung Galaxy S10, an AT&T 5G Evolution capable smartphone
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: UVVM @.>
Sent: Thursday, July 18, 2024 12:58:38 AM
To: UVVM/UVVM @.>
Cc: Whiteway, Alex @.>; Author @.>
Subject: Re: [UVVM/UVVM] Avalon ST empty symbols (Issue #203)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hi,
Has this issue been resolved?
—
Reply to this email directly, view it on GitHubhttps://github.com/UVVM/UVVM/issues/203#issuecomment-2235767544, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7JQNN5Z36TPIOV4V5O6EDZM5RR5AVCNFSM6AAAAABLCAY3RGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZVG43DONJUGQ.
You are receiving this because you authored the thread.Message ID: @.***>


I don't have ubuntu terminal like everyone else

I think the title says it all.

Just gonna quite @DHowett

You have deleted the bug template. Please don't do that -- it makes it very hard for us to triage bugs.

What version of Terminal are you using?
What version of Windows?
What version of Git for Windows?

@whyiseverynamealreadytaken Have you installed WSL and the Ubuntu distro from the Store? The Terminal doesn't come with any linux distros on its own, you need to install them separately.


Update for PureScript 0.10.7

See https://github.com/purescript/purescript/releases/tag/v0.10.7

Coverage remained the same at 100.0% when pulling 3c3983a43cfa4cf65167573c7b803b23ce843284 on sectore:v0.10.7 into f200b307938ee6fd9c351b9456702cc70856adc4 on purescript-contrib:master.

According to the 0.10.6...0.10.7 diff there is a drastic change and it should make the node-purescript-bin tests broken. I don't know why the CI result is green.

@shinnn the diff you linked is from 0.10.7 to master. We're currently working on 0.11 which is going to feature breaking changes, but 0.10.6 to 0.10.7 is just a small reverted change to code generation which unfortunately broke psc-bundle. Because of that the 0.10.7 release is cut from the v0.10.x-staging branch: https://github.com/purescript/purescript/commits/v0.10.x-staging.
Thank you for being so thorough in your analysis and making sure we're not releasing anything stupid!

Thanks for clarification, @kRITZCREEK. Also I just finished reading https://github.com/purescript/purescript/issues/2642.


Add sensor samples.

LGTM

@kaixinjxq, please submit another PR to update the folder name from 'Sample' to 'samples'.


Documentation: fix the type of some nodes.

Fixes #1910
Fixes #1929

Codecov Report

Merging #1935 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1935   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files           1       1
  Lines        4056    4056
  Branches      717     717
======================================
  Hits         4056    4056

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1bfd79c...7c2c64f. Read the comment docs.


stage1: revert interpreter changes in coreos build

86ad903 bumped the image version for RKT_STAGE1_FROM=coreos and in
doing so removed the LD_LIBRARY_PATH and interpreter overrides. However
we still need those to ensure the stage1 is truly self-contained and
does not have dependencies on host libraries.

wait, we need interp too, hold up

lgtm pending green

you're killing me travis

finished!


cannot play .m3u8 playlist??

cannot play .m3u8 playlist??

There is no support for this at the moment, no. It should be feasible if the entries in the playlist are in a codec supported by flv.

very appreciated for you response!
the entries are ts files, with video codec h264, audio code aac. they are supported by flv.
so what should I do to play those ts files?

Well, it is not implemented, so you would have to do the implementation - or pay someone to do it.


feat(store): multiple inStock labels config

Description
Closes #322

Changed store.labels config to allow multiple inStore containers

This helps for configs like nvidia store where a product list page and product details page are being searched, but the '.main-container' selector only works for the products list page (and a different container selector needs to be used for the product details page '.js-product-item .btn-cart')

Testing

I added a second debug card in the nvidia store config for testing, and verified both debug pages are matching the 'add to cart' buttons and showing the "IN STOCK" alert

New dependencies
N/A

Closes #322

This looks great! If you are able to resolve these conflicts, this is going in next!
Thank you very much @admon84 :)

#270 added support for array of inStock labels, would the below be enough to cover this use case?
Index: src/store/model/nvidia.ts
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- src/store/model/nvidia.ts	(revision 07bd246e876cd27df1b5019af5ee8613bb5368f0)
+++ src/store/model/nvidia.ts	(date<PHONE_NUMBER>909)
@@ -6,10 +6,13 @@
 			container: 'body',
 			text: ['are you a human?']
 		},
-		inStock: {
+		inStock: [{
 			container: '.main-container',
 			text: ['add to cart']
-		}
+		}, {
+			container: '.js-product-item .btn-cart',
+			text: ['add to cart']
+		}]
 	},
 	links: [
 		{
@@ -19,6 +22,12 @@
 			url: 'https://www.nvidia.com/en-us/shop/geforce/gpu/'
 		},
 		{
+			brand: 'test:brand',
+			model: 'test:model',
+			series: 'test:series',
+			url: 'https://www.nvidia.com/en-us/geforce/graphics-cards/rtx-2060-super/'
+		},
+		{
 			brand: 'nvidia',
 			model: 'founders edition',
 			series: '3080',

#270 added support for array of inStock labels, would the below be enough to cover this use case?

I thought this got added already and I must've misunderstood the intent. At this point, the current labels are Element[], thus abstracting out all of these properties.
Makes sense to close this one out then.

I agree, this one can be closed out.


Removed isInline prop

Summary
Resolves this.
Additional Details
Removed isInline prop because field-set no longer needs it thinking of it as a wrapper to the form fields.

This doesn't affect the rendering of components, but does removing this make it non-passive as it will result in an unknown prop being spread to the feildset element?

I think I'd lean towards doing it as a non passive version. Like you said, jest tests would have to be rewritten most likely to use this change.


Filtering /dataset by nom code returns incomplete list

There seems to be too few datasets returned when filtering by nom code:
https://api.checklistbank.org/dataset?code=botanical
For example, 1140 is not in the list and nom code is set:
https://api.checklistbank.org/dataset/1140/settings

Unexpected indeed. But the code does look fine, investigating...

https://api.checklistbank.org/dataset?code=botanical returns 41 datasets now!


Wakaama bootstrap server crashes

Wakaama bootstrap server built with command cmake ../bootstrap_server/ -DDTLS=1.
Wakaama bootstrap server is crashing early. Behavior same for debug and non debug build. Logs attached.
Code in sync with master. Same behavior on Mac and Ubuntu.

Hi,
The bootstrap server is not designed to work with DTLS.
I considering two options: preventing -DDTLS=1 in the CMakeLists.txt or handling DTLS connection in the bootstrap server. But the latter would require a way to provide the credentials.

I created PR #200 to prevent the usage of DTLS with the example server, bootstrap server and light client.
If one wants to implement this, it requires several things:

use dtls_connection_t when WITH_TINYDTLS is defined.
set the dtls context when a new incoming connection is created
add command line parameters to set the servers credentials


Potential implementation guidance / spec clarifications

Questions from @maweit on AMWA Slack that we think are worth tracking to clarify in the spec or an accompanying INFO doc...
We're having difficulties to judge if an activation request is erroneous. We cannot catch all failure modes against constraints. Constraints can express only a very basic set of restrictions and cannot catch all cases. Example: senders and receivers that support IS-05 control but are restricted to a subset of AES67.
Should these additional restrictions be applied to /staged or can it be deferred to activation time?
There are activations coming from controllers with master_enable=true but all rtp_enabled=false. How to deal with this? What is the intention of sending such an activation request?
What to populate on staged and active endpoints if activation does not come from NMOS-IS-05 (i.e. user interface)?
More specifically, what address to use in the second entry of transport_params for senders that support 2022-7 but are configured not to use it (i.e. through the UI).
Related to the above, what addresses to use in transport_params for senders that have not been configured at all?

Taking questions one at a time... First, you can reject PATCH requests for other reasons besides schema and constraints validation, including for example identifying unsupported stream via the SDP transport_file in a Receiver. However, the quirk is that such rejection has to be reported via 500 not 400.
So if you can identify the issue at staging time, then do so, as in the case of scheduled activations it ensures the client gets an immediate error rather than having to watch for a failed/missed activation later.
Activations with master_enable true but all rtp_enabled false sound very odd... although are valid.
Activations that are made by device specific means, e.g. front panel, web UI or non-NMOS API, should be reflected into /active when they happen for certain. The rule for IS-04 /target interop with IS-05 was that such immediate activations would also be applied to /staged so that a partial PATCH activation via IS-05 subsequently would use the most recent params. That seems like a reasonable device behaviour generally to me...
The other parameters on a leg that is rtp_enabled false should have no effect on the stream... but should be consistent with the SDP /transportfile for Senders, so it is a good question. source_port and destination_port are required to have sensible defaults applied when the controller stages "auto" so those defaults would make sense as values in the case you describe. The same goes for source_ip, destination_ip and interface_ip. Receiver multicast_ip can be null reasonably enough...
The sensible defaults for Sender destination_ip and Receiver source_ip have been discussed before... I seem to remember some vendors using <IP_ADDRESS> and others using random SSM addresses.
Of course after initialization, such PATCHes also have the option of just leaving the existing values on the disabled leg alone.

Architecture Review Group review: place on backlog


Why using Webpack & Gulp

Hi!
I have just started working on this project and it looks really promising.
One thing I can not understand though is, why are you running webpack from gulp? Why not just stick to webpack?

@atais Thanks!

One thing I can not understand though is, why are you running webpack from gulp? Why not just stick to webpack?

First, I don't like importing CSS in JS files.
Second, to make this project be able to run from Jekyll without npm/gulp/webpack.
Third, to integrate the configuration.


⚠ Samsung has degraded performance

In cc9bbc2, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1968 ms

Resolved: Samsung performance has improved in a8750f9.


dd.read_parquet : RuntimeError: invalid input size (corrupted?)

Hi,
Still struggling to have a basic work-flow.
Parquet files which were generated by Apache Drill, a single file can be read correctly  using fastparquet, the exact same file results in the folowing stack trace when using dd.read_parquet:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-45-2a671e4e009b> in <module>()
      3 import dask.dataframe as dd
      4
----> 5 df_from_parquet = dd.read_parquet(PARQUET_FILES)
      6 # df_from_parquet = d_client.persist(df_from_parquet)
      7 # Dask runs entirely asynchronously, leaving operators free to explore while computations happen in the background.

/usr/local/lib/python2.7/dist-packages/dask/dataframe/io/parquet.pyc in read_parquet(path, columns, filters, categories, index, storage_options)
     83
     84     # Find an index among the partially sorted columns
---> 85     minmax = fastparquet.api.sorted_partitioned_columns(pf)
     86
     87     if index is False:

/usr/local/lib/python2.7/dist-packages/fastparquet/api.pyc in sorted_partitioned_columns(pf)
    506     statistics
    507     """
--> 508     s = statistics(pf)
    509     columns = pf.columns
    510     out = dict()

/usr/local/lib/python2.7/dist-packages/fastparquet/api.pyc in statistics(obj)
    468
    469     if isinstance(obj, ParquetFile):
--> 470         L = list(map(statistics, obj.row_groups))
    471         names = obj.columns
    472         d = {n: {col: [item[col].get(n, None) for item in L]

/usr/local/lib/python2.7/dist-packages/fastparquet/api.pyc in statistics(obj)
    465     if isinstance(obj, parquet_thrift.RowGroup):
    466         return {'.'.join(c.meta_data.path_in_schema): statistics(c)
--> 467                 for c in obj.columns}
    468
    469     if isinstance(obj, ParquetFile):

/usr/local/lib/python2.7/dist-packages/fastparquet/api.pyc in <dictcomp>((c,))
    465     if isinstance(obj, parquet_thrift.RowGroup):
    466         return {'.'.join(c.meta_data.path_in_schema): statistics(c)
--> 467                 for c in obj.columns}
    468
    469     if isinstance(obj, ParquetFile):

/usr/local/lib/python2.7/dist-packages/fastparquet/api.pyc in statistics(obj)
    454             return rv
    455         if s.max is not None:
--> 456             rv['max'] = encoding.read_plain(ensure_bytes(s.max), md.type, 1)[0]
    457         if s.min is not None:
    458             rv['min'] = encoding.read_plain(ensure_bytes(s.min), md.type, 1)[0]

/usr/local/lib/python2.7/dist-packages/fastparquet/encoding.pyc in read_plain(raw_bytes, type_, count, width)
     45         return read_plain_boolean(raw_bytes, count)
     46     # variable byte arrays (rare)
---> 47     return np.array(unpack_byte_array(raw_bytes, count), dtype='O')
     48
     49

/usr/local/lib/python2.7/dist-packages/fastparquet/speedups.pyx in fastparquet.speedups.unpack_byte_array (fastparquet/speedups.c:3276)()
    164
    165     if remaining != 0:
--> 166         raise RuntimeError("invalid input size (corrupted?)")
    167     return out

RuntimeError: invalid input size (corrupted?)

Is this too a python 2 issue?
I really want something working before I give up :)

@QuantScientist , it is hard to diagnose from the stack-trace alone. As usual, is there any chance you can provide a self-contained example? Failing that, perhaps an extract from the data itself that shows the problem. It appears to happen while analysing the partition max/min values.
@mrocklin , if occurs to me that it's wasted effort to load statistics if index=False, and should only load statistics for the given index column, if an index is specified.

How to reproduce:
import dask
PARQUET_FILES_FROM_DASK= '/root/parquet/parquet_small_3/0_0_0.parquet'# docker mapping
import dask.dataframe as dd
df_from_parquet = dd.read_parquet(PARQUET_FILES_FROM_DASK)

Open the attached ZIP file which contains the parquet file.
parquet_small_3.zip

Also note that the same file, can be read by fastparquet easily:

I am still getting the same error even after updating to the latest versions.

Did you also update fastparquet pip install --upgrade git+https://github.com/dask/fastparquet ?

I experience the same issue using latest dask and fastparquet trying to read a parquet file generated by Spark 2.1. Here is the sample tar file:
dask-data.tar.gz

I'm afraid that the data reads fine with dask or raw fastparquet, sorry :|
You probably know, but all of those data files are empty (contain only metadata, no rows) except for part-00000.

Hmm... that is interesting. Are you saying that you can read.parquet the whole dir without any issue? Do you use dd.read_parquet('./dask_data')?
This dataset is quite small, only three rows and three columns. So I am not surprised that some of them are empty.

Yes, dd.read_parquet('dask_data') worked.

Cool. This time is my bad. I can confirm if I am using the latest master fastparquet. everything is good now. :)


How to create the mask_folder?

Good Morning,
I am trying to run the code. But when running the 'create_surrogate_data_STL.py', it appears an error. I think is because i haven´t create the mask folder but i don´t know how to do so. Any suggestions?
Traceback (most recent call last):
File "create_surrogate_data_STL.py", line 82, in
mask = Image.open(mask_path + '/' + str(label_ind).zfill(len(str(nb_classes)))[:-4] + '.png')
File "/usr/local/lib/python3.6/dist-packages/PIL/Image.py", line 2809, in open
fp = builtins.open(filename, "rb")
FileNotFoundError: [Errno 2] No such file or directory: './surrogate_dataset/class_folder_16000_set/00000.png'

Did you find the solution?? I am facing the same issue

Traceback (most recent call last):   File "create_surrogate_data_STL.py", line 77, in <module>     mask = Image.open(mask_path + '/' + str(label_ind).zfill(len(str(nb_classes)))[:-4] + '_edge.png')   File "/home/pratt3000/anaconda3/lib/python3.8/site-packages/PIL/Image.py", line 2878, in open     fp = builtins.open(filename, "rb") FileNotFoundError: [Errno 2] No such file or directory: './surrogate_dataset/class_folder_16000_set_edge/00_edge.png'

Traceback (most recent call last):
File "create_surrogate_data_STL.py", line 77, in
mask = Image.open(mask_path + '/' + str(label_ind).zfill(len(str(nb_classes)))[:-4] + '_edge.png')
File "/home/pratt3000/anaconda3/lib/python3.8/site-packages/PIL/Image.py", line 2878, in open
fp = builtins.open(filename, "rb")
FileNotFoundError: [Errno 2] No such file or directory: './surrogate_dataset/class_folder_16000_set_edge/00_edge.png'

'_edge' part was added in the later version maybe but the fundamental issue remains the same


Cassandra Cursor

I made a CassandraCursor class that implements a lot of the same interface as the MySQLdb cursor class so that django can pass this object around and that our database backend can find this useful. This will make a lot of the database introspection and migration features that are apart of Django 1.7
I also noticed that Django 1.7 refactored a lot of the DatabaseWrapper functionality into methods that make sense. I already had this logically seperated in a similar way but I went ahead and refactored what I had into the new DatabaseWrapper interface methods.

cr by @simlay


Passing props to Styled Component doesn't work in v5.2.1

  border: ${({ active }) => (active ? "1px solid red" : "")};

This didn't work in 5.2.1 and active always seemed to be true even if I set active={false} on the component. Downgrading back to 5.1.1 fixed the issue.

Can you give me a link on codesandbox.So that i could check the code...

Just had a similar issue except we found that there were conflicting styles generated with the same classname.
It seems like it could be the same underlying issue as #3376.
There is a reproduction in that issue that produces similar results.

If you have a codesandbox, then we could take a look, however if this is a usage question, I'd suggest Stackoverflow for these kinds of issues. Without a full issue filled out there's not much we can say about this.


Settings for "api_key" input's placeholder

Is there any chance to add a configuration option to make possible for "api_key" input's placeholder to be customized?
https://github.com/ruby-grape/grape-swagger-rails/blob/5799fa26736e02d9b5fc040c12b5b883c6c46ea9/app/views/grape_swagger_rails/application/index.html.erb#L99
In our case, we are using Authorization bearer and it would be more intuitive for the end user to see the "access_token" placeholder instead of "api_key".

It's a good idea, care to contribute?

Closed via https://github.com/ruby-grape/grape-swagger-rails/pull/114


Adds mobile responsiveness for the building page

On mobile, there is no image or map on the building page. The screen would've been too cluttered otherwise.
Closes #219

Header is scrollable, is it possible to expand to fit content?

Header is scrollable, is it possible to expand to fit content?

There's a weird css bug where if I expand it to fit content, the size of the header of a building will be the biggest size from any header of a building. So expanding it to fit content will make it so it's too big most of the time. I don't know how to fix that issue, so I've decided to use a scrollbar instead.

Styling of this entire detail view has been reworked, also concerns about the scrollable data are fixed


I can't install. /usr/local/Homebrew/.git: Permission denied Failed during: git init -q

After fresh install macOS Sierra 10.12.1, I tried to install homebrew, but I can't install.
It says
/usr/local/Homebrew/.git: Permission denied Failed during: git init -q
What am I gonna do?

Sorry, It caused by my mistake.

How to solve？


proxy does not get dst metadata for some pods

I deployed strest with TLS enabled, and it two pods in a cluster of 10 are not receiving TLS'd traffic:
NAME                                  MESHED   SUCCESS       RPS   LATENCY_P50   LATENCY_P95   LATENCY_P99    TLS
strest-client-98df4ccbd-zctzk            1/1         -         -             -             -             -      -
strest-server-fast-8f456d97d-9m4qp       1/1   100.00%   33.1rps          18ms          74ms          97ms   100%
strest-server-fast-8f456d97d-bvvg5       1/1   100.00%   36.8rps          20ms          78ms          98ms   100%
strest-server-fast-8f456d97d-f5zbx       1/1   100.00%   37.0rps          22ms          75ms          98ms   100%
strest-server-fast-8f456d97d-fv22l       1/1   100.00%   36.3rps          21ms          82ms          97ms   100%
strest-server-fast-8f456d97d-pmpxg       1/1   100.00%   31.9rps          22ms          84ms         443ms   100%
strest-server-fast-8f456d97d-r67vb       1/1   100.00%   30.8rps          18ms          73ms          94ms     0%
strest-server-fast-8f456d97d-xmrjn       1/1   100.00%   49.6rps          21ms          74ms          95ms   100%
strest-server-fast-8f456d97d-zccs7       1/1   100.00%   28.0rps          19ms          74ms          95ms   100%
strest-server-fast-8f456d97d-zwnrb       1/1   100.00%   29.6rps          21ms          73ms          95ms   100%
strest-server-slow-79b46659dc-dgkdx      1/1   100.00%   44.1rps          20ms          75ms          96ms     0%

If we look at one of the unprotected endpoints, the no_proxy_tls label indicates that the endpoint is not receiving encrypted traffic, and that it previously accepted a connection before identity was ready.
:; kubectl -n strest exec strest-server-fast-8f456d97d-r67vb   -c conduit-proxy -- curl -s localhost:4191/metrics | grep -ve '^#' -e '_bucket' -e '_sum'
request_total{authority="target:8888",direction="inbound",tls="no_proxy_tls"} 1011714
response_total{authority="target:8888",direction="inbound",tls="no_proxy_tls",classification="success",status_code="200",grpc_status_code="0"} 1011713
response_latency_ms_count{authority="target:8888",direction="inbound",tls="no_proxy_tls",classification="success",status_code="200",grpc_status_code="0"} 1011713
tcp_open_total{direction="inbound",peer="dst",tls="no_identity"} 1
tcp_open_total{direction="inbound",peer="src",tls="no_proxy_tls"} 1
tcp_open_connections{direction="inbound",peer="dst",tls="no_identity"} 0
tcp_open_connections{direction="inbound",peer="src",tls="no_proxy_tls"} 1
tcp_read_bytes_total{direction="inbound",peer="dst",tls="no_identity"} 1735286
tcp_read_bytes_total{direction="inbound",peer="src",tls="no_proxy_tls"} 0
tcp_write_bytes_total{direction="inbound",peer="dst",tls="no_identity"} 1441450
tcp_write_bytes_total{direction="inbound",peer="src",tls="no_proxy_tls"} 0
tcp_close_total{direction="inbound",peer="dst",tls="no_identity",classification="success"} 1
tcp_connection_duration_ms_count{direction="inbound",peer="dst",tls="no_identity",classification="success"} 1
tls_config_reload_total{status="reloaded"} 103
process_cpu_seconds_total 46526
process_open_fds 110
process_max_fds 1048576
process_virtual_memory_bytes 37801984
process_resident_memory_bytes 15171584
process_start_time_seconds<PHONE_NUMBER>

If we look at the client-side, something interesting arises:
:; kubectl -n strest exec strest-client-98df4ccbd-zctzk -c conduit-proxy -- curl -s localhost:4191/metrics | grep -ve '^#' -e '_bucket' -e '_sum' -e 'tls="true"'
request_total{authority="target:8888",direction="outbound",dst_namespace="strest",dst_service="target",tls="no_identity"} 2268760
response_total{authority="target:8888",direction="outbound",dst_namespace="strest",dst_service="target",tls="no_identity",classification="success",status_code="200",grpc_status_code="0"} 2268758
response_latency_ms_count{authority="target:8888",direction="outbound",dst_namespace="strest",dst_service="target",tls="no_identity",classification="success",status_code="200",grpc_status_code="0"} 2268758
...

These metrcs are missing dst_pod labels, etc.
This suggests that strest-client's proxy did not get endpoint metadata for these endpoints from the Destination service.  I'm not yet sure whether to lay blame with the proxy or the destination service.

In this situation, this is resolved by running e.g.
:; kubectl -n strest delete po strest-server-fast-8f456d97d-r67vb strest-server-slow-79b46659dc-dgkdx

The replacement pods receive TLS traffic properly.
I think this points to either a data race in the destination service or a caching bug in the proxy.

Interestingly, this seems to also occur when scaling out an existing deployment.
I believe that this behavior occurs independently of whether TLS is enabled. A side effect of this behavior is that TLS may not be enabled for some endpoints.

The missing dst_ labels that you mention make it sound like this is the same issue as #783. I thought that issue had been fixed by adding readiness probes for the destination service, but that doesn't seem to be the case.

Here's an example strest.yml I used to repro

I managed to reproduce this in GCP with the strest.yml @olix0r posted above, by repeatedly scaling up and down the number of replicas in the strest deployment.
I ran controller/script/destination-client and watched the destination service's responses for the target service:
➜ bin/go-run controller/script/destination-client -path target.strest.svc.cluster.local:8888

Then I scaled the strest deployment down to 0 replicas and up to 15:
➜ kubectl -n strest scale deploy -l 'strest-server-profile=fast' --replicas=0
deployment.extensions "strest-server-fast" scaled

➜ kubectl -n strest scale deploy -l 'strest-server-profile=fast' --replicas=15
deployment.extensions "strest-server-fast" scaled

In the destination-client output, one of the responses had no metadata:
// ...

INFO[0033]
INFO[0034] Add:
INFO[0034] labels: map[namespace:strest service:target]
INFO[0034] - <IP_ADDRESS>:8888
INFO[0034]   - labels: map[conduit_io_control_plane_ns:liza-conduit deployment:strest-server-fast pod_template_hash:4250649811 pod:strest-server-fast-8694b8fd55-b6d6g]
INFO[0034]   - pod identity: strest-server-fast.deployment.strest.conduit-managed.liza-conduit.svc.cluster.local
INFO[0034]   - controller ns: liza-conduit
INFO[0034]
INFO[0035] Add:
INFO[0035] labels: map[namespace:strest service:target]
INFO[0035] - <IP_ADDRESS>:8888
INFO[0035]   - labels: map[]
INFO[0035]
INFO[0035] Add:
INFO[0035] labels: map[namespace:strest service:target]
INFO[0035] - <IP_ADDRESS>:8888
INFO[0035]   - labels: map[conduit_io_control_plane_ns:liza-conduit deployment:strest-server-fast pod_template_hash:4250649811 pod:strest-server-fast-8694b8fd55-nlv4r]
INFO[0035]   - pod identity: strest-server-fast.deployment.strest.conduit-managed.liza-conduit.svc.cluster.local
INFO[0035]   - controller ns: liza-conduit

// ...

 The destination service watches for updates to both pods and endpoints. The pod updates are used for form an in-memory index of pods by their IP address. The endpoints updates provide the set of currently available IP addresses for all pods matching a given service. When a new set of IP addresses is received, the destination service diffs those with the last know set and streams any new addresses back to the proxies. Before sending the address updates, it supplements them with additional information about the pod, using the in-memory index of pods by their IP addresses.
Testing locally, it appears possible that the endpoints update that's received by the Destination service can include IP addresses that have not yet made it into the pod index. This causes the destination service to stream the address with no owner labels or TLS identity information.
A sample endpoints update event looks like this:
updateEndpoints: &Endpoints{
  ObjectMeta:metav1.ObjectMeta{
    Name:target,
    Namespace:strest,
    ResourceVersion:49848,
  },
  Subsets:[
    {
      [
        {<IP_ADDRESS>  0xc4205d2290 ObjectReference{
          Kind:Pod,
          Namespace:strest,
          Name:strest-server-fast-5657d6bf4b-c9t5w,
          ResourceVersion:49330,
        }}
        {<IP_ADDRESS>  0xc4205d22a0 &ObjectReference{
          Kind:Pod,
          Namespace:strest,
          Name:strest-server-fast-5657d6bf4b-ptjzf,
          ResourceVersion:49846,
        }}
        {<IP_ADDRESS>  0xc4205d22b0 &ObjectReference{
          Kind:Pod,
          Namespace:strest,
          Name:strest-server-slow-bd85d58f6-hm98f,
          ResourceVersion:49345,
        }}
      ]
      []
      [{strest-grpc 8888 TCP}]
    }
  ],
}

This update triggered the following message in the destination service's logs:
time="2018-07-06T01:58:00Z" level=error msg="Could not find running pod for IP [<IP_ADDRESS>], this IP will be sent with no metric labels."

Note that the resource version of the endpoints update and the resource version of the missing pod are very close to each other (49848 and 49846). This means that the two updates fired almost simultaneously, and the endpoints update won the race, causing us to stream that address with no pod data.
It's also worth noting that the endpoints update already includes the pod name and namespace along with the IP address. So we can remove the additional index of pods by IP that we're using and instead just rely on the primary index of pods by namespace, name. That won't fix the race, but at least it will be less overhead when pod updates are received.
To fix the race, I think we should ignore any new addresses that can't be found in the primary pod index. When a deployment is scaled out in Kubernetes, that triggers multiple endpoints update events to fire, as pods move from the Pending to Ready state. If we ignore any updates for pods that cannot be found in the pod index, there's a very high likelihood that the pod will be found by the time the next endpoints update fires, and at that point we can stream it. The downside of this approach is that if the pod still can't be found by the final endpoints update, then the proxies will not route to it. This seems better that the existing implementation, however, of routing with incomplete information, which causes us to misreport stats and bypass TLS.

One thing to note: from the proxy's perspective, it's not really a problem that we get results that lack labels -- it IS a problem that we don't get an update when labels are available. I'm think it's fine to change this to avoid notifying the proxy when no labels are present; though, if it's simpler for the destination service, it should also be Fine if these are delivered as the labels become available.


CLI examples in readme have wrong syntax

The CLI examples in the readme, like e.g. javascript-obfuscator input.js --output out.js --sourceMap true --sourceMapBaseUrl 'http://localhost:9000' --sourceMapFileName example have the wrong syntax. They use the JS options syntax, instead of the CLI syntax.
The example in this case should be :
javascript-obfuscator input.js --output out.js --source-map true --source-map-base-url 'http://localhost:9000' --source-map-file-name example
I was fighting with this for a bit wondering why the source maps were not generated.

Wow, thank you. Eill fix it today

<EMAIL_ADDRESS>is out!


Fixing id to 'What Are We Building?' section

Found an issue in "What are we building?" section - it's not highlighted, despite clicking or scrolling trough it. Fixed it locally and created this HUGE pull request.

Thanks


[BUG] - DropdownItem Events onPress doesn't work

NextUI Version
2.3.6
Describe the bug
I have one Dropdown component with one item logout, I want to run a function and log string when i click on logout, I used one of DropdownItem event onClick and pass anonymous function that  log string but it doesn't show me anything on console when i click on logout. I have also read the documentation there were also mention one thing that onClick is Deprecated use onPress insted but this also give me the same result.
 <Dropdown placement="bottom-end">
        <DropdownTrigger>
             <Avatar
                  isBordered
                  as="button"
                  className="transition-transform"
                  src="https://i.pravatar.cc/150?u=a042581f4e29026704d"
              />
        </DropdownTrigger>
        <DropdownMenu aria-label="Profile Actions" variant="flat">
            <DropdownItem key="profile" className="h-14 gap-2">

Signed in as

                 <p<EMAIL_ADDRESS>            </DropdownItem>
            <DropdownItem key="settings">My Settings</DropdownItem>
            <DropdownItem key="team_settings">Team Settings</DropdownItem>
            <DropdownItem key="analytics">Analytics</DropdownItem>
            <DropdownItem key="system">System</DropdownItem>
            <DropdownItem key="configurations">
                    Configurations
            </DropdownItem>
            <DropdownItem key="help_and_feedback">
                    Help & Feedback
            </DropdownItem>
            <DropdownItem
                 key="logout"
                 color="danger"
                 onClick={() => {
                    console.log('hhh');
                 }}
                  >
                    Log Out
           </DropdownItem>
      </DropdownMenu>
</Dropdown>

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Click on logout
Expected behavior
it should log "hhh" string
Screenshots or Videos
No response
Operating System Version
linux
Browser
Chrome

I couldn't reproduce the issue.

Maybe you can check if you have disabled the info log.

Closing due to inactivity


Keep the word on the screen thoughout the round in a way that the player is always aware of what the word is

Initial prototype:
76a5b7b1badc39ba26d843ed73a682353b7557a2
Updates to follow


Implementing for Android Application

Hi, I want to embed this on an Android Application. I'm no expert on Javascript and etc. but I do know few things.
I've researched a bit and found out that maybe I can use Ionic in order to implement this on Android. Any help would be nice. Thanks in advance.

Hi @atesahmet0, I don't know much about Android, but it sounds like you are on the right track. A good place to ask for help is on Discord.