Fix clock()
usage causing errors in prod environments
This commit is contained in:
parent
07f1ef4262
commit
2da8042b0f
2 changed files with 4 additions and 2 deletions
|
@ -3,6 +3,10 @@ This file is a running track of new features and fixes to each version of the pa
|
|||
|
||||
This project follows [Semantic Versioning](http://semver.org) guidelines.
|
||||
|
||||
## v1.10.1
|
||||
### Fixed
|
||||
* Fixes a surprise `clock()` function that was used for debugging and should not have made it into the release. This was causing activity events to not properly sync between the Panel and Wings.
|
||||
|
||||
## v1.10.0
|
||||
### Fixed
|
||||
* Fixes improper cache key naming on the frontend causing server activity logs to be duplicated across server page views.
|
||||
|
|
|
@ -26,8 +26,6 @@ class ActivityProcessingController extends Controller
|
|||
$servers = $node->servers()->whereIn('uuid', $request->servers())->get()->keyBy('uuid');
|
||||
$users = User::query()->whereIn('uuid', $request->users())->get()->keyBy('uuid');
|
||||
|
||||
clock()->log($request->input('data'));
|
||||
|
||||
$logs = [];
|
||||
foreach ($request->input('data') as $datum) {
|
||||
/** @var \Pterodactyl\Models\Server|null $server */
|
||||
|
|
Loading…
Reference in a new issue