text:
47 multi datasource alert

What this PR does / why we need it (변경 내용 / 필요성):

alerter를 작성하고 기초적인 테스트 코드를 추가했습니다.
상세한 테스트 코드는 logger 도입 후에 하면 좋겠습니다. verbose 모드로 확인해야 할 것이 많아 보입니다.
alerter에서 사용하는, 이번에 새로 도입한 AlertFile은 기존의 RuleFile과 대응되는데, RuleFile은 DatasourceSelector를 가지지만 AlertFile은 Datasource 1개를 가지게 되어 있습니다. 따라서 RuleFile과 AlertFile은 DatasourceSelector 해당되는 datasource의 개수만큼 1:N 대응됩니다.
userConfig/usersConfig, datasourceConfig/datasourcesConfig 반드시 복수형일 필요가 없는 곳은 혼동이 없도록 단수형으로 변경했습니다. 앞으로도 의미상 복수형이 꼭 필요하지 않다면 단수형을 우선 고려하는 게 좋겠습니다.
configuration 디렉토리/패키지명을 config로 변경했습니다.

Which issue(s) this PR fixes (관련 이슈):

#47
#23

Special notes for your reviewer (리뷰어에게 하고 싶은 말):
리뷰 감사합니다.
Additional documentation, usage docs, etc. (기타 관련 문서, 사용법 등):
pkg/model/rulefmt.go 에 prometheus 관련 프로젝트들에서 사용하는 모델들을 표로 정리했습니다. 왔다갔다 하다 보니 현행화가 약간 미흡할 수는 있습니다. 결론적으로는 commonModel을 우선 고려하고 그것으로 해결이 안되면 대안을 찾아야 할 것 같습니다.

Codecov Report
Patch coverage: 40.46% and project coverage change: -2.33 :warning:

Comparison is base (6fa8f8c) 40.76% compared to head (62b0d92) 38.44%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
- Coverage   40.76%   38.44%   -2.33%
==========================================
  Files          19       23       +4
  Lines         628      848     +220
==========================================
+ Hits          256      326      +70
- Misses        341      484     +143
- Partials       31       38       +7

Impacted Files
Coverage Δ

pkg/handler/api_error.go
0.00% <ø> (ø)

pkg/handler/auth.go
1.90% <ø> (ø)

pkg/handler/config.go
50.00% <ø> (ø)

pkg/handler/datasource.go
15.38% <ø> (ø)

pkg/handler/handle_spa.go
33.33% <ø> (ø)

pkg/handler/remote.go
54.54% <ø> (ø)

pkg/mock/alert_rule_file.go
0.00% <0.00%> (ø)

pkg/mock/datasource.go
0.00% <0.00%> (ø)

pkg/mock/datasource_config.go
0.00% <0.00%> (ø)

pkg/store/dashboard_store.go
0.00% <0.00%> (ø)

... and 11 more

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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

수정 후 테스트 과정에서 alertmanager mock을 추가하였습니다.
리뷰해주신 부분 반영하였습니다. 리뷰 감사합니다. squash and merge 합니다.

수정 후 테스트 과정에서 alertmanager mock을 추가하였습니다.
리뷰해주신 부분 반영하였습니다. 리뷰 감사합니다. squash and merge 합니다.

authors: codecov-commenter jmnote

repo: kuoss/venti


text:
Update linux to 6.13-rc2

I bisected linux so I found the commit that is causing the systemd messages to not appear, though I am not sure about the root cause. Added a revert for now, and it fixes the issue.
Also this PR does not build currently without this: https://github.com/NixOS/nixpkgs/pull/364044
I might just include it as a nixpkgs patch if that PR does not get attention quickly, we are already patching nixpkgs anyway...
Status:

[ ] Tested
[ ] Reviewed

Can't test because apparently the new firefox hasn't made it into the binary cache yet, and I don't think I want to attempt building that as part of the install process... I will try again tomorrow.

@powpingdone you can take a look if you want, I think this will be the final version, but as I mentioned above I am waiting for Hydra to build firefox to be able to test it: https://hydra.nixos.org/build/282044215

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
KUZ 552 Response from router.execute() is not an ResponseObject

Because plugins protocol are now loaded by LB, and the LB has only a response and not a responseObject, we can return directly response and not responseObject.toJson()

+1

[Current coverage][cc-pull] is 98.36%

Merging [#7][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master         #7   diff @@
==========================================
  Files             2          2
  Lines            61         61
  Methods           7          7
  Messages          0          0
  Branches         11         11
==========================================
  Hits             60         60
  Misses            1          1
  Partials          0          0

Powered by Codecov. Last updated by [c8bf1ed...ce2c666][cc-compare]
[cc-base-branch]: https://codecov.io/gh/kuzzleio/kuzzle-plugin-socketio/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/kuzzleio/kuzzle-plugin-socketio/compare/c8bf1ed10180df1203d2041bf90fb7de3f37a88d...ce2c666ab8563c3b01a5ca81ee9388667cf65772
[cc-pull]: https://codecov.io/gh/kuzzleio/kuzzle-plugin-socketio/pull/7?src=pr

+1

+1

+1

authors: AnthonySendra benoitvidis codecov-io jenow scottinet stafyniaksacha

repo: kuzzleio/kuzzle-plugin-socketio

license_source: bigquery


text:
Adding multi language support system

I want to add multi language support system to the website which can help us understand in their native language.

This feature is already present...

@kvcops  sry i don't see this feature in website

It's ok...make sure to suggest more features that may help for the website

source: gharchive/issue

repo: kvcops/KV-Nexus


text:
More about the question about the forecastability

I appreciate your quick reply.  :-)

Q: It seems a counterintuitive phenomenon of forecastability. Table 1 shows that the weather and Electricity datasets possess high forecastabilities. In other words, they are easier to predict than these datasets with low forecastability, e.g., ETT (4 datasets). However, the ETT, traffic datasets have obvious periodic patterns derived from the visualizations and ACF. Especially, it is harder to find the pattern to fit, as shown in Fig 12 of the paper. Could you provide some insights into the above question?

A: Thank you very much for your attention to our work. Forecastability is a key issue in time series analysis. Currently, our forecastability calculations are performed through global sampling on the time series. The ETT dataset is actually recognized as one with a higher degree of forecasting difficulty. The visual showcases only display a portion of the content and do not represent the complete time series. Compared to larger datasets such as Electricity and Traffic, the patterns of cycles and trends are more evident, resulting in stronger predictability.

Moreover, How about the weather dataset? No matter the complete or partial time series, there are no obvious cycles or trends. Why is it easy to predict?

This is indeed a very pertinent question. When examining visualizations alone, handling weather data presents notable challenges. Although the forecastability analysis of the weather dataset appears promising, this may be attributed to the specific method of forecastability analysis employed. As detailed in our paper, the current forecastability analysis is conducted through fitting analysis using Fourier series. It is noteworthy that "Weather is recorded every 10 minutes throughout the year 2020, encompassing 21 meteorological indicators, such as air temperature, humidity, etc." This implies that, as a meteorological dataset, weather data exhibits pronounced seasonality, which could explain why the forecastability measurement method based on Fourier analysis yields favorable results. Furthermore, in comparison to datasets such as ETT, the weather dataset contains fewer missing and outlier values. The ETT dataset, which comprises data on electric transformer temperatures, includes a substantial amount of missing and anomalous data due to collection and sensor issues. Consequently, the weather dataset demonstrates superior performance in this regard, making it more favorable in terms of forecastability analysis compared to the ETT dataset.
Moreover, we should consider more rational methods of forecastability analysis for time series datasets. In other words, what constitutes an effective forecastability analysis of time series data? Although classical theories have provided numerous explanations, they all encounter limitations when faced with continuously growing time series data. We are actively exploring this issue and welcome any innovative ideas or further communication on this topic.
Once again, I would like to express my gratitude for the constructive question you raised. Deep contemplation surpasses mere practice; a well-posed question can significantly advance research development. Since the publication of Informer and Autoformer in 2021 and 2022, the time series community has experienced unprecedented growth. Data is a reflection of real-world problems, and excellent research necessitates starting from data to uncover the underlying essence. Current research on time series data lags behind that on image and text data, and it requires our collective effort to foster the prosperity and advancement of the community.

Many thanks for your thorough analysis. Especially, the last words mean a lot to the researchers in the time series community, of course, including me.

authors: kwuking mb-Ma

repo: kwuking/TimeMixer


text:
Create PostgreSQL Database with Tables

Description
A PostgreSQL database will be created to store our application data. The tables Device, Location, DeerSighting, Alerts, and Users will be defined to organize data for better management and querying.
Requirements

Set Up PostgreSQL Database:

Install PostgreSQL if not already installed.
Create a new database for the project, using a name that aligns with project standards.

Define Tables:

Device: Fields such as device_id, device_name, status.
Location: Fields like location_id, latitude, longitude, description.
DeerSighting: Fields such as sighting_id, location_id, time, description.
Alerts: Fields like alert_id, sighting_id, alert_time, alert_level.
Users: Fields such as user_id, username, email, password_hash.

Set Up Foreign Key Constraints:

Link tables with appropriate foreign keys (e.g., DeerSighting.location_id references Location.location_id).

Test Database Setup:

Create sample entries in each table to confirm structure and foreign key integrity.
Run queries to fetch data and ensure results match expected structure.

Acceptance Criteria

[x] PostgreSQL is installed and the project database is created.
[ ] Tables (Device, Location, DeerSighting, Alerts, Users) are defined with all necessary fields.
[ ] Foreign keys are set up and verified for integrity.
[ ] Sample data has been added to each table, and test queries confirm table relationships and data structure.

Created database and sudo users.


text:
[ModuleCatalog] Adapt Watch Mechanism to Monitor ModuleReleaseMeta CR Changes

Description:
The current watch mechanism for ModuleTemplate in the Kyma lifecycle manager needs to be adapted to track changes in the ModuleReleaseMeta Custom Resource (CR). This will enable the detection of new versions, channel switches, and other updates related to modules. The existing ModuleTemplate watch mechanism can be found here.
Detailed decision ticket: https://github.com/kyma-project/lifecycle-manager/issues/1815
Requirements:

The new watch mechanism must observe the ModuleReleaseMeta CR for changes, including:

Addition of new module versions.
Channel changes.
Any other relevant updates to the module-to-channel mappings.

Kyma Requeue Logic:

Requeue all Kymas that have a module enabled with the specific channel defined in the ModuleReleaseMeta.
Kymas with modules enabled by a specific version should not be requeued if the version remains unchanged.

Change in Implementation:

The current implementation uses EnqueueRequestsFromMapFunc in setup.go to watch changes, which does not allow for the comparison of old and new states of the ModuleReleaseMeta CR.
Switch to handler.Funcs{...}. This will allow access to both the old and new states in the Update function for proper reconciliation.

Example Code to get the diff in the Watch mechanism:
// ModuleReleaseMetaEventHandler implements handler.EventHandler
type ModuleReleaseMetaEventHandler struct{}

// Create handles Create events
func (c *ModuleReleaseMetaEventHandler) Create(e event.CreateEvent, q workqueue.RateLimitingInterface) {
	// Handle create logic if needed
}

// Update handles Update events and gets old and new state
func (c *ModuleReleaseMetaEventHandler) Update(e event.UpdateEvent, q workqueue.RateLimitingInterface) {
	log.Info("Resource updated", "Old Object", e.ObjectOld, "New Object", e.ObjectNew)
	kymaList := GetAllKymas()

	// Access both old and new objects
	// e.ObjectOld is the old state of the object
	// e.ObjectNew is the new state of the object
	affectedKymas := getAffectedKymas(kymaList, e.ObjectOld, e.ObjectNew)

	// With q.Add, we can add objects to the Reconcile Queue
	for _, kyma := range affectedKymas {
		q.Add(reconcile.Request{
			NamespacedName: types.NamespacedName{
				Name:      kyma.GetName(),
				Namespace: kyma.GetNamespace(),
			},
		})
	}
}

// getAffectedKymas determines which Kymas are affected by the update
func getAffectedKymas(kymas []v1beta2.Kyma, oldModuleReleaseMeta, newModuleReleaseMeta TypedUpdateEvent) []v1beta2.Kyma {
	var affectedKymas []v1beta2.Kyma
	for _, kyma := range kymas {
		for _, statusModule := range kyma.Status.Modules {
			if statusModule.Channel == newModuleReleaseMeta.Channel {
				affectedKymas = append(affectedKymas, kyma)
			}
		}
	}
	return affectedKymas
}

// Delete handles Delete events
func (c *ModuleReleaseMetaEventHandler) Delete(e event.DeleteEvent, q workqueue.RateLimitingInterface) {
	// Handle delete logic if needed
}

// Generic handles generic events
func (c *ModuleReleaseMetaEventHandler) Generic(e event.GenericEvent, q workqueue.RateLimitingInterface) {
	// Handle generic events if needed
}

func (r *Reconciler) SetupWithManager(mgr ctrl.Manager, opts ctrlruntime.Options, settings SetupOptions) error {
	...
	if err := ctrl.NewControllerManagedBy(mgr).For(&v1beta2.Kyma{}).
		Named(controllerName).
		WithOptions(opts).
		Watches(&v1beta2.ModuleTemplate{},
			&handler.Funcs{
				UpdateFunc: func(e event.UpdateEvent, rli workqueue.RateLimitingInterface) {
					// Call the custom update handler
					customHandler := &ModuleReleaseMetaEventHandler{}
					customHandler.Update(e, rli)
				},
			},
			builder.WithPredicates(predicates)).
		Watches(&apicorev1.Secret{}, handler.Funcs{}, builder.WithPredicates(predicates)).
		Watches(&v1beta2.Manifest{},
			handler.EnqueueRequestForOwner(mgr.GetScheme(), mgr.GetRESTMapper(), &v1beta2.Kyma{},
				handler.OnlyControllerOwner()), builder.WithPredicates(predicate.ResourceVersionChangedPredicate{})).
		WatchesRawSource(source.Channel(runnableListener.ReceivedEvents, r.skrEventHandler())).
		Complete(r); err != nil {
		return fmt.Errorf("failed to setup manager for kyma controller: %w", err)
	}
	return nil
}

Acceptance Criteria:

[ ] Implement the new watch mechanism for ModuleReleaseMeta CRs.
[ ] Create a follow up to remove the ModuleTemplate watch mechanism and replace it completely with a new one.
[ ] Current watch mechanism should stay but it should be reduced to scope in only the ModuleTemplates that have a channel assigned
[ ] Reconcile corresponding Kyma CRs:

Reconcile all Kymas that have modules enabled via the specified channel when a ModuleReleaseMeta CR is created, updated, or deleted.
Ensure Kymas with a specific version assigned (not tied to a channel) are not requeued.

[ ] Cover the functionality with tests to ensure that the watch mechanism and requeue logic work correctly.
[ ] Update affected documentation

Follow-Up:

https://github.com/kyma-project/lifecycle-manager/issues/1955

repo: kyma-project/lifecycle-manager


text:
chore: Bump e2e CM version to align with prod

Description
Changes proposed in this pull request:

e2e test suite should run with the same version from landscapes

Related issue(s)

LGTM, should we re-run the failed tests? Both seem to be flaky and I assume not directly related to this change.

LGTM, should we re-run the failed tests? Both seem to be flaky and I assume not directly related to this change.

Yes, Given SKR Cluster Then Module CR and Manifest CR are removed is very flakey recently. Very annoying.
We have an issue ready to be picked up.

authors: c-pius lindnerby


text:
Remove hardcoding of kymata-toolbox directory in submit_gridsearch.sh

@caiw  tried to fix it with
# This gets the directory of the toolbox, assuming that *this file you're reading right now* is in the root directory of
# the toolbox
TOOLBOX_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )

but we get this
'/usr/bin/bash: line 1: cd: /var/spool/slurm/job3347806: No such file or directory'

So I put it back to hardcoded. It must be that the SLURM thinks it is in '/var/spool/slurm/job3347806' when it runs...

Fixed by #418

repo: kymata-atlas/kymata-core


text:
🛑 senoshaidodelasmanos.love is down

In beb0dcd, senoshaidodelasmanos.love (https://senoshaidodelasmanos.love) was down:

HTTP code: 0
Response time: 0 ms

Resolved: senoshaidodelasmanos.love is back up in 563baaf after 568 days, 10 hours, 2 minutes.

repo: kyryl-bogach/upptime


text:
Any update for new versions of firebaseui?

With new version Firebase, Firebase ui and angular 13 i'm getting multiple errors.
Error: export 'default' (imported as 'firebaseOriginal') was not found in 'firebase/app'
Error: export 'ɵfirebaseAppFactory' (imported as 'ɵfirebaseAppFactory') was not found in '@angular/fire'
error TS2305: Module '"@angular/fire/auth"' has no exported member 'AngularFireAuth'.

Hi @nikolas-nelson,
I've just released two new versions: the first one can be used with Angular 12, while the second release supports Angular 13.
Note that both of them require Firebase 9.
Since you are using Angular 13, make sure to install these dependencies:

Angular
Firebase
AngularFire
FirebaseUI
firebaseui-angular-i18n

13.0.0
^9.3.0
^7.1.1
^6.0.0
6.1.0

Once you do that, you should be good to go.
Please let me know if it worked so that I can close this issue :)

Hi, now it works great, thx for quick fix.


text:
Error: Invalid print parameters: scale is outside of [0.1 - 2] range

Hello,
I choose 100 downscale percent and try to export. However, I get the error in the title.

It seems that there is no problem with the parameters. Restart Obsidian to see if the problem still exists?

It seems that there is no problem with the parameters. Restart Obsidian to see if the problem still exists?

Restarting Obsidian helped. That's very weird. Thanks a lot!


text:
Suppressible checks resolving, Consistent naming

closes #127

PR-Codex overview
This PR focuses on renaming the ru.l3r8y.rule package to ru.l3r8y.checks.
Detailed summary

Renamed ru.l3r8y.rule package to ru.l3r8y.checks
Renamed ru.l3r8y.Rule interface to ru.l3r8y.Check interface
Updated imports and references to reflect the package and interface name changes

The following files were skipped due to too many changes: src/main/java/ru/l3r8y/rule/MethodChangesState.java, src/main/java/ru/l3r8y/ValidateMojo.java, src/main/java/ru/l3r8y/rule/AssigmentCheck.java, src/main/java/ru/l3r8y/checks/ClassCanSuppress.java, src/test/java/ru/l3r8y/checks/ClassCanSuppressTest.java, src/test/java/ru/l3r8y/rule/MethodChangesStateTest.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (64d72cd) 80.64% compared to head (b2d622f) 80.85%.

Files
Patch %
Lines

src/main/java/ru/l3r8y/ValidateMojo.java
0.00%
1 Missing :warning:

...rc/main/java/ru/l3r8y/checks/ClassCanSuppress.java
83.33%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master     #131      +/-   ##
============================================
+ Coverage     80.64%   80.85%   +0.21%
- Complexity       85       87       +2
============================================
  Files            23       24       +1
  Lines           248      256       +8
  Branches         10       10
============================================
+ Hits            200      207       +7
- Misses           42       43       +1
  Partials          6        6

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

@l3r8yJ please review this Pull Request. Deadline (when it should be merged or closed) is 2024-01-12T12:30:27.665550.
You should check if the requirements have been implemented (partially or in full), if there are unit tests covering the changes and if the CI build passes. Feel free to reject the PR or ask for changes if it's too big or not clear enough.
Estimation here is 30 minutes, that's how much you will be paid. You will be paid even if this PR gets rejected.

@rultor merge

@rultor merge

@l3r8yj OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@l3r8yj Done! FYI, the full log is here (took me 2min)

@l3r8yJ thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


text:
JPMS改造

Java 9引入了Java平台模块系统。计划对项目进行相关改造

当下完成了依赖模块的改造（未完全验证）。启动模块可能要待Spring 6.x、Spring Boot 3.x发布前后，有相关解决方案了才进行

相关方案，估计到下半年了

主体不在Spring，而是依赖中有一些非module的

主体不在Spring上。启动报错是因为部分依赖无法模块化，编译时有相关警告 can't extract module name from xxx.jar: Provider class xxx not int module。具体原因 暂未找到解决方案

通过idea启动正常，jar方式后续

repo: lWoHvYe/eladmin


text:
[Button Group] Rename Button Group to Content Switch

Rename Button Group to Content Switch so it equalizes Figma and Bold website to Storybook.

The ButtonGroup component is actually just a building block for building the content switch. There might exist scenarios where we need a ButtonGroup but without the content switching functionality.
So what we could do here is create a ContentSwitch component providing this functionality that currently ButtonGroup doesn't provide.

authors: CarlosBonetti laiseing

repo: laboratoriobridge/bold


text:
Studying "I ADOPTED A KITTEN!!!"

https://www.youtube.com/watch?v=2-bFB6_iOCQ

Dictation
Hey guys.
I am in the car and I am on the way to get a kitten.
Someone I know from high school is giving away their kittens and I am going to go check them out if they are health and if they look like well-taken care. Then I will bring one home.
But we don't have anything for the cat yet. So first we're going to go Pet Smart and then buy the littele box.. the food and bed and everything like that.
So cute. Oh my gosh. Hi. So cute.
Ok. We just picked out our kitten. Oh my gosh.
It's a girl. We didnt' know if we wanted a boy or a girl.
I am a little bit allergic to cats and I already got hives on right hand. Yeap. That's a hive.

hives: 두드러기 (note: hive 는 벌집))

Meaw.
Oh my gosh. Just probably scared. It's a really bumpy road. Hey, you tried to peek your head out of your littel cage? You're so cute.

peek your head

머리를 들고 보다?? (확실치 않음)
the craziest idea of a secret agent spy going on a mission to peek his head out of a toilet
Peek your head out and see what's going on
peek your head out one more time!

TBD: From https://youtu.be/2-bFB6_iOCQ?t=86

Dictation (From https://youtu.be/2-bFB6_iOCQ?t=86_)
OK, we just got home. We bought the can, a little bed and a scratcher toy and some food, it doesn't eat hard food yet but it will in a few.

a few
A short period of time
Hey, I'll be back in a few, so start making dinner now.

We got some canned food, let's see.
We have to buy, you know like, everying from scratch because we don't own any pets.

If you do something from scratch, you do it without making use of anything that has been done before.

This is for the food, this is for the water.
It matches. We got the matching set. This your litter box we got.

She just came out of her cage.
This is the first time in her new home.
She has stripes like a tiger. We should call her tigress.
Tiger lily, oh my gosh, _____________

TIGRESS is a female tiger

Shouly we call her tiger lily? She's so small.... she's like so small.

TBD : Dictation (from https://youtu.be/2-bFB6_iOCQ)

Dictation (from https://youtu.be/2-bFB6_iOCQ?t=253)

Dictation (from https://youtu.be/2-bFB6_iOCQ?t=289)
So the second question that was asked was why did I get the kitten in ~for~ the first place because everybody knows i am a dog person.
And it's because I couldn't ~cannot~ have a dog. My landlord would not let me get a dog because our apartment was newly renovated. She didn't ~doesn't~ want the wear and tear on her new appliances, doors, wall, anything like that.
So I can't have a dog. I really wanted to have Australian Shepherd ~Sheppard~ but it's just not in the cards.

in the cards: likely to happen:

Marriage isn't in the cards for me right now – I'm focused on my career.
Note: Used especially in negative sentences.

Now, kittens, I have no idea that they're just as high maintenance as a dog.

high-maintenance: adj.

needing frequent or major maintenance or repair:

Imported sports cars are high-maintenance.

Informal. (of a person) demanding a great deal of attention, money, or effort:

His high-maintenance girlfriend refuses to get engaged without a big diamond ring.

The reason I wanted a kitten in the first place was because I thouht that they are ~are~ aloof, I thouht that they were ~are~ independent, I thought that they play ~play~ by themselves, I thought that they just lay their ~eat~ food out and they just eat it whenever..

aloof

adj, distant either physically or emotionally

an aloof, unfriendly manner

adv, at a distance

trying to keep failure aloof

No No I had no idea that cats were ~need~ so high maintenance.
(TBD: https://youtu.be/2-bFB6_iOCQ?t=340)

Dictation (from https://youtu.be/2-bFB6_iOCQ?t=340)
Kittens are like new born babies. They always want your attention.
I can't even walk outside in my room without their mewing, looking for me. She always wants to be by me 24/7.
She usually sleeps right on my neck, on my boob, on my shoulder, on my head, on my side, like tucked under.

tuck: to put something in a particular place, especially in order to keep it safe or hidden.

So this is her hugging my face while falling asleep. She's so sweeet and affectionate. I am really happy that I got her as a furry ~free~ friend.

furry: covered with fur

The last question that was asked was that what is her breed.
Shel's a brown tabby ~hairy~ cat and her breed comes from a line of leopards.
And then what is her age. She is six weeks old.

tabby cat: a domestic cat with a striped and mottled coat
mottled: 얼룩덜루한

I will make sure to do an ~doing~ updte on her when she gets older. But that's all for now.
Thank you guys for watching, like, and subscribe. Bye.

Questions for discussion

Why does she get a kitten instead of a dog?
What does the cat look like?
What change happen to her life since she got the kitten?
What did she prepare to live with the kitten?

repo: labsurde-life/english


text:
Add tags to IAM Role

Issue: Add tags to IAM Role
Description:
Adding the user provided tags to the IAM role created by this terraform module
Additional Info:
N/A

@afiune - Anything else required from my side? Thanks.

make it so

make it so

@rajgandhi9 I don't think you added the tags argument in the right resource. 🤔
Could you double-check, please?

repo: lacework/terraform-aws-ecr


text:
v1.1.8

#495 - auto scale iframe
#499 - use names in links
#510 - fix print view
#503 - fix superleague tons
#505 - multiple date filter support

Pull Request Test Coverage Report for Build 5569969865

33 of 33 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 95.081%

Totals

Change from base Build 5543352771:
-0.006%

Covered Lines:
6676

Relevant Lines:
6795

💛  - Coveralls

authors: coveralls laingsimon


text:
Investigate Rollbar Error 56 - undefined class

https://rollbar.com/lale-help/lale-help/items/56/

the problem clearly are those complex objects which gets passed into sidekiq and then the deserialization fails on wrong nesting of class constants.
the implementation does not follow the recommendation from sidekiq:
https://github.com/mperham/sidekiq/wiki/Delayed-extensions#actionmailer
It is recommended to avoid passing an object instance to mailer methods. Instead, pass an object id and then re-instantiate the object in the mailer method
there are not to many places where the delay is used on Mailer classes, could be switched easily to do the right thing.

@mkristian That would be an excellent solution. We were never happy with the short term fix of just using delay and serializing the entire object. Let me know if you can fix this for us...

I can fix it easily but code becomes less object-oriented like
TaskMailer.delay.task_reminder(task, user, token) will become TaskMailer.delay.task_reminder(task.id, user.id, token.code) so sidekiq needs to serialize only primitives.
probably OK as you want all emails sent out asynchronously

Works for me...

authors: dottorer mkristian

repo: lale-help/lale-help

license: mit


text:
Repo cloned but cannot build it

Hi,
Could you help please.
Repo has been cloned in my user folder.
Your line of command is not working, why ? thanks

Is this repo still working right with telegram ?

repo: laliux/telegram-crypto-signals


text:
update makefile

Closes #9
This Pr adds steps in makefile to compile the project

Looks good, but let's merge #10 first and adapt it here.

✅ I was able to check that make setup works in a recently cloned repo.
TODO  I haven't tested the make run command yet. Let me check that.

The code looks good to me. I would like to propose some improvements, which I can provide in another PR if you like.

WAIT
I tried to run calling make run first instead the era-test-node instance that I have running in the background at all times. This failed because it required to run make setup first, which depends on having the era-test-node running.
I'm going to make a PR pointing to this one with my suggested solution.

authors: daphneherlambda fkrause98 jpcenteno


text:
🍱 DFolder.get_dobject

Write _objectkey to .dobjects from DFolder
Implemented DFolder.get_dobject(relpath)

Thanks you, left some minor comments.

Great work, Sunny! Great comments, Sergei! I'll do the small fixes as suggested by Sergei so that this can be merged.

authors: Koncopd falexwolf sunnyosun

repo: laminlabs/lamindb


text:
Clear neopixels on startup.

Without it, I was getting the pixel 0 in blinding green color. This is only for C++, not used by PXT.

LGTM, I'll merge and it will be included in the next tag, whenever that may be...

authors: jamesadevine mmoskal


text:
feat: expose underlying dataset uri of the table

We frequently need to recover this uri so exposing it to make it easy

Yeah we def want to start supporting all of these. Just unblocking for the time being will create a ticket

repo: lancedb/lancedb


text:
Landbook Promoted Thematic feature

this have/create bad dependencies to CT event.
it shows up in the teaser view of the thematic narratives

fixed in new version (new promoted module)

repo: landportal/drupal


text:
🛑 vipgifts.net is down

In 89bfc84, vipgifts.net (https://vipgifts.net) was down:

HTTP code: 567
Response time: 845 ms

Resolved: vipgifts.net is back up in 69f725c after 22 minutes.

repo: lanen/bs-site


text:
🛑 vipgifts.net is down

In 85eec05, vipgifts.net (https://vipgifts.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: vipgifts.net is back up in 1ba9319.


text:
🛑 vipgifts.net is down

In 9a22939, vipgifts.net (https://vipgifts.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: vipgifts.net is back up in f9a8cf2.


text:
🛑 vipgifts.net is down

In 97f204a, vipgifts.net (https://vipgifts.net) was down:

HTTP code: 567
Response time: 328 ms

Resolved: vipgifts.net is back up in 6bf4e3f after 41 minutes.


text:
🛑 rexingsports.cn is down

In d0de290, rexingsports.cn (https://www.rexingsports.cn) was down:

HTTP code: 567
Response time: 1026 ms

Resolved: rexingsports.cn is back up in 6734b07 after 13 minutes.


text:
Issue: Continue from a saved checkpoint

Issue you'd like to raise.
I am looking for help to continue langchain Refine chain from a saved checkpoint. None of my code got completed because of GPT API overload. Any help would be appreciated.
Suggestion:
No response

I am curious how people process long texts using chains. As currently, those chains can't be finished because of GPT overload.

repo: langchain-ai/langchain


text:
Adds an in-memory implementation of RecordManager

Description:
langchain offers three technologies to save data:

vectorstore
docstore
record manager

If you want to combine these technologies in a sample persistence stategy you need a common implementation for each. DocStore propose InMemoryDocstore.
We propose the class MemoryRecordManager to complete the system.
This is the prelude to another full-request, which needs a consistent combination of persistence components.
Tag maintainer:
@baskaryan
Twitter handle:
@pprados

No. All is async, because all method works in memories.

@hwchase17
Some news ?

@baskaryan
I resynchronize the code for langchain-community version 0.0.14

@eyurtsev @hwchase17
Hello,
Can you reconsider this PR?

@eyurtsev
I rewrite the tests to be compatible with the same tests with SQLRecordManager.

@eyurtsev
Can you check this ?

@eyurtsev
I can result this bug.
with
git checkout master
cd /libs/core
poetry lock --no-update
Resolving dependencies... (0.0s)

Because langchain-core depends on langchain-text-splitters (0.2.1) @ file:///home/pprados/workspace.bda/langchain/libs/text-splitters which depends on langchain-core (^0.2.0), langchain-core is required.
So, because langchain-core is 0.0.0a64, version solving failed.

@eyurtsev
In the test CI /cd libs/core / make extended_tests, I receive an error:
INTERNALERROR>     raise Failed(msg=reason, pytrace=pytrace)
INTERNALERROR> Failed: Package `aiosqlite` is not installed but is required for extended tests. Please install the given package and try again.

It has nothing to do with my patch

@pprados please review
I reused the existing implementation of the in memory record manager from unit tests.

data is scoped to the instance not to the class (we generally don't want to scope data to the class namespace)
has slightly more documentation

It's moved to base.py together with the abstract interface. We can move it into a separate module as well (doesn't really matter), we just need it to be a non private module for it to appear in the API Reference documentation.
The typical name for memory implementations is "InMemory"

@eyurtsev
It's perfect for me.

authors: eyurtsev pprados


text:
No response when using the "Ask Open Canvas" feature for editing.

When using the "Ask Open Canvas" feature to request changes in the document editor, there is no response returned by the system. The issue persists even after attempting to make further changes via the chat interface.
Steps to Reproduce:

Open the document editing interface.
Request a change to a highlighted section using the "Ask Open Canvas" button.
Observe that no response is given by the system.
Attempt to make additional requests using the chat input field.
Notice that still no response is provided.

Expected Behavior:
The system should provide a response to the user's request, either allowing edits or providing guidance, similar to the cloud version.
Observed Behavior:

No response is given when using "Ask Open Canvas".
No response is provided even after repeated requests via the chat.

Environment:

Version: Local server (localhost:3000)
Document Title: "Whispers of the Sea"
Specific section attempted for edit: The final paragraph, highlighted in blue.

Screenshots:
(Attach the provided screenshot showing the issue)
Additional Information:
This issue does not occur in the cloud version, where the requested edits are processed successfully.
Severity:
High - Blocks editing functionality, disrupting user workflow.
Potential Cause:

The issue may be related to differences in the backend processing logic between the local and cloud environments.

Suggested Label:

Bug
Editing Functionality

This detail for errors:
langgraph-api-1       | FAILED TO GENERATE TOOL CALL {
langgraph-api-1       |   styleRules: [
langgraph-api-1       |     'Use clear and concise language to explain complex concepts, ensuring accessibility for a broad audience.',
langgraph-api-1       |     'Structure written content with clear headings and subheadings to enhance readability and organization.',
langgraph-api-1       |     'Incorporate historical context and practical applications to provide depth and relevance to the topic being discussed.'
langgraph-api-1       |   ],
langgraph-api-1       |   content: [
langgraph-api-1       |     'The user is interested in writing articles, particularly on technical subjects like Design of Experiments (DoE).',
langgraph-api-1       |     "The user values detailed and thorough explanations, as indicated by their request to 'chi tiết hoá' (detail) the article.",
langgraph-api-1       |     'The user is open to further adjustments and additional information regarding the content they are working on.'
langgraph-api-1       |   ]
langgraph-api-1       | }
langgraph-api-1       | Error: Reflection tool call failed.
langgraph-api-1       |     at RunnableLambda.reflect (/Volumes/DATA/open-canvas-main/src/agent/reflection/index.ts:80:11)
langgraph-api-1       |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
langgraph-api-1       |     at async /Volumes/DATA/open-canvas-main/node_modules/@langchain/core/dist/runnables/base.cjs:1531:34 {
langgraph-api-1       |   pregelTaskId: '15c3f8ee-7a7e-5ec3-96c7-3dddfb405f73'
langgraph-api-1       | }

@sonnt-dna that's the reflection graph, which is not blocking the open canvas graph from executing. I also made a change sometime next week which should mitigate those errors in the reflection graph. I'm going to close this issue now, please ping me if you encounter another error.

authors: bracesproul sonnt-dna

repo: langchain-ai/open-canvas


text:
[FEATURE] Retry option and augmented resilience in output parsing for AiServices

For AiServices returning java objects other than String, there is always a certain risk that the model doesn't entirely return the expected format, resulting in conversion errors when the framework tries to parse the result.
Two proposals to make this a bit more resilient:

Trim the answer in a smart way, eg. in case of JSON parsing, cut off everything before the first { and after the last }. Models like to add some unwanted things before and after the real answer, smart trimming would solve this issue that happens relatively often.
Add a 'numberOfRetries' options for AiServices, that will make new call(s) to the model if the parsing failed, in the hope the new answer is parsable.

A third idea is to allow the user to provide a method String curate(String modelOutput) to do some pre-trimming or curation of the direct model output themselves, after which the curated answer is parsed by LangChain4j (eg. cutting of numbers when asking for List, in case the model numbered the  items). Possibly this curation can also be done on the returned java object afterwards, but I can imagine that there are cases where the user observes a specific type of wrong answer appearing often, that is easy to intercept in code. The curate method could also throw an error in that case, which would 'reject' the model answer, and trigger a retry, just like a parsing error would (if this functionality will be implemented).

Hi @LizeRaes thank you!
This is a duplicate of https://github.com/langchain4j/langchain4j/issues/859 and https://github.com/langchain4j/langchain4j/issues/968.
I will close this issue and link it to those two.


text:
feat(component): API Request Component Overhaul

Changes in API Request Component:
Major Changes:

Input Structure:

Removed cURL input field
Changed NestedDictInput to TableInput for headers and body
Added table schema definitions for better structure
Modified method dropdown to have empty default value

Build Config:

Removed parse_curl method and related functionality
Simplified update_build_config to only handle method changes
Added body visibility toggle based on HTTP method

Code Formatting:

Improved line breaks and indentation
Split long lines for better readability
Added default_keys list

Minor Changes:

TableInput:

Added ToolModeMixin to TableInput class
Enhanced table schema with key/value pairs
Added descriptions for table fields

UI/UX:

Made timeout and headers advanced options
Added real_time_refresh to method dropdown
Improved description texts

Code Cleanup:

Removed print statement in add_query_params
Improved error message formatting
Enhanced code documentation

Technical Details:

Modified input types for better type safety
Enhanced error handling
Improved code organization
Added tool mode support for table inputs

Thanks @Vigtu ! One other thing.  i see a change to the Vector Store RAG template in here (check if there's any others) i dont think thats required for this PR, right?

Thanks @Vigtu ! One other thing. i see a change to the Vector Store RAG template in here (check if there's any others) i dont think thats required for this PR, right?

You are absolutely right; the Langflow repository loads all templates as staged changes, and unfortunately, this one slipped past my attention. I mistakenly included an incorrect item in the commit and had to fix it.

I'm not sure removing the curl parsing is a good idea.

I'll work on making the curl mode more user-friendly, as I found it quite confusing in its current form. Instead of implementing it as a separate component, I'll try to integrate it into the API request component in a way that feels more intuitive for the user.

FE tests fixed!

authors: Cristhianzl Vigtu erichare

repo: langflow-ai/langflow


text:
闪退

一填cookie就闪退，太难了，不知道怎么解决，大佬还更新吗

一填cookie就闪退，太难了，不知道怎么解决，大佬还更新吗

现在知苗cookie怎么获取啊

一填cookie就闪退，太难了，不知道怎么解决，大佬还更新吗

现在知苗cookie怎么获取啊

抓包啊

repo: lanomw/qt-zmyy


text:
Error: Our systems have detected unusual activity coming from your system. Please try again later.

大佬，好像总是触发这个报错：是IP的问题吗？还是账号的问题
Error: Our systems have detected unusual activity coming from your system. Please try again later.

我也是，请问你解决了吗？

没彻底解决偶尔会这样，我把重试的次数加多了，目前还行


text:
Future compatibility warning for winapi 0.2.8

warning: the following packages contain code that will be rejected by a future version of Rust: winapi v0.2.8 started appearing in rustc 1.62.0 nightly.

Just wanted to mention that this warning is also appearing on the stable branch, and I'm wondering what part exactly is the cause here.

I think it is most likely due to mio https://github.com/lapce/lapce/blob/81c47869bc4a8846ece08ee76cceb6fa3006a80d/lapce-proxy/Cargo.toml#L22 which is using very old winapi v0.2.8 (even latest update of winapi v0.3.9 is 2 years old but used by many important projects) , upstream of mio has moved to windows-rs (made by Microsoft), which many rust projects are moving to or already moved (winit recently moved)

Fixed since we updated alacritty

authors: Diapolo10 bugadani ghishadow panekj

repo: lapce/lapce


text:
Cannot declare class

Info:

Docker version ($ docker --version): 18.09.1, build 4c52b90
Laradock commit ($ git rev-parse HEAD): 50b6272ffffd0f75b6b8af81d842542c96dc8182
System info (Mac, PC, Linux): Linux
System info disto/version: Debian 10

Issue:
I have several installations of XenForo (different projects). All have exact same version and own databases. But there are an issue with php. If i restart php-fpm and then go to forum #1 it works but then forums #2 and #3 not works. Again if i restart php-fpm and then go to forum #2 (for example) it works but then forums #1 and #3 not works.
PHP log gives an error:
Cannot declare class "CLASS_NAME" because the name is already in use

@0xbadc0de I got that the projects are different, but what about DATA_PATH_HOST in .env files?

Issue resolved by disabling PHP OPcache

repo: laradock/laradock


text:
Fixed pecl redis, PHP <= 7.3 removed

Description
PECL Redis 6.1.0 removed PHP <= 7.3
https://pecl.php.net/package-info.php?package=redis&version=6.1.0
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue).
[] New feature (non-breaking change which adds functionality).
[] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Definition of Done Checklist:

[x] I've read the Contribution Guide.
[] I've updated the documentation. (refer to this for how to do so).
[x] I enjoyed my time contributing and making developer's life easier :)

@bestlong hi, ping :), this PR fix tests

@bestlong hi, ping :), this PR fix tests


text:
Updating webroots to have the same defaults

Caddy, NGINX and Apache2 should have the same default application paths. The public/ path suffix is now added in the dotenv file to be able to use Laradock for non-laravel projects as well. Also, updated the documentation.
This should fix issue #849.
Update: I can't spell today. Apologies for changing the title two times. 🔢

@winfried-van-loon Can you please address the (new) merge conflicts?  I will get this merged as soon as it is clean :-)

authors: mikeerickson winfried-van-loon


text:
Allow HTML for notification messages

This would allow us to put links or a bit of formatting inside the message. For example, a link to a downloaded file.

If we do this, we should probably change the surrounding <p> tag to a <div>, so it's a little more semantic. Thoughts?

You are right. Totally missed that.

Is there any chance of an XSS from allowing HTML like this?

Is there any chance of an XSS from allowing HTML like this?

Since the HTML comes from Filament or plugins I don't see much risk here. Only if stuff gets injectected into the session data, but I guess you have other issues then 😅

I'm thinking, if people put the name of the record in the notification from user input, then it could be vulnerable.
If we allow markdown instead with Str::markdown(), does that strip dangerous HTML for us?

If we allow markdown instead with Str::markdown(), does that strip dangerous HTML for us?

Yes, I just tested that earlier this week, whether it's save to {!! Str::markdown($userInput) !!}. The result was that things like <iframes> were stripped, but normal Markdown was rendered correctly.

Great, lets do that @pxlrbt @ryangjchandler ?

I wrapped the notification messages inside Str::markdown(). As a side effect the message is wrapped in -Tags but I don't think that's an issue as we don't have any general styling.

authors: danharrin pxlrbt ralphjsmit ryangjchandler

repo: laravel-filament/filament


text:
Add observers to FiresCallbacks

Is your feature request related to a problem? Please describe.
We have no way to abstract callback and extension logic into dedicated classes.
Describe the solution you'd like
Something like this: Callable::observe(Observer::class); would work. We don't need to worry about colliding with Eloquent I don't think.

This is in place already.

repo: laravel-streams/streams


text:
SubscriptionBuilder::newSubscription() does not support specifying an existing payment method

At the moment, creating a new subscription with Cashier via SubscriptionBuilder::newSubscription() accepts a token. If you do not provide a token, the subscription will be created with the default source set on the customer.
It would be helpful if Cashier's newSubscription method accepted a source_id. That would allow me to specify a payment method that is not the customer's default payment method. In my application, customers may add multiple payment methods, and have multiple subscriptions.
It is realistic to assume that enterprise customers will be using multiple payment methods in my use case. Making new subscriptions from my marketplace will allow users to choose which of their payment methods they would like to use.
I may be able to code something up here soon, but I wanted to add the issue as an enhancement in case I don't get around to it.

The new cashier version will make use of payment methods. It'll now be possible to choose a different card payment method for the subscription creator. This will then be the default payment method for that subscription.
At the moment this only allows for cards but later payment methods will also support banks.

authors: ColinLaws driesvints

repo: laravel/cashier


text:
orWhereHas() requires Closure as an argument

Laravel Version: 5.3.30
PHP Version: 7.0
Database Driver & Version: MySQL 5.7.16

Description:
I'm not sure why orWhereHas() requires Closure as an argument when whereHas() doesn't.
It seems consistent. If there is no argument passed this error is thrown:
TypeError: Argument 2 passed to Illuminate\Database\Eloquent\Builder::orWhereHas() must be an instance of Closure, none given on line 3
You can easily circumvent the issue by putting an empty Closure in:
Model::whereHas('thing)->orWhereHas('other_thing', function($query){})->get();
Is that the desired behaviour?
Steps To Reproduce:
Perform an Eloquent query on a model which has at least two relations. Get a collection of models that has either one relationship or the other using:
Model::whereHas('thing')->orWhereHas('other_thing')->get()
This will result in an error:
TypeError: Argument 2 passed to Illuminate\Database\Eloquent\Builder::orWhereHas() must be an instance of Closure, none given on line 3

Moving the discussion to the PR. Thank you!

authors: Kwapi themsaid

repo: laravel/framework


text:
Column not selected in get([columns]) if placed first in the array

Laravel Version: 5.6.29
PHP Version: 7.2
Database Driver & Version: Mysql 5.7.21

Description:
Calling get([columns]) on a model with global scope and specifying some columns leaves one of those columns out in the results. However, changing the order of the columns returns the correct results.
Steps To Reproduce:
I have a simple eloquent model that extends another model and just adds a global scope. I am running the following in tinker one after another.
Notice how the slug value is returned in the first call, but not in the second.
>>> MemberSettingKey::get(['default_value', 'value', 'slug']);
=> Illuminate\Database\Eloquent\Collection {#3574
     all: [
       App\Models\MemberSettingKey {#3585
         default_value: "en-US",
         value: "en-US",
         slug: "locale",
       },
       App\Models\MemberSettingKey {#3595
         default_value: "USD",
         value: "USD",
         slug: "currency",
       },
     ],
   }
>>> MemberSettingKey::get(['slug', 'default_value', 'value']);
=> Illuminate\Database\Eloquent\Collection {#318
     all: [
       App\Models\MemberSettingKey {#327
         default_value: "en-US",
         value: "en-US",
       },
       App\Models\MemberSettingKey {#328
         default_value: "USD",
         value: "USD",
       },
     ],
   }

Funnily, adding a fourth column to the first query does include both slug and the new column in the results:
>>> MemberSettingKey::get(['slug', 'default_value', 'value', 'milestone_id']);
[!] Aliasing 'MemberSettingKey' to 'App\Models\MemberSettingKey' for this Tinker session.
=> Illuminate\Database\Eloquent\Collection {#3535
     all: [
       App\Models\MemberSettingKey {#3554
         slug: "locale",
         default_value: "en-US",
         value: "en-US",
         milestone_id: null,
       },
       App\Models\MemberSettingKey {#3555
         slug: "currency",
         default_value: "USD",
         value: "USD",
         milestone_id: null,
       },
     ],
   }

Unable to reproduce. We'll probably need some more information here, such as the relevant migration and model code.
At the very least we'll need to know exactly what your global scope is doing.

@36864
Migration for table:
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class CreateSettingKeysTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('setting_keys', function (Blueprint $table) {
            $table->increments('id');
            $table->unsignedInteger('setting_group_id');
            $table->unsignedInteger('milestone_id')->nullable();
            $table->string('slug');
            $table->string('default_value');
            $table->string('value');
            $table->timestamps();

            $table->foreign('setting_group_id')->references('id')->on('setting_groups');
            $table->foreign('milestone_id')->references('id')->on('milestones');
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::dropIfExists('setting_keys');
    }
}

Base model code:
<?php

namespace App\Models;

class SettingKey extends BaseTenantModel
{
    /**
     * @inheritDoc
     */
    protected $guarded = [];

    /**
     * Get all of the settings for this key.
     *
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function settings()
    {
        return $this->hasMany(
            Setting::class, 'setting_key_id', 'id'
        );
    }

    /**
     * Get the setting group for this key.
     *
     * @return \Illuminate\Database\Eloquent\Relations\BelongsTo
     */
    public function group()
    {
        return $this->belongsTo(
            SettingGroup::class, 'setting_group_id', 'id'
        );
    }

    /**
     * Get the milestone for this key.
     *
     * @return \Illuminate\Database\Eloquent\Relations\BelongsTo
     */
    public function milestone()
    {
        return $this->belongsTo(
            Milestone::class, 'milestone_id', 'id'
        );
    }
}

Extended model with global scope:
<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Builder;

class MemberSettingKey extends SettingKey
{
    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = ['value'];

    /**
     * @inheritdoc
     */
    protected $table = 'setting_keys';

    protected static function boot()
    {
        parent::boot();

        static::addGlobalScope('memberSettings', function (Builder $builder) {
            $builder->whereHas('group', function ($query) {
                $query->where('name', 'member');
            });
        });
    }
}

Removing the default_value column from the get() also allows the selection of slug:
>>> MemberSettingKey::get(['slug', 'default_value', 'value']);
=> Illuminate\Database\Eloquent\Collection {#320
     all: [
       App\Models\MemberSettingKey {#329
         default_value: "en-US",
         value: "en-US",
       },
       App\Models\MemberSettingKey {#330
         default_value: "USD",
         value: "USD",
       },
     ],
   }
>>> MemberSettingKey::get(['slug', 'value']);
=> Illuminate\Database\Eloquent\Collection {#3553
     all: [
       App\Models\MemberSettingKey {#3557
         slug: "locale",
         value: "en-US",
       },
       App\Models\MemberSettingKey {#3558
         slug: "currency",
         value: "USD",
       },
     ],
   }
>>>

P.S. I'm now updated to laravel 5.6.29

I used a basic SettingGroup model with just the id and name fields to test this. Still unable to replicate:
>>> MemberSettingKey::get(['slug', 'default_value', 'value']);
=> Illuminate\Database\Eloquent\Collection {#2870
     all: [
       App\MemberSettingKey {#2880
         slug: "locale",
         default_value: "en-US",
         value: "en-US",
       },
       App\MemberSettingKey {#2883
         slug: "currency",
         default_value: "USD",
         value: "USD",
       },
     ],
   }
>>> MemberSettingKey::get(['default_value', 'slug', 'value']);
=> Illuminate\Database\Eloquent\Collection {#2878
     all: [
       App\MemberSettingKey {#2884
         default_value: "en-US",
         slug: "locale",
         value: "en-US",
       },
       App\MemberSettingKey {#2885
         default_value: "USD",
         slug: "currency",
         value: "USD",
       },
     ],
   }
>>>

Are you able to dump out the sql queries being executed, using debugbar for example?

@36864 Miraculously, it is working now. I swear I haven't changed anything. I have been running artisan cache:clear and artisan config:cache and switching the cache driver from file to array and back to file. Not sure if that fixed it but can't reproduce the error anymore.
Doesn't work for our front-end dev though running on the same codebase, same composer.lock, so will have to leave slug in the end of the get() for now. Can't debug at the moment.
Closing this for now. Thanks for your help.
P.S. Back-end is an api so not sure how to run debugbar there. Will have to figure out how to do that at some point :)

For back-end sql dumping, I like https://github.com/mnabialek/laravel-sql-logger
Times like these I like to blame the OPCache. Try clearing that if it's enabled.


text:
IAM Database Authentication for RDS mySQL

Hi there,
We have security issues, which means we been storing RDS databases user name and passwords on .env file and security team have forced us to remove those, does larvel supports IAM authentications on AWS : URL:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html

???

Hi there,
Welcome to Laravel and we are glad to have you as part of the community.
Unfortunately this GitHub area is not a support area for general application issues. This is only for issues/bugs with the framework code itself.
I will be closing your ticket here. Instead please try asking your question on one of the many great community support areas that will likely give you a better answer more quickly:

Laravel Slack (https://larachat.co/)
Laravel.io Forum (https://laravel.io/forum)
Laracasts Forum (https://laracasts.com/discuss)
StackOverflow (http://stackoverflow.com/questions/tagged/laravel)

If you feel I've closed this issue in error, please provide more information about how this is a framework issue, and I'll reopen the ticket.
Thanks in advance.

but those are security issues mate?

Are you using an env file in production? If so, that is the security issue. The issues section here is specifically for reporting bugs in the framework.
To understand how to more securely store your credentials, it is better to reach out to one of the great laravel communities that are available.

Yes I am using for production, security is a bit worry, even uploading images to s3 needs keys, rather then roles..
From: Clayton Stone notifications@github.com
Reply-To: laravel/framework reply@reply.github.com
Date: Thursday, 4 April 2019 at 10:38
To: laravel/framework framework@noreply.github.com
Cc: ilirkodra ilirkodra@hotmail.com, Author author@noreply.github.com
Subject: Re: [laravel/framework] IAM Database Authentication for RDS mySQL (#28097)
Are you using an env file in production? If so, that is the security issue. The issues section here is specifically for reporting bugs in the framework.
To understand how to more securely store your credentials, it is better to reach out to one of the great laravel communities that are available.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flaravel%2Fframework%2Fissues%2F28097%23issuecomment-479825801&data=02|01||709cf7875a4641a9b0d108d6b8e13aea|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636899674819515299&sdata=RDrTS3ROfwCx%2BEkEWV7t0rAJPqnL6ZSS4WdPddGWE5I%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABp6OYlmVGXFaBesnspZbB30pk5hCz_3ks5vdcf3gaJpZM4caMXA&data=02|01||709cf7875a4641a9b0d108d6b8e13aea|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636899674819525308&sdata=FrF0VcezkpmjfSf8JlyMVT8cvimMxOKK7uSJOnEwH44%3D&reserved=0.

You should never store passwords in a text file on your server. That's definitely a security issue.

Yes we know that, hence is scary, I am trying to find any help how Laravel handel the RDS IAM authentications connection.. but the database driver for Laravel asks for db name and password..
 env('DB_CONNECTION', 'mysql'),

    /*
    |--------------------------------------------------------------------------
    | Database Connections
    |--------------------------------------------------------------------------
    |
    | Here are each of the database connections setup for your application.
    | Of course, examples of configuring each database platform that is
    | supported by Laravel is shown below to make development simple.
    |
    |
    | All database work in Laravel is done through the PHP PDO facilities
    | so make sure you have the driver for your particular database of
    | choice installed on your machine before you begin development.
    |
    */

    'connections' => [

        'sqlite' => [
            'driver' => 'sqlite',
            'database' => env('DB_DATABASE', database_path('database.sqlite')),
            'prefix' => '',
        ],

        'mysql' => [
            'driver' => 'mysql',
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8',
            'collation' => 'utf8_general_ci',
            'prefix' => '',
            'strict' => true,
            'engine' => null,

From: Claytonone
Reply-To: laravel/framework
Date: Thursday, 4 April 2019 at 10:44
To: laravel/framework
Cc: ilirkodra , Author
Subject: Re: [laravel/framework] IAM Database Authentication for RDS mySQL (#28097)

You should never store passwords in a text file on your server. That's definitely a security issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi there,
We have security issues, which means we been storing RDS databases user name and passwords on .env file and security team have forced us to remove those, does larvel supports IAM authentications on AWS : URL: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.html

@ilirkodra did you find any solution for it?

Hi there,
No, I never figured out!
Let me know if you have found out!
Thanks
Steve
Sent from my iPhone
On 18 Nov 2021, at 12:00, RS299 @.@.>> wrote:
Hi there,
We have security issues, which means we been storing RDS databases user name and passwords on .env file and security team have forced us to remove those, does larvel supports IAM authentications on AWS : URL: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.htmlhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.aws.amazon.com%2FAmazonRDS%2Flatest%2FUserGuide%2FUsingWithRDS.IAMDBAuth.html&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416942187|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=nRi04F1dXjdCzJmdvf%2FmNMfOo9m0EbHRMA8acv7%2Ffyo%3D&reserved=0
@ilirkodrahttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Filirkodra&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416942187|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=53bC3eFULX5Xyr9R2vm2R1rWcqWEn9pnrlC6sVssJ5s%3D&reserved=0 did you find any solution for it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flaravel%2Fframework%2Fissues%2F28097%23issuecomment-972800927&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416952138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=cGrlR0WcZB9XQfGZ77kvqLhVbOuZ7GBKiTt%2BlRW0w%2FE%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAANHUOKKWSPT57JKWXVUCT3UMTTGPANCNFSM4HDIYXAA&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416952138|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=SoIROuD60CMs5BPnQ0DUhZh2uvC6fUNVWGhzyBryR0w%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416962097|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=ehQ7AZ2IOCmr1pfnIpQfOVYdhvYieP%2FnWnW%2BnH9z6zA%3D&reserved=0 or Androidhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||d0ad56df67844498b35a08d9aa8b0a01|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637728336416972052|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Fz75FyUQA%2FSvBb54qjv23IQzu8vmSyDHQN%2BWeWH%2FOPc%3D&reserved=0.

authors: RS299 devcircus ilirkodra laurencei


text:
Error Warning: filesize() while using cron after upgrading Laravel 5.8

Hi,
We recently have updated to Laravel 5.6 to 5.8 and we randomly have this error now while using cron to call some api endpoints as we did before :
Warning: filesize(): stat failed for storage/framework/cache/data/aa/ba/aabaeafdb90f0d93adc97d019d71de3fd2045953
in /public/index.php - line 55
$request = Illuminate\Http\Request::capture()
Do you have any idea why?
Thank you very much!

What's the full stack trace?
My guess is a file permission error, where the cron user is different to the web user.

Hi @laurencei  and thank you for your answer.
Here is the full stack trace : Here
Note that, the cron user is the same as the nginx user, we try every permission , every chown, chmod 777 and so on on folder, we changed the cron folder and the user of the storage folder.
We cleared cache, every of them config, routes, view, app....  We removed files manually, we call composer update and dump-autoload
A thing which is very strange is that the datetime of the file is after the datetime of the error, like the file do not exist at the time the request was called?! It was working fine on version 5.6, I really do not understand why now it's broken.
Sometimes the error is th fopen failed to open stream: No such file or director sometime it is the errorfilesize(), we try with wget, curl, same result.....
Thank you for your light

Hey there,
Can you first please try one of the following support channels? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

Also: please fill in the issue template next time. Thanks!

I did not see issue template while creating the issue .
Moreover problem still occurs, not only on cron but everywhere...
I don't know if it's a bug or not, but there is clearly something not properly working with this last version.

I did not see issue template while creating the issue .
Moreover problem still occurs, not only on cron but everywhere...
I don't know if it's a bug or not, but there is clearly something not properly working with this last version.

Were you able to ever find any resolution to this issue?  I am having the exact same problem after upgrading to 5.8

I am actually having this issue in version 5.7

Exact same problem. We can't figure it out yet. Like, the EXACT same problem.

I still haven't been able to solve it.  I ended up just caching on a Redis instance as opposed to the file system as a workaround.

I am having the same issue randomly getting reported by Sentry

@driesvints I am not sure this is a support issue. We are also seeing this on numerous projects. Considering this was not an issue in previous versions, it seems like a bug. Maybe not a serious bug, but it definitely feels like a regression. The problem is that it’s intermittent so it seems to be getting ignored. Is anyone going to look into this or should we just expect to to ignore it in the future?

@djohnston08 can you please try a support channel first and then report back if that didn't help?

@driesvints I'm pretty sure this is a bug rather than a support issue. We're getting it too but it's very sporadic. It seems to be an issue with the file cache driver.
ErrorException
Warning: filesize(): stat failed for /var/www/x/storage/framework/cache/data/a2/db/a2db5ca42f2189b4ea48e92035d86e01956e31a7

I'm seeing this issue too, and a related issue in the same section of code (also triggered from public/index.php, line 55 like above). Seems to be a race condition, somehow. I've attached two screenshots from my Sentry instance - hope it helps.

screenshot 2:

I'm convinced it's a bug, not a support issue.

Okay, I'll re-open this. Appreciating anyone who could help look into this.

Thanks! I'm at a loss for how as for how a filesize() call could fail on a file after you've acquired a lock on it (first screenshot).

Ok, so I thought (and read) about it a bit more. I think there might be one of two things happening here:

Whatever flock() does is advisory, meaning that maybe (?) you don't really get a file lock even if you do call flock(). So any competing process could theoretically just call unlink(), maybe to clean out the cache folder, and delete the file that we thought we had a lock on.

flock() operates on a file handle, not on a file name. Assuming that flock() get us an actual lock, not an advisory one, then the code above could still fail if we rename the file that we have a lock on. That wouldn't affect the lock, as the file itself still has the lock – the file just has a different name. However, in the code, after we obtain the lock, we try to do an operation on the file with the name as it was before the assumed rename. Since that file name no longer exists, it would fail - triggering this error.

My two cents on this. Not sure on how to best address them. Thoughts?

it also happened on version 5.7

Well that screenshot has given me a thought - is everyone here using sentry?
I use sentry so maybe it's related...

From the stacktrace, the original issue seems more like a ThrottleRequests cache failure than related with cron itself. Using file store even sessions sometimes can throw an exception of file not found and that's present for quite some time, minimum from laravel 5.2.

Well that screenshot has given me a thought - is everyone here using sentry?
I use sentry so maybe it's related...

Yep, using Sentry here.

I wonder if its related to this: https://github.com/getsentry/sentry-laravel/issues/254

Laravel 6.10.1 - same problem.

@Rishats are you using sentry-laravel? Can you try upgrading to 1.4.0 to see if that fixes your problem?https://github.com/getsentry/sentry-laravel/issues/254#issuecomment-543558493

@Rishats are you using sentry-laravel? Can you try upgrading to 1.4.0 to see if that fixes your problem?getsentry/sentry-laravel#254 (comment)

I use https://packagist.org/packages/sentry/sentry-laravel
composer.lock
"name": "sentry/sentry-laravel",
"version": "1.5.0",
...

We are using Sentry as well. The error occured the first time, when following packages in our installation were updated. Some are internal packages so I just listed the public ones:

Package
From
To

aws/aws-sdk-php
3.130.3
3.132.1

egulias/email-validator
2.1.13
2.1.14

facade/ignition
1.13.1
1.14.0

laravel/nova
v2.9.2
v2.9.3

sentry/sdk
2.0.4
2.1.0

sentry/sentry
2.2.6
2.3.0

phpunit/phpunit
7.5.18
7.5.20

The sentry/sdk had following changes:
Added: guzzlehttp/psr7 and symfony/polyfill-uuid
Removed: ramsey/uuid and zendframework/zend-diactoros
I'm now trying to upgrade to sentry/sentry-laravel 1.5.0  to check if that makes a difference.

authors: Perh0rd Rishats Xpedigo andypa devsi djohnston08 donnysim driesvints eberkund foxinatardis infostreams jamiehd laurencei markgukov masbenx wtbloom


text:
[6.x] Maximum execution time exceeded when using relation belongsToMany with Eloquent

Laravel Version: 6.1.0
PHP Version: PHP 7.2.19-0ubuntu0.18.04.2 (cli)
Database Driver & Version: PostgreSQL 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1)

Description:
After you insert data into an intermediate table, data is not returned in a query. The following error occurs:
{
    "message": "Maximum execution time of 30 seconds exceeded",
    "exception": "Symfony\\Component\\Debug\\Exception\\FatalErrorException",
    "file": "/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasRelationships.php",
    "line": 604,
    "trace": []
}

For this error to happen it is enough that only 1 record is inserted in the database.
Steps To Reproduce:

Create a Basic Model of a Many To Many Relationship.
Create a method with find and with

Example:

Model Sepultura.php

<?php

namespace App;

class Sepultura extends Model
{
    protected $table = 'sepulturas';

    protected $fillable = ['lote', 'lote_anterior', 'quadra', 'quadra_anterior'];

    protected $appends = ['proprietario_list'];

    public function proprietarios()
    {
        return $this->belongsToMany('App\Proprietario', 'proprietarios_sepulturas', 'sepultura_id', 'proprietario_id')->withTimestamps();
    }

   public function getProprietarioListAttribute()
    {
        return array_map('strval', $this->proprietarios->pluck('id')->toArray());
    }
}

Model Proprietario.php

<?php

namespace App;

class Sepultura extends Model
{
    protected $table = 'proprietarios';

    protected $fillable = ['nome', 'rg', 'cpf', 'telefone', 'email'];

    protected $appends = ['sepultura_list'];

    public function sepulturas()
    {
        return $this->belongsToMany('App\Sepultura', 'proprietarios_sepulturas', 'proprietario_id', 'sepultura_id')->withTimestamps();
    }

    public function getSepulturaListAttribute()
    {
        return array_map('strval', $this->sepulturas->pluck('id')->toArray());
    }
}

Controller ProprietariosController.php

<?php

namespace App\Http\Controllers;

use App\Proprietario;

class ProprietariosController extends Controller
{
    private $proprietario;

    public function __construct(Proprietario $proprietario)
    {
        $this->proprietario = $proprietario;
    }

    public function show($id)
    {
        $proprietario = $this->proprietario->with('sepulturas')->find($id);

        if(count($proprietario->toArray()) > 0)
            return response()->json($proprietario);

        return response()->json(['error' => 'Resource not found!'], 404);
    }
}

The show method simply gives the error Maximum execution time exceeded when something is inserted in the proprietarios_sepulturas table.
I have the perfect code running on Laravel 5.8.
How to fix this problem ?!
Thanks

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Hello driesvints,
Many thanks for the reply. I put the problem here because it actually seems to be a framework problem in this release. I will wait to see if anyone is having the same problem.
Best regards

Any solutions yet?
I have a datatable which gets its data with ajax request. I can fetch model itself but when i try to fetch it with its relations, i get the max execution timeout exception. Its look like there is an infinite loop somewhere in core. Here is my code;
$data = User::with('doctor')->get()->sortByDesc('created_at')->tojson(); return response()->json($data, 200);

authors: driesvints ibrahimdolas larsurilch


text:
CORS Not working

Laravel Version: ^10.0
PHP Version: 8.2.2
Database Driver & Version:
Postfress Database

Description:
ç
Problem 1
- fruitcake/laravel-cors[v0.1, ..., v0.1.2] require illuminate/support 4.x -> found illuminate/support[v4.0.0, ..., v4.2.17] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.2.0, ..., v0.2.3] require illuminate/support ~4.1 -> found illuminate/support[v4.1.0, ..., v4.2.17] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.3.0, ..., v0.4.0] require illuminate/support 5.0.x -> found illuminate/support[v5.0.0, ..., v5.0.33] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.5.0 requires illuminate/support ~5.0.17|5.1.x -> found illuminate/support[v5.0.22, ..., v5.1.41] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.6.0 requires illuminate/support 5.0.x|5.1.x -> found illuminate/support[v5.0.0, ..., v5.1.41] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.7.0, ..., v0.7.2] require illuminate/support ~5.0.14|5.1.x -> found illuminate/support[v5.0.22, ..., v5.1.41] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.7.3 requires illuminate/support ~5.0.14|5.1.x|5.2.x -> found illuminate/support[v5.0.22, ..., v5.2.45] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.8.0 requires illuminate/support 5.1.x|5.2.x -> found illuminate/support[v5.1.1, ..., v5.2.45] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.8.1, ..., v0.8.2] require illuminate/support 5.1.x|5.2.x|5.3.x -> found illuminate/support[v5.1.1, ..., v5.3.23] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.8.3, ..., v0.9.2] require illuminate/support 5.1.x|5.2.x|5.3.x|5.4.x -> found illuminate/support[v5.1.1, ..., v5.4.36] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.9.3, ..., v0.10.1] require illuminate/support 5.3.x|5.4.x|5.5.x -> found illuminate/support[v5.3.0, ..., v5.5.44] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.11.0 requires illuminate/support 5.3.x|5.4.x|5.5.x|5.6.x -> found illuminate/support[v5.3.0, ..., v5.6.39] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.11.1 requires laravel/framework 5.5.x|5.6.x|5.7.x -> found laravel/framework[v5.5.0, ..., v5.7.29] but it conflicts with your root composer.json require (^10.0).
- fruitcake/laravel-cors v0.11.2 requires illuminate/support 5.5.x|5.6.x|5.7.x -> found illuminate/support[v5.5.0, ..., v5.7.28] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v0.11.3 requires illuminate/support 5.5.x|5.6.x|5.7.x|5.8.x -> found illuminate/support[v5.5.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v0.11.4, v1.0.0] require illuminate/support ^5.5|^6 -> found illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v1.0.1, ..., v1.0.2] require php ^7.1.3 -> your php version (8.2.2) does not satisfy that requirement.
- fruitcake/laravel-cors v1.0.3 requires illuminate/support ^5.5|^6.0|^7.0 -> found illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v1.0.4, ..., v1.0.6] require illuminate/support ^5.5|^6.0|^7.0|^8.0 -> found illuminate/support[v5.5.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v2.0.0, ..., v2.0.1] require illuminate/support ^5.6|^6.0|^7.0|^8.0 -> found illuminate/support[v5.6.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors v2.0.2 requires illuminate/support ^6|^7|^8 -> found illuminate/support[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- fruitcake/laravel-cors[v2.0.3, ..., v2.2.0, v3.0.0] require illuminate/support ^6|^7|^8|^9 -> found illuminate/support[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.4] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires fruitcake/laravel-cors * -> satisfiable by fruitcake/laravel-cors[v0.1, ..., v0.11.4, v1.0.0, ..., v1.0.6, v2.0.0, ..., v2.2.0, v3.0.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require fruitcake/laravel-cors:*" to figure out if any version is installable, or "composer require fruitcake/laravel-cors:^2.1" if you know which you need.
Steps To Reproduce:

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

authors: driesvints microsoftjulius


text:
Unexpected Lazy Loading Behavior with Eager Loaded Relations in Nested Queries

Laravel Version
9.52.7
PHP Version
8.1
Database Driver & Version
MYSQL 8.0
Description
Hi everyone, I’ve been running into a strange issue with eager loading in Laravel. I have a nested query where I load an Order model with Customer and Products relations, but when I access Products inside a nested foreach loop, Laravel is performing lazy loading instead of using the eager-loaded data.
Here’s a simplified version of my code:
php
$orders = Order::with(['customer', 'products'])->get();
foreach ($orders as $order) {
echo $order->customer->name;
foreach ($order->products as $product) {
echo $product->name;
}
}
For some reason, it’s firing additional queries for products even though I eager-loaded it. I’m on Laravel 9 and have tried using load() to explicitly load relationships, but I can’t figure out why this is happening. Is there a way to prevent this unexpected lazy loading?
Steps To Reproduce:
Define the Order model with customer and products relationships.
Fetch orders with eager loading using Order::with(['customer', 'products'])->get();.
Access customer and products relationships within a nested loop and observe additional queries triggered for products despite eager loading.

Steps To Reproduce
The products relation should be eager-loaded and not trigger additional queries when accessed within nested loops.

thanks


text:
[proposal] some kind of namespacing on globals

I just installed Drupal and Drush in Homestead using Composer. I know Homestead is made for Laravel, but its just so good :)
When doing anything with Drush I would get:

PHP Fatal error:  Cannot redeclare base_path() (previously declared in /home/vagrant/.composer/vendor/illuminate/support/Illuminate/Support/helpers.php:365) in /home/vagrant/Workspace/drupal/8/community/core/includes/common.inc on line 830

Drupal also has a base_path global function. I ended up renaming the Laravel base_path to laravel_base_path. Maybe not the prettiest solution, but it looks like it is working for now.
Please consider some solution (probably not mine) to this problem.
EDIT: Same goes for dd()

That would go against the whole point of these functions, sorry. They need to be easy to use in views, like the trans function. We can't namespace them.

@CarstenHoyer how did you work around this and change this variable when working in Drupal sites?

@rossedman I didn´t. I started using Homestead for Laravel and [VDD][https://www.drupal.org/node/2008792] for Drupal. Much better solution.

@CarstenHoyer Thats what I was considering. Thanks so much for responding.

I've got the same problem with Drupal.
Follow-up:

laravel/internals/issues/709
laravel/framework/issues/20370

authors: CarstenHoyer GrahamCampbell kenorb rossedman


text:
[5.7] Resolve Blade facade to named service

I am unsure whether the manual resolution was added for a specific purpose. I am assuming it was just there because the first version of the ViewServiceProvider did not register a binding for the Blade compiler.

The only other facade that does not return a string from getFacadeAccessor() is the Schema facade.
If we replace that logic with a binding (we'd have to register a new one), we could get rid of some complexity because we could require all facades to return a string from that method.

Hmm, I'm scared to change this in case I forgot some reason I did it this way. 👀

@taylorotwell I don't see why there should be a reason other than what I wrote:

I am assuming it was just there because the first version of the ViewServiceProvider did not register a binding for the Blade compiler.

We can target it at 5.8, then there's enough time to find out?

authors: franzliedke taylorotwell


text:
fix bug #25671

It looks like you've changed permissions on HandleExceptions.php to make it executable. Is that necessary or just a mistake?

It looks like you've changed permissions on HandleExceptions.php to make it executable. Is that necessary or just a mistake?

That's mistake and stupid. :(
fixed.

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!

authors: ipengxh sisve taylorotwell


text:
[5.8] Fix some docblocks

They should be also null included.

Thanks. 👍


text:
[5.8] Fix bug in scheduler

This resolves https://github.com/laravel/framework/issues/28943
Q: What was this caused by?
Carbon does some "under the hood" swaps when the end time is greater than the start time during a between() check. So when we pass in $start = 23:00 & $end = 03:00 - Carbon inverts those numbers since the date was always "today".
So we need to ensure that we've accounted for this before passing in the times and give Carbon a correct date range in addition to the time.
Q: Why did you change some of the original tests?
It turns out some of the original tests were incorrect, and were not actually "testing" what we thought they were.
In the original test suite, the Event class is mocked once per test function. But each subsequent test in the same function would "add" a new rule to the array stack, and therefore we were not testing them in isolation of each other.
This caused the later tests in the one function to be influenced by the earlier ones, and that caused some unexpected issues during the refactor. This is why @driesvints ran into some issues here https://github.com/laravel/framework/issues/28943#issuecomment-505453400
Q: Why do you do check on the startTime vs "now"
So we need to determine if we need to decrease the startTime date (when we've past that current time), or increase the endTime (when we've not gone past the start time). This helps handle the before/after midnight scenario.
I added some extra tests, with various scenarios to try to prove it works as expected.
Would be great if @aarondfrancis could test in his production to confirm this works before we merge this in.
It's been like this for literally years (maybe since 5.0) - so there's no rush here to merge - lets make sure we've all good...

@laurencei thanks for all your work on thus 👍
It may be beneficial to wait until the next major version to do these changes? Because maybe people would expect the old behavior and it could disrupt their scheduling flow. It might be better to inform people of the breaking change in the upgrade guide. Like you said, there's no real rush to fix this.

@driesvints - yeah I was thinking the same thing. It's been like this for so long, that I think of this xkcd comic and worry people are unintentionally relying on a bug: https://xkcd.com/1172/

Yeah I just want to reference this comment by @devcircus where he notes that he expects this behavior atm: https://github.com/laravel/framework/issues/28943#issuecomment-505209601

@driesvints maybe a stopgap until the next major release is to add a warning to the docs? I don't think it's intuitive that this is the actual behavior.

@laurencei let's just move this to the master branch to be sure?

Yes, can this be re-opened on master branch for discussion?

@driesvints @laurencei was this reopened against master? I can't seem to find it.

Issue is still open so I don't think so.

Resent: https://github.com/laravel/framework/pull/29467

authors: aarondfrancis driesvints laurencei taylorotwell


text:
[7.x] Don't replicate timestamp fields only when timestamps are enabled

At the moment created_at and updated_at are always not replicated but in fact they should not be replicated only when model has timestamps enabled.
It's possible that they are managed manually or they contain completely different values than timestamps so they should not be excluded when replicating in such case

Shouldn't we fix this in 6.x instead?

Yeh, I'd say so. Looks pretty clear cut as a bug fix, unless I'm missing something?

@mnabialek unless you have a specific reason why this can't be fixed on 6.x feel free to send it to that branch.

@GrahamCampbell @driesvints Taylor rejected PR to 6.x branch as breaking change, so maybe we should reopen this?

@mnabialek I think this is a no-fix judging from Taylor's remarks. Sorry

authors: GrahamCampbell driesvints mnabialek


text:
[8.x] Compile view:cache views using a fresh app instance

The view:cache command was recently appended to the optimize command. This breaks optimize in situations where views need to be compiled based on the cache created by config:cache.
I ran into this issue when trying to run optimize in a project that uses the blade-ui-kit/blade-icons package. Running optimize would throw a "component class name not found" error, however running config:cache and then view:cache worked as expected.
This PR creates a fresh instance of the app before compiling any views in the view:cache command. This way the cached config generated by config:cache can be used in the view compilation step.

Personally would rather revert the other PR.

authors: imacrayon taylorotwell


text:
Added argument transformNullToEmptyString to the functions old() and …

…getOldInput() and added tests

I implemented this feature: https://github.com/laravel/ideas/issues/1826
Basically I modified the old() and getOldInput() functions to work nicely with the ConvertEmptyStringsToNull middleware. At the moment when you are making an update form (or a create form with a default non empty value) you can't use the old() helper function. Because if a specific field already has a value and the user removes this value in the form, the empty value is overridden with the existing value (or the default value). Which is not the intended behavior and makes the old() function rather useless at the moment. The only way to properly use the old() function at the moment is by not using the ConvertEmptyStringsToNull middleware. But this is a default middleware so in my opinion it makes sense that the old() function can handle this properly.
This shouldn't break anything. I added a default value of false and the tests are all working. I also added some extra tests (asserts) cases that weren't covered yet and added tests for the new feature itself.
Personally I think it would make sense to make the default value equal true. But this would be a breaking change, that's why I used false.

There's a breaking change to the method signature of getOldInput so please send this to master.

There's a breaking change to the method signature of getOldInput so please send this to master.

authors: Loots-it driesvints


text:
[9.x] Optionally cascade thrown Flysystem exceptions

This PR gives the ability to optionally cascade thrown Flysystem exceptions with a throws_exceptions config option.
There's a concern with this: operations like the delete method will hard-fail now when passing multiple paths. Any paths that haven't been reached yet won't be deleted yet. Not sure if this is something we should work around?
This PR is opt-in and non-breaking.
Related: https://github.com/laravel/framework/issues/41269

@driesvints
Thanks for the PR. :heart_eyes:
Please guide us where to specify the config option throws_exceptions in config/filesystem.php, an example would be helpful.

@ankurk91 no problem. You'd add this to any disk's config array:
'disks' => [
    'local' => [
        'driver' => 'local',
        'root' => storage_path('app'),
        'throws_exceptions' => true,
    ],
],

Renamed this config option to just throw. 👍

is there a way to conditionally @throw an exception in the docblock? otherwise the IDE gets confused why we're trying to catch an exception it doesn't think is being thrown.

@browner12 don't think so no


text:
[10.x] Store instantiated middleware within Kernel

Problem
Right now, all of the Http\Kernel@sendRequestThroughRouter() instantiates all of the middleware to pipe the request through. Then subsequently, Kernel@terminateMiddleware() instantiates all the middleware again just to check if there's a terminate() method on the middleware.
But is it really a problem?
For a lot of users, this will probably have a pretty minimal impact.
But if you have numerous middleware that require the container to resolve and inject dependencies, every request is made slower by this duplication of instantiation.
Solution
Store middleware instances within the Kernel.
Room for improvement
Router@runRouteWithinStack() could push check for terminating middleware and push that to the Kernel's $terminatingMiddlewareInstances array (though there's a dependency conflict).
It might also be nice to have a TerminatingMiddleware interface or a separate middleware stack that's just for terminating middleware.
To me, the co-mingling of the middlewares is very messy.

Potentially a breaking change if dependency bindings are changed during request.

@taylorotwell - what if I re-opened this and instead of storing instances, stored the class-name string for any middleware that has a terminate() method?
Then it can be reinstantiated to refresh bindings without having to instantiate middleware that doesn't have a terminate() method and was instantiated previously?

authors: cosmastech taylorotwell


text:
[10.x] Accept Mailables\Address as mail address

Currently the Illuminate\Mail\Mailables\Envelope accepts \Illuminate\Mail\Mailables\Address as a "to" and "bcc":
public function envelope(): Envelope
{
    return new Envelope(
        to: [new Address('foo@bar.baz', 'Foo')],
        bcc: [new Address('foo@bar.baz', 'Foo')],
    );
}

but doing the same with Mail Message
Mail::send('', [], static function (Message $message) {
    $message->to([new Address('foo@bar.baz', 'Foo')]);
});

fails because it only accepts \Symfony\Component\Mime\Address as possible address.
This pull add the ability to pass \Illuminate\Mail\Mailables\Address to the message - "to", "bcc, "cc", and other methods that call addAddresses directly like replyTo.
This is useful as we have a helper method on User to generate an address with mail and name and pass it to Envelope, and sometimes in a queue'd job/cron to Mail directly, which the latter required us to create an extension of the message and pass it as:
 $message->to([$user->getMailAddress()->toSymfonyAddress()])

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

authors: donnysim taylorotwell