text:
[BUG] Plugin with id 'kotlin-android' not found.

Hi, I have failed Android build.
It says:
A problem occurred configuring project ':react-native-vision-camera-face-detector'.
> compileSdkVersion is not specified. Please add it to build.gradle

"react-native": "0.71.13",
"react-native-vision-camera": "^4.0.0-beta.12",
"react-native-vision-camera-face-detector": "^1.4.0",
"react-native-worklets-core": "^0.4.0",
 "react-native-reanimated": "3.6.2",

Error logs:
BUILD FAILED in 18s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installUftDebug -PreactNativeDevServerPort=8081
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

Where:
Build file '/Users/yo/www/driver-app/node_modules/react-native-vision-camera-face-detector/android/build.gradle' line: 2

What went wrong:
A problem occurred evaluating project ':react-native-vision-camera-face-detector'.

Plugin with id 'kotlin-android' not found.

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.
==============================================================================

2: Task failed with an exception.

What went wrong:
A problem occurred configuring project ':react-native-vision-camera-face-detector'.

compileSdkVersion is not specified. Please add it to build.gradle

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 18s
at makeError (/Users/yo/www/driver-app/node_modules/execa/index.js:174:9)
at /Users/yo/www/driver-app/node_modules/execa/index.js:278:16
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async runOnAllDevices (/Users/yo/www/driver-app/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:82:7)
at async Command.handleAction (/Users/yo/www/driver-app/node_modules/@react-native-community/cli/build/index.js:108:9)

info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
{
"name": "driverApp",
"version": "4.19.3",
"private": true,
"scripts": {},
"dependencies": {
"@mapbox/polyline": "^1.1.1",
"@onfido/react-native-sdk": "10.7.0",
"@react-native-async-storage/async-storage": "^1.19.3",
"@react-native-community/geolocation": "^2.0.2",
"@react-native-community/hooks": "^2.8.0",
"@react-native-community/image-editor": "^2.3.0",
"@react-native-community/netinfo": "^6.0.4",
"@react-native-community/picker": "^1.8.1",
"@react-native-community/toolbar-android": "^0.2.1",
"@react-native-firebase/analytics": "^14.7.0",
"@react-native-firebase/app": "^14.7.0",
"@react-native-firebase/crashlytics": "^14.7.0",
"@react-native-firebase/messaging": "^14.7.0",
"@react-native-firebase/perf": "^14.7.0",
"@react-native-masked-view/masked-view": "^0.2.9",
"@react-navigation/bottom-tabs": "^6.5.4",
"@react-navigation/compat": "^5.3.20",
"@react-navigation/material-top-tabs": "^6.5.3",
"@react-navigation/native": "^6.1.3",
"@react-navigation/native-stack": "^6.9.9",
"@react-navigation/stack": "^6.3.12",
"@stripe/stripe-react-native": "0.35.1",
"@types/mapbox__polyline": "^1.0.1",
"@types/point-in-polygon": "^1.0.0",
"axios": "^0.27.2",
"clevertap-react-native": "^1.1.0",
"code-push": "4.0.5",
"dayjs": "^1.11.1",
"deprecated-react-native-prop-types": "^4.1.0",
"geolib": "^3.3.1",
"humanize-duration": "^3.24.0",
"i18next": "^19.8.1",
"i18next-async-storage-backend2": "^2.0.3",
"i18next-chained-backend": "^2.0.1",
"i18next-http-backend": "^1.3.1",
"jsc-android": "^241213.1.0",
"libphonenumber-js": "^1.10.14",
"lodash": "^4.17.20",
"mobx": "^5.15.6",
"mobx-persist": "^0.4.1",
"mobx-react": "^6.3.0",
"moment": "^2.29.1",
"moment-range": "^4.0.2",
"moment-timezone": "^0.5.31",
"patch-package": "^8.0.0",
"point-in-polygon": "^1.0.1",
"prop-types": "^15.7.2",
"query-string": "^6.13.7",
"react": "18.2.0",
"react-dom": "^17.0.2",
"react-i18next": "^11.7.3",
"react-lifecycles-compat": "^3.0.4",
"react-native": "0.71.13",
"react-native-alertbox": "^0.2.11",
"react-native-base64": "0.1.0",
"react-native-bluetooth-state-manager": "^1.3.2",
"react-native-bootsplash": "^4.0.2",
"react-native-calendar-events": "^2.2.0",
"react-native-camera": "^4.2.1",
"react-native-check-box": "^2.1.7",
"react-native-circular-progress": "^1.3.6",
"react-native-config": "^1.4.2",
"react-native-country-picker-modal": "^2.0.0",
"react-native-device-info": "^10.6.0",
"react-native-document-picker": "^5.3.0",
"react-native-exception-handler": "^2.10.9",
"react-native-fast-image": "^8.6.3",
"react-native-gesture-handler": "^2.10.1",
"react-native-google-places-autocomplete": "^2.5.1",
"react-native-hyperlink": "0.0.19",
"react-native-image-pan-zoom": "^2.1.12",
"react-native-image-resizer": "^1.4.5",
"react-native-keyboard-aware-scroll-view": "^0.9.3",
"react-native-keyboard-spacer": "^0.4.1",
"react-native-lightbox": "^0.8.1",
"react-native-linear-gradient": "^2.5.6",
"react-native-localize": "^1.4.3",
"react-native-map-link": "^2.7.19",
"react-native-maps": "1.9.0",
"react-native-maps-directions": "^1.9.0",
"react-native-markdown-display": "^6.1.6",
"react-native-modal": "^13.0.1",
"react-native-network-info": "^5.2.1",
"react-native-offline": "^6.0.1",
"react-native-pager-view": "^5.4.15",
"react-native-paper": "^4.10.1",
"react-native-permissions": "^4.0.0",
"react-native-phone-call": "^1.0.9",
"react-native-progress": "^5.0.0",
"react-native-rate": "^1.2.4",
"react-native-ratings": "^8.1.0",
"react-native-reanimated": "3.6.2",
"react-native-safe-area-context": "^3.1.8",
"react-native-screens": "3.29.0",
"react-native-select-contact": "^1.5.0",
"react-native-sensitive-info": "^5.5.8",
"react-native-share": "10.0.2",
"react-native-simple-crypto": "^0.2.15",
"react-native-skeleton-placeholder": "^2.0.11",
"react-native-slider": "^0.11.0",
"react-native-snap-carousel": "^3.9.1",
"react-native-status-bar-height": "^2.5.0",
"react-native-svg": "^13.4.0",
"react-native-swipe-gestures": "^1.0.5",
"react-native-tab-view": "^3.1.1",
"react-native-toast-message": "^2.1.5",
"react-native-touch-id": "^4.4.1",
"react-native-vector-icons": "9.2.0",
"react-native-video": "^5.2.0",
"react-native-view-pdf": "^0.14.0",
"react-native-vision-camera": "^4.0.0-beta.12",
"react-native-vision-camera-face-detector": "^1.4.0",
"react-native-webview": "^11.0.2",
"react-native-worklets-core": "^0.4.0",
"rn-fetch-blob": "^0.12.0"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/plugin-proposal-decorators": "^7.10.5",
"@babel/plugin-transform-runtime": "^7.11.5",
"@babel/runtime": "^7.20.0",
"@jumpn/react-native-jetifier": "^0.1.4",
"@react-native-community/eslint-config": "^3.2.0",
"@types/enzyme": "^3.10.14",
"@types/humanize-duration": "^3.18.1",
"@types/jest": "^27.5.1",
"@types/lodash": "^4.14.161",
"@types/moment-timezone": "^0.5.30",
"@types/react": "^18.0.24",
"@types/react-lifecycles-compat": "^3.0.1",
"@types/react-native": "0.70.13",
"@types/react-native-keyboard-spacer": "^0.4.3",
"@types/react-native-permissions": "^2.0.0",
"@types/react-native-share": "^3.3.4",
"@types/react-native-tab-view": "^2.3.0",
"@types/react-native-vector-icons": "^6.4.15",
"@types/react-native-video": "^5.0.16",
"@types/react-test-renderer": "^18.0.3",
"@typescript-eslint/eslint-plugin": "5.53.0",
"@typescript-eslint/eslint-plugin-tslint": "5.53.0",
"@typescript-eslint/parser": "5.53.0",
"babel-jest": "^27.5.1",
"babel-plugin-transform-remove-console": "^6.9.4",
"chokidar-cli": "^2.1.0",
"enzyme": "^3.11.0",
"enzyme-adapter-react-16": "^1.15.5",
"eslint": "^8.19.0",
"eslint-config-standard": "^16.0.3",
"eslint-plugin-import": "^2.23.4",
"eslint-plugin-jest": "27.2.1",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-react": "^7.24.0",
"eslint-plugin-react-hooks": "^4.2.0",
"eslint-plugin-react-native": "^3.11.0",
"eslint-plugin-security": "^1.5.0",
"eslint-plugin-standard": "^5.0.0",
"husky": "^4.3.0",
"jest": "^27.5.1",
"jest-sonar": "^0.2.12",
"license-checker": "^25.0.1",
"lint-staged": "^10.4.0",
"metro-react-native-babel-preset": "^0.76.9",
"postinstall-postinstall": "^2.1.0",
"react-native-clean-project": "^3.6.7",
"react-native-svg-transformer": "^1.0.0",
"react-test-renderer": "18.2.0",
"reactotron-react-native": "5.0.3",
"ts-jest": "^27.1.3",
"tslint": "^6.1.3",
"typescript": "4.9.4",
"yarn-audit-fix": "^7.1.2"
},
"resolutions": {
"@react-native/normalize-colors": "0.73.2",
"react-native": "0.71.13"
},
"husky": {
"hooks": {
"pre-commit": "tsc && lint-staged"
}
},
"lint-staged": {
"*.{ts,tsx,js,jsx}": "eslint --max-warnings=100"
}
}

@YuriOlepir can you please check your app's build.gradle file if they have kotlinVersion and compileSdkVersion props defined?

Here is my build.gradle file, it seems that those defined

buildscript {

    ext {
        kotlinVersion = '1.8.0'
        buildToolsVersion = "33.0.0"
        minSdkVersion = 29
        compileSdkVersion = 34
        targetSdkVersion = 34
        googlePlayServicesVersion = "15+"
        androidMapsUtilsVersion = "0.5+"
        supportLibVersion = "29.0.0"
        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"
    }

    repositories {
        google()
        mavenCentral()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:7.4.2'
        classpath 'com.google.gms:google-services:4.3.14'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.8.1'
        classpath 'com.google.firebase:perf-plugin:1.4.1'
        classpath 'com.facebook.react:react-native-gradle-plugin'
    }
}

def REACT_NATIVE_VERSION = new File(['node', '--print', "JSON.parse(require('fs').readFileSync(require.resolve('react-native/package.json'), 'utf-8')).version"].execute(null, rootDir).text.trim())

...

@nonam4 I've just set up the new react-native project from the stretch with only these dependencies and got the same error.

"react-native": "0.71.13",
"react-native-vision-camera": "^4.0.0-beta.12",
"react-native-vision-camera-face-detector": "^1.4.0",
"react-native-worklets-core": "^0.4.0",
 "react-native-reanimated": "3.8.1",

@YuriOlepir can you test new build.gradle version and see if the error is gone?

@YuriOlepir can you test new build.gradle version and tell me if the error is gone?

I checked, there is nothing changed.

Can you create a public repo with a min reproducible example?
So I'll be able to debug and fix this issue.

Same bug, can u update anything new? :(

@namanh6669 does this error happens on example app?

can you guys test new 1.4.1 version? Do it fix this issue?

The issue persists in version 1.4.1

Please test new 1.4.2 version and give me a feedback about it 😁

Please test new 1.4.2 version and give me a feedback about it 😁

Hi, I migrated from v1.3.5 to the latest v1.6.3.
this issue still exists.
I did a patch fix for the node_modules/react-native-vision-camera-face-detector/android/build.gradle, please check, maybe it will be helpful
def safeExtGet(prop, fallback) {
    rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}

def kotlinVersion = safeExtGet("VisionCameraFaceDetector_kotlinVersion", "1.9.20")

buildscript {
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath "com.android.tools.build:gradle:7.4.2"
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:${kotlinVersion}"
    }
}

apply plugin: "com.android.library"
apply plugin: "kotlin-android"

android {
    buildToolsVersion = safeExtGet("VisionCameraFaceDetector_buildToolsVersion", "34.0.0")
    ndkVersion safeExtGet("VisionCameraFaceDetector_ndkVersion", "25.1.8937393")

    defaultConfig {
        minSdkVersion safeExtGet("VisionCameraFaceDetector_minSdkVersion", 26)
        compileSdkVersion safeExtGet("VisionCameraFaceDetector_compileSdkVersion", 34)
        targetSdkVersion safeExtGet("VisionCameraFaceDetector_targetSdkVersion", 34)
        versionCode 1
        versionName "1.0"
    }

    buildTypes {
        release {
            minifyEnabled false
        }
    }
    lintOptions {
        disable "GradleCompatible"
    }
}

repositories {
    mavenLocal()
    maven {
        url("$rootDir/../node_modules/react-native/android")
    }

    google()
    mavenCentral()
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:${kotlinVersion}"
    implementation "com.facebook.react:react-native:+"
    api project(":react-native-vision-camera")
    implementation "androidx.annotation:annotation:1.7.1"
    implementation "androidx.camera:camera-core:1.3.3"
    implementation "com.google.mlkit:face-detection:16.1.6"
}

@YuriOlepir thanks for your help.
Can you open a PR with this fix?


text:
Scroll Not Functional

Scrolling doesn't work, only way to scroll is to go into dev tools and right click on element and press the scroll into view button. I think the valentine's day update is when the bug appeared

I will fix it tonight

Fixed!

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Doesn't work well when indent_size = 2

vim.opt.list = true

vim.cmd [[highlight IndentBlanklineIndent2 guifg=#E5C07B gui=nocombine]]
vim.cmd [[highlight IndentBlanklineIndent3 guifg=#98C379 gui=nocombine]]
vim.cmd [[highlight IndentBlanklineIndent4 guifg=#56B6C2 gui=nocombine]]

require("indent_blankline").setup {
    char_highlight_list = {
        "IndentBlanklineIndent2",
        "IndentBlanklineIndent3",
        "IndentBlanklineIndent4",
    },
    -- indent_size = 2,

}

It works not well...

indent_size is not a valid option. What are you trying to do?

I have commented that line...
I just want try to specify indent size to 2. Because default config doesn't work well for my project (indent size is 2).

Right, I think I understand. You have to do :set shiftwidth=2
indent-blankline uses what is configured as the shiftwidth

authors: Yatogaii lukas-reineke


text:
Undesired indent lines started to show in dashboard

Hello. A couple of commits ago the dashboard displayed by dashboard.nvim worked just fine, but at some point some undesired indent lines like the ones shown below started to show up. Any idea why that might be?

Duplicate of #566


text:
Empty graphics in bigdesk plugin

Hi:
I have installed bigdesk, but there are a few graphic that i cant see, for example:
OS
CPU vendor: n/a
CPU model: n/a
CPU total logical cores: n/a
CPU cache: n/a
Process
Total: 100%
Process:
File system
Writes: n/a
Reads: n/a
Write: n/a
Also i can see the Experimental cluster Pack diagram
Any suggestion??
Many thanks and goo job

Which version of elasticsearch you have installed

I am archiving this repository now. Thanks for contributions.

authors: lukas-vlcek nishantsaini pacosoplas

repo: lukas-vlcek/bigdesk

license_source: bigquery


text:
Need sample code

Hi,
Could you please provide sample code and documentation??
I have a unsorted dictionary. how can I use your library to make it as orderdDict
It's bit tricky with init methods(Elements/Sequences). Please suggest as I am new to Swift.
Thanks in advance.

Hi, you can find sample code in the playground included in the repository. For API documentation please refer to the comments in the source files. I will eventually turn the code comments into an API documentation using Jazzy in #24.
Regarding your specific problem, there is actually not a simple way for doing it. I might add a secondary initializer which would take a dictionary and a sort function in the future (see #30). For now you have to construct the elements sequence from the dictionary on your own and apply custom sorting. Here is an example:
let dictionary = [
    1: "foo",
    2: "bar",
    3: "baz"
]

let unsortedElements = dictionary .map { key, value in
    return (key: key, value: value)
}

let sortedElements = unsortedElements.sorted { element1, element2 in
    return element1.key < element2.key
}

let orderedDictionary = OrderedDictionary<Int, String>(sortedElements)

authors: balakrishnaJarugubelli lukaskubanek

repo: lukaskubanek/OrderedDictionary

license: mit


text:
how to convert [String:[[String:AnyObject]]] to OrderedDictionary type?

how to convert [String:[[String:AnyObject]]] to OrderedDictionary type?
let orderedDictionary: OrderedDictionary<String, Any> = (self.dic as? OrderedDictionary)!
warning message
Cast from '[String : [[String : Any]]]' to unrelated type 'OrderedDictionary<String, Any>' always fails

You cannot cast a regular Dictionary to OrderedDictionary. You can use either a dictionary literal or an initializer on OrderedDictionary which takes a regular Dictionary and specify the ordering closure (see below).
let dictionary: [String:[[String:AnyObject]]] = [
    "A": [],
    "C": [],
    "B": [],
]

let orderedDictionary = OrderedDictionary(unsorted: dictionary) { element1, element2 in
    element1.key < element2.key
}

authors: lukaskubanek yoonjason


text:
Critical Crash after starting App  with crack sounding via Soundsystem

ShutdownTimerClassic@1.2.3 experienced a critical exception.
The following data includes information about your system, the exception and the internal state of the application at the time of the exception. You may remove certain information (like your username which may be included in the log) to protect your privacy.
Please open an issue on https://github.com/lukaslangrock/ShutdownTimerClassic and include the contents of this log file to help identify and fix the issue.
---- Process Info ----
PID: 1200
ProcessName: ShutdownTimerClassic
Arguments:
PriorityClass: Normal
Threads: 9
Responding: True
HasExited: False
StartTime: 19.01.2024 00:59:57
PeakWorkingSet64: 22,4MB (23470080byte)
WorkingSet64: 22,4MB (23465984byte)
PeakWorkingSet64: 22,4MB (23470080byte)
PrivateMemorySize64: 13,5MB (14204928byte)
VirtualMemorySize64: 191,6MB (200921088byte)
PeakVirtualMemorySize64: 192,6MB (201986048byte)
PagedSystemMemorySize64: 290,8KB (297776byte)
NonpagedSystemMemorySize64: 20,7KB (21240byte)
PagedMemorySize64: 13,5MB (14204928byte)
PeakPagedMemorySize64: 13,5MB (14204928byte)
UserProcessorTime: 00:00:00.0937500
TotalProcessorTime: 00:00:00.2812500
PrivilegedProcessorTime: 00:00:00.1875000
---- Application Info ----
Product Name: ShutdownTimerClassic
Product Version: 1.2.3.0
Current Culture: de-DE
Executable Path: C:\Program Files\WindowsApps\19341LukasLangrock.ShutdownTimerClassic_1.2.3.0_x64__jnfph5tq58r4j\ShutdownTimer\ShutdownTimerClassic.exe
MD5 Checksum: f755519e89e2e543ed11f113634d6e20
---- Environment Info ----
64-bit OS: True
64-bit Process: False
OS Version: Microsoft Windows NT 10.0.19045.0
Runtime Version: 4.0.30319.42000
System Uptime: 119515
Machine Name: SYDOW
Processor Count: 8
Shutdown Started: False
---- Exception ----
Type: UnhandledException
Message: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Stack Trace:
bei ShutdownTimer.Helpers.SettingsProvider.CheckSettings()
bei ShutdownTimer.Helpers.SettingsProvider.Load()
bei ShutdownTimer.Program.Main(String[] args)
---- Internal Event Log ----
[Settings] Checking settings object
[Settings] Loading settings.json
[Settings] Loading settings...
[Program] Running Menu
[Program] Attaching ExceptionHandler.cs
---- End of Log ----

I couldnt start it afterwards i always get a security Issue template following this here.

This seems to be related to https://github.com/lukaslangrock/ShutdownTimerClassic/issues/30, I'll post updates if I eventually come back to working on this project again there. Thanks for the report tho.

repo: lukaslangrock/ShutdownTimerClassic


text:
Question: Would it be possible to have sync from GitHub?

Thank you so much of this marvellous plugin,
I was wondering if you had any plans/interests into allowing sync back from github?

I have 3 themes in my DS and I find maintaining Figma files for the 3 themes is really time consuming
Having a way to sync my tokens back to a single "white label" file would really rock
Sometimes Figma can get out of control with contributors and it's hard to see the differences between live code and FIGMA, Syncing back from code could help starting on strong bases.

Anyway let me know if that something you could consider? or if you have any tips to handle such workflow
THanks

Hey @edwardbattistini,
I do have interest in a sync back to Figma. However currently I have not worked on this.
I would love to allow a sync from a w3c token file to text styles, color styles, elevation styles and grid styles. So anything that can be added as a style.
Would you be interested in contributing?

authors: edwardbattistini lukasoppermann

repo: lukasoppermann/design-tokens


text:
doesn't build?

after npm install on a fresh clone trying to npm run build fails during both swagger-gen and routes-gen with:
Error: Error generate parameter method: 'AccountsController.current' argument: someFlag Error: Parameter 'someFlag' can't macth in path: '/Current'
I tried updating the deps in package.json and that just ended up with me having a type conflict between the Account model and an Account type in node_modules someplace

Fixed in #4

repo: lukeautry/tsoa-example


text:
server Not render the expected page

Hi, it looks like server just render home page, then route to the page which user real visit to by JavaScript in browser. Expectation is the server render the page visit to by user, some help?
let url = req.url;
let body = render(h(App, { url }));

here, bodycan't get the correct page structure to which the url points, it's designed like this or Preact bug ?

Hey,
I'm not sure why, but it's actually a behavior specific to the now.sh deployment. If you run this locally, you'll see that each route's is rendered from the server:

I can chat with the ZEIT guys to try & get more insight, but the setup, as is, works correctly. I'm using it for a couple production sites 😄

Thanks for the reply, and it's really a stupid mistake that I made that I changed the id of root div, but forget to change the server side.
// here the id not changed as app.js
const RGX = /<div id="app"[^>]*>.*?(?=<script)/i;

now it works.

Oops, haha. Happens to all of us 😆

authors: lukeed owcc

repo: lukeed/preact-cli-ssr


text:
TypeError: history.listen is not a function

Uncaught TypeError: history.listen is not a function
    at Object../src/index.js (app.e72e671….js:1)
    at n (vendor.e72e671….js:1)
    at window.webpackJsonp (vendor.e72e671….js:1)
    at app.e72e671….js:1

Is this because of my setup? I used yarn instead of npm

Oh whoops! No, this is a remnant from my port of inferno-starter. Fix this in a sec

Fixed; thanks for catching!

authors: BatuhanK lukeed

repo: lukeed/preact-starter


text:
Request: no captions or file names.

Is it possible to hide the caption and/or file names? I would like to just show my photos in the card.

Just looked at code. One of the hack would be to pass ' ' (space).
caption_format: ' '
This worked for me.

repo: lukelalo/gallery-card


text:
Data deserialization crash in PTPusherEvent is fixed

It could crash if string is empty

Any luck in reviewing it?

@lukeredpath is this good to be merged?

source: gharchive/pull-request

authors: darvin hamchapman

repo: lukeredpath/libPusher


text:
potplayer@1.7.17508: hash check failed

Updating 'potplayer' (1.7.16291 -> 1.7.17508)
Uninstalling 'potplayer' (1.7.16291)
Unlinking ~\scoop\apps\potplayer\current
Installing 'potplayer' (1.7.17508) [64bit]
PotPlayerSetup64.exe (27,0 MB) [==============================================================================] 100%
Checking hash of PotPlayerSetup64.exe ... ERROR Hash check failed!
App:         Ash258/potplayer
URL:         https://t1.daumcdn.net/potplayer/PotPlayer/Version/Latest/PotPlayerSetup64.exe#/cosi.7z
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    521672085381e1ab5d2d58d56e0aee38d99ccb15cafcef0223049e2d3522d352
Actual:      2dcc9a625b27b1730c02d5398c7f20cf88e43982124516d1606cb62210f88a97
Please contact the bucket maintainer!

@Ash258 is the maintainer of this program.

Whoops. Didn't read the repository name. I also see that he has fixed it. So I'll close this.

repo: lukesampson/scoop-extras

license: Unlicense


text:
[Help/Suggestion Wanted] Attempt at updating the ghostscript bucket

Hi,
Needed ghostscript for opening .esp-files in Inkscape.  But the bucket were lacking a bit.  I tried adding a "bin" line for both 32/64 bit, and added the lib folder under envs.  As that is required by Inkscape.
{
    "homepage": "http://www.ghostscript.com",
    "version": "9.19",
    "license": "http://www.gnu.org/licenses/agpl-3.0.html",
    "architecture": {
        "64bit": {
            "url": "https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs919/gs919w64.exe#/dl.7z",
            "hash": "272fbe49981935f9393b829045756b5cfd5946d7acc88753250ab678816a57fc"
        },
        "32bit": {
            "url": "https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs919/gs919w32.exe#/dl.7z",
            "hash": "36fd0d44cd8a978254bba597881313f31ddf4ea83470c10c7858ced00620c3e1"
        }
    },
    "bin": if ( test-path( $dir\bin\gswin32.exe ) ) {
      "bin\\gswin32.exe"
    }
    else {
      "bin\\gswin64.exe"
    },
    "env_add_path": [
      "bin",
      "lib"
    ]
}

Obviusly I don't know jack s**t about JSON, but I had to try :-P  Can this be achieved somehow?  Also, maybe it's easier to use archive condition?

I've added those changes c56e687a1b11b373f068a548e94f45e1a9f093c5, following an update to allow architecture-specific bins. Can you run scoop update and let me know if it works now?

Works like a boss! 👍 You're the man..
Also, there is gsw64c.exe as the CLI tool.  You'll update, or shall I submit a PR?

Done! Feel free to submit PRs too if you notice app updates that need to be made.

Thanks :-)

authors: MindTooth lukesampson

repo: lukesampson/scoop

license: unlicense


text:
Update Makefile to include Ledger support

Closes: #XXX
Description

Adds Ledger support to Makefile

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added  relevant godoc comments.
[ ] Re-reviewed Files changed in the Github PR explorer

For admin use:

[ ] Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
[ ] Reviewers assigned
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]"

LGTM! Thank you for backporting this

authors: Segfaultd dylanschultzie

repo: lum-network/chain


text:
interpreter-in-browser doesn't build

I'm trying to build the examples. spawn-chain builds and works fine, but with interpreter-in-browser I get multiple errors of this type:
   Compiling libeir_diagnostics v0.1.0 (https://github.com/eirproject/eir.git?branch=lumen#2124ea35)
error[E0080]: erroneous constant used
  --> /Users/erszcz/.cargo/git/checkouts/eir-9a91440c84f5797a/2124ea3/libeir_diagnostics/src/index.rs:15:73
   |
15 |     pub const UNKNOWN: Self = Self(unsafe { NonZeroUsize::new_unchecked(Self::UNKNOWN_SRC_ID) });
   |                                                                         ^^^^^^^^^^^^^^^^^^^^ referenced constant has errors

error[E0080]: evaluation of constant expression failed
  --> /Users/erszcz/.cargo/git/checkouts/eir-9a91440c84f5797a/2124ea3/libeir_diagnostics/src/index.rs:49:20
   |
49 |         if self == Self::UNKNOWN {
   |                    ^^^^^^^^^^^^^ referenced constant has errors
...
error: aborting due to 8 previous errors

All but the first one are about Self::UNKNOWN.
My env:
$ rustc --version
rustc 1.45.0-nightly (769d12eec 2020-05-12)

The interpreter broke with the DynOp changes to EIR.

authors: KronicDeth erszcz

repo: lumen/lumen


text:
Abs method

This adds abs method for a LQuery value

The code itself looks good.
It'd be great if you added some tests. See https://github.com/luna/Dataframes/blob/master/native_libs/test/Tests.cpp#L381 for example how it was done with negate. The fixture deifiniton is here: https://github.com/luna/Dataframes/blob/master/native_libs/test/Tests.cpp#L279

Also, likely a separate matter, but Luna's built-in types (Int, Real) should get this method as well. The assumption is that LQuery tries to mimic the built-in types interface.

If you're doing a PR, please connect it to an issue (even if it meant creating one just for the sake of being connected to). ZenHub doesn't handle standalone PRs well ;)

authors: mwu-tow piotrMocz sylwiabr

repo: luna/Dataframes


text:
Why minus -w[yi] in x_grad[i] += alpha * o_grad[i, yi] * (df_dx - w[yi])?

Do you mind explaining this part? I am unable to get why need to -w[yi] here.

see here.

求和的下标不一样

这样做是为了方便计算第一项，也就是原始全连接的梯度

懂了谢谢

authors: luoyetx yxchng

repo: luoyetx/mx-lsoftmax


text:
feat: witness caching now operates on a bounded buffer

What's in this PR?
This removes the assumption that prove_recursively has access to the whole set of multiframes, by :

removing lifetime semantics on store references, in favor of the simpler use of Arc,
making prove_recursively operate on an Iterator of MultiFrame, opening the way for that iterator to eventually be lazy,
making prove_recursively's witness caching only run ahead of proving by at most a fixed number of frames (set to 1000),

[!NOTE]
This PR is split in commits matching the above bullet points, the Commits  view will let you inspect them separatedly.

Next Steps
Transferring the above memory-sparse semantics to prove_from_frames,evaluate_and_prove and other transitive consumers of prove_recursively. In other words, evaluation should, as much as is possible, produce an iterator of frames.

Also, I think the message direction you implemented is backwards. The main thread - the one doing the folding - should be the one requesting witnesses to be cached upfront

Right before folding starts at index i, we send that message via the mpsc API. Then, in the witness caching thread, we simply need to cache the witness of the MultiFrame at index i + 1.

This is already what's happening: as the main thread pulls item i, the witness caching thread starts preparing item (i + channel_capacity).

@arthurpaulino Insisting on this:

I wouldn't touch this until we have proper benchmarks for SuperNova folding.
What's the issue for this, describing the gap precisely?

If we have doubts regarding performance optimizations, it would be helpful to have benchmarks that justify those performance optimizations - and until we do, descriptions of what work needs to be accomplished for those benchmarks to exist.

authors: arthurpaulino huitseeker

repo: lurk-lab/lurk-rs


text:
bump

Bumping this repository as well, with the new YatimaStdLib

I'm closing it for now because the next bump worth going for is to the Lean 4 stable release

authors: BoltonBailey arthurpaulino

repo: lurk-lab/yatima


text:
Region is not loaded from AWS config

.aws/config
[profile mail-server-wdes-intranet]
region = garage
services = garage
endpoint_url = http://x.x.x.x:3900

[services garage]
s3 =
  endpoint_url = http://x.x.x.x:3900

Running: stu --profile mail-server-wdes-intranet it does not use the region but ap-northeast-1. Checked in debug log.
Maybe it is only the unexpected scope: ?
<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error>AuthorizationHeaderMalformed<Message>Authorization header malformed, unexpected scope: 20240908/ap-northeast-1/s3/aws4_request</Message><Resource>/</Resource><Region>garage</Region></Error>

That said passing --region garage makes it work

Thanks for reporting, it certainly does seem to not be loading 😕

I would expect it to be loaded by the Default Region Provider, but it doesn't seem to be loaded. At least it seems to be loaded when specified by the environment variable AWS_REGION.

Thank you for looking into it
ap-northeast-1/s3/aws4_request</Message><Resource>/</Resource><Region>garage
Shows some part of the code knows the region and another part does not, this is quite an interesting bug

The new version of stu (0.6.0) now does a better error message: No bucket found (region: us-east-1) with stu --profile mail-server-wdes-intranet

The implementation up to 0.5.2 was as follows:

If --region is set, use it.
If AWS default value (environment variable, profile, etc.) is set, use it.
If none of them can be obtained, use the default value (ap-northeast-1).

In 0.6.0, users can now set the default value of 3 individually as a configuration.
On the other hand, this issue is about the profile value not being loaded correctly in 2.

I am also seeing the issue, I would have expected the region from my aws profile to be used, but I have to specify it manually. Following.

https://github.com/lusingander/stu/releases/tag/v0.6.2

Thank you !
It works fine 🎉

Thanks for checking!

authors: evanofslack lusingander williamdes

repo: lusingander/stu


text:
NNEF support

Khronos Neural Net Exchange Format (NNEF) is an open-source model format. It would be good to visualize these models using Netron.
Tools are available for parsing the model file. Integrating the NNEF format natively with Netron would take the same process as other formats such as ONNX.
NNEF - https://www.khronos.org/nnef
NNEF Tools - https://github.com/KhronosGroup/NNEF-Tools

@kiritigowda can you implement this, submit a pull request and sign up to support the feature.

Duplicate of #1274

authors: kiritigowda lutzroeder

repo: lutzroeder/netron


text:
🛑 BrandTag Staging API is down

In 7c7782b, BrandTag Staging API (https://trasee.staging.brandtag.io) was down:

HTTP code: 404
Response time: 606 ms

Resolved: BrandTag Staging API is back up in b9bacc3.

repo: luxtagofficial/upptime


text:
Data replication from tidb to es by kafka and ticdc

What problem does this PR solve?
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation

Release notes:

NONE

Complete the merge for replication from tidb to es

repo: luyomo/OhMyTiUP


text:
Update LwkRnModule.swift

I have gotten an edge case crash report that happens when the apply update runs when there is no wollet or update available. By checking first if both wollet and update exist we can throw an error and not crash the app.

3baa12c0d60962968a772cd458b1a3a5eaf5ace7 looks  good to me

authors: BlakeKaufman lvaccaro

repo: lvaccaro/lwk-rn


text:
Throw NullPointerException at parsing

Owner is really a great library.  But it has some issues:

It really should natively support overwriting configuration properties via command line. This has already been requested and discussed in other thread. Meanwhile I managed to combine Owner with apache-commons-cli, which works. But again: Owner should support this natively. IDeally Owner should provide a CommandLineArgumentSource that can be  given in the annotation of the Config interface.
Owner should throw a "MissingPropertyDefinitionException" at parse time, when a property that is defined in the Config interface is not defined anywhere.   Currently it throws a NullPointerException at runtime when you try to read an undefined property.    If you forget to define a prop in your .property file the user should immidiately be notified.

Hi.
It is possible to overwrite properties through system properties, that can be specified at the command line
http://owner.aeonbits.org/docs/importing-properties/
Validation at creation time is more complex that can appear at first sight, since there is also hot reload. It was planned to be implemented, but I would like to make a good implementation. At the moment I'm not actively developing on this project, for health and personal reasons. By the way the library should allow to implement all validation you need though reload events.

Check if your problem can be solved by specifying a @DefaultValue

authors: Doogiemuc lviggiano

repo: lviggiano/owner


text:
AlertIOS/Alert will not let Camera render on iOS. No errors, camera just doesn't show up

Steps to reproduce

Create a Alert Dialog before/after/during rendering
Render the camera
Only alert shows, camera does not show

Expected behaviour
Camera will show up behind the dialog
Actual behaviour
only the dialog shows up
Environment

Node.js version: 7.4.0
React Native version: 0.40
React Native platform + platform version: iOS 10.0

react-native-camera
Version: release 0.6

It is normal react-native behaviour, will happen with any render if alert is blocking a render. You need to post render events to alert.

This issue is closed because of inactivity.
Furthermore RCTCamera is deprecated now, use RNCamera instead. If this issue is also related to RNCamera, please open a new one.

authors: SimonErm manishtpatel ykcai

repo: lwansbrough/react-native-camera


text:
Design Starters

Fibo
JavaScript
JavaScript

2.7+/3

Fibo uses abstraction and extends
Answers skills and shows insights
Javascript is well ldone
Creates a nice table
Designed some wireframe


text:
LXD becomes unresponsive waiting for information of QMP socket

Required information

Distribution: Ubuntu
Distribution version: 22.04.2 LTS (Jammy)
The output of "lxc info" is attached below.

Issue description
On a machine making heavy use of LXD it sometimes happens that many LXD commands become unresponsive, e.g. lxc list or lxc info <some-vm-instance>. With guidance from @tomponline I enabled pprof and apparently LXD gets stuck waiting for information from the QMP socket:
goroutine 2250137 [sync.Mutex.Lock, 18 minutes]:
sync.runtime_SemacquireMutex(0xc000f4d3e0?, 0x60?, 0x60?)
	/snap/go/current/src/runtime/sema.go:77 +0x26
sync.(*Mutex).lockSlow(0x337e4f8)
	/snap/go/current/src/sync/mutex.go:171 +0x165
sync.(*Mutex).Lock(...)
	/snap/go/current/src/sync/mutex.go:90
github.com/lxc/lxd/lxd/instance/drivers/qmp.Connect({0xc0011e2aa0, 0x48}, {0x1d998f9, 0x13}, 0xc000f4d3e0)
	/build/lxd/parts/lxd/src/lxd/instance/drivers/qmp/monitor.go:216 +0x9e
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).statusCode(0xc00176f680)
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7345 +0x14b
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).Render(0xc00176f680, {0x0, 0x0, 0xc000a29001?})
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7007 +0x3f2
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).RenderFull(0xc00176f680, {0xc000167a40?, 0x13919?, 0xc0014586b0?})
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7047 +0x4a
main.doInstancesGet.func5()
	/build/lxd/parts/lxd/src/lxd/instances_get.go:460 +0x25f
created by main.doInstancesGet
	/build/lxd/parts/lxd/src/lxd/instances_get.go:437 +0x1085

Full pprof data: https://paste.ubuntu.com/p/3FwhpRtH7H/
Killing the lxd process (kill -9 <pid of lxd>) and waiting for snapd to restart it "fixes" the issue. This without manually killing any qemu process.
Steps to reproduce
Not easy to reproduce. Happens randomly every few days on a bare metal machine running Jammy and using LXD (snap) to start/destroy several LXD containers and VMs per day.
Information to attach

[x] pprof data
[x] Any relevant kernel output (dmesg): I don't see anything LXD related, in any case: https://paste.ubuntu.com/p/zRGzXqCPbp/
[ ] Container log (lxc info NAME --show-log): the command hangs.
[ ] Container configuration (lxc config show NAME --expanded):
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log): the latest entry is several days old, nothing relevant to this bug.
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

lxd info

config:
  core.debug_address: 127.0.0.1:8444
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid
- snapshot_scheduling
- snapshot_schedule_aliases
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
- usedby_consistency
- custom_block_volumes
- clustering_failure_domains
- resources_gpu_mdev
- console_vga_type
- projects_limits_disk
- network_type_macvlan
- network_type_sriov
- container_syscall_intercept_bpf_devices
- network_type_ovn
- projects_networks
- projects_networks_restricted_uplinks
- custom_volume_backup
- backup_override_name
- storage_rsync_compression
- network_type_physical
- network_ovn_external_subnets
- network_ovn_nat
- network_ovn_external_routes_remove
- tpm_device_type
- storage_zfs_clone_copy_rebase
- gpu_mdev
- resources_pci_iommu
- resources_network_usb
- resources_disk_address
- network_physical_ovn_ingress_mode
- network_ovn_dhcp
- network_physical_routes_anycast
- projects_limits_instances
- network_state_vlan
- instance_nic_bridged_port_isolation
- instance_bulk_state_change
- network_gvrp
- instance_pool_move
- gpu_sriov
- pci_device_type
- storage_volume_state
- network_acl
- migration_stateful
- disk_state_quota
- storage_ceph_features
- projects_compression
- projects_images_remote_cache_expiry
- certificate_project
- network_ovn_acl
- projects_images_auto_update
- projects_restricted_cluster_target
- images_default_architecture
- network_ovn_acl_defaults
- gpu_mig
- project_usage
- network_bridge_acl
- warnings
- projects_restricted_backups_and_snapshots
- clustering_join_token
- clustering_description
- server_trusted_proxy
- clustering_update_cert
- storage_api_project
- server_instance_driver_operational
- server_supported_storage_drivers
- event_lifecycle_requestor_address
- resources_gpu_usb
- clustering_evacuation
- network_ovn_nat_address
- network_bgp
- network_forward
- custom_volume_refresh
- network_counters_errors_dropped
- metrics
- image_source_project
- clustering_config
- network_peer
- linux_sysctl
- network_dns
- ovn_nic_acceleration
- certificate_self_renewal
- instance_project_move
- storage_volume_project_move
- cloud_init
- network_dns_nat
- database_leader
- instance_all_projects
- clustering_groups
- ceph_rbd_du
- instance_get_full
- qemu_metrics
- gpu_mig_uuid
- event_project
- clustering_evacuation_live
- instance_allow_inconsistent_copy
- network_state_ovn
- storage_volume_api_filtering
- image_restrictions
- storage_zfs_export
- network_dns_records
- storage_zfs_reserve_space
- network_acl_log
- storage_zfs_blocksize
- metrics_cpu_seconds
- instance_snapshot_never
- certificate_token
- instance_nic_routed_neighbor_probe
- event_hub
- agent_nic_config
- projects_restricted_intercept
- metrics_authentication
- images_target_project
- cluster_migration_inconsistent_copy
- cluster_ovn_chassis
- container_syscall_intercept_sched_setscheduler
- storage_lvm_thinpool_metadata_size
- storage_volume_state_total
- instance_file_head
- instances_nic_host_name
- image_copy_profile
- container_syscall_intercept_sysinfo
- clustering_evacuation_mode
- resources_pci_vpd
- qemu_raw_conf
- storage_cephfs_fscache
- network_load_balancer
- vsock_api
- instance_ready_state
- network_bgp_holdtime
- storage_volumes_all_projects
- metrics_memory_oom_total
- storage_buckets
- storage_buckets_create_credentials
- metrics_cpu_effective_total
- projects_networks_restricted_access
- storage_buckets_local
- loki
- acme
- internal_metrics
- cluster_join_token_expiry
- remote_token_expiry
- init_preseed
- storage_volumes_created_at
- cpu_hotplug
- projects_networks_zones
- network_txqueuelen
- cluster_member_state
- instances_placement_scriptlet
- storage_pool_source_wipe
- zfs_block_mode
- instance_generation_id
- disk_io_cache
- amd_sev
- storage_pool_loop_resize
- migration_vm_live
- ovn_nic_nesting
- oidc
- network_ovn_l3only
- ovn_nic_acceleration_vdpa
- cluster_healing
- instances_state_total
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIICBjCCAYygAwIBAgIQLwn5+hm0ujz9RdvVpWphSzAKBggqhkjOPQQDAzA1MRww
    GgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRUwEwYDVQQDDAxyb290QGtlY2xl
    b24wHhcNMjIwNTAyMDgwNDE0WhcNMzIwNDI5MDgwNDE0WjA1MRwwGgYDVQQKExNs
    aW51eGNvbnRhaW5lcnMub3JnMRUwEwYDVQQDDAxyb290QGtlY2xlb24wdjAQBgcq
    hkjOPQIBBgUrgQQAIgNiAASMW37FAAD4O0BTX4M8kFVEkaPqTETSnc4TU/UKzA/y
    uQavs6X3dxwG/js+saymVdBNO/nzpodGMA0U5q3kBXJwMlEMnTwxp2DHw26N1rIh
    3a9I4GuMnhJ5ZILzAoJGU+ujYTBfMA4GA1UdDwEB/wQEAwIFoDATBgNVHSUEDDAK
    BggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMCoGA1UdEQQjMCGCB2tlY2xlb26HBH8A
    AAGHEAAAAAAAAAAAAAAAAAAAAAEwCgYIKoZIzj0EAwMDaAAwZQIxAKienzNCcyDU
    h8PV7qMoOgM8akGQNBst8LC2aLIxAGBdQLxAxcrg2I3HM4Uu2Z6zPQIwS24tnpUB
    FCBCmOmJN+Izf+mGEizMK0sE7qZ8nK/lSaBtESr4jSOe0hpCk6qjcT4A
    -----END CERTIFICATE-----
  certificate_fingerprint: 9ee5af9f4a1e60c6cfae0614ee435a6da9c6bb155f313f51ca96a5b240d9bde7
  driver: lxc | qemu
  driver_version: 5.0.2 | 8.0.0
  firewall: nftables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    idmapped_mounts: "true"
    netnsid_getifaddrs: "true"
    seccomp_listener: "true"
    seccomp_listener_continue: "true"
    shiftfs: "false"
    uevent_injection: "true"
    unpriv_fscaps: "true"
  kernel_version: 5.15.0-75-generic
  lxc_features:
    cgroup2: "true"
    core_scheduling: "true"
    devpts_fd: "true"
    idmapped_mounts_v2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_allow_deny_syntax: "true"
    seccomp_notify: "true"
    seccomp_proxy_send_notify_fd: "true"
  os_name: Ubuntu
  os_version: "22.04"
  project: default
  server: lxd
  server_clustered: false
  server_event_mode: full-mesh
  server_name: kecleon
  server_pid: 2604
  server_version: "5.14"
  storage: zfs
  storage_version: 2.1.5-1ubuntu6~22.04.1
  storage_supported_drivers:
  - name: cephfs
    version: 17.2.5
    remote: true
  - name: cephobject
    version: 17.2.5
    remote: true
  - name: dir
    version: "1"
    remote: false
  - name: lvm
    version: 2.03.11(2) (2021-01-08) / 1.02.175 (2021-01-08) / 4.45.0
    remote: false
  - name: zfs
    version: 2.1.5-1ubuntu6~22.04.1
    remote: false
  - name: btrfs
    version: 5.16.2
    remote: false
  - name: ceph
    version: 17.2.5
    remote: true

full pprof trace https://paste.ubuntu.com/p/7WPjrfW4KX/

There is a thread blocked in the digital ocean qmp package:
goroutine 734540 [IO wait]:
internal/poll.runtime_pollWait(0x7fed2479e3f0, 0x72)
	/snap/go/current/src/runtime/netpoll.go:306 +0x89
internal/poll.(*pollDesc).wait(0xc000c24c00?, 0xc000ca00b3?, 0x0)
	/snap/go/current/src/internal/poll/fd_poll_runtime.go:84 +0x32
internal/poll.(*pollDesc).waitRead(...)
	/snap/go/current/src/internal/poll/fd_poll_runtime.go:89
internal/poll.(*FD).Read(0xc000c24c00, {0xc000ca00b3, 0xf4d, 0xf4d})
	/snap/go/current/src/internal/poll/fd_unix.go:167 +0x299
net.(*netFD).Read(0xc000c24c00, {0xc000ca00b3?, 0x0?, 0x0?})
	/snap/go/current/src/net/fd_posix.go:55 +0x29
net.(*conn).Read(0xc00058e6f8, {0xc000ca00b3?, 0xc001addda8?, 0x411b31?})
	/snap/go/current/src/net/net.go:183 +0x45
bufio.(*Scanner).Scan(0xc001addf08)
	/snap/go/current/src/bufio/scan.go:214 +0x876
github.com/digitalocean/go-qemu/qmp.(*SocketMonitor).listen(0xc000cb2280, {0x20e1880?, 0xc00058e6f8?}, 0xc000c7eb40, 0xc000c7eba0)
	/build/lxd/parts/lxd/src/.go/pkg/mod/github.com/digitalocean/go-qemu@v0.0.0-20221209210016-f035778c97f7/qmp/socket.go:175 +0x10b
created by github.com/digitalocean/go-qemu/qmp.(*SocketMonitor).Connect
	/build/lxd/parts/lxd/src/.go/pkg/mod/github.com/digitalocean/go-qemu@v0.0.0-20221209210016-f035778c97f7/qmp/socket.go:151 +0x36a

OK so this could be caused by a bug in the digitalocean/go-qemu package.
So LXD calls  qmp.NewSocketMonitor() which succeeds https://github.com/lxc/lxd/blob/master/lxd/instance/drivers/qmp/monitor.go#L227
Then LXD tries a Connect() call in a different go routine and waits for a response https://github.com/lxc/lxd/blob/master/lxd/instance/drivers/qmp/monitor.go#L232-L236
If after 5s Connect() doesn't return, then LXD calls Disconnect() https://github.com/lxc/lxd/blob/master/lxd/instance/drivers/qmp/monitor.go#L244-L247
And I can see go routine blocked in Disconnect() for a long time:
goroutine 2524696 [chan receive (nil chan), 5400 minutes]:
github.com/digitalocean/go-qemu/qmp.(*SocketMonitor).Disconnect(...)
	/build/lxd/parts/lxd/src/.go/pkg/mod/github.com/digitalocean/go-qemu@v0.0.0-20221209210016-f035778c97f7/qmp/socket.go:107
github.com/lxc/lxd/lxd/instance/drivers/qmp.Connect({0xc0005b4730, 0x48}, {0x1d998f9, 0x13}, 0xc000f3f320)
	/build/lxd/parts/lxd/src/lxd/instance/drivers/qmp/monitor.go:245 +0x64e
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).statusCode(0xc000d4a600)
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7345 +0x14b
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).Render(0xc000d4a600, {0x0, 0x0, 0x1f?})
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7007 +0x3f2
github.com/lxc/lxd/lxd/instance/drivers.(*qemu).RenderFull(0xc000d4a600, {0xc001123590?, 0x137eb?, 0x20?})
	/build/lxd/parts/lxd/src/lxd/instance/drivers/driver_qemu.go:7047 +0x4a
main.doInstancesGet.func5()
	/build/lxd/parts/lxd/src/lxd/instances_get.go:460 +0x25f
created by main.doInstancesGet
	/build/lxd/parts/lxd/src/lxd/instances_get.go:437 +0x1085

Looking at the go-qemu package I can see a potential bug in the way Connect() and Disconnect() work:
We can see that Disconnect() is blocked on this line:
https://github.com/digitalocean/go-qemu/blob/master/qmp/socket.go#L107
And we can see that Connect() only populates mon.stream if it gets a valid response from the QMP socket.
https://github.com/digitalocean/go-qemu/blob/master/qmp/socket.go#L154
So calling Disconnect() before Connect() has initialised mon.stream will block forever (as reading from a nil channel blocks).
So I think we need to make a contribution upstream to ensure that mon.stream is initialised in NewSocketMonitor and closed if Connect() fails.

I also think it would be good to add a ConnectCtx() function to that package so we can pass a connect cancellation context to it.

https://github.com/digitalocean/go-qemu/pull/201

authors: paride tomponline

repo: lxc/lxd


text:
Containers not started after boot automatically

I rebooted a xenial host with /sbin/reboot. The next morning I logged in and ran the following commands. Notice how the first one indicated the container was stopped and the second one indicated it was running. These commands were in quick succession (I was using ifconfig to see if the bridge was up). I don't know if running the lxc command caused lxd to do something that started the container or what. It was weird. The container definitely started after I ran lxc list and the machine had been up for hours at that point.
dean@courage:~$ lxc list
+-------+---------+------+------+-----------+-----------+
| NAME  |  STATE  | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+-------+---------+------+------+-----------+-----------+
| lsdev | STOPPED |      |      | NO        |         0 |
+-------+---------+------+------+-----------+-----------+
| maast | STOPPED |      |      | NO        |         0 |
+-------+---------+------+------+-----------+-----------+
| maasx | STOPPED |      |      | NO        |         0 |
+-------+---------+------+------+-----------+-----------+
dean@courage:~$ ifconfig
br0       Link encap:Ethernet  HWaddr 00:24:9b:16:77:19
enp3s0    Link encap:Ethernet  HWaddr 78:2b:cb:8e:56:6b
enx0023552c5378 Link encap:Ethernet  HWaddr 00:23:55:2c:53:78
enx00249b167719 Link encap:Ethernet  HWaddr 00:24:9b:16:77:19
lo        Link encap:Local Loopback
lxcbr0    Link encap:Ethernet  HWaddr 06:59:06:34:88:5f
vethG8PSVM Link encap:Ethernet  HWaddr fe:cc:22:08:ee:87
dean@courage:~$ lxc list
+-------+---------+-----------------+------+-----------+-----------+
| NAME  |  STATE  |      IPV4       | IPV6 | EPHEMERAL | SNAPSHOTS |
+-------+---------+-----------------+------+-----------+-----------+
| lsdev | STOPPED |                 |      | NO        |         0 |
+-------+---------+-----------------+------+-----------+-----------+
| maast | STOPPED |                 |      | NO        |         0 |
+-------+---------+-----------------+------+-----------+-----------+
| maasx | RUNNING | 10.7.0.3 (eth0) |      | NO        |         0 |
+-------+---------+-----------------+------+-----------+-----------+
dean@courage:~$

Yeah, lxd is socket activated so I guess it only started for real when you issued the first command, then noticed it had containers that were supposed to be running and started them then.
That's not how things are supposed to work though, we have another unit that should have kicked in at boot time, noticed you had containers that needed to be started and spawned those then...
I'll take a look.

This is still not working with 2.0.0~rc1-0ubuntu3

That's expected, the fix is in rc2.

I confirm it is fixed for me in rc2

authors: dhenrich stgraber


text:
[feature request] Computer parsable snapshot listing.

It would be great if a container's snapshots can be listed in a computer parsable format.
This way it could be scriptable.

We'd probably do something similar to whatever we come up with for #882

authors: stgraber tomposmiko


text:
Add container to a host's vlan

Ubuntu 16.04
lxd 2.0.4
lxc 2.0.4
Hi,
I am trying to add the container to a host's VLAN and was unable to configure it properly.
The network configuration is as follows.
Physical interface: eth0
VLAN interface : eth0.172
bridge: br0 with eth0 as the physical interface.
containers running on bridge br0.
I want to run the containers on the VLAN interface.,
I tried the following,

add eth0.172 to br0 instead of eth0
create br0.172 and adding it to the config of container, (it failed)
Tried adding VLAN interface inside the container, and was able to access from container to outside world on VLAN, but not vice versa.

I want to access containers on a VLAN IP from other hosts, along with 10.x.y.z IP.

lxc config device add container-name eth0 nic nictype=macvlan parent=eth0.172 name=eth0

That should work fine so long as you don't need communication between your host and container.
If you do need that kind of communication, then you need to setup a bridge in /etc/network/interfaces of your host, making sure that eht0.172 is bridged inside it, that eth0.172 itself has no IP configuration and that both br0 and eth0.172 are up before starting the container.

Yes,
That works, however macvlan interface doesn't support migration. Isn't it ?

Right, @tych0 is working on fixing that in CRIU.

Hmm.
Thanks.

So yeah, if you need live migration to work right now, you need to setup a bridge in /etc/network/interfaces on your host, then after confirming that it's all good, just tell LXD to use it.

In fact the patchset went in last week, so if you build from source you can try it out!

Oh, but you'll need my liblxc patches too. Let me post those.

https://github.com/lxc/lxc/pull/1248

Thanks @tych0 .
I will give a try.

@stgraber
Do you mean add VLAN interface to the bridge, and specify the bridge to the container ?
Doesn't the container need to know any information about VLAN tag to process the packets ?

@upuvvad1
If you define a device in /etc/network/interfaces like:
auto br0
iface br0 inet manual
bridge-ports eth0.172
And then use "br0" as the container's bridge, the container will be bridged onto eth0.172 and so see those packets untagged.

@stgraber
Thanks..It worked.

Good to hear, closing


text:
Difficulties restoring LXD System from backup

Hi all - I've recently run into a situation wherein I need to restore a lxd system from backup.
I've got the /var/lib/lxd directory backed up, but on direct copy-and-paste restore - I cannot seem to get a container to start.  I haven't found any documentation detailing on what must be done in this situation.
Required information
I'm on ubuntu server 16.04.2.
Output of 'lxc info' - https://hastebin.com/eyemomevun.diff
Steps to reproduce

Backup stopped lxd instances
Copy over lxd instances to /var/lib/lxd in new machine
attempt to start lxd container

https://hastebin.com/norozaxoye.sql
Not entirely sure what needs to be done at this juncture - I have attempted the lxd import command but to no avail, instead receiving a "error: readlink /var/lib/lxd/containers/$containername: invalid argument" error.

Can you paste the output of "ls -lh /var/lib/lxd/containers/"?

Yep -
night@c3:~# ls -lh /var/lib/lxd/containers/
total 12K
lrwxrwxrwx 1 root root   55 Mar  6 19:58 atlassian -> /var/lib/lxd/storage-pools/default/containers/atlassian
lrwxrwxrwx 1 root root   52 Mar  6 19:58 haraka -> /var/lib/lxd/storage-pools/default/containers/haraka
-rw-r--r-- 1 root root 8.4K Mar  6 20:10 lxc-monitord.log
lrwxrwxrwx 1 root root   55 Mar  6 19:58 notifiers -> /var/lib/lxd/storage-pools/default/containers/notifiers

What about
ls -lh /var/lib/lxd/storage-pools/default/containers/

:~# ls -lh /var/lib/lxd/storage-pools/default/containers/
total 12K
drwxr-xr-x 4 231072 165536 4.0K Mar  6 19:58 atlassian
drwxr-xr-x 4 231072 165536 4.0K Mar  6 19:58 haraka
drwxr-xr-x 4 231072 165536 4.0K Mar  6 19:58 notifiers

What error are you getting when you try to start one of those containers?

https://hastebin.com/azateqekek.swift

Did you make sure your target server has the exact same /etc/subuid and /etc/subgid as the source one?

I thought I did - apologies.  Editing the values again gave me this "error"
https://hastebin.com/odoreyeqok.sql
So I guess that means success.  However, this error was not present in the previous host.  Have I missed a detail somewhere?

That typically indicates that you're running a kernel with partial apparmor support rather than an official Ubuntu kernel.

Closing the issue since the restore was succesful.

authors: NightDevel stgraber


text:
sys-kernel-config.mount fails to load in unprivileged container

Required information

Distribution: Ubuntu
Distribution version: Ubuntu 18.04 LTS
The output of "lxc info" or if that fails:

$ lxc info # via snap
config:
  images.auto_update_cached: "false"
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- candid_authentication
- candid_config
- candid_config_key
- usb_optional_vendorid
- id_map_current
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    ...
  certificate_fingerprint: ...
  driver: lxc
  driver_version: 3.0.4
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features: {}
  kernel_version: 4.15.0-72-generic
  lxc_features: {}
  project: ""
  server: lxd
  server_clustered: false
  server_name: ...
  server_pid: 1256
  server_version: 3.0.4
  storage: dir
  storage_version: "1"

Issue description
I saw https://github.com/lxc/lxc/issues/436 but it was quite old. I apologize if this is a duplicate or known issue.
On a bionic host, in a bionic unprivileged container, the container almost, but not quite, comes up clean. The only issue is:
$ sudo systemctl --failed --all
  UNIT                    LOAD   ACTIVE SUB    DESCRIPTION
● sys-kernel-config.mount loaded failed failed Kernel Configuration File System

$ sudo systemctl status sys-kernel-config.mount
● sys-kernel-config.mount - Kernel Configuration File System
   Loaded: loaded (/lib/systemd/system/sys-kernel-config.mount; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-01-07 09:40:22 CST; 24min ago
    Where: /sys/kernel/config
     What: configfs
     Docs: https://www.kernel.org/doc/Documentation/filesystems/configfs/configfs.txt
           https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
  Process: 61 ExecMount=/bin/mount configfs /sys/kernel/config -t configfs (code=exited, status=32)

Jan 07 09:40:23 test mount[61]: mount: /sys/kernel/config: permission denied.

It is my understanding that this is desirable behavior and that /sys/kernel/config is intentionally not loaded in the container and services in the container seem to run fine so I just assume not add the access.
I'm currently using sudo systemctl mask sys-kernel-config.mount which 'works', but I'm not sure it is the right approach. Are unprivileged containers expected to come up clean by default? If not, what is the recommended way of handling this?

Unprivileged containers will have some services failing. configfs failing is fine imho. Usually services that fail but are not detrimental can just be ignored. One option to not have them fail is to mask them via systemctl mask.

I don't believe it is safe to have this mounted in unprivileged containers which is why the kernel refuses the mount (even outside of apparmor rules).
I suspect the right fix for this would be a change to the systemd unit to not mount when inside a container.

Closing as not a LXD bug and not something we'd actually ever want to allow.
I'd strongly recommend opening a bug against systemd and/or sending a PR which adds a container restriction on this unit so that it doesn't show up as failed on startup.

Ran into this on Proxmox and I resolved it by adding lxc.cap.drop: sys_rawio to my config and this is the result, no more error. What may I be missing by dropping that cap in an unprivileged container?
root@erling:~# systemctl status sys-kernel-config.mount
* sys-kernel-config.mount - Kernel Configuration File System
     Loaded: loaded (/lib/systemd/system/sys-kernel-config.mount; static)
     Active: inactive (dead)
  Condition: start condition failed at Tue 2021-11-09 11:21:58 UTC; 3min 47s ago
             `- ConditionCapability=CAP_SYS_RAWIO was not met
      Where: /sys/kernel/config
       What: configfs
       Docs: https://www.kernel.org/doc/Documentation/filesystems/configfs/configfs.txt
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems

This was also an interesting read, don't know if it's relevant: https://systemd.io/CONTAINER_INTERFACE/

I don't think you're likely to miss anything by dropping sys_rawio inside of an unprivileged container as I'd expect just about every kernel codepath requiring this capability to check it against the host namespace. We in theory could add mediated raw PCI access or something down the line through syscall interception which would then make use of that capability in the container, but it's not something we've seen any need for yet.

how i can fix this, help plaese! its a nextcloud server 25.0.1 in debian 11

authors: Ikomaz aadnehovda brauner jdstrand stgraber


text:
No information about unprivileged containers with lxd and all possible images list

Since /etc/lxc is mostly empty when using lxd. I found some information about creating lxc unprivileged containers. But that should be adapted to lxd. Want to run steam easy with lxd. And that must be normal amd64 ubuntu trusty container. (most games use 64bit)
https://www.stgraber.org/2012/11/16/running-steam-in-a-lxc-container/
Maybe we can just adapt steam-lxc to execute on lxd-images import lxc steam trusty amd64 --alias steam or something like that. But that way steam-lxc needs upgrade. But better solution will be create end-user image with separated profile (direct GPU access, pulseaudio access ) for lxc/lxd configuration.
Also there are no information on linuxcontainers.org about all possible images we have now, and where and how we can share user created images.(container + profile)
Best description will be what container include and how to create it.
For example:
Ubuntu 14.04 64 bit:
lxd-images import lxc ubuntu trusty amd64 --alias ubuntu
Debian 7 Wheezy 64bit:
lxd-images import lxc debian wheezy amd64 --alias debian
Ubuntu 12.04 32 bit:
lxd-images import lxc ubuntu precise i368 --alias ubuntu
Ubuntu 14.04 64 bit steam image:
lxd-images import lxc steam amd64 --alias steam
etc...
Maybe wiki will be best solution for that, where users can add information about new container images and links for them, with install instructions  in case when image can't be used or hosted on original linuxcontainers.org. Most people use same software, so repository with prepared container images can save bunch of time.

Just a quick note: all containers are always unprivileged when using LXD.
You can check that easily by ps'ing on the host on a running container (the container's process is mapped to user 100000 here).

As for images, the best is to have the image server behave as a LXD server, as is the case for images.linuxcontainers.org (lxd-images doesn't have to be used for it).
Then just do:
lxc remote add images images.linuxcontainers.org

And after that you can simply do:
lxc image list images:

To list all images and:
lxc launch images:ubuntu/trusty/amd64 blah

To start a container from one of those images (caching it in the process).

lxc remote add images images.linuxcontainers.org
lxc image list images:

Thats even better then what I want. Cool. How I can setup my own image server?

Just a quick note: all containers are always unprivileged when using LXD.

I know about process rights on main machine, checked that. But how to get user shell from container and run applications with user only? (without droping rights in container itself and using ssh)
For example, with that commands I get root shell and htop running with root rights.
lxc exec conname -- /bin/bash
lxc exec conname -- htop
And sorry for another stupid question how I can get container autostart with lxd or lxc, when using lxd. As I already said, we haven't many things in /etc/lxc.
Currently I'm using
/usr/bin/lxc start conname >/dev/null 2>&1 in /etc/rc.local

For image servers, you can run a public LXD with public images, that should work.
The implementation on images.linuxcontainers.org however is done by manually writing json files and with a few rewrite rules so that a static http server can act as a lxd image server.
User namespaces make it so that uid 0 (root) inside the container isn't actually real root outside of it.
So when you do "lxc exec", you see that you are root and most everything will think that you are, but you're not, from the host point of view, you're uid 165536 or some such.
As for auto-start, there's no such thing in LXD. But recent versions have a "last-state" mode which you can trigger by sending SIGPWR to the lxd daemon. It will then perform a clean shutdown of all containers and exit. Upon restart it will then restore all those containers to the state they were before LXD was shut down.

authors: chrisglass cryptofuture stgraber


text:
dns entry for lxd host

Required information

Distribution: Lubuntu
Distribution version: 20.04

Issue description
That's not a bug, that's a feature request.
When running multiple lxd guest machines, they can find each other on dns in the lxd. domain with their names.
But I didn't find a trivial way (other than routing tables or replacing the own ip with .1) to query the IP of the host machine, e.g. when using lxd to run a test client for a server. I didn't find a hint in the man pages or help texts about how to manually configure additional dns entries.
Would be nice if the host with its lxd network address appeared in DNS with both a canonical and its regular hostname (or some configurable one)
regards

At least for containers using systemd with resolved, you can use _gateway to resolve to whatever the gateway is.

You can also use the raw.dnsmasq setting on your managed network to add a custom DNS entry returned by dnsmasq.
Option 1:
Use the interface-name dnsmasq option to create DNS records for the IP addresses on the interface of your managed bridge, e.g:
lxc network set lxdbr0 raw.dnsmasq='interface-name=gateway.lxd,lxdbr0'

Then inside the instance:
dig any gateway.lxd

; <<>> DiG 9.16.1-Ubuntu <<>> any gateway.lxd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13060
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;gateway.lxd.			IN	ANY

;; ANSWER SECTION:
gateway.lxd.		0	IN	A	10.98.30.1
gateway.lxd.		0	IN	AAAA	fd42:f402:8623:5b6b::1

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Jul 05 08:21:28 UTC 2021
;; MSG SIZE  rcvd: 84

Or you can add manual DNS records using:
lxc network set lxdbr0 raw.dnsmasq='address=/gateway.lxd/10.98.30.1'

Then inside the instance:
dig any gateway.lxd

; <<>> DiG 9.16.1-Ubuntu <<>> any gateway.lxd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17215
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;gateway.lxd.			IN	ANY

;; ANSWER SECTION:
gateway.lxd.		0	IN	A	10.98.30.1

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Jul 05 08:22:58 UTC 2021
;; MSG SIZE  rcvd: 56

@stgraber perhaps we could add an option in LXD to use the interface-name option without using raw.dnsmasq?
@hadmut then for resolving .lxd domains from the host, see this guide: https://linuxcontainers.org/lxd/docs/master/networks#integration-with-systemd-resolved

There is, btw., a problem with the _gateway hostname offered by systemd-resolved as mentioned above. Since this is not an RFC2396 compliant hostname, it cannot be used as part of a URI. E.g. the ruby runtime does not accept it as a hostname.

I suspect that was somewhat intentional to avoid clashing with normal legitimate entries and is also why we used it for LXD as you can't call a container _gateway

authors: hadmut stgraber tomponline


text:
GUI: Manually specify targets?

Is it possible to manually specify IP to connect to?
I cannot use Search since devices are on another broadcast domain.
Cannot find anything in docs or UI, but it wouldn't be the first time some GUI is messed up in my WM (sway), so I might be missing something that should be obvious..
Thanks!

Sorry. Right now it does not support adding devices manually. However, it will be added in the future but only after v2.0 has been released.

Support for manually adding instruments is now supported. Added in f243363fafd273d966d1ef22a373352432584717 and will be part of the next release.

authors: lundmar stromnet

repo: lxi-tools/lxi-tools


text:
一道有趣的行列式习题的探究 | Olórin's Blog

https://lixiuyu.cc/2018/05/01/interesting-determinant-question/
上周五在世史课上做柯斯特利金的代数学引论第一章的习题时，发现了一道有趣的问题： 证明在三阶行列式展开式中的六项不可能同时为正。 当时我的第一反应是通过分类讨论来证明六项为正的情况不存在，然而暴力枚举三阶行列式9个元素的所有正负性的情况一共有$2^9 = 512$种组合，不可能通过手算得出。于是我便开始认真思考这个问题，并最后探究出了以下几个有趣的方法和结论。

Test gitalk


text:
Minor coding enhancement

as suggested here: https://github.com/lycheeverse/lychee/pull/570#discussion_r835931903

The Docker workflow of course is expected to fail on forks, unless they have DockerHub login credentials stored as secrets as well. Probably all DockerHub related steps, or the whole workflow, should be skipped on pull requests from forks? E.g.
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.owner.login == github.event.pull_request.base.repo.owner.login

Thanks @MichaIng. 😃

The Docker workflow of course is expected to fail on forks, unless they have DockerHub login credentials stored as secrets as well. Probably all DockerHub related steps, or the whole workflow, should be skipped on pull requests from forks? E.g.
if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.owner.login == github.event.pull_request.base.repo.owner.login

@MichaIng, sounds reasonable. Could you create a PR for that? Then we can test if it works right away. 😄

authors: MichaIng mre

repo: lycheeverse/lychee


text:
Model concern breaks devise reconfirmable

Because the model concern sets email_changed? to always be false, Devise's reconfirmable portion of :confirmable will never trigger.  I found this issue saying that it was necessary to override the redirect_url.  Does that mean that breaking reconfirmable is an unfortunate but necessary side effect?

I need that reconfirmable to work, I dont need that redirect_url in confirmations controller. How could I fix it ?

something new ? What redirect_url is involved in this problem ? Could somebody present what is colliding with each other ?

Just ran into this issue myself. Would be nice there's a way to play nice with reconfirmable.

Same issue here.

ditto

Same issue here ! Any fix planned ? :slightly_smiling_face:

I just overrode email_changed? this way in User model to revert it to the original behavior:
class User < ActiveRecord::Base
  devise :database_authenticatable, :registerable, :confirmable,
         :recoverable, :rememberable, :trackable, :validatable

  include DeviseTokenAuth::Concerns::User

  #...

  def email_changed?
    super
  end

  #...

end

and everything seems to work just fine for me (using Rails in api mode + separate React app).
In #229 @lynndylanhurley is concerned about redirect url, but I couldn't find any side effect at least for my case from the above change - confirmation email is being sent fine, it contains correct url in the confirmation link, after following the link a new email is being confirmed and I'm being redirected to correct sign-in url in the front-end app and can successfully sign in using the new email.
May be @lynndylanhurley could better explain what is wrong with this ?

May be having some configurable option for a redirect url would solve the issue with changing redirect url ? Since for me overriding email_changed? in User from false to super and having a custom redirect in ConfirmationsController#show works just fine. Then you could define that overriding method only in case redirect url is not specified in config. Just an idea...

https://github.com/lynndylanhurley/devise_token_auth/issues/1013

authors: Animeye LaurentKretz Marinlemaignan RonGans bobmshannon ryankc33 trushkevich truthSeekr

license: WTFPL


text:
1131 fix deprecation warning for dirty attributes for rails > 5

Resolves #1131

    if Rails::VERSION::MAJOR <= 5
      encrypted_password_changed? &&
      DeviseTokenAuth.remove_tokens_after_password_reset
    else
      saved_change_to_encrypted_password? &&
      DeviseTokenAuth.remove_tokens_after_password_reset
    end

It looks like in the else block is dead code because of expression Rails::VERSION::MAJOR <= 5 always return true for supported version 4 and 5? Else block is executed when major rails version is 6 or higher.
@Marinlemaignan in the header of the issue you used strict comparison > 5. Did you test it against rails 6?
@MaicolBen what do you think?

Yeah, I would change it to Devise.activerecord51? like the code linked by me, good discovery!

Method saved_change_to_attribute? was introduced in ActiveRecord since 5.1 version.
Version checking should be put outside of the should_remove_tokens_after_password_reset? method. Like the code you linked above.
Mongoid doesn't support saved_change_to_attribute? method. I think be better define the should_remove_tokens_after_password_reset? method into mongoid_support and active_record_support concerns. In active_record_support concern you may useActiveRecord constant for version checking (didn't check) or Devise constant.

authors: MaicolBen Marinlemaignan dks17


text:
Set up plugin not working

Am I going crazy?
I recently had to reset my Bosch thermostat and I can not set it back up again.
Where is the ACCESS_KEY now shown in the app. I've looked everywhere.

It printed on the back of the ct200

authors: TheSwiftster olly-j


text:
Typographical Errors

Minor in the grand scheme of things, but also really easy to fix ;)
When viewing the personal Inventory > Weapons the text shows:
Sorted by Type (Strenght)
When it should show:
Sorted by Type (Strength)
I'll add to this ticket if I find more examples.

Corrected ! Thanks a lot for reporting !

authors: leewiscovitch lyrgard

repo: lyrgard/ffbeEquip

license: ISC


text:
Readme - directions

The readme has no getting started directions, the readme is like a map to get going on your project - think about all the times you wished a repo had a good readme to understand what is happening.

@lyricnrhyme @JEFrady Since the three of use are touching most of the front end we need to develop a readme for anyone who comes to our repo so they can better understand what our app is about

@hkotak Ok, do you know what happened to the readme branch? It'll probably be a good starting point to start editing from

authors: JEFrady ba5eem hkotak

repo: lyricnrhyme/eeden


text:
🛑 TMS Get Tenants is down

In 1ba8117, TMS Get Tenants (https://tms.dev.cmxapp.cloud/tenants/$AMS_TENANT_ID) was down:

HTTP code: 401
Response time: 308 ms

Resolved: TMS Get Tenants is back up in 262993d after 32 minutes.


text:
请教rtdetr_r50vd.yml文件中的一些参数设置。

作者你好，我看到rtdetr_r50vd.yml文件中有两个300的参数，分别是RTDETRTransformer: num_queries: 300和 DETRPostProcess: num_top_queries: 300。
我想请问这两个300分别表示什么，原论文中写到在IoU aware query selection中选取了Top K 个分数，文中K=300，请问论文中的K=300是代码中的哪个参数，num_queries还是num_top_queries?以及最后预测头会预测出多少个预测框和GT进行匹配？
期待你的答复

好的，意思就是selection中选出了分数最高的300个，对应代码中的num_queries.然后最终也是300个预测框和GT去做匹配。那根据数据集类别数的不同，num_queries和num_top_queries是不是可以修正，而且可以递减（比如query 200个，后处理的时候是100个）？

iouri topk 对应的是 query的数量 也就是num_queries
num_top_queries是在后处理里 意思是在1中的num_queries中再去选择k个作为最终的结果 （只不过在rtdetr里这两个数设置的一样）

是的 都可以改的  可以在自己的数据集上做做实验对比一下

好的，感谢回复，我没有问题了

authors: TaroPlay lyuwenyu

repo: lyuwenyu/RT-DETR


text:
无法通过歌单添加

没办法用歌单添加歌曲吗？

歌单添加暂时没做还，有空会加上


text:
Rename bqutil -> bqext

Followup to rename bqutil to bqext, and TableUtil to Table, to improve readability.

This change is

Coverage remained the same at 81.111% when pulling f0cc8f6cb7be2195c23028ef8a899ff757c17a4e on filenames into b8982a538db4b1b71b81c8b2d19ac542a84d2a3c on master.

Reviewed 9 of 9 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: coveralls gfr10598 stephen-soltesz

repo: m-lab/go


text:
Create configs for injecting fake data and errors

This change refines the work started in https://github.com/m-lab/go/pull/75 by defining user-specified fake configuration to control errors, iteration rows and iteration errors. New functionality is the ability to provoke iteration .Next() errors.

This change is

Pull Request Test Coverage Report for Build 613

12 of 12 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 83.538%

Totals

Change from base Build 611:
0.03%

Covered Lines:
883

Relevant Lines:
1057

💛  - Coveralls

authors: coveralls stephen-soltesz


text:
Dependency on Sinon 11 causes type errors when compiling TypeScript?

Checklist

[x] I have read Caveats documentation and didn't find a solution for this problem there.

Bug description
aws-sdk-client-mock has a dependency on ^sinon@11.1.1. This is an older version of Sinon that included its own types, which have since been removed in subsequent versions and replaced with the @types/sinon package, but it seems that built-in types take precedence over @types/.
This appears to be causing the problem mentioned in this discussion over at the DefinitelyTyped repo, when you try to build a project with that version of Sinon anywhere in your dependency tree, you get this:
$ ./node_modules/.bin/tsc
node_modules/@types/sinon/index.d.ts:1447:53 - error TS2694: Namespace '"/Users/nmason/Source/sinon-aws-client-mock/node_modules/@sinonjs/fake-timers/types/fake-timers-src"' has no exported member 'FakeTimerInstallOpts'.

1447         useFakeTimers: boolean | Partial<FakeTimers.FakeTimerInstallOpts>;
                                                         ~~~~~~~~~~~~~~~~~~~~

node_modules/@types/sinon/index.d.ts:1569:67 - error TS2694: Namespace '"/Users/nmason/Source/sinon-aws-client-mock/node_modules/@sinonjs/fake-timers/types/fake-timers-src"' has no exported member 'FakeTimerInstallOpts'.

1569         useFakeTimers(config?: number | Date | Partial<FakeTimers.FakeTimerInstallOpts>): SinonFakeTimers;
                                                                       ~~~~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: node_modules/@types/sinon/index.d.ts:1447

Reproduction
Check out the very minimal repository, install dependencies, run npm run build.
Uninstall aws-sdk-client-mock and tsc happily builds the project without errors.
Environment

Node version: 16.18.1
Typescript version: 4.8.4
AWS SDK v3 Client mock version: 2.0.0

Hey,
an immediate solution is to put compilerOptions.skipLibCheck to true in tsconfig.json.
The sinon v11 does not have TS types included, they are added as a separate dependency (@types/sinon). But since the mock instance is basically a Sinon stub, I had to put the types as a "regular" dependency, not a dev one, or TS would complain on lack of types.
Since the issue with the FakeTimers was introduced in @types/sinon v10.0.13, and it's the latest version, an alternative is to use the previous version (v10.0.12). If you add it by yourself to the package.json it will force using this version and will solve the problem as well.
I'm a bit reluctant to change the required @types/sinon version in the library. Right now it's ^10.0.10. If I hardcode it to exactly 10.0.12, I guess there will be people using sinon or other libs depending on it for whom it will cause version conflicts.

Hey, I was wrong about bumping the Sinon version - it actually bumped the@sinonjs/fake-timers and solved the issue 🙂
Thanks to the @samchungy for double-checking it and making a PR.
The fix is released in v2.0.1.

authors: m-radzikowski nickmason

repo: m-radzikowski/aws-sdk-client-mock


text:
CYC-38 CYC-39 CYC-45 Add Authentication scaffolding

Description
closes #36
closes #33
This installs Laravel/Breeze, which subsequently adds AlpineJS and Tailwind. Additionally creates an Auth Namespace with controllers, view presenters, and tests.
note: i realize this adds another JS framework that we dont intent to use in the long run, but we can refactor the Authentication views to be ReactJS components later
How to use
This adds a number of routes that are immediately visit-able upon running yarn install && yarn dev

Run php artisan migrate to create your required database tables

if you get an error its likely that you are missing the MySQL php module, run sudo apt install php7.4-mysql
Another possibility is that you haven't created your database, get a mysql client like Datagrip, connect to the DB and create the schema manually if it doesn't exist

Visit /register and create an account
If you aren't logged in automatically visit /login and sign in with your created account
Observe the dashboard you are brought to
Alternatively: run php artisan test to ensure that all tests are passing

@m-triassi please do yarn add jest, it should fix the conflict

authors: m-triassi willyyhuang


text:
Yggdrasil-VR sudden crashes

what the title says. every 5-20 min of gameplay I'm having crushes and I don't know what to do about it.
can someone help, please?

Follow the template.

repo: m-vlad/Yggdrasil-VR


text:
Flush and bootstrap index blocks using series metadata in the data files

[x] storage/index.go tests

LGTM


text:
🛑 DNS is down

In 442e019, DNS (dns.m4d3bug.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS is back up in 740281f after 14 minutes.


text:
Start mining after calibration + don't exit on unstable hashrates

Currently, if hashrates doesn't stabilize after x minutes, minotaur exits calibration mode.
Some algorithms(miners?) has very unstable hashrates, making it hard to do a complete calibration for all algos/miners, without checking the rig all the time, if it might have stopped.
Would be nice if it would just skip the algo/miner and proceed to the next.
An option to start mining after completing calibration would also be nice!

ive just pushed a change to master so it no longer exits when it doesn't get a stable hashrate, so if you've asked it to calibrate more than one algo it will continue.
to mine after calibration, you can first start mining as normal across all of your devices, then run calibration with --force.  minotaur will ignore the devices until they've finished calibrating and then start mining with them when they're done.


text:
function encodePath problem

I think there is something wrong with function encodePath in AbstractApi.php line 122
As Gitlab documentation says "make sure that the NAMESPACE/PROJECT_NAME is URL-encoded, eg. /api/v3/projects/diaspora%2Fdiaspora (where / is represented by %2F)."
line: rawurlencode($path); encodes path as documentation describes and
line: return str_replace(array('%2F', '.'), array('/', '%2E'), $path)
changes it back
result is 404 error
[07/May/2015:20:29:31 +0200] "GET /api/v3/projects/dd/dd?private_token=
I use earlier version of php-gitlab-api in one of my projects and it works fine

Ah crap, I'll sort a fix for this tomorrow. It seems that the reason for the code in the encodePath() method only applies to the branch endpoints.

Hi @m4tthumphrey
Have you found some time to fix this?

Agh I'd completely forgotten to be honest. I'll do it now!

Should be good now!

Thank you :)