Server error from Groq API in Whispering

Getting this error.
Windows 10
Server error from Groq API
file must be one of the following types: [flac mp3 mp4 mpeg mpga m4a ogg opus wav webm]
when i look in recordings and download it's a webm file so unsure what's happening.
Have tested whisper in groq playgorund and it's working.

No problem! Just an update, Some people in the groq discord are reporting issues as well, with other apps and the playground so perhaps it's just a temporary groq issue that will be resolved in due course

Just a heads up that it seems to have resolved itself today!

Resolved


pass exception information to javascript for possible handling

Closes #291 - save a resolve and reject pointer for promises returned by calling python functions

Added some examples as well, let me know if you want the readme updated...for now I left that out due the try/catch being a tad more complex.

Anything else needed for this pull request to be considered?

Hi @Kevinrp01 - thanks for the PR. It looks good to me but I'd be keen to get @ChrisKnott's opinion.

Yes, I think this is fine. It is technically a breaking change but I don't feel like we ever guaranteed behaviour in the case of exceptions.
It makes particular sense for JS heavy apps that make occasional calls to py.
Is there an easy way to do the reverse? Raise uncaught js exceptions back to python?

Good point, I'll see about adding that as well

I am not familiar enough with python equivalent of promises and couldn't figure out a way for an exception to be generated such that the user function could handle it...so instead, I just extended the callback flow and so users can provide a 2nd callback function that will be called if an error occurs.
failure callback takes error message (simple string), and error stack (full javascript failure stack)

@ChrisKnott just checking in on this again in case you have any more input or changes requested

Sorry I didn't get a chance yet, I reckon just ship this half of it and if I ever get time I can look into adding the reverse for Python side.

Thanks for the contribution @Kevinrp01 👍


Any way to include jetpack via es6 module import syntax?

Is it possible to include this library into a project via the import syntax?
import { wordwrap } from 'd3-jetpack'
And just pull off one function like wordwrap?

Working on it now! Should be done in a couple of days.


doc: fix and improve bundle command info

Description of the change:

remove the link for the https://github.com/openshift/enhancements/blob/master/enhancements/olm/operator-bundle.md#docker
add in the command help the relevant info as in the CLI docs
fix the examples since the layout project has no longer the dir directory
add the links for the relevant docs and places instead of the OCP enhancements
fix the layout issues for the command line and docs.

Motivation for the change:
Closes #2880
Related to: #2998

HI @estroz,
The steps and some info are wrong and as you can check users has been facing issues with as I did. So, I will add comments and ping you directly in the changes performed with the reasons so it may makes its more clear.

/hold
we decide to split the changes here to be easier to make the review.

Done in others PRs


Improve Python debugger handling of multiple function apps in the workspace

The Python debugger can also handle one function app in each workspace. If more than one function app is present it will only launch the last function app listed in tasks.json. In the example below only function-app-2 will be opened in the debugger, unless the json objects associated with are deleted.
The desired behavior would be an option to choose which function should attach to the debugger.
{
	"version": "2.0.0",
	"tasks": [
		{
			"type": "func",
			"command": "host start",
			"problemMatcher": "$func-python-watch",
			"isBackground": true,
			"dependsOn": "pipInstall",
			"options": {
				"cwd": "${workspaceFolder}/function-app-1"
			}
		},
                {
			"type": "func",
			"command": "host start",
			"problemMatcher": "$func-python-watch",
			"isBackground": true,
			"dependsOn": "pipInstall",
			"options": {
				"cwd": "${workspaceFolder}/function-app-2"
			}
		}

@adiazulay does this help you: https://github.com/microsoft/vscode-azurefunctions/wiki/Multiple-function-projects

@ejizba looks like option 2 should work, I'll test it and let you if it works for my use case.

@ejizba That worked when I followed the example, but I wasn't able to get it to work with a project I already created.

@ejizba That worked when I followed the example, but I wasn't able to get it to work with a project I already created.


Added logfile rotation and removal

Added logfile rotation and removal when they are using too much space.

Thanks for the PR. There's a lot in here that isn't specific to this project (estos etc). I've fixed the identifier issue with the defaultInstance. I've very curious about your commit https://github.com/jollyjinx/XCGLogger/commit/744a58e5d3705c9125fa6577bd899606924d3955 . Wondering how a Windows user is using this library?

It's for customer care that uses windows. And unzipping colons is problematic for Windows users.


[Feature request] Is it doable that allow {select} variable in template?

When I want to select a range of text, and then I want quick add it to my kanban or other notes.
if it is doable to make current select as a variable like {select}？

Hey! Thanks for the suggestion.
I adapted {{VALUE}} to do this. If any text is selected, {{VALUE}} will get it. If not, you'll be prompted as usual.


page.pdf error: Alpine docker image fails on pdf()

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.18.0 || 1.18.1
Platform / OS version: Alpine Linux Docker image
URLs (if applicable):
Node.js version: 10/11

What steps will reproduce the problem?
Please include code that reproduces the issue.

Just try to generate a pdf in a alpine linux image

What is the expected result?
Generate pdf
What happens instead?
Returns an error, i guess it's related to chrome version. On npm pupppetter is using 77, but alpine it's still on 73.
(node:123) UnhandledPromiseRejectionWarning: Error: Protocol error (IO.read): Invalid parameters handle: string value expected\n    at Promise (/app/node_modules/puppeteer/lib/Connection.js:183:56)\n    at new Promise (<anonymous>)\n    at CDPSession.send (/app/node_modules/puppeteer/lib/Connection.js:182:12)\n    at Function.readProtocolStream (/app/node_modules/puppeteer/lib/helper.js:238:37)\n    at Page.pdf (/app/node_modules/puppeteer/lib/Page.js:943:25)\n    at process._tickCallback (internal/process/next_tick.js:68:7)\n
Probably it's related to this: https://github.com/GoogleChrome/puppeteer/pull/4587
I'm using 1.17 meanwhile.

Please use a matching chromium version: https://github.com/GoogleChrome/puppeteer#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy


Emit declaration files

Hi @langley-agm,
This is second attempt to help resolve issue with build tools like Webpack going crazy when referencing this package (#39 and #65). My previous PR #70 did not in fact solve problem that Webpack should not compile files that are already included in dist folder. Here comes my solution:

Let's put ES5 node-compliant files into dist/es5 folder
Allow TS compiler to emit declarations both for ES5 and ES6 formats
Let's make ES5 output default since any bundler is going to like this moduie format. That way, you can reference logger by just typing:
import { Logger } from 'angular2-logger';
no matter if you write in ES6 or TS.

Of course, referencing by import { Logger } from 'angular2-logger/core'; will still works for users that used it before.

Question @orkisz ,
Would it make a difference if we replace all your changes for only this one:
typings": "core.d.ts ?

I'm afraid no. As long as main file points out to core.js in root folder, Webpack is going to compile TSes (remember, core.js imports those!).

core.js imports a name without an extension, you decide what extension to look for, doesn't have to be .ts

One another pros of my solution is defaulting to ES5 build. Please take into consideration that ES5 commonJS module is most widely used format of NPM modules and it is unlikely to cause any troubles in wide range of bundlers.

isn't the current core.js in the root es5?

Yes, it is. The problem is when using imports without file extension, Webpack loaders will use TS files.

Let me try approach with just typings statement in package.json...

@langley-agm Confirmed: just adding "typings": "core.d.ts" did not help. Webpack still tries to compile TS

The problem is when using imports without file extension, Webpack loaders will use TS files.

Supposing it does this by default which I doubt, to me its angular cli configuring it that way, can't you change this configuration?

Confirmed: just adding "typings": "core.d.ts" did not help. Webpack still tries to compile TS

We already know this. What I will look for is how to change the configuration so it does not do this.

Similar to how the angular team uses SystemJS:
rxjs: {         defaultExtension: 'js'       },
They specify that whenever rxjs is requested, the loader will use .js for the extension.
Remember webpack is merely a bundler, it does not compile. Angular cli is the link between your code, webpack and typescript configuring it in a certain way.

I don't use angular-cli, but plain Webpack. Maybe I can reconfigure it to take js files before ts, but can you ensure me that it won't cause other modules to fail?
I can't get it. There is something obviously wrong with your build process:

Destination files go to same directory as source (app) - bad practice
Import process is different depending on end-user bundler configuration
but after many pages of conversation (#39 and #65) you still deny to admit it. Can you at least tell me what is wrong in approach proposed by me in this PR?

I don't use angular-cli, but plain Webpack. Maybe I can reconfigure it to take js files before ts, but can you ensure me that it won't cause other modules to fail?

You configure this module, not a global configuration, just like the example I showed you configures only rxjs.

but after many pages of conversation (#39 and #65) you still deny to admit it

I haven't said there isn't anything wrong with the current build process once. What I've said a million of times is that you should not compile third party libraries and I want to find the root cause of this issue that is making your project do so. Not a workaround patch. I haven't said any of these PRs is wrong, there's a reason they are still open after all.  What I'm trying to do is to get clear on the assumptions we're making. As far as I understand Webpack has no idea of Typescript and as such it cannot compile them, I can be wrong, that's why I said I'll search into it.

Destination files go to same directory as source (app) - bad practice

Do you have any official source of this? Someone actually saying its bad practice? These technologies are far too new to decide over best practices yet imho, even the Angular team keeps changing them in a matter of months, not so long ago they had them the way I do. I'm not saying they're correct the way they are but lets not make wrong assumptions just for the sake of doing them.

Import process is different depending on end-user bundler configuration

This is definitely not a goal, and to correctly fix it I need to find the root cause of the problem. Note that the current importing process is the same as in the Quickstart Angular page, trying to look for something similar with Webpack is the opposite of a different process, is actually looking a way to do it the same way.

I don't use angular-cli, but plain Webpack. This is interesting could you share an example? Are you not using any third parties that augment webpack?

You configure this module, not a global configuration, just like the example I showed you configures only rxjs.

I believe it's not possible in Webpack...

As far as I understand Webpack has no idea of Typescript and as such it cannot compile them, I can be wrong, that's why I said I'll search into it.

Ok, I'm going to comment it in the end of this message.

Do you have any official source of this? Someone actually saying its bad practice?

I don't think there is any official source. Just my practice, few samples:

Cleaning before build - just rimraf dist,
.gitignore have dist folder and .npmignore have src
But OK, maybe I went too far considering my opinions as standard

Let me know you why it's so important to me. I like your logger, I really do. For me, there is no equivalent available yet. But I must go live with my app migrated to ng2 final (TS compiler version 2...) before Monday EOD and this is only module causing build to fail. I can either do a) fork and publish my version of module (what I don't want do to since it's your work and additionally I don't want to loose easy-to-get updates from you) b) use other logger (but time window is tight to do so) c) completely get rid of logging facility.
Please at least tell me if there is any chance you will consider changes in build process until Monday. If no, I'm going choose a, b or c. There is simply no time for discussion for me if it is pointless.

I actually have an idea for a very quick-fix: let's just add .ts files to .npmignore. This will remove a root cause of the problem.
As a follow up to previous message: I think an action is required since more and more people will migrate to ng2 final next week and they will experience the same issue.

@orkisz

Please at least tell me if there is any chance you will consider changes in build process until Monday

I will not consider any changes until I find the root cause of the issue. Most likely it won't be by Monday.
My suggestions:
Option 1- Try the officially released version of Typescript 1.8 instead of 2+, which should not give you this error. If Angular doesn't work with it anymore try option 2.
Option 2- Point to either your fork or deity's until next week when I fix this specific error. This is a very powerful feature of git and npm, no reason to disregard it =).
A note of advice: I will try to keep it as import { Logger } from 'angular2-logger/core.

I actually have an idea for a very quick-fix: let's just add .ts files to .npmignore. This will remove a root cause of the problem.

It will just hide it, there is a value on having those files in the distribution, I won't remove them.

Ok, I will follow option 2. then. But let me try to point you out what in my opinion causes problems.
Let's look on your app's source structure:
core.ts
app
     |
     core
           |
           ---logger.ts
           ... and other files

core.ts contains:
export * from "./app/core/level";

That how it is, right? So now we compile sources and we get:
core.ts
core.d.ts
core.js
app
     |
     core
           |
           logger.ts
           logger.d.ts
           logger.js
           ... and other files

So far so good, right? So let's suppose we're lazy and forgot to clean all dist files before next compilation.
Now we invoke tsc again and what it does it basically takes core.ts and import all depencencies. But wait, now we have both logger.ts and logger.js... Do we care? No, because tsc compiles .ts files, not .js so they do not matter at all!
If it was opposite, the source code would never be compiled more than once since tsc would always take precompiled JSes as source of truth. Do you agree?
Now, we get back to my Webpack process. The loader for TypeScript is just a wrapper around tsc so it behaves identically. It does not matter for it that npm package exposes js file as entry point; it's main responsibilty is to compile TypeScripts. If export statement has references both to TS and JS it will always take TS. Still logical?
Now, basically, you ask me and other people having same problem to override this very logical process just for your package. Does it make sense?
And just to ask - what is the reason to keep sources in NPM? (just asking!)

@orkisz

So far so good, right?

There's no core.ts, there's only core.d.ts, that's why you should not go find the ts files because the .d.ts file already has everything that typescript needs.

The loader for TypeScript is just a wrapper around tsc so it behaves identically. It does not matter for it that npm package exposes js file as entry point; it's main responsibilty is to compile TypeScripts.

Wrong, once again the loader does not compile, you can add this functionality through plugins that will handle tsc, but that's nowhere near its main responsability, its main responsability is to load files, in this case it should load js files.

Now, basically, you ask me and other people having same problem to override this very logical process just for your package.

Never did such a thing.
For reference I just followed both new Quickstart Guides in Angular 2's Web Page and none of them gave this issue even though its using typescript 2+.
https://angular.io/docs/ts/latest/quickstart.html
https://angular.io/docs/ts/latest/guide/webpack.html
So its definitely an issue with your configuration.
I wonder if this part has something to do with it (from webpack.common.js):
resolve: {
    extensions: ['', '.js', '.ts']
},

Does it prioritize adding js before ts?
I only followed their webpack guide, installed the angular2-logger and that's it, I didn't have to configure anything at all.
Now that I've seen its behaving just fine without changes even when using webpack I'm going to fix the
"Type 'string' is not assignable to type 'Level'." error. But I highly suggest that If you were getting this error you take a look at your webpack configuration because compiling third party libraries will make your build proccess ineficient to say the least.


when run i got this error without add any code for cloud_firestore

when run i got this error without add any code for cloud_firestore
Launching lib\main.dart on sdk gphone x86 in debug mode... C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:13: error: cannot find symbol import com.google.firebase.firestore.AggregateQuery; ^ symbol: class AggregateQuery location: package com.google.firebase.firestore C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:14: error: cannot find symbol import com.google.firebase.firestore.AggregateQuerySnapshot; ^ symbol: class AggregateQuerySnapshot location: package com.google.firebase.firestore C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:15: error: cannot find symbol import com.google.firebase.firestore.AggregateSource; ^ symbol: class AggregateSource location: package com.google.firebase.firestore C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\streamhandler\TransactionStreamHandler.java:19: error: cannot find symbol import com.google.firebase.firestore.TransactionOptions; ^ symbol: class TransactionOptions location: package com.google.firebase.firestore C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestoreMessageCodec.java:412: error: where(Filter) is not public in Query; cannot be accessed from outside package query = query.where(filter); ^ C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:536: error: cannot find symbol AggregateQuery aggregateQuery = query.count(); ^ symbol: class AggregateQuery location: class FlutterFirebaseFirestorePlugin C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:536: error: cannot find symbol AggregateQuery aggregateQuery = query.count(); ^ symbol: method count() location: variable query of type Query C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:537: error: cannot find symbol AggregateQuerySnapshot aggregateQuerySnapshot = ^ symbol: class AggregateQuerySnapshot location: class FlutterFirebaseFirestorePlugin C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestorePlugin.java:538: error: cannot find symbol Tasks.await(aggregateQuery.get(AggregateSource.SERVER)); ^ symbol: variable AggregateSource location: class FlutterFirebaseFirestorePlugin C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\streamhandler\TransactionStreamHandler.java:72: error: package TransactionOptions does not exist new TransactionOptions.Builder().setMaxAttempts(maxAttempts).build(), ^ Note: C:\Users\AppData\Local\Pub\Cache\hosted\pub.dev\cloud_firestore-4.5.2\android\src\main\java\io\flutter\plugins\firebase\firestore\FlutterFirebaseFirestoreMessageCodec.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 10 errors

FAILURE: Build failed with an exception.

What went wrong: Execution failed for task ':cloud_firestore:compileDebugJavaWithJavac'.
Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org/
BUILD FAILED in 7s Exception: Gradle task assembleDebug failed with exit code 1 Exited (sigterm)

minSdkVersion 21
my pubspec.yaml
intl: ^0.18.0 shared_preferences: ^2.1.0
firebase_core: ^2.10.0
firebase_auth: ^4.4.2
google_sign_in: ^6.1.0
cloud_firestore: ^4.5.2
any solution

@MTEV
Can you provide flutter doctor -v ?
Also, try flutter pub cache repair followed by flutter pub get to see if it helps or not.

flutter pub cache repair nothing  solve  same issue
and -pubspec.yaml
name: mynew
description: A new Flutter project.
The following line prevents the package from being accidentally published to
pub.dev using flutter pub publish. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number is used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
In Windows, build-name is used as the major, minor, and patch parts
of the product and file versions while build-number is used as the build suffix.
version: 2.4.0+14
environment:
sdk: '>=2.18.1 <3.0.0'
Dependencies specify other packages that your package needs in order to work.
To automatically upgrade your package dependencies to the latest versions
consider running flutter pub upgrade --major-versions. Alternatively,
dependencies can be manually updated by changing the version numbers below to
the latest version available on pub.dev. To see which dependencies have newer
versions available, run flutter pub outdated.
dependencies:
flutter:
sdk: flutter
carousel_slider: ^4.2.1
http: ^0.13.5
date_field: ^3.0.0
sign_button: ^2.0.3
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^1.0.2
flutter_login_facebook: ^1.7.0
syncfusion_flutter_gauges: ^21.1.35
material_dialogs: ^1.1.4
animate_gradient: ^0.0.2
validators: ^3.0.0
awesome_dialog: ^3.0.2
custom_radio_grouped_button: any
intl:
shared_preferences: ^2.1.0
firebase_core: any
firebase_auth: any
google_sign_in: ^6.1.0
cloud_firestore: ^4.5.2
firebase_core: ^2.10.0
firebase_storage: ^11.1.1
#cloud_firestore: ^4.5.2
firebase_messaging: ^9.0.0
firebase_auth: ^4.2.2
google_sign_in: ^6.1.0
firebase_core_platform_interface: ^4.6.0
cloud_firestore: ^4.5.2
dev_dependencies:
flutter_launcher_icons: ^0.13.1
change_app_package_name: ^1.1.0
flutter_icons:
android: "launcher_icon"
ios: true
image_path: "images/logoapp.png"
min_sdk_android: 21
flutter_test:
sdk: flutter
The "flutter_lints" package below contains a set of recommended lints to
encourage good coding practices. The lint set provided by the package is
activated in the analysis_options.yaml file located at the root of your
package. See that file for information about deactivating specific lint
rules and activating additional ones.
flutter_lints: ^2.0.0
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter packages.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
To add assets to your application, add an assets section, like this:
assets:
- images/a_dot_burr.jpeg
- images/a_dot_ham.jpeg
assets:
- images/intro_bg.jpg
- images/intro_bgb.jpg
- images/logoapp.png
- images/assets/logo_footer.png
- images/assets/logo_head.png
- images/assets/logo.png
- images/assets/google.png
- images/assets/facebook.png
- images/assets/user_password.png
- images/assets/icon_eye_close.png
- images/assets/icon_eye_open.png
- images/assets/apple.png
- images/assets/icon_password.png
- assets/logo_footer.png
- assets/logo_head.png
- assets/logo.png
- assets/google.png
- assets/facebook.png
- assets/user_password.png
- assets/icon_eye_close.png
- assets/icon_eye_open.png
- assets/apple.png
- assets/icon_user.png
- assets/icon_password.png
- assets/alogoapp.png
#- assets/background.png
An image asset can refer to one or more resolution-specific "variants", see
https://flutter.dev/assets-and-images/#resolution-aware
For details regarding adding assets from package dependencies, see
https://flutter.dev/assets-and-images/#from-packages
To add custom fonts to your application, add a fonts section here,
in this "flutter" section. Each entry in this list should have a
"family" key with the font family name, and a "fonts" key with a
list giving the asset and other descriptors for the font. For
example:
fonts:
- family: Lobster-Regular
fonts:
- asset: fonts/Lobster-Regular.ttf
- asset: fonts/Schyler-Italic.ttf
style: italic
- family: Trajan Pro
fonts:
- asset: fonts/TrajanPro.ttf
- asset: fonts/TrajanPro_Bold.ttf
weight: 700

For details regarding fonts from package dependencies,
see https://flutter.dev/custom-fonts/#from-packages
dependency_overrides:
intl: ^0.18.1

@MTEV Can you provide flutter doctor -v ? Also, try flutter pub cache repair followed by flutter pub get to see if it helps or not.
not working

Can you try by creating a new Flutter project, add required flutterfire plugins like core, auth and firestore and try to run and see if you still get the same error or not ? That way you can check if any other plugin you might be using could be causing the conflict or not.

same issue

Can you try by creating a new Flutter project, add required flutterfire plugins like core, auth and firestore and try to run and see if you still get the same error or not ? That way you can check if any other plugin you might be using could be causing the conflict or not.

same issue

can you try create new project and  just add    cloud_firestore: ^4.5.2
and telll me  if working
just write
flutter run

Can you try by creating a new Flutter project, add required flutterfire plugins like core, auth and firestore and try to run and see if you still get the same error or not ? That way you can check if any other plugin you might be using could be causing the conflict or not.

can you try create new project and just add cloud_firestore: ^4.5.2
and telll me if working
just write
flutter run

I tried as above and was able to run the app properly without the reported error:
Building with Flutter multidex support enabled.
Running Gradle task 'assembleDebug'...                             10.2s
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app-debug.apk...           4.3s
Syncing files to device Android SDK built for x86...                99ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

💪 Running with sound null safety 💪

An Observatory debugger and profiler on Android SDK built for x86 is available at: http://<IP_ADDRESS>:62895/frowBbZKIuo=/
The Flutter DevTools debugger and profiler on Android SDK built for x86 is available at: http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:62895/frowBbZKIuo=/

Maybe try switching to latest master and run again. Also check what gradle build and Android SDK version you are using that might be leading to the error.


SetupSignalHandler changed to secure single execution

Although SetupSignalHandler is implemented to panic when called twice, it is possible to secure single execution without panic by using sync.Once
Signed-off-by: kpango<EMAIL_ADDRESS>

Thanks @kpango!
I am not certain we want to do this. In my mind, SetupSignalHandler should only be called once in main, but this opens up the possibility of calling it multiple times. Would love to hear other thoughts around this though.

Hey @kpango going to close this for now, if you have any thoughts or feedback from @alexbrand's comments, please reopen and we can discuss.


The padding of the dialog content should be set to 0

If the dialog has an action container, the content container of the dialog should have a padding of 0. Otherwise, the gap between actions and content is too great.
Actual:

Expect:

@buseselvi can you comment about this?

Good point! Since there is padding at the top of the footer where the buttons are located, the two paddings together lose some space. So we may not give any padding to the bottom of the content.
But of course, in the case where the button footer is not used on the dialog component, still, there should be a 24 px padding from the bottom. @muratcorlu @Enes5519


MAIN B-19902 locking moves and UI changes

INTEGRATION PR
ISSUE FIX PR
Agility ticket
Summary
In order to "lock" moves while office users are working on them, we must initially set that lock and then display the relevant UI elements to inform the users that the move is currently being worked on at a glance (when viewing their queue) as well as who is working on the move (after entering the move).
This PR does the following:

updating all database queries done when searching and viewing queues to pull in foreign key values from the office_users table
updating swagger definitions with newly introduced values
created new service object to lock a move with office user that is locking it and 30 minute expiration timer
created component for LockedMoveBanner.jsx
added lock icon to all queues that conditionally renders on values in move
wrapped all relevant UI code in feature flag checks for move_code feature flag

How to test

In your envrc, turn FEATURE_FLAG_MOVE_LOCK to true
Fire up client & server
Log in as an office user (can use multi role for efficiency)
Enter any move as TOO/TIO/SC
Log out
Log back in as another user
When your queue loads, you should be able to see a lock icon to the left of the move that the previous user entered (we are simulating them "working on it")
Enter the move
You should see a banner displayed at the top of the screen of the first & last name of the user that is "working on it" as well as their transpo office
The lock icon & banner will display until the time in lock_expires_at passes, but if any office user enters the move after that time, it will be reset to 30 minutes. Future work will be done to clear these values when the user returns to their queue. Right now they will stay in the database, but UI elements will conditionally render.
Within each office role, view queues, perform searches, and the lock icons should still be visible in the queue - if the lock icon is on the move, the banner should display if you are NOT the user that has it locked

Screenshots
TOO view with locked moves

TOO search with locked move

TIO with locked moves

SC with locked moves in counseling queue & PPM closeout queue

Banner that displays when user is viewing a locked move - read only permissions are being handled in later stories

Looks like there are some differences.

swagger-def has a different placement of orderType in the definition. Not sure why that is, but it still exists in the SearchMoves definition.

Could I also get a Happo check from someone? Due to the added LockedMoveBanner component.
Thanks!

Happo accepted

Swagger "Affiliation" is also missing from the commit history.. But I see it is present in main. Very odd

Yeah I noticed that, too. I went through and checked everything to make sure it was all working and didn't find anything fishy, so.. who knows.

Many discrepancies already present between main and diff
See conflicts https://github.com/transcom/mymove/pull/12044


Tolerations added to helm values not being added to the actual deployment

Description
Observed Behavior:

Expected Behavior:

Reproduction Steps (Please include YAML):
Versions:

Chart Version: 0.37
Kubernetes Version (kubectl version): 1.29

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What's your helm install command so I can reproduce? I just changed the values in my values.yaml and saw the tolerations apply.

@njtran
helm --kubeconfig=/home/consul/.kube/eks-dev.yml upgrade --install --namespace kube-system karpenter oci://public.ecr.aws/karpenter/karpenter --version 0.37.0 --set settings.clusterName=k8s-dev --set "serviceAccount.annotations.eks\.amazonaws\.com/role-arn=arn:aws:iam::408531640850:role/KarpenterControllerRole-k8s-dev"

Can anyone help here?


Add examples of dotnet core gRPC service invocation to samples

I am struggling to implement the invocation of a dotnet core gRPC service via Dapr, and no example exists in the samples project.
I have found an example in the Java SDK, and attempted to work from that (although I don't know Java), but I haven't managed to get it working, so some examples/documentation of how to invoke services over gRPC in C# would be greatly appreciated, including how to implement streaming calls.

I am using this (not sure if this is best practice, though). So any feedback welcome as well.
using static Dapr.Client.Grpc.Dapr;

var defaultPort = Environment.GetEnvironmentVariable("DAPR_GRPC_PORT") ?? "52918";
// Create Client
var daprUri = $"http://<IP_ADDRESS>:{defaultPort}";
var channel = GrpcChannel.ForAddress(daprUri);
DaprClient grpcClient = new DaprClient(channel);

var getStateEnvelope = new GetStateEnvelope()
{
	StoreName = "mystore",
	Key = myId,
};

var response = await grpcClient.GetStateAsync(getStateEnvelope);

if (!response.Data.Value.IsEmpty)
{
	// do something with the value
}

@sebader Thsi seems fine. We are int he process of refactoring our SDK and we will be providing wrapper methods for App-> Dapr calls which will under the hood use autogenerated gRPC clients from proto. This it he main issue tracking the work and it will be part of our next release https://github.com/dapr/dotnet-sdk/issues/197

@sebader thanks for your response - I had also managed to access the statestore and publish events over gRPC without difficulty, but this issue more specifically relates to the invocation of another microservice over gRPC and Dapr i.e. Service A <-> Service B becomes Service A <-> Dapr A <-> Dapr B <-> Service B.
I have subsequently managed to get this working, although I think I've discovered a couple of bugs in Dapr.Client.Grpc in the process. I'll create a sample repo and link to it when I get a chance.
@amanbha do you know whether the refactoring work will allow streaming calls from service - service over gRPC, or will they still be unary as they are at present? i think the lack of streaming calls will be a bit of a blocker for my app.

@TomHermolle The calls would be unary, the Dapr runtime itself doesnt support it.

With the refactored client the code snippet is added to samples https://github.com/dapr/dotnet-sdk/commit/51fc48fb743204d6e2a830bfb12568d1231fa410#diff-d43fb1cb49d2d5bea15afe07418dd112R87
Please feel free to reopen if you have more questions.


Is palindrom: Shorter version

Hey what about such isPalindrom implementation:
function isPalindrome(str) {
    str = str.replace(/\W/g, '').toLowerCase();
    return (str === str.split('').reverse().join(''));
}

While that is probably fine in practice, the isTextPalindrome implementation is tuned for performance as might be expected in a tech interview, only needing to iterate through n/2 items in the string. Your example does a lot of piping through functions which creates 5 new strings/arrays, all of which are O(n) operations.


⚠ Bofrost.lu has degraded performance

In d176073, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1410 ms

Resolved: Bofrost.lu performance has improved in 30cc327 after 37 minutes.


supabase client hangs after upgrade to v2.4.1

Bug report
Describe the bug
When I try to upgrade the supabase-js client to the latest release v2.4.1, program hangs after it has created supabaseclient.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

install v2.4.1 supabase-js client
create a simple file containing following code

import { createClient } from "@supabase/supabase-js";

const adminClient = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_ANON_KEY);

run node supabase-test.js
execution does not terminate. No error is displayed.

Expected behaviour
program execution should terminate.
If applicable, add screenshots to help explain your problem.
System information

OS: macOS
Version of supabase-js: 2.4.1
Version of Node.js:  18.3.0

Additional Context
Same program terminates when supabase-js is v2.4.0

Thanks for reporting this. Can you double check that it works in v2.4.0? I can reproduce the issue as far back as v2.0.0 - it works on v1.
I was also able to narrow this down to gotrue-js client constructor - can you reproduce the issue with this example?

@soedirgo I could reproduce the issue with the example.
Here's the repo where on running gotrue.js, it hangs.
I have noticed that this happens when gotrue-js client is set at v2.10.0. Any version below that works without any issue.

I have noticed that this happens when gotrue-js client is set at v2.10.0. Any version below that works without any issue.

Thanks! I'm also able to replicate this.


Running forever unless I print the size of the data structure

Hi All,
I wrote a piece of code that is running forever and I believe it should not.
The code is below.
Note that if rather than env.out.print("here forever ") I write env.out.print("here forever " + list.size().string()) then it behaves correctly, and it stops executing when it's supposed to.
I believe this is a bug.
I'm using the latest pony version (master branch). And this is happening on both MacOS and Ubuntu.
use "collections"
actor Main
  new create(env: Env) =>
    let n: I32 = 128
    let x: I32 = 6
    var list = List[I32]
    while (list.size() < 128) do
      env.out.print("here forever ")
      for d in Range[I32](4, x + 1, 2) do
        list.push(d)
      end
    end

Thanks in advance,
Juliana

I can confirm this. The code works correctly if you run a debug build without optimizations. Its an incorrect LLVM optimization of some sort.
@Praetonus could you take a look?

Seems like the for loop is optimized away.
Given this example, the print call inside the loop doesn't print anything.
actor Main
  new create(env: Env) =>
    var list = List[I32]

    while list.size() < 128 do
      env.out.print("here forever ")

      for d in Range[I32](0, 128) do
        env.out.print("..................................") // Never runs
        list.push(d)
      end
    end

Works properly if the for iterates over an Iterator from an Array instead of a Range.
actor Main
  new create(env: Env) =>
    var list = List[I32]

    while list.size() < 128 do
      for d in [as I32: 1,2,3,4,5].values() do
        list.push(d)
      end
    end

    env.out.print("Success!")

But if the Array is declared as a variable before the while loop, we get Illegal instruction.

This bug was introduced by commit #1080
This works prior to that commit but doesn't work afterwards:
https://github.com/ponylang/ponyc/commit/12ca5acecff41f4a17fc7bbcb52f58f3af1779ea

As part of a fix for this, we should add a test that verify this sort of code works going forward.

@Praetonus would it make sense to revert #1080 to solve the issue then try reimplementing sans issues?

@jemc @sylvanc it would seem that @Praetonus isn't around today, any objection to my reverting the offending commit and it could be reimplemented later?

@SeanTAllen - I worry that some later commits might be depending on it, but if it reverts cleanly, then I say go for it.

@jemc i tried reverting this. it became a nightmare. it looks like the only way to solve is to move forward from this and fix whatever it is in #1080 that is causing the bug.

I found a simple change that solves the problem for this particular repro, but I want to spend at least some time trying to figure out why there was a problem, and whether other bits of invariant information added in #1080 need to be removed as well.
If it starts taking a long time to figure out I will just file a PR with the fix that I don't yet understand.

I mostly figured out what was going on. though the details are fuzzy and I don't have additional time to resolve them at the moment.
See #1232.


Kinesis integration

Add connector for ingesting from Amazon Kinesis

Hi @mcvsubbu @npawar Yes, I am already working on this. It has been on pause for a while since I picked up JDBC driver.
The driver will need changes in SQL Parser so I am planning to  pick this up again and drive it to conclusion.

Created an issue because there wasn't one already

Looking at the voting result so far (https://poll.ly/#/2YeaKQ5o), We can probably get to this in q4.

Design doc: https://docs.google.com/document/d/1hFbzumQAGALAi8XZMOsVlwVHN-s2t37MA5QUfduL4Yk/edit#


Add support for host

:+1:
a bit surprised native support for including a host/ip isn't already available for this integration, absolutely needed in a load-balanced/distributed environment, esp. if underlying 'loggly' node.js library supports this argument already

:+1:

:+1: Yeah, this would be great to have!

@indexzero  anything stopping merging this PR in?

:+1:

Hey all, I was tripped up by the README on this. The host option does not allow a hostname to be sent with the logs. It is actually the destination for the logs to be sent to.
Setting it to os.hostname() as I did will silently break communication with Loggly, which is bad.
The default is logs-01.loggly.com, and I'm not aware of a use case to change that.
https://github.com/nodejitsu/node-loggly/blob/master/lib/loggly/client.js#L52
I would suggest reverting this, as it is breaks the transport silently. At a minimum, I can submit a PR to correct the README.

@bradfol thanks for finding this. An update to tests with a subsequent PR would be very helpful.

@bradfol @indexzero I misunderstood the purpose of host. Thanks for caching this. I would suggest undoing my PR, as there is not really a good reason to configure this. Apologies for troubles caused.

@indexzero @chris-rudmin Thanks guys. I've opened PR #35 to revert this.


DRUP-21-22-23: Default Media entities structure (Image, Video, File)

DRUP-21: Default Image Media entity
DRUP-22: Default Video Media entity
DRUP-23: Default File Media entity
This PR does the following:

Adds default field/form/display structure for media entities
Adds a simple Preview mode to be used throughout the admin area.

To Review:

[x] Checkout this branch.

[x] Clone the Sous-Project repo.

[x] Update that projects composer file so the "fourkitchens/sous": "dev-master", requirement on line 30 now points to this branch "fourkitchens/sous": "dev-feature-media/drup-21-22-23",

[x] Run composer install and setup a fresh Drupal site.

[x] Verify there are no config import errors during the install

[x] Go to http://sous-project.lndo.site/media/add and verify there are 3 media types

[x] Click on each one and verify the fields are organized into logical tabs and the field structure matches our data model: https://docs.google.com/spreadsheets/d/1_u-FVCzh1v1z082p7SiNMRq5hBaYKFK9G3lGUUYLpDQ/edit#gid=1974210121

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

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


[SPARK-529] [sql] Modify SQLConf to use new config API from core.

Because SQL keeps track of all known configs, some customization was
needed in SQLConf to allow that, since the core API does not have that
feature.
Tested via existing (and slightly updated) unit tests.

Test build #52622 has started for PR 11570 at commit 884926c.

Test build #52622 has finished for PR 11570 at commit 884926c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    .doc(\"The output committer class used by Parquet. The specified class needs to be a \" +
    .doc(\"A comma separated list of class prefixes that should be loaded using the classloader \" +
    .doc(\"A comma separated list of class prefixes that should explicitly be reloaded for each \" +

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52622/
Test PASSed.

Merged build finished. Test PASSed.

Test build #52879 has started for PR 11570 at commit ffa69ea.

Test build #52879 has finished for PR 11570 at commit ffa69ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52879/
Test PASSed.

Merged build finished. Test PASSed.

Ping anyone?

Another friendly ping.

Test build #53115 has started for PR 11570 at commit c18fa66.

Test build #53115 has finished for PR 11570 at commit c18fa66.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53115/
Test PASSed.

Merged build finished. Test PASSed.

Another ping? Fixing conflicts is getting kinda boring.

Test build #53233 has started for PR 11570 at commit a69cb89.

Test build #53233 has finished for PR 11570 at commit a69cb89.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53233/
Test FAILed.

Test build #53244 has started for PR 11570 at commit 96ee1d7.

Test build #53244 has finished for PR 11570 at commit 96ee1d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53244/
Test PASSed.

@vanzin I don't think anybody gets a ping message unless you explicitly cc them. Will take a look.

@rxin yes but it moves to the top of https://spark-prs.appspot.com/#sql. And people do use that, right?

BTW, a different approach where the list of known configs is kept by the code in o.a.s.internal.config would make this change simpler. The main reason I didn't do that is because initialization of these conf variables relies on triggering static initialization of classes, which may not happen in all cases, so there might be missed duplicates.

@rxin did you have a chance to think about this? I addressed some comments you made in the other PR and simplified the SQLConf code a bit.

Test build #54222 has started for PR 11570 at commit 5ebfc39.

Test build #54222 has finished for PR 11570 at commit 5ebfc39.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54222/
Test FAILed.

Merged build finished. Test FAILed.

Test build #54224 has started for PR 11570 at commit 42a9419.

Test build #54224 has finished for PR 11570 at commit 42a9419.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54224/
Test FAILed.

retest this please

Test build #54379 has started for PR 11570 at commit 42a9419.

Test build #54379 has finished for PR 11570 at commit 42a9419.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54379/
Test FAILed.

Alright, one last try to get people to review this... let me try some others too: @yhuai @andrewor14

Test build #54545 has started for PR 11570 at commit 3a881ae.

Test build #54545 has finished for PR 11570 at commit 3a881ae.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54545/
Test FAILed.

Test build #54553 has started for PR 11570 at commit 690478f.

Test build #54560 has started for PR 11570 at commit ca9df5d.

Test build #54560 has finished for PR 11570 at commit ca9df5d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54560/
Test FAILed.

Test build #54567 has started for PR 11570 at commit 4588c7e.

Test build #54553 has finished for PR 11570 at commit 690478f.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54553/
Test FAILed.

Test build #54567 has finished for PR 11570 at commit 4588c7e.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class MultilayerPerceptronClassificationModel(JavaModel, JavaMLWritable, JavaMLReadable):

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54567/
Test PASSed.

Test build #54660 has started for PR 11570 at commit 0ce2722.

Test build #54660 has finished for PR 11570 at commit 0ce2722.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54660/
Test FAILed.

Merged build finished. Test FAILed.

Test build #54664 has started for PR 11570 at commit 07af6cd.

Test build #54664 has finished for PR 11570 at commit 07af6cd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54664/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

I'm seeing a lot of builds fail in this code in SparkBuild.scala:
      if (!new File(testTempDir).isDirectory()) {
        require(new File(testTempDir).mkdirs())
      }

I wonder what's going on; are things running in parallel? Are different jobs somehow trying to write to the same directory?

Test build #54667 has started for PR 11570 at commit 07af6cd.

Test build #54667 has finished for PR 11570 at commit 07af6cd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54667/
Test FAILed.

Test build #54675 has started for PR 11570 at commit de594b6.

Test build #54675 has finished for PR 11570 at commit de594b6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54675/
Test PASSed.

@andrewor14 @rxin Please advise.

deep-review this please

deep-review this please

Test build #54710 has started for PR 11570 at commit 3458f26.

@andrewor14 Review complete. No major issues found.

Test build #54710 has finished for PR 11570 at commit 3458f26.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ShowTablesCommand(
case class ShowDatabasesCommand(databasePattern: Option[String]) extends RunnableCommand
case class BatchPythonEvaluation(udfs: Seq[PythonUDF], output: Seq[Attribute], child: SparkPlan)
      // enable memo iff we serialize the row with schema (schema and class should be memorized)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54710/
Test FAILed.

Test build #54867 has started for PR 11570 at commit ddc3655.

Test build #54867 has finished for PR 11570 at commit ddc3655.

This patch fails some tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54867/
Test FAILed.

retest this please

Test build #54884 has started for PR 11570 at commit ddc3655.

This pr seems to have trouble passing tests... I will definitely review it today.

There wasn't a specific failure in the last run, just seemed like some infrastructure issue. All tests actually passed.

Test build #54902 has started for PR 11570 at commit e089501.

Test build #54884 has finished for PR 11570 at commit ddc3655.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54884/
Test PASSed.

The change looks alright to me. I'm still not a huge fan of the naming of the new API but since it is internal it's not that big of a deal.

Test build #54902 has finished for PR 11570 at commit e089501.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54902/
Test PASSed.

Test build #55003 has started for PR 11570 at commit 7bad3f9.

Test build #55003 has finished for PR 11570 at commit 7bad3f9.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
             s\"Unable to generate an encoder for inner class$`
case class UnresolvedDeserializer(deserializer: Expression, inputAttributes: Seq[Attribute])
case class ShowTablePropertiesCommand(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/55003/
Test PASSed.

Alright, merging to master to avoid another round of fixing conflicts.


fix(decl): potential nil ptr deref and shell script SIGUSR handling

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
This PR fixes the SIGUSR1 signal handling for shell scripts by correctly handling the exit code set by the signal (138). The first instruction after the blocking wait now verifies the returned exit code and clears its value if it matches the one set by the signal. Moreover, this PR fixes a potential nil pointer dereference in test context validation and conditionally disable shell script execution when both "before" and "after" scripts are not provided by the user.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ekoops
Once this PR has been reviewed and has the lgtm label, please assign fededp for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, ekoops
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 264bc63b69d6e52fdd049cb38208a7da6276804c


Incompatability with older OpenGL Versions

From the discord, it's been brought up that the rendering of the dams will crash your game if your Opengl version is lower than 4, specifically the glGenVertexArrays function.
Attached are the relevant crash reports from Alastor.
crash-2021-04-30_17.03.59-client.txt
crash-2021-04-30_17.17.47-server.txt

Thanks for letting me know!
glGenVertexArrays is OpenGL 3.0 and a very, very old standard. Sadly, there is not too much i can to do about it. I need that call. My laptop is old and barely runs GTNH, but already has the newest OpenGL version. I don't expect many people to have a problem with it.

Just putting this for reference even though I have mentioned it to you, I figure it should be here too. MacOS doesn't have support for opengl past 2.1 or so since 10.14 mojave, switching main support to Apple's in-house graphics API. So this is more than likely the issue ;-;.
And as I mentioned I'd put it here just for future's reference:
Is there is a way to not show the dam water graphically to those who wouldn't be able to see it (that being those on mac in this case) and still use it despite that fact? That would at least solve the issue of people potentially crashing when rendering it? Like how you got the mod to show the opengl version, maybe making that a gate to render the dam water?
I know you're working on it, this is more for other's reference than anything else.

I implemented fallback rendering for the time being. Won't be perfect, but it won't crash for now


Remove orphaned indexes command

Added the delete orphaned indexes command and fixed a typo in ContentManagement/IndexController.php

@theus77 Can we merge this?

Hey Laurens, you forgot to check phpcs, the failing issues can be fixed running phpcbf !


Enable new selectable rule, "Frederiksberg"

Enable new selectable rule, "Frederiksberg"

This has now been implemented.


[PE-D][Tester D] Header "Adding an appointment" is indented

Header indentation is inconsistent.

"Adding an appointment" should be at the same level as "Deleting a person".

Labels: severity.VeryLow type.DocumentationBug
original: colinac/ped#1

Issues closed with linked closed PR


Replaced lsmod by package-list

When using tools like pm2, the method used by lsmod is not capable of detecting the packages of the child process. This means that sentry will always receive the list of modules of pm2 and not of your project's own dependencies.
Here's an example for a project using foo and package-listas dependencies, plus lsmod installed but not added to the project's package.json:
Output from `lsmod`:
{ pm2: '0.7.7', 'coffee-script': '1.7.0' }
------
Output from `package-list`
{ foo: '1.0.0',
  'package-list': '0.0.1',
  lsmod: '0.0.3 (extraneous)' }

This is up for discussion as the async nature of getModules changes the return values of some functions.

Closing, as it's very outdated, over 3 years now. @ruimarinho please let me know if this is still something that you'd like to add and you could find time to verify it's still valid. Closing for now.

@kamilogorek the original issue is no longer valid. At first, I though the fix was done at the vendored file of lsmod that ships with raven, but using v0.0.3 (pre-PR) provides the same output. My guess is that the change in behaviour was introduced by pm2 (in the way it spawns child processes) or node itself.
For future reference, the current version of lsmod and its use inside getModules() is now able to correctly list the modules inside of the running script and not the launcher itself (in the original example, pm2 in either fork or cluster mode).

Thanks for getting back on this one. Cheers!


Remove exit calls and instead propagate errors to the call side

A library is not supposed to exit an application. Instead, an unrecoverable error is propagated to the call side (where exit may be called or not). This gives an application the chance to perform own cleanup and tear-down (independent of "magic" exit handler code). This requirement belongs to the code safety category which is about allowing our code to be adopted where highest standards apply.

libxsmm_build.c completed.

This issue is also unveiled/checked by the package review aiming for general Linux distribution.

Moved this issue to https://github.com/hfp/libxsmm/wiki/Development/_edit#longer-term-issues.


Does condor_tail work in the jobsub_lite setup?

This is a long-standing question from @rlcee that has unfortunately gotten prioritized behind many other work items.  I wanted to formalize this into an issue so that others can also take a look if they've got the bandwidth.
The question is exactly as the title states - we need to see if condor_tail works with the jobsub_lite setup (i.e. remote submission - so can we run condor_tail from the INTERACTIVE nodes, not the schedds), and if not, decide whether or not we want to support it.

So I ran a couple of quick tests... So far no joy.   I have a job that prints a bunch of stuff and sleeps for 5 minutes,
and ran condor_tail -debug on it...  I get:
[mengel@fifeutilgpvm01 ~]$ /usr/bin/condor_tail -debug -name jobsub04.fnal.gov 70018.0
04/26/23 12:40:48 Can't open directory "/etc/condor/passwords.d" as PRIV_ROOT, errno: 13 (Permission denied)
04/26/23 12:40:48 Can't open directory "/etc/condor/passwords.d" as PRIV_ROOT, errno: 13 (Permission denied)
04/26/23 12:40:48 Requesting GoAhead from the transfer queue manager.
04/26/23 12:40:48 Received GoAhead from the transfer queue manager.
[FERMIHTC-APPTAINER]: INFO -- SingularityImage classAd detected
[FERMIHTC-APPTAINER]: INFO -- Attempting to run job in /cvmfs/singularity.opensciencegrid.org/fermilab/fnal-wn-sl7:latest
[FERMIHTC-APPTAINER]: INFO -- Running /cvmfs/oasis.opensciencegrid.org/mis/apptainer/current/bin/apptainer exec --pid --ipc --contain --bind /cvmfs --bind /etc/hosts --home /storage/local/data1/condor/execute/dir_22712:/srv --pwd /srv /cvmfs/singularity.opensciencegrid.org/fermilab/fnal-wn-sl7:latest ./condor_exec.exe

But no actual job output arrived...


${workspaceFolder} expands to VSCode executable directory when no workspace folder is loaded`

Observe one of our settings such as python.dataScience.notebookFileRoot which use ${workspaceFolder} variable as a value. When you load this setting without a workspace loaded instead of undefined or empty string it provides a value for the current directory, usually the vscode exe location. This isn't the workspace directory and can throw off things trying to use these settings.

TODO:

As a simple first step, we need to review existing code and understand the impact of defaulting to an empty string instead of __dirname

This should be fixed by #7724

validated


根据最新的微信支付文档增加删除了一些参数

文档请见 https://pay.weixin.qq.com/wiki/doc/api/tools/cash_coupon.php?chapter=13_4&index=3

Codecov Report

Merging #201 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #201   +/-   ##
=======================================
  Coverage   76.81%   76.81%
=======================================
  Files          88       88
  Lines        3338     3338
=======================================
  Hits         2564     2564
  Misses        774      774

Impacted Files
Coverage Δ

wechatpy/pay/api/redpack.py
42.85% <ø> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4bc972f...f056c7c. Read the comment docs.


Add Zipkin autoconfiguration

This is first / incomplete attempt to add Zipkin autoconfiguration.

@geoand +1 :)

PR should be ready for review @pavolloffay

@pavolloffay PR updated to reflect the changes you requested

I forgot to add the zipkin test that utilizes the jUnit rule... I'll do that soon as well

@geoand it needs rebase

@pavolloffay Done

@geoand travis is still failing
[ERROR]     'dependencies.dependency.version' for io.opentracing.contrib:opentracing-spring-cloud-starter-jaeger:jar is missing. @ io.opentracing.contrib:opentracing-spring-cloud-starter-jaeger-it:[unknown-version], /home/travis/build/opentracing-contrib/java-spring-cloud/opentracing-spring-cloud-starter-jaeger-it/pom.xml, line 35, column 17

It's red again :/

Yes, there seems to be a very interesting bug in the tests that run for Edgeware :)
I'm looking into it

@pavolloffay It's all green :P

@pavolloffay I updated the branch so I will merge when green. Do that sound OK with you?

yes merge anytime. It could have been merged before :)

Done :)


new operator support

Maybe we can change the declaration file pointer.d.ts
export declare type PointerCastInstance<T extends new (...args: any) => any, E = NonPointerTypes> = T extends new (...args: any) => infer R ? T & {
    wrap(ptr: Pointer<PointerCastObject<R, E>>): PointerCastObject<R, E>;
} : never;

to
export declare type PointerCastInstance<T extends new (...args: any) => any, E = NonPointerTypes> = T extends new (...args: infer A) => infer R ? (new (...args: PointerCastArray<A, E>) => PointerCastObject<R, E>) & {
    wrap(ptr: Pointer<PointerCastObject<R, E>>): PointerCastObject<R, E>;
} : never;

So that, we can use the new operator.

Thanks for pointing this out, I've created a PR to fix this ;)


It seems to have stopped working.

I tried to run this as normal but kept getting the following error.
FileNotFoundError: [Errno 2] No such file or directory: 'File "/Users/wesley/Documents/Youtube-Whisper-Streamlit/app.py", line 52, in  filename = glob.glob("output/*")[0]'
Traceback:
File "/opt/homebrew/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 562, in _run_script
exec(code, module.dict)
File "/Users/wesley/Documents/Youtube-Whisper-Streamlit/app.py", line 48, in
st.video(url.strip())
File "/opt/homebrew/lib/python3.10/site-packages/streamlit/runtime/metrics_util.py", line 231, in wrap
result = callable(*args, **kwargs)
File "/opt/homebrew/lib/python3.10/site-packages/streamlit/elements/media.py", line 125, in video
marshall_video(coordinates, video_proto, data, format, start_time)
File "/opt/homebrew/lib/python3.10/site-packages/streamlit/elements/media.py", line 257, in marshall_video
_marshall_av_media(coordinates, proto, data, mimetype)
File "/opt/homebrew/lib/python3.10/site-packages/streamlit/elements/media.py", line 187, in _marshall_av_media
with open(data, "rb") as fh:

@swankwc , can you send me some details on your python version and the requirements.txt file? Please ensure you are having a virtual environment created separately for installing the dependencies and working on the app


Remove version: LupoPenSuite.DropIt version 8.5.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Package still available.;


Dev running stop

Description
Add test to check if a vehicle is running a stop
Fixes #
Where has this been tested?

Platform(s): Ubuntu 16.04
Python version(s): 3.5.5
Unreal Engine version(s): NA
CARLA version: overnight 2019-03-19

Possible Drawbacks

This change is

srunner/scenariomanager/atomic_scenario_criteria.py, line 879 at r1 (raw file):

        waypoint = self._map.get_waypoint(current_location)
        for i in range(multi_step):
            waypoint =  waypoint.next(5.0)[0]

Why 5.0 ?


Icon of callout are not displayed

To Reproduce
Create a callout like this:
> [!info]
> I am a info Callout.

And export it.
Screenshots

Thanks, I can reproduce this and I will look into it

Hello! Any update? Thanks!

Hi, I have a lot of stuff going on and there are lots of bugs to fix. I'll update this issue once progress has been made. Thanks! :)

Especially weird: in my experience sometimes some of icons are displayed and other times none of them are.

This issue is fixed in the beta, and will be fixed in the next stable release as well

This should be fixed in 1.8.0. Let me know if it still does not work as expected and reopen the issue. If you find any new issues please submit a new issue :)
Thanks!


Configurability: save output file with non-default name

Similar to pytest-html's options
--html=report.html --self-contained-html

Superceded by

This is available now with the   --tui-htmlfile=TUI_HTMLFILE flag


#issue1 file delete bug fixed(may be)

The bug is described in #1 , i think something wrong in tokio nested asynchronous execution.
I created another tokio Runtime and executed the asynchronous logic of deleting the file in that runtime, this solved the problem, but I don't know if this is the best practice for nested tasks in tokio...

fix: in #1 -> in #2


Webpack: more flexibility with HTML files

Current webpack setup can't even handle multiple index.html files in different directories without overwriting, which is a pretty big issue. Maybe worth looking at html-webpack-plugin because it seems to be much more popular and much more powerful than Webpack's html-loader

I think it's good now... I'll reopen if more issues appear


Remove Abstraction enum from IRs

This PR removes the Abstraction type from the mir and lir modules and extends the Term enum to accommodate binary and unary operations. Now operators don't exist by themselves in the inner representation, i.e., they are saturated.
These changes didn't introduce any benchmark regressions:
arithmetic              time:   [919.30 ns 927.84 ns 939.39 ns]
                        change: [-45.402% -44.592% -43.654%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  6 (6.00%) high mild
  5 (5.00%) high severe

fact_rec                time:   [215.33 us 216.99 us 219.64 us]
                        change: [-26.719% -26.084% -25.382%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  3 (3.00%) high mild
  8 (8.00%) high severe

fact_tail               time:   [100.80 us 101.08 us 101.42 us]
                        change: [-43.156% -42.734% -42.331%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 12 outliers among 100 measurements (12.00%)
  7 (7.00%) high mild
  5 (5.00%) high severe

fancy_max               time:   [2.5668 us 2.5748 us 2.5831 us]
                        change: [-26.381% -25.873% -25.428%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
  2 (2.00%) high mild
  1 (1.00%) high severe

step                    time:   [1.2365 us 1.2418 us 1.2486 us]
                        change: [-15.927% -15.564% -15.063%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 100 measurements (10.00%)
  5 (5.00%) high mild
  5 (5.00%) high severe

@seanchen1991 I think we are very close to being able to implement short-circuiting operators without too much difficulty.


Fix lunar-en.js layout (Uncaught SyntaxError)

Without layout set to null a HTML template will be rendered around the JavaScript, causing an error while loading the file in the browser.
lunr-en.js:1 Uncaught SyntaxError: Unexpected token <

Thanks @LouisMT


Unnecessary vibra enabled for minimal notification

Minimal notification with just a title and body appears silently on screen in node-pushnotifications, while it vibrates in note-pushnotifications-http2

try with latest master and tell me if it persists, I've updated the dependency

When I try to add package from master it tries to run tests and tests are failed


[Device Support Request] Tuya TS0601 by _TZE200_ghynnvos

Problem description
Tuya PIR have no functions, pairs fine and according to ZHA have the latest firmware.
Solution description
Get it to have some more function than using battery and displaying firmware version :)
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

Device signature
Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0051",
      "input_clusters": [
        "0x0000",
        "0x0004",
        "0x0005",
        "0xef00"
      ],
      "output_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_ghynnvos",
  "model": "TS0601",
  "class": "zigpy.device.Device"
}

Diagnostic information
Diagnostic information
[Paste the diagnostic information here]

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
No response

Seems to have a sensor in the corner,  the seller has very little information on functions and I don't have a Tuya Zigbee controller for testing at the moment

Any updates or custom quirks available for this? I have the same sensor, only firmware is showing after "successful" pairing in HA.

I just bought the same device. I'm not using ZHA (but Zigbee2MQTT) but I want to add some context as this is the only page I could find about this specific device. Z2M doesn't even show firmware version or battery level for this.
This is being sold in Finland (by Power, a Nordic consumer electronics chain) under brand name Conecto with model name: COZIGPMS (I guess Conecto is all just rebranded Tuya devices?).
I'm a developer and interested in helping to add support for this (at least for Z2M, maybe also ZHA if I can help) but I'm pretty new to HA, ZHA and Z2M even as a user so I'm not sure what it requires or how deep reverse engineering would be needed. I'm trying to start from here https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
I'm not sure if having it working in Z2M would help with ZHA side also.

I did some digging in https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts searching by "TS0601" (there are hundreds of results) and looking for anything related to motion sensing.
I found this this section which describes a "Haozee PIR sensor" (Tuya TS0601 by _TZE200_f1pvdgoh). I did a google search for that and found this issue https://github.com/Koenkk/zigbee2mqtt/issues/12883 which links to an Ali Express listing for a sensor that looks pretty much identical to this one so I guess it's basically the same device (just identified differently).
I was able to get mine to work on Z2M just by making a custom converter by reusing the main parts of the configuration defined for the Haozee PIR sensor.
This is my current JS definition file that seems to work perfectly with Z2M.
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const e = exposes.presets;

const definition = {
  fingerprint: tuya.fingerprint('TS0601', ['_TZE200_ghynnvos']),
  model: 'TS0601_pir_2',
  vendor: 'Tuya',
  description: 'PIR Motion Sensor',
  fromZigbee: [tuya.fz.datapoints],
  toZigbee: [tuya.tz.datapoints],
  onEvent: tuya.onEvent(),
  configure: tuya.configureMagicPacket,
  exposes: [e.occupancy(), e.illuminance(), e.battery()],
  meta: {
    tuyaDatapoints: [
      [1, 'occupancy', tuya.valueConverter.trueFalse0],
      [4, 'battery', tuya.valueConverter.raw],
      [101, 'illuminance', tuya.valueConverter.raw],
    ],
  },
  whiteLabel: [
    tuya.whitelabel('Conecto', 'COZIGPMS', 'PIR Motion Sensor', ['_TZE200_ghynnvos']),
  ],
};

module.exports = definition;

By quick testing at least occupancy and illuminance status works fine. Can't see battery percentage yet, but I guess it might start reporting later after running for some time. I guess the small black dot on the device is the illuminance sensor.

@Haprog Hej! :) I have added this to my setup, but the occupancy is very flakey. The light detection is working well, though. The strange thing is that sometimes the occupancy is set as occupied for hours, then sudden it won't see occupancy at all. Have you seen anything like that?

@Mastiffen Terve! I have not seen such problems. For me the occupancy has been reliable. I use this to automate lights on/off in one room so it's used pretty much every day and has been reliable so far.
Maybe your device is broken? Does it have good signal to the Zigbee network? I also bought two more of the same device, but have not taken those into use yet.

Aha, Finland, inte Sverige! Min fru er 2/3 finsk.
Thanks! Maybe it's the placement. It's in the ceiling pointing down towards the shower (lights went off when my wife used more than five minutes in there), but it's only 10 cm from the frame of the shower. I'll try to move it.

I use mine in a utility/laundry room (kodinhoitohuone) which is mostly used as a corridor to get to the larger bathroom and sauna. I made an automation in Home Assistant to immediately turn off the lights when no motion is detected (without extra timeout) and it seems to take around 20-30 seconds until the lights turn off if I just walk through so there's probably around 20s internal delay in the device until it updates the occupancy state when motion is not detected anymore.
If I stay in the room e.g. to do empty the washing machine, it does sometimes turn off the light while I'm there when I'm not moving much, but it turns back on when I wave or do a bigger movement. I could add a timeout on the automation side so it does not turn off until occupancy has been cleared for X amount of time, but most of the time I want it to turn off quicker so I haven't done that. Your shower use case might work better with some added timeout.
But I think if you have it directly above or too close to the shower the sensor might get "cloudy" from the moisture in the air, when the shower is being used, and thus does not see movement as well which might add to your issue? I also wouldn't expect this device to last long in so humid environment as it's probably not that well insulated and moisture might get inside it with some time and cause electrical issues.

@Haprog  Of course you have it in a corridor to the sauna... ;) But I gave up this one and put up a Fibaro "Eye" that I had laying around instead. Problem solved, no more showers in the dark. I will take down this one and see if it works better in my house, where I am using a ConBee II, not a cheap Ali Express Zigbee. That may be related.

I did some digging in https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts searching by "TS0601" (there are hundreds of results) and looking for anything related to motion sensing.
I found this this section which describes a "Haozee PIR sensor" (Tuya TS0601 by _TZE200_f1pvdgoh). I did a google search for that and found this issue Koenkk/zigbee2mqtt#12883 which links to an Ali Express listing for a sensor that looks pretty much identical to this one so I guess it's basically the same device (just identified differently).
I was able to get mine to work on Z2M just by making a custom converter by reusing the main parts of the configuration defined for the Haozee PIR sensor.
This is my current JS definition file that seems to work perfectly with Z2M.
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const e = exposes.presets;

const definition = {
  fingerprint: tuya.fingerprint('TS0601', ['_TZE200_ghynnvos']),
  model: 'TS0601_pir_2',
  vendor: 'Tuya',
  description: 'PIR Motion Sensor',
  fromZigbee: [tuya.fz.datapoints],
  toZigbee: [tuya.tz.datapoints],
  onEvent: tuya.onEvent(),
  configure: tuya.configureMagicPacket,
  exposes: [e.occupancy(), e.illuminance(), e.battery()],
  meta: {
    tuyaDatapoints: [
      [1, 'occupancy', tuya.valueConverter.trueFalse0],
      [4, 'battery', tuya.valueConverter.raw],
      [101, 'illuminance', tuya.valueConverter.raw],
    ],
  },
  whiteLabel: [
    tuya.whitelabel('Conecto', 'COZIGPMS', 'PIR Motion Sensor', ['_TZE200_ghynnvos']),
  ],
};

module.exports = definition;

By quick testing at least occupancy and illuminance status works fine. Can't see battery percentage yet, but I guess it might start reporting later after running for some time. I guess the small black dot on the device is the illuminance sensor.

this seems to have worked, thx!

now that it has been running a while its not reporting battery


Add docs on querying a variant store with Impala.

Thanks, @tomwhite!  This is great.
Is there a Hive CLI equivalent of LIKE PARQUET <file>?  I can't figure out how to get Hive to infer the schema from the Parquet file rather than specifying it explicitly.
It would be awesome to be able to query the genotypes, too.  It seems like we could write a SerDe (now I'm thinking ImpEx isn't so bad :)) to unpack the genotypes.  Does that sound like the right approach?
On a related note, we've played with storing VDS natively as Parquet as (variant, variant annotations, array(genotype)).  Even when I ported over some of the GenotypeStream encoding tricks (OD instead of DP, etc.), it was 2-3x larger (using Snappy compression vs. our internal LZ4 compression).  That's disappointing, esp. when we have 30+TB datasets on the way.
What's worse, simple operations like counting genotypes (count -g) are 5-10x in the native representation.
Current master:
$ hail importvcf ~/1kg/profile225.vcf.bgz write -o ~/profile225.vds read -i ~/profile225.vds count -g
hail: info: timing:
  importvcf: 508.829ms
  write: 3m6.7s
  read: 1.629s
  count: 13.934s
$ du -sh profile225.vds
2.0G profile225.vds

And with the jg_dataframe1 experimental branch, which uses native Parquet and computes the count using a UDF that computes the sum per array (fastest Parquet-based implementation we've found so far):
$ hail importvcf profile225.vcf.bgz write -o profile225.vds read2 -i profile225.vds count2
hail: info: timing:
  importvcf: 492.354ms
  write: 5m57.1s
  read2: 1.466s
  count2: 1m44.1
$ du -sh profile225.vds
5.4G profile225.vds

That's 2.5x larger and >7x slower.  This includes the fact that the Parquet version is only loading the GT field of the genotypes (!).  This might be a non-starter for us.  We'd love the flexibility and interoperability of standard Parquet.

Oops, it looks like those Parquet numbers were uncompressed.  Here are the --parquet-compression snappy numbers:
hail: info: timing:
  importvcf: 502.211ms
  write: 6m12.6s
  read2: 1.463s
  count2: 1m54.7s
$ du -sh profile225.vds
4.0G profile225.vds

Slightly slower and modestly smaller.

Is there a Hive CLI equivalent of LIKE PARQUET <file>? I can't figure out how to get Hive to infer the schema from the Parquet file rather than specifying it explicitly.

I don't think there is a Hive equivalent unfortunately.

It would be awesome to be able to query the genotypes, too. It seems like we could write a SerDe (now I'm thinking ImpEx isn't so bad :)) to unpack the genotypes. Does that sound like the right approach?

In Hive a UDTF (user-defined table function; ImpEx naming is growing on me :) would allow you to return a genotype per row.
Impala doesn't support UDTFs, but it should be possible to write a UDF that returns an array of genotypes. The UDF to do this could be written in Java so that Hive or Impala can use it; it's also possible to write an optimized version in C++ for Impala.
On standard Parquet storage: thanks for the numbers. I don't have a good idea of how to close the gap. I ran some experiments with a standard Parquet representation (in Quince) but have now come to the conclusion that custom encoding of the genotypes is a pragmatic way of achieving the best performance.


Fix default keychain selection

This fixes a typo; keyring is not a valid keyringBackend.

Ugh, I knew those not being consts would bite us eventually. Thanks and apologies.


Error [ERR_REQUIRE_ESM]: require() of ES Module

Hello,
Thank you for this lib.
I'm trying to make it work on a test repo.
This code throws :
import en from "dictionary-en";

console.log(en);

With the following error :
yoann@yoann-XPS-ubuntu:~/dev/test$ ts-node dictionnary/index.ts
/home/yoann/.nvm/versions/node/v20.12.0/lib/node_modules/ts-node/dist/index.js:851
            return old(m, filename);
                   ^
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/yoann/dev/test/node_modules/dictionary-en/index.js from /home/yoann/dev/test/dictionnary/index.ts not supported.
Instead change the require of index.js in /home/yoann/dev/test/dictionnary/index.ts to a dynamic import() which is available in all CommonJS modules.
    at require.extensions.<computed> [as .js] (/home/yoann/.nvm/versions/node/v20.12.0/lib/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (/home/yoann/dev/test/dictionnary/index.ts:7:41)
    at m._compile (/home/yoann/.nvm/versions/node/v20.12.0/lib/node_modules/ts-node/dist/index.js:857:29) {
  code: 'ERR_REQUIRE_ESM'

I checked the index.js file in node_modules, as you can see it does not hold require() call :
/**
 * @typedef Dictionary
 *   Hunspell dictionary.
 * @property {Uint8Array} aff
 *   Data for the affix file (defines the language, keyboard, flags, and more).
 * @property {Uint8Array} dic
 *   Data for the dictionary file (contains words and flags applying to those words).
 */

import fs from 'node:fs/promises'

const aff = await fs.readFile(new URL('index.aff', import.meta.url))
const dic = await fs.readFile(new URL('index.dic', import.meta.url))

/** @type {Dictionary} */
const dictionary = {aff, dic}

export default dictionary

I'm on node 20.12.0
Would you have any idea of what I could do to make it work ?

I'm ready to help with a PR, I just don't know how to approach the problem. I've read some docs but this ESM/commonJS thing (+ ts-node which interacts above it) - it seems to deep haha - which I why I'd be curious to solve it.
If you have any idea, happy to help and dig

Hey! This package uses ESM. I am not interested in adding CJS again.
Either use ESM yourself, or use the previous version (which was CJS).
I personally recommend adding "type": "module" to your package.json, then you’re in ESM. I’ve done that for about 4 years now. Works well in 100s of projects.

It works with npx tsx dictionnary/index.ts
but node with ts-node
I can't even get the file being executed with esm config with ts-node, I don't know where it comes from
I'll just go with tsx
Thank you


Merge Pull Request: Migration to Swift 5, iOS 12.2

Migration to Swift 5, iOS platform 12.2. Corrected all the issues (errors and warnings) that Xcode came up with.
Hope this worx as I'm new to GitHub ;)

Thanks for this! I was gone over the weekend, I'll give this a spin today

@DaGerry I think I figured out why the tests are failing. I'll hopefully be able to fix this later today and can then merge. I'll keep you posted.


[stable/grafana] Grafana pod has unbound PersistentVolumeClaims (will not schedule)

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

Version of Helm and Kubernetes:
Kubernetes: v1.10.0
Helm: v2.8.2
Which chart:
stable/grafana
What happened:
Tried to install Grafana but the Grafana pod could not be scheduled because of the error: pod has unbound PersistentVolumeClaims, even though I disabled persistence using a custom config, it tried to configure a persistent volume.
What you expected to happen:
Grafana pod should have started successfully
How to reproduce it (as minimally and precisely as possible):
values.yaml
rbac:
  create: true
  pspEnabled: true
serviceAccount:
  create: true
  name:

replicas: 1

deploymentStrategy: RollingUpdate

livenessProbe:
  httpGet:
    path: /api/health
    port: 3000

readinessProbe:
  httpGet:
    path: /api/health
    port: 3000
  initialDelaySeconds: 60
  timeoutSeconds: 30
  failureThreshold: 10
  periodSeconds: 10

image:
  repository: grafana/grafana
  tag: 5.2.4
  pullPolicy: IfNotPresent

securityContext:
  runAsUser: 472
  fsGroup: 472

downloadDashboardsImage:
  repository: appropriate/curl
  tag: latest
  pullPolicy: IfNotPresent

service:
  type: ClusterIP
  port: 80
  annotations: {}
  labels: {}

ingress:
  enabled: false
  annotations: {}
  labels: {}
  path: /
  tls: []

resources: {}

nodeSelector: {}

tolerations: []

affinity: {}

persistence:
  enabled: false

adminUser: adminuser
adminPassword: thepassword

env: {}

envFromSecret: ""

extraSecretMounts: []

plugins: []

datasources: {}

dashboardProviders: {}

dashboards: {}

dashboardsConfigMaps: {}

grafana.ini:
  paths:
    data: /var/lib/grafana/data
    logs: /var/log/grafana
    plugins: /var/lib/grafana/plugins
    provisioning: /etc/grafana/provisioning
  analytics:
    check_for_updates: true
  log:
    mode: console
  grafana_net:
    url: https://grafana.net

ldap:
  existingSecret: ""
  config: ""

smtp:
  enabled: true
  existingSecret: "kube-grafana-smtp"

sidecar:
  image: kiwigrid/k8s-sidecar:0.0.3
  imagePullPolicy: IfNotPresent
  resources:

  dashboards:
    enabled: false
    label: grafana_dashboard
    folder: /tmp/dashboards
  datasources:
    enabled: false
    label: grafana_datasource

Anything else we need to know:
Output of pod describe:
Name:           kube-grafana-7cbf8d8588-24j7p
Namespace:      default
Node:           <none>
Labels:         app=kube-grafana-grafana
                component=grafana
                pod-template-hash=3769484144
                release=kube-grafana
Annotations:    checksum/config=4fa36d33f7bbdc218145adc7680f4e668fb4a5b97087d2977733bba3a319eb72
                checksum/dashboards-config=c60e4ee88c9d3f060dde064744346163eea3c2a7a645cc9250022c436193d3e9
Status:         Pending
IP:
Controlled By:  ReplicaSet/kube-grafana-7cbf8d8588
Init Containers:
  copy-configs:
    Image:      busybox
    Port:       <none>
    Host Port:  <none>
    Command:
      sh
      -c
      cp /tmp/config-volume-configmap/* /tmp/config-volume 2>/dev/null || true; cp /tmp/dashboard-volume-configmap/* /tmp/dashboard-volume 2>/dev/null || true
    Environment:  <none>
    Mounts:
      /tmp/config-volume from config-volume (rw)
      /tmp/config-volume-configmap from config-volume-configmap (rw)
      /tmp/dashboard-volume from dashboard-volume (rw)
      /tmp/dashboard-volume-configmap from dashboard-volume-configmap (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-74z8v (ro)
Containers:
  grafana:
    Image:      grafana/grafana:5.0.4
    Port:       3000/TCP
    Host Port:  0/TCP
    Requests:
      cpu:      100m
      memory:   100Mi
    Readiness:  http-get http://:3000/api/health delay=30s timeout=30s period=10s #success=1 #failure=3
    Environment:
      GF_SECURITY_ADMIN_USER:      <set to the key 'grafana-admin-user' in secret 'kube-grafana'>      Optional: false
      GF_SECURITY_ADMIN_PASSWORD:  <set to the key 'grafana-admin-password' in secret 'kube-grafana'>  Optional: false
    Mounts:
      /etc/grafana from config-volume (rw)
      /var/lib/grafana from storage-volume (rw)
      /var/lib/grafana/dashboards from dashboard-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-74z8v (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  config-volume:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  dashboard-volume:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  config-volume-configmap:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kube-grafana-config
    Optional:  false
  dashboard-volume-configmap:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kube-grafana-dashs
    Optional:  false
  storage-volume:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  kube-grafana
    ReadOnly:   false
  default-token-74z8v:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-74z8v
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  1m (x37 over 11m)  default-scheduler  pod has unbound PersistentVolumeClaims

Output of kubectl describe persistentvolumeclaim kube-grafana:
Name:          kube-grafana
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        app=kube-grafana-grafana
               chart=grafana-0.8.5
               component=grafana
               heritage=Tiller
               release=kube-grafana
Annotations:   <none>
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
Events:
  Type    Reason         Age                From                         Message
  ----    ------         ----               ----                         -------
  Normal  FailedBinding  1m (x63 over 16m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

Persistence has been disabled, so the fact that it has tried to create a PVC is odd. It might be worth noting that I tried to install Grafana with persistence enabled and storage parameters defined, but had the exact same issue.

I managed to resolve this issue.
I had to update my helm repo database to get the latest stable version of Grafana, 5.2.4
For reference: helm repo update


Abstract component instance config with settings.spacelift.workspace_enabled: true get created as Stacks

Describe the Bug
The following configuration creates a Spacelift stack if imported into a stack file:
components:
  terraform:
    kms/defaults:
      metadata:
        component: kms-key
        abstract: true
      settings:
        spacelift:
          workspace_enabled: true
      vars:
        deletion_window_in_days: 10
        enable_key_rotation: true
        allowed_principals: []
        allowed_roles: {}
        allowed_permission_sets: {}

Expected Behavior
Since it is tagged as abstract: true and atmos won't plan / apply this component instance, I would assume that this Spacelift module would avoid the same and not create a Spacelift Stack.
Steps to Reproduce
Steps to reproduce the behavior:

Add the above configuration to catalog file.
Import it into a stack file.
Run this spacelift automation module
See that a <environment>-<stage>-kms-defaults stack was created.

Screenshots
N/A
Environment (please complete the following information):

Spacelift Module version: 0.49.4

Additional Context
N/A

@aknysh Aha! This must have been a goof by me or someone from my team then. I'll fix it and confirm. Thanks!

This works as expected! Thanks for the info and pointing out our goof @aknysh 👍