feat: 🚀 preminliary implementation of plugin-eslint.

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/xun082/create-neat/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Closes #133
Related to #

What is the new behavior?

 实现 eslint 插件开发 #133
Does this PR introduce a breaking change?
[ ] Yes
[ x ] No

Other information

应该关联到重构的主issue


 should have less visual weight than  in ToC

In the new stylesheet, 5th-level headings are indented the same amount as 4th-level, and are shown in the same font as 3rd-level headings which makes them look too important:

https://w3c.github.io/tr-design/src/sample.html shows them indented farther, which works, or they could be the same smaller font as their section number.

Yeah, I think @fantasai just made that indentation change this weekend.  I'll copy it over.

And done.


Example program cannot connect in Centos7 VM

Hello,
I was unsure where else to put this so I am putting it here.
I was unable to get your example file to run properly. This is on a centos 7 vm and lksctp-tools were installed through yum. The program compiles fine but fails on connect line here
https://github.com/phsym/sctp-sys/blob/master/examples/dirty.rs#L33
If you have any advice or comments, it would be appreciated. Thanks!

Hi,
Do you have a sctp enpoint listenning on <IP_ADDRESS>:3868 ? If not, you can create one with netcat.

Oh I didn't. Thanks! I actually ended up deciding not to use it, so I'm going to close the issue. Thanks still!

You can have a look to https://github.com/phsym/rust-sctp if you need a higher level library. It's still quite basic for now, but do its job


Homographs in slugs for different pages and different languages should not raise MultipleObjectsReturned

Your site has two sibling pages:
# a page about sticks
/it/bastone
/fr/canne
/en/cane

# a page about dogs
/it/cane
/fr/chien
/en/dog

At present, as soon as you try to publish (it will let you save a draft) the Italian translation, you'll get:
MultipleObjectsReturned at /it/cane/
get() returned more than one Page -- it returned 2!

Issues to be decided:

[ ] should we allow the creation of the slug? We would need to stop ignoring the language prefix when processing URLs.
[ ] if we do, how would we decide what serve when the user asked for /fr/cane/ - should it serve up chien or canne (see #3547 on django CMS's page-guessing behaviour)
[ ] if we don't, we should advise the user of a slug conflict, instead of raising the MultipleObjectsReturned error.

@evildmp @ojii @mkoistinen further opinion on this?
I don't think we could handle this in 3.1

I have no further opinion, the way you outlined it above is the correct way this should be done, IMO.


🆕 Software Suggestion | Adnauseum

What’s PrivacyTools take on Adnauseum?
Adnauseum
Fingerprinting protection??
Description (From their website)
As online advertising becomes ever more ubiquitous and unsanctioned, AdNauseam works to complete the cycle by automating ad clicks universally and blindly on behalf of its users. Built atop uBlock Origin, AdNauseam quietly clicks on every blocked ad, registering a visit on ad networks' databases. As the collected data gathered shows an omnivorous click-stream, user tracking, targeting and surveillance become futile. Read more about AdNauseam in this paper.
AdNauseam is a free browser extension designed to obfuscate browsing data and protect users from tracking by advertising networks. At the same time, AdNauseam serves as a means of amplifying users' discontent with advertising networks that disregard privacy and facilitate bulk surveillance agendas.

@Thorin-Oakenpants curious to know what your specific views on this are.
I seem to remember reading about this, and that AdNauseam actually was worse for fingerprinting than blocking adverts altogether.
Aside from that I seem to remember something about advertisers being able to from a fingerprint filter out AdNauseam users anyway.
Unfortunately I cannot find the source.

waste of time and a stupid gimmick in my opinion - why add overhead: just block the offending third parties / scripts etc and be done with it.
AMO

It is best to remove or disable other adblockers (such as uBlock or Adblock Plus) as they may block ads before AdNauseam can identify or collect them

FFS: the whole point of adbocking (and custom uBO blocks) is to make sure the 3rd parties aren't connected to. And allowing ads is a malware risk
At this point I can't take it seriously, TBH. I understand the want to strike back at corporate surveillance, but this is a solution to a problem that doesn't exist. If you block ads you shouldn't really see any.  It doesn't get any more basic than that.
If you're interested in something, say you're in the market for some hiking boots - then go to specific websites are check them out directly in Private Browsing mode or something (or you know, FPI, sanitize, containers, compartmentalize, dress up as Batman).

And allowing ads is a malware risk

Yeah I was thinking that when I was writing (but forgot to put it in my reply. It's not the first time malware has been distributed through advertising networks through exploits.


MOUSE_DOWN, MOUSE_UP, CLICK events firing on trackpad touch on MacOS 10.14.5 (Neko/CPP)

I am seeing MOUSE_DOWN, MOUSE_UP and CLICK firing when I only touch the trackpad on my Macbook in MacOS 10.14.5, on Neko and CPP targets. I also use Debian Testing on the same machine and I am not seeing this behaviour there, so it doesn't seem like a hardware issue.
I have the "Tap to click" and other such options in the MacOS Trackpad preferences disabled, and I am not having trouble with touches registering as clicks in other applications.
This happens with whatever type of contact I make with the trackpad - eg. dragging my finger to move the mouse cursor causes all three events to fire.
I'm not sure if this is due to some obscure option I've set somewhere back in the mists of time, but hopefully someone else can confirm it happening on another Mojave installation.
MacOS 10.14.5 (Mojave)
OpenFL 8.9.1
Lime 7.5.0

Sample Main.hx:
package;

import openfl.display.Sprite;
import openfl.events.MouseEvent;

class Main extends Sprite
{
    public function new()
    {
        super();
        stage.addEventListener(MouseEvent.CLICK, function(e) {
            trace('click');
        });
        stage.addEventListener(MouseEvent.MOUSE_DOWN, function(e) {
            trace('down');
        });
        stage.addEventListener(MouseEvent.MOUSE_UP, function(e) {
            trace('up');
        });
    }
}

I have narrowed this down to Lime version 7.4.0 and up, so I will start an issue there and this one should presumably be closed?

Someone can reopen it if they think it's useful here.


Feature: Track Habits for Days in the Past

After to starting to use dijo yesterday, I wanted to enter some data from the past days, but I couldn't find a way to do that.
Personally I can also clearly imagine wanting to track a habit a day or two after, because I were busy or didn't have my computer available or something, so I think this is rather necessary.

This is a very important feature for me too. I track activities in other application and I wanted to automatically import my history.
I noticed that the data for the app is stored in $HOME/Library/Application\ Support/rs.nerdypepper.dijo/habit_record.json (OSx). As a workaround you could append to this file. But I agree there should be a standard way to inject data here.
[
  {
    "type": "Count",
    "name": "my-project-example",
    "stats": {
      "2020-07-21": 1
    },
    "goal": 3,
    "auto": false
  }
]

This is definitely on the list of things to add, and it has been requested over at #10. I would prefer it if feature requests are documented in that thread, it makes things a lot easier for me to track. You may choose to receive notifications only if you are mentioned.

Closed by latest release (v0.2.6).


helm search command

helm search [arg] should search all of the repository cache files in $HELM_HOME/cache for a regex match on name or any keywords (located in $HELM_HOME/cache/) and return repo-name/chart-version.
For example,
helm search nginx might return something like this:
Charts:
hotdog-charts/nginx-1.0.0
kubernetes-charts/nginx-1.0.0
kubernetes-charts/nginx-2.0.0
wiggly-lamb-charts/nginx-1.0.0

More context: https://gist.github.com/michelleN/002c799026e90bdfb8d27f47557c1223


chore: switch to pinning a major or minor version instead of a patch version

Once https://github.com/blue-build/github-action/pull/19 is released, we'll have the @v1, @v1.1, and @v1.1.0 tags available.
I'm unsure whether to pin to the major (v1) version or the minor (v1.1) version. With major versions it would be very automatic for users, but they also wouldn't get notified of new features by Dependabot.

Once blue-build/github-action#19 is released, we'll have the @v1, @v1.1, and @v1.1.0 tags available.
I'm unsure whether to pin to the major (v1) version or the minor (v1.1) version. With major versions it would be very automatic for users, but they also wouldn't get notified of new features by Dependabot.

If minor versions fix some ground-breaking change, I think that we should release that as an exception.

If minor versions fix some ground-breaking change, I think that we should release that as an exception.

Patch versions (the third number) have fixes, minor versions have features. Although, if there are both fixes and features in line, it will turn into a minor version. Hmm. I'm not sure exceptions are possible here, though.

5d9cc76 closes this
Was supposed to be a PR but I forgot to check out the branch. But oh well...


Comparison of rephetio metapath contributions and unsupervised p-values

This noteboook is similar to the one comparing compound rankings, except that it looks at individual metapaths for each compound instead of compounds as a whole. Interestingly, where the other notebook finds a weak but statistically significant correlation, this notebook finds no correlation between the p values for a metapath and the weight the metapath is assigned in a supervised model.

I talked with Daniel about the result above and he said that the file that I was using didn't contain the actual model weights but the weights for the model normalized so that each compound/disease pair's positive weights would add to one. It is reasonable that there wouldn't be a correlation, because a metapath's rank within compound/disease pair should only correlate weakly with the global p-value.
Upon using the raw positive weights, we get the cool results below. I'm not sure what causes the stratification (maybe @dhimmel does), but it's encouraging that the stronger metapath weights have stronger p-values.

I'm not sure what causes the stratification (maybe @dhimmel does), but it's encouraging that the stronger metapath weights have stronger p-values.

Color by metapath and thou shall see.

The stratifications seem to be strongly related to individual metapaths

Good call, the legends were already ordered by y-value (I posted the wrong image), but the standard error curves are now colored according to their metapaths.


Enforce a max_fevals on all strategies

Modify the strategies and in particular _cost_func to ensure a strategy does not use more than max_fevals evaluations. This should be possible through counting the length of the list of 'results' in _cost_func.

already supported:

bayes_opt

hillclimber-based (already support max_fevals):

greedy_mls
ordered_greedy_mls
greedy_ils
mls

scipy optimize based:

minimize
basinhopping
diff_evo
dual_annealing

custom implementations:

random_sample
genetic_algorithm (not strictly enforced yet)
pso
simulated_annealing
firefly_algorithm


[dv,usbdev] usbdev Sequences PR

This PR contains following sequences:
-> usbdev_resume_link_active_vseq
-> usbdev_stall_trans_vseq

@jdonjdon kindly review it.
Thanks

@jdonjdon kindly review it.
Thanks

Please could you chop this up into one commit per sequence, and one PR per commit? It should make the review much simpler.

Please could you chop this up into one commit per sequence, and one PR per commit? It should make the review much simpler.

ok I'll


adds defined type for S3 backups

We want to stop backing up to a remote server and backup to an
S3 bucket instead. We should backup everything in /srv/logs/log-1/
except for the cdn directory which contains the Bouncer CDN logs.

I think this looks good, second pair of eyes appreciated :+1:

This looks good to me. It will need some changes to add the credentials in ci-deployment. What AWS environment should this be running against, production? (Maybe a question for @rjw1)

https://github.gds/gds/ci-deployment/pull/78

Hm, I'm having trouble provisioning a machine with this pull request. The error is:
==> transition-logs-1: Error: Duplicate declaration: Package[python-gobject-2] is already declared; cannot redeclare at /tmp/vagrant-puppet/modules-bd297425287331245c5fd118ef6e6630/duplicity/manifests/packages.pp:12 on node transition-logs-1.internal

There's the same problem for python-paramiko. I'll open a pull request on the duplicity module to fix it.

https://github.com/alphagov/puppet-duplicity/pull/11


Upgrade Conscrypt to 2.5.1

Motivation:
Conscrypt 2.5.1 is available and it's a good idea to upgrade to the latest version.
Modification:
Upgraded Conscrypt 2.4.0 to 2.5.1
Result:
Newer Conscrypt version.

@netty-bot test this please


Board Review: Event Grid System Events

Thank you for submitting this review request. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
To ensure consistency, all Tier-1 languages (C#, TypeScript, Java, Python) will generally be reviewed together.  In expansive libraries, we will pair dynamic languages (Python, TypeScript) together, and strongly typed languages (C#, Java) together in separate meetings.
For Tier-2 languages (C, C++, Go, Android, iOS), the review will be on an as-needed basis.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline

Responsible service team: Azure Communication Services
Main contacts: @JoshLove-msft, @osaghaso
Expected code complete date: 2/3/23
Expected release date: 2/7/23

About the Service

Link to documentation introducing/describing the service:
Link to the service REST APIs:  https://github.com/Azure/azure-rest-api-specs/pull/22286, https://github.com/Azure/azure-rest-api-specs/pull/22272
Link to GitHub issue for previous review sessions, if applicable:

About the client library

Name of the client library: Azure.Messaging.EventGrid

Artifacts required (per language)
Please read through “API Review” section here to understand how these artifacts are generated. It is critical that these artifacts are present and are in the right format. If not, the language architects cannot review them with the SDK Team’s API review tool.
.NET

APIView Link: To be added

Java

APIView Link: To be added

Python

APIView Link: To be added

TypeScript

APIView Link: To be added

For all other languages, send a request to the Architecture Board to discuss the best format on individual basis.
Thank you!

@JoshLove-msft
The next hold for an Event Grid would be Feb 27th. Is that date okay?
And any timezones to consider here? or will 2:05PM - 4PM PST work fine?

This was meant to be for the Feb release - is it not possible to do it this week or next week?

This was meant to be for the Feb release - is it not possible to do it this week or next week?

Sorry about that. Our HOLDs for Event Grids normal time lapsed in the new year.
The timeslot tomorrow opened up if the teams could be ready then and I can okay it with the architects.

Recording (MS INTERNAL ONLY)


vkSetDebugUtilsObjectNameEXT crashes during recording

Looks like vkSetDebugUtilsObjectNameEXT is not implemented in the capture layer and I get crashes in the NVIDIA driver when calling it, presumably because the passed in object pointer is not unwrapped to the underlying object that the driver knows.
This was reproduced with the gfxreconstruct layer of the <IP_ADDRESS> SDK on Windows.
Thanks for looking into it!

This should be fixed in the latest dev branch.  It was addressed with #449, in response to issue #446.

I can confirm this doesn't crash when making a build from latest dev branch. Closing. Thanks!


Use multiple mainFields in resolver

Do you want to request a feature or report a bug?
I want to request a feature.

What is the current behavior?
Current behavior is to use one of the mainFields and the first matched field will be used, ignoring all others.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Use multiple mainFields, i.e. if mainFields is [["module", "main", "style", "styles"]], if one of main fields in mainFields[0] matches, then inject assets in all mainFields[0] found from vendor's package.json.
If this is a feature request, what is motivation or use case for changing the behavior?
Because this will allow to import .css assets with just require("package"), if mainFields is [["module", "main", "style", "styles"]].
Currently module authors include "style" field in their package.json and this will be quite useful to import css assets author intended for the module with one line instead explicitly requiring each individual css file which is the case now to my understanding.
i.e. if I do require("bootstrap") in vendor.js, then all .js assets and .css assets would be imported.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Using webpack 3.8.1, nodejs v6.11.2 , windows 8.1

You can achieve this using loaderContext.getResolve({ mainFields: ["module"] }) and loaderContext.getResolve({ mainFields: ["main"] }) and etc, css-loader will load style field by default in the next release


MINOR: update security docs

minor doc change: replaced "broker.properties" with "server.properties"

cc @ijuma

@ijuma  Can you pls merge this.


fix(Image): preview toolbar error

close #4157

Codecov Report
Base: 62.53% // Head: 62.53% // No change to project coverage :thumbsup:

Coverage data is based on head (13f92be) compared to base (673f081).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4159   +/-   ##
=======================================
  Coverage   62.53%   62.53%
=======================================
  Files        1069     1069
  Lines       22380    22380
  Branches     5862     5862
=======================================
  Hits        13996    13996
  Misses       6863     6863
  Partials     1521     1521

Impacted Files
Coverage Δ

src/image/src/ImagePreview.tsx
30.73% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


K8S - cannot list resource "nodes" in API group "" at the cluster scope

Can't browse K8S pod, I don't have role to list Nodes, we use a restricted cluster, and I have this error with xpipe:
Error from server (Forbidden): nodes is forbidden: User "..." cannot list resource "nodes" in API group "" at the cluster scope

Oh, I have not considered the case with limited permissions. I think I can work around this without listing nodes in the next update.
But you have any other permissions usually required that you need to query pods, enter shells into containers, etc. or is there any other permissions I also need to think twice about?

I have this for production namespace (can't enter shells for example):
PS C:\> kubectl auth can-i --list  --namespace <namespace>
Resources                                       Non-Resource URLs   Resource Names   Verbs
selfsubjectaccessreviews.authorization.k8s.io   []                  []               [create]
selfsubjectrulesreviews.authorization.k8s.io    []                  []               [create]
*.chaos-mesh.org                                []                  []               [get list watch]
externalsecrets.external-secrets.io             []                  []               [get list watch]
pushsecrets.external-secrets.io                 []                  []               [get list watch]
secretstores.external-secrets.io                []                  []               [get list watch]
poddisruptionbudgets.policy                     []                  []               [get list watch]
pods.metrics.k8s.io                             []                  []               [get watch list]
                                                [/api/*]            []               [get]
                                                [/api]              []               [get]
                                                [/apis/*]           []               [get]
                                                [/apis]             []               [get]
                                                [/healthz]          []               [get]
                                                [/healthz]          []               [get]
                                                [/livez]            []               [get]
                                                [/livez]            []               [get]
                                                [/openapi/*]        []               [get]
                                                [/openapi]          []               [get]
                                                [/readyz]           []               [get]
                                                [/readyz]           []               [get]
                                                [/version/]         []               [get]
                                                [/version/]         []               [get]
                                                [/version]          []               [get]
                                                [/version]          []               [get]
configmaps                                      []                  []               [list get watch]
endpoints                                       []                  []               [list get watch]
events                                          []                  []               [list get watch]
namespaces                                      []                  []               [list get watch]
persistentvolumeclaims                          []                  []               [list get watch]
pods/attach                                     []                  []               [list get watch]
pods/exec                                       []                  []               [list get watch]
pods/log                                        []                  []               [list get watch]
pods                                            []                  []               [list get watch]
podtemplates                                    []                  []               [list get watch]
resourcequotas                                  []                  []               [list get watch]
serviceaccounts                                 []                  []               [list get watch]
services                                        []                  []               [list get watch]
deployments.apps/rollback                       []                  []               [list get watch]
deployments.apps/scale                          []                  []               [list get watch]
deployments.apps                                []                  []               [list get watch]
replicasets.apps/scale                          []                  []               [list get watch]
replicasets.apps                                []                  []               [list get watch]
statefulsets.apps/scale                         []                  []               [list get watch]
statefulsets.apps                               []                  []               [list get watch]
horizontalpodautoscalers.autoscaling            []                  []               [list get watch]
cronjobs.batch                                  []                  []               [list get watch]
jobs.batch/status                               []                  []               [list get watch]
jobs.batch                                      []                  []               [list get watch]
ingressroutes.traefik.containo.us               []                  []               [list get watch]
ingressroutetcps.traefik.containo.us            []                  []               [list get watch]
middlewares.traefik.containo.us                 []                  []               [list get watch]
middlewaretcps.traefik.containo.us              []                  []               [list get watch]
serverstransports.traefik.containo.us           []                  []               [list get watch]
tlsoptions.traefik.containo.us                  []                  []               [list get watch]
traefikservices.traefik.containo.us             []                  []               [list get watch]
replicationcontrollers                          []                  []               [list]
daemonsets.apps                                 []                  []               [list]
podsecuritypolicies.policy                      []                  [psp-project]    [use]
podsecuritypolicies.policy                      []                  [restricted]     [use]

So I fixed the issue when nodes could not be listed and that will be released in the next update.
But it's going to be complicated when you don't have permission to enter shells as that kinda removes most of the functionality as you can't open a terminal session or file browser session then. Assuming from the permissions you posted you also can't start, stop, control pods, I don't think there's anything useful that you can do in xpipe with these limited permissions other than listing and checking the status for that cluster.

Thanks for your fix!
I cant' list nodes on all environements. But on environments other than production, I have permission to enter shells.

This is now released. Let me know whether everything works for you now

@crschnick
I have now this error: cannot list resource "pods" in API group "" at the cluster scope
I can list pod at the namespace scope but not at the cluster scope

I guess this error is now more expected, XPipe uses contexts instead of namespaces to access clusters so I think that you would have to list permissions for the context not the namespace. I probably missed that you listed namespace permissions


docs: add Khushi Marothi's introduction

added intro .

Thanks for adding your introduction. Make sure to join our community, by creating an issue here: https://github.com/The-Lively-Developers-Community/become-a-member


How to render more lines ?

current problems on android:

if you scroll a bit faster, the editor will easily become blank.
if you scroll the cursor out of the container, the keyboard will be dismissed
sometimes when you click on the editor, the keyboard will show up, but then quickly dismissed due to ⇖

video demostrating point 3:
https://user-images.githubusercontent.com/11593903/233276876-cfa66c54-d246-4a33-80a6-685d360de834.mp4
this css will render all lines, but too slow :
	.CodeMirror {
		width:auto;
		height:auto;
	}

viewportMargin:50


shims/mac: handle usage of Homebrew make

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

We have a handful of formulae that use Homebrew make to build. Doing
this evades our compiler shims. Let's try to avoid this by allowing our
shims to support usage of Homebrew make by calling it as gmake in
the formula.

Thanks @carlocab!


Delegate access information is out of date

The page https://docs.microsoft.com/en-us/dynamics365/outlook-app/enable-delegate-access has a blue section that has material and typographic issues needing an update.
In the "Prerequisites" section there is a link to an article that talks about delegated access. However, there seems to be a systemic change... if one were to follow it, they would get a  message that reads:

"The Delegates page is not available. Cannot access the Outlook folder."

More importantly, they would be inclined to believe that material permission changes are necessary for calendaring; they effectively tell you to give full rights to a mailbox. In fact, if you were to follow the guide you would end up on this article.  However, that's not what is true today -- something changed in Exchange.  Instead you follow https://docs.microsoft.com/en-us/exchange/troubleshoot/outlook-issues/cannot-view-outlook-delegates-page and you end up with Exchange Online's "Send on Behalf Of" permission. This is far more desirable.

"Configure delegate access in Microsoft Outlook. At a minimum, a delegated user must have at least Editor permission on the delegated mailbox. For more information, see Allow someone else to manage your mail and calendar."

Finally, the text below has overlap and makes first item redundant:

Things to verify before enabling delegate access in App for Outlook:

Delegate access is set up correctly in Outlook.
The delegated user has at least Editor permissions on the delegated mailbox.

@wiicode Thank you for the feedback. Let me verify the information with our internal team. I'll get back to you when I hear back.
Thanks,
Mints

@wiicode, Our internal team has reviewed/tested the steps in the topic and has updated it accordingly.
Thank you again for submitting feedback.
Thanks,
Mints


Revert "Don't run CI on Node 0.10"

Reverts facebookincubator/create-react-app#1521

as @gaearon was saying, lerna dropped node v0.10, so I'm afraid, no CI 😞

Actually :scream:

I'm persistent. ;)


Install updates from Files

Fixes #1513
I implemented the feature to install updates via a button in the about settings page.

@Thomas1664 Instead of adding a button to check for updates, it should autmaticly check for udpates when launching the app.

I didn't want to implement it yet because if the code is wrong the app crashes

I didn't want to implement it yet because if the code is wrong the app crashes

That's fine, we will test it in a flight group to make sure it works correctly first, and if needed, we can wrap it in a try/catch.

@Thomas1664 Instead of adding a button to check for updates, it should autmaticly check for udpates when launching the app.

No need. It will slow down the app startup. Also this app is available on the Store so it will check for updates automatically. Users will click the update button only if the store doesn't check,.

@Thomas1664 Is this because the app is not connected to the Store in our debug builds?

Yes

Yes

How did you get around this?

Yes

How did you get around this?

See the attatched issue. We used a flight group.

See the attached issue. We used a flight group.

interesting. i've been struggling with this. I have a flight group also, but this still happens.

@myokeeh We ended up wrapping this in a try/catch, for some reason we still get the error every time and updates are not detected, but at least the app isn't crashing.

@yaichenbaum, so GetAppAndOptionalStorePackageUpdatesAsync is in fact still broken--no updates detected. 🤷♂I hope somebody at Microsoft gets on this and get it fixed.


Negative values on current day

Hi, thanks for your script! However, I also face the issue regarding the high negative numbers.
I stopped HA and deleted the interim statistics from the database before starting the import, as described:

If you are restoring data into a fresh Home Assistant database, we must delete any interim statistics Home Assistant has written since the database was created. The reason for this is that a sum column is tracked for each entity in short term statistics (representing the all-time total of the statistic), which Home Assistant will have reset to 0 when it recreated the database. This column in the short-term table is used to update a corresponding sum column in the long-term statistics table during each statistics run. If we do not get rid of the interim statistics, the sum of each statistic will reset to 0, despite having large historical values. This will short up as massive negative spikes in the statistics values in the energy dashboard, for example.
To wipe the interim statistics, verified that your backup was successful, and run this command from the command line:
sqlite3 home-assistant_v2.db "delete from statistics_short_term; delete from statistics;"

However, even with this deletion of the interim statistics, the current day still has these massive negative spikes in the statistics values:

Do you know how this can be resolved, or is there maybe some way to override them manually for the current day?

Okay so I found out it's actually pretty easy to (mostly) fix the statistics:
Apparently the value for all of the sensors already are a counter (counted in kWh), and Home Assistant holds a separate counter. By determining in the statistics_meta table what the id of the statistic to be fixed is (select * from statistics_meta;), and updating it with UPDATE statistics SET sum = state WHERE metadata_id = <id>; and UPDATE statistics_short_term SET sum = state WHERE metadata_id = <id>; the energy dashboard displays reasonable values again


Multi-format word fixes, round 3

Closes #1675, #1984 I think. Redo of #1771 and #1942. Multiple formats within the same word behave now, I hope.
The diff is kind of a mess, but this PR ignores formatRange.end when word wrapping. All text between textIndex and the next space/break/end of text is placed at once, and all format changes, word wrapping, and breaking of long words are handled within each of those placements.

Just for info, defaultTextFormat fixes, left/rightMargin implementation, and RTL need this first.

Ahh I found an existing bug I might as well fix: breakIndex should have a +1 in the same way that spaceIndex does throughout the space handling chunk. I'm getting empty layout groups instead of the \n being included in the previous group.

Alright, I think this is to a point where it doesn't introduce any new issues.


show slide indicator dots even if only one slide

I have implemented a custom pagination using the "slide indicator dots" such as in this example https://jsfiddle.net/AdrienBe/L0v2s26t/
However, when there is only one slide, the "slide indicator dots" are removed. See example on https://jsfiddle.net/AdrienBe/m35n3qcj/
Is there a way to "fix" this (still show the relevant custom pagination) without forking the repo?
Thanks in advance

sure:
Fiddle
You can add an item, the js check the items and only change the slider if count(items) == 1
In the fiddle there is a little issue. You have set a border so the width is calculated in css and will not change if the viewport width changes...
If you can remove the border set the item width to 100% and all will be fine.

Does the job... but that's a pretty dirty hack :/
Adding the relevant HTML after the slider might be a simpler/cleaner solution even though not what I was hoping for.

@adrien-be .. when you have dirty ui, you need dirty hacks :wink:  ... I think you meant to say something like:

"WOW!! :tada: :astonished:
Thanks @mazzaker for taking your time to solve my problem!!, and even describing extra how to overcome an additional problem with my ui... Really appreciate your help. Good day! :bow:"

Cheers, Si.

and: if you really want a border, nest a box inside the slider with the border... no hacky the box-model

@simeydotme answer edited. Still, I disagree that dirty hacks are always needed. Anyhow, not a big deal.


add link for ALI

I just noticed that there is a github link available for ALI (Adversarially Learned Inference): https://github.com/IshmaelBelghazi/ALI

Thanks for the link @emckenzi123 , sorry for the late response. Will add it :)


Apply pre- and post-submit workflows to release branches.

This is in preparation for using release branches to create patch (AKA "bugfix") releases.

This change is


[1.24.x] Fix build-cli issue

Similar to https://github.com/kiegroup/kogito-operator/pull/1258
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains a link to the JIRA issue
[ ] Pull Request contains a description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've ran make before-pr and everything is working accordingly
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

How to retest this PR or trigger a specific build:

Run operator BDD testing
Please add comment: /jenkins test

Run RHPAM operator BDD testing
Please add comment: /jenkins RHPAM test

/jenkins test

PR job #625 was: UNSTABLE
Possible explanation: This should be test failures
You can find test error logs here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/625//artifact/test/logs/error/
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/625/display/redirect
See console log:

Console Logs
                               FAIL	github.com/kiegroup/kogito-operator/test	1508.293sFAILTests finished with code 1-------- Pruning namespacesI0804 08:54:18.869496   63578 request.go:655] Throttling request took 1.012768644s, request: GET:https://<IP_ADDRESS>:443/apis/image.openshift.io/v1?timeout=32s{"level":"info","T":"2022-08-04T08:54:20.484Z","logger":"kogito-operator-system","msg":"Deleting namespace","namespace":"kogito-operator-system"}{"level":"error","T":"2022-08-04T08:54:20.500Z","logger":"kubernetes_client","msg":"Failed to delete resource.","name":"kogito-operator-system","error":"namespaces \"kogito-operator-system\" not found"}{"level":"error","T":"2022-08-04T08:54:20.500Z","logger":"main","msg":"Error in deleting namespace","error":"Cannot delete namespace kogito-operator-system: namespaces \"kogito-operator-system\" not found"}Pruning namespaces done./home/jenkins/agent/workspace/kogito/kogito-operator-PR-check/test-------- Delete stucked namespacesProjects deleted:-------- Clean Cluster operators--- Clean subscriptions in openshift-operatorsNo resources found in openshift-operators namespace.--- Clean clusterserviceversions in openshift-operatorsNo resources found in openshift-operators namespace.--- Clean subscriptions in operatorsNo resources found in operators namespace.--- Clean clusterserviceversions in operatorsNo resources found in operators namespace.-------- Clean dependencies CRDsDelete cluster crds grafanadashboards.integreatly.orgcustomresourcedefinition.apiextensions.k8s.io "grafanadashboards.integreatly.org" deletedDelete cluster crds grafanadatasources.integreatly.orgcustomresourcedefinition.apiextensions.k8s.io "grafanadatasources.integreatly.org" deletedDelete cluster crds grafananotificationchannels.integreatly.orgcustomresourcedefinition.apiextensions.k8s.io "grafananotificationchannels.integreatly.org" deletedDelete cluster crds grafanas.integreatly.orgcustomresourcedefinition.apiextensions.k8s.io "grafanas.integreatly.org" deletedDelete cluster crds backups.infinispan.orgcustomresourcedefinition.apiextensions.k8s.io "backups.infinispan.org" deletedDelete cluster crds batches.infinispan.orgcustomresourcedefinition.apiextensions.k8s.io "batches.infinispan.org" deletedDelete cluster crds caches.infinispan.orgcustomresourcedefinition.apiextensions.k8s.io "caches.infinispan.org" deletedDelete cluster crds infinispans.infinispan.orgcustomresourcedefinition.apiextensions.k8s.io "infinispans.infinispan.org" deletedDelete cluster crds restores.infinispan.orgcustomresourcedefinition.apiextensions.k8s.io "restores.infinispan.org" deletedDelete cluster crds kafkabridges.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkabridges.kafka.strimzi.io" deletedDelete cluster crds kafkaconnectors.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkaconnectors.kafka.strimzi.io" deletedDelete cluster crds kafkaconnects.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkaconnects.kafka.strimzi.io" deletedDelete cluster crds kafkamirrormaker2s.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkamirrormaker2s.kafka.strimzi.io" deletedDelete cluster crds kafkamirrormakers.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkamirrormakers.kafka.strimzi.io" deletedDelete cluster crds kafkarebalances.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkarebalances.kafka.strimzi.io" deletedDelete cluster crds kafkas.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkas.kafka.strimzi.io" deletedDelete cluster crds kafkatopics.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkatopics.kafka.strimzi.io" deletedDelete cluster crds kafkausers.kafka.strimzi.iocustomresourcedefinition.apiextensions.k8s.io "kafkausers.kafka.strimzi.io" deletedmake[2]: *** [Makefile:8: run-tests] Error 1make[2]: Leaving directory '/home/jenkins/agent/workspace/kogito/kogito-operator-PR-check/test'make[1]: *** [Makefile:16: run-smoke-tests] Error 2make[1]: Leaving directory '/home/jenkins/agent/workspace/kogito/kogito-operator-PR-check/test'make: *** [Makefile:327: run-smoke-tests] Error 2[Pipeline] sh+ rm -rf console.log[Pipeline] sh+ wget --no-check-certificate -qO - https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/625/consoleText+ tail -n 100

cherry-picked https://github.com/kiegroup/kogito-operator/pull/1254 to solve the Grafana problem

/jenkins test

PR job #628 was: UNSTABLE
Possible explanation: This should be test failures
You can find test error logs here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/628//artifact/test/logs/error/
Please look here: https://jenkins-kogito-tools.kogito-cluster-0ad6762cc85bcef5745bb684498c2436-0000.us-south.containers.appdomain.cloud/job/kogito/job/kogito-operator-PR-check/628/display/redirect
Test results:

PASSED: 9
FAILED: 1

Those are the test failures:

Deploy source files (dmn, drl, bpmn, bpmn2, ...) with CLI.Deploy .dmn source files with CLI using runtime springboot
Step HTTP POST request on service "dmn-springboot-example" is successful within 2 minutes with path "Traffic Violation" and body:: Timeout waiting for HTTP POST request on path 'Traffic Violation' to be successful

/jenkins test


WIP: Extend functionalities of the Upload component

What kind of change does this PR introduce?
Extended the present functionality of the Upload component. (Issue #254)
What is the current behavior?
The `Upload' component didn't support 'tracking'/retrieval of the uploaded files.
What is the new behavior?
• Added two props: files and setFiles which allow you to control the uploaded files using state from a parent component.
• Added previews for uploaded images in the story.
Additional context

Planning to add the ability to delete any of the uploaded files. Let me know what you think.

Done ✅

classic commit 🙃

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The best way to fake uuid.v4

In SUT is v4 method  uuid  used:
uuid = require('uuid')
uuid.v4()
'b14b1abb-180e-4d34-a59c-940bc2e77ac7'

What is the best way fake their returning value in Arrange phase?
// How should we replace 'b14b1abb-180e-4d34-a59c-940bc2e77ac7'
// Can I simply use chance.guid?
uuid = {v4: sandbox.stub().named('uuid.v4').returns(...)}

Why would you stub a method that generates a UUIDv4 with a method that generates a UUIDv4 when you could just use the method itself?

OK, in which cases I SHOULD do it?
I should test if - char has been removed from random uuid:
// Code in SUT
uuid.v4().replace(/-/g, '')

As I mentioned I should stub uuid.v4()  with string constant only?
Usage of  chance.guid is in this case unnecessary.

I'm sorry, but I don't think I understand the question :( Maybe someone else can help.

is chance.guid() guaranteed to produce unique result? Even if called in sequence in for loop? We have a case when it seemingly produces duplicates. It's intermittent, so we cannot reliably reproduce.

is chance.guid() guaranteed to produce unique result?

No. This is a library for fake data.


How to add arrows to features?

Like in https://www.biodalliance.org/ss/cview1.png, or as on biodalliance.org.

What kind of features are you working with here?
Do you mean the arrows that occur as part of the grouping lines, or the '>' and '<' characters which get prepended to feature labels.
In both cases, these are currently only available on 'grouped' features (typically gene structures), although I'd be open to adding some stylesheet option for finer grained control of when they're used, if there's demand.

Sorry I wasn't clear - I was talking about the arrows that occur as part of the grouping lines. We are using mRNA features with exons and CDS and I think they are grouped. Here's the XML sent out by our DAS server - https://gist.github.com/yeban/32fd7a0ce645037ab5c6. Please could you take a look and advise what's wrong?
/cc @Filip-Ter


[No QA] Add CLA workflow to repo

This repo doesn't have a CLA workflow, so we're adding one to make sure it's consistent with all our other repos
$ https://github.com/Expensify/Expensify/issues/438820

Yep, just realized I pasted the wrong one 🤦


Added the running rosa spots ability

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
Span the Rosa worker nodes with the help of machinepools by creating the default cluster with 3(M+W+I).
The remaining Spot worker nodes are WorkerNodes - 3

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please describe the System Under Test.
Please provide detailed steps to perform tests related to this code change.

Add the variable enable_spot_workers=true  in the install config file of rosa.

How were the fix/results from this change verified? Please provide relevant screenshots or results.
Ran the airflow cluster by creating a playground on the sailplane cluster.

@krishvoor ptal. 👋


mushroom-detail page needs functionality

Cards now link to mushroom-detail page when 'Details' button is clicked - logic needs to be updated to get the correct details for each mushroom

Steve would like some functionality that allows the user to click some metadata (that we have filters for) and be taken to the results page with only that filter applied.

Steve would like some functionality that allows the user to click some metadata (that we have filters for) and be taken to the results page with only that filter applied.

So from the specific mushroom-detail page that's about one species, click a filter that goes back to the results page with that filter applied? I'll look in to it

Updated


Migrate existing minimal BE implementation

https://github.com/EMBL-EBI-ABC/Pert_Cat_BE

To preserve commit history, migrated using direct merge: https://github.com/EMBL-EBI-ABC/PerturbationCatalogue/commit/d0bac5d75e29d6dcb2aa72bf58ab792c8cbda23e


unoredered_map erase

unordered map returns an iterator in these two cases, can we change the pxd file to  reflect this?
http://www.cplusplus.com/reference/unordered_map/unordered_map/erase/
Thank you,
Michael

this is a duplicate


Upgrade filebeat to 7.9.2

I tested this in 7 scenarios:

on-prem ("any" provider) Ubuntu Epiphany starting from develop  (running epicli apply and epicli upgrade)
on-prem ("any" provider) Centos Epiphany starting from develop  (running epicli apply and epicli upgrade)
on-prem ("any" provider) RedHat Epiphany starting from develop  (running epicli apply and epicli upgrade)
cloud with the k8s_as_cloud_service flag enabled (to test helm changes) using https://github.com/epiphany-platform/m-generic-epiphany-on-aks module

m-generic-epiphany-on-aks/examples/basic_flow$ kubectl --kubeconfig shared/build/azepi/kubeconfig get pods
NAME                      READY   STATUS    RESTARTS   AGE
filebeat-filebeat-dtkj6   1/1     Running   0          27m
filebeat-filebeat-s5c9x   1/1     Running   0          27m
node-exporter-w2z86       1/1     Running   0          25m
node-exporter-zt4t6       1/1     Running   0          25m

No issues encountered! :+1::innocent:

I just realized that there is a documentations update missing :)

Yes that's correct, also there is no changelog entry. But I'm glad code looks OK. I will add the rest shortly. :+1:


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cbr/ibm (source)
module
minor
1.28.1 -> 1.29.0

terraform-ibm-modules/event-notifications/ibm (source)
module
patch
1.14.4 -> 1.14.8

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
patch
4.16.8 -> 4.16.11

Release Notes

terraform-ibm-modules/terraform-ibm-cbr (terraform-ibm-modules/cbr/ibm)
v1.29.0
Compare Source
Features

added cloud logs support to the fscloud submodule profile (#568)

terraform-ibm-modules/terraform-ibm-event-notifications (terraform-ibm-modules/event-notifications/ibm)
v1.14.8
Compare Source
Bug Fixes

deps: update terraform-module (#335) (c74ff33)

v1.14.7
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cos/ibm to v8.14.5 (#333) (2d2268d)

v1.14.6
Compare Source
Bug Fixes

deps: update terraform-module (#331) (f7d52ad)

v1.14.5
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#330) (d19b633)

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.16.11
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/key-protect/ibm to v2.8.8 (#589) (0cc8088)

v4.16.10
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cbr/ibm to v1.29.0 (#588) (0319e5f)

v4.16.9
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#584) (92226cc)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.19.1

Your semantic-release bot :package::rocket:


ci: add testing on 1.18

Oof, I forgot to update my local main checkout first...

Hmm...2h waiting for actions to fire seems like something is hung...gonna close and reopen this to see if that helps


Pagination styling on activities page

Update pagination coding and styling - show current page, and provide more options to move around the pages. Make it look prettier (not just blue links and plain text)

This somehow got closed even though I did nothing towards it. Oops! Working towards this now.


fix: support k8s 1.29 1.30

What type of PR is this?

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

Fixes #688
Special notes for reviewers:
add k8s v1.29、v1.30 support

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

None

/lgtm


BookSearchTile Test Updates

Description
After meeting with Geoff, I figured out how to test when a user 'clicks' on the Add to List button in the BookSearchTile and ensure that the correct dropdowns are displayed with the correct text!
Requires using act(), awaits and async because React needs to be able to make the updates asynchronously to the states and the other components.
Linked Issue
#68

LGTM
Remmber to sync with master. Some of my merged PR may could result in the test failing.

Merged with master and resolved conflicts in the testing file!


net: pkt: Account for IP header length for allowable payload data

For calculating amount of payload data that can be added in a packet,
we need to subtract IPv6 or IPv6 header lengths from MTU.
Signed-off-by: Vakul Garg<EMAIL_ADDRESS>

The maximum data length that can be appended using net_pkt_append() should be set to TCP send_mss only if it is smaller than allowed payload length in net_pkt.

Can you explain what problem this patch fixes?

During test of http server sample using 6loble, I found tcp ctx send_mss
was set to 1220 (i.e ipv6_mtu - size of(v6_hdr) - size of(tcpheader).
However net_pkt->data_len was set to 1212 (since tcp opt hdr of 8 bytes) is
also considered. So variable max_len wrongly got increased to 1220 due to
unconditional assignment.
On 28-Nov-2017 5:49 PM, "Paul Sokolovsky"<EMAIL_ADDRESS>wrote:

The maximum data length that can be appended using net_pkt_append() should
be set to TCP send_mss only if it is smaller than allowed payload length in
net_pkt.
Can you explain what problem this patch fixes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zephyrproject-rtos/zephyr/pull/5179#issuecomment-347506115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM4O3GXKztp_FzTRh3o4PhUUlAOwSYZgks5s6_pPgaJpZM4Qstvp
.


Valid code in "No repeats please" challenge freezes browser up

Challenge Name:
No Repeats Please
https://www.freecodecamp.com/challenges/no-repeats-please
Issue Description
Browser freezes up when I run perfectly valid code on freecodecamp JS interpreter - have tested it in my browser's JS interpreter and it runs fine.
NOTE: I know that this isn't the final solution, but this code should still not be freezing the browser up. Also, I followed the suggestion of entering localStorage.clear() into the console. That, however, has cleared the code from ALL my challenges, but it still shows on my map that I completed them. Does this mean that I will not have to redo the challenges, even though the code is now missing?
Browser Information
Firefox 53.0.3 (32-bit)
Windows 10 Home Edition
Desktop
Code
WARNING: the code below might be a slight spoiler for some who still wish to do the challenge.

function perms(str)
{
  if (str.length === 0)
    return [""];
  else
  {
    var allPerms = [];
    for (var i = 0; i < str.length; i++)
    {
      var ch = str.charAt(i);
      var newString = str.substring(0, i) + str.substring(i + 1);
      var allThesePerms = perms(newString);
      for (var j = 0; j < allThesePerms.length; j++)
      {
        allThesePerms[j] = ch + allThesePerms[j];
      }
      allPerms = allPerms.concat(allThesePerms);
    }
    return allPerms;
  }
}

function permAlone(str) {
  return perms(str);
}

permAlone("abc");

Hi @k-kapp
Thanks for reporting this issue.
Here are some next steps that you should follow before we can help you with your query:

Check these troubleshooting steps first.
Please use the Chat Rooms or try looking through our forum for help with a specific challenge and any coding assistance.

IMPORTANT:
Please NOTE that this tracker is for reporting bugs and enhancements to freeCodeCamp's code base only.
Happy Coding!

Please revert back with the details as requested.


Update docker_remote_api_v1.21.md to complete the docs

Update docker_remote_api_v1.21.md to complete the docs. Tht old docs is short of name about containers apis.
#20536
Signed-off-by: tracylihui<EMAIL_ADDRESS>

@thaJeztah

LGTM, perhaps we can combine all the API changes in a single PR? I see https://github.com/docker/docker/pull/20542 as well, would be nice to have them all in a single PR, I think @longliqiang88

yes,I will test other Api Versions. And combine in a single PR

I found that the PR of @longliqiang88 has been merged. So I don't need to change   docker_remote_api_v1.20.md. So I make a new commit to change from docker_remote_api_v1.14.md to docker_remote_api_v1.19.md. So the old version and v1.21 has been changed too. If there's no problem, I hope it can be merged.Thanks. @thaJeztah @vdemeester

LGTM 🐺


Annotations fix in workflow client

Fixes https://github.com/temporalio/sdk-php/issues/98

Closed. It was created by accident on the wrong branch.


Create a Project Gallery component for the Third theme

As per provided designs, Create a Project Gallery component for the Third theme

Reference for the design: https://www.figma.com/file/0ISIz6XklEToDd4KXfIWRB/SCoRe-Lab-Theme-designs?node-id=3%3A3
Cc: @charithccmc, @dinithminura

Hello , I would like to work  on this issue


bug: In React, IonSearchbar can't be given focus with JS

Bug Report
Ionic version:

[x] 5.0.2
Current behavior:

The IonSearchbar component has a documented function for setting focus setFocus, but it doesn't seem to work. Calling it does not produce a change in the current focus.
Expected behavior:

Calling setFocus on the searchbar should focus the element and bring the cursor into it.
Steps to reproduce:

See below for the linked repo containing a reproduction of the problem. Basically, all I'm doing is adding a searchbar, getting a ref to it, and then calling setFocus on the ref once it's resolved. I have found that even if I inspect the element in the browser, set a variable to it in the console, and then call setFocus on that variable it does not work.
Related code:

I have a sample repo to show the problem here:
https://github.com/aub/ionic-searchbar-focus-problems
The only thing I changed in here after creating the app with  ionic start focus-problems --type=react --capacitor was to add the searchbar and its setup in the ExploreContainer. I have verified that the console logging is being produced and setFocus is being called on the searchbar.
insert short code snippets here

Other information:

Ionic info:

Ionic:

   Ionic CLI       : 5.4.13 (/usr/local/lib/node_modules/ionic)
   Ionic Framework : @ionic/react 5.0.2

Capacitor:

   Capacitor CLI   : 1.5.0
   @capacitor/core : 1.5.0

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   NodeJS : v13.8.0 (/usr/local/Cellar/node/13.8.0/bin/node)
   npm    : 6.13.7
   OS     : macOS Catalina

Thanks for the issue. Which device are you testing this on? I tested this on an iPhone running iOS 13 and setFocus worked fine.

Whoops, sorry I should have included that. This is on the desktop in Chrome.

Thanks for the follow up. I tested in Chrome as well and it works fine there. What version of Chrome do you have?

Version 81.0.4044.26 (Official Build) beta (64-bit)
So when you run the app I linked to the flashing cursor appears in the searchbar?

I tested this on Chrome 81 Beta, and it works fine there too. What platform are you testing on?

Man, that's baffling. My system info is:
   NodeJS : v13.8.0 (/usr/local/Cellar/node/13.8.0/bin/node)
   npm    : 6.13.7
   OS     : macOS Catalina

I am on Catalina as well. Does it work if you just call the focus method on a regular input? (without using an Ionic component)

Grrr, it's also working for me now. If you don't mind, give me a few minutes to figure out what happened here and then if I still can't reproduce it I'll close this issue. Sorry about that, thanks for your time.

Ok, it seems like this does work correctly for me unless I have the Chrome dev inspector open. I'm not really sure what to make of that, but it seems like other inputs on other sites cannot be given programmatic focus from the dev tools, so it seems like not a bug. Thanks again for looking at it and for your time!


update repo

Coverage remained the same at 100.0% when pulling da57f087a903d7a0ea155066206762d793541c8e on zaneck:master into bec4c48cdc847477b6755eb0fea7cb46009b5cf5 on chdemko:master.


[CAPI]correct required fields in post request

#1586  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @anna-statsig and the rest of your teammates on  Graphite

🚀 Deployed on https://6646822556a65119d308f8bb--cozy-fox-0defec.netlify.app


fix: Allow different model types with the same ID

Issue #, if available:
Description of changes:
This PR contains two changes

Use modelName in MutationSyncMetadata.id as the new key format "modelName|modelId"
Migration scripts that run before the sync engine starts to migrate the ids to the new key format

Check points: (check or cross out if not relevant)

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1490 (3e7eb32) into main (a1d1661) will increase coverage by 0.15%.
The diff coverage is 80.58%.

@@            Coverage Diff             @@
##             main    #1490      +/-   ##
==========================================
+ Coverage   58.50%   58.65%   +0.15%
==========================================
  Files         678      684       +6
  Lines       20729    20874     +145
==========================================
+ Hits        12127    12244     +117
- Misses       8602     8630      +28

Flag
Coverage Δ

API_plugin_unit_test
61.57% <ø> (-0.10%)
:arrow_down:

AWSPluginsCore
72.58% <35.71%> (-0.41%)
:arrow_down:

Amplify
45.94% <ø> (-0.07%)
:arrow_down:

Analytics_plugin_unit_test
71.76% <ø> (ø)

Auth_plugin_unit_test
78.96% <ø> (ø)

DataStore_plugin_unit_test
75.16% <84.61%> (+0.35%)
:arrow_up:

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...eCategoryPlugin/Storage/ModelStorageBehavior.swift
0.00% <ø> (ø)

...eCategoryPlugin/Storage/StorageEngineAdapter.swift
0.00% <ø> (ø)

...sCore/Sync/MutationSync/MutationSyncMetadata.swift
35.71% <35.71%> (ø)

.../AddModelNameToMutationSyncMetadataMigration.swift
75.40% <75.40%> (ø)

.../OutgoingMutationQueue/OutgoingMutationQueue.swift
76.95% <80.00%> (+0.33%)
:arrow_up:

...n/Storage/SQLite/StorageEngineAdapter+SQLite.swift
74.08% <82.60%> (+0.47%)
:arrow_up:

...meToMutationSyncMetadataMigration+Validation.swift
91.42% <91.42%> (ø)

...gin/AWSDataStorePlugin+DataStoreBaseBehavior.swift
63.01% <100.00%> (+0.25%)
:arrow_up:

...WSDataStoreCategoryPlugin/AWSDataStorePlugin.swift
67.92% <100.00%> (+0.30%)
:arrow_up:

...toreCategoryPlugin/Migration/ModelMigrations.swift
100.00% <100.00%> (ø)

... and 12 more

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 a1d1661...3e7eb32. Read the comment docs.


2415 mock type map

Thanks @danielkec . The branch for change is helidon-2415 and I had tried to fix this by modifying Mocked DS. I was using HashMap straight instead of I picked your changes manually from this one. We can close this.


Problem with Expiry Date

Hi.
We have problems with expiry date funct.
The problem appears when you use one input to month and year.
for example:
    <input #expiryInput="ngModel" [(ngModel)]="expiryFull"
                      class="form-control" name="year" placeholder="•• / ••" (ngModelChange)="testValueExpired($event)"
                      required data-stripe="exp_year"  id="cc-exp-date" type="tel" autocomplete="cc-exp" ccExp [maxLength]="7"/>

In this case we want to validate years with 2 digits only.
Problem:
When a user press the keys very fast the year part could have from 2 to 4 digits, so, for us is a problem.
i modded the file credit-card.js to validate only 2 digit , but for futher version may you can add some decorator for 2 or 4 digits.

duplicate of #30


refactor: Resolve name collision of route target attribute

resolves #14
I hope I didn't miss something :)
Not sure what to do with Active component. to sounds wrong in that context, leaving it as target is probably fine despite inconsistency, both have a different purpose. Also, span doesn't have a target attribute, so no html collision in this case.

I guess the examples, and the Active component.

Ugh, I'm sorry about that. As I stated in the first post, I'm not so sure about Active :/ to doesn't seem like it makes sense semantically, target sounds fine.

Another option is to rename that attribute for both to route, which solves the ambiguity issue, but makes it syntactically different from yew_router (dunno if that feature has any value for you though)

Ugh, I'm sorry about that. As I stated in the first post, I'm not so sure about Active :/ to doesn't seem like it makes sense semantically, target sounds fine.

Naming is hard … You're right. It doesn't. Keeping it target also feels wrong. A good compromise could be to name it route for the Active component only. "check if that route is active" sounds reasonable. A "target" would never be "active" anyway I guess.

True, that sounds weird. Oki, I'll rename it there as well


upgrading compatibility up to macOS 10.15

upgrading pyscard 1.9.6 to 1.9.9 correctly handles macOS versions older than 10.10 (including latest 10.15)

LGTM! :+1:
Merging, thanks @zaza81 for your contribution! :tada:


Enhancement fill user field for profile.

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.24 seconds
load time: 488 seconds
storage size:<PHONE_NUMBER>8 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230129153539_clickbench_pr_86484.html


Update gp.py

Resolves #900.

Codecov Report

Merging #915 (bdbafe5) into devel (ff82f12) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel     #915   +/-   ##
=======================================
  Coverage   54.55%   54.55%
=======================================
  Files         211      211
  Lines       21568    21568
  Branches     2894     2894
=======================================
  Hits        11767    11767
  Misses       9250     9250
  Partials      551      551


Fill in compounds from db

Summary Change Description
Use a database query to fill in any empty columns that could not be filled in from data from the peak annotations file.
Affected Issues/Pull Requests

Partially addresses #829
Merges into PR #1018
Next PR: #1028

Review Notes

See comments in-line.
Checklist

This pull request will be merged once the following requirements are met.  The
author and/or reviewers should uncheck any unmet requirements:

Review requirements

Minimum approvals: 1
No changes requested
All blocking issues resolved by reviewers
Specific reviewers: @add_username_here

Review period: 2 days

Associated issue/pull request requirements:

[x] All requirements in affected issues marked "resolved" are satisfied
[x] All required pull requests are merged (or none)

Basic requirements

[x] All linters pass
[x] All tests pass
[x] All conflicts resolved

Overhead requirements

[x] New/changed method tests implemented/updated (or no change)
[ ] Updated Unreleased section of changelog.md (or no change)
[x] Migrations created & committed (or no change)

Merged via #1076


Customize navigation transitions in theme

It's been implemented in the latest release: https://flet.dev/docs/controls/page#navigation-transitions


Add tests for git package

Problem
Missing tests for the package
A/C
At least some coverage

We can write tests as we go.


frontend MIME checking strict error

Hello, on the latest version I get a white page after following instructions of installations without docker. The console shows :
Refused to apply style from 'http://localhost:8080/styles.a10ccf2429c77a75d2fe.bundle.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
localhost/:1 Refused to execute script from 'http://localhost:8080/inline.318b50c57b4eba3d437b.bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
localhost/:1 Refused to execute script from 'http://localhost:8080/polyfills.a7e8614283b1ade81941.bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
localhost/:1 Refused to execute script from 'http://localhost:8080/main.93ec3bcc0ef152d14aa4.bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

Hey @LivioGama, thanks for helping out with fastlane.ci. Can you tell us a bit more of how you installed & set up fastlane.ci? That error is in your web browser, right? Is there anything in your server logs?

I installed rvm. I installed Ruby 2.3.3 though RVM.
git clone https://github.com/fastlane/ci
cd ci
npm install
npm run-script build
gem install bundler
bundle install
bundle exec rake prod

Interesting - I don't know enough about this part of fastlane.ci, does this happen when you use <IP_ADDRESS> instead? Does this happen on a different browser also?

Thanks for reporting this and sorry you're running into this problem, we'll get back to you later this week or next week 👍

Did you ever run ng build --deploy-url="/.dist" --dev -w? If not, can you give this a try?
If that also doesn't work, you can run fastlane.ci after setting an ENV variable
export FASTLANE_CI_ERB_CLIENT=1

@LivioGama Our npm run-script build is not correct right now since it's missing the  --deploy-url="/.dist" flag. This is most likely the issue. Let me whip up a PR. In the meantime doing what @KrauseFx suggested should get you going 🚀
ng build --deploy-url="/.dist" --prod

Thanks, it works ! Just a question, what are the login and password I'm asked to fill ? I didn't create any user and I get this :


findthemasks.com/whoweare.html should credit airbrake

Please thank airbrake for giving a sponsored account to catch Javascript errors.

Added to Partners spreadsheet just need a dev now :)

All sponsors are now on the live www.findthemasks.com/partners page!

It's not a big deal but I think we are still missing airbrake so keeping this open

Yes, please keep it --- sorry I am working on my final project for school. I'm presenting next Tuesday!
This is on my To do. I'll close it when I add it to the Partner's list and get a dev to update :)

Closing, looks like this was done


Gaussian Noise

Excuse me, I noticed you add different gaussian noise for 2D input in your Supplementary Material. I try to add noise for input but can not reproduce your result, could you please tell me how to add gaussian noise correctly. Thanks a lot!!!!!!!!!!!!!

We use 'np.random.normal' to add gaussian noise.

Yeah,  I know it. What I mean is where do i add the code？ Can I add it in main.py of line 39?

Yes, it is right.
##----------Gaussian----------##
gaussian_scale = 20 / 500
input_2D = input_2D.cpu().numpy()
nosie = np.random.normal(0, gaussian_scale, input_2D.shape)
input_2D = input_2D + nosie
input_2D = torch.from_numpy(input_2D.astype('float32'))
input_2D = input_2D.cuda()
##----------------------------##
But need to ‘/500’ due to the input_2D is normalized in https://github.com/Vegetebird/MHFormer/blob/fcf238631016f906477ec9c1d17582097ecf9803/common/camera.py#L7


install via pip fails

Trying to install pinball on a brand new ubuntu 14.04 ec2 instance and I am receiving the following error after running pip install pinball:
Command /usr/bin/python -c "import setuptools, tokenize;__file__='/tmp/pip_build_root/guppy/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-_Rny0e-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip_build_root/guppy
Storing debug log for failure in /root/.pip/pip.log```

See gist here: https://gist.github.com/arukaen/d0847fbd3a6b07230984#file-pinball-issue-github

apt-get install python-dev  fixed said issue.


Refactor/aws integration

Added AWS Services
Added Cognito Auth Middleware
Added Admin Seed to Cognito
Changed upload middleware from Google Bucket to AWS S3
Added Amazon SES

API Information

Endpoint
Method
Description

/api/upload-test
POST
Uploads the image to Amazon S3 and returns presigned URL

/api/send-test-email
POST
Sends email with Subject and Body to the provided email from Amazon SES

Please merge https://github.com/wesionaryTEAM/go_clean_architecture/pull/114 before merging this PR


@storybook/react 4.0.0-alpha.18 Throwing Error

If you are reporting a bug or requesting support, start here:
Bug or support request summary
The latest version of storybook (4.0.0-alpha.18) is breaking the build. So as a temporary solution we have had to roll back to 4.0.0-alpha16.
Please provide issue details here - What did you expect to happen? What happened instead?
Expected:
Executed the following task and expected the storybook build to complete successfully.
cross-env NODE_ENV=production build-storybook -c source/App/Lib/.storybook -o ClientName/Storybook

Actual:
The storybook is throwing the following exception:
[20:44:39]                                                   76% advanced chunk optimization RemoveEmptyChunksPlugin
[20:44:39]              ...acc,
[20:44:39]              ^^^
[20:44:39]SyntaxError: Unexpected token ...
[20:44:39]    at Object.exports.runInThisContext (vm.js:76:16)
[20:44:39]    at Module._compile (module.js:542:28)
[20:44:39]    at Object.Module._extensions..js (module.js:579:10)
[20:44:39]    at Module.load (module.js:487:32)
[20:44:39]    at tryModuleLoad (module.js:446:12)
[20:44:39]    at Function.Module._load (module.js:438:3)
[20:44:39]    at Module.require (module.js:497:17)
[20:44:39]    at require (internal/module.js:20:19)
[20:44:39]    at Object.<anonymous> (C:\BuildAgent\work\89174915197d6e98\node_modules\@storybook\core\dist\server\config\webpack.config.prod.js:16:57)
[20:44:39]    at Module._compile (module.js:570:32)

Please provide necessary steps for reproduction of this issue. Describe the exact steps a maintainer has to take to make the problem occur. If the problem is non-trivial to reproduce, please link a repository or provide some code snippets.
(A screencast can be useful for visual bugs, but it is not a substitute for a textual description.)
Please specify which version of Storybook and optionally any affected addons that you're running
    "babel-core": "6.26.3",
    "babel-loader": "^7.1.5",
    "@storybook/addon-actions": "3.4.10",
    "@storybook/addon-info": "3.4.10",
    "@storybook/addon-knobs": "3.4.10",
    "@storybook/addon-options": "3.4.10",
    "@storybook/cli": "4.0.0-alpha.18",
    "@storybook/react": "4.0.0-alpha.18"

Affected platforms
Node v10.8.0
Screenshots / Screencast / Code Snippets (Optional)
//webpack config
module.exports = {
    module: {
        rules: [
            {
                test: /\.(js|jsx)$/,
                exclude: [/node_modules/],
                loader: 'babel-loader',
                include: [path.resolve(__dirname, '../../../App')]
            },
            {
                test: /\.scss$/,
                loaders: ['style-loader', 'css-loader', 'sass-loader'],
                include: path.resolve(__dirname, '../../../assets/sass')
            },
            {
                test: /\.css$/,
                loaders: ['style-loader', 'css-loader'],
                include: [path.resolve(__dirname, '../../../App')]
            },
            {
                test: /\.(png|jpg|gif|woff|svg|woff2)$/,
                use: [
                    {
                        loader: 'url-loader',
                        options: {
                            limit: 8192,
                            name: '[name]-[hash].[ext]'
                        }
                    }
                ]
            }
        ]
    },
    plugins: [
        new webpack.DefinePlugin({
            ENVIRONMENT: JSON.stringify(environment),
            VERSION: JSON.stringify(version)
        })
    ]
};

End bug report support request - delete the rest below

Do you have any babel config?

@Hypnosphi updated description with babel config.


[WIP] Reject egress rules that conflict on some domain

What this PR does / why we need it:
Prevent conflicting egress rules from causing envoy to crash.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1166
Special notes for your reviewer:
Release note:

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
984432df36be8dde06769ad0e434249551297f37
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

make fmt should fix most of issues. run bin/check.sh too before next update.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
88cb024f0f39100ab4a072e726bcae3ec7285fa0
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Closing temporarily

?

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f2d8f470a6ff1a0d9ac049d38560c198dfa93181
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

no problem; bin/init.sh and/or install-prereqs.sh should do that for you
try rebasing your fork as it seems prow can't merge/test it

/retest

@ldemailly OK, will rebase.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f2d8f470a6ff1a0d9ac049d38560c198dfa93181
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
35ea633c7bce4fd919a6ff9c19515217e12e0190
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ldemailly fixed presubmit.sh errors.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
51a1485c2b88138d8bd2e54663bab26cb113512b
link
/test pilot-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram thank you for your review, I have applied your comments.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
53285eb5a4bc910bbf5fdcb9d080048471746e04
link
/test pilot-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram Good catch, I have fixed the test - making ports into consideration when calculating conflicting rules.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
57ebfaaa6499dadbbedc92f7b9605675da19d52b
link
/test pilot-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

merging this - as this is the only PR with all green in pilot!


fix: more proper scanning of the conda-meta folder for json entries

The path::ends_with function only compares full segments. We need to compare the extension if we want to filter only JSON files.
The condition was anyways wrong (we would have skipped over files that end with json but those are the ones we are interested in).
cc @ruben-arts I believe this would fix the issue with putting the prefix file into the conda-meta folder.
cc @baszalmstra

wow! How has this worked previously?!

It never matched because ends_with on a path is not the same as string ends_with - only matches full segments.

Yeah but that would mean we would always be reinstalling packages and never uninstalling them. That seems like something we would e caught


Simulation method used for the signal datasets?

Dear Charlotte,
Thanks for your intensive work on the evaluation of DE methods. When reading the paper https://www.nature.com/articles/nmeth.4612, we found it unclear on how did you simulate the datasets with signals, which contain 10% DE genes. Could you describe it in details?

I used the powsim package for the simulation, starting from three of the experimental data sets. The exact code I used is here: https://github.com/csoneson/conquer_comparison/blob/master/scripts/simulate_data.R

Do you have any description of that method in the paper?

The approach is described in our Methods section:

three of the data sets (GSE45719, GSE74596 and GSE60749-GPL13112) are used as the basis for simulation of data using a slightly modified version of the powsim R package34. Individual reports generated by countsimQC35 and verifying the similarity between the simulated and real data sets across a range of aspects are provided as Supplementary Data 1. As for the original, experimental data sets, we subsample data set instances with varying number of cells per group, and further generate null data sets by random sampling from one of the simulated groups. In each simulated data set, 10% of the genes are selected to be differentially expressed between the two groups, with fold changes sampled from a Gamma distribution with shape 4 and rate 2. The direction of the DE is randomly determined for each gene, with equal probability of up- and downregulation. Mean and dispersion parameters used as basis for the simulations are estimated from the respective real data sets using edgeR7. For each of the three data sets, the rounded length-scaled TPMs for all genes with at least two nonzero counts are used as input to the simulator, and a data set with the same number of genes is generated.

The code shows exactly which functions we ran, and with which parameters.
The powsim paper describes their simulation model in more detail: https://www.biorxiv.org/content/10.1101/117150v1.full


capacity field

Fixes #88

Coverage decreased (-1.5%) to 88.736% when pulling 104fb6918d1e6fcf9ecab7afc517b3fece965456 on feature/capacity-field into ca9a59ef2ad95442436b6a0ed9f061e6a47e376a on master.

@cristaloleg LGTM

@janisz it's a simple field exposing, 0 new logic.
Can we left tests for this change as a separate issue atm? :)


chore: Connector Message Statisics Drawer

Awesome, thanks for pointing those out @Kells512!  Think what I'll do is have a look at how this PR looks locally first and figure out the least bit of markup we can pull out to wrap the stories in the other PR.  Ideally without creating extra maintenance in the future which is a concern when mocking things.
Another option we could consider is to just ensure that the general layout and properties of the message statistics components are what we want and iterate on them in the other repo, once they're ready we merge them, get a release of app-services-ui-components and then update these stories to use them.  So if turns out there's a lot of stuff to copy, we'll go this route, I'll look now :smile:

@gashcrumb Thanks again for that Stan


Create dataset loader for Myanmar-Rakhine Parallel Data

Dataloader name: myanmar_rakhine_parallel/myanmar_rakhine_parallel.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?myanmar_rakhine_parallel

Dataset
myanmar_rakhine_parallel

Description
The data contains 18,373 Myanmar sentences of the ASEAN-MT Parallel Corpus, which is a parallel corpus in the travel domain. It contains six main categories: people (greeting, introduction, and communication), survival (transportation, accommodation, and finance), food (food, beverages, and restaurants), fun (recreation, traveling, shopping, and nightlife), resource (number, time, and accuracy), special needs (emergency and health). Manual translation into the Rakhine language was done by native Rakhine students from two Myanmar universities, and the translated corpus was checked by the editor of a Rakhine newspaper. Word segmentation for Rakhine was done manually, and there are exactly 123,018 words in total.

Subsets
-

Languages
mya, rki

Tasks
Machine Translation

License
GNU General Public License v3.0 (gpl-3.0)

Homepage
https://github.com/ye-kyaw-thu/myPar/tree/master/my-rk

HF URL
-

Paper URL
https://aclanthology.org/W19-1408/

#self-assign

Hi @muhsatrio, may we know the update on this dataloader issue? It's been 2 weeks since the last poke from the SEACrowd stale-checker, and we might consider unassigning if there's no progress update in the next 24 hours.

#self-assign


[release-1.12] bump istio v1.19.6

Hm there are conflicts on prow builds?

It's a weird prow bug - the branch was opened against main by accident so you see the main jobs - latest_net-istio_main
Changing the base target to release-1.11 made the release branch jobs show up latest_net-istio_release-1.12 but it doesn't remove the main jobs
Since everything passed tide is just looking for an lgtm - Not mergeable. Needs lgtm label.

/retest

/override "build-tests_net-istio_main"

/override integration-tests_net-istio_main
/override latest-mesh_net-istio_main
/override latest_net-istio_main
/override unit-tests_net-istio_main


Training code

Hello, can you provide the training code of DFM-Net, thank you！

Training code is now updated.


Add new scam message and link

Someone sent a message with a link that was malicious my iPad even said it was
There was also a message sent in my friends discord server

Now that I'm at a computer I can see this addition is already there: https://github.com/Erisa/Cliptok/blob/main/Lists/scams.txt#L436
The domain will be handled by me updating the secret phishing.txt to the latest version. So this PR isn't needed.
Thank you for your contribution nonetheless!


[layout] implement bubbles api for android

https://developer.android.com/guide/topics/ui/bubbles
It would be cool to implement the bubbles api or some other type of overlay so streamers can continue to read chat while using other apps.

Let's not do this one. It's too complex.


[Bug?]: Static Asset Imports Do Not Work With SSR

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Hi Ryan, Nikhil, and everyone else who's been putting in the amazing work into solid start (and the web at large haha)! 👋
When importing static assets, for example, import Img from "~/test.png";, the default export of this appears to be incorrect when server rendering this string, resulting in a 404 for the browser.
Example server output:

Client side rendering (with { start: { ssr: false } }) appears to get this src attribute correct with a /_build/@fs prefixed url that does not 404. I didn't try client side navigation within an SSRed app, but my suspicion is that it works since the client bundles are probably working the same in that case.
Also note that using hand-crafted, "public" urls from the vite /public directory appears to be work in both modes, unsurprisingly.
Expected behavior 🤔
Both server and client bundles should have same default export strings.
Steps to reproduce 🕹
Minimal reproduction (this is my app.jsx file in a "bare" start setup) and { start: { ssr: true } } in vite.config.js
// @refresh reload
import img from "~/test.png";

export default function App() {
  return ;
}

Context 🔦
No response
Your environment 🌎
"@solidjs/start": "^0.4.2",
"solid-js": "^1.8.7",
"vinxi": "0.0.54"

Experiencing the same thing using latest SolidStart!

Thanks for the report! Will take a look. Probably a bug in vinxi

Should be fixed in<EMAIL_ADDRESS>please try that and reopen this issue if it still doesn't work.


Support for github registry image

Any plans to support other image services like dockerhub and github registry? Or is it already supported?

Hi @asimkt, this seems to be more like a product ask, feel free to visit the roadmap (https://github.com/aws/apprunner-roadmap). You can either upvote an existing item or add new issue for your product ask. Service team will prioritize tickets based on the number of upvotes. Thanks and appreciate your support for App Runner.


add directives (wip)

To be honest, I don't understand this move towards a stripped down value file you are using here as a template. The values file we have in the renku charts directory has (almost) all of the values documented which makes it much easier to read and process. Here all of the doc strings are gone.

I'm not sure this is relevant anymore - closing