[dr-autosync] QPS drop 0 when switch from async to sync_recover after 2 hours

Development Task
The synchronization speed of the Raft log should be adjustable rather than monopolizing all resources; otherwise, it will impact the QPS and Latency.
Test Steps:

working in async for more than 2 hours;
Then clean the chaos and cluster will switch to sync_recover;
QPS drop 0;

Version: 6.5.4

/assign @Connor1996


⚠ Avatar API Endpoint has degraded performance

In dbf8bc9, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1066 ms

Resolved: Avatar API Endpoint performance has improved in b1755ff.


improve plot qsphere examples

Summary

Unwrap comments and code (qiskit code line length limit is 120, no need to wrap)
Remove spaces around "=" in function arguments

Details and comments
This is a follow up of https://github.com/Qiskit/qiskit-terra/pull/8355. The PR was merged before I push the changes.

I need to import numpy before qiskit in this PR. Please do not merge yet.

This PR is superseded by #8450. Closing.


[DO NOT MERGE] Update index parameter on tabs

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
What
Change the index parameter on the tabs component to align with recent changes to the index parameter and how we're processing it within GA4.
Why
Part of the GA4 migration.
Visual changes
None.
Trello card: https://trello.com/c/8tNN5gGX/426-change-the-index-parameter

Have had an analyst test this and confirmed it is correct. Will deploy when ready.


app.classeur.io down. data lost?

Seems like classeur.io has been taken down.
Is there any way i can retrieve the files i had stored within this app 😢 ?

They moved to Stackedit io
Obter o Outlook para Androidhttps://aka.ms/ghei36

From: bijzz<EMAIL_ADDRESS>Sent: Sunday, June 10, 2018 3:47:55 AM
To: classeur/classeur
Cc: Subscribed
Subject: [classeur/classeur] app.classeur.io down. data lost? (#244)
Seems like classeur.iohttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp.classeur.io&data=02|01||6f8a107478aa49570d5208d5ce9e1ace|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636642100799720473&sdata=AuqxznrG9vSzCeh44ZRbJHDxNzH9bL9U%2FnHKkzf21IQ%3D&reserved=0 has been taken down.
Is there any way i can retrieve the files i had stored within this app 😢 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclasseur%2Fclasseur%2Fissues%2F244&data=02|01||6f8a107478aa49570d5208d5ce9e1ace|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636642100799720473&sdata=Ql%2Bhf%2BaOrfsub2So4tU1w1tl%2Fk6ZEGA8zfFfddjlQbU%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFrkqU5Bna8pnYVY9kJjjpkx_p2TqmCgks5t7MEbgaJpZM4Uhmvz&data=02|01||6f8a107478aa49570d5208d5ce9e1ace|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636642100799720473&sdata=Nl%2BCB89bLSXu9bqFAjRYcDBJL5cLdDXL2l2%2BCB8hVWc%3D&reserved=0.

Ok, but then the notes i created within classeur.io are now lost to me?

Maybe this will help.
Open up your browser devtools.  Go to application or storage tab.  Then look in:

local storage
session storage
indexed db
etc

Perhaps you can find where classeur stashed your local offline data.

Thanks for the help. I could retrieve some old versions on different machines. Unfortnuately, the latest usage was primarly for a firefox at work which seems to have cleared the local storage with each restart 😞


how to train the SphereFormer in DDP mode?

Current implementation is already based on DDP.

Is it enought for the DDP mode to  adding "CUDA_VISIBLE_DEVICES=0,1,2,3***" before "python train.py --config config/semantic_kitti/semantic_kitti_unet32_spherical_transformer.yaml". Because the DDP mode usually needs to set the lanuch mode, such as python -m torch****. I have just come across this repo and have not run it.

Some questions about the performance gap between the validation set and the test set on the semanticKITTI benchmark.
I have read your paper, which is an excellent work.The performance of this SphereFormer on the SemanticKITTI validation set in this repo is 67.8， meanwhile the performance on the test set is 74.8. However, for my model, the performances on the val set and the test set are 71.4 and 72.3, respectively. May I ask you how to solve this problem? Thank you

Firstly, you can also run with ddp mode without ddp launcher, like in the released train.py file.
Secondly, to reach a better performance on the test benchmark, many works use some tricks like gt sampling and model ensembling. You can try them. The reported validation results are without these tricks.

I am a Phd student in Zhejiang University. could I have your contact information? My email address is<EMAIL_ADDRESS>

I am a Phd student in Zhejiang University. could I have your contact information? My email address is<EMAIL_ADDRESS>

Firstly, you can also run with ddp mode without ddp launcher, like in the released train.py file. Secondly, to reach a better performance on the test benchmark, many works use some tricks like gt sampling and model ensembling. You can try them. The reported validation results are without these tricks.
Model ensembling means the ensembling among different epochs or the ensembling among the semantic models such as SPVCNN, MinkUnet, Cylinder? Gt sampling means the data augmentation method in the training stage in the SECOND paper?

Model ensembling means ensembling the same models with different hyperparameters (e.g., batch size, weight decay, learning rate, etc.).
For GT sampling, please refer to Sec. 3.4 of the paper of RPVNet.

Model ensembling means ensembling the same models with different hyperparameters (e.g., batch size, weight decay, learning rate, etc.). For GT sampling, please refer to Sec. 3.4 of the paper of RPVNet.

Thank you!


fix: update jsonrpsee to track active requests correctly

PR Type
Bug fix, Enhancement

Description

Updated jsonrpsee dependency to version 0.24.6, which includes fixes for tracking active requests correctly.
Removed a TODO comment in the RPC middleware related to the calculation of active connections, as the issue has been resolved in the new jsonrpsee version.
These changes improve the accuracy of request tracking and remove outdated comments, enhancing the overall reliability of the RPC system.

Changes walkthrough 📝
Relevant filesEnhancement

rpc_middleware.rsRemove TODO comment for active connections

src/eth/rpc/rpc_middleware.rs

Removed TODO comment related to active connections calculation

+1/-1

Dependencies

Cargo.tomlUpdate jsonrpsee dependency version

Cargo.toml

Updated jsonrpsee dependency version from 0.24.5 to 0.24.6

+1/-1

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Final benchmark:
RPS Stats: Max: 1176.00, Min: 518.00, Avg: 835.55, StdDev: 71.34
TPS Stats: Max: 1126.00, Min: 518.00, Avg: 835.22, StdDev: 69.78
Plot: View Plot


Date highlighter

Hello There.
I want to highlight dates between today and date selected by user on  SingleDatePicker
I donot konw how to use isDayHighlighted: PropTypes.func,
<SingleDatePicker
                            id="date_input1"
                            placeholder="mm/dd/yyyy"
                            date={this.state.startDate}
                            focused={this.state.focused}
                            onDateChange={this.onDateChange}
                            onFocusChange={({ focused }) => this.setState({ focused })}
                          />

There is example here: https://github.com/airbnb/react-dates/blob/8eca5d0aeb00e22e92a1232de923408572dd0e96/stories/SingleDatePicker_day.js#L48
isDayHighlighted should be a function. The parameter passed into the function is the day that needs to be checked (it should be a moment object), and the return value should be true or false.

I am confused between .
import { SingleDatePicker } from 'react-dates'
and import { SingleDatePickerWrapper } from 'react-dates'
components. They are same?

SingleDatePickerWrapper is a wrapper around SingleDatePicker that seems to be used for the examples. You can see the code here: https://github.com/airbnb/react-dates/blob/master/examples/SingleDatePickerWrapper.jsx
It seems to just proiide a bunch of default properties to SingleDatePicker

@jseminck Thanks for Your Suggestion.

@jseminck hit it on the head. The wrapper is there to show how to use the exported components. If you copy it over into your own project, it is a good starting point.
All of the modifier props (isOutsideRange, isDayBlocked, isDayHighlighted) take in a moment object and return true or false based on weather or not that day should have that class.

@lausellduane It's generally a better idea to open a new issue than comment an a closed issue! :)
That being said, you can accomplish what you want by storing your highlighted days in a Set or other data structure and then checking for presence in that object rather than checking for equality, e.g. isDayHighlighted={day => highlightedDays.has(day.format('YYYY-MM-DD'))}. It's probably a good idea to store strings rather than moment objects since two moment objects for the same day may be different instances.

Thanks it worked!
Yea will do next time. I commented here because I though it was gonna be easier for you to find.
Sorry I find the documentation very vague in the matter but do you know or could you point me in the right direction of how i can style the css for that highlight? I mean changing the background color or even inserting emojis like in one of the storybook examples?


[Trans] Auto trans on devs content should not be a thing

Edit: You committed something about that in menu.html.twig @kevinpapst
added method to configure translation domain for menu items (https://github.com/kevinpapst/TablerBundle/pull/150)
But still the case for the navbar
https://github.com/kevinpapst/TablerBundle/blob/28287dc810186ef3188811af071cb67832e7c7f0/templates/includes/navbar_user.html.twig#L28

I'm currently experiencing some translation errors when using the menu and navbar.
What I got
From a subscriber, I implement some items to the menu.
These items have labels that are already translated inside the subscriber.
$changePassword = new MenuItemModel(
    'change_password',
    $this->translator->trans('action.edit_profile'), // <----- HERE
    'user_edit',
    ['user_uuid' => $user->getUuid()]
);
$event->addLink($changePassword);

What TablerBundle does
When TablerBundle print the twig result of the menu item, it tries to trans a content that is already translated.
Like {{ 'Modifier mon profil'|trans }}.
What is the problem?
Because of this, Symfony tells me that I have missing/wrong translations.

What is the solution?

Add the trans domain to any trans function/filter that the bundle uses
❌ I don't think this is a good idea:

Translations like that are not auto discovered by bin/console translation:extract (huge nono for me)
I found it easier to expect as a dev, to do a "raw" print by the bundle if my label is a message ID.

DO NOT try to translate content that devs define.
Only word/phrase that we define in the bundle.
✔ Rude, but I'll take it!

I find it disturbing to use the translator in the backend, even though this is a frontend centric piece of the backend.
For myself I don't see an issue when Symfony warns about missing translations.
That happens all the time with form choices and such.
But I don't know, if there are any official best practice for such cases in bundles.
What about adding the same translation domain logic to the user navbar?

For myself I don't see an issue when Symfony warns about missing translations.

This is not a missing translation error.
Those are error from a translation of a translated label.

That happens all the time with form choices and such.

How?
Do you not translate your labels and/or choices?
$builder
    ->add('nom', TextType::class, [
        'label' => $this->getTranslator()->trans('label.name'),
    ])
    ->add('statut', EnumType::class, [
        'label'        => $this->getTranslator()->trans('label.status'),
        'class'        => DocumentStatutEnum::class,
        'choice_label' => fn(DocumentStatutEnum $statut) => $statut->trans($this->getTranslator()),
    ])
;

enum DocumentStatutEnum: string implements TranslatableInterface
{
    case Nouveau   = 'nouveau';
    case Brouillon = 'brouillon';
    case EnCours   = 'en_cours';
    case Valide    = 'valide';
    case Refuse    = 'refuse';

    public function trans(TranslatorInterface $translator, string $locale = null): string
    {
        return match ($this) {
            self::Nouveau   => $translator->trans('label.new', locale: $locale),
            self::Brouillon => $translator->trans('label.draft', locale: $locale),
            self::EnCours   => $translator->trans('label.in_progress', locale: $locale),
            self::Valide    => $translator->trans('label.valid', locale: $locale),
            self::Refuse    => $translator->trans('label.refused', locale: $locale),
        };
    }
}

But I don't know, if there are any official best practice for such cases in bundles.

There's no best practice about that.
https://symfony.com/doc/current/best_practices.html#internationalization
But I know it is not a good practice to try to translate dynamically a variable, even in twig than PHP back-end.
And this is what we are doing in the menu template.

❌
✔

{# this translation uses a Twig variable  #}
{# so it won't be detected #}
{% set message = 'This is wrong' %}
{{ message|trans }}

{# Great use #}

{% set message = 'This is great'|trans %}
{{ message }}

What about adding the same translation domain logic to the user navbar?

As I said before, it's a big nono for me.

A menu item like that will not be found and extracted by the symfony translation command:
$changePassword = new MenuItemModel(
    'change_password',
    'action.edit_profile', // <----- That will not be detected
    'user_edit',
    ['user_uuid' => $user->getUuid()]
);

php bin/console translation:extract --force fr will not create an input for action.edit_profile

There is a lot of data that cannot be translated, e.g. Cities, Numbers ... but that is not the point, right?
I see what you are saying. It works very well for me since years, but that doesn't mean it is the correct way.
Just changing it will cause massive BC breaks (at least in my projects), so please propose a way forward that is BC safe. My project uses plugins from third party developers and I am not able to simply rip that feature out.
It needs time and a sunsetting phase with deprecation notices.

There is a lot of data that cannot be translated, e.g. Cities, Numbers ... but that is not the point, right?

TRUE! Some data can be translated and some can't.
So why do we force all data to be translated? That is indeed the point.

Just changing it will cause massive BC breaks

Also true, unfortunately 😞
I don't even know how to handle the "deprecated" state to warn other devs.
Because it is part of the variable content, not a "use way"/import/function/template.
This is also why it is not a correct way, we have no control over what the devs give us NOR how they use it.

You know the AdminLTE Bundle, right?! It has the same logic and it was used and installed (and still is) a couple of times every day: https://packagist.org/packages/kevinpapst/adminlte-bundle/stats
Nobody every complained about the logic. I just mention that, because ...

This is also why it is not a correct way

... I don't like these "there is only one correct way to do it and it's mine" expressions 😁
I am a fan of having all translation calls in the frontend, but then I never used that translation command as well 🤷 so that's probably why I never really thought about it twice.
But I do accept your arguments and that's why we should concentrate on finding a way forward:
What about add a new flag (isTranslated = false) to the MenuItem class and check that in the template when displaying the label?
If isTranslated == true, simply show the label.
But if isTranslated == false then trigger a deprecation and append the |trans filter.
That could work? At some point in the future we need to remove that extra flag isTranslated again, but in that case it does not work without that BC code.

... I don't like these "there is only one correct way to do it and it's mine" expressions 😁

I am not here to impose my wishes / my needs.
Otherwise this will be PR not an issue 😉
In my company, we have some tests to make sure there's no missing translation.
php bin/console debug:translation --only-missing $LOCALE --domain=$DOMAIN
If this command returns an error code, we will not be able to deploy.
ATE, we strictly do not use variable with trans function to be able to run that command.
As Symfony doc recommend it: https://symfony.com/doc/current/translation.html#how-to-find-missing-or-unused-translation-messages

The extractors can't find messages translated outside templates (like form labels or controllers) unless using Translations or calling the trans() method on a translator (since Symfony 5.3). Dynamic translations using variables or expressions in templates are not detected either

What about add a new flag (isTranslated = false)

Sounds good to me 👍

Sounds like a good approach! I'll play with that as well and see how I like it.
And don't hesitate to change the Menu Interface if necessary (like I recently did). This is also a BC break, but a "minor" one that is identifiable and fixable in 5 minutes. And I do not expect that many users implement their own MenuItemModel.

i'am also working with a UserDetailsSubscriber and for example
$event->addLink(new MenuItemModel('profile', 'Change password', 'app_change_password'));
Translation works if i manuall ad it to messages.de.xlf but if i wan't ti extract it with
php bin/console translation:extract --force --clean de
it isn't recognised and added to the messages.de.xlf file.
Is there any workaround for this?
also spotted that there
https://github.com/kevinpapst/TablerBundle/blob/main/templates/includes/navbar_user.html.twig#L26
https://github.com/kevinpapst/TablerBundle/blob/main/templates/includes/navbar_user.html.twig#L28
the optional translation domain is missing

@akkushopJK Pass a translated param to the MenuItemModel label (from the TranslatorInterface).
From this:
$changePassword = new MenuItemModel(
    'change_password',
    'action.edit_profile', // <----- That will not be detected
    'user_edit',
    ['user_uuid' => $user->getUuid()]
);

To this:
$changePassword = new MenuItemModel(
    'change_password',
    $this->translator->trans('action.edit_profile'), // <----- HERE
    'user_edit',
    ['user_uuid' => $user->getUuid()]
);

You will get a warning from Symfony that you are translating something that has already been translated.
But better that than lost data 👍


Adding new row to table

I've implemented md-data-table to my application sucessfully, But One issue i'm facing is adding new row to the table. I've list of candidates in the $scope.candidates
$scope.candidates = [
      {
        name: 'John Doe',
        experience: 3,
        current_ctc: 8,
        expected_ctc: 12,
        location: 'Bangalore'
      },
      {
        name: 'Joey Doe',
        experience: 1.5,
        current_ctc: 2.5,
        expected_ctc: 6,
        location: 'Bangalore'
      },
      {
        name: 'Frank Doe',
        experience: 2,
        current_ctc: 4,
        expected_ctc: 10,
        location: 'Guragon'
      }
    ];

Added md-progress="promise".
I've a form which lets you add new candidates which pushes an object into the candidates array. It's not async adding it to the table.
$scope.addCandidate = function(obj) {
  var deferred = $q.defer();
  $scope.promise = deferred.promise;
  $scope.candidates.push(obj);
  deferred.resolve($scope.iScoreCandidates);
};

Adding candidate method
$scope.instantScoreAdd = function(candidateObj) {
  $scope.addCandidate(candidateObj);
};

Thank you

I'm guessing you're using ng-repeat to loop over $scope.candidates but I don't see where you are adding the new candidate to the $scope.candidates array. I see $scope.iScoreCandidates.push(obj) but that is not the same array.

That's just editing mistake. That's is $scope.candidates. So what should i do rather than ng-repeat?

@daniel-nagy Is there any solution for this?

All you have to do is push the new item onto the array. Here is a Pen, click the "Add Banana Split" button and it will add it to the table.


 A problem with this is that if you are using a base class with overridable properties, this property needs to be virtual and in so doing, becomes lazy.
Now, there are 2 things I want to discuss here:

We keep lazy properties but maybe make them more explicit, maybe by using a new attribute such as
[DittoLazy]
public virtual MyPRop { get; set; }

This way, it's clear that you intend this property to be lazy, rather than just assuming all virtual properties are lazy.

The more controversial part of the question is, do we need lazy properties at all?

This feature was introduced early on in ditto's life, when it's place in the world was still being discovered. Now though, we know that we want ditto to be a view models builder, and not just a general mapper. Given that the idea behind a view model is to only make available to the view the properties that are needed by the view, the question is why should lazy properties be needed at all? Because, if we have declared a property on our view model, then it should always be needed and thus there is no need to be lazy.

This to some degree relates to pr #188

The more controversial part of the question is, do we need lazy properties at all?

We need them. I use them constantly and would recommend most people do. Not everyone uses Ditto with view models. I don't and I'd much prefer not to. I have a well established process which works perfectly and allows me to very rapidly create performant websites.
I really don't like the idea of the [DittoLazy] attribute at all. The virtual keyword is clear enough and is used by every proxy generator out there (Castle, Entity Framework) for interception. Adding an attribute simply adds overhead.
Devs shouldn't be using virtual properties in ViewModels anyway since Viewodels shouldn't be inheriting from each other. It's pollutant and screams of poor design. If any inheritance is to take place it should be from a single base class which shouldn't require overwriting if designed appropriately.

Hmm, can't help but feel that sounds a little double standards to say we should support lazy when arguably you shouldn't have properties on your view model you don't need, but then to say you shouldn't be using virtual, overridable properties on your view model. Surely we should be either flexible, or opinionated, but to mix the two sounds a little too contradictory.
An example I had that needed virtual overridable properties was using the polymorphism stuff with nested content. In my example, we created a list of links. We have multiple doc types, one for internal links, one for media and one for external links. In our view model, each view model consists of the same properties Name, Url and Target. To stay DRY then, I created a base Link class with these properties, and extended classes which override the Url property, attributing them with the required processors need for mapping that spacific versions url value.
This to me sounds like a valid use, but this usage forces the Url property to be lazy. This might not cause any issues, but it could equally cause confusion if a problem does arrive and suddenly you are in IProxy land wondering what is going on.

Och I'm not saying that though since I don't use my models a view models. We just use it different methods.
In retrospect adding the attribute will not cost us much perf wise and allow us to use virtual properties, I'm a go for it.

Non of this is a dig BYW, just trying to have the conversation, and really value your side of the argument. I really like that people use Ditto differently, we just need to make sure when people do, they don't get unexpected behavior, so it's just about how to make it work for everyone.

Of course. It's the incredible flexibility of it that I love most. Adding the attributes will only boost that. 😄

Having agreed we will use a DittoLazy attribute, I've started a PR for this, so we can move the discussion over there #191


Undo uri changes

This PR is for https://github.com/microsoft/vscode/issues/76506 and https://github.com/microsoft/vscode/issues/76606

@jrieken will this make it into https://github.com/microsoft/vscode-uri too?

@jrieken will this make it into https://github.com/microsoft/vscode-uri too?

Yes


DOCS update typo

According to packagist, 3.7.4 is already released! https://packagist.org/packages/silverstripe/framework#3.7.4

This also isn't on the 4 branch. What's the best way to get it there? Copy this file in a separate PR?

Yeah separate PR. We don’t merge up between existing stable major release branches (eg 3-4)


Make waving less obtrusive

Thanks for writing code that is easy to understand such that this was a trivial change :D


What is the source of this data?

Thank you for your hard work. If you don't mind can you please tell what is the source of this data. Thanks again

No problem! The db is built by merging data from multiple sources .

BSE StarMF Master data  - scheme details with RTA code
AMFI NAV - AMFI code
Quandl AMFI API Metadata - AMFI code

No problem! The db is built by merging data from multiple sources .

BSE StarMF Master data  - scheme details with RTA code
AMFI NAV - AMFI code
Quandl AMFI API Metadata - AMFI code


Extra unit tests

This change is

Current coverage is 76% (diff: 100%)

Merging #1634 into master will increase coverage by <1%

@@             master      #1634   diff @@
==========================================
  Files           272        272
  Lines         16670      16670
  Methods        2649       2649
  Messages          0          0
  Branches       1839       1839
==========================================
+ Hits          12713      12732    +19
+ Misses         3522       3515     -7
+ Partials        435        423    -12

Powered by Codecov. Last update b8362f5...421b102

Reviewed 2 of 2 files at r1, 13 of 13 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Emojification of culture guide

I've been feeling like the culture guide is a lot of text and hard to scan. @seanknox's new day-in-a-life page inspired me to add emojis to the various sections of the guide. I think this is much more scannable plus more light hearted in a good way, but open to feedback if anyone thinks it's going too far and detracting from the material 😁
@rachktz @emilyrichmond @ryanswood @richieweldon

You know I'm 🙌 about those emojis.

I like the emojis! Gives it a whimsical feel.


rooster-command-bar-overflow class is not getting added to the focusZone

The npm package of roosterjs-react is yeilding inconsistent results compared to the demo. The command bar overflow styling is off. There is a difference in the latest build files and the npm package files.
roosterjs-react version - 0.0.72
roosterjs version - 7.9.1
On pulling from npm and running sample code-

On running sample code from repo-

The following files are different in the github repo build and npm package build-
RoosterCommandBar.js
On cloning repo and running npm run build-
RoosterCommandBar.prototype.render = function () {
        var _a = this.props, className = _a.className, calloutClassName = _a.calloutClassName, calloutOnDismiss = _a.calloutOnDismiss, overflowMenuProps = _a.overflowMenuProps, commandBarClassName = _a.commandBarClassName, ellipsisAriaLabel = _a.ellipsisAriaLabel;
        // with the newest changes on the editor, refresh the buttons (e.g. bold button being selected if text selected is bold and header being checked if used)
        this._buttons.forEach(this._refreshButtonStates);
        return (React.createElement("div", { className: Utilities_1.css("rooster-command-bar", className) },
            React.createElement(CommandBar_1.CommandBar, { className: Utilities_1.css("rooster-command-bar-base", commandBarClassName), items: this._buttons, overflowButtonProps: {
                    ariaLabel: ellipsisAriaLabel,
                    menuProps: __assign({}, overflowMenuProps, {
                        // we set items as empty to satisfy the type checker & because otherwise the component
                        // throws an error about an unexpected `undefined` value on first render.
                        //
                        // We expect it to be overridden by the commandBar when rendering the button
                        // after measuring.
                        items: [], calloutProps: {
                            className: calloutClassName
                        }, onDismiss: calloutOnDismiss, className: Utilities_1.css("rooster-command-bar-overflow", overflowMenuProps && overflowMenuProps.className), focusZoneProps: { direction: FocusZone_1.FocusZoneDirection.horizontal } })
                } }),
            React.createElement("input", { type: "file", ref: this._fileInputOnRef, accept: "image/*", style: DisplayNoneStyle, onChange: this._fileInputOnChange })));
    };

On pulling from npm-
RoosterCommandBar.prototype.render = function () {
        var _a = this.props, className = _a.className, calloutClassName = _a.calloutClassName, calloutOnDismiss = _a.calloutOnDismiss, overflowMenuProps = _a.overflowMenuProps, commandBarClassName = _a.commandBarClassName, ellipsisAriaLabel = _a.ellipsisAriaLabel;
        // with the newest changes on the editor, refresh the buttons (e.g. bold button being selected if text selected is bold and header being checked if used)
        this._buttons.forEach(this._refreshButtonStates);
        return (React.createElement("div", { className: Utilities_1.css("rooster-command-bar", className) },
            React.createElement(CommandBar_1.CommandBar, { className: Utilities_1.css("rooster-command-bar-base", commandBarClassName), items: this._buttons, overflowMenuProps: __assign({}, overflowMenuProps, { calloutProps: {
                        className: calloutClassName
                    }, onDismiss: calloutOnDismiss, className: Utilities_1.css("rooster-command-bar-overflow", overflowMenuProps && overflowMenuProps.className), focusZoneProps: { direction: FocusZone_1.FocusZoneDirection.horizontal } }), elipisisAriaLabel: ellipsisAriaLabel }),
            React.createElement("input", { type: "file", ref: this._fileInputOnRef, accept: "image/*", style: DisplayNoneStyle, onChange: this._fileInputOnChange })));
    };

This repo is archived now. For react wrapper of roosterjs, please refer to roosterjs-react package in roosterjs repo. Thanks.


-webkit-scrollbar

-webkit-scrollbar

This issue was imported from Google Moderator
Moderator votes: +16
Issue added by egpierro on 2014-04-22
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

Duplicate of #1449.


Share the same ESlint and Prettier config

I see that each time the changed code in commits includes "..." => '...' this is just an example but we need to use the same config.

What about configuring pre-commit hooks?
@Khalid1G


Need validation tool to ascertain that user provided pipeline definition is valid

is the user input provided valid?
model parameters, actions along edges, switch statements with defaults

Hi @mkbhanda , we use a DAG to ensure the pipeline definition is valid. Once you add an edge with a flow_to, it will check whether the pipeline contains a cycle and raise an error if it does. For more info please check https://github.com/opea-project/GenAIComps/blob/main/comps/cores/mega/dag.py.
Regarding to the model parameters, we use existing library docarray and pydantic for each microservice to validate the parameters passed by users, which is defined in https://github.com/opea-project/GenAIComps/blob/main/comps/cores/proto/docarray.py.
Regarding to your question about "switch statements with defaults", I assume that you are talking about possible different conditions under which data is transmitted to different downstream microservices. We actually have a basic modification on our DAG which can support deleting edge at runtime if some conditions are met. That part of logics is in https://github.com/opea-project/GenAIComps/blob/main/comps/cores/mega/orchestrator.py. One usecase is that if the users' prompt is invalid, the orchestrator will deny to forward the first GuardRails microservice's output to other downstreams (Embedding, Reranking, Retrieval, LLM), otherwise should let it pass.

Hi @mkbhanda , can we close this issue now?


Valeriya: Headless-CMS, Weeks 3

Learning goals

[x] 🥚 Understanding what a content management system is, and why people use it
[ ] 🥚 Given an existing CMS installation fill in and publish a new piece of content
[ ] 🥚 Perform a simple http call via postman to retrieve a piece of information.
[ ] 🐣 Extend and adapt an existing CMS configuration
[ ] 🐣 Perform a http call with filtering via Postman
[ ] 🐣 Perform a http call with "include" via Postman
[ ] 🐣 Perform a http POST call to create new data
[ ] 🐣 Perform a http PUT call to update existing data
[ ] 🐣 Configuring endpoint permissions (Authentication vs Authorization)
[ ] 🐥 Design a data model from scratch based on user requirements

my fork of module repository

Week 1
I Need Help With:

my last week project ToDo List. I have  problem with checkbox https://github.com/V-Valkiriya/todo-list

What went well?

my last project ToDo List. Another version of the tutorial https://github.com/V-Valkiriya/todo-list-2

What went less well?

CMS is not quite clear yet for me.

Lessons Learned

Data modelling

Sunday Prep Work

Read about it :smile_cat:

Week 2
I Need Help With:

ex. 6 en 7 (2-complex-queries)

What went well?

ex. 1-5, watching film about strapi

What went less well?

some exers.

Lessons Learned

complex queries

Sunday Prep Work

Read about it :smile_cat:

Week 3
I Need Help With:

don`t need help now

What went well?

watching video about strapi and postman. Reading about React.

What went less well?

team project (I was online)

Lessons Learned

work with strapi (get and modifying data)

Sunday Prep Work

I doing that :smile_cat:


[stable/phpmyadmin] not working with traefik ingress controller

Is this a request for help?: yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:

Helm:

Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Kubernetes:

Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-10T11:44:36Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T20:56:12Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}

Which chart:

stable/phpmyadmin

What happened:
I'm trying to install phpyadmin with traefik as ingress controller. It deploys without problems but when I try to open the ingress url phpmyadmin only shows a blank page. When opening dev-tools in chrome I saw that the  element has a display: none style. After removing this I see an error message that a missassignment between HTTP and HTTPS. When I try to log in it errors with Failed to set session cookie. Maybe you are using HTTP instead of HTTPS to access phpMyAdmin.
What you expected to happen:
Actually see the phpmyadmin login when opening the ingress URL.
How to reproduce it (as minimally and precisely as possible):

Install traefik as an ingress controller
run helm install --name phpmyadmin stable/phpmyadmin --set ingress.enabled=true,ingress.host=phpmyadmin.example.com

Anything else we need to know:
My k8s cluster is running on bare metal. I don't think this is the problem since everything else is running smoothly. Just FYI

I think the problem is one of the annotations set by default in the values.yaml.
If you comment/delete the first annotation it works fine:
annotations:
    #ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/rewrite-target: /

I had a different issue (CSS/JS were not loading due to strict mime type checking) but @tompizmor 's solution worked for me.
By any chance would it be possible to include that fix in the repository ?

could this be reopened? The error still exists and phpmyadmin-chart does not work out of the box with the annotations. I wonder if the chart would work with the ngingx-controller and without the annotations or are they required?.

I would also like to request re open this issue . I am facing the same problem  with traefik controller as explained by cwinkler.


[code] improve cards on phone

Current

Change required

File to change
society-sphere/src/components/FlipCard/

#40 solves this issue


Docker Image is not removing from teamcity cloud profile

Hi,
We have added multiple docker images in one cloud profile. when i delete it's deleting from list and saving my changes. But, when i re-open the cloud profile the same image is showing.
I have done  multiple times, but same issue.
Can you please help with this.

Hi,
There is indeed a missing Javascript callback when deleting images. The JSON structure hosting the image configuration is then not updated as it should... This issue has been here for a while...
As a temporary workaround, you can delete the table entry, and then open and save any other cloud image. The deletion should then be effective.
I'll release a new minor version handling both issues you reported, middle of the next week.
Thank you for reporting!


Service is down

Hi,
Will the service be back up any time soon?
Thanks

Service is down again. Is there any mirrors ?

Service is down but domain is still working.
A non-onion mirror site here :
http://pwndb2am4tzkvold.onion.pet/

Domain is no longer working
Any new mirrors?

@226914011
http://pwndb2am4tzkvold.onion.pet/
The above mentioned site is working quite well without tor. You can try with any simple emails or passwords if want to check it. If your creds is not showing up in there, that mean your creds are not in leaked database.


RHOAIENG-4214: Fixing broken link

Description
Fixing broken link
How Has This Been Tested?
local build

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

lgtm


Add amo (mozilla add-ons) badges

The mozilla add-ons API (unfortunately) returns XML.
Theres is a JSON version that does not include all the fields, such as ratings, reviews and daily_users.
So I’m using xml2js to transform the XML to JSON.

Cool! Thanks @tusbar


unfork eth's EVM

@benjaminbollen @compleatang capturing what we decided in Berlin WRT to this:

Fork Ethereum to allow changes or track upstream as we wish
Update eris/tendermint to match the godeps vendored tendermint in eris/eris-db
Sync the vendored version of tendermint with eris/tendermint
Pull up the tendermint repository to the top level of this repository
Make tests pass
Factor out some of the tendermint/* stuff then pull tendermint/tendermint to top level
Make tests pass
Make eris-db depend on appropriate packages in eris/ethereum (for current VM)
Remove old tendermint VM
Manually apply work-in-progress unforking changes from #69
Complete unforking of Ethereum VM so eris/eris-db/tendermint depends on current Ethereum VM as a proper dependency

How are we planning to address ed22519 support in the unforked EVM?

@AFDudley I don't know, could you elaborate? Assuming we have some patched ed22519 support in currently eris-db -> vendored tendermint -> 'forked' eth?

Yeah. That's the assumption, I don't have the details, but it should be trivial to check by looking at imports.

With erismint and other priorities consider this superceded and ticket not needed to remind us that this is a thing, let's create another ticket before we embark on such integration.


Data in the wrong columns

+1

Fixed in the major version release.
🔗 https://github.com/ahmadawais/corona-cli/releases/tag/3.0.0
🔗 https://www.npmjs.com/package/corona-cli
🏁 Done (in 27s.)


Laravel new breaks at autoloading

Laravel Version: v8.6.2
PHP Version: 8.0.10

Description:
Creating a new laravel app stops at Generating optimized autoload files
Steps To Reproduce:
laravel new sample
Generating optimized autoload files
    Class Symfony\Component\Translation\Extractor\AbstractFileExtractor located in C:/code/sample/vendor/symfony/translation\AbstractFileExtractor.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Catalogue\AbstractOperation located in C:/code/sample/vendor/symfony/translation\AbstractOperation.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\AbstractOperationTest located in C:/code/sample/vendor/symfony/translation\AbstractOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\AbstractProviderFactory located in C:/code/sample/vendor/symfony/translation\AbstractProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Util\ArrayConverter located in C:/code/sample/vendor/symfony/translation\ArrayConverter.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Util\ArrayConverterTest located in C:/code/sample/vendor/symfony/translation\ArrayConverterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\ArrayLoader located in C:/code/sample/vendor/symfony/translation\ArrayLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\AbstractOperationTest located in C:/code/sample/vendor/symfony/translation\Catalogue\AbstractOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\MergeOperationTest located in C:/code/sample/vendor/symfony/translation\Catalogue\MergeOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\TargetOperationTest located in C:/code/sample/vendor/symfony/translation\Catalogue\TargetOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Extractor\ChainExtractor located in C:/code/sample/vendor/symfony/translation\ChainExtractor.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\TranslationProviderTestCase located in C:/code/sample/vendor/symfony/translation\Command\TranslationProviderTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\TranslationPullCommandTest located in C:/code/sample/vendor/symfony/translation\Command\TranslationPullCommandTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\XliffLintCommandTest located in C:/code/sample/vendor/symfony/translation\Command\XliffLintCommandTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ControllerArguments located in C:/code/sample/vendor/symfony/translation\ControllerArguments.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\CrowdinProvider located in C:/code/sample/vendor/symfony/translation\Crowdin\CrowdinProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\CrowdinProviderFactory located in C:/code/sample/vendor/symfony/translation\Crowdin\CrowdinProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\CrowdinProvider located in C:/code/sample/vendor/symfony/translation\CrowdinProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\CrowdinProviderFactory located in C:/code/sample/vendor/symfony/translation\CrowdinProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\Tests\CrowdinProviderFactoryTest located in C:/code/sample/vendor/symfony/translation\CrowdinProviderFactoryTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Crowdin\Tests\CrowdinProviderTest located in C:/code/sample/vendor/symfony/translation\CrowdinProviderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\CsvFileDumper located in C:/code/sample/vendor/symfony/translation\CsvFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\CsvFileDumperTest located in C:/code/sample/vendor/symfony/translation\CsvFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\CsvFileLoader located in C:/code/sample/vendor/symfony/translation\CsvFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\CsvFileLoaderTest located in C:/code/sample/vendor/symfony/translation\CsvFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DataCollector\TranslationDataCollectorTest located in C:/code/sample/vendor/symfony/translation\DataCollector\TranslationDataCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DataCollectorTranslatorTest located in C:/code/sample/vendor/symfony/translation\DataCollectorTranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ControllerArguments located in C:/code/sample/vendor/symfony/translation\DependencyInjection\fixtures\ControllerArguments.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceArguments located in C:/code/sample/vendor/symfony/translation\DependencyInjection\fixtures\ServiceArguments.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceMethodCalls located in C:/code/sample/vendor/symfony/translation\DependencyInjection\fixtures\ServiceMethodCalls.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceProperties located in C:/code/sample/vendor/symfony/translation\DependencyInjection\fixtures\ServiceProperties.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceSubscriber located in C:/code/sample/vendor/symfony/translation\DependencyInjection\fixtures\ServiceSubscriber.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationDumperPassTest located in C:/code/sample/vendor/symfony/translation\DependencyInjection\TranslationDumperPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationExtractorPassTest located in C:/code/sample/vendor/symfony/translation\DependencyInjection\TranslationExtractorPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationPathsPassTest located in C:/code/sample/vendor/symfony/translation\DependencyInjection\TranslationPathsPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslatorPassTest located in C:/code/sample/vendor/symfony/translation\DependencyInjection\TranslatorPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\Dsn located in C:/code/sample/vendor/symfony/translation\Dsn.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Provider\DsnTest located in C:/code/sample/vendor/symfony/translation\DsnTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\CsvFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\CsvFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\FileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\FileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\ConcreteFileDumper located in C:/code/sample/vendor/symfony/translation\Dumper\FileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\IcuResFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\IcuResFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\IniFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\IniFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\JsonFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\JsonFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\MoFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\MoFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\PhpFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\PhpFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\PoFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\PoFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\QtFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\QtFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\XliffFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\XliffFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\YamlFileDumperTest located in C:/code/sample/vendor/symfony/translation\Dumper\YamlFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\DumperInterface located in C:/code/sample/vendor/symfony/translation\DumperInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Exception\UnsupportedSchemeExceptionTest located in C:/code/sample/vendor/symfony/translation\Exception\UnsupportedSchemeExceptionTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\ExceptionInterface located in C:/code/sample/vendor/symfony/translation\ExceptionInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Extractor\PhpExtractorTest located in C:/code/sample/vendor/symfony/translation\Extractor\PhpExtractorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Extractor\ExtractorInterface located in C:/code/sample/vendor/symfony/translation\ExtractorInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\FileDumper located in C:/code/sample/vendor/symfony/translation\FileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\FileDumperTest located in C:/code/sample/vendor/symfony/translation\FileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\ConcreteFileDumper located in C:/code/sample/vendor/symfony/translation\FileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\FileLoader located in C:/code/sample/vendor/symfony/translation\FileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\FilteringProvider located in C:/code/sample/vendor/symfony/translation\FilteringProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Formatter\IntlFormatterTest located in C:/code/sample/vendor/symfony/translation\Formatter\IntlFormatterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Formatter\MessageFormatterTest located in C:/code/sample/vendor/symfony/translation\Formatter\MessageFormatterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\IcuDatFileLoader located in C:/code/sample/vendor/symfony/translation\IcuDatFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IcuDatFileLoaderTest located in C:/code/sample/vendor/symfony/translation\IcuDatFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\IcuResFileDumper located in C:/code/sample/vendor/symfony/translation\IcuResFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\IcuResFileDumperTest located in C:/code/sample/vendor/symfony/translation\IcuResFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\IcuResFileLoader located in C:/code/sample/vendor/symfony/translation\IcuResFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IcuResFileLoaderTest located in C:/code/sample/vendor/symfony/translation\IcuResFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\IdentityTranslatorTest located in C:/code/sample/vendor/symfony/translation\IdentityTranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\IncompleteDsnException located in C:/code/sample/vendor/symfony/translation\IncompleteDsnException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\IniFileDumper located in C:/code/sample/vendor/symfony/translation\IniFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\IniFileDumperTest located in C:/code/sample/vendor/symfony/translation\IniFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\IniFileLoader located in C:/code/sample/vendor/symfony/translation\IniFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IniFileLoaderTest located in C:/code/sample/vendor/symfony/translation\IniFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Formatter\IntlFormatter located in C:/code/sample/vendor/symfony/translation\IntlFormatter.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Formatter\IntlFormatterInterface located in C:/code/sample/vendor/symfony/translation\IntlFormatterInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Formatter\IntlFormatterTest located in C:/code/sample/vendor/symfony/translation\IntlFormatterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\InvalidArgumentException located in C:/code/sample/vendor/symfony/translation\InvalidArgumentException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\InvalidResourceException located in C:/code/sample/vendor/symfony/translation\InvalidResourceException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\JsonFileDumper located in C:/code/sample/vendor/symfony/translation\JsonFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\JsonFileDumperTest located in C:/code/sample/vendor/symfony/translation\JsonFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\JsonFileLoader located in C:/code/sample/vendor/symfony/translation\JsonFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\JsonFileLoaderTest located in C:/code/sample/vendor/symfony/translation\JsonFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\CsvFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\CsvFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IcuDatFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\IcuDatFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IcuResFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\IcuResFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\IniFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\IniFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\JsonFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\JsonFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\LocalizedTestCase located in C:/code/sample/vendor/symfony/translation\Loader\LocalizedTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\MoFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\MoFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\PhpFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\PhpFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\PoFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\PoFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\QtFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\QtFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\XliffFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\XliffFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\YamlFileLoaderTest located in C:/code/sample/vendor/symfony/translation\Loader\YamlFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\LoaderInterface located in C:/code/sample/vendor/symfony/translation\LoaderInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\LocalizedTestCase located in C:/code/sample/vendor/symfony/translation\LocalizedTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\LocoProvider located in C:/code/sample/vendor/symfony/translation\Loco\LocoProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\LocoProviderFactory located in C:/code/sample/vendor/symfony/translation\Loco\LocoProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\LocoProvider located in C:/code/sample/vendor/symfony/translation\LocoProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\LocoProviderFactory located in C:/code/sample/vendor/symfony/translation\LocoProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\Tests\LocoProviderFactoryTest located in C:/code/sample/vendor/symfony/translation\LocoProviderFactoryTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Loco\Tests\LocoProviderTest located in C:/code/sample/vendor/symfony/translation\LocoProviderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\LoggingTranslatorTest located in C:/code/sample/vendor/symfony/translation\LoggingTranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\LogicException located in C:/code/sample/vendor/symfony/translation\LogicException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\LokaliseProvider located in C:/code/sample/vendor/symfony/translation\Lokalise\LokaliseProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\LokaliseProviderFactory located in C:/code/sample/vendor/symfony/translation\Lokalise\LokaliseProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\LokaliseProvider located in C:/code/sample/vendor/symfony/translation\LokaliseProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\LokaliseProviderFactory located in C:/code/sample/vendor/symfony/translation\LokaliseProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\Tests\LokaliseProviderFactoryTest located in C:/code/sample/vendor/symfony/translation\LokaliseProviderFactoryTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Bridge\Lokalise\Tests\LokaliseProviderTest located in C:/code/sample/vendor/symfony/translation\LokaliseProviderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Catalogue\MergeOperation located in C:/code/sample/vendor/symfony/translation\MergeOperation.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\MergeOperationTest located in C:/code/sample/vendor/symfony/translation\MergeOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\MessageCatalogueTest located in C:/code/sample/vendor/symfony/translation\MessageCatalogueTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Formatter\MessageFormatter located in C:/code/sample/vendor/symfony/translation\MessageFormatter.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Formatter\MessageFormatterInterface located in C:/code/sample/vendor/symfony/translation\MessageFormatterInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Formatter\MessageFormatterTest located in C:/code/sample/vendor/symfony/translation\MessageFormatterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\MissingRequiredOptionException located in C:/code/sample/vendor/symfony/translation\MissingRequiredOptionException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\MoFileDumper located in C:/code/sample/vendor/symfony/translation\MoFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\MoFileDumperTest located in C:/code/sample/vendor/symfony/translation\MoFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\MoFileLoader located in C:/code/sample/vendor/symfony/translation\MoFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\MoFileLoaderTest located in C:/code/sample/vendor/symfony/translation\MoFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\NotFoundResourceException located in C:/code/sample/vendor/symfony/translation\NotFoundResourceException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\NullProvider located in C:/code/sample/vendor/symfony/translation\NullProvider.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\NullProviderFactory located in C:/code/sample/vendor/symfony/translation\NullProviderFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Provider\NullProviderFactoryTest located in C:/code/sample/vendor/symfony/translation\NullProviderFactoryTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Catalogue\OperationInterface located in C:/code/sample/vendor/symfony/translation\OperationInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Extractor\PhpExtractor located in C:/code/sample/vendor/symfony/translation\PhpExtractor.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Extractor\PhpExtractorTest located in C:/code/sample/vendor/symfony/translation\PhpExtractorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\PhpFileDumper located in C:/code/sample/vendor/symfony/translation\PhpFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\PhpFileDumperTest located in C:/code/sample/vendor/symfony/translation\PhpFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\PhpFileLoader located in C:/code/sample/vendor/symfony/translation\PhpFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\PhpFileLoaderTest located in C:/code/sample/vendor/symfony/translation\PhpFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Extractor\PhpStringTokenParser located in C:/code/sample/vendor/symfony/translation\PhpStringTokenParser.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\PoFileDumper located in C:/code/sample/vendor/symfony/translation\PoFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\PoFileDumperTest located in C:/code/sample/vendor/symfony/translation\PoFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\PoFileLoader located in C:/code/sample/vendor/symfony/translation\PoFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\PoFileLoaderTest located in C:/code/sample/vendor/symfony/translation\PoFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Provider\DsnTest located in C:/code/sample/vendor/symfony/translation\Provider\DsnTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Provider\NullProviderFactoryTest located in C:/code/sample/vendor/symfony/translation\Provider\NullProviderFactoryTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\ProviderException located in C:/code/sample/vendor/symfony/translation\ProviderException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\ProviderExceptionInterface located in C:/code/sample/vendor/symfony/translation\ProviderExceptionInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\ProviderFactoryInterface located in C:/code/sample/vendor/symfony/translation\ProviderFactoryInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Test\ProviderFactoryTestCase located in C:/code/sample/vendor/symfony/translation\ProviderFactoryTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\ProviderInterface located in C:/code/sample/vendor/symfony/translation\ProviderInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Test\ProviderTestCase located in C:/code/sample/vendor/symfony/translation\ProviderTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\PseudoLocalizationTranslatorTest located in C:/code/sample/vendor/symfony/translation\PseudoLocalizationTranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\QtFileDumper located in C:/code/sample/vendor/symfony/translation\QtFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\QtFileDumperTest located in C:/code/sample/vendor/symfony/translation\QtFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\QtFileLoader located in C:/code/sample/vendor/symfony/translation\QtFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\QtFileLoaderTest located in C:/code/sample/vendor/symfony/translation\QtFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\RuntimeException located in C:/code/sample/vendor/symfony/translation\RuntimeException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceArguments located in C:/code/sample/vendor/symfony/translation\ServiceArguments.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceMethodCalls located in C:/code/sample/vendor/symfony/translation\ServiceMethodCalls.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceProperties located in C:/code/sample/vendor/symfony/translation\ServiceProperties.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\fixtures\ServiceSubscriber located in C:/code/sample/vendor/symfony/translation\ServiceSubscriber.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Catalogue\TargetOperation located in C:/code/sample/vendor/symfony/translation\TargetOperation.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Catalogue\TargetOperationTest located in C:/code/sample/vendor/symfony/translation\TargetOperationTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\TranslatableTest located in C:/code/sample/vendor/symfony/translation\TranslatableTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\DataCollector\TranslationDataCollector located in C:/code/sample/vendor/symfony/translation\TranslationDataCollector.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DataCollector\TranslationDataCollectorTest located in C:/code/sample/vendor/symfony/translation\TranslationDataCollectorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\DependencyInjection\TranslationDumperPass located in C:/code/sample/vendor/symfony/translation\TranslationDumperPass.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationDumperPassTest located in C:/code/sample/vendor/symfony/translation\TranslationDumperPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\DependencyInjection\TranslationExtractorPass located in C:/code/sample/vendor/symfony/translation\TranslationExtractorPass.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationExtractorPassTest located in C:/code/sample/vendor/symfony/translation\TranslationExtractorPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslationPathsPassTest located in C:/code/sample/vendor/symfony/translation\TranslationPathsPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\TranslationProviderCollection located in C:/code/sample/vendor/symfony/translation\TranslationProviderCollection.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Provider\TranslationProviderCollectionFactory located in C:/code/sample/vendor/symfony/translation\TranslationProviderCollectionFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\TranslationProviderTestCase located in C:/code/sample/vendor/symfony/translation\TranslationProviderTestCase.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Command\TranslationPullCommand located in C:/code/sample/vendor/symfony/translation\TranslationPullCommand.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\TranslationPullCommandTest located in C:/code/sample/vendor/symfony/translation\TranslationPullCommandTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Command\TranslationPushCommand located in C:/code/sample/vendor/symfony/translation\TranslationPushCommand.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Reader\TranslationReader located in C:/code/sample/vendor/symfony/translation\TranslationReader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Reader\TranslationReaderInterface located in C:/code/sample/vendor/symfony/translation\TranslationReaderInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Command\TranslationTrait located in C:/code/sample/vendor/symfony/translation\TranslationTrait.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Writer\TranslationWriter located in C:/code/sample/vendor/symfony/translation\TranslationWriter.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Writer\TranslationWriterInterface located in C:/code/sample/vendor/symfony/translation\TranslationWriterInterface.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Writer\TranslationWriterTest located in C:/code/sample/vendor/symfony/translation\TranslationWriterTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\TranslatorBagTest located in C:/code/sample/vendor/symfony/translation\TranslatorBagTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\TranslatorCacheTest located in C:/code/sample/vendor/symfony/translation\TranslatorCacheTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\StaleResource located in C:/code/sample/vendor/symfony/translation\TranslatorCacheTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\DependencyInjection\TranslatorPass located in C:/code/sample/vendor/symfony/translation\TranslatorPass.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\DependencyInjection\TranslatorPassTest located in C:/code/sample/vendor/symfony/translation\TranslatorPassTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\DependencyInjection\TranslatorPathsPass located in C:/code/sample/vendor/symfony/translation\TranslatorPathsPass.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\TranslatorTest located in C:/code/sample/vendor/symfony/translation\TranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\StringClass located in C:/code/sample/vendor/symfony/translation\TranslatorTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Exception\UnsupportedSchemeException located in C:/code/sample/vendor/symfony/translation\UnsupportedSchemeException.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Exception\UnsupportedSchemeExceptionTest located in C:/code/sample/vendor/symfony/translation\UnsupportedSchemeExceptionTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\XliffFileDumper located in C:/code/sample/vendor/symfony/translation\XliffFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\XliffFileDumperTest located in C:/code/sample/vendor/symfony/translation\XliffFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\XliffFileLoader located in C:/code/sample/vendor/symfony/translation\XliffFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Loader\XliffFileLoaderTest located in C:/code/sample/vendor/symfony/translation\XliffFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Command\XliffLintCommand located in C:/code/sample/vendor/symfony/translation\XliffLintCommand.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Command\XliffLintCommandTest located in C:/code/sample/vendor/symfony/translation\XliffLintCommandTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Util\XliffUtils located in C:/code/sample/vendor/symfony/translation\XliffUtils.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Dumper\YamlFileDumper located in C:/code/sample/vendor/symfony/translation\YamlFileDumper.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Tests\Dumper\YamlFileDumperTest located in C:/code/sample/vendor/symfony/translation\YamlFileDumperTest.php does not comply with psr-4 autoloading standard. Skipping.
Class Symfony\Component\Translation\Loader\YamlFileLoader located in C:/code/sample/vendor/symfony/translation\YamlFileLoader.php does not comply with psr-4 autoloading standard. Skipping.
    Class Symfony\Component\Translation\Tests\Loader\YamlFileLoaderTest located in C:/code/sample/vendor/symfony/translation\YamlFileLoaderTest.php does not comply with psr-4 autoloading standard. Skipping.
    > Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   Error

  Class "Symfony\Component\Translation\Loader\ArrayLoader" not found

  at C:\code\sample\vendor\nesbot\carbon\src\Carbon\Translator.php:80
     76▕     public function __construct($locale, Translation\Formatter\MessageFormatterInterface $formatter = null, $cacheDir = null, $debug = false)
     77▕     {
     78▕         $this->initializing = true;
     79▕         $this->directories = [__DIR__.'/Lang'];
  ➜  80▕         $this->addLoader('array', new Translation\Loader\ArrayLoader());
     81▕         parent::__construct($locale, $formatter, $cacheDir, $debug);
     82▕         $this->initializing = false;
     83▕     }
     84▕

  1   C:\code\sample\vendor\nesbot\carbon\src\Carbon\Translator.php:70
      Carbon\Translator::__construct("en")

  2   C:\code\sample\vendor\nesbot\carbon\src\Carbon\Traits\Localization.php:691
      Carbon\Translator::get()
    Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Refer to #39008

It's an issue in Symfony. They're aware and on it.


Set up Automated Regression Test workflow

Requirements:

[ ] Identify Existing Tests to be included in the workflow

[ ]  Add Automated tests to Regression test workflow

[ ] Schedule to be run in Dev environment on a weekly basis

@MaeganWood64 Provide list to Yefim and then this ticket can be added to in development

Need confirmation on when to run smoke and regression tests in test and beta


Remove transitionEnd eventlistener

Because the transitionEnd event isn't always triggered on the root component node (if modal contains some other transitions), it wasn't always removed.

Thanks again!