text:
Failed to apply plugin [id 'com.google.gms.google-services']

The build for Android start failing with this exception:
....
:config phase:  addAarDependencies
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Common-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Data-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/facebook-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/List-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Primitives-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/pushplugin.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/widgets-release.aar

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/build.gradle' line: 802

* What went wrong:
A problem occurred evaluating root project 'ForSaleByOwner'.
> Failed to apply plugin [id 'com.google.gms.google-services']
   > For input string: "+"

@ignaciolarranaga
I suppose you are using one of the latest versions of the plugin - 0.1.0 or higher. Please note there is a difference between both - 0.1.1 automatically adds to your build gradle the google-services plugin with a + version.
What you can try on your side is:

set the push plugin as a dependency with the latest version (0.1.2)
tns platform remove android
tns platform add android
tns install

Build again.
Alternatively, edit the build.gradle and add to the class path where the google-services plugin is added 3.0.0 instead of +. Try building again.
I suspect that somewhere updating the project failed. Please try the above on your side and let me know how it goes.

I had the same problem on 0.1.1

tns platform remove android
tns platform add android

resolve the issue

mmm, add/remove the platform did not work for me. I tried even add/remove the plugin:
MacBook-Pro-de-Ignacio:hezea-app ignacio$ tns plugin add nativescript-push-notifications

> nativescript-push-notifications@0.1.2 postinstall /Users/ignacio/Workspaces/DuenoVende/hezea-app/node_modules/nativescript-push-notifications
> node postinstall.js

for-sale-by-owner@2.0.2 /Users/ignacio/Workspaces/DuenoVende/hezea-app
├── UNMET PEER DEPENDENCY @angular/compiler@2.4.3
├── UNMET PEER DEPENDENCY @angular/core@2.4.3
└── nativescript-push-notifications@0.1.2

Successfully installed plugin nativescript-push-notifications.
MacBook-Pro-de-Ignacio:hezea-app ignacio$ tns prepare android
Copying template files...
  ◟ Installing tns-androidInstalling  tns-android
  ◟ Installing tns-androidfor-sale-by-owner@2.0.2 /Users/ignacio/Workspaces/DuenoVende/hezea-app
├── UNMET PEER DEPENDENCY @angular/compiler@2.4.3
├── UNMET PEER DEPENDENCY @angular/core@2.4.3
└── tns-android@2.5.0

Project successfully created.
Executing before-prepare hook from /Users/ignacio/Workspaces/DuenoVende/hezea-app/hooks/before-prepare/nativescript-dev-android-snapshot.js
Executing before-prepare hook from /Users/ignacio/Workspaces/DuenoVende/hezea-app/hooks/before-prepare/nativescript-dev-typescript.js
Found peer TypeScript 2.1.6
Executing before-prepare hook from /Users/ignacio/Workspaces/DuenoVende/hezea-app/hooks/before-prepare/nativescript-push-notifications.js
Preparing project...

:config phase:  createDefaultIncludeFiles

:config phase:  copyAarDependencies

:config phase:  addAarDependencies
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Common-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Data-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/facebook-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/List-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Primitives-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/pushplugin.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/widgets-release.aar
google-services plugin could not detect any version for com.google.android.gms or com.google.firebase, default version: 9.0.0 will be used.
please apply google-services plugin at the bottom of the build file.
Incremental java compilation is an incubating feature.
:asbg:clean UP-TO-DATE
:deleteMetadata
:deleteFlavors
:deleteConfigurations UP-TO-DATE
:clean

BUILD SUCCESSFUL

Total time: 5.386 secs

This build could be faster, please consider using the Gradle Daemon: https://docs.gradle.org/2.10/userguide/gradle_daemon.html
Successfully prepared plugin nativescript-angular for android.
Successfully prepared plugin nativescript-intl for android.
Successfully prepared plugin nativescript-facebook-login for android.
nativescript-fcuuid is not supported for android.
Successfully prepared plugin nativescript-fcuuid for android.
Successfully prepared plugin nativescript-fresco for android.
Successfully prepared plugin nativescript-google-analytics for android.
nativescript-iqkeyboardmanager is not supported for android.
Successfully prepared plugin nativescript-iqkeyboardmanager for android.
Successfully prepared plugin nativescript-phone for android.
Successfully prepared plugin nativescript-push-notifications for android.
Successfully prepared plugin nativescript-telerik-ui for android.
Successfully prepared plugin nativescript-theme-core for android.
Successfully prepared plugin tns-core-modules for android.
Successfully prepared plugin tns-core-modules-widgets for android.
Project successfully prepared (android)
Executing after-prepare hook from /Users/ignacio/Workspaces/DuenoVende/hezea-app/hooks/after-prepare/nativescript-dev-android-snapshot.js
MacBook-Pro-de-Ignacio:hezea-app ignacio$ tns run android
Skipping prepare.
Searching for devices...
Building project...

:config phase:  createDefaultIncludeFiles
	+found plugins: nativescript-facebook-login
	 + creating include.gradle file for /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-facebook-login
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-facebook-login -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F0
	+found plugins: nativescript-fresco
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-fresco -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F1
	+found plugins: nativescript-google-analytics
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-google-analytics -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F2
	+found plugins: nativescript-phone
	 + creating include.gradle file for /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-phone
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-phone -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F3
	+found plugins: nativescript-push-notifications
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-push-notifications -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F4
	+found plugins: nativescript-telerik-ui
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/nativescript-telerik-ui -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F5
	+found plugins: tns-core-modules-widgets
	 + creating include.gradle file for /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/tns-core-modules-widgets
Renaming plugin directory to flavor name: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/tns-core-modules-widgets -> /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/src/F6

:config phase:  createPluginsConfigFile
	 Creating product flavors include.gradle file in /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations folder...

:config phase:  pluginExtend
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-facebook-login/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-fresco/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-google-analytics/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-phone/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-push-notifications/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-telerik-ui/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/tns-core-modules-widgets/include.gradle

:config phase:  copyAarDependencies

:config phase:  addAarDependencies
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Common-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Data-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/facebook-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/List-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Primitives-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/pushplugin.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/widgets-release.aar

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/build.gradle' line: 802

* What went wrong:
A problem occurred evaluating root project 'ForSaleByOwner'.
> Failed to apply plugin [id 'com.google.gms.google-services']
   > For input string: "+"

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

BUILD FAILED

Total time: 4.298 secs
Command /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/gradlew failed with exit code 1
# run android

┌─────────────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────┐
│ Usage                   │ Synopsis                                                                                │
│ Run on all connected    │ $ tns run android [--key-store-path <File Path> --key-store-password <Password> --key-store  │
│ devices and running     │ -alias <Name> --key-store-alias-password <Password>] [--release] [--justlaunch]              │
│ emulators               │                                                                                │
│ Run on a selected       │ $ tns run android --device <Device ID> [--key-store-path <File Path> --key-store-password    │
│ connected device or     │ <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [--release] [-    │
│ running emulator        │ -justlaunch]                                                                                │
│ Start an emulator and   │ $ tns run android --emulator [<Emulator Options>] [--key-store-path <File Path> --key-store  │
│ run the app inside it   │ -password <Password> --key-store-alias <Name> --key-store-alias-password <Password>] [-      │
│                         │ -release] [--justlaunch]                                                                     │
└─────────────────────────┴──────────────────────────────────────────────────────────────────────────────────────────────┘

Runs your project on a connected Android device or in a native Android emulator, if configured. This is shorthand for prepare, build and deploy. While your app is running, prints the output from the application in the console and watches for changes in your code. Once a change is detected, it synchronizes the change with all selected devices and restarts/refreshes the application.

### Options

    * --no-watch - If set, changes in your code will not be reflected during the execution of this command.
    * --device - Specifies a connected device/emulator on which to run the app.
    * --emulator - If set, runs the app in a native emulator for the target platform, if configured. When set, you can also set any other valid combination of emulator options as listed by $ tns help emulate android.
    * --release - If set, produces a release build. Otherwise, produces a debug build. When set, you must also specify the --key-store-* options.
    * --key-store-path - Specifies the file path to the keystore file (P12) which you want to use to code sign your APK. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-password - Provides the password for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-alias - Provides the alias for the keystore file specified with --key-store-path. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --key-store-alias-password - Provides the password for the alias specified with --key-store-alias-password. You can use the --key-store-* options along with --release to produce a signed release build. You need to specify all --key-store-* options.
    * --justlaunch - If set, does not print the application output in the console.
    * --clean - If set, forces rebuilding the native application.

### Attributes

    * <Device ID> is the index or name of the target device as listed by $ tns device android
    * <Emulator Options> is any valid combination of options as listed by $ tns help emulate android

Sending exception report (press Ctrl+C to stop).....

Alternatively, edit the build.gradle and add to the class path where the google-services plugin is added 3.0.0 instead of +. Try building again.
did you do that?

Yep, and it did not work either, but I think something else might be wrong, because despite I changed the version it keeps saying the same, might it be a hook or another plugin interfering ?:
MacBook-Pro-de-Ignacio:hezea-app ignacio$ head -n 30 /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/build.gradle | tail
import groovy.json.JsonSlurper //used to parse package.json
buildscript {
    repositories {
        jcenter()
    }

	dependencies {
		classpath "com.google.gms:google-services:3.0.0"
		classpath "com.android.tools.build:gradle:2.1.2"
	}
MacBook-Pro-de-Ignacio:hezea-app ignacio$ tns run android
Skipping prepare.
Searching for devices...
Building project...

:config phase:  createDefaultIncludeFiles
	+found plugins: nativescript-facebook-login
	+found plugins: nativescript-fresco
	+found plugins: nativescript-google-analytics
	+found plugins: nativescript-phone
	+found plugins: nativescript-push-notifications
	+found plugins: nativescript-telerik-ui
	+found plugins: tns-core-modules-widgets

:config phase:  createPluginsConfigFile
	 Creating product flavors include.gradle file in /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations folder...

:config phase:  pluginExtend
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-facebook-login/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-fresco/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-google-analytics/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-phone/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-push-notifications/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/nativescript-telerik-ui/include.gradle
	+applying configuration from: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/configurations/tns-core-modules-widgets/include.gradle

:config phase:  copyAarDependencies

:config phase:  addAarDependencies
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Common-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Data-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/facebook-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/List-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/Primitives-2017.1.201-dev-release.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/pushplugin.aar
	+adding dependency: /Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/libs/aar/widgets-release.aar

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/ignacio/Workspaces/DuenoVende/hezea-app/platforms/android/build.gradle' line: 802

* What went wrong:
A problem occurred evaluating root project 'ForSaleByOwner'.
> Failed to apply plugin [id 'com.google.gms.google-services']
   > For input string: "+"

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

BUILD FAILED

Got it!, I think the problem were the hooks not actually the platform.
I removed the hooks folder and the compilation worked. May be a catche there ?

@ignaciolarranaga I just reproduced the problem. However, for me the problem was solved with the suggestion for adding/removing platforms. I had the new plugin added after the android platform was initialized. Then the build failed with the same exception. I am using {N} 2.5.
The issue you described, however, really sounds like some cache/hooks problem (given the plugin now uses a hook). Let me know if there is a new information on the case.
Closing the issue for now.

@AntonDobrev just to comment I had to delete the node_modules and once rebuild it, the hook started executing again together with the problem, so I guess the hook is doing something wrong.
The problem was the same, it starts saying:
Failed to apply plugin [id 'com.google.gms.google-services']
For input string: "+"

Actually just realized that the compilation pass but the application failed at runtime:
02-16 06:12:55.885 3506-3506/? E/AndroidRuntime: FATAL EXCEPTION: main
                                                 Process: com.hezea.ForSaleByOwner, PID: 3506
                                                 java.lang.NoSuchMethodError: No static method zzdD(Ljava/lang/String;)Z in class Lcom/google/android/gms/common/util/zzv; or its super classes (declaration of 'com.google.android.gms.common.util.zzv' appears in /data/app/com.hezea.ForSaleByOwner-1/base.apk)
                                                     at com.google.firebase.FirebaseOptions.<init>(Unknown Source)
                                                     at com.google.firebase.FirebaseOptions.fromResource(Unknown Source)
                                                     at com.google.firebase.FirebaseApp.initializeApp(Unknown Source)

I got the reproduction from scratch, the problem arise when used together with nativescript-google-analytics (I guess because both use firebase), checkout out here: #101

Remove "Google Analytics" plugin..
remove platform android and add again
if it show firebase related error then go into AndroidStudio > SDK > AndroidRepositories and update
it should done

authors: AntonDobrev ignaciolarranaga philippsander vats28

repo: NativeScript/push-plugin


text:
Favicons

https://realfavicongenerator.net/ provides a service which creates a bundle of favicons to support for as many platforms/browsers as possible.

[x] Agree on Folder location for Banano favicons #98

[ ] Edit <link> and <meta> tags relevant to favicons in /src/index.html

@Nault/nano Are favicons created every time when building? (Asking because there is a folder src/assets/logo_source).

Only two minor deficiencies identified by Favicon Checker with the Nault favicons currently

@BitDesert
I got the BananoNault favicons ready.
Which path has to be used in site.webmanifest and browserconfig.xml ?
Relative to src/themes/banano/assets/favicon/ ?

If you want you can create a PR for them @sebrock
If the filename stays the same you don't have to change anything there.
The base path stays assets/*

Favicons working fine on Chrome 84

source: gharchive/issue

authors: BitDesert sebrock

repo: Nault/Nault

license: MIT

license_type: permissive

license_source: github-api


text:
[Improvement] Change namespaces

namespace SandboxPlus;

Yes, this might also happen to allow us to be compatible with addons built against/referencing Facepunch/Sandbox (though there might also be plenty of other issues with that preventing that from ever really being a possibility)

repo: Nebual/sandbox-plus


text:
Everything goes white

I get the following error:
[20175:0708/094729:ERROR:core.cc(335)] Received message with 1 handles, but handle table full
[20151:0708/094729:ERROR:channel.cc(300)] RawChannel read error (connection broken)

And then the UI becomes completely unresponsive and just displays a white screen, there's nothing I can do to revive it.
We're abandoning this repository as soon as the new UI is ready, so I'm not worried about fixing it. But I am worried about making sure it's not going to be a problem on the new UI so I'm documenting it.

I'm getting this same error with a kiosk webpage display on a Chromebox. Any help would be greatly appreciated!!

This seems like it may be a recently-introduced bug: http://code.google.com/p/chromium/issues/detail?id=502887
I was able to trace the error message to this function. Worth noting that the size of the handle table is 1M entries. This seems like a very high upper bound, so I suspect there is a leak of some sort that is preventing handles from being closed.

authors: DavidVorick lukechampine mikerichard

repo: NebulousLabs/Sia-UI

license: mit

license_source: bigquery


text:
Firefox Extension Support

Firefox supports much of the chrome.* extension API in order to make it easy to port chrome extensions to Firefox (and it's also related to the standard WebExtensions standard). The only difference, in this case, is that in some contexts (content script, window), the chrome value doesn't exist and the browser will throw an exception if you try to access it directly.
The change to make this portable to Firefox was quite trivial: we just need to verify chrome is defined before we check the property on it.
I have verified this with the LocalForageExplorer plugin, which I'm porting to Firefox.

mate can you please explain how would context identification work in firefox then? like you say it doesn't have chrome.* in content scripts?

Also, off-topic, how did you find out about this package? Upon googling relevant keywords, ext-messenger takes precedence than crx-bridge, I'm curious to know if you considered using ext-messenger as well.

Also, off-topic, how did you find out about this package?

Technically, from the chrome docs.

From this page, clicking "two alternative message passing techniques here."
Leads to this github issue where you commented at the end with a link to your package.

mate can you please explain how would context identification work in firefox then? like you say it doesn't have chrome.* in content scripts?

Firefox supports chrome.*, but only in certain contexts. In the window context, chrome doesn't exist and will throw an error if JS tries to access it. In the chrome browser, the chrome object exists in all contexts. The window context might be the only one that firefox does not support it, but I haven't extensively tested that.

I haven't extensively tested that
I think that's cool, this package doesn't promises firefox support anyway, it's like it might work, it might not. And this patch doesn't affect existing Chrome support badly so I'm cool with this.

Will get this merged and pushed by end of today.

Patch is now live in 2.2.0, please npm i again and see if everything's nominal and let me know if anything's off.
cheers.

source: gharchive/pull-request

authors: NeekSandhu jgillick

repo: NeekSandhu/crx-bridge


text:
🛑 Becpl Angular UI is down

In 680b35c, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in ff8c854 after 5 minutes.

repo: NehalDamania/becpl-uptime


text:
🛑 Becpl Angular UI is down

In 959cf9c, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 9c43362 after 7 minutes.


text:
🛑 Becpl Angular UI is down

In b443c72, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 74a3e16 after 6 minutes.


text:
🛑 Becpl Angular UI is down

In 5468a8d, Becpl Angular UI ($BECPL_ANGULAR_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Becpl Angular UI is back up in 2e3f45e after 5 minutes.


text:
Setup for more flexible responseStrategy

This PR is not finished and is open for the discussion.
This PR should make it possible to have different response strategies for different requests.
The property responseStrategy can now also be filled in with an object.
Example:
responseStrategy: [
  { patterns: /^\/server/, strategy: 'network-first' },
  { patterns: /./, strategy: 'cache-first' } // Matches everything else
]

What it will do is: It will check the requested url against all the responseStrategies (from top down) and if it find a match for the pattern and the url. Then that strategy will be used.
If nothing matches then the default ('cache-first') will be used.
It now matches against urlString but i am not sure if i should use urlString or cacheUrl
You can still use the already existing options so responseStrategy: 'network-first' should still work.
Todo:

[ ] Fix tests
[ ] Add tests

Issue: #275

This is fine, but you'll have to pass RegExp correctly from the config to the SW code somehow. I mean, there is a way of course, you may look how it's done with cacheMaps option. Also there should be a way to specify how to match the RegExp: against whole URL or only path + query, otherwise you'll have to specify domains all the time.
Thanks for the PR, this is very much appreciated :-)

@JordyMoos is this something you want to pursue according to @NekR's comments?

@GGAlanSmithee No I forgot about this project. It is too long ago

authors: GGAlanSmithee JordyMoos NekR

repo: NekR/offline-plugin


text:
Randomize directory names for model download

Currently, we are using the following https://github.com/Nelson-Gon/streamspeech/blob/7030cdda5be8b5dc5da65bd1f2e7131c0ea9f9b2/streamspeech/app_main.py#L32-L33
This is problematic because it will always attempt to either download models or load them from that specific folder which will sometimes fail with no obvious reason as to why it has failed.
This issue proposes using a randomized directory name as the save directory. A better approach might be to use some sort of caching to cache the models. This is related to #8

This is likely obsolete but leaving it here as I figure out what to do with TTS GANs

repo: Nelson-Gon/streamspeech


text:
neopt should be using CMake instead of make

Recommend targeting version 3.10 as a minimum requirement. Ubuntu 18.04 has version 3.10.2. VS2019 has a custom build of v3.14. I forget what VS2017 has, but I'm pretty sure it's later than 3.10

Seems about right for OSX too. I don't recall installing it but I got 3.10.2 on my system

@rodoufu do you think this is easily done?

The first thing I've suggested is the first issue =)
@igormcoelho ,  haven't seen anything too complicated in the makefiles, so I don't think it will be that difficult.
The first time I saw the project I was going to send a PR for that, but you said you were changing a lot of stuff so I decided to wait for a little.

authors: devhawk igormcoelho ixje rodoufu

repo: NeoResearch/neopt


text:
FileNotFoundError

Describe the bug
When using a separate location for the updated files it will try to delete the old ones and give a FileNotFoundError.
See gist: https://gist.github.com/falceso/96a597f0725e65a90f60fbcf5885e4f0
To Reproduce
Steps to reproduce the behavior:

Configure separate update location
Update any plugin
Get file not found error

Expected behavior
Removing of file should be stopped.

Fixed in: Version v1.1.1

repo: Neocky/pluGET


text:
Merge conflict missing files

Description
Unmerged paths:
  (use "git add <file>..." to mark resolution)
        added by them:   e2e/tests/lowCode.spec.ts

This file doesen't show in neogit.
for "added by us" and "both modified" it works now after https://github.com/NeogitOrg/neogit/pull/1216
Neovim version
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1703358377
Operating system and version
macOS 14.4.1
Steps to reproduce
Create 2 branches on one rename folder on the second one create file in folder then merge second to first.
Expected behavior
File should show just like for "added by us" and "both modified".
Actual behavior
File does not show in neovim and I need to manually add those files with git add <file> in terminal.
Minimal config
-- NOTE: See the end of this file if you are reporting an issue, etc. Ignore all the "scary" functions up top, those are
-- used for setup and other operations.
local M = {}

local base_root_path = vim.fn.fnamemodify(debug.getinfo(1, "S").source:sub(2), ":p:h") .. "/.min"
function M.root(path)
  return base_root_path .. "/" .. (path or "")
end

function M.load_plugin(plugin_name, plugin_url)
  local package_root = M.root("plugins/")
  local install_destination = package_root .. plugin_name
  vim.opt.runtimepath:append(install_destination)

  if not vim.loop.fs_stat(package_root) then
    vim.fn.mkdir(package_root, "p")
  end

  if not vim.loop.fs_stat(install_destination) then
    print(string.format("> Downloading plugin '%s' to '%s'", plugin_name, install_destination))
    vim.fn.system({
      "git",
      "clone",
      "--depth=1",
      plugin_url,
      install_destination,
    })
    if vim.v.shell_error > 0 then
      error(string.format("> Failed to clone plugin: '%s' in '%s'!", plugin_name, install_destination),
        vim.log.levels.ERROR)
    end
  end
end

---@alias PluginName string The plugin name, will be used as part of the git clone destination
---@alias PluginUrl string The git url at which a plugin is located, can be a path. See https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols for details
---@alias MinPlugins table<PluginName, PluginUrl>

---Do the initial setup. Downloads plugins, ensures the minimal init does not pollute the filesystem by keeping
---everything self contained to the CWD of the minimal init file. Run prior to running tests, reproducing issues, etc.
---@param plugins? table<PluginName, PluginUrl>
function M.setup(plugins)
  vim.opt.packpath = {}                      -- Empty the package path so we use only the plugins specified
  vim.opt.runtimepath:append(M.root(".min")) -- Ensure the runtime detects the root min dir

  -- Install required plugins
  if plugins ~= nil then
    for plugin_name, plugin_url in pairs(plugins) do
      M.load_plugin(plugin_name, plugin_url)
    end
  end

  vim.env.XDG_CONFIG_HOME = M.root("xdg/config")
  vim.env.XDG_DATA_HOME = M.root("xdg/data")
  vim.env.XDG_STATE_HOME = M.root("xdg/state")
  vim.env.XDG_CACHE_HOME = M.root("xdg/cache")

  -- NOTE: Cleanup the xdg cache on exit so new runs of the minimal init doesn't share any previous state, e.g. shada
  vim.api.nvim_create_autocmd("VimLeave", {
    callback = function()
      vim.fn.system({
        "rm",
        "-r",
        "-f",
        M.root("xdg")
      })
    end
  })
end

-- NOTE: If you have additional plugins you need to install to reproduce your issue, include them in the plugins
-- table within the setup call below.
M.setup({
  plenary = "https://github.com/nvim-lua/plenary.nvim.git",
  telescope = "https://github.com/nvim-telescope/telescope.nvim",
  diffview = "https://github.com/sindrets/diffview.nvim",
  neogit = "https://github.com/NeogitOrg/neogit"
})
-- WARN: Do all plugin setup, test runs, reproductions, etc. AFTER calling setup with a list of plugins!
-- Basically, do all that stuff AFTER this line.
require("neogit").setup({}) -- For instance, setup Neogit

If you're running nvim 0.10 you can test out neogit on our "nightly" branch. I've beed doing a ton of work there so I can use some newer APIs.

authors: CKolkey raaymax

repo: NeogitOrg/neogit


text:
Integrate with statuscolumn

Describe the solution you'd like
New statuscolumn PR just landed into neovim recently. Now we can configure statuscolumn just like statusline.
Describe alternatives you've considered
Currently embedded signs are fine, but integration via new statuscolumn may be considered.
Additional context

See plugin: luukvbaal/statuscol.nvim

Pretty happy with the current sign-based approach. We use it for a lot of stuff, like line highlighting.

authors: CKolkey hinell


text:
Deadlock caused by CLI RPC call prune-abandoned-monitored-utxos?

A call to this CLI command seems to have caused a deadlock in my node and left it hanging.
2023-10-24T09:17:21.051751975Z  INFO ThreadId(02) RPC{rpc.trace_id=00 rpc.deadline=2023-10-24T09:17:31.051541029Z otel.kind="server"}: tarpc::server: ReceiveRequest
2023-10-24T09:17:21.052049314Z  INFO ThreadId(02) RPC{rpc.trace_id=00 rpc.deadline=2023-10-24T09:17:31.051541029Z otel.kind="server" otel.name="RPC.prune_abandoned_monitored_utxos"}: tarpc::server: BeginRequest

Nothing after the above line was outputted by the client, indicating a deadlock in the software.

To avoid deadlock problems, perhaps we might consider using a crate like locktree or ordered_locks.    There might be others. I found these with a quick search.

locktree (ab)uses Rust's type system to guarantee that locks are always taken in the same order. Locks under locktree's management are organized into a linear sequence. Locks can only be acquired by moving forward into this sequence, and locks must be released when moving back. Thus it is statically impossible for two threads to acquire the same set of locks in different orders, and so deadlocks are impossible as long as all locks are managed by locktree.

Here are the tests for locktree, that give an idea of usage.
https://github.com/Ereski/locktree/tree/master/locktree/tests

I installed and ran lockbud, which performs static (compile time) analysis.   Full log of results is attached.
it did not detect any problems in neptune-core.   When analyzing triton-vm, it detected two possible atomicity violations in tokio fn that are called by triton-vm.  Not a smoking gun, but worth further investigation.
Examples of atomicity violations can be found at:
https://github.com/BurtonQin/lockbud/blob/all/Code/toys/atomic-violation/src/main.rs
These are all the dep crates that had possible issues: once_cell, getrandom, parking_lot, opentelemetry_sdk, tracing_subscriber, tokio, tokio_util.
If anyone ever needs to reproduce, the process is pretty easy.   The steps were:
$ git clone https://github.com/BurtonQin/lockbud.git
$ cd lockbud
$ rustup component add rust-src
$ rustup component add rustc-dev
$ rustup component add llvm-tools-preview
$ cd Code
$ cargo install --path .

neptune specific:
$ ln -s rust-toolchain.toml /path/to/neptune-core
$ ./detect.sh /path/to/neptune-core/ 2>&1 | tee neptune.log
[neptune.log](https://github.com/Neptune-Crypto/neptune-core/files/13272446/neptune.log)

I am able to reproduce this reliably, though behavior varies a bit from that described @Sword-Smith.
Steps:

Start neptune-core running with command:
RUST_BACKTRACE=1 RUST_LOG='info,neptune-core=warn,tarpc=warn' cargo run --bin neptune-core -- --mine --throttled-mining --peers 51.15.139.238:9798 --peers 139.162.193.206:9798

Wait until log indicates mining has begun.

Observe in top that CPU usage is well below 50%.

Execute neptune-cli prune-abandoned-monitored-utxos

Observations:

tarpc logs DeadLineExceeded.
neptune-cli prints Error: the request exceeded its deadline
top reports neptune-cli using 100% cpu.
Some neptune-cli rpc calls still succeed, eg: block-height, get-peer-info
Other rpc calls hang, eg: synced-balance, wallet-status
shutdown rpc call appears to succeed in neptune-cli output, however the server does not actually shutdown.
Server logs SIGINT and SIGTERM, but does not terminate.
Finally can be killed with killall -9 neptune-core.
I did not see the same log-lines as @Sword-Smith.  Possibly due to different invocation.  @Sword-Smith can you post the command you start neptune-core with?

Here is a sample log from the last of 3 runs:
2023-11-07T00:33:26.991327035Z  INFO ThreadId(01) neptune_core::main_loop: Performing peer discovery
2023-11-07T00:34:24.034572892Z  WARN ThreadId(01) neptune_core::models::state: Could not recover MSMP as transaction appears to be on an abandoned chain
2023-11-07T00:34:41.685048134Z ERROR ThreadId(03) tarpc::server::in_flight_requests: DeadlineExceeded
2023-11-07T00:36:45.765176191Z ERROR ThreadId(02) tarpc::server::in_flight_requests: DeadlineExceeded
2023-11-07T00:37:14.501046128Z ERROR ThreadId(03) tarpc::server::in_flight_requests: DeadlineExceeded
2023-11-07T00:37:26.624843189Z  INFO ThreadId(03) neptune_core::peer_loop: Got new block from peer 51.15.139.238:9798, block height 8914
2023-11-07T00:37:26.627328157Z  INFO ThreadId(03) neptune_core::models::blockchain::transaction::validity: validity logic for 'kernel_to_lock_scripts', 'kernel_to_type_scripts', 'type_scripts_halt' not implemented yet.
2023-11-07T00:37:26.652194487Z  INFO ThreadId(03) neptune_core::peer_loop: Block with height 8914 is valid
2023-11-07T00:37:26.652287726Z  INFO ThreadId(03) neptune_core::peer_loop: Updated block info by block from peer. block height 8914
2023-11-07T00:37:27.947861033Z  INFO ThreadId(03) neptune_core::peer_loop: Got new block from peer 139.162.193.206:9798, block height 8914
2023-11-07T00:37:27.950371622Z  INFO ThreadId(03) neptune_core::models::blockchain::transaction::validity: validity logic for 'kernel_to_lock_scripts', 'kernel_to_type_scripts', 'type_scripts_halt' not implemented yet.
2023-11-07T00:37:27.974812671Z  INFO ThreadId(03) neptune_core::peer_loop: Block with height 8914 is valid
2023-11-07T00:37:27.974893116Z  INFO ThreadId(03) neptune_core::peer_loop: Updated block info by block from peer. block height 8914
^C2023-11-07T00:38:43.449094383Z  INFO ThreadId(03) neptune_core::main_loop: Received SIGINT

Analysis:

Given that this is so far 100% reproduceable, it should be feasible to track down.
The 100% CPU usage appears to indicate the code is stuck in a loop somewhere, rather than deadlocked.

Fixed by @dan-da in 1a97899191215b1af385a2ed047829dfa6fe3f29

authors: Sword-Smith dan-da

repo: Neptune-Crypto/neptune-core


text:
Trying to change my default US layout to SP layout

I'm trying to create a USB Rubber Ducky with Raspberry Pi Pico following this tutorial: https://www.youtube.com/watch?v=e_f9p-_JWZw&t=472s
The thing is i've tried to get your layout and keycode for SP keyboard, move both file to the raspberry pico lib folder, and i've also changed code.py as you suggested on this post: https://github.com/dbisu/pico-ducky/issues/10#issuecomment-910684858
When I've done everything, my code.py corrupted and could do anything else. What am I doing wrong?
Thanks for your time.
Regards,
Guillem

Corrupted ? Like, the content of the file is messed up ? Or do you just mean it doesn't execute ?
There's 3 files to copy (py or mpy version)

keyboard_layout.py
keyboard_layout_win_sp.py
keycode_win_sp.py

You can see if there's an error printed out to the serial console:
https://learn.adafruit.com/welcome-to-circuitpython/kattni-connecting-to-the-serial-console
If you can use discord, it's the better place for support, #help-with-circuitpython on the adafruit discord. (No private messages).

I was missing the keyboard_layout.py... Somehow I didn't read that this file should've been moved to the raspberryxd. Thx for your help.
Btw do you know how to prevent the rubber ducky script from running every time it's plugged in?
Thx for your help mate

authors: GuillemRX Neradoc


text:
Button gets triggered accidentally when swiping for scrolling on mobile

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue: Current
Last working release (if known): /
Browser and Operating System:
Android 13 with HomeAssistant App

Description of problem:
Tile card feature buttons are getting triggered by accident when swiping to scroll.
I posted a video showing the issue: https://youtu.be/fRQNLYEdWv4.
The button should only be triggered if actually pressed. I guess there is something wrong with the event listeners on the button.

Javascript errors shown in the web inspector (if applicable): /
YAML of tile card:
features:
  - type: custom:service-call
    entries:
      - type: button
        icon: mdi:power
        tap_action:
          action: call-service
          service: switch.toggle
          target:
            entity_id: switch.fernsehbank_steckdosenleiste_schalter
type: tile
entity: switch.fernsehbank_steckdosenleiste_schalter
name: TV Bank
icon: mdi:power-socket-eu
state_content: state
vertical: false
show_entity_picture: false

That's a weird one, nice find. I'm able to recreate it on my phone and on desktop browsers when using the device toolbar in developer tools.
I believe it's an issue with touch events triggering when swiping to scroll, something I hadn't accounted for. I think I can use touchmove to detect scrolling and not fire actions if there is scrolling.

Should be fixed in 3.1.1. Fixing it for buttons/selectors was pretty easy, but sliders proved difficult. If your finger moves when you're tapping on a button or selector option the feature will now consider it a swipe and not call an action. This doesn't work for slider though, since you're supposed to be able to swipe on them. My solution for sliders is as long as the x distance is less than the y distance while swiping it'll consider it a slider action and not a scroll swipe.

Thank you very much 👍

authors: Feuerhamster Nerwyn

repo: Nerwyn/service-call-tile-feature


text:
Dep problem

Here error that i get when i try to install kansha :
Using /usr/lib/python2.7/site-packages/kansha-2.0.7-py2.7.egg
Not found: /tmp/easy_install-U__Cza/kansha-2.0.7/vendors
Processing dependencies for kansha
Searching for nagare[database,i18n]==0.4.1.post473
Reading http://www.nagare.org/snapshots/
Reading https://pypi.python.org/simple/nagare/
No local packages or download links found for nagare[database,i18n]==0.4.1.post473
error: Could not find suitable distribution for Requirement.parse('nagare[database,i18n]==0.4.1.post473')

I have find my problem.
Upgrade setuptools
pip install setuptools --upgrade

repo: Net-ng/kansha


text:
[ARCTIC-994] fix serialization for target files of hive support table

Why are the changes needed?

misuse of com.netease.arctic.utils.SerializationUtils#toInternalTableFile
Brief change log

change to com.netease.arctic.utils.SerializationUtils#toContentFile for target files

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduces a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @shidayang

repo: NetEase/arctic


text:
DefaultAppConfig simplification

Modify DefaultAppConfig to be a DelegatingConfig instead of a CascadingCompositeConfig to avoid exposing all of the CascadingCompositeConfig functionality.
Remove withLoadSystem from ConfigLoader
Expose getting any layer from AppConfig

archaius-pull-requests #222 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » archaius » archaius-pull-requests #53 FAILURE
Looks like there's a problem with this pull request

archaius-pull-requests #223 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » archaius » archaius-pull-requests #54 FAILURE
Looks like there's a problem with this pull request

archaius-pull-requests #224 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » archaius » archaius-pull-requests #55 FAILURE
Looks like there's a problem with this pull request

archaius-pull-requests #225 SUCCESS
This pull request looks good

NetflixOSS » archaius » archaius-pull-requests #56 SUCCESS
This pull request looks good

NetflixOSS » archaius » archaius-pull-requests #57 SUCCESS
This pull request looks good

archaius-pull-requests #226 SUCCESS
This pull request looks good

@brharrington, thanks for the thorough review.  I believe all your comments have been addressed but there is one thing I'm not too happy about.  Should we allow setting an external application layer Config AND try to load the configuration properties files as well.  Currently, when an external application config is provided DefaultAppConfig will silently not load the application properties.  Does it make sense to load both into a composite layer?

Can it just be a special case of calling withApplicationConfig? In which case if you do both it would be the same as calling withApplicationConfig twice on the same builder. It seems like this is mostly a question of what the builder makes convenient, if a user needs to have a config and load the configuration properties then they could just set the application layer to a composite themselves.

repo: Netflix/archaius


text:
[DOC]: Dead link for installing and running conductor in production

What are you missing in the docs

The above link is dead and leads to a 404 page. Looking through the docs files, it's not clear whether the source for this page actually exists.
Proposed text
It would be fantastic to have some documentation about running conductor in production, in addition to the existing instructions for running the in-memory version to try it out.

Thanks for bringing this to our attention. We are currently working on improving our documentation and will update this section soon.

Should be fixed with docsite update.

authors: ProjectFrank apanicker-nflx peterlau

repo: Netflix/conductor


text:
Codegen to support sparse updates

GraphQL Mutation requires an input object.  This input object has optional fields, and all those fields are not set in a mutation call, the default Deserialization by this codegen utility for all those missing fields are set to default value if specified in the schema or "null".  This will result in DGS/subgraph overwriting those fields with default value/"null", which is not desirable.
Codegen deserialization should mark fields that are not provided, so that the DGS/subgraph  implementation can handle sparse updates.
Example
Schema
mutation {
  patchProfile(input: ProfileInput!): Profile
}

input ProfileInput {
  id: ID!
  name: String
  address: String
}

type Profile {
  id: ID!
  name: String
  address: String
}

Mutation call
mutation patchProfile($input: ProfileInput!) {
  patchProfile(input: $input) {
    id
    name
    address
}

Calls
Call 1
Input
{
  "id": "1",
  "address": "new address"
}

DGS for the field name gets default value when specified by schema or "null",  and will overwrite the value that was already there for the name field.
After fixing this issue, only address should be updated and remaining fields should not be altered.
Call 2
Input
{
  "id": "1",
  "name": "New name",
  "address": null
}

Deserialization works well for this now (DGS will set the address to null and name to "New name".
After fixing this issue, when the user explicitly sets a field to null, it should be honored.

Example gitrepo to reproduce this issue: https://github.com/ramapalani/sparseupdate

repo: Netflix/dgs-codegen


text:
Is there a list of all required env variables?

Is there a comprehensive list of all the required env variables that are required to:
A.) Successfully run dispatch and
B.) Successfully integrate all plugins
The documentation contains some, as do the env example file, but I've found from looking through previous issues that there are other env variables that are mentioned in some responses there that are not present in the documentation or the env example file?
When creating incidents, there are some of the plugins/integrations that do not work, and I'm wondering if I have the correct/all of the required env variables.
Thanks!
Gary

For example, I have all the required & correct JIRA envvars included as per documentation, but are there any more steps to creating a JIRA ticket upon incident creation?  One is not created.

Was able to find these via going back through old documentation.

repo: Netflix/dispatch


text:
Provide a more robust way to get local host info

Ref #617 (unfortunately the pull is not re-openable). There is a similar fix in the transport refactoring branch work but it need to be also ported to the older code base.

New transport is now the default, closing.

repo: Netflix/eureka


text:
@conda/@pypi appears to remove CUDA instructions for GPU

Hello,
As the title mentions, I am trying to get a job run on AWS Batch that will run on a GPU. When I omit the @conda/@pypi decorator, I am able to see that a GPU is allocated. However, when I throw on an @conda/@pypi decorator, I am unable to get a GPU appear. Why is this? For reference, I am essentially using this Cloud Formation template.
Here is some simple code to demonstrate the issue. Again this occurs whether I use @pypi or @conda. I am using MetaFlow version 2.12.5. Note that if I omit the tensorflow library in the @conda decorator, I get a ModuleNotFoundError: No module named 'tensorflow', so the @conda/@pypi decorators seems to wipe the Tensorflow library from the compute instance.
from metaflow import FlowSpec, step, batch, conda, conda_base

@conda_base(python='3.12')
class test_gpu(FlowSpec):
    @batch(gpu=1, image="docker.io/tensorflow/tensorflow:latest-gpu", queue="job-queue-gpu-metaflow",)
    @conda(libraries={'tensorflow': '2.16.1'})
    @step
    def start(self):

        import tensorflow as tf
        print("tensorflow" + tf.__version__)

        import sys
        print("Python version")
        print(sys.version)

        print("Num GPUs Available: ", len(tf.config.list_physical_devices('GPU')))

        self.next(self.end)

    @step
    def end(self):

        print("All done. \n\n Congratulations!\n")
        return

if __name__ == '__main__':
    test_gpu()

For reference, this is the output:
2024-06-27 14:54:07.462 Creating local datastore in current directory (/Users/ed/Developer/metaflow-test-gpu/.metaflow)
2024-06-27 14:54:07.462 Bootstrapping virtual environment(s) ...
2024-06-27 15:17:46.520 Virtual environment(s) bootstrapped!
2024-06-27 15:17:47.734 Workflow starting (run-id 15):
2024-06-27 15:17:52.723 [15/start/56 (pid 5595)] Task is starting.
2024-06-27 15:17:54.545 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status SUBMITTED)...
2024-06-27 15:17:57.656 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:18:27.686 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:18:57.741 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:19:27.845 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:19:28.346 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:19:58.409 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:20:28.590 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:20:58.855 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:21:27.582 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNING)...
2024-06-27 15:21:26.689 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Setting up task environment.
2024-06-27 15:21:34.717 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Downloading code package...
2024-06-27 15:21:35.552 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Code package downloaded.
2024-06-27 15:21:35.590 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting.
2024-06-27 15:21:35.983 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Bootstrapping virtual environment...
2024-06-27 15:22:00.642 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Environment bootstrapped.
2024-06-27 15:22:02.275 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] 2024-06-27 22:22:02.275781: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
2024-06-27 15:22:02.275 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-06-27 15:22:04.153 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] tensorflow2.16.1
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Python version
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] 3.12.0 | packaged by conda-forge | (main, Oct  3 2023, 08:43:22) [GCC 12.3.0]
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Num GPUs Available:  0
2024-06-27 15:22:31.518 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task finished with exit code 0.
2024-06-27 15:22:32.432 [15/start/56 (pid 5595)] Task finished successfully.
2024-06-27 15:22:33.633 [15/end/57 (pid 8378)] Task is starting.
2024-06-27 15:22:40.407 [15/end/57 (pid 8378)] All done.
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)]
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)] Congratulations!
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)]
2024-06-27 15:22:42.793 [15/end/57 (pid 8378)] Task finished successfully.
2024-06-27 15:22:43.116 Done!

@EdIzaguirre - @conda and @pypi provide a clean virtual environment. The default tensorflow conda package is not GPU-compatible; have you tried the tensorflow-gpu package instead?

When I try using the tensorflow-gpu package instead of tensorflow in the @conda decorator, I get:
Micromamba ran into an error while setting up environment:
    command '/Users/ed/.metaflowconfig/micromamba/bin/micromamba create --yes --quiet --dry-run --no-extra-safety-checks --repodata-ttl=86400 --retry-clean-cache --prefix=/var/folders/y6/vkmmb9lj41q4_0dq4q_h0xyh0000gn/T/tmplv17ujp3/prefix --channel=conda-forge --channel=Microsoft --channel=defaults requests==>=2.21.0 boto3==>=1.14.0 tensorflow-gpu==2.6.0 rmg::glibc==2.19 python==3.12' returned error (1)
    nothing provides __glibc >=2.17 needed by tensorflow-base-2.6.0-cuda110py37hb8f09f9_2

. Notably, when I use the @pypi with the tensorflow library, I do see a GPU. However, one of my packages doesn't work with @pypi, so I would like to use the @conda decorator.

You may be able to try CONDA_OVERRIDE_GLIBC=2.17 as an env var. You can also try the bleeding edge decorators that allow you to combine conda and pypi (see here: https://docs.metaflow.org/scaling/dependencies/libraries#bleeding-edge-versions-of-the-decorators) and also handle the GLIBC notion a little bit differently. +1 to @savingoyal 's point about package name and the "clean slate". Package names usually match between pypi and conda but that is not always the case; conda still distinguishes the GPU version (it basically adds additional dependencies). Feel free to come on slack too for a more interactive conversation. There is a similar question that was asked there in the last two weeks iirc.

Hi Romain, it's Ed, the same guy from the Slack 😅. I wanted to formalize my question on the GitHub, sort of put all my comments/thoughts in one post.
I was able to get tensorflow-gpu conda library working when setting the Python version to 3.9. I still am having issues with my other library (keras-cv) but I suppose that deserves it's own post. Thanks!

authors: EdIzaguirre romain-intel savingoyal

repo: Netflix/metaflow


text:
Use different flags for chunked and regular data in memcached

The data in memcached should be set with different flags when the chunked handler is used and when the standard handler is used. This is helpful to differentiate the data if we ever want to have tooling that doesn't speak to memcached through the rend proxy.

The chunking feature is basically never used for Netflix purposes anymore, and it doesn't seem like this feature adds a whole lot of value. We also use our EVCache Client to communicate with the cache, which has its own set of flags that we would want to avoid. It is generally known internally if a cache is chunked or not, and this metadata wouldn't really help.

repo: Netflix/rend


text:
Ensure /run is executable for backward compatibility

The previous pre-tmpfs behaviour was to allow executables in /run, so preserve that behaviour.

Pull Request Test Coverage Report for Build 3103

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 25.961%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

executor/runtime/docker/docker.go
0
1
0.0%

Totals

Change from base Build 3089:
0.0%

Covered Lines:
3000

Relevant Lines:
11556

💛  - Coveralls

Pull Request Test Coverage Report for Build 3108

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 25.961%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

executor/runtime/docker/docker.go
0
1
0.0%

Totals

Change from base Build 3089:
0.0%

Covered Lines:
3000

Relevant Lines:
11556

💛  - Coveralls

authors: coveralls rgulewich

repo: Netflix/titus-executor


text:
Rerender region

I'm trying to dynamically update data. While providing 2 different JSON files with data (first sample_data.json, then sample_data_simple.json after 5 seconds), I expect region view to remove regions which are not present within updatedTraffic. How can I force Vizceral to update regions correctly?

Addressed in https://github.com/Netflix/vizceral/commit/dea6b2e44447c845af545bf30064de90ec364362 and pushed in vizceral@4.3.2. If you make sure dependencies are fully up to date, vizceral-react should pull in vizceral@4.3.2.

authors: Baransu jrsquared

repo: Netflix/vizceral-example


text:
Update log4j to 2.17.1 to address CVE-2021-44832.

https://nvd.nist.gov/vuln/detail/CVE-2021-44832

Closed in favor of https://github.com/Netflix/zuul/pull/1169

authors: Chromico argha-c

repo: Netflix/zuul


text:
Add brkraw

Fixes #601
Builds fine on my local system. May need a updated version of TinyRange on the self-hosted builder.

There is a issue with the current version. It creates a python virtual environment in /root/pyenv. This is required with Alpine since pip doesn't let you install distribution wide packages. This will need to be fixed before we can merge. Any thoughts @stebo85?

Why build in alpine in the first place? Would Debian / centos work better?
Thank you
Steffen
--
W: https://mri.sbollmann.nethttps://mri.sbollmann.net/  | W: https://www.neurodesk.orghttps://www.neurodesk.org/  | T: https://twitter.com/sbollmann_MRI  | G: https://github.com/stebo85
Book meeting: https://calendly.com/s-bollmann/meeting

From: Joshua Scarsbrook @.>
Sent: Friday, February 23, 2024 10:31:44 AM
To: NeuroDesk/neurocontainers @.>
Cc: Steffen Bollmann @.>; Mention @.>
Subject: Re: [NeuroDesk/neurocontainers] Add brkraw (PR #602)
There is a issue with the current version. It creates a python virtual environment in /root/pyenv. This is required with Alpine since pip doesn't let you install distribution wide packages. This will need to be fixed before we can merge. Any thoughts @stebo85https://github.com/stebo85?
—
Reply to this email directly, view it on GitHubhttps://github.com/NeuroDesk/neurocontainers/pull/602#issuecomment-1960569330, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6V2W235UEQXNVVEKL75WLYU7PPBAVCNFSM6AAAAABDV4G2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRQGU3DSMZTGA.
You are receiving this because you were mentioned.Message ID: @.***>

I've switched it to Ubuntu. This version works fine.
I started with Alpine to see if I could get the container size a little smaller.

Yes, great it works now :) good idea to start with alpine - one day we will find a package where alpine works well :p
Thank you
Steffen
--
W: https://mri.sbollmann.nethttps://mri.sbollmann.net/  | W: https://www.neurodesk.orghttps://www.neurodesk.org/  | T: https://twitter.com/sbollmann_MRI  | G: https://github.com/stebo85
Book meeting: https://calendly.com/s-bollmann/meeting

From: Joshua Scarsbrook @.>
Sent: Friday, February 23, 2024 10:44:53 AM
To: NeuroDesk/neurocontainers @.>
Cc: Steffen Bollmann @.>; Mention @.>
Subject: Re: [NeuroDesk/neurocontainers] Add brkraw (PR #602)
I've switched it to Ubuntu. This version works fine.
I started with Alpine to see if I could get the container size a little smaller.
—
Reply to this email directly, view it on GitHubhttps://github.com/NeuroDesk/neurocontainers/pull/602#issuecomment-1960581837, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA6V2W5CL7TKNY6L3HVL5ATYU7RALAVCNFSM6AAAAABDV4G2V2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRQGU4DCOBTG4.
You are receiving this because you were mentioned.Message ID: @.***>

repo: NeuroDesk/neurocontainers


text:
Bsmart refactoring

Refactors bsmart.py to make the code cleaner and more Pythonic

@cliffckerr - shouldn't affect the results right??

@cliffckerr - can you confirm you tested some examples (ideally some in netpyne/examples?) and got identical results?  thx!

@cliffckerr - can you confirm you tested some examples (ideally some in netpyne/examples?) and got identical results? thx!

Once we have confirmation that this PR produces identical results, we will accept it.  @cliffckerr

authors: cliffckerr joewgraham salvadord

repo: Neurosim-lab/netpyne


text:
Add missing JavaScript docs for the Sarufi SDK

Hello, @Kalebu the following have been done:-

Add missing docs for the JavaScript SDK
Fix some typos
Improve document styling for some tabular view parts
Add the chat method to the global sarufi import in the JavaScript SDK

This PR fixes #1

Hi @BaharaJr
Thank you for your awesome documentation contribution
Merging this into main

authors: BaharaJr Kalebu

repo: Neurotech-HQ/sarufi-docs


text:
Geforce Experience

Any way to make this work with users who play using Geforce experience service? =(

Unfortunately no, this is on GGG's side.

authors: NeverSinkDev diegosilent


text:
profile picture addition

Here, I have added my profile picture to the Hacktoberfest2020 repository

This is a pull request I have made to add my profile picture to the repository


text:
fix: textlintが落ちまくってるのがこれで治ってください！！！

textlintをupgradeしたら治るような気がしました
https://github.com/tsuyoshicho/action-textlint/pull/68

@all-contributors please add @Shinyaigeek for tool

authors: Shinyaigeek yokinist


text:
CodeQL tests are deprecated

The version of CodeQL that this is using to run tests it deprecated and no longer receiving updates. Need to upgrade to v2.
https://github.blog/changelog/2023-01-18-code-scanning-codeql-action-v1-is-now-deprecated/
Not a huge vulnerability issue, but could result in problems.

Merged and applied to 1.x and 2.x

license: ISC


text:
Finish Advanced Usage Documentation

Updates needed:

HTTP-Client: HTTP Client for requests using aiohttp
Utils - Utility Extension for openhiven.py for expanded logic and functionality in openhiven.py
Event Handler - EventHandler Class used to trigger events and register new methods

Will need to do this when the rewrite is done


text:
WIP: Immunizationproject

This pullrequest adds extension for a reference from the nl core profiles vaccination-event to pharmaceuticalProduct and this extension is added to the vaccination-event profile. From the zib-Vaccination-event profile the constraint of using 'mL' as a unit for dosage is removed and the occurence is set to datetime (so that a string is no longer allow voor vaccition events). Lastly the definitions of the vaccinationDate in the vaccination event and the vaccination recommendation is changed to clearify the distinction.

[x] Add a definition to the pharmaceuticalProduct reference extension

I closed this pull request because this branch includes the integration branch. I created a new branch with the same commits but with the integration branch merge and opened a new Pull Request here


text:
Elongate the deepmedic network

Hi, I want to elongate the deepmedic network so I added a few more numbers in the variable 'self.conv_features' in deepmedic.py.
E.g.,

self.conv_features = [30,30,40,40,40,40,50,50] --> [30,30,40,40,40,40,50,50,50,50]

But I got this error message:
`
ValueError: Dimension 1 in both shapes must be equal, but are 7 and 3. Shapes are [10,7,7,7] and [10,3,3,3]. for 'worker_0/DeepMedic/residual_concat/concat' (op: 'ConcatV2') with input shapes: [10,7,7,7,50], [10,3,3,3,50], [] and with computed input tensors: input[2] = <-1>.
originally defined at:
File "/home/RR/Niftynet/niftynet/layer/elementwise.py", line 31, in init
super(ElementwiseLayer, self).init(name=self.layer_name)
File "/home/RR/Niftynet/niftynet/layer/base_layer.py", line 58, in init
super(TrainableLayer, self).init(name=name)
File "/home/RR/Niftynet/niftynet/layer/base_layer.py", line 26, in init
self.op = tf.make_template(name, self.layer_op, create_scope_now=True)
File "/home/RR/.local/lib/python2.7/site-packages/tensorflow/python/ops/template.py", line 153, in make_template
**kwargs)
`
I guess that this has to do with the output size after upsampling..
Thanks so much!

I have the same issue!! also waiting for an answer

In the deepmedic framework, the two paths must end with patches of similar spatial sizes. By using the "VALID" option in the convolution layer, adding new layers will break this consistency. You have to calculate the required initial patch size (and associated number of layers) to make this possible.

authors: RayJkl RocketRollxx mmodat

repo: NifTK/NiftyNet


text:
German traffic sign recognition benchmark Model

Dataset

https://benchmark.ini.rub.de/?section=gtsrb&subsection=dataset

Hey! I would like to work on this issue. Can you please assign this issue to me under GSSoC'22?

Make PR till 31 May.

Sure. Thanks!

Hey! I have created the pull request. Could you please take a look?

@Rutikab12 I have added another commit to the PR for this issue. Can you check that one? I think it should work now.

repo: Niketkumardheeryan/ML-CaPsule


text:
AI Language Learning Assistant

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The primary goal of the "AI Language Learning Assistant" script is to create a helpful tool for language learners to practice and enhance their language skills in an interactive and engaging manner. By offering conversation practice, vocabulary quizzes, grammar exercises, and pronunciation feedback, the script aims to support users in becoming more confident and proficient in the target language.
Use Case
The script, "AI Language Learning Assistant," is a Python program designed to assist language learners in practicing and improving their target language skills. The main aim of the script is to provide an interactive and engaging learning experience for users, helping them enhance their vocabulary, grammar understanding, and pronunciation.
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign this to me @Niketkumardheeryan


text:
Implement syntax checker for django

Think this will be helpful

Is this supposed to be a lint?

This issue refers specifically to the rubric item "use of syntax checkers." Looking up what a lint is, I think that would probably fulfill the requirement, so yes?


text:
Wasm builds fail

Thanks for making this template, but when I try to follow the steps to build for web on a fresh clone of this repo, it fails with the following output:

Finished dev [optimized + debuginfo] target(s) in 2m 01s
Running wasm-server-runner target/wasm32-unknown-unknown/debug/bevy_game.wasm
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /home/pixelartist/.cargo/registry/src/github.com-1ecc6299db9ec823/wasm-bindgen-cli-support-0.2.79/src/descriptor.rs:208:15

I get the same error when I try to use Github Actions to build this template from tags. It seems like an issue with the wasm-bindgen step?
However, I am able to build the standard Bevy examples to web just fine.
Is anyone else running into this issue? I'm running the latest version of Pop OS (Linux) and am able to build the template for Linux just fine, just not for web.

This seems to be an issue with the latest version of wasm-bindgen-cli.
See rustwasm/wasm-bindgen#2776

Everything works fine for me on 0.2.78
I pinned the crate to this version in the makefile for now. Let me know if that resolves the issue for you, too.

Hey, great template, thanks very much for your hard work!
Getting the same issue as descirbed above, building on OSX 12.1:
Finished dev [optimized + debuginfo] target(s) in 2m 24s
     Running `wasm-server-runner target/wasm32-unknown-unknown/debug/bevy_game.wasm`
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /Users/freddywordingham/.cargo/registry/src/github.com-1ecc6299db9ec823/wasm-bindgen-cli-support-0.2.79/src/descriptor.rs:208:15
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Building and running natively works no problem

I also tested it on 0.2.79 and it works fine there, too.

Do you still get this issue using the new web setup with trunk?

With the new setup the web workflow should have improved a lot.
I'll close this for now. If you still run into issues with the new setup, feel free to open a new issue :slightly_smiling_face:

authors: CashWasabi FreddyWordingham NiklasEi sfarmer1


text:
Add missing requirements

This addresses #22.

Using requirements.txt will be outdated as soon as #18 is merged. Hence, I will close this PR but thanks for the support!

Alright, my pleasure 🙌🏾

repo: Nimuedaertya/reallife-quest-murder-game


text:
Alert Notifications Not Displayed on Tipping Page in Enatega Multivendor.

Issue: Alert Notifications Not Displayed on Tipping Page in Enatega Multivendor
Description:
There is an issue where alert notifications are not being displayed on the tipping page. This issue hinders the user's ability to receive important alerts or information while on the tipping page.
Impact:
User Awareness: The absence of alert notifications may result in users missing important information or updates related to tipping.
User Experience: A comprehensive user experience includes the timely display of notifications across all relevant pages.
Steps to Reproduce:

Access the tipping page within the application.
Observe the absence of alert notifications or any alerts that should be displayed.

Expected Resolution:
The issue should be addressed to ensure that alert notifications are correctly displayed on the tipping page. This ensures that users receive important information and updates while using this feature, enhancing the overall user experience.

Hello @Sohailqureshi9 ,
I'm pleased to inform you that we've resolved the issue where alert notifications were not displayed on the tipping page in the Enatega Multivendor Admin Dashboard.
Thank you for reporting this issue, and we appreciate your patience. If you encounter any more issues or have additional feedback, please don't hesitate to reach out.
Best regards,
@beKashif
@Ninjas-Code-official/ninjas-code


text:
🛑 IRIS is down

In 50a6576, IRIS (https://iris.dscvit.com) was down:

HTTP code: 520
Response time: 10439 ms

Resolved: IRIS is back up in 8f9d64b.

repo: Nirmitjatana/upptime-personal


text:
Cannot remove RK using Chrome

As a user I cannot remove RK using the Chrome interface for managing FIDO2 Security Key (non-Windows OS only).
Firmware version: v1.0.1, v1.0.2 (market samples).
Reproduction:

Create RK, e.g. using OpenSSH
Try to remove it using Chrome
See error:

Security key sign-in data. Your sign-in data couldn't be deleted

Cannot reproduce with v1.1.0.  @szszszsz Can you please try again with the current firmware?

Cannot reproduce with 1.3RC1, too.
Should we close this ?

authors: daringer robin-nitrokey szszszsz


text:
Add AARCH64 channels for NixOS 20.09

This adds a channel for NixOS 20.09 on AArcch64 based on the hydra
jobset that we already have.
The topic of an aarch64 specific channel has come up regular and as
these devices are gaining in popularity will only be discussed more
often.
This had been discussed on the nixpkgs issue tracker: https://github.com/NixOS/nixpkgs/issues/83049

Just in case, as an, ahem, an active participant if the discussion of the RFC mentioned here, I am pretty sure that promoting aarch64 to full Tier 1 is supposed to be  complicated process (because it needs to move expectations in the review process, which is the hard part in our case).
And that means that merging this PR today makes perfect sense — it just improves aarch64-linux tooling for now, without creating much new burden on Hydra or any process burden on other platforms. And «proper» upgrades towards Tier 1 will take a couple of forevers, so it's good to have what we can have cheaply.

Updated the PR for 21.05. I still don't think we need to move the platform to a higher tier in order to add a channel for it.

I don't see any reason to not do this, other than a potential cost of confusion if we were to continue adding many channels for many different use cases We should probably use this PR as a learning experience and improve the "how to do a new architecture" flow with what we've learned.

Deployed.

I don't think we can have a «how to do a new architecture» flow above Tier 3, because small details in context can have unreasonable influence on the events (see aarch64-darwin…) And of course each of the architectures worth such a discussion will be important for its own and unique reasons.
I am not sure too many people would succeeed at telling how many channels there are, so the confusion might be somewhat limited. Maybe discussing a good way to present the choices so that we can add more channels based on things that are built anyway could be useful, though!

authors: 7c6f434c andir grahamc

repo: NixOS/nixos-org-configurations


text:
Reorganize gnome package set

Issue description
We have packages that are part of the gnome package-set spread out over nixpkgs.
For example:

clutter
gcab
glib
gtk
networkmanager
vala

Imo these should be part of the gnome package set and only have top-level aliases.
This would make the gnome set consistent with upstream and also make updating easier. Currently the maintainers script only picks up the stuff that is actually inside pkgs/desktops/gnome-3/ and is limited to packages that follow the gnome release cycle versioning.
If we stick to the gnome package layout for all packages we can check the cache.json for the relevant gnome version und pick up all version changes from there
Just take a look at clutter and vala for examples of the problems this introduces into nixpkgs.
There are old unused derivations and the current versions use overrides to pick up correct dependencies.
I'm working on cleaning up some of the cruft at the moment, but in the future I think this change will facilitate stuff greatly.
Most if not all of these packages should probably be moved:
ag --ignore 'gnome-*' mirror...gnome pkgs
95

CC
gnome maintainers @DamienCassou @lethalman
glib maintainers @lovek323 raskin urkud
gtk+ maintainers urkud raskin @vcunat @lethalman
vala maintainers @antono @lethalman

I somewhat agree but something tells me this is not a good idea... have to think about it. @vcunat do you have an idea about this?

glib: I believe this one can be shared and makes little sense to bind to gnome version. I don't remember a glib update causing wider problems anywhere.
gtk+: I suppose you only mean versions >= 3.x, but even there I'm not certain what exactly will happen with the new stable versioning scheme. I assume gnome releases will require those "unstable" 3.9x, perhaps each gnome release with a different "x" (we might alias the latest one as gtk4). Most of nixpkgs tree will have to remain on gtk3 3.22.y, as I don't expect apps to move so fast, similarly to what was happening with 2->3. If this holds, then 3.9x might belong under gnome and 3.22.y outside, but it might be unnecessary duplication of code.
I know very little about the others, except that NetworkManager is certainly used outside gnome a lot, but that might not be any problem for this at all.

gtk+: the duplication could be avoided e.g. by having most of the expression shared and then just stubs like this in individual gnome releases.

BTW, Raskin is @7c6f434c and urkud has been inactive for years now (we might just purge him from maintainers).

Also consider xfce.

--
NixOS Linux http://nixos.org

Somewhat relevant. Gnome provides Python bindings for quite some packages. Currently these are (indirectly) available via all-packages.nix. I think the functions building those derivations should be called from python-packages.nix since that way we can guarantee the same version of the interpreter is used.

Or we could improve the maintainer script and dissolve the GNOME package set à la triton, keeping it only virtually.

We've pretty much decided to dissolve the gnome3 attribute completely so I will close this issue.
Everything at gnome3 is slowly turning into aliases, and eventually we'll have some sort of solution for the maintainer script.

authors: FRidh groxxda jtojnar lethalman vcunat worldofpeace

repo: NixOS/nixpkgs


text:
GDM 3.22: Cannot open virtual console 7 (Permission denied)

Issue description
I'm on nixos-unstable and wanted to try gnome 3.22:
gdm-x-session[2762]: (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
gdm-x-session[2762]: (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
gdm-x-session[2762]: (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
gdm-x-session[2762]: (II) VESA: driver for VESA chipsets: vesa
gdm-x-session[2762]: (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
gdm-x-session[2762]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms
gdm-x-session[2762]: (EE)
gdm-x-session[2762]: Fatal server error:
gdm-x-session[2762]: (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
gdm-x-session[2762]: (EE)
gdm-x-session[2762]: (EE)
gdm-x-session[2762]: Please consult the The X.Org Foundation support
gdm-x-session[2762]:          at http://wiki.x.org
gdm-x-session[2762]:  for help.
gdm-x-session[2762]: (EE) Please also check the log file at "/dev/null" for additional information.
gdm-x-session[2762]: (EE)
gdm-x-session[2762]: (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
gdm-x-session[2762]: (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
gdm-x-session[2762]: (EE) Server terminated with error (1). Closing log file.
gdm-x-session[2762]: Unable to run X server

same for me

I think it's still all the same problem as in the link. The default GDM mode (with wayland) needed some changes to Xserver arguments; that was implemented in a way that broke other display managers and got reverted. AFAIK noone has yet implemented a fix that would override those options for GDM only.

It's a bit unfortunate we're stuck in this in-between state.

I believe this is fixed. (Ping me if not.)

authors: DamienCassou bjornfor jgeerds vcunat