AS   V. 1 6 4 0  installs on every start of windows

win 8.1 64bit
Switcher works fine but asks for (and seems to need) installation every time windows starts.
Any ideas why?
Rocky

The exe doesn't actually install anything. It's considered a "portable".
Can you screenshot the message you are getting?

I get this, every time I start my computer, switcher will not work unless I
go through the install, it will however remember the Hot keys I set for
this previously
[image: Inline images 1]
Pete
On 16 March 2015 at 20:27, Sean Chapman<EMAIL_ADDRESS>wrote:

The exe doesn't actually install anything. It's considered a "portable".
Can you screenshot the message you are getting?
—
Reply to this email directly or view it on GitHub
https://github.com/xenolightning/AudioSwitcher_v1/issues/654#issuecomment-81920165
.

Can you post the image on GitHub, the emails don't attach images properly.
Cheers.

Thanks.
That message appears as a security warning, as is built into Windows.
I notice you are running it out of a temp folder. Try extracting AudioSwitcher.exe into another folder. Program Files/Documents/Desktop, and running it from there.


Set regions to fade-in/fade-out rather than instantly change.

With plugin commands, user will be able to set listed regions to fade-in/fade-out when they are added or removed from the dark list. The fade option can be unset for listed regions or for all regions.
Added plugin commands
DarkenRegion fadeToOpacity [frames] [opacity] [region list]

Pushed feature to v0.03 development branch.


specify connection URI through Code

Is there a way to specify the URI through code rather than via environment variable?
I know I can specify it when creating a DB such as db = Database(DATABASE_URL) but the StructuredNode still seems to be use the default localhost:7474

This is now fixed in master


I2 seir phe model

Closes #2

Codecov Report

Merging #14 (d503869) into main (66465d8) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main       #14    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files            3         4     +1
  Lines          257       414   +157
==========================================
+ Hits           257       414   +157

Impacted Files
Coverage Δ

epimodels/__init__.py
100.00% <ø> (ø)

epimodels/_setup_matrices.py
100.00% <100.00%> (ø)

epimodels/phe_model.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Non collapsible sub menu

Hi
In the Sidebar left menu, is it possible to have a label with children without the accordion/collapse?
If so, how?

Hi,
There is no way at this time to disable sub menu collapse feature.
I'll add this feature when I'll have time.

Hi,
In the code below, how do I add active?

Hi,
Can can do this now with @0.4.0.
Add disableCollapse in adminLteConf:

...
{label: 'Layout', iconClasses: 'fa fa-th-list', disableCollapse: true, children: [
   ...
]


Cross build to windows-x64 fails on Linux

Trying to build on Linux, I get the following
/usr/local/go/pkg/tool/linux_amd64/link: running x86_64-w64-mingw32-gcc failed: exit status 1 /usr/bin/x86_64-w64-mingw32-ld: i386 architecture of input file/tmp/go-link-892782650/000000.o' is incompatible with i386:x86-64 output
collect2: error: ld returned 1 exit status
build command is
GOOS=windows GOARCH=amd64 CGO_ENABLED=1 CC=x86_64-w64-mingw32-gcc CXX=x86_64-w64-mingw32-g++ go build -ldflags "-H windowsgui"
`
only fails to build amd64 version, I386 builds fine.
go version go1.15 linux/amd64
x86_64-w64-mingw32-gcc (GCC) 10-win32 20200525

Updating title

Haha, getting used to close my own issues here,
this was caused by stale syso file in my working directory.


Put collectstatic dry run output somewhere nicer than /dev/null

Sort of a feature request, I suppose, to improve UX/DX.
Having somewhere to look for build errors, such as something found during the collectstatic dry-run, would be really peachy.  I would've been able to figure out some deploy issues I was having much quicker if I had a build error logfile to reference.

Good idea, but this feature needs to be integrated in the upstream repo, did you opened an issue on the upstream repo too ?

Sorry, I guess I was not clear.  I'm not talking about a general feature request,  I'm speaking directly about what I see as a problem with this build pack and how it handles output during build steps; explicitly the collectstatic behavior.
Instead of redirecting "collectstatic --dryrun" into /dev/null you should consider redirecting it into a log file; or any other similar steps explicitly done in this build-pack.

You were perfectly clear :) don't worry about that.
I was saying that I'm using the exact same collect-static step as the original heroku python buildpack.
That's why I was suggesting that your comment is more pertinent for the heroku python buildpack.

Indeed, I think you're right!  I had assumed steps that seemed Django-specific were being handled by this fork, not the python buildpack.


Update stream-analytics-power-bi-dashboard.md

Updated query

Hi @jeffstokes72, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (jeffstok). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Add extra volume support so that private CA certificates can be added (rather than ignoring certs)

Scenarios like this can be supported:
environment:
  ENABLE_DELETE_IMAGES: "true"
  DOCKER_REGISTRY_URL: "https://..."
  BASIC_AUTH_USER: "..."
  BASIC_AUTH_PASSWORD: "..."
  CA_FILE: "/secrets/ca.crt"

extraVolumeMounts:
  - name: ca-certificate
    mountPath: /secrets
    readOnly: true

extraVolumes:
  - name: ca-certificate
    secret:
      secretName: "root-secret"
      items:
        - key: "ca.crt"
          path: "ca.crt"
          mode: 0644
      optional: false

Merged in 2822830.
New version was published:
https://github.com/klausmeyer/helm-charts/releases/tag/docker-registry-browser-0.1.2


Mixed languages style

Is it possible to add mixed languages style?
(for example - mixing ruby, http, html)

Ok that's Ruby. But how would we have any idea what's inside the strings?

If HTML-merging is not deprecated, I would think a solution like nesting the code container tags:
{
    "title": "<?= $title; >"
}

I don't think auto-merged ever handled cases like that... if I understand you properly you'd need to highlight individual spans "from the inside out" with highlightElement or something for that to work.

You could probably (carefully) build something like that on top of auto-merging, but it'd likely require some looping, recursion, etc...

Yes. I mean to use the auto-merging plugin as dependency.

"Explicit is better than implicit."
( https://www.python.org/dev/peps/pep-0020/ ;-) )
In my point of view - the better way to allow in highlight.js multiple tags use,
for example
print("Hello from my_some_laguage1 !")
( princ "Hello from my_some_laguage2 !")

Actually this is quite complex and I can't think of a trivial way to do it.  You can't just do it "inside out" because later highlighting phases would rehilighting the inner sections with the wrong language... there is no way to say "already highlighted".  With a custom grammar you can do this slightly with sublanguage (since now the parser itself is aware of what's going on)... say if you wanted a ruby_where_strings_are_html grammar... but doing this generically would almost require a custom parser or very ingenious glue around what already exists.

Let me try in "vanilla"
```var s = document.getElementByClassName('thing');
And simply apply a new cascade style.

print("Hello from my_some_laguage1 !")
( princ "Hello from my_some_laguage2 !")

That's two different blocks, that's easy... and works already... what the original request was talking about is one language randomly nested inside of another, which is a much harder problem.

How are we are handle this (from me - old computer science teacher)?
I'll try to make some algorithm (we can do it by our self - no need ML)
I look at code at issue start:
res = - res is is equal to
hmm - it must be a some pointer or some variable (in ruby - it is)
The quotation mark " opens
It must be a start string (it is)
What is inside the string?
Content-type:
hmm - it must be a start of http response (it is)
what value of Content-type?
text/html
2 end of row in the end
The  quotation mark " is closing  - end of string
end of part of http response
res = res +
hmm - it must be appending to string
to http response (it is)
The quotation mark " opens
It must be a start string
'< - it must be a start of *(x)ml tag (it is) 'DOCTYPE - hmm - it  must be a tag "DOCTYPE" (it is)
This is a html (it si)
html - tag has an attribute "html"
> end of tag "DOCTYPE"
 - opened tag html

Hello from ruby!

" - end of string, end of html
empty string - end of some logic
puts res - calling method "puts" with argument "res"
Voila
I must to apologize - I'm a little tired
As teach to me my teachers (students of grate Lev Landau):
I have not prepared myself, so I will speak for a long time

I didn't follow most of that (or try to) - probably due to formatting issues.
As I said the problem is not doing this specifically - it's doing it in a general way that works with out existing framework and is flexible - without having to write custom logic.  And I don't think that's easily doable (outside of writing a grammar, which I've already mentioned).
My very first question is still highly relevant I feel:

Ok that's Ruby. But how would we have any idea what's inside the strings?

I do not know
maybe we always try to parse string content as code?

Except most strings are just strings, not code.

Ce la vie
If we can not parse this - just do not parse this

You say that as if it's easy to determine whether a string is taxed or something else. That's actually a really hard problem. Just because a string might have an HTML tag in it does not mean that it's HTML, etc.

I do not agree with you.
For us - for a person
this is a really very simple problem
Just try to handle this
how do you explain it to yourself
Try to use all known code languages

For us - for a humans...this is a really very simple problem

So many things are... 😭🤷🏻♂

Try to use all known code languages

Problem: False positives.
Also, it might not be any language - even if it looks like it is.  I think code within strings in code is likely the edge case (out of all strings in the entire world).  So the majority of the time you'd just get false positives.  Perhaps your use case is different.
Not to mention it's not even trivial to know where the string ends once you start embedding other code:
var a = "test # "thingy""

Is this plain text?
Is it ruby with a comment of "thingy"..
how do we know if the " that starts thingy the end of the string or just content inside of a comment.

...if you escape the string properly (for JS) you have a whole other host of problems:

var a = "x = \"thingy\""

Now it's valid Javascript and the string would be x = "thingy" (as seen by JS) - but our parser can't easily know that - if does not decode JS encoded strings in source  The content [as seen by the parser] (inside the quotes) is x = \"thingy\"... which isn't valid Ruby at all.  You'd have to first decode any escape sequences as JS before you could even being to understand what's inside the string.
And now you're entirely outside the scope of what Highlight.js does.

If anything here has been helpful for you great.... if you've solved this problem and have some actual code to show us your solution, great... I'd certainly love to see a simple solution to what I know as very complex problem.  But I think you're just imagining the very simple cases...
I'll point you to where we do something like this:

https://github.com/highlightjs/highlight.js/blob/main/src/languages/javascript.js#L103-L128

It works in this case because the strings are tagged... but even that could have subtle issues around escaping if it were mixed right in the middle of highlighted tokens in the sublanguage... such as having a char.escape right in the middle of a variable name...  very strange, but entirely possible.

I'l leave this open a bit longer incase you want to share an actual implementation (if you've actually solved this in some sort of elegant and general way). Otherwise tagging as "autoclose" since this has been answered to the best of our ability.

We shouldn't try not to try. We must stop this in time. We couldn't say. There is no recursion here. And different types of quotes, brackets, less signs, opening tags will tell us where what begins


feat(share/availability): Store success results for light availability

Change contains:

Store coordinates of successful sampling calls
fix some minor bugs

ctx.Error returning too early without storing any result
Put error was not propagated

simplification refactoring of Samples selection code

remove squareSampler
remove binary encode/decode in favour of json

removal of no longer relevant TODOs
rename "cache" naming artefacts from the past
use height in logs instead of root hash

TODO: extract fixes/refactoring into separate PRs
Based on https://github.com/celestiaorg/celestia-node/pull/3883

Codecov Report
Attention: Patch coverage is 72.54902% with 28 lines in your changes missing coverage. Please review.

Project coverage is 44.95%. Comparing base (2469e7a) to head (fc26162).
Report is 362 commits behind head on main.

Files with missing lines
Patch %
Lines

share/availability/light/availability.go
71.62%
16 Missing and 5 partials :warning:

share/availability/light/sample.go
75.00%
5 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3887      +/-   ##
==========================================
+ Coverage   44.83%   44.95%   +0.11%
==========================================
  Files         265      311      +46
  Lines       14620    21890    +7270
==========================================
+ Hits         6555     9840    +3285
- Misses       7313    10977    +3664
- Partials      752     1073     +321

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Why do we store successful sampling results? I know we wanted to do this, but I think we should wait to do it. My concern is mainly about not doing this together with the reconstruction and the new light node storage that would keep the bitmap-like state. If think you we need to do it earlier, then please explain.

Why do we store successful sampling results? I know we wanted to do this, but I think we should wait to do it. My concern is mainly about not doing this together with the reconstruction and the new light node storage that would keep the bitmap-like state. If think you we need to do it earlier, then please explain.

We need to store list of sampled coordinates for pruning. We would need to know coordinates to delete samples from blockstore by cid


Automated Changelog Entry for 0.1.0 on main

Automated Changelog Entry for 0.1.0 on main
npm workspace versions:
jupyterlab-blockly: 0.1.0
jupyterlab-blockly-extension: 0.1.0

After merging this PR run the "Full Release" Workflow on your fork of jupyter_releaser with the following inputs

Input
Value

Target
QuantStack/jupyterlab-blockly

Branch
main

Version Spec
0.1.0

Since
<EMAIL_ADDRESS>

Doesn't include all commits.


The reference of node name

The reference of node name should take some more considerations.
Currently, the reference of node is pointing to the node name defined in enterprise network inventory draft.
typedef node-ref {
type leafref {
path "/nw:networks/nw:network/nw:node/nw-inv:name";
}
description "reference a network node.";
}
It is a little bit strange while adopting this model in operators' network. And there are still some arguments of the modeling of network inventory. We'd better wait for the conclusion of NIMBY. And then choose the fundamental model to reference.
Or we can reference the node-id defined in network model.

ok. I have changed to node-id


Classes representing schema and database

Background
Schema and database has to be represented in application too.
Feature
Create a class representing database and schema. Schema's owner to come from dbowner.txt file.
Both classes offer SQL entries for their creations.
NB!
There's no simple SQL expression to create database safely. It will have to be done either via PL/pgSQL expression or doing a query first (preferably the first).

Merged PR


Scrollable.ensureVisible does not work with nested SingleChildScrollViews on both axes

Steps to Reproduce

Run the sample app below. It creates a grid of cells using a Column of Rows and two SingleChildScrollViews--one for Axis.horizontal and the other for Axis.vertical.

Expected results:
Tapping any cell should center that cell in the viewport via ensureVisible.
         Scrollable.ensureVisible(context,
            alignment: .5,
            duration: Duration(
              milliseconds: 500,
            ));

Actual results:
Cells are not centered as expected. This works correctly when using just a single SingleChildScrollView but not with two.
ensureVisible does traverse all the Scrollables in the context:
https://github.com/flutter/flutter/blob/a8281e31afa9dddfa0764f59128c3a2360c48f49/packages/flutter/lib/src/widgets/scrollable.dart#L312-L323
But something about nesting the scrollviews will yield different values here:
https://github.com/flutter/flutter/blob/a8281e31afa9dddfa0764f59128c3a2360c48f49/packages/flutter/lib/src/widgets/single_child_scroll_view.dart#L628
This behavior has been present since 2019 and is reproducible on the latest beta branch on both iOS and Android.
import 'package:flutter/material.dart';

void main() async {
  runApp(
    MaterialApp(
      home: Scaffold(
        body: Grid(),
      ),
    ),
  );
}

class Grid extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    List<Row> rows = List.generate(
      15,
      (y) => Row(
        children: List.generate(
          12,
          (x) => Cell(
            child: Text("$x,$y"),
          ),
        ),
      ),
    );

    return SingleChildScrollView(
      scrollDirection: Axis.horizontal,
      child: SingleChildScrollView(
        scrollDirection: Axis.vertical,
        child: Column(
          children: rows,
        ),
      ),
    );
  }
}

class Cell extends StatelessWidget {
  final Widget child;

  const Cell({
    this.child,
  });

  @override
  Widget build(BuildContext context) {
    return InkWell(
      onTap: () {
        Scrollable.ensureVisible(context,
            alignment: .5,
            duration: Duration(
              milliseconds: 500,
            ));
      },
      child: Container(
        width: 100,
        height: 100,
        color: Colors.grey.withOpacity(.2),
        margin: EdgeInsets.all(3),
        child: Center(
          child: child,
        ),
      ),
    );
  }
}

Hi @orischwartz
Can you please provide your flutter doctor -v?
Thank you

$ flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, 1.20.0-7.2.pre, on Microsoft Windows [Version 10.0.18362.1016], locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[√] Android Studio (version 4.0)
[√] VS Code (version 1.47.2)
[√] Connected device (1 available)

! Doctor found issues in 1 category.

But this is reproducible on all builds/platforms since at least August 2019 -- no special setup required.

I am currently investigating this issue.

I was able to reproduce this on latest master channel. The scroll is not happening in both directions at the same time.
flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.65, on Mac OS X 10.15.6 19G2021, locale
    en)
    • Flutter version 1.22.0-10.0.pre.65 at
      /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision 2032a448ed (81 minutes ago), 2020-09-02 23:36:19 -0700
    • Engine revision 165abef0a2
    • Dart version 2.10.0 (build 2.10.0-77.0.dev)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 48.1.4
    • Dart plugin version 202.7206

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

[✓] Connected device (4 available)
    • sdk gphone x86 arm (mobile) • emulator-5554 • android-x86    • Android 11 (API
      30) (emulator)
    • macOS (desktop)             • macos         • darwin-x64     • Mac OS X 10.15.6
      19G2021
    • Web Server (web)            • web-server    • web-javascript • Flutter Tools
    • Chrome (web)                • chrome        • web-javascript • Google Chrome
      85.0.4183.83

! Doctor found issues in 2 categories.

@orischwartz
I found the cause of the problem.
The outer Scrollable is responsible for the horizontal adjust, When it calculates the adjustment displacement, it calculates all the cells as a whole, not the one clicked, so the whole is centered in the horizontal direction.
I modified the related algorithm, and now it works as expected

But I'm not sure the expectation is correct for this sample code.
@HansMuller @Piinks @Hixie Would you guys mind taking a look at the behavior?

Fix had to be reverted. Will try to come up with a new test case covering the breakage.

Quick update here: I'm starting to suspect the internal test this broke just needs to be updated. Trying to find the owners of that test to discuss further.
At a high level, the test is using ensureVisible and taking a screenshot. I think that it might not be waiting long enough now to take the screenshot, and that it might have been expecting the wrong element to be centered.

Ok! The basic problem here if you have a TabView or PageView that has Rows in its listview, and you try to scroll something on the righthand side of the screen in thef rist page/tab, it will actually now move you to the second tab. This is not desired behavior.
We might be able to somehow use the hasImplicitScrolling flag to work with this. I'll add a test case to clarify what needs to pass.

Ok! The basic problem here if you have a TabView or PageView that has Rows in its listview, and you try to scroll something on the righthand side of the screen in thef rist page/tab, it will actually now move you to the second tab. This is not desired behavior.
We might be able to somehow use the hasImplicitScrolling flag to work with this. I'll add a test case to clarify what needs to pass.

Thank you very much for your investigation and additional test cases. ：）
I think we can't directly change its behavior, but through a parameter to control it so that developers can choose the scrolling behavior. I will fix it as soon as possible.

I believe I have a fix for this. Posting a PR.

My original instinct to try to use allowImplicitScrolling was wrong, but an easier solution was to just discard the targetRenderObject in _PagePosition's implementation of ScrollPosition.


COPY FROM DATABASE cause Segmentation fault

Copying a MySQL database to a local DuckDB database using
COPY FROM DATABASE results in a segmentation fault.
duckdb --version : v1.1.3 19864453f7
mysql: Server version: 8.0.35-commercial MySQL Enterprise Server - Commercial
OS: Debian GNU/Linux 12 (bookworm)

Steps to reproduce:
duckdb my_duckdb
ATTACH 'host=<IP_ADDRESS> user=myuser password=mystrongpass port=3306 database=mydb' AS mydb (TYPE MYSQL);
use mydb;
COPY FROM DATABASE mydb TO my_duckdb;
Segmentation fault

Thanks for the report!
This might already be fixed in the nightly - could you try installing the nightly to check if the problem persists?
force install mysql from core_nightly;

Thank you,
I tested it with a 20GB database, and my system froze. However, it worked successfully with a smaller database using core_nightly. I'll close this issue as resolved.


Installation instructions and why does it not work?

It would be great to have actual installation instructions for the different cameras/boards and so on. Currently you need to search in 4 different raspi threads to get it working.
I tried installing it by following these steps:
https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=189661&p=1232058#p1218763
and cloning this repository instead of the download which is in the instructions above.
But I still don't seem to get it working correctly. Images captured are completely white. Before updating the PI software there were just some small blue bars captured.
I use a Raspberry Pi B Rev 2.1 and a raspi cam v2.
Tried to use any of the tools. But can't seem to be able to capture a single good frame.
Thanks for your help :)

Thank you for helping.
When I type ./camera_i2c:
setting GPIO for board revsion: 000e
B Rev2 - I2C 0 on GPIOs 0 & 1. GPIOs 5 & 21 for LED and power

Running raspivid first didn't really fix anything. I can take perfect videos and photos using raspivid and raspistill.
I have tried all your suggestions. I assume I kind of botched my installation.

@nabbl Unfortunately I do not have your board revision to try it out and see the exact output. I do see that your revision is in the script, so it should be setting up the pins correctly.
As a side note: It seems that you may not get that table output for every board, so it might not apply to this case.
I would double check on the forums to see if anybody else has tried with a model B board.
I believe those errors are just from the cleaning up section of the program and your error must be happening before that.
Did you not get any output on the screen connected to the raspberry?

If you're having trouble with this library, a potential alternative is https://github.com/cedricve/raspicam. I'm not advocating one over the other, I've just used it a project before and didn't have much trouble getting it up and running.

Thank you jacobhuesman. That one looks promising. I need the camera to capture in 300-600fps though. I don't know if I will manage to do this with raspicam lib.
In the readme however I found the source of my errormessages above (port is not enabled). Need to increase the gpu RAM.
Is it really necessary to install the userland repo completely in order to get  raspiraw running?

https://github.com/cedricve/raspicam is using the standard camera stack, so you won't get frame rates above 120fps.
raspiraw is only meant as a starting point, not a fully fledged app. If you don't understand at least some of the detail of what is going on then you will be in a world of pain, and everything is set up to be fully manual control (probably explains your fully white images to start with - it is running, but totally saturated).
And please remember that the images off the sensor will be the raw Bayer images and therefore probably in need of some processing to make them useful.
I'm a little surprised that you needed to increase GPU mem if you had raspistill/vid working. Enabling the camera in raspi-config normally increases GPU mem to 128, which should be more than sufficient for raspiraw.
As long as the installed userland is reasonably up to date, then there is no need to clone and build it yourself. I'm guessing you're tripping over old instructions where the raspiraw app was in a fork of the userland repo, but now it is out in this repo by itself.
mmal_port_disable error message hopefully fixed with the latest push.
Please always provide the full text including the command when reporting issues, and preferably report on any delays between lines of text (eg 5 seconds from starting the command to those error messages would have told me that it had run and waited the default timeout). I'm making an educated guess as to how you're using raspiraw.
As surmised it's only the clean up code which is trying to disable a port that had already been disabled when not capturing.
@nsimon1 Any objections if I lift your comment above with minor edits and stick it into README.md as installation instructions? You've done a pretty good job at covering everything so I'd only be rehashing it to write my own.

@6by9 No objections, use whatever you can, thanks!

Hey there.
Was able to make a complete reset of my pi and use the installation instructions from @nsimon1
I am now able to take good looking fotos. Thx a lot :)


Improve type alias doc generation

Bug:
Currently, type aliases with optional members don't generate question marks for the member keys.
Enhancement:
Generate descriptions from JSDoc comments for type alias members, in the same way they're generated for interface members. For comparison, see https://doc.deno.land/https/deno.land/std/fs/copy.ts#CopyOptions
Source:
export type ReadTextOptions = {
  /**
   * Trim leading and trailing whitespace. Default is `true`
   */
  trim?: boolean;
  /**
   * Convert all CRLF newlines to LF newlines. Default is `true`
   */
  unixNewlines?: boolean;
};

Generated:
type ReadTextOptions: { trim: boolean, unixNewlines: boolean }

Sorry I don't have a link to provide: that example data was form an ephemeral repo that I deleted. Here are screenshots:

I think this is actually an upstream denoland/deno issue. cc @bartlomieju


app.use(cors()) is simply just not working

I am at a complete loss. After reading material about cross-origin yadda yadda, I am no further along getting this fixed. The error I'm getting is the well-known:
XMLHttpRequest cannot load http://<IP_ADDRESS>:9095/static/5607de95a10c548d52cf.hot-update.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.
My server is setup as follows:
const app = express();
var cors = require('cors')

app.use('/static', express.static(path.join(process.cwd(), '.build')));

app.use(cors())

const bundle = `http://<IP_ADDRESS>:9095/static/client.bundle.js`;
const styles = `http://<IP_ADDRESS>:9095/static/styles.css`;

app.use('/', (req, res) => {
  res.status(200).send(`<!doctype html>

        <title>APP</title>
        <link rel="stylesheet" type="text/css" href="${styles}" />

    `);
});

PLEASE HELP!

I assume that http://<IP_ADDRESS>:9095/static/5607de95a10c548d52cf.hot-update.json is being responded to from your express.static middleware. That means your CORS needs to be prior to that for it to apply to those requests. In other words:
const app = express();
var cors = require('cors')

app.use(cors())

app.use('/static', express.static(path.join(process.cwd(), '.build')));

const bundle = `http://<IP_ADDRESS>:9095/static/client.bundle.js`;
const styles = `http://<IP_ADDRESS>:9095/static/styles.css`;

app.use('/', (req, res) => {
  res.status(200).send(`<!doctype html>

        <title>APP</title>
        <link rel="stylesheet" type="text/css" href="${styles}" />

    `);
});

I've attempted that and it's still not working.

Hi @ddaaggeett have you tried clearing your browser / use private browsing or something? I did run your code and got the error you showed and the new code I posted works just fine. If it doesn't work for you, I'm at a loss, so would need some additional information to get our environments in sync, for example:

Version of this module you are using
Version of Express you are using
The web browser and version you are using
Version of Node.js you are using
Full code you are using
The exact steps you are doing to see the error. Start from opening the web browser and say the exact things you type and click.

Thanks!

@dougwilson - yup still having trouble.
I'm using:
"cors": "^2.8.3"
"express": "^4.13.4",
Chrome version 58.0.3029.110
Node.JS version 7.7.2

As for the exact code and steps I'm using, I'll write in a new comment. If you'd like to dig into this, I'll be very grateful.

Yea, I'd be happy to dig into it. Besides the code & instructions, please also list what version of Express you are using, just in case that matters. You posted a range of versions, not the specific version you're using.

@dougwilson
It looks like I'm using
express: 4.15.2
cors: 2.8.3

The project I'm referring to is blooprint/output in which displays output image content after running image processing on images received by blooprint/input.
in blooprint/input:
run npm run server then npm run android
in blooprint/output
run rethinkdb then npm start then view <IP_ADDRESS>:3000
The blooprint/output server file (app.js) looks like this and can be found here:
import path from 'path';
import express from 'express';
import horizon from '@horizon/server';
import devProps from '../../config/webpack/devProps';
import config from '../../config/page';
import dbConfig from '../../config/db';
var fs = require('fs');

import { socketIO_setup } from './sockets'

const app = express();

var cors = require('cors')

app.use(cors())
app.use('/static', express.static(path.join(process.cwd(), '.build')));

/**
 * @TODO move the html out of the server dir
 */
const host = process.env.NODE_ENV === 'production' ? '' : `http://<IP_ADDRESS>:${devProps.webpackPort}`;
const bundle = `${host}/static/client.bundle.js`;
const styles = `${host}/static/styles.css`;

app.use('/', (req, res) => {
  res.status(200).send(`<!doctype html>

        <title>${config.title}</title>
        <link rel="stylesheet" type="text/css" href="${styles}" />

    `);
});

const run = () => {
    const port = process.env.PORT || config.port;

    const httpServer = app.listen(port, (err) => {
        if (err) {
            throw err;
        }

        console.info(`Express listening at http://localhost:${port}`);
        // eslint-disable-line
    });

    horizon(httpServer, {
        auto_create_collection: true,
        auto_create_index: true,
        project_name: dbConfig.db,
        permissions: false, // waiting for additions to permission system atm
        auth: {
            allow_anonymous: true,
            allow_unauthenticated: true,
            token_secret: config.token_secret
        }
    });

    socketIO_setup(app)

};

export default {
    run
};

Hi @ddaaggeett thanks! I'm going to work on getting it all running. But a quick note is that the error you posted:
XMLHttpRequest cannot load http://<IP_ADDRESS>:9095/static/5607de95a10c548d52cf.hot-update.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.

It says the issue is that you don't have CORS setup on whatever is running on port 9095, but it seems odd that the code you're posted you're trying to add this module to is running on port 3000. What is running on port 9095? That is the server that needs CORS on it, not the server on port 3000.

Right now I'm struggling to get npm run android working. I'm stuck with the following message:
$ npm run android

><EMAIL_ADDRESS>android C:\Users\dougw\GitHub\blooprint-input
> react-native run-android

Looks like you installed react-native globally, maybe you meant react-native-cli?
To fix the issue, run:
npm uninstall -g react-native
npm install -g react-native-cli

I ran
npm uninstall -g react-native
npm install -g react-native-cli

as instructed but just continue to get the same error. How do I resolve?

port:9095 is the webpack dev server and port:3000 is the app
I'll have to look a little more into the react-native issue you're facing. I ended up following Facebook's install instructions as best I could.

port:9095 is the webpack dev server

Gotcha. I mean, the error you posted is saying that is the server not sending the CORS headers, so adding this module to your app on port:3000 will make no difference for that error message. You need to enable CORS on the webpack dev server however you do that.

I'll give that a shot - hopefully will have a response within 24 hours.
Yea, don't worry about digging into my project if you don't want to - although PLEASE JOIN if you'd like!! :) I'd love all the help/mentoring I can get.

Also, a lot of the blooprint/output application is still heavily boilerplate formatted. I know this is frowned upon by many, but for prototyping, it's been great (up until now).

@dougwilson - last commenting on my end for the evening
it looks like you've put me on a promising path - i'll dig into it and let you know how it goes so we can ultimately close this issue
i believe i'm going to have to bite the bullet and figure out how to upgrade to webpack 2.0 in order to add headers to the webpack config file as discussed here

I believe this is no longer an issue. I've included in the webpack configuration:
devServer: {
    ...
    headers: {
        'Access-Control-Allow-Origin': '*'
    }
}

and the CORS issue seems to be handled. Thanks for the tip on getting the header updated on the webpack port and not the app port.  Big help!!!

@ddaaggeett still not working
devServer: {
        contentBase: path.join(__dirname, 'dist'),
        port: 9000,
        index: 'panel.html',
        historyApiFallback: true,
        watchOptions: { aggregateTimeout: 300, poll: 1000 },
        headers: {
            "Access-Control-Allow-Origin": "*",
            "Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, PATCH, OPTIONS",
            "Access-Control-Allow-Headers": "X-Requested-With, content-type, Authorization"
        }
    }

oh boy, i wouldn't even know where to begin. i have no memory of what i was working on while having this issue - but, maybe this may help.
@FlamesoFF, does changing the order help?
headers: {
    "Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, PATCH, OPTIONS",
    "Access-Control-Allow-Headers": "X-Requested-With, content-type, Authorization",
    "Access-Control-Allow-Origin": "*"
}

That last part help a lot

I am using react-rewired how can I add cors?


Mouse cursor getting detached from where it actually is

Hyprland Version
Hyprland, built from branch main at commit 3b657257ecb7628a12a4fe72e733a60f031bfec2 dirty (layout: check for specialworkspace in floating toggle). Tag: v0.30.0-11-g3b657257
Bug or Regression?
Bug
Description
Since yesterday, when I am doing anything that causes a floating window (right click, save file, popup message), the windows will stop responding to mouse input. The mouse actions will not work until I either switch workspaces and back, or if I move my mouse over certain elements (text box usually works) and keep clicking it seems to eventually correct itself.
At one time, I can confirm the mouse was actually interacting with a separate workspace than the one which was on my screen. I had a fullscreen video paused on another workspace, and when I was clicking it was unpausing and pausing that video.
How to reproduce
Open a right click context menu, or a floating popup window
Crash reports, logs, images, videos
No logs as there is no crash, but video of the behavior here: In this video, I am constantly clicking after triggering the right click menu, and towards the end you can see the cursor is over the file browser but actually interacting with the web browser window. Once I placed my mouse over the text box at the top of the file browser, it corrects itself.  https://streamable.com/2qllxn

I have found that moving my mouse over waybar and then back will restore normal behavior every time.

My hyprland updates since it started happening:
2023-09-23T19:11:30-0700] [ALPM] upgraded hyprland-git (0.29.1.r104.1357b660-1 -> 0.30.0.r7.2c4a06eb-1)
[2023-09-24T11:59:53-0700] [ALPM] upgraded hyprland-git (0.30.0.r7.2c4a06eb-1 -> 0.30.0.r8.352ceb11-1)
[2023-09-24T16:37:24-0700] [ALPM] upgraded hyprland-git (0.30.0.r8.352ceb11-1 -> 0.30.0.r11.3b657257-1)
[2023-09-25T14:51:24-0700] [ALPM] upgraded hyprland-git (0.30.0.r11.3b657257-1 -> 0.30.0.r12.ffacd2ef-1)
Looks like it started happening when moving from 0.29 to 0.30. Is there possibly some change here that is conflicting with my config?

Same issue here. In a vertical waybar config scrolling over workspaces sets the focus to the most left/right window. So, you can't scroll more than one workspace before you have to refocus to the waybar.
It started after updating to 0.30.

I'm having a possibly related issue on 29.1 when using movecursortocorner. I have a bind to move the cursor off screen so I can navigate with keyboard without interference. The cursor visually moves, but the program thinks the cursor is still in the same place. Scrolling a webpage with keyboard still has elements popping up even though cursor has been moved. I tried movecursor, but it doesn't seem to work at all for me.

can I get your config?

Here is my config: https://gist.github.com/sawb/81e2155dcabfacc810fa332887f59232

can I get your config?

Here's mine: https://gist.github.com/kevb1973/97a58e24cb00cf8ef83015bb50e0c294

I'm also experiencing this issue. Here is my config.
I can consistently fix it by mousing up to Waybar, then the cursor reattaches to the active window. Switching active windows also does the job.
Opening a right click context window consistently causes the problem.

I've reverted back to b662215fad037e41872d5b820a70577752469520 - and I'm not longer experiencing the issue

#3659 got fixed by 92cf1c23371e35fa352da13305d8489a9e08d540
is that also the case here?

#3659 got fixed by 92cf1c2
is that also the case here?

I just built the latest source and still see this behavior.
Version:
Hyprland, built from branch main at commit 92cf1c23371e35fa352da13305d8489a9e08d540 dirty (input: fix mouse down handling on unset last surface).
Tag: v0.31.0-42-g92cf1c23

what bout 47256a6ed8fb486fd351834c85235a0672d69abc

what bout 47256a6

Yeah, that fixed it, thanks! I'm not able to link the commit to this issue, so please go ahead and reopen and close if you want to add that info.


Update Model Garden vllm serving docker script and dockerfile

Update Model Garden vllm serving docker script and dockerfile.

If you are opening a PR for Community Content under the community-content folder:

[x] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
[x] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
[x] Passes all the required formatting and linting checks. You can locally test with these instructions.

@KCFindstr there is a conflict with the branch. Can you please resolve it? Thanks.


Update for latest geometry access traits

Closed by https://github.com/kylebarron/geoarrow-rs/pull/76


Export full vehicle as one single DAE file

Hello,
is it possible to export a vehicle with all parts and configurations into one single DAE file? I want to add parked cars to my scenario and adding Vehicle objects decrease the performance drastically, so I want to add them as StaticObjects. I found out that JBeam files configure the cars, but since it is not possible to add them to StaticObject files, what could be done alternatively?

Hey, this sounds easy in concept, but making a combined mesh that accurately replicates the exact look of a vehicle is not trivial due to all the other aspects of mashes like the materials you'd have to replicate. The material system in particular isn't as simple as putting everything related into one texture. Furthermore, we are actually slowly phasing out the DAE format, so work on that front would soon be obsolete.
In the meantime, we already do have a basic GLTF exporter, but the engine hasn't been switched to use those for vehicles/objects, so it's basically only one way. You could, however, export to GLTF, convert that to DAE and use that in the meantime. It would also not include any of the textures, due to the complications mentioned above. Hacky, but if it works it works.

If a vehicle looking like this as a placeholder is good enough for your case, you can manually export a vehicle as a GLTF by adding the GLTF exporter UI app from the UI apps menu. If that works for you I can also expose that function to Python.


Fix IPv4 link local address configuration

This PR is fixing the ARP packet type issue and the sender IP address in the ARP announce packets in #15373.

Minor thing about commit subject, please add "net:" prefix to both commit.

Updated all three of them.

The third patch trying to unset the extra padding did not work. Apparently the size needs to be nudged in place, but I don't know how.

@pfl please create github issue for the padding problem, and lets fix it in separate PR.

Issue for the extra padding is #15522


Fix build for OSX by applying the rule of three

Coverage increased (+0.03%) to 84.69% when pulling a730c56314e541dd7870ac8556d43b3cee0c6371 on ruleOfThree into 97262aa25ff3765e672e44ee2cc075e454368cfa on master.


Update missing type/link in D3D12_FEATURE_DATA_SHADER_CACHE

@john-h-k : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Update finding-users.md

Consistent capitalization looks nicer :D (and "for" is lower case in other headings)

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Not sure why or what test has failed or how to go about fixing it... The tests pass when I run them locally!
Not sure what to do?

@PuZZleDucK No worries, it's random failure and not your fault. Thanks for your contribution to Open Source Guides! You rock!

hhflqluip;q;u'q'8]qytq0984330pyv ;w'"a8t'''q'ghga;eoeá488g;aw


Remove a leak when quit() is used in interactive mode, the buffer hol…

…ding the command not beeing freed
Problem
When in interactive mode with chip-tool or the darwin-framework-tool the buffer holding the command "quit()" is not freed.
leaks -atExit -- ./out/debug/standalone/darwin-framework-tool interactive start
quit()

That is not really a big deal for the SDK but it is annoying as it shows up as a leak when using tools to find leaks..
1 (16 bytes) ROOT LEAK: 0x7fd6da6ed230 [16]  length: 6  "quit()"

Change overview

Free the buffer...

Testing
The leak does not show up anymore with this PR.

Accepted for 1.0: examples change


Add PostViews to loading & no posts scenarios; fix paths on Links generation …

I added the PostViews component to the loading and not found scenarios for the PostList because it's more visually consistent across slow loading, and if you don't have it when there are no posts you're sort of stuck without a way out.
Also, the links were broken so I fixed that. I'm guessing that FlowRouter method was deprecated...?

Weird, FlowRouter.extendPathWithQueryParams should work. The reason I don't just use the / route is that if you're already sorting by category, I don't want to undo the category sort when you also filter the list by view. So this method extends the query params without reseting them.

I'll merge in the other change manually though.

Instead of manually merging I can just use the current path and append the params. Not including that part breaks the links once you've clicked on any of the sorting links. Should I do that or is it too late?

Also, I can't find anything about FlowRouter.extendPathWithQueryParams. Am I overlooking it in the docs?

FlowRouter.extendPathWithQueryParams is defined here:
https://github.com/TelescopeJS/Telescope/blob/nova/packages/nova-core/lib/router.jsx#L3-L8

Well, even still this extends and not replaces, which seems more appropriate. And if you do want to extend and then apply multiple params there's something still wrong.
There's a new PR more specific to the URLs: https://github.com/TelescopeJS/Telescope/pull/1259

Well the intended behavior is definitely to extend and not replace. So if that's not working properly maybe we need to fix the extendPathWithQueryParams function? That being said this is part of the components anyway, so people are supposed to customize it to their needs. So we can probably use either behavior as long as it works properly.

So you want to be able to have both "best" and "rejected" applied at the same time? Using extend allows two or more to be applied at the same time and some seem to conflict internally.

Not best and rejected since they're both views, but best and a category, or a category and dates, etc.

But anyway I see the issue, I'll take a look and either fix my function or change the behavior :)

merged this manually.


"lxc storage info" lies about the placement of images? Results in a full filesystem.

"lxc storage show" seems to be lying about where the images are stored.
This is the "default" storage:
# lxc storage show default
config:
  source: /data/lxd
  volatile.initial_source: /data/lxd
description: ""
name: default
driver: btrfs

Further, it shows that the images are stored there, too:
# lxc storage info default
info:
  description: ""
  driver: btrfs
  name: default
  space used: 1.74TB
  total space: 2.85TB
used by:
  containers:
(...)
  images:
  - 02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092
  - 8d894551208470ab85c3d555638ea988dc095b448a1f0f31f38541b76d3eba2d
  - e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c
  profiles:
  - default

However, this is not true - the images are stored somewhere else:
# du -sh /var/snap/lxd/common/lxd/images/*
4.0K    /var/snap/lxd/common/lxd/images/02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092
106M    /var/snap/lxd/common/lxd/images/02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092.rootfs
4.0K    /var/snap/lxd/common/lxd/images/8d894551208470ab85c3d555638ea988dc095b448a1f0f31f38541b76d3eba2d
125M    /var/snap/lxd/common/lxd/images/8d894551208470ab85c3d555638ea988dc095b448a1f0f31f38541b76d3eba2d.rootfs
4.0K    /var/snap/lxd/common/lxd/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c
122M    /var/snap/lxd/common/lxd/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c.rootfs

This misplacement can result in not being able to create an image for largish containers - here, we can see that we have 827 GB free in /data/lxd:
# df -h /data/lxd
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       2.6T  1.6T  827G  67% /data/lxd

However, contrary to "lxc storage info" output, the images are stored somewhere else - on a filesystem with much less space:
# df -h /var/snap/lxd/common/lxd/images
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0         20G  7.9G   11G  43% /

When we want to create an image i.e. for a container which has 50 or 100 GB, it errors, because it tries to do it in /var/snap/lxd/common/lxd/images, which just has 11 GB free - but it should be creating it in /data/lxd/images, which has 827 GB free.

To reproduce "filesystem full":
lxc publish $container --alias $container

You will notice that the image is being built in /var/snap/lxd/common/lxd/images/ - while we would expect it to be built in /data/lxd/images/

It's not a lie at all, images as compressed tarballs or squashfs aren't tied to a storage pool, they're just stored in the images directory, same goes for backups stored in the backups directory.
What's stored in the various storage pools is a much heavier, unpacked copy of those images that's ready for cloning as a new container.
You can manually mount a different storage device onto those two directories to avoid this issue, just be careful that those are always mounted prior to LXD starting up.

It doesn't work as described.
I've tried to bind-mount /data/lxd/images to /var/snap/lxd/common/lxd/images/ via /etc/fstab. It worked, and I'm able to create an image for a large container.
However, this now fails:
# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c' exists and it is not a directory

If I try to mount bind these all directories:
# let LXD use a bigger disk for the images
/data/lxd/images /var/snap/lxd/common/lxd/images       none    bind,nofail      0 0
/data/lxd/images /var/snap/lxd/common/lxd/storage-pools/default/images       none    bind,nofail        0 0

It then errors differently:
# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: UNIQUE constraint failed: storage_volumes.storage_pool_id, storage_volumes.node_id, storage_volumes.project_id, storage_volumes.name, storage_volumes.type

So, I'm unsure how to handle this.

You only want to mount over /var/snap/lxd/common/lxd/images, not over /var/snap/lxd/common/lxd/storage-pools/default/images as this will cause some serious problems.
Did you make sure to move all existing content over to /data/lxd/images before setting up the bind-mount?
And did you restart the LXD daemon after doing all that?

Did you make sure to move all existing content over to /data/lxd/images before setting up the bind-mount?

It was empty, as I've removed all images with "lxd image delete" before.

And did you restart the LXD daemon after doing all that?

I've restarted the whole server - with just this single mount point:
/data/lxd/images /var/snap/lxd/common/lxd/images       none    bind,nofail      0 0
It errors as follows:
# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c' exists and it is not a directory

This is to show the bind mount it mounted properly:
# touch /var/snap/lxd/common/lxd/images/test.txt

# ls /data/lxd/images
e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c  e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c.rootfs  test.txt

# ls /var/snap/lxd/common/lxd/images/
e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c  e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c.rootfs  test.txt

This is empty and not bind mounted, as recommended earlier:
# ls /var/snap/lxd/common/lxd/storage-pools/default/images/
#

Mounts:
# mount|grep btrfs
/dev/sda2 on /data/lxd type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/)
/dev/sda2 on /var/snap/lxd/common/lxd/images type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=264,subvol=/images)

There has to be a simpler way to create images for large containers!

Probably fails because /data/lxd is btrfs - however, /var/snap is ext4:
 # btrfs sub create /var/snap/lxd/common/lxd/storage-pools/default/images/test
ERROR: not a btrfs filesystem: /var/snap/lxd/common/lxd/storage-pools/default/images

You may want to go cleanup /var/snap/lxd/common/mntns/var/snap/lxd/common/lxd/storage-pools/default/images/ which is what LXD sees itself (and is different from what you were looking at).
Sounds like there's a file in there which is causing some trouble.

It is empty when I want to create a new container:
# lxc image delete e2a0808c44c0

# ls /var/snap/lxd/common/mntns/var/snap/lxd/common/lxd/storage-pools/default/images/

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c' exists and it is not a directory

# ls /var/snap/lxd/common/mntns/var/snap/lxd/common/lxd/storage-pools/default/images/
e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c  e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c.rootfs

And then:
# lxc image list
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT  | PUBLIC |             DESCRIPTION              |  ARCH  |   SIZE   |         UPLOAD DATE          |
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+
|       | e2a0808c44c0 | no     | Ubuntu bionic amd64 (20190218_07:43) | x86_64 | 121.31MB | Feb 19, 2019 at 1:17am (UTC) |
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: UNIQUE constraint failed: storage_volumes.storage_pool_id, storage_volumes.node_id, storage_volumes.project_id, storage_volumes.name, storage_volumes.type

Can you show:

nsenter -t $(pgrep daemon.start) -- cat /proc/self/mountinfo
nsenter -t $(pgrep daemon.start) -- ls -lh /var/snap/lxd/common/lxd/images
nsenter -t $(pgrep daemon.start) -- ls -lh /var/snap/lxd/common/lxd/storage-pools/default/images/

# nsenter -t $(pgrep daemon.start) -- cat /proc/self/mountinfo
22 27 0:21 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
23 27 0:4 / /proc rw,relatime shared:13 - proc proc rw
24 27 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev rw,size=131974632k,nr_inodes=32993658,mode=755
25 24 0:22 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
26 27 0:23 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs rw,size=26401024k,mode=755
27 0 9:0 / / rw,noatime shared:1 - ext4 /dev/md0 rw,discard
28 22 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - securityfs securityfs rw
29 24 0:24 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw
30 26 0:25 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs rw,size=5120k
31 22 0:26 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:9 - tmpfs tmpfs ro,mode=755
32 31 0:27 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:10 - cgroup2 cgroup rw
33 31 0:28 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:11 - cgroup cgroup rw,xattr,name=systemd
34 22 0:29 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:12 - pstore pstore rw
35 31 0:30 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:14 - cgroup cgroup rw,pids
36 31 0:31 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,devices
37 31 0:32 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:16 - cgroup cgroup rw,net_cls,net_prio
38 31 0:33 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:17 - cgroup cgroup rw,memory
39 31 0:34 / /sys/fs/cgroup/rdma rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,rdma
40 31 0:35 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:19 - cgroup cgroup rw,hugetlb
41 31 0:36 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,blkio
42 31 0:37 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:21 - cgroup cgroup rw,cpu,cpuacct
43 31 0:38 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:22 - cgroup cgroup rw,perf_event
44 31 0:39 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:23 - cgroup cgroup rw,cpuset
45 31 0:40 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:24 - cgroup cgroup rw,freezer
46 24 0:41 / /dev/hugepages rw,relatime shared:25 - hugetlbfs hugetlbfs rw,pagesize=2M
47 23 0:42 / /proc/sys/fs/binfmt_misc rw,relatime shared:26 - autofs systemd-1 rw,fd=36,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=69798
48 24 0:19 / /dev/mqueue rw,relatime shared:27 - mqueue mqueue rw
49 22 0:8 / /sys/kernel/debug rw,relatime shared:28 - debugfs debugfs rw
50 49 0:11 / /sys/kernel/debug/tracing rw,relatime shared:29 - tracefs tracefs rw
51 22 0:20 / /sys/kernel/config rw,relatime shared:30 - configfs configfs rw
52 22 0:43 / /sys/fs/fuse/connections rw,relatime shared:31 - fusectl fusectl rw
181 27 7:0 / /snap/core/6405 ro,nodev,relatime shared:32 - squashfs /dev/loop0 ro
85 27 7:1 / /snap/lxd/9919 ro,nodev,relatime shared:33 - squashfs /dev/loop1 ro
119 27 7:2 / /snap/core/6350 ro,nodev,relatime shared:34 - squashfs /dev/loop2 ro
192 27 7:3 / /snap/lxd/10102 ro,nodev,relatime shared:35 - squashfs /dev/loop3 ro
298 27 7:4 / /snap/lxd/10150 ro,nodev,relatime shared:36 - squashfs /dev/loop4 ro
300 27 7:5 / /snap/core/6259 ro,nodev,relatime shared:37 - squashfs /dev/loop5 ro
86 27 0:44 / /data/lxd rw,noatime shared:38 - btrfs /dev/sda2 rw,ssd,space_cache=v2,subvolid=5,subvol=/
87 27 0:44 /images /var/snap/lxd/common/lxd/images rw,noatime shared:38 - btrfs /dev/sda2 rw,ssd,space_cache=v2,subvolid=264,subvol=/images
386 26 0:23 /snapd/ns /run/snapd/ns rw,nosuid,noexec,relatime - tmpfs tmpfs rw,size=26401024k,mode=755
468 386 0:3 mnt:[4026532781] /run/snapd/ns/lxd.mnt rw - nsfs nsfs rw
574 27 0:54 / /var/snap/lxd/common/ns rw,relatime - tmpfs tmpfs rw,size=1024k,mode=700
587 574 0:3 mnt:[4026532782] /var/snap/lxd/common/ns/shmounts rw - nsfs nsfs rw
562 574 0:3 mnt:[4026532781] /var/snap/lxd/common/ns/mntns rw - nsfs nsfs rw
702 47 0:77 / /proc/sys/fs/binfmt_misc rw,relatime shared:262 - binfmt_misc binfmt_misc rw
1756 26 0:169 / /run/user/0 rw,nosuid,nodev,relatime shared:276 - tmpfs tmpfs rw,size=26401020k,mode=700

# nsenter -t $(pgrep daemon.start) -- ls -lh /var/snap/lxd/common/lxd/images
total 122M
-rw-r--r-- 1 root root  568 Feb 19 01:17 e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c
-rw-r--r-- 1 root root 122M Feb 19 01:17 e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c.rootfs

# nsenter -t $(pgrep daemon.start) -- ls -lh /var/snap/lxd/common/lxd/storage-pools/default/images/
total 0

@tchwpkgorg Can you also show:

lxd sql global "SELECT * FROM images;"
lxd sql global "SELECT * FROM storage_volumes;"

+-----+------------------------------------------------------------------+------------+----------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+
| id  |                           fingerprint                            |  filename  |      size      | public | architecture |    creation_date     |     expiry_date      |          upload_date           | cached |         last_use_date          | auto_update | project_id |
+-----+------------------------------------------------------------------+------------+----------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+
| 276 | e2a0808c44c0d95e6845e250d743303f55bbfa191bab3209a15682952c68187c | lxd.tar.xz | 1.27197752e+08 | 0      | 2            | 2019-02-18T00:00:00Z | 1970-01-01T00:00:00Z | 2019-02-19T01:17:50.983151743Z | 1      | 2019-02-19T01:18:57.123800071Z | 1           | 1          |
| 277 | 02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092 | lxd.tar.xz | 1.10961208e+08 | 0      | 2            | 2019-02-18T00:00:00Z | 1970-01-01T00:00:00Z | 2019-02-19T01:47:55.955467437Z | 1      | 2019-02-19T01:47:56.061013197Z | 1           | 1          |
+-----+------------------------------------------------------------------+------------+----------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+

# lxd sql global "SELECT * FROM storage_volumes;"
+------+------------------------------------------------------------------+-----------------+---------+------+-------------+----------+------------+
|  id  |                               name                               | storage_pool_id | node_id | type | description | snapshot | project_id |
+------+------------------------------------------------------------------+-----------------+---------+------+-------------+----------+------------+
| 25   | shard01c                                                         | 1               | 1       | 0    |             | 0        | 1          |
| 493  | dbs-prod-old-records                                             | 1               | 1       | 0    |             | 0        | 1          |
| 1160 | vis-mongos                                                       | 1               | 1       | 0    |             | 0        | 1          |
| 1162 | mongo-repl04a                                                    | 1               | 1       | 0    |             | 0        | 1          |
| 1163 | mongo-repl04b                                                    | 1               | 1       | 0    |             | 0        | 1          |
| 1165 | repo02-sys-timedoctor-com                                        | 1               | 1       | 0    |             | 0        | 1          |
| 1166 | geoip                                                            | 1               | 1       | 0    |             | 0        | 1          |
| 1190 | preprod-webserver                                                | 1               | 1       | 0    |             | 0        | 1          |
| 1192 | preprod-webserver-db                                             | 1               | 1       | 0    |             | 0        | 1          |
| 1224 | dbs-preprod                                                      | 1               | 1       | 0    |             | 0        | 1          |
| 1355 | mysql-preprod-2019-02-05-11-48-50                                | 1               | 1       | 0    |             | 0        | 1          |
| 1402 | mysql-prod-slave-before-sharding                                 | 1               | 1       | 0    |             | 0        | 1          |
| 1407 | mysql-prod-slave-before-sharding-orig                            | 1               | 1       | 0    |             | 0        | 1          |
| 1424 | mysql-prod-slave-before-sharding-tests                           | 1               | 1       | 0    |             | 0        | 1          |
| 1598 | shard02c                                                         | 1               | 1       | 0    |             | 0        | 1          |
| 1600 | TDv2-aa697da868-2019-02-18-09-08-08                              | 1               | 1       | 0    |             | 0        | 1          |
| 1604 | TDv2-81ff1beae7-2019-02-18-10-47-35                              | 1               | 1       | 0    |             | 0        | 1          |
| 1605 | TDv2-75367d812a-2019-02-18-11-09-07                              | 1               | 1       | 0    |             | 0        | 1          |
| 1611 | TDv2-d3a1994040-2019-02-18-12-53-59                              | 1               | 1       | 0    |             | 0        | 1          |
| 1612 | TDv2-aa697da868-2019-02-18-13-01-22                              | 1               | 1       | 0    |             | 0        | 1          |
| 1613 | TDv2-preprod-f920d20d74-2019-02-18-13-02-04                      | 1               | 1       | 0    |             | 0        | 1          |
| 1614 | TDv2-9675387f3e-2019-02-18-13-12-38                              | 1               | 1       | 0    |             | 0        | 1          |
| 1620 | TDv2-4eb09c149b-2019-02-18-15-11-40                              | 1               | 1       | 0    |             | 0        | 1          |
| 1621 | TDv2-7b9e5043ff-2019-02-18-15-50-04                              | 1               | 1       | 0    |             | 0        | 1          |
| 1622 | shard01c/shard01c-2019-02-18-23-53-54                            | 1               | 1       | 0    |             | 0        | 1          |
| 1623 | shard01c/shard01c-2019-02-18-23-55-30                            | 1               | 1       | 0    |             | 0        | 1          |
| 1624 | shard01c/shard01c-2019-02-18-23-58-13                            | 1               | 1       | 0    |             | 0        | 1          |
| 1643 | 02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092 | 1               | 1       | 1    |             | 0        | 1          |
+------+------------------------------------------------------------------+-----------------+---------+------+-------------+----------+------------+

Ok, so LXD lists two images in the image store, one of which is supposed to also be in your storage pool.
This doesn't match what's on disk though, so you need to get rid of that 02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092 image to have things match up.
Try lxc image delete 02f5fcaeb7ab85898bc2f2e9b355f0d7f35eb8e1e13b239921ef843a966d2092 and post a new dump of the DB tables to see if it's properly gone from both.

Please note that I'm trying from the scratch with all images removed - as described in "It is empty when I want to create a new container" comment above. Meaning - there is no image at all (as they were all removed) as I try to create a container.
Just to show it once again in more detail:

we don't have any images, what's confirmed by "ls":

# ls /data/lxd/images /var/snap/lxd/common/lxd/images /var/snap/lxd/common/lxd/storage-pools/default/images/
/data/lxd/images:

/var/snap/lxd/common/lxd/images:

/var/snap/lxd/common/lxd/storage-pools/default/images/:

we don't have any images, what's confirmed by "lxc image list":

# lxc image list
+-------+-------------+--------+-------------+------+------+-------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE |
+-------+-------------+--------+-------------+------+------+-------------+

we don't have any images, what's confirmed by sqlite query:

# lxd sql global "SELECT * FROM images;"
+----+-------------+----------+------+--------+--------------+---------------+-------------+-------------+--------+---------------+-------------+------------+
| id | fingerprint | filename | size | public | architecture | creation_date | expiry_date | upload_date | cached | last_use_date | auto_update | project_id |
+----+-------------+----------+------+--------+--------------+---------------+-------------+-------------+--------+---------------+-------------+------------+
+----+-------------+----------+------+--------+--------------+---------------+-------------+-------------+--------+---------------+-------------+------------+

We have this bind mount:
/data/lxd/images /var/snap/lxd/common/lxd/images       none    bind,nofail      0 0

Let's try to create a container now - it fails:
# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40' exists and it is not a directory

repeating "ls":

# ls /data/lxd/images /var/snap/lxd/common/lxd/images /var/snap/lxd/common/lxd/storage-pools/default/images/
/data/lxd/images:
d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40  d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40.rootfs

/var/snap/lxd/common/lxd/images:
d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40  d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40.rootfs

/var/snap/lxd/common/lxd/storage-pools/default/images/:

repeating "lxc image list":

# lxc image list
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT  | PUBLIC |             DESCRIPTION              |  ARCH  |   SIZE   |         UPLOAD DATE          |
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+
|       | d9703623e85b | no     | Ubuntu bionic amd64 (20190219_07:43) | x86_64 | 121.32MB | Feb 20, 2019 at 2:05am (UTC) |
+-------+--------------+--------+--------------------------------------+--------+----------+------------------------------+

repeating sqlite query:

# lxd sql global "SELECT * FROM images;"
+-----+------------------------------------------------------------------+------------+---------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+
| id  |                           fingerprint                            |  filename  |     size      | public | architecture |    creation_date     |     expiry_date      |          upload_date           | cached |         last_use_date          | auto_update | project_id |
+-----+------------------------------------------------------------------+------------+---------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+
| 282 | d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40 | lxd.tar.xz | 1.2721004e+08 | 0      | 2            | 2019-02-19T00:00:00Z | 1970-01-01T00:00:00Z | 2019-02-20T02:05:19.035211215Z | 1      | 2019-02-20T02:05:19.127845403Z | 1           | 1          |
+-----+------------------------------------------------------------------+------------+---------------+--------+--------------+----------------------+----------------------+--------------------------------+--------+--------------------------------+-------------+------------+

Let's try to create the container again - from now on, it fails with a different error (the error "alternates"):
# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: UNIQUE constraint failed: storage_volumes.storage_pool_id, storage_volumes.node_id, storage_volumes.project_id, storage_volumes.name, storage_volumes.type

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40' exists and it is not a directory

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: UNIQUE constraint failed: storage_volumes.storage_pool_id, storage_volumes.node_id, storage_volumes.project_id, storage_volumes.name, storage_volumes.type

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40' exists and it is not a directory

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: UNIQUE constraint failed: storage_volumes.storage_pool_id, storage_volumes.node_id, storage_volumes.project_id, storage_volumes.name, storage_volumes.type

# lxc launch images:ubuntu/bionic/amd64 build
Creating build
Error: Failed container creation: Create container from image: Failed to create image volume: subvolume snapshot failed, source=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40_tmp, dest=/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40, output=ERROR: '/var/snap/lxd/common/lxd/storage-pools/default/images/d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40' exists and it is not a directory

Hopefully it's enough info.
Basically, the usage case is:

want to have rootfs ("/") on a small disk/partition/device, i.e. 20 GB

want to have LXD storage on a large disk/partition/device, i.e. 2 TB or 10 TB, with btrfs

want to be able to create the images for containers which are larger (compressed) than the 20 GB rootfs

In other words - quite a typical usage case if one uses i.e. Amazon AWS (one disk for the system, separate disk for other things), or dedicated server usage (one small partition for the system, the rest of space for the services).

Oh, can you show me lxc storage show default?
A lot of your problems would be explained by you re-using the storage pool's images directory for /var/snap/lxd/common/lxd/images causing conflicts all over the place.

In a setup using two drives, /dev/sdc and /dev/sdd, I get things working without any problem:
root@lantea:~# mkdir -p /data/lxd
root@lantea:~# mkfs.btrfs /dev/sdc
btrfs-progs v4.15.1
See http://btrfs.wiki.kernel.org for more information.

Label:              (null)
UUID:               2f63482b-fb7b-4f98-a90b-bc80fdb4da60
Node size:          16384
Sector size:        4096
Filesystem size:    2.73TiB
Block group profiles:
  Data:             single            8.00MiB
  Metadata:         DUP               1.00GiB
  System:           DUP               8.00MiB
SSD detected:       no
Incompat features:  extref, skinny-metadata
Number of devices:  1
Devices:
   ID        SIZE  PATH
    1     2.73TiB  /dev/sdc

root@lantea:~# mount /dev/sdc /data/lxd
root@lantea:~# df -h /data/lxd
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc        2.8T   17M  2.8T   1% /data/lxd
root@lantea:~# mkdir /data/lxd/images

root@lantea:~# snap install lxd
2019-02-20T03:15:48Z INFO Waiting for restart...
lxd 3.10 from Canonical✓ installed

root@lantea:~# lxd init
Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]:
Name of the new storage pool [default=default]:
Name of the storage backend to use (btrfs, ceph, dir, lvm, zfs) [default=zfs]: btrfs
Create a new BTRFS pool? (yes/no) [default=yes]:
Would you like to use an existing block device? (yes/no) [default=no]: yes
Path to the existing block device: /dev/sdd
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]:
What should the new bridge be called? [default=lxdbr0]:
What IPv4 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
What IPv6 address should be used? (CIDR subnet notation, “auto” or “none”) [default=auto]:
Would you like LXD to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]:

root@lantea:~# mount -o bind /data/lxd/images /var/snap/lxd/common/lxd/images
root@lantea:~# snap restart lxd
Restarted.

root@lantea:~# lxc launch images:ubuntu/bionic build
To start your first container, try: lxc launch ubuntu:18.04

Creating build
Starting build

root@lantea:~# ls /data/lxd/images/
d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40
d9703623e85b3419db46a34d84ffa077ad81e4211d194eaf4f8b64e6b2300e40.rootfs

So it does seem likely that in your setup, /data/lxd is the source of your default storage pool, which would explain why you're running into all those problems.
One way out of this would be to simply make a /data/lxd/lxd_images directory and then bind-mount that over /var/snap/lxd/common/lxd/images rather than use the reserved and already used /data/lxd/images directory for this.

Oh, can you show me lxc storage show default?

config:
  source: /data/lxd
  volatile.initial_source: /data/lxd
description: ""
name: default
driver: btrfs
used_by:
- /1.0/containers/TDv2-0c8224787a-2019-02-20-02-29-36
- /1.0/containers/TDv2-2de17a1881-2019-02-19-16-03-26
- /1.0/containers/TDv2-2de17a1881-2019-02-19-16-07-10
- /1.0/containers/TDv2-2de17a1881-2019-02-19-16-23-03
- /1.0/containers/TDv2-331cc03060-2019-02-20-03-53-39
- /1.0/containers/TDv2-3f7999c686-2019-02-20-02-35-15
- /1.0/containers/TDv2-4eb09c149b-2019-02-18-15-11-40
- /1.0/containers/TDv2-75367d812a-2019-02-18-11-09-07
- /1.0/containers/TDv2-7b9e5043ff-2019-02-18-15-50-04
- /1.0/containers/TDv2-81ff1beae7-2019-02-18-10-47-35
- /1.0/containers/TDv2-9675387f3e-2019-02-18-13-12-38
- /1.0/containers/TDv2-9675387f3e-2019-02-20-04-27-05
- /1.0/containers/TDv2-9675387f3e-2019-02-20-04-33-21
- /1.0/containers/TDv2-aa697da868-2019-02-18-09-08-08
- /1.0/containers/TDv2-aa697da868-2019-02-18-13-01-22
- /1.0/containers/TDv2-b6d7382330-2019-02-20-07-30-17
- /1.0/containers/TDv2-b6d7382330-2019-02-20-09-07-22
- /1.0/containers/TDv2-d0df94d229-2019-02-19-14-39-41
- /1.0/containers/TDv2-d3a1994040-2019-02-18-12-53-59
- /1.0/containers/TDv2-preprod-175180a3a4-2019-02-19-16-26-36
- /1.0/containers/TDv2-preprod-1f796973a8-2019-02-19-14-48-50
- /1.0/containers/TDv2-preprod-405b79089d-2019-02-19-15-49-20
- /1.0/containers/TDv2-preprod-4810d55a1f-2019-02-20-04-34-09
- /1.0/containers/TDv2-preprod-53ec22a856-2019-02-20-09-08-46
- /1.0/containers/TDv2-preprod-80b73cf846-2019-02-20-05-16-53
- /1.0/containers/TDv2-preprod-9620eca3ce-2019-02-20-02-36-02
- /1.0/containers/TDv2-preprod-f920d20d74-2019-02-18-13-02-04
- /1.0/containers/TDv2-preprod-fe4c4c5355-2019-02-20-04-45-48
- /1.0/containers/dbs-preprod
- /1.0/containers/dbs-prod-old-records
- /1.0/containers/geoip
- /1.0/containers/mongo-repl04a
- /1.0/containers/mongo-repl04b
- /1.0/containers/mysql-preprod-2019-02-05-11-48-50
- /1.0/containers/mysql-prod-slave-before-sharding
- /1.0/containers/mysql-prod-slave-before-sharding-orig
- /1.0/containers/mysql-prod-slave-before-sharding-tests
- /1.0/containers/preprod-webserver
- /1.0/containers/preprod-webserver-db
- /1.0/containers/repo02-sys-timedoctor-com
- /1.0/containers/shard01c
- /1.0/containers/shard02c
- /1.0/containers/vis-mongos
- /1.0/images/78e2aede36d073504df16894de984dc021ae2bc1783f0076d0c93ed873bfc1c1
- /1.0/profiles/default
status: Created
locations:
- none

Yes, it works with the following bind mount:


Potential Malware Hosting Sites

Description
Open Directory Listing Host with suspicious filenames in their contents.
Censys Search Query
Malware Hosting Sites.
same_service((services.http.response.html_title:"Index of /" OR services.http.response.html_title:"Directory Listing for /") AND services.http.response.body: /.*?(metasploit|cobaltstrike|sliver|covenant|brc4|bruteratel|(badger|shellcode|sc|beacon|artifact|payload|teamviewer|anydesk|mimikatz|cs)\.(exe|ps1|vbs|bin)).*/)

Additional context
Common malware frameworks and initial payloads list on an Open Directory site. The list of filenames could easily be extended to other frameworks, names, details, etc...

This is a quite powerful regex query! Thanks for submitting. Sorry for the delay on adding the other couple queries, its been a hectic bit.

I leaned you could do them from you, so thank you for teaching me that. :-) No worries on the delay, we've all been there.

Updated to:
same_service((services.http.response.html_title:"Index of /" OR services.http.response.html_title:"Directory Listing for /") AND services.http.response.body: /.*?(metasploit|cobaltstrike|sliver|covenant|brc4|brute-ratel|commander-runme|bruteratel|(badger|shellcode|sc|beacon|artifact|payload|teamviewer|anydesk|mimikatz|cs)\.(exe|ps1|vbs|bin)).*/)

Malware Hosting Sites
A few more interesting files and spelling.

Added in 5a24af8

Update to include reference to "CVE" commonly referred to in exploit code filenames. Also include references to rclone.exe commonly used for data theft.
same_service( (services.http.response.html_title:"Index of /" or services.http.response.html_title:"Directory Listing for /") and services.http.response.body: /.*?(cve|metasploit|cobaltstrike|sliver|covenant|brc4|brute-ratel|commander-runme|bruteratel|ps2exe|(badger|shellcode|sc|beacon|artifact|payload|teamviewer|anydesk|mimikatz|cs|rclone)\.(exe|ps1|vbs|bin|nupkg)).*/ )


Devel

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

20 of 20 (100.0%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+3.0%) to 94.471%

Files with Coverage Reduction
New Missed Lines
%

table.go
4
98.02%

Totals

Change from base Build<PHONE_NUMBER>4:
3.0%

Covered Lines:
1589

Relevant Lines:
1682

💛  - Coveralls


Curl command fails without retrying

Here's my step:
      - name: Wait for backend
        id: wait_backend
        uses<EMAIL_ADDRESS>        with:
          url: # my url here
          max-attempts: 10
          retry-delay: 30s

But I get this immediately when the step runs
Error running action Error: Command failed: curl --fail -sv  [my-url] --retry 10 --retry-delay 30 --retry-connrefused
    at checkExecSyncError (child_process.js:621:11)
    at Object.execSync (child_process.js:657:15)
    at curl (/home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:73:20)
    at /home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:90:9
    at Array.forEach (<anonymous>)
Error: Command failed: curl --fail -sv  [my-url] --retry 10 --retry-delay 30 --retry-connrefused
    at Object.34 (/home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:89:10)
    at __webpack_require__ (/home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:22:30)
    at startup (/home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:37:19)
    at /home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:41:18
    at Object.<anonymous> (/home/runner/work/_actions/jtalk/url-health-check-action/v1.4/dist/index.js:44:10) {
  status: 22,
  signal: null,
  output: [ null, null, null ],
  pid: 3005,
  stdout: null,
  stderr: null
}

I expected retry to work even on 4XX and 5XX, not just connection refused. Was this an incorrect assumption?

Hey @wbobeirne, thanks for your report.
Curl's --retry was designed to retry transient errors, i.e. ones that can get resolved on their own. You should see 5XX errors being retried as expected, whilst 4XX would fail immediately, skipping the retry. Can you confirm if you're seeing this behaviour on 5XX as well and let me know if so?
Most of the time, transient 4XX errors should be avoided (e.g. one could use 503 instead of 404 etc), but I appreciate your case might be an exception. I've added support for --retry-all-errors in v1.5 in case you still need it, however it will not work with the current ubuntu-latest due to its Curl being a tad out of date.
I'm closing this, but feel free to reopen if you're still facing problems in v1.5.


Fixed permission request, Added optional backdrop.

The permission request was happening too late and causing a crash.
I added code to ask for the permission on startup instead, but left the original code in place.

Why is the permission request too late? at that point does it fails?

It happens when you select a new image to crop (I was testing transparency).
This is the stack trace from the emulator:
04-16 11:47:40.879: E/AIC(2759): Failed to load image by URI
04-16 11:47:40.879: E/AIC(2759): java.lang.RuntimeException: Failed to load sampled bitmap: content://media/external/images/media/39
04-16 11:47:40.879: E/AIC(2759): 	at com.theartofdev.edmodo.cropper.BitmapUtils.decodeSampledBitmap(BitmapUtils.java:154)
04-16 11:47:40.879: E/AIC(2759): 	at com.theartofdev.edmodo.cropper.BitmapLoadingWorkerTask.doInBackground(BitmapLoadingWorkerTask.java:93)
04-16 11:47:40.879: E/AIC(2759): 	at com.theartofdev.edmodo.cropper.BitmapLoadingWorkerTask.doInBackground(BitmapLoadingWorkerTask.java:26)
04-16 11:47:40.879: E/AIC(2759): 	at android.os.AsyncTask$2.call(AsyncTask.java:295)
04-16 11:47:40.879: E/AIC(2759): 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
04-16 11:47:40.879: E/AIC(2759): 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
04-16 11:47:40.879: E/AIC(2759): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
04-16 11:47:40.879: E/AIC(2759): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
04-16 11:47:40.879: E/AIC(2759): 	at java.lang.Thread.run(Thread.java:818)
04-16 11:47:40.879: E/AIC(2759): Caused by: java.lang.SecurityException: Permission Denial: reading com.android.providers.media.MediaProvider uri content://media/external/images/media/39 from pid=2759, uid=10057 requires android.permission.READ_EXTERNAL_STORAGE, or grantUriPermission()
04-16 11:47:40.879: E/AIC(2759): 	at android.os.Parcel.readException(Parcel.java:1599)
04-16 11:47:40.879: E/AIC(2759): 	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
04-16 11:47:40.879: E/AIC(2759): 	at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:146)
04-16 11:47:40.879: E/AIC(2759): 	at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:692)
04-16 11:47:40.879: E/AIC(2759): 	at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1104)
04-16 11:47:40.879: E/AIC(2759): 	at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:942)
04-16 11:47:40.879: E/AIC(2759): 	at android.content.ContentResolver.openInputStream(ContentResolver.java:662)
04-16 11:47:40.879: E/AIC(2759): 	at com.theartofdev.edmodo.cropper.BitmapUtils.decodeSampledBitmap(BitmapUtils.java:135)
04-16 11:47:40.879: E/AIC(2759): 	... 8 more

It looks like there is a bug in isReadExternalStoragePermissionsRequired because this code wouldn't reach that point unless this method cleared it.
Can you debug it and see why it thinks the permissions are not required when it clearly does, my money is on isUriRequiresPermissions method, something with the exception.
Greatly appreciate.

I'm not sure I have time for it this week.
But why bother?
I can just take out the old code that wasn't working and the demo app will still do what it needs to do.

I believe i fixed it, it looks like it throws SecurityException for you while in my tests it's always FileNotFoundException... Android...
I think its important for an application to request permissions only if and when they are required, not all URI's require external storage access so I want to check if it does before it request it.
It's not important for the sample but the relevant code is part of CropImageHelper that I created to be used by clients.

Make sure you re building with 23 and the project is set with that minimum.
you should get a security exception. But, you might not if the user has denied several times  (not sure).
The code I added is a little more robust and will tell the user how to handle the situation.
It should be fairly simple to refactor the code in onPostResume to its own method and call it later (essentially as soon as the user clicks the menu option).

It's probably have to do either with the device, I use Moto X, or the source app, Dropbox in my case.
How is your code more robust?

It's doing the recommended practice of providing a rational if the user denies.
I think i also included a button to the settings page (I usually do).

I don't agree, the alert window in not required because the permission request is shown right after the user selected a source that requires it, so it is obvious why it was requested. It's the recommended behavior as documented in ActivityCompat.shouldShowRequestPermissionRationale.
If the use denies the permissions a toast notifies if the cancellation due to permissions denial. the user can then either try again or select a source that doesn't require external storage.

Its your codebase. but your case won't hand the user going back and trying again later, as far as I can see.

I have cherry-picked the checkerboard but decided to leave the permissions out.
Thx.


Swift "naive" impl contradicts the philosophy

The README states

We define the "naive" implementations as those which a developer with enough experience in a given language would implement as a baseline "good enough" solution where correctness is more important than performance.

Yet the Swift Language Guide, which relatively speaking a developer with any experience will spend some time glancing at clearly states:

The additional capabilities that classes support come at the cost of increased complexity. As a general guideline, prefer structures because they’re easier to reason about, and use classes when they’re appropriate or necessary. In practice, this means most of the custom data types you define will be structures and enumerations.

https://docs.swift.org/swift-book/LanguageGuide/ClassesAndStructures.html
Yet the impl uses classes exclusively contradicting the above two notions
https://github.com/frol/completely-unscientific-benchmarks/blob/86c455f2dfdfc9637dc66760a6d86571dad7cefe/swift/Sources/naive/main.swift#L4

@rex-remind101 good catch! May I ask you to submit a PR?

Nodes need to be moved a lot, so I wouldn't use a struct for it. Also it doesn't build if you try to use a struct:
error: value type 'Node' cannot have a stored property that recursively contains it


Automatic Shema Reading

Solve #69

can you rebase your branch on dev?

Will do.
On Tue, Aug 17, 2021 at 5:50 PM Mohamed Shaban @.***>
wrote:

can you rebase your branch on dev?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/CogSLanguageUtilities/pull/119#issuecomment-900414908,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATO5ZCGNYQHPBLADQCYOYLTT5KAIFANCNFSM5CIDYJIQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Will do.
…
On Tue, Aug 17, 2021 at 5:50 PM Mohamed Shaban @.***> wrote: can you rebase your branch on dev? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#119 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATO5ZCGNYQHPBLADQCYOYLTT5KAIFANCNFSM5CIDYJIQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

Will do.
…
On Tue, Aug 17, 2021 at 5:50 PM Mohamed Shaban @.***> wrote: can you rebase your branch on dev? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#119 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATO5ZCGNYQHPBLADQCYOYLTT5KAIFANCNFSM5CIDYJIQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

can you please pull the latest changes from dev (origin) before rebasing


Team-mate added

Joss. Amra eivabei kaj korbo.
Branch kore sekhane code korbo. Then pull request diba, check kore merge kore dibo.\
Eibar ami nijei pull request diye merge kore disi, just for example.

Ami vule branch ta restore kore disilam, Sorry.
Ignore that delete > restore > delete thing.


Pinned k8s-extension to 0.4.3

Pinnded k8s-extension to 0.4.3 working version
Any update logic for k8s-extension has been changed to remove and then add to pin (az extension update does not support specifying version).

I have tested the end-to-end deployment with the Microk8s Data scenario - here's a screenshot at the very end of the successful deployment:

Rolling this back, as upstream fix seems to be in place for now.