[webview_flutter] Video keeps playing on new route / app inactive

Steps to Reproduce (scenario 1 of 2)
(Demo app code at the bottom)

From Screen0, open Screen1
In Screen1, press play on the video
Still in Screen1, open Screen2

Expect: audio from video stops
Actual: it kept playing
This only happens in Android because iOS plays the video fullscreen and user can't navigate around while playing something. I think this is an issue with PlatformView in general, not just limited to WebView.
Steps to Reproduce (scenario 2 of 2)

From Screen0, open Screen1
In Screen1, press play on the video
Switch app

Expect: audio from video stops
Actual: it kept playing
Logs
[✓] Flutter (Channel master, v1.5.9-pre.168, on Mac OS X 10.14.4 18E226, locale
    en-VN)
    • Flutter version 1.5.9-pre.168 at /Users/xxx/repos/flutter
    • Framework revision 2f1e7cf662 (2 days ago), 2019-05-07 08:33:22 -0700
    • Engine revision ee6412a74d
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 dbe80f3397)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/xxx/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/xxx/Library/Android/sdk
    • Java binary at: /Users/xxx/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/182.5314842/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.3)
    • Android Studio at /Users/xxx/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/182.5314842/Android
      Studio.app/Contents
    • Flutter plugin version 34.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build
      1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.33.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.0.0

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API
      28) (emulator)

• No issues found!

Demo code
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) => MaterialApp(home: Screen0());
}

class Screen0 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 0')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              RaisedButton(
                child: Text('Screen 1'),
                onPressed: () => Navigator.of(context).push(
                      MaterialPageRoute(builder: (_) => Screen1()),
                    ),
              ),
            ],
          ),
        ),
      );
}

class Screen1 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 1')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              AspectRatio(
                aspectRatio: 560 / 315,
                child: WebView(
                  initialUrl: 'https://www.youtube.com/embed/fq4N0hgOWzU',
                  javascriptMode: JavascriptMode.unrestricted,
                ),
              ),
              RaisedButton(
                child: Text('Screen 2'),
                onPressed: () => Navigator.of(context).push(
                      MaterialPageRoute(builder: (_) => Screen2()),
                    ),
              ),
            ],
          ),
        ),
      );
}

class Screen2 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 2')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[Text('This is screen 2')],
          ),
        ),
      );
}

As a workaround, I have to reload the WebView on widget deactivate and AppLifecycleState.paused. This stops the annoying background audio issue but not the best user experience.

class Screen1 extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => _Screen1State();
}

class _Screen1State extends State<Screen1> with WidgetsBindingObserver {
  WebViewController _controller;

  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 1 (workaround)')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              AspectRatio(
                aspectRatio: 560 / 315,
                child: WebView(
                  initialUrl: 'https://www.youtube.com/embed/fq4N0hgOWzU',
                  javascriptMode: JavascriptMode.unrestricted,
                  onWebViewCreated: (controller) => _controller = controller,
                ),
              ),
              RaisedButton(
                child: Text('Screen 2'),
                onPressed: () => Navigator.of(context).push(
                      MaterialPageRoute(builder: (_) => Screen2()),
                    ),
              ),
            ],
          ),
        ),
      );

  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addObserver(this);
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    super.dispose();
  }

  @override
  void deactivate() {
    super.deactivate();
    _controller?.reload();
  }

  @override
  void didChangeAppLifecycleState(AppLifecycleState state) {
    if (state == AppLifecycleState.paused) {
      _controller?.reload();
    }
  }
}

Please @amirh and @iskakaushik, any input regarding this issue?

I see the same behaviour. As a workaround, I did this (Stateful widget):
@override
void dispose() {
//These two steps are needed to stop audio and video
_webViewController.loadUrl('about:blank');
setState(() {});
// TODO: implement dispose
super.dispose();
}
This works. But I get an exception which tells me to report a bug for this:
════════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown while finalizing the widget tree:
'package:flutter/src/widgets/framework.dart': Failed assertion: line 4138 pos 12: '_debugLifecycleState != _ElementLifecycle.defunct': is not true.
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md
When the exception was thrown, this was the stack
#2      Element.markNeedsBuild
package:flutter/…/widgets/framework.dart:4138
#3      State.setState
package:flutter/…/widgets/framework.dart:1253
#4      _ArticleDetailPageState.dispose
package:fiper/…/article/article_page.dart:36
#5      StatefulElement.unmount
package:flutter/…/widgets/framework.dart:4729
#6      _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1922
...

I have also had to use the workaround posted by @woutervanwijk as my webview contains a vimeo video which auto plays. If i close the webview the video audio continues to play with no way of stopping it.
The reload workaround posted by @dacaiguoguogmail will not work if the media in the webview will autoplay.

Btw, the sound continues to play, even while I completely reload the whole app. So the webview stays hidden and active in the background in a way

For me reload or anything that will interrupt Vimeo player in WebView is not working so only workaround I found for that (besides going deep in bridges) is adding this in Activity
@Override protected void onPause() {     super.onPause();     ((AudioManager)getSystemService(             Context.AUDIO_SERVICE)).requestAudioFocus(                     new OnAudioFocusChangeListener() {                         @Override                         public void onAudioFocusChange(int focusChange) {}                     }, AudioManager.STREAM_MUSIC,                      AudioManager.AUDIOFOCUS_GAIN_TRANSIENT); }
Here is fix (without depricated) https://stackoverflow.com/questions/56968138/how-to-pause-a-webview-in-flutter

The issue is reproducible on latest dev channel (1.20.0-0.0.pre) and with latest version of webview_flutter.

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-0.0.pre, on Mac OS X 10.15.2 19C57, locale en-US)
    • Flutter version 1.20.0-0.0.pre at /Users/deeptibelsare/Documents/Fluttersdk/flutter
    • Framework revision d9653445f4 (8 days ago), 2020-06-09 18:43:03 -0400
    • Engine revision e8c13aa012
    • Dart version 2.9.0 (build 2.9.0-14.0.dev 5c1376615e)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/deeptibelsare/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/deeptibelsare/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/deeptibelsare/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3, Build version 11C29
    • CocoaPods version 1.9.3

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

! Doctor found issues in 1 category.

I also noticed on iOS that the WKWebView instances are still active and accessible via Safari using webview_flutter: 0.3.22+1.
To reproduce follow the steps

Use the code example below and make sure debuggingEnabled is enabled for the webview and run the app on iOS
Launch Safari and verify that you can see your device in the developer tab.
Navigate to Screen 1 and back to Screen 0, repeat this a few times
Verify that the unmounted WKWebView instances are still active and accessible via Safari, see screenshot

How can the WKWebView correctly be unmounted when the page of the webview is disposed?

Code Example
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) => MaterialApp(home: Screen0());
}

class Screen0 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 0')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              RaisedButton(
                child: Text('Screen 1'),
                onPressed: () => Navigator.of(context).push(
                  MaterialPageRoute(builder: (_) => Screen1()),
                ),
              ),
            ],
          ),
        ),
      );
}

class Screen1 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 1')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              AspectRatio(
                aspectRatio: 560 / 315,
                child: WebView(
                  debuggingEnabled: true,
                  initialUrl: 'https://www.youtube.com/embed/fq4N0hgOWzU',
                  javascriptMode: JavascriptMode.unrestricted,
                ),
              ),
              RaisedButton(
                child: Text('Screen 2'),
                onPressed: () => Navigator.of(context).push(
                  MaterialPageRoute(builder: (_) => Screen2()),
                ),
              ),
            ],
          ),
        ),
      );
}

class Screen2 extends StatelessWidget {
  @override
  Widget build(BuildContext context) => Scaffold(
        appBar: AppBar(title: Text('Screen 2')),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[Text('This is screen 2')],
          ),
        ),
      );
}

You can use javascript code to pause video
@override
  void didChangeAppLifecycleState(AppLifecycleState state) async {
    if (state == AppLifecycleState.paused && Platform.isAndroid) {
      _controller.future.then(
        (controller) => controller.evaluateJavascript(
            'var video = document.querySelector("video");video.pause();'),
        onError: (error) => debugPrint(error.toString()),
      );
    }
  }

You can use javascript code to pause video
@override
  void didChangeAppLifecycleState(AppLifecycleState state) async {
    if (state == AppLifecycleState.paused && Platform.isAndroid) {
      _controller.future.then(
        (controller) => controller.evaluateJavascript(
            'var video = document.querySelector("video");video.pause();'),
        onError: (error) => debugPrint(error.toString()),
      );
    }
  }

@marcjulian Could you file a new issue for your case? The steps there are somewhat different, and it's on iOS, so it may not be exactly the same issue.

@daohoangson Can you elaborate for the initial descriptions why you expect the video to stop? If the web view is still active in the route, or in the app, why would it stop playing?

@daohoangson Can you elaborate for the initial descriptions why you expect the video to stop? If the web view is still active in the route, or in the app, why would it stop playing?

It's expected that way I think. It's quite a surprise to receive a Google Play review regarding YouTube playing in background.

@daohoangson Sorry, I wasn't clear in my question. I understand why you might want your app to stop playing something when pushing a new route or switching apps; I'm asking why you expect this behavior to be fundamental to the web view itself. If the widget containing the web view still exists, why would the web view automatically stop playing without the developer doing so deliberately?

Your question made me wonder so I tried with a native Android app and the webview is indeed kept playing there. If there is no objection then I guess this issue can be closed now.


AMBARI-23086 Target host shows all the hosts available in Move Wizard

How was this patch tested?
21510 passing (28s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/829/
Test PASSed.


How can I throttle perMonth?

hi,
Thank you Stefan for your answer just before on other issue, I closed that issue. I have another question, we have to throttle PerMonth, Is it possible?

You can't do that directly, as an workaround you can split your month limit in 4 and rate limit per week. This is one of the limitation of WebApiThrottle that I have addressed in the ASP.NET Core port. When you'll migrate your solution to .NET Core you can use AspNetCoreRateLimit where you can specify custom time ranges for the rate limits.

hi Stefan ,
Thank you for your prompt response. Is there anyway I can write handler when limit is reached. My idea is that I update the policy run time (perWeek in my case) when the limit is  about to reach.

You can override the rate limit logic here ThrottlingHandler but updating the perWeek limit to solve the perMonth issue does't look good to me.

Thank you Stefan for guidelines.

hi Stefan,
I tried to override ThrottlingHandler method you suggested previously to override rate limit logic, but I think ThrottlingCore is not accessible outside of  WebApiThrottle library.
Would you please help me  how can I extend/override rate limit logic to support for perMonth.  We can  not upgrade our project to.NET core at this stage.
Thank you.

hi Stefan,
My manager decided  pricing  perWeek, so I can use in built behaviour.
Thank you.


Time period filter on the Demographics Tab

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
There needs to be a time period filter on the Demographics tab. Currently it has a filter on a single day by selecting a date. Add a feature of time period filter which has start_date and end_date. This helps understand the increase/decrease in the positive cases as per our city.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Can you confirm this is still an issue?.

This is more like a feature and not an issue. If there is a time period
filter on the tab, It gives us the number of cases per city which is not
present in the site.
Thanks & regards,
Amogh Kulkarni
On Sat, Jun 20, 2020, 5:48 PM Vignesh<EMAIL_ADDRESS>wrote:

Can you confirm this is still an issue?.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/covid19india/covid19india-react/issues/1886#issuecomment-646987400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHONWCTRJOBZ3QLBUNP5PGTRXSSIPANCNFSM4NATSP2Q
.

Obsolete now since demographics has been deprecated


Vue 3 support

I have released the official Vue 3 Blitzar! 🎉

See new docs:
https://blitzar.cycraft.co/

--

[x] double check wether or not the documentation of blitzar covers all use cases & features for the Vue 2 version
[x] recreate the documentation in Vite + Vue 3 with all the markdown content ready.
[x] start implementing all the examples of the docs one by one.

[x] completely rewrite BlitzForm, BlitzTable, BlitzListForm based on this rewrite
[ ] keep an ongoing list of breaking changes

--
Breaking Changes For Blitzar + Vue 3
BlitzTable
BlitzTable was completely rewritten and has changed a lot.

Please check out the new documentation on BlitzTable and adjust accordingly.
Some features are not yet re-implemented like conditional/dynamic styles & classes but they will be soon

BlitzForm
renamed terminology

@input to @update:modelValue

reason: Vue 3 requirement

@field-input to @updateField

reason: update-field makes sense with Vue 3 terminology (because Vue 3 doesn't rely on @input anymore)

@input-cell to @updateCell

reason: same as above

fieldInput (the function) to updateField

reason: same as above

evaluatedProps to dynamicProps

reason: clarity — Dynamic Props is a bit easier to understand imo.

mode: 'view' to mode: 'readonly'

reason: clarity — closer to HTML5 readonly attribute

upgrade strategy for the above:

find and replace

Deprecated props

deprecate rules validation array per field

reason: we do not use Quasar under the hood anymore, rules was only used because Quasar's QField uses it for Validation
I have thought a long time about the best way of implementing Validation, looking at VeeValidate, Vuelidate, Quasar, Vuetify and others, and have realised we already have a very simple implementation of form validation via Dynamic Props... So to reduce codebase complexity, I have added a new prop called error where you can simple pass a validation function much like the rules prop before. The difference is, it's a single function (to be marked as dynamicProps: ['error']) and you make it a single function that returns null if there's no error, or the error you want to display when there is one.
upgrade strategy: Read the new Documentation on Validation here. Please scroll to "validation" at the bottom

// before
{
  rules: [(val) => Number(val) > 18 || 'no minors allowed']
}
// after
{
  dynamicProps: ['error'],
  error: (val) => Number(val) > 18 ? null : 'no minors allowed'
}

deprecate prop internalErrorsFor array of field-names

reason: reduce codebase complexity & delete less common options to reduce size
upgrade strategy: just add internalErrors: true to the fields you need this

deprecate prop validator global validation function

reason: reduce codebase complexity & delete less common options to reduce size
upgrade strategy: just add error validation to each field in your schema instead

deprecate mode: 'add'

reason: reduce complexity
upgrade strategy:

check if your forms rely on mode: 'add' by doing a global search for add
write custom logic to difference between mode: 'add' and mode: 'edit'

Is there an estimate on when this might be available?  Or, alternatively, any insight into what needs to be done to migrate to Vue 3?

This is a great question!
Currently Blitzar uses QForm and QTable under the hood.
I plan to make the library way more Framework Agnostic by removing the dependencies on QForm and QTable.
I have nothing against QForm and QTable, but the issue is: using those as dependency introduces a lot of global CSS pollution in projects. So currently it's really annoying when using Blitzar in Non-Quasar projects...
Planned steps:

Remove QForm dependency
Remove QTable dependency

Upgrading to Vue3:

If Quasar upgrades to Vue 3 before I remove the dependencies, I can make the upgrade to Vue 3 on beforehand.
If I am able to remove the dependencies before Quasar upgrades to Vue 3, I can make the upgrade to Vue 3 myself.

I do not mind the QForm and QTable dependencies; Quasar v2 beta appears to be very stable and I am using Quasar for my application.  So my preference is for movement to Vue 3 first.  I looked at the Blitzar code and thought that there would not be too many changes but I was not confident in my doing it myself.

@Peter-Gabel the thing is, I rather wait until Quasar's official Vue 3 release.
If you want to help out and try using the current Quasar Vue 3 beta, you can help me out on a new branch. Do you want to try?
We can have a short zoom session if you'd like where I show you how to best do it if you're still new to contributing on Github.

Yes.  I'd love to get right on it but it will take me about a week to find the time in my schedule.  If you could propose when might be convenient for you, I would be grateful for guidance including any insights that you could share about migrating the code to Vue 3.  I'm still getting up to speed on Vue 3 - I keep dropping into Vue 2 idioms and then need to remind myself of the differences.  I am in the eastern US time zone but can be very flexible.

@mesqueeb Seeing as quasar already updated to Vue3, is there any issue updating now?

@Am3ra I will do my best to try to find the time to work on it!! Your support is much appreciated! : )

ps: WIP on this branch
https://github.com/CyCraft/blitzar/tree/v1.0.0

Finished BlitzForm and BlitzListForm.
Now working on BlitzTable. Looking at vue-dataset and vuejs-smart-table.

Loving what I'm seeing so far with Blitzar.
Looking forward to the updates to support the latest version of Quasar.

Thanks guys. I will try to host the new docs and release beta version this week. BlitzForm and BlitzListForm are already done and usable in beta in Vue 3 projects.

Thanks, Luca. I'm using BlitzTable in a new Quasar project and had to drop back to v1 because this library is helpful enough to make it worth doing that. Personally, I'd rather see it working with QForm and QTables than wait for the non-Quasar refactoring.

I'm having issues with hosting the new docs because of some Vite dynamic import issues...
But you can open the new docs by cloning this repo and doing these steps:
git checkout v1.0.0
npm i
npm run dev -w=docs

You need at least npm v7.14+ to be able to install the dependencies correctly.
You can install the Vue 3 compatible BlitzForm by
npm i @blitzar/form@next

and use it accordingly to the new docs.
Also check out the breaking changes documented in the first post of this thread.

I will continue to update here once I make progress hosting the new docs and also updates on the Vue 3 compatible BlitzTable.

I was able to deploy the docs for Vue 3 here:
https://blitzar-next.web.app/blitz-form/

I got the error in my browser with Quasar:
[Vue warn]: Failed to resolve component: CodeBlock
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
at <Blitzar onVnodeUnmounted=fn ref=Ref< null > >
I tried to register the component in boot - but did not help => What do I need to do to make it work with quasar 2?
_**** quasar boot file ****
import { boot } from 'quasar/wrappers'
import * as BlitzForm from '@blitzar/form'
// BlitzListForm
// export default boot(({ app }) => {
export default boot(async ({ app }) => {
app.component('BlitzForm', {
BlitzForm
})
// app.use(BlitzForm)
// app.use(Blitzar.BlitzListForm)
})_

@WaltiDev did you globally register CodeBlock?

I think yes: My "quasar boot file" has filename "blitzar.js" and is located in the /src/boot/ folder.
And in quasar.conf.js I added "blitzar" into boot:
boot: [
'blitzar'
],

your code seems wrong.
First of all, you need to globally register BlitzForm like so:

✅ correct: app.component('BlitzForm', BlitzForm)
❌ wrong: app.component('BlitzForm', { BlitzForm })

And second of all, I think you have a typo for CodeBlock. Where are you getting this component from?

✅ correct: app.component('CodeBlock', CodeBlock) (but you need to import it from somewhere)
❌ wrong: app.component('CodeBlock', { BlitzForm })

I hope that helps!

Hi,
Is there a timeline for when BlitzTable will work with Vue 3?
I migrated to quasar v2 recently and would love to implement Blitzar.

@phineas629 yes I've been working on it this week and hopefully have something out next week.

@mesqueeb sweet!
I really want to try Blitzar out.
If it's a fit then you got my support.

I have released the official Vue 3 Blitzar! 🎉

See new docs:
https://blitzar.cycraft.co/

Will continue to improve Blitzar heavily into 2022.

Thanks!
Sent from my T-Mobile 4G LTE Device
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Luca Ban @.>
Sent: Saturday, December 18, 2021 4:08:16 AM
To: CyCraft/blitzar @.>
Cc: Phineas Vang @.>; Mention @.>
Subject: Re: [CyCraft/blitzar] Vue 3 support (#55)
I have released the official Vue 3 Blitzar! 🎉

See new docs:
https://blitzar.cycraft.co/

Will continue to improve Blitzar heavily into 2022.
—
Reply to this email directly, view it on GitHubhttps://github.com/CyCraft/blitzar/issues/55#issuecomment-997180152, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDA6JVHW2VRKJFHKXTSAPTURRMRBANCNFSM4V2CJVCQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

To everyone here:
Vue 3 release of Blitzar is getting quite stable! Closing this issue for now.
I still plan to:

create a framework example for Quasar, Nuxt, ...

Let me know if anything's up!
--Blitzar was made with 💜 by Luca Ban.You cannot sponsor every project, but next time you do, think of this one for its prolonged maintenance.

HI Luca,
Can you meet online for consulting?
I have questions about blitzar integration with quasar.
Thanks,
Phineas
On Jan 8, 2022, at 11:13 PM, Luca Ban<EMAIL_ADDRESS>wrote:
To everyone here:
Vue 3 release of Blitzar is getting quite stable! Closing this issue for now.
I still plan to:

create a framework example for Quasar, Nuxt, ...

Let me know if anything's up!
--
Blitzar was made with 💜 by Luca Ban.
You cannot sponsor every project, but next time you do, think of this onehttps://github.com/sponsors/mesqueeb for its prolonged maintenance.
—
Reply to this email directly, view it on GitHubhttps://github.com/CyCraft/blitzar/issues/55#issuecomment-1008232044, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDA6JWALEK3QSM65I3E3ZLUVEKODANCNFSM4V2CJVCQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

Is continued support for Blitzar still ongoing?


Tailscale QS not working on Bluefin 40

Describe the bug
After rebasing from Bluefin 39 to 40, Tailscale QS stopped working, being marked as incompatible with the current version of GNOME.
What did you expect to happen?
Tailscale QS being compatible with the current version of GNOME.
Output of rpm-ostree status
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:40
                   Digest: sha256:a94ac734c5c8f17a74ce23d5642b2f083f8507049dc4900876aa4fb4f5312413
                  Version: 40.20240517.0 (2024-05-17T17:03:14Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:40
                   Digest: sha256:a0b83de7a0bf18e3e08f320baaeee05e5443d36b130125c6a8c4c4462f1a30ac
                  Version: 40.20240514.0 (2024-05-16T02:11:08Z)

Output of groups
No response
Extra information or context
Reported as requested on Discord.

I'll sync our fork with upstream.
https://github.com/ublue-os/tailscale-gnome-qs

I've updated Bluefin to the most recent version:
❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:090cbd08f4b7b588505428ccbfc00d33b31b17ebd81c582eb0522df7ce67b8f1
                  Version: 40.20240518.0 (2024-05-19T01:42:17Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:cdb047b826181585546c3711afb1ba526d441cdf80a5cdaff2bc9325a5e0f4df
                  Version: 40.20240518.0 (2024-05-18T16:57:48Z)

Now I'm getting a different error when looking at the extension in Extension Manager:
TypeError: scrollView.add_actor is not a function

This is the commit causing the error:
https://github.com/ublue-os/tailscale-gnome-qs/commit/33008d453dd3482d8977893568b195f8e3f577b5
Due to this update in GNOME 46:
https://gjs.guide/extensions/upgrading/gnome-shell-46.html#gjs

Our fork had those commits removed. Should have the updated package after today's image.

Good news! I can confirm the extension works now. Unfortunately, it doesn't take my screen size into consideration when drawing its GUI so it draws way past the end of the screen. Seems like I'll have to stick to Tailscale Status for the time being. XD


First batch of includes

Created four include templates based on a selection of guide profiles
Removed user-choice scoring sections from includes
Added these to the includes.json

@rcdailey - tagging for a general review, but also the YAML Lint checks are failing...have I got something wrong with these, or is it because the rules are expecting a different indentation?

Hey yammes, the issue is that everything is indented by 2 spaces from the very left column. You only need to shift everything back 2 spaces and it'll clear up the lint issues.

As an example, your current file indentation looks like this:
  quality_definition:
    type: movie

But it needs to shift left by 2 spaces:
quality_definition:
  type: movie

I'm only showing a very small piece for example purposes, but this would apply to the entire file.

As an example, your current file indentation looks like this:
  quality_definition:
    type: movie

But it needs to shift left by 2 spaces:
quality_definition:
  type: movie

I'm only showing a very small piece for example purposes, but this would apply to the entire file.

I was certain I'd done that already which is why I asked...but not, I'd not done enough...sorry 😄

Fixed now - does everything else look alright?

Seems ok so far! I think where things will be more interesting is when you start including them in templates. We talked a little about this a few days ago, but you could either commit template changes to your fork (and change the config repo URL in your settings.yml) or just create copies in this repo for now so they don't interfere with the stable release.
You could go a number of ways. Did you have a plan already? Or were you just going to manipulate local configs for now to see how they would work if you had created them with config create?

Seems ok so far! I think where things will be more interesting is when you start including them in templates. We talked a little about this a few days ago, but you could either commit template changes to your fork (and change the config repo URL in your settings.yml) or just create copies in this repo for now so they don't interfere with the stable release.
You could go a number of ways. Did you have a plan already? Or were you just going to manipulate local configs for now to see how they would work if you had created them with config create?

For now, the idea is that I'll locally build 'new-style' templates that reference these includes, and then should they pass testing without issue then I'd look to update the templates themselves in the repo to match what I've built locally.
I've deviated a little from our last discussion on this, and haven't split quality profiles and custom formats into separate sections. For includes that are designed to mirror the guides, I don't think it's necessary.

Sounds like a great plan yammes. Good work! I think you'll eventually get a feel for how granular you want your include files as you play around with these more.

@yammes08 I went ahead and merged this so we have something to test with.

@yammes08 I went ahead and merged this so we have something to test with.

No problem, thanks for this, I just didn't get to it.


Add getR2dbcUrl Method on MariaDB, MySQL, PostgreSQL, MsSQL

I have added functionality to support the getR2dbcUrl method for MySQL, MariaDB, PostgreSQL, and MsSQL, as it was requested in this issue https://github.com/testcontainers/testcontainers-java/issues/8797

Can you add tests, please?

Of course! I'm currently writing and testing the tests. However, I encountered an error in MsSQL Test.
Project error log:
11월 27, 2024 9:32:30 오후 com.microsoft.sqlserver.jdbc.SQLServerConnection prelogin
WARNING: ConnectionID:49 ClientConnectionId: 307fe177-58b3-484d-9704-af971c580c28 Prelogin error: host localhost port 56807 Unexpected end of prelogin response after 0 bytes read

MsSQL Docker container error log:
2024-11-27 09:00:00 11:22:22.82 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.82 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]

I've found that these error logs keep repeating(but it seems like it's working fine). After researching, it seems that this issue is not only present in "Testcontainers" (https://github.com/testcontainers/testcontainers-java/issues/3079) but also appears in "mssql-docker" issues. However, I am unsure how to resolve this. Could you provide guidance on how to address this problem?

whole error log (MsSQL Docker container)
2024-11-27 20:22:14 SQL Server 2022 will run as non-root by default.
2024-11-27 20:22:14 This container is running as user mssql.
2024-11-27 20:22:14 To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2024-11-27 20:22:18 2024-11-27 11:22:18.51 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.53 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.54 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.55 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.56 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.57 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.58 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.59 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.60 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.61 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.62 Server      Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.65 Server      Microsoft SQL Server 2022 (RTM-CU14) (KB5038325) - 16.0.4135.4 (X64)
2024-11-27 20:22:18
        Jul 10 2024 14:09:09
2024-11-27 20:22:18
        Copyright (C) 2022 Microsoft Corporation
2024-11-27 20:22:18
        Developer Edition (64-bit) on Linux (Ubuntu 22.04.4 LTS) <X64>
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.65 Server      UTC adjustment: 0:00
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.65 Server      (c) Microsoft Corporation.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.66 Server      All rights reserved.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.66 Server      Server process ID is 472.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.66 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.66 Server      Registry startup parameters:
2024-11-27 20:22:18
         -d /var/opt/mssql/data/master.mdf
2024-11-27 20:22:18
         -l /var/opt/mssql/data/mastlog.ldf
2024-11-27 20:22:18
         -e /var/opt/mssql/log/errorlog
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.66 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.67 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.67 Server      Detected 12688 MB of RAM. This is an informational message; no user action is required.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.67 Server      Using conventional memory in the memory manager.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.68 Server      Detected pause instruction latency: 110 cycles.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.68 Server      SQL Server detected the following NUMA node configuration (NUMA Node number 0, Processor Group number 0, CPU Mask 0x00000000000000ff).
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.69 Server      Page exclusion bitmap is enabled.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.73 Server      Buffer pool extension is not supported on Linux platform.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.73 Server      Buffer Pool: Allocating 2097152 bytes for 1951326 hashPages.
2024-11-27 20:22:18
2024-11-27 09:00:00 11:22:18.86 Server      Buffer pool extension is already disabled. No action is necessary.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.31 Server      Installing Client TLS certificates to the store.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.33 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2 AVX512 (F CD BW DQ VL IFMA VBMI VBMI2 VNNI BITALG VPOQCNTDQ VP2INTERSECT)
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.42 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.46 Server      Query Store settings initialized with enabled = 1,
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.47 Server      The maximum number of dedicated administrator connections for this instance is '1'
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.47 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.49 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.52 Server      In-Memory OLTP initialized on standard machine.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.55 Server      [INFO] Created Extended Events session 'hkenginexesession'
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.55 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2024-11-27 20:22:19
ForceFlush is enabled for this instance.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.58 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.59 Server      clwb is selected for pmem flush operation.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.59 Server      CLR version v4.0.30319 loaded.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.59 Server      Software Usage Metrics is disabled.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.61 spid27s     [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.61 spid27s     Starting up database 'master'.
2024-11-27 20:22:19
ForceFlush feature is enabled for log durability.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.73 spid27s     The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  1024 bytes at offset 396288 in file /var/opt/mssql/data/mastlog.ldf will be written.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.78 spid27s     Converting database 'master' from version 927 to the current version 957.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.78 spid27s     Database 'master' running the upgrade step from version 927 to version 928.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.82 spid27s     Database 'master' running the upgrade step from version 928 to version 929.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.88 spid27s     Database 'master' running the upgrade step from version 929 to version 930.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.90 spid27s     Database 'master' running the upgrade step from version 930 to version 931.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.92 spid27s     Database 'master' running the upgrade step from version 931 to version 932.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.96 spid27s     Database 'master' running the upgrade step from version 932 to version 933.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.97 Server      Common language runtime (CLR) functionality initialized.
2024-11-27 20:22:19
2024-11-27 09:00:00 11:22:19.98 spid27s     Database 'master' running the upgrade step from version 933 to version 934.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.00 spid27s     Database 'master' running the upgrade step from version 934 to version 935.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.03 Server      External governance manager initialized
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.03 spid27s     Database 'master' running the upgrade step from version 935 to version 936.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.06 spid27s     Database 'master' running the upgrade step from version 936 to version 937.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.07 spid27s     Database 'master' running the upgrade step from version 937 to version 938.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.10 spid27s     Database 'master' running the upgrade step from version 938 to version 939.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.12 spid27s     Database 'master' running the upgrade step from version 939 to version 940.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.13 spid27s     Database 'master' running the upgrade step from version 940 to version 941.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.15 spid27s     Database 'master' running the upgrade step from version 941 to version 942.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.17 spid27s     Database 'master' running the upgrade step from version 942 to version 943.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.22 spid27s     Database 'master' running the upgrade step from version 943 to version 944.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.24 spid27s     Database 'master' running the upgrade step from version 944 to version 945.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.27 spid27s     Database 'master' running the upgrade step from version 945 to version 946.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.29 spid27s     Database 'master' running the upgrade step from version 946 to version 947.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.32 spid27s     Database 'master' running the upgrade step from version 947 to version 948.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.34 spid27s     Database 'master' running the upgrade step from version 948 to version 949.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.35 spid27s     Database 'master' running the upgrade step from version 949 to version 950.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.37 spid27s     Database 'master' running the upgrade step from version 950 to version 951.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.40 spid27s     Database 'master' running the upgrade step from version 951 to version 952.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.42 spid27s     Database 'master' running the upgrade step from version 952 to version 953.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.44 spid27s     Database 'master' running the upgrade step from version 953 to version 954.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.46 spid27s     Database 'master' running the upgrade step from version 954 to version 955.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.48 spid27s     Database 'master' running the upgrade step from version 955 to version 956.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.52 spid27s     Database 'master' running the upgrade step from version 956 to version 957.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.63 spid29s     [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.64 spid29s     Starting up database 'mssqlsystemresource'.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.64 spid29s     The resource database build version is 16.00.4135. This is an informational message only. No user action is required.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.66 spid37s     Password policy update was successful.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.69 spid29s     [3]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.69 spid29s     Starting up database 'model'.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.70 spid27s     [32762]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.71 spid27s     Starting up database 'model_replicatedmaster'.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.73 spid29s     The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.75 spid27s     The tail of the log for database model_replicatedmaster is being rewritten to match the new sector size of 4096 bytes.  2560 bytes at offset 99840 in file /var/opt/mssql/data/model_replicatedmaster.ldf will be written.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.78 spid29s     Converting database 'model' from version 927 to the current version 957.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.78 spid29s     Database 'model' running the upgrade step from version 927 to version 928.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.83 spid29s     Database 'model' running the upgrade step from version 928 to version 929.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.84 spid27s     Converting database 'model_replicatedmaster' from version 927 to the current version 957.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.84 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 927 to version 928.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.88 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 928 to version 929.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.89 spid29s     Database 'model' running the upgrade step from version 929 to version 930.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.91 spid29s     Database 'model' running the upgrade step from version 930 to version 931.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.93 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 929 to version 930.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.94 spid29s     Database 'model' running the upgrade step from version 931 to version 932.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.96 spid29s     Database 'model' running the upgrade step from version 932 to version 933.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.99 spid29s     Database 'model' running the upgrade step from version 933 to version 934.
2024-11-27 20:22:20
2024-11-27 09:00:00 11:22:20.99 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 930 to version 931.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.01 spid29s     Database 'model' running the upgrade step from version 934 to version 935.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.01 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 931 to version 932.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.03 spid29s     Database 'model' running the upgrade step from version 935 to version 936.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.03 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 932 to version 933.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.06 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 933 to version 934.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.06 spid29s     Database 'model' running the upgrade step from version 936 to version 937.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.08 spid29s     Database 'model' running the upgrade step from version 937 to version 938.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.08 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 934 to version 935.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.10 spid29s     Database 'model' running the upgrade step from version 938 to version 939.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.11 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 935 to version 936.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.12 spid29s     Database 'model' running the upgrade step from version 939 to version 940.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.13 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 936 to version 937.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.14 spid29s     Database 'model' running the upgrade step from version 940 to version 941.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.16 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 937 to version 938.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.17 spid29s     Database 'model' running the upgrade step from version 941 to version 942.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.19 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 938 to version 939.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.20 spid29s     Database 'model' running the upgrade step from version 942 to version 943.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.22 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 939 to version 940.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.23 spid29s     Database 'model' running the upgrade step from version 943 to version 944.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.24 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 940 to version 941.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.26 spid29s     Database 'model' running the upgrade step from version 944 to version 945.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.28 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 941 to version 942.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.28 spid37s     A self-generated certificate was successfully loaded for encryption.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.28 spid37s     Server is listening on [ 'any' <ipv6> 1433] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.29 spid37s     Server is listening on [ 'any' <ipv4> 1433] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.29 Server      Server is listening on [ ::1 <ipv6> 1434] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.29 Server      Server is listening on [ <IP_ADDRESS> <ipv4> 1434] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.29 Server      Dedicated admin connection support was established for listening locally on port 1434.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.32 spid29s     Database 'model' running the upgrade step from version 945 to version 946.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.32 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 942 to version 943.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.34 spid37s     Server is listening on [ ::1 <ipv6> 1431] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.34 spid37s     Server is listening on [ <IP_ADDRESS> <ipv4> 1431] accept sockets 1.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.34 spid37s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.35 spid29s     Database 'model' running the upgrade step from version 946 to version 947.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.38 spid29s     Database 'model' running the upgrade step from version 947 to version 948.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.40 spid29s     Database 'model' running the upgrade step from version 948 to version 949.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.40 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 943 to version 944.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.43 spid29s     Database 'model' running the upgrade step from version 949 to version 950.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.43 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 944 to version 945.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.46 spid29s     Database 'model' running the upgrade step from version 950 to version 951.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.47 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 945 to version 946.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.49 spid29s     Database 'model' running the upgrade step from version 951 to version 952.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.50 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 946 to version 947.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.52 spid29s     Database 'model' running the upgrade step from version 952 to version 953.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.54 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 947 to version 948.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.56 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.56 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.57 spid29s     Database 'model' running the upgrade step from version 953 to version 954.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.58 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 948 to version 949.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.60 spid29s     Database 'model' running the upgrade step from version 954 to version 955.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.61 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 949 to version 950.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.63 spid29s     Database 'model' running the upgrade step from version 955 to version 956.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.64 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 950 to version 951.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.67 spid29s     Database 'model' running the upgrade step from version 956 to version 957.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.68 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 951 to version 952.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.70 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 952 to version 953.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.73 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 953 to version 954.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.74 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.74 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.77 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 954 to version 955.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.82 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 955 to version 956.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.84 spid27s     Database 'model_replicatedmaster' running the upgrade step from version 956 to version 957.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.87 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.87 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.97 spid27s     [32761]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:21
2024-11-27 09:00:00 11:22:21.98 spid27s     Starting up database 'model_msdb'.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.01 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.01 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.06 spid27s     Converting database 'model_msdb' from version 927 to the current version 957.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.06 spid27s     Database 'model_msdb' running the upgrade step from version 927 to version 928.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.08 spid27s     Database 'model_msdb' running the upgrade step from version 928 to version 929.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.11 spid27s     Database 'model_msdb' running the upgrade step from version 929 to version 930.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.14 spid27s     Database 'model_msdb' running the upgrade step from version 930 to version 931.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.15 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.15 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.17 spid27s     Database 'model_msdb' running the upgrade step from version 931 to version 932.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.18 spid27s     Database 'model_msdb' running the upgrade step from version 932 to version 933.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.21 spid27s     Database 'model_msdb' running the upgrade step from version 933 to version 934.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.23 spid27s     Database 'model_msdb' running the upgrade step from version 934 to version 935.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.25 spid27s     Database 'model_msdb' running the upgrade step from version 935 to version 936.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.27 spid27s     Database 'model_msdb' running the upgrade step from version 936 to version 937.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.28 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.28 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.29 spid27s     Database 'model_msdb' running the upgrade step from version 937 to version 938.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.31 spid27s     Database 'model_msdb' running the upgrade step from version 938 to version 939.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.33 spid27s     Database 'model_msdb' running the upgrade step from version 939 to version 940.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.35 spid27s     Database 'model_msdb' running the upgrade step from version 940 to version 941.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.37 spid27s     Database 'model_msdb' running the upgrade step from version 941 to version 942.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.39 spid27s     Database 'model_msdb' running the upgrade step from version 942 to version 943.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.43 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.43 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.46 spid27s     Database 'model_msdb' running the upgrade step from version 943 to version 944.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.48 spid27s     Database 'model_msdb' running the upgrade step from version 944 to version 945.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.51 spid27s     Database 'model_msdb' running the upgrade step from version 945 to version 946.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.52 spid27s     Database 'model_msdb' running the upgrade step from version 946 to version 947.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.54 spid27s     Database 'model_msdb' running the upgrade step from version 947 to version 948.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.56 spid27s     Database 'model_msdb' running the upgrade step from version 948 to version 949.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.56 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.56 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.58 spid27s     Database 'model_msdb' running the upgrade step from version 949 to version 950.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.59 spid27s     Database 'model_msdb' running the upgrade step from version 950 to version 951.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.61 spid27s     Database 'model_msdb' running the upgrade step from version 951 to version 952.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.63 spid27s     Database 'model_msdb' running the upgrade step from version 952 to version 953.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.65 spid27s     Database 'model_msdb' running the upgrade step from version 953 to version 954.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.67 spid27s     Database 'model_msdb' running the upgrade step from version 954 to version 955.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.69 spid27s     Database 'model_msdb' running the upgrade step from version 955 to version 956.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.69 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.69 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.71 spid27s     Database 'model_msdb' running the upgrade step from version 956 to version 957.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.81 spid34s     Attribute synchronization initialized
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.81 spid27s     Resource governor reconfiguration succeeded.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.81 spid34s     Attribute synchronization manager initialized
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.81 spid27s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.81 spid27s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.82 spid27s     XE session 'system_health' started.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.82 Logon       Error: 18456, Severity: 14, State: 7.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.82 Logon       Login failed for user 'sa'. Reason: An error occurred while evaluating the password. [CLIENT: <IP_ADDRESS>]
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.85 spid27s     SQL Trace ID 1 was started by login "sa".
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.86 spid27s     Server name is '8771db1dd11d'. This is an informational message only. No user action is required.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.88 spid29s     Clearing tempdb database.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.88 spid46s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.88 spid48s     [4]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.89 spid46s     Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.89 spid48s     Starting up database 'msdb'.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.96 spid48s     Converting database 'msdb' from version 927 to the current version 957.
2024-11-27 20:22:22
2024-11-27 09:00:00 11:22:22.96 spid48s     Database 'msdb' running the upgrade step from version 927 to version 928.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.01 spid48s     Database 'msdb' running the upgrade step from version 928 to version 929.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.02 spid29s     [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. ConcurrentGAMUpdate: 1. ConcurrentSGAMUpdate: 1, CleanupUnderUserTransaction: 0. TranLevelPVS: 0
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.03 spid29s     Starting up database 'tempdb'.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.07 spid48s     Database 'msdb' running the upgrade step from version 929 to version 930.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.08 spid29s     The tempdb database has 1 data file(s).
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.09 spid46s     The Service Broker endpoint is in disabled or stopped state.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.09 spid46s     The Database Mirroring endpoint is in disabled or stopped state.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.10 spid46s     Service Broker manager has started.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.10 spid48s     Database 'msdb' running the upgrade step from version 930 to version 931.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.12 spid48s     Database 'msdb' running the upgrade step from version 931 to version 932.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.14 spid48s     Database 'msdb' running the upgrade step from version 932 to version 933.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.17 spid48s     Database 'msdb' running the upgrade step from version 933 to version 934.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.19 spid48s     Database 'msdb' running the upgrade step from version 934 to version 935.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.20 spid48s     Database 'msdb' running the upgrade step from version 935 to version 936.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.22 spid48s     Database 'msdb' running the upgrade step from version 936 to version 937.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.23 spid48s     Database 'msdb' running the upgrade step from version 937 to version 938.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.25 spid48s     Database 'msdb' running the upgrade step from version 938 to version 939.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.27 spid48s     Database 'msdb' running the upgrade step from version 939 to version 940.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.29 spid48s     Database 'msdb' running the upgrade step from version 940 to version 941.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.31 spid48s     Database 'msdb' running the upgrade step from version 941 to version 942.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.33 spid48s     Database 'msdb' running the upgrade step from version 942 to version 943.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.37 spid48s     Database 'msdb' running the upgrade step from version 943 to version 944.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.39 spid48s     Database 'msdb' running the upgrade step from version 944 to version 945.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.42 spid48s     Database 'msdb' running the upgrade step from version 945 to version 946.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.44 spid48s     Database 'msdb' running the upgrade step from version 946 to version 947.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.46 spid48s     Database 'msdb' running the upgrade step from version 947 to version 948.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.48 spid48s     Database 'msdb' running the upgrade step from version 948 to version 949.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.50 spid48s     Database 'msdb' running the upgrade step from version 949 to version 950.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.51 spid48s     Database 'msdb' running the upgrade step from version 950 to version 951.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.53 spid48s     Database 'msdb' running the upgrade step from version 951 to version 952.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.55 spid48s     Database 'msdb' running the upgrade step from version 952 to version 953.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.56 spid48s     Database 'msdb' running the upgrade step from version 953 to version 954.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.58 spid48s     Database 'msdb' running the upgrade step from version 954 to version 955.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.60 spid48s     Database 'msdb' running the upgrade step from version 955 to version 956.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.64 spid48s     Database 'msdb' running the upgrade step from version 956 to version 957.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.72 spid27s     Recovery is complete. This is an informational message only. No user action is required.
2024-11-27 20:22:23
2024-11-27 09:00:00 11:22:23.84 spid35s     The default language (LCID 0) has been set for engine and full-text services.
2024-11-27 20:22:24
2024-11-27 09:00:00 11:22:24.09 spid35s     The tempdb database has 8 data file(s).

@eddumelendez
I just added some tests, and I’d appreciate it if you could review it!


About the challenge

Hi author of MOTSYNTH
Can we use real data (e.ge. MOT17) with un-labeled and use unsupervised learning?

Hi,
Sorry for the late reply. We've had an internal discussion regarding this, and have decided that we will allow it!
Guillem

@guillembraso Does that mean UDA (Unsupervised Domain Adaptation) can be applied with MOT17-train as target domain? Also, does this unsupervised learning still exclude MOT17-test?

@guillembraso what about other sources of real data. I mean is mot17-train still the only allowed data even in a unsupervised manner?

hi, the link to motsynth dataset is broken, is there new link?Also, the domain gap between motsynth(MOTA:54) and mot17(mot17 half train only, MOTA:60) is a little small, is it necessary for domain adaption.


[cardano-wallet.network:Warning:15] [  UTC] Couldn't connect to node . Retrying in a bit...

Just checking...

[X] This is a cardano-wallet bug.
[X] I am using the latest cardano-wallet release.
[X] I am using the correct cardano-node version for that release of cardano-wallet.

Version
2021.8.11
Platform
Ubuntu
Installation method
IOHK Docker image
Network configuration
mainnet
Context
When I installed cardano-wallet with :
wget https://raw.githubusercontent.com/input-output-hk/cardano-wallet/master/docker-compose.yml
NETWORK=mainnet docker-compose up
At the beginning it installed well and everything was working with the API.
After a while I started getting this message and the server was not responding correctly anymore:

The blockchain is downloaded, and everything was working normally until this came.
I get this message when I try to go to wallets/id :
My associated worker for id.............. is no longer responding. This is not something that is supposed to happen. The worker must have left a trace in the logs of severity Error when it died which might explain the cause. Said differently, this wallet won't be accessible until the server is restarted but there are good chances it'll recover itself upon restart
I am able to see the sync progress on the network page on the browser
Tried a fresh install on a new os Ubuntu, same.
Ubuntu 20, 6gb Ram
Tried to leave it for hours, restart...
Description
Install all the dependencies, docker
run
wget https://raw.githubusercontent.com/input-output-hk/cardano-wallet/master/docker-compose.yml
NETWORK=mainnet docker-compose up

Hi, thanks for the report. This message usually means that the cardano-node process which provides the socket file /ipc/node.socket is not running. You should be able to use docker or docker-compose to check the status and logs of the cardano-node service.

Hi, thanks for the report. This message usually means that the cardano-node process which provides the socket file /ipc/node.socket is not running. You should be able to use docker or docker-compose to check the status and logs of the cardano-node service.

Ok when I check my logs I see :
Named volume "node--db:/data:rw" is used in service "cardano-node" but no declaration was found in the volumes section.
It seems that the node is running but something else is wrong.

Named volume "node--db:/data:rw" is used in service "cardano-node" but no declaration was found in the volumes section.

This message is from docker, not cardano-wallet or cardano-node. It appears e.g. when you do not set NETWORK env variable when starting docker compose.
Your description and cardano-wallet logs you shared suggest that cardano-node crashed/stopped working at some point and cardano-wallet couldn't connect to it any longer as @rvl mentioned. (hard to tell what happend without the node logs)
Perhaps stopping and restarting docker-compose gracefully might help?
NETWORK=mainnet docker-compose down
NETWORK=mainnet docker-compose up

or killing some orphaned docker processes you may have running in the background (docker ps to check)?

Named volume "node--db:/data:rw" is used in service "cardano-node" but no declaration was found in the volumes section.

This message is from docker, not cardano-wallet or cardano-node. It appears e.g. when you do not set NETWORK env variable when starting docker compose.
Your description and cardano-wallet logs you shared suggest that cardano-node crashed/stopped working at some point and cardano-wallet couldn't connect to it any longer as @rvl mentioned. (hard to tell what happend without the node logs)
Perhaps stopping and restarting docker-compose gracefully might help?
NETWORK=mainnet docker-compose down
NETWORK=mainnet docker-compose up

or killing some orphaned docker processes you may have running in the background (docker ps to check)?

Tried to install everything again from scratch, tell me if I did anything wrong:
sudo apt-get update
sudo apt-get install automake build-essential pkg-config libffi-dev libgmp-dev libssl-dev libtinfo-dev libsystemd-dev zlib1g-dev make g++ tmux git jq wget libncursesw5 libtool autoconf -y
sudo apt-get install
apt-transport-https
ca-certificates
curl
gnupg
lsb-release
sudo apt-get install build-essential curl libffi-dev libffi7 libgmp-dev libgmp10 libncurses-dev libncurses5 libtinfo5
curl --proto '=https' --tlsv1.2 -sSf https://get-ghcup.haskell.org | sh
reboot
ghcup --version
ghcup install ghc 8.10.4
ghcup set ghc 8.10.4
ghc --version
cabal --version
cabal-install version <IP_ADDRESS>
sudo apt-get update
sudo apt install docker.io docker-compose
wget https://raw.githubusercontent.com/input-output-hk/cardano-wallet/master/docker-compose.yml
NETWORK=mainnet docker-compose up
6GB RAM 4 core

For starting our docker-compose only having docker and docker-compose should be enough.

The problem still not solved even with a new fresh install. Is it may be because I have to make the volume shared or does the script already makes it.

I'm not sure what might be the problem. I suspect the node stopping and now cannot recover somehow. Is it possible that you share logs from cardano-node?
One option to recover might be also to clean-up your docker volumes/images/processes and try starting docker-compose again. (But pls note that you will need to restore the whole blockchain from scratch)
This should clean up all of what you have, but you my want to limit only to cardano-node / cardano-wallet...
docker rm -f $(docker ps -a -q)
docker volume rm -f $(docker volume ls -q)
docker image rm -f $(docker image ls -q)

NETWORK=mainnet docker-compose up

I'm not sure what might be the problem. I suspect the node stopping and now cannot recover somehow. Is it possible that you share logs from cardano-node?
One option to recover might be also to clean-up your docker volumes/images/processes and try starting docker-compose again. (But pls note that you will need to restore the whole blockchain from scratch)
This should clean up all of what you have, but you my want to limit only to cardano-node / cardano-wallet...
docker rm -f $(docker ps -a -q)
docker volume rm -f $(docker volume ls -q)
docker image rm -f $(docker image ls -q)

NETWORK=mainnet docker-compose up

This is what I get when I check the logs :
ERROR: Named volume "node--db:/data:rw" is used in service "cardano-node" but no declaration was found in the volumes section.
The node is running, tried a fresh install and still the same result. Is it built for ubuntu 20.4?

ERROR: Named volume "node--db:/data:rw" is used in service "cardano-node" but no declaration was found in the volumes section.

This suggests that NETWORK env variable is somehow not picked up by docker :thinking: ...

Is it built for ubuntu 20.4?

Yes, it works on Ubuntu 20.04 for me.
Can you follow those steps please?

wget https://raw.githubusercontent.com/input-output-hk/cardano-wallet/master/docker-compose.yml
Start NETWORK=mainnet docker-compose up (do you see some logs from node and wallet here after starting the command?)
Check running containers with docker ps, I have something like this:

CONTAINER ID        IMAGE                                          COMMAND                  CREATED             STATUS              PORTS                    NAMES
81f13e2cf2e2        inputoutput/cardano-node:alonzo-purple-1.0.1   "entrypoint"             2 minutes ago       Up 2 minutes                                 cardano-wallet_cardano-node_1
cbfbc639e432        inputoutput/cardano-wallet:2021.8.11           "bash -c ' ([[ $NETW…"   2 minutes ago       Up About a minute   <IP_ADDRESS>:8090->8090/tcp   cardano-wallet_cardano-wallet_1

Then look-up logs for cardano-node container, e.g. docker logs -f  81f13e2cf2e2
In my case I see cardano-node logs:

[8596e314:cardano.node.ChainDB:Notice:34] [2021-08-18 16:35:52.76 UTC] Chain extended, new tip: 744e2e79ed97d34dbdc8e3325bf79cf3ef111cb8ec8ace9faae0bf1edc521cb4 at slot 25297
[8596e314:cardano.node.ChainDB:Notice:34] [2021-08-18 16:35:54.01 UTC] Chain extended, new tip: 95fad99fdf46879aec1f361754e6fd6308ecf3f24792a1c79f80775b92bd608a at slot 27160
...

Cannot reproduce.


🐞Moving on top of food powerups causes the editor to hang

As issue title. The game and editor hangs when attempting to move on top of a food powerup.
Reproduction:

Move around the level until you find a fish icon
Move onto the fish icon
Weep as you are forced to force close the editor using the task manager.

There also seem to be uncaught exceptions in pathfinding occasionally when near the food. Assuming this is a pathfinding bug until proven otherwise.

Can confirm. In game console doesn't show anything alarming, but Unity itself becomes unresponsive. CPU utilization stays low.

Just confirmed it was when the seals moved onto a fish. could it be that the path finding never resolves because it can't find seal?

Penguins actually avoid the fish currently, not sure if that helps, but I just played ring around the fishy with a lovely trio of penguins and they treated it like a pilar

I had a showerthought™ this morning. Writing it down for future reference. This hang could be caused by the pathfinder looping back on itself. When generating edges, it doesn't check to see if the edge it's about to create was used to get to the tile/node that the pathfinder is currently on.

Penguins actually avoid the fish currently, not sure if that helps, but I just played ring around the fishy with a lovely trio of penguins and they treated it like a pilar

Fishies are their god. They treat it with gentle reverence.


Distribute license data as an embed fs.

The code is a first draft. The idea is to make it work first, then simplify and make code beautiful.

[X]  Add mage file target
[x] Modify code to use embed fs.
[ ] Prettify code
[ ]  Create a job / pipeline to renew the embed FS in the binary distribution

@cpanato  I guess we would need to change https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/bom/bom-presubmits.yaml . Should we do that after this is merged ?

https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/bom/bom-presubmits.yaml

dont need, in the targets test and verify you add your new function to be called in the beginning

@cpanato
dont need, in the targets test and verify you add your new function to be called in the beginning

Fixed the tests. Thanks. Now I'll need to prettify the code.

@puerco  @cpanato  thanks for review. To summarize

The user won't be able to update the license list once bom is installed. They'd need to update bom itself to acheive this. This is because embed.FS is read only, and can't updated during runtime.
As @puerco  suggested IMHO we should commit the licenses in the repo. The CI would check if incoming PR has stale licenses and fail if necessary. We could also have a periodic job which would update the licenses, this could be run as part of release pipeline.
Due to (1), there's really no point of downloader, we should rename the deserialization code and eliminate other unrequired stuff.

Let me know if I missed something.

Due to (1), there's really no point of downloader, we should rename the deserialization code and eliminate other unrequired stuff.

@sbs2001  I still think we need to keep the modules to download the licenses, this is still needed because a) we  need to download them to embed and b) at some point we may need to download a specific version (so to verify an SBOM using an older version)
One way of improving it though is downloading the license release tarballs instead of following the links in the JSON list. (I didn't know about these one I first created the download code :upside_down_face: )
So in the end, we only need two methods:  One to download (and install) the latest version and another to the same with a specific version. We can rework Downloader.GetLicenses() in the licenses package to download the latest tarball and we can add a new Downloader.GetLicensesVersion() (or whatever name) to use the same logic to download a specific version.
This allows us to delete a ton of code as you said :)

@puerco This downloader code can be just a mage target now, no ?
I meant to say that there's no point of having the downloader code shipped into bom binary. It can live in magefile instead

there's no point of having the downloader code shipped into bom binary
Yes, if at some point we want to validate against a previous version of the license list, we need to get them. OTOH we can download the archive in one go (as mentioned above) and we can strip the parallel everything as we only need one file.


outdated...

sorry guys but this def does NOT remove all of the bloatware*,  the script is outdated

m$ solitaite
Xbox gamebar (yes still even it trying to remove that crap, this still exist)
Your phone
thanks!

It's in the default whitelist, I think. I'm not sure why. Edit it yourself and make a pull request, if you want to remove it so badly, but if this is just going to complain about the software, please close the issue.

whatever you say..


Quiz Extension

Is your extension request related to a problem? Please describe.
I will make a Quiz Extension in which the user will see a question and then will have to guess the correct answer.
Describe the solution you'd like.
I will use HTML,CSS ,JS.
Describe alternatives you've considered.
.
Add any other context or screenshots about the extension here.
I am contributor at GSSoC '22. Please assign this issue to me.
@harshita214

I would like to work on this
@harshita214

@Sukriti-m will you be working on this? @srishtig2412 Since @Sukriti-m  asked first, let her decide.

@Sukriti-m will you be working on this? @srishtig2412 Since @Sukriti-m asked first, let her decide.

Yes, I'd like to work on this.

@Sukriti-m Kindly create a PR by EOD


Double the default allowed table elements

This commit doubles the default allowed table elements per table in the pooling allocator from 10k to 20k. This helps to, by default, run the module produced in #8504.

Good catch 👍


changed face mapping so people can automate tool supply for this machine

changed face mapping so people can automate tool supply for this machine

Hey yeah thats a good idea actually

Hey, the release with your changes is out now. https://minecraft.curseforge.com/projects/cyclic/files/2454864
Took a few days since i wanted to roll in all my other new stuff at the same time. Enjoy!


No actual CPU/memory usage on Web UI after upgrading to distributed-1.20.2/dask-0.16.0

After upgrading to distributed-1.20.2/dask-0.16.0, CPU/memory usage on workers page cannot reflect real usage. Every host shows 8% or 10% CPU usage and <5% memory usage all the time. Jobs can finish without any problem. Just can not see any CPU/memory usage change.

Before upgrading, I'm using distributed-1.19.3/dask-0.15.4. I can see the usage change when running any job.

Unfortunately I'm unable to reproduce this.  Things seem to respond normally for me.  A couple things to check:

Verify that you've created a client where you're running jobs and that that client is pointing to this cluster.  Maybe it's using a different set of resources?

Look at the other pages in the dashboard to verify that computations are being run and that memory is being used.  As a simple example, perhaps try to persist some data on the cluster with the following:
import dask.array as da
x = da.random.random((20000, 20000), chunks=(1000, 1000)).persist()

It's same job running on same cluster. The only difference is dask/distributed version.
My use case is using subprocess.Popen to run another script in a new process:
process = Popen(
    command,
    stdin=PIPE,
    stdout=PIPE,
    stderr=STDOUT,
    shell=True
)
process.communicate()

Seems the resource usage of new process is not collected. Same code works well with old versions (distributed-1.19.3/dask-0.15.4).

Can you reproduce this issue? We are very interested in dask after your presentation to our team. Popen may not be a good use case for dask. We just start testing dask cluster with existed executable scripts.

I have not run into cases where the dashboard doesn't operate well.  It shows memory as measured by psutil.Process().memory_info().rss.  If you were concerned about the accruacy of the dashboard you might check your workers memory use while operating by using the Client.run method
import psutil
def get_memory():
    return psutil.Process().memory_info().rss

client.run(get_memory)

Maybe we used to measure it differently before?  Maybe we used vms?
If your tasks are running in a separate process then I wouldn't necessarily expect them to be counted under rss.

Maybe children(recursive=True) ?
in https://github.com/dask/dask/blob/105649e2fdb36981529c9f267630e48ed8e88ff2/dask/diagnostics/profile.py#L225

Also, .cpu_percent() will return the percentage of time spent in this process, since last call.
But the code re-instanciates the children at each loop, so the .cpu_percent() will always be 0 for children, be it recursive or not.
Only self.parent has a correct value.

That code isn't used for the dashboard.  That's used for the single-machine scheduler's diagnostics.

Not saying it's not wrong, just that it's not related to the issue you were seeing.
I'm also surprised by what you say, because that diagnostic has been used for a while and, if memory serves, provided non-zero results.

This conversation seems to have stalled.  Closing.

Yes, and the problem is probably more in https://github.com/dask/distributed/blob/0dedc514caa08d7a177a13c8cc745fd22aaabb20/distributed/system_monitor.py#L48 than in dask itself.


IGNITE-17395 Thin 3.0: Design Client Partition Awareness [POC]

https://issues.apache.org/jira/browse/IGNITE-17395
https://cwiki.apache.org/confluence/display/IGNITE/IEP-95+Client+Partition+Awareness

Closed: proof-of-concept does not need to be merged.


Support an implicit many-to-many relations

This is a good tool. Thank you!
As of now, it seems that implicit m-n-relations are not illustrated, it would be good to support it as well.
model Post {
  id         Int        @id @default(autoincrement())
  title      String
  categories Category[]
}

model Category {
  id    Int    @id @default(autoincrement())
  name  String
  posts Post[]
}

Oh, I hadn't known that prisma starts supporing implicit M: N relationship.
By the way, generated schema is extremely ugly. I'll support this feature, but recommend not to use it.

Upgrade to v1.0.3, then be supported.

Thank you for the quick response!

@yubrot Upgrade to v1.0.4.
Previous version has a bug that misunderstanding self-recursive 1: N relationship as implicit M: N relationship.
Therefore, previous version may draw non-existing table and diagram for that.


Postfix Header Checks loading error

Upon clicking on Header Checks the following is printed to console
Uncaught Error: Syntax error, unrecognized expression: label[for="d_/^Content-(Disposition|Type).*name\s*=\s*"?(.*(\.|=2E)(ade|adp|asp|bas|bat|chm|cmd|com|cpl|crt|dll|docm|exe|hlp|ht[at]|inf|ins|isp|jse?|lnk|md[betw]|ms[cipt]|nws|\{[[:xdigit:]]{8}(?:-[[:xdigit:]]{4}){3}-[[:xdigit:]]{12}\}|ops|pcd|pif|prf|reg|sc[frt]|sh[bsm]|swf|vb[esx]?|vxd|ws[cfh]))(\?=)?"?\s*(;|$)/ix"]
package.min.js?1551:8
The page infinitely spins and red loading bar is stuck at end.

As workaround, click ESC key or loader close button to dismiss loading page.
I will try to reproduce the issue a bit later.

What version of the theme are you using? I can't reproduce the issue? When I click on Headers Check all loads fine?

Version 15.51
It only happens on one server with the following check:
/^Content-(Disposition|Type).*name\s*=\s*"?(.*(\.|=2E)(ade|adp|asp|bas|bat|chm|cmd|com|cpl|crt|dll|docm|exe|hlp|ht[at]|inf|ins|isp|jse?|lnk|md[betw]|ms[cipt]|nws|\{[[:xdigit:]]{8}(?:-[[:xdigit:]]{4}){3}-[[:xdigit:]]{12}\}|ops|pcd|pif|prf|reg|sc[frt]|sh[bsm]|swf|vb[esx]?|vxd|ws[cfh]))(\?=)?"?\s*(;|$)/ix
Perhaps it does not like the " near the end? ?"?\s*(;|$)/ix

At first, please update the theme to 16.01. Then restart Webmin using console by running /etc/webmin/restart :) Try again and tell us what you got?

That fixes it :)


docs: add docs for 3.0.0 version (ebpf + lite)

Looks good to me.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Refactoring react-native-navbar

I was going to review it and I did even though you have already merged it :+1: . Seems really good! I'm going to upgrade my app to use it and let you know if I find any bugs. :+1:

yeah, sorry, wanted to release it yesterday :smiley:


Menu 20: No EXIT at OFF

Hi 1O11.
if I set BACKL to OFF and want to exit it won't let me exiting. But I like to exit again ;) Values above OFF working.

Couldn't find my way back to the backlight menu option after turning it off on mine lol.
Anyway, hopefully fixed. Let me knoiw.

Use a flashlight to get back. LOL. Tnx. I'll try...

Hello 1O11. Works like a charm again. :)

Sorry. I've to reopening it. EXIT on light OFF doesn't work.

Did you do a re-do commit here? A few 10 minutes ago it worked?!

It seems only to do it under certain sequences, looking for the bug now.

Right, I found it this time.
Plus I've made the backlight come on when you go the backlight menu no matter what it's set to - so the user can see what they are doing (I couldn't see any text due to low light level in the room)  !

Now it stays on >=10 seconds at OFF.

...until I reach BLIGHT menu??? hahahaha then its turning on?!

Only while your setting/changing the menu option, once the light goes off it won't come back on, until you visit the backlight menu again.
I've done that because the screen can't be seen in low light conditions, so finding the backlight menu is possible if the light comes on for that 10 seconds when you cross the backlight menu.

Got it. It's more intelligent Light management if light stays on whole time at menu? and if you quit it: turn light off immediately if menu quitting with exit button? ( in later version) ;)

but: no exit at LIGHT OFF is closed now.