Error: Process completed with exit code 100.

Hello, guys , this tools error! what happen ?
Run # ======
================================================================================
BEFORE CLEAN-UP:

$ dh -h /

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        84G   63G   22G  75% /
$ dh -a /

Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/root       87[204](https://github.com/nervosnetwork/ckb-explorer/actions/runs/6194473061/job/16817524423#step:2:206)404 65040924  22147096  75% /
$ dh -a

Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/root       87204404 65040924  22147096  75% /
devtmpfs         3541732        0   3541732   0% /dev
proc                   0        0         0    - /proc
sysfs                  0        0         0    - /sys
securityfs             0        0         0    - /sys/kernel/security
tmpfs            3544060<PHONE_NUMBER>   1% /dev/shm
devpts                 0        0         0    - /dev/pts
tmpfs            1417624     1092   1416532   1% /run
tmpfs               5120        0      5120   0% /run/lock
cgroup2                0        0         0    - /sys/fs/cgroup
pstore                 0        0         0    - /sys/fs/pstore
bpf                    0        0         0    - /sys/fs/bpf
systemd-1              -        -         -    - /proc/sys/fs/binfmt_misc
hugetlbfs              0        0         0    - /dev/hugepages
mqueue                 0        0         0    - /dev/mqueue
debugfs                0        0         0    - /sys/kernel/debug
tracefs                0        0         0    - /sys/kernel/tracing
fusectl                0        0         0    - /sys/fs/fuse/connections
configfs               0        0         0    - /sys/kernel/config
ramfs                  0        0         0    - /run/credentials/systemd-sysusers.service
/dev/loop0         65024    65024         0 100% /snap/core20/2015
/dev/loop1        114688   114688         0 100% /snap/lxd/24322
/dev/loop2         41856    41856         0 100% /snap/snapd/20092
/dev/sda15        106858     6182    100677   6% /boot/efi
binfmt_misc            0        0         0    - /proc/sys/fs/binfmt_misc
/dev/sdb1       14341128  4194336   9396508  31% /mnt
tmpfs             708812       12    708800   1% /run/user/1001
tmpfs            1417624     1092   1416532   1% /run/snapd/ns
nsfs                   0        0         0    - /run/snapd/ns/lxd.mnt
================================================================================

********************************************************************************
=> Android library: Saved 12GiB
********************************************************************************

********************************************************************************
=> .NET runtime: Saved 2.1GiB
********************************************************************************

********************************************************************************
=> Haskell runtime: Saved 0B
********************************************************************************

Reading package lists...
Building dependency tree...
Reading state information...
Package 'dotnet-nightly' is not installed, so not removed
Package 'dotnet-targeting-pack-3.1' is not installed, so not removed
Package 'dotnet-host-7.0' is not installed, so not removed
Package 'dotnet-sdk-6.0-source-built-artifacts' is not installed, so not removed
Package 'dotnet-sdk-7.0-source-built-artifacts' is not installed, so not removed
Package 'dotnet-templates-6.0' is not installed, so not removed
Package 'dotnet-templates-7.0' is not installed, so not removed
Package 'dotnet-apphost-pack-3.1' is not installed, so not removed
Package 'dotnet-runtime-3.1' is not installed, so not removed
Package 'dotnet-sdk-3.1' is not installed, so not removed
Package 'dotnet-hostfxr-3.1' is not installed, so not removed
Package 'dotnet-runtime-deps-3.1' is not installed, so not removed
The following additional packages will be installed:
  aspnetcore-targeting-pack-6.0 aspnetcore-targeting-pack-7.0
The following packages will be REMOVED:
  aspnetcore-runtime-6.0 aspnetcore-runtime-7.0 dotnet-apphost-pack-6.0
  dotnet-apphost-pack-7.0 dotnet-host dotnet-hostfxr-6.0 dotnet-hostfxr-7.0
  dotnet-runtime-6.0 dotnet-runtime-7.0 dotnet-runtime-deps-6.0
  dotnet-runtime-deps-7.0 dotnet-sdk-6.0 dotnet-sdk-7.0
  dotnet-targeting-pack-6.0 dotnet-targeting-pack-7.0
The following packages will be upgraded:
  aspnetcore-targeting-pack-6.0 aspnetcore-targeting-pack-7.0
2 upgraded, 0 newly installed, 15 to remove and 16 not upgraded.
Need to get 3045 kB of archives.
After this operation, 1029 MB disk space will be freed.
Get:1 file:/etc/apt/apt-mirrors.txt Mirrorlist [142 B]
Ign:2 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-6.0 amd64 6.0.121-0ubuntu1~22.04.1
Ign:3 http://azure.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-7.0 amd64 7.0.110-0ubuntu1~22.04.1
Ign:2 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-6.0 amd64 6.0.121-0ubuntu1~22.04.1
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-7.0 amd64 7.0.110-0ubuntu1~22.04.1
Ign:2 http://security.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-6.0 amd64 6.0.121-0ubuntu1~22.04.1
Err:2 mirror+file:/etc/apt/apt-mirrors.txt jammy-updates/universe amd64 aspnetcore-targeting-pack-6.0 amd64 6.0.121-0ubuntu1~22.04.1
  404  Not Found [IP: 52.[252](https://github.com/nervosnetwork/ckb-explorer/actions/runs/6194473061/job/16817524423#step:2:254).75.106 80]
Ign:3 http://security.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-targeting-pack-7.0 amd64 7.0.110-0ubuntu1~22.04.1
Err:3 mirror+file:/etc/apt/apt-mirrors.txt jammy-updates/universe amd64 aspnetcore-targeting-pack-7.0 amd64 7.0.110-0ubuntu1~22.04.1
  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch mirror+file:/etc/apt/apt-mirrors.txt/pool/universe/d/dotnet6/aspnetcore-targeting-pack-6.0_6.0.121-0ubuntu1%7e22.04.1_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch mirror+file:/etc/apt/apt-mirrors.txt/pool/universe/d/dotnet7/aspnetcore-targeting-pack-7.0_7.0.110-0ubuntu1%7e22.04.1_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Error: Process completed with exit code 100.

Facing the same issues in my build

Facing the same issues in my build

It seems that the location of some third-party packages has changed. Wait for the author to fix it.

experiencing the same issue

The script will first run apt get update to update the software package list, and then run apt get remove - y '^ dotnet -. *' to fix the issue of executing errors based on rm rf/usr/share/dotnet

@ywt114 thanks you for pointing out how to workaround this issue!
Based on the info, here is a copy-paste snippet.
Just place this step before free-disk-space step.
      # temporary workaround for an error in free disk space action
      # https://github.com/jlumbroso/free-disk-space/issues/14
      - name: Update Package List
        run: |
          sudo apt-get update
          sudo apt-get remove -y '^dotnet-.*'

@ywt114 thank you for pointing out how to workaround this issue!
Based on the info, here is a copy-paste snippet. Just place this step before free-disk-space step.
      # temporary workaround for an error in free disk space action
      # https://github.com/jlumbroso/free-disk-space/issues/14
      - name: Update Package List and Remove Dotnet
        run: |
          sudo apt-get update
          sudo apt-get remove -y '^dotnet-.*'

In fact, the only commands extracted from his script are: sudo - E rm - rf/usr/local/lib/android/usr/share/dotnet/opt/ghc | | true
Sudo - E apt get update
Sudo E apt get remove - y '^ dotnet -. *' ^ llvm -. * '' php. * '^ mongodb -. *' ^ mysql -. * 'azure cli Google cloud sdk Google chrome table firefox powershell mono devel libgl1 mesa dri | | true
Sudo - E apt get autoremove - y | | true
Sudo - E apt get clean | | true
Sudo Docker image prune -- all -- force | | true
Sudo - E rm - rf "$Agent_TOOLSDIRECTORY" | | true
Sudo swapoff - a&&sudo rm - f/mnt/swapfile | | true
Free - h
So I think adding it to line 174 is more reasonable

temporary workaround for an error in free disk space action
  # https://github.com/jlumbroso/free-disk-space/issues/14
  - name: Update Package List and Remove Dotnet
    run: |
      sudo apt-get update
      sudo apt-get remove -y '^dotnet-.*'

Thanks this workaround works for me. Maybe @jlumbroso can have a look at this to get this fixed in the main repo?

@wind57 thanks for the workaround I'll try this

@wind57 didn't help https://github.com/rook/rook/pull/12959

@jakoch Thanks for the awesome workaround!!! 🥳
With the recent pull-requests and fixes, does v1.3.0 address the issues encountered in this thread or not? Thanks for letting me know, and sorry for the delays in updating this.

Removed all my workarounds and jlumbroso/free-disk-space@main now works again. Thanks!

Thanks so much for letting me know @firefart ! Thanks for your patience to all of you!


Don't require note when adding

The add command currently treats a command without the note o/ flag as being in invalid format. Let's fix it to not require specifying that (notes being optional).

To check: Ensure editing doesn't require notes either

I will try to look into this this week.


Incorrect coords of the pin

Description
Dear author,
I'm trying to use your library in my project but I stack on problem concerning to pin displaying.
I added PinView from your source code. And set pin like this:
pointF = PointF(mark.lat, mark.lng)
ivDrawing.setPin(pointF!!),

where pointF is the x and y coordinates.
I also set image view state with center in this point with some scale:
val state = ImageViewState(PHOTO_MIN_SCALE, pointF!!, ORIENTATION_0)

and set image from file (I take file URI, because Bitmap is not my case: I have to large image (8000x8000 px) for displaying):
ivDrawing.setImage(ImageSource.uri(drawing.attachment.fileName), state)

but receive strange result in view (you can see it below)
I saw the #408 , but in there is no my case - I use file instead drawable source. And there is no informations in doc about pin's displaying.
What in your opinion the problem is?
Expected behaviour

Actual behaviour

System
Android Studion 3.4.1
Best Regards,
Pavel A.

Well, I found the weak place of this case.
In fact coords are saved on Server as PointF(lat, lng), in the coordinate system with (0;0) in bottom-left corner. However in this lib the (0;0) point is in the top-left corner.
In this case I should set pin in coordinates (lng; <image_height> - lat) to show it correctly.
BTW Thanks for your library! It's perfect for my purposes.


[WEAPON] Mining laser

A Mining Laser should be implemented so that, upon selection and use within the time of play, it fires and operates properly.
--The mining laser is a long range beam of energy. This beam deals consistent damage over a moderate range.--
The mining laser:

Should produce a slightly conical - but straight-pointing - beam of light.

Additional features:
-The laser will produce low damage; however, due to its' constant hit rate, will deal damage consistently and at high quantities.
-The laser should be slightly conical; the beam will taper to a point as it reaches its' maximum range.
-Much like any other weapon, when used with the homing projectile module, this beam can contort into curved lines.
-Will assess starting damage later on, apologies, will add soon
The following polishes can be done later, and will have their own seperate task if not done here.
-The laser should be a very very light blue, representing electricity.
-It should have small sparks running through it.
Additional context
Refer to mood board on capstone google drive for reference on appearance.

Currently trying to approach this by using many very fast bullets. Video one just uses very fast bullets with trails:
https://user-images.githubusercontent.com/19755210/128593533-cef51c5f-8318-4041-9af1-787c1bfb76ae.mp4
Video 2 uses more dense bullets, with logic that has them stay closer to one-another, in an attempt to make it look more like a beam
https://user-images.githubusercontent.com/19755210/128593555-3b106874-3a2a-4288-9100-5595fbadcc38.mp4
Have sent these on discord for feedback.

https://user-images.githubusercontent.com/19755210/128633552-c9ac501e-2c6c-4273-91ee-e89c3a74f47c.mp4
^ what it is like now! After Sunday meeting, group is OK with implementing this weapon the way it is. I'm calling it a 'rapid-fire mining laser', though a line/damage over time laser like the one discussed in this issue could definitely be implemented in future.


License missing in package.json

See here. The MIT license is missing.

Mind submitting a pull request for this?

See #29

Thanks!


Use link cursor instead of select for details section in Markdown preview

VSCode Version: 1.10.2
OS Version: Windows7 x64.

Steps to Reproduce:

Add a detail section in markdown (.md) document

<details>
  <summary>Source Code</summary>

   Some text
</details>

Open Preview:
For this element a link cursor  should be used (same for common links) instead of select cursor .

I can also reproduce this in Chrome proper. The cause seems to be that the details/summary contains text. If you use an image or other element, you retrain the standard cursor
I believe the current behavior is by design so I'm closing this issue as upstream/as-designed. Try using ]custom css](https://code.visualstudio.com/Docs/languages/markdown#_using-your-own-css) to alter the cursor style for this element
summary {
    cursor: default
}


bug(config): fill missed options to pass default values to callback

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.04%) to 82.55%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

enapter/ucm/config.lua
6
7
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
1.04%

Covered Lines:
123

Relevant Lines:
149

💛  - Coveralls


python312Packages.aiounifi: 73 -> 74

Diff: https://github.com/Kane610/aiounifi/compare/refs/tags/v73...v74
Changelog: https://github.com/Kane610/aiounifi/releases/tag/v74
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 301058 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.unifi
python311Packages.aiounifi
python311Packages.aiounifi.dist
python312Packages.aiounifi
python312Packages.aiounifi.dist


Log refresh create/update statements to stdout not stderr

Hello lovely Abletech developers!
When records are refreshed this gem sends puts statements to stderr. This happens when successfully creating or updating a record, not for error/exception scenarios. These end up in our logs looking like errors and effecting our error monitors.
Would you please consider changing them to stdout instead of stderr?
Thanks!

Hi Tracey,
Thanks for raising this, I'll look into it now :)

This is now solved, please update to 1.2.1. Thank you @traceyn !

Amazing, thanks so much!


Sample issue

I want to take this issue

I want to take this up

I'll take it up

i want to take this issue

I can solve this issue

Me too

i want to take this issue


selectAllRows does not render the style of each row checkbox

$scope.gridApi.selection.selectAllRows();

I'm using this api to checkall, but the UI not correct, when the first time, only the header checkbox is checked.  If I using this api again, none of the checkbox will be checked, while I'm using

$scope.gridApi.selection.getSelectedGridRows()

it seems all are checked.
So how to checkall as default?

It's not really clear what your problem is.  Could you try again to explain what it's doing and what you want it to do?

@PaulL1 I solved my problem, but I'm not sure if it is the best way. My problem is how to make all the checkbox checked when the data is loaded, now I use $timeout after I load griddata, let me show you in plunker, So is it the best/right way to do it ? http://plnkr.co/edit/Eel592CZCbKtUdqKxzhB?p=preview

$timeout is the recommended way - just call selectAll from a $timeout after you load the data.  The data rendering will always take only 1 digest cycle, and a timeout of 0 ms will always run immediately after that digest cycle, irrespective of how much data you have.


Move generic client APIs into pkg/apis/

Description
This makes much more visible which APIs are supported by the generic client, makes it easier to have generic client supporting APIs not sharing any code with existing old clients and is a place where other big projects place their API definitions.
Release Note
Release note for CHANGELOG:

* NONE (unreleased feature)

References

for generic client introduced in #56
moves core/resources API built in #67

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Codecov Report

Merging #86 (32ca322) into main (6e6d43e) will decrease coverage by 0.19%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##             main      #86      +/-   ##
==========================================
- Coverage   55.80%   55.61%   -0.20%
==========================================
  Files          89       93       +4
  Lines        4012     4051      +39
==========================================
+ Hits         2239     2253      +14
- Misses       1409     1433      +24
- Partials      364      365       +1

Flag
Coverage Δ

integration
44.39% <9.16%> (-0.47%)
:arrow_down:

unittests
28.11% <32.50%> (+0.07%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apis/lbaas/v1/frontend_genclient.go
0.00% <0.00%> (ø)

pkg/core/resource/api.go
100.00% <ø> (+48.00%)
:arrow_up:

pkg/core/resource/resource.go
14.28% <ø> (ø)

pkg/lbaas/backend/api.go
100.00% <ø> (+27.27%)
:arrow_up:

pkg/lbaas/backend/backend.go
43.70% <ø> (ø)

pkg/lbaas/frontend/api.go
100.00% <ø> (+86.66%)
:arrow_up:

pkg/lbaas/frontend/frontend.go
42.95% <ø> (ø)

pkg/lbaas/loadbalancer/api.go
100.00% <ø> (+68.75%)
:arrow_up:

pkg/lbaas/loadbalancer/loadbalancer.go
50.79% <ø> (ø)

pkg/apis/lbaas/v1/loadbalancer_genclient.go
18.75% <18.75%> (ø)

... and 2 more

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 6e6d43e...32ca322. Read the comment docs.


Url life time

The url parameter of the Thumbnail resource type seems to expire within 24 hours. It might be a good idea to mention this somewhere.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 34278783-5c78-7257-bb3b-469d0046743d
Version Independent ID: 35192842-4fc6-b17d-d228-4e1edcfc5035
Content: Thumbnail - Microsoft Graph v1.0
Content Source: api-reference/v1.0/resources/thumbnail.md
Product: ****
Technology: microsoft-graph
GitHub Login: @JeremyKelley
Microsoft Alias: JeremyKelley

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Citation

Codecov Report
Base: 76.70% // Head: 76.70% // No change to project coverage :thumbsup:

Coverage data is based on head (7678607) compared to base (71b9f11).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   76.70%   76.70%
=======================================
  Files         101      101
  Lines        6246     6246
=======================================
  Hits         4791     4791
  Misses       1455     1455

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Implement posterior level concealment

We need to implement a way to conceal the chains too!
This will require us to move the smokescreen namespace to have something like:
import smokescreen.ConcealDataVector and import smokescreen.ConcealPosterior to conceal at different levels.

Discussions from Telecon on 2024-11-12

What do we do with parameters that are prior bounded? these can give away any shifts (@jessmuir has an implementation from the DES analysis for these cases)
Multi-chain support
Two different shifts:

absolute shifts $\delta \theta$ centered at zero
relative shifts with relation to a fiducial value or a chain such that model comparison can be done (@jessmuir has some examples of how to do this).

Include also an "exclusion list" to avoid shifting some desired parameters

Jessie sent the DES scripts via slack here


Automatic image orientation based on EXIF is broken

Expected Behavior
When processing any image, the intended orientation should be preserved.
Current Behavior
In the provided example, a portrait image gets saved in landscape. You can see the black bars that get added on left and right. The core image is oriented correctly inside, but the output file has the wrong dimensions.
Failure Information (for bugs)
Steps to Reproduce

git clone https://github.com/mkondel/jimp-exif-text.git
yarn
yarn start
look at input.jpg and output.jpg

Screenshots
I have screenshots in the repo linked above ^^.
Context
I am using Jimp with excellent result on AWS Lambda. This bug is not related to that at all, as it can be replicated locally.

Jimp Version: v0.6.4
Operating System: Linux (Fedora)
Node version: v8.12.0

Failure Logs

I am also experiencing this issue, which is quite crippling for any application that allows users to upload an image from their device and camera.
This issue has noting to do with the rotate function (yet). As in the sample code provided by @mkondel, simply loading and writing the image will already deform it.

I fixed my issue by using another lib called jpeg-autorotate. Please checkout my repo above for a working demo. I use this lib before JIMP to "burn in" the rotation.
const fileIn = fs.readFileSync('input.jpg')
const jo = require('jpeg-autorotate')
const {buffer} = await jo.rotate(fileIn, {quality: 30})
const image = await Jimp.read(buffer)

I agree with @grnch : it would be great if this could be fixed in Jimp.
I've struggled with this for hours yesterday wondering what I was doing wrong.
jpeg-autorotate works but you have to add another module and understand how it works (for exemple it will throw an error (!) if no rotation has to be done so you need another code path to handle this case...).

@oliver-moran I think this is broken again in v0.14.0 (maybe before)

The same issue with v0.14.0

this issue with v0.16.1

Any news?

Still broken in v0.16.1

same here with v0.16.1

Still broken in 0.16.1.

Folks. The image rotation is not handled equally by each browser. There are even differences between OS'es for the same browser. It is possible that even with a working JS lib (jimp or other) the EXIF data will get stripped/ignored by the upload. As an example, on windows chrome I have to pre-process all my images locally with a shell script that applies EXIF rotation directly to the files.

I have the same issue. And for me 'v0.10.3' is the latest version that auto rotate images (and resize). From a EXIF meta tag to actual pixels that are rotated. Rotating the pixels is what I would like to achieve.
Anyone a suggestion to get this working in a newer version. I'm using the following javascript code:
jimp.read(sourceFilePath)
.then(image => {

	image.resize(1000, jimp.AUTO);
	image.quality(80);

	image.write(targetFilePath, () => {
		process.stdout.write("≈");
		resolve(true);
	});

})
.catch(err => {
	console.error(err);
	resolve(false);
});

still brocken in "jimp": "0.22.12"


feat: implement new api DiscoverDevices

This feature allows cfm to discover the devices in the network by type (cma or cxl-host).
dingm@juniper:~/CFM/cfm$ curl -s -X GET http://localhost:8080/cfm/v1/discover?type=cxl-host | jq

[
{
"hostname": "mag-cfm-cxlhost1.local",
"address": "<IP_ADDRESS>",
"port": 8082,
"type": "cxl-host"
}
]

dingm@juniper:~/CFM/cfm$ curl -s -X GET http://localhost:8080/cfm/v1/discover?type=cma | jq

[
{
"hostname": "granite104.local",
"address": "<IP_ADDRESS>",
"port": 443,
"type": "cma"
},
{
"hostname": "granite7.local",
"address": "<IP_ADDRESS>",
"port": 443,
"type": "cma"
}
]

Please use https://github.com/holoplot/go-avahi as module


Path to Labfiles is not correct

Cloning this repo or downloading as a zip results in a file system structure like: "D:\PL-300-Microsoft-Power-BI-Data-Analyst-Main\Allfiles\Labs\01\Starter\01-prepare-data-with-power-query-in-power-bi-desktop"
The extraneous "\01\Starter" should be removed.

I concur - this seems like the best solution to modify the existing /Allfiles such that:  The extraneous "\01\Starter" should be removed.

This issue has been addressed with the latest commit.


Workbox swDest references are inconsistent

Reported on twitter: https://twitter.com/marcushellberg/status/1103827852552736768
@jeffposnick it looks like many of our build tool docs share config partials. I believe workbox-webpack-plugin is the only one that defaults to a  particular swDest option. Can you confirm?
If so, any objection to just changing all of our swDest examples to be service-worker.js?

That's correct; only the webpack plugin has a default swDest filename—because webpack can infer the output path. The other build tools need you to provide output info.


Pin CCurl version in Package.swift

Fixes issue #2394.  Pins CCurl version to 0.2.3 to fix potential self-signed certificates issue.

PG 1656

👍


[EMB-561] Fix Registries.discover to recognize test.osf.io registrations

Purpose
Fix Registries.discover to recognize test.osf.io registrations
Summary of Changes

Fix regex used to determine the main link for registrations of OSF source
Add tests

Side Effects
N/A
Feature Flags
N/A
QA Notes
Check and make sure registration created on test.osf.io appears in search results with test.osf.io links.
Ticket
EMB-561
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2638

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.786%

Totals

Change from base Build 2627:
0.0%

Covered Lines:
5672

Relevant Lines:
7228

💛  - Coveralls


Timestamps not being parsed

I have this function in my model
    parse: function(attributes) {
        return _.reduce(attributes, function(memory, value, key) {
            memory[_.str.camelize(key)] = value;
            return memory;
        }, {});
    }

That camelizes my fields. However when I save a model in the database and then call .toJSON() it returns my fields camelized except for the timestamps that keep as updated_at and created_at that I would expect them to be updatedAt and createdAt.

Solved. Instead of put
hasTimestamps: ['created_at', 'updated_at'],

I put
hasTimestamps: ['createdAt', 'updatedAt'],

And it works.


Permission sets cannot be viewed for OnPrem

Describe the bug
while trying to open Permissions from Permission sets Page, unable to view permissions.
To Reproduce
Steps and to reproduce the behavior:

Go to Permission Sets Page
Select one of the below Permission Set and click Permissions action.
a.  PAYPALSTANDARD
b.  PAYPALSTANDARDREAD
c.   INTELLIGENTCLOUDBASE
d.   INTELLIGENTCLOUDBC

Expected behavior
Should be able to see permissions.
it seems like if the permission set has any new object that is created in that app then we are getting error
Screenshots
Below are details of error

5. Versions:

Business Central: 15.2  OnPrem

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
As this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


About us mobile

Oops, will do that real quick

we'll need to change the images (they are currently hex shaped, we'll need rectangular ones so that they render correctly).
otherwise lgtm
merging it in

actually, @mxinburritos  can you resolve the merge conflict? Feel free to merge after that

I got it fixed

thx appreciate it!


$cordovaPushV5 register documentation

The example for register in the documentation for $cordovaPushV5 incorrectly shows that the register promise is passed an object with a registrationId property, when in reality, the registration ID is passed directly to the promise callback.
Example in docs:
// register to get registrationId
$cordovaPushV5.register().then(function(data) {
  // `data.registrationId` save it somewhere;
})

should be:
// register to get registrationId
$cordovaPushV5.register().then(function(registrationId) {
  // save registrationId somewhere
})

Here's the source code where you can see that the registration ID is passed to the promise resolve function.
It took me quite a while to determine that the reason that data.registrationId was undefined in my app was because data wasn't an object.

Feel free to add a PR to the docs to correct them. This is good work, thank you!

@gortok Cool, I'll do it now. The reason i posted here though is because I couldn't figure out where the docs live or if they're open source. Just found them in the gh-pages branch, so good to go.

PR submitted.


aws-shared-1: introduce second staging bastion

What is the problem that this PR is trying to fix?
I keep getting locked out of the other one we have and I do not know why.
This is at least a workaround for now.

Wasn't able to get this working, giving up on it for now. :)


v2.2.0 Documentation on Netgate 4200 gives "Failed to load API definition."

Describe the bug
v2.2.0 Documentation on Netgate 4200 gives "Failed to load API definition."
That is /api/v2/documentation gives "Failed to load API definition." on v2.2.0.
Rolled back to v2.1.3 and /api/v2/documentation loads correctly once more.
To Reproduce
Steps to reproduce the behavior:
1.) Upgrade from v2.1.3 to v2.2.0 via System > REST API > Updates
2.) Try and view System > REST API > Documentation, now get the "Failed to load API definition." error.
3.) Roll back to v2.1.3 on System > REST API > Updates
4.) System > REST API > Documentation now loads correctly once more.
Expected behavior
I expect for System > REST API > Documentation to still work when on v.2.2.0.
Screenshots or Response

pfSense Version & Package Version:

pfSense Version: 24.03-RELEASE
Package Version: v2.2.0 / v2.1.3

The OpenAPI schema path changed in v2.2.0, looks like your browser may still have the Swagger config with the old path cached. Try clearing your browser cache and see if it loads correctly afterward.

Got you, indeed. :)
Can fix this by setting Cache-Control: no-store, no-cache, must-revalidate

I'll consider this resolved since this path shouldn't change again in the future.


Update refined to 0.9.26

Updates eu.timepit:refined from 0.9.25 to 0.9.26.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "eu.timepit", artifactId = "refined" } ]

labels: library-update, semver-patch

Codecov Report

Merging #475 (bedda30) into master (7e5d3d7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #475   +/-   ##
=======================================
  Coverage   86.31%   86.31%
=======================================
  Files         108      108
  Lines        1425     1425
  Branches       40       40
=======================================
  Hits         1230     1230
  Misses        195      195

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 7e5d3d7...bedda30. Read the comment docs.


TypeError: Cannot read property '__type' of null

Issue Description
While performing a query through the REST API:
curl 'http://$IP:1337/parse/classes/SectionItem' --data-binary '{"where":
{"$relatedTo":{"object" {"__type":"Pointer","className":"Class","objectId":"uAgTxj5kIt"},"key":"items"}},
"include":"<lots and lots of nested classes>"

I get the following response:
Uncaught internal server error. [TypeError: Cannot read property '__type' of null] TypeError: Cannot read property '__type' of null
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:778:15)
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:753:32)
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:788:10)
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:788:10)
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:753:32)
    at includePath (/usr/lib/node_modules/parse-server/lib/RestQuery.js:644:18)
    at RestQuery.handleInclude (/usr/lib/node_modules/parse-server/lib/RestQuery.js:625:22)
    at /usr/lib/node_modules/parse-server/lib/RestQuery.js:630:22
    at run (/usr/lib/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:89:22)
    at /usr/lib/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:102:28

I think this could be due to missing pointers
Environment Setup

Server

parse-server version: 2.2.15
Operating System:     Debian 8.5
Localhost or remote server?: DigitalOcean

Database

MongoDB version: 3.0.11
Localhost or remote server?: ObjectRocket

Please let me know if I need to clarify my bug report

This maybe fixed by that: https://github.com/ParsePlatform/parse-server/pull/2114

@flovilmart I just tested this branch, but got the same error message.
I digged a bit deeper and it happens when having null pointers in an array like so:
[null, null, {__type: "Pointer", className: "_User", objectId: "luvzg4fRHb"}]
The expected outcome is that the null pointers remain when included in the query, and the non-null pointers are expanded.
I implemented a naive fix which solved the issue, but I don't know whether it broke any tests as I'm unable to run the test suite:
(node) warning: possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at Server.addListener (events.js:239:17)
    at Server.once (events.js:265:8)
    at Server.close (net.js:1490:12)
    at helper.js:82:12
    at new Promise (/root/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:193:7)
    at reconfigureServer (helper.js:81:10)
    at run (/root/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:89:22)
    at /root/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:102:28
    at flush (/root/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickDomainCallback (node.js:390:13)

Error: listen EADDRINUSE :::8378
    at Object.exports._errnoException (util.js:873:11)
    at exports._exceptionWithHostPort (util.js:896:20)
    at Server._listen2 (net.js:1250:14)
    at listen (net.js:1286:10)
    at Server.listen (net.js:1382:5)
    at EventEmitter.listen (/root/parse-server/node_modules/express/lib/application.js:617:24)
    at helper.js:92:22
    at Server.<anonymous> (net.js:1491:9)
    at Server.g (events.js:260:16)
    at emitNone (events.js:72:20)
    at Server.emit (events.js:166:7)
    at emitCloseNT (net.js:1537:8)
    at nextTickCallbackWith1Arg (node.js:431:9)
    at process._tickDomainCallback (node.js:394:17)

I'm getting similar error as well
2016-08-03T21:05:28.747016+00:00 app[web.2]: error: Uncaught internal server error. [TypeError: Cannot read property '__type' of null] TypeError: Cannot read property '__type' of null 2016-08-03T21:05:28.747046+00:00 app[web.2]:     at findPointers (/app/node_modules/parse-server/lib/RestQuery.js:778:15) 2016-08-03T21:05:28.747047+00:00 app[web.2]:     at findPointers (/app/node_modules/parse-server/lib/RestQuery.js:753:32) 2016-08-03T21:05:28.747048+00:00 app[web.2]:     at findPointers (/app/node_modules/parse-server/lib/RestQuery.js:788:10) 2016-08-03T21:05:28.747048+00:00 app[web.2]:     at findPointers (/app/node_modules/parse-server/lib/RestQuery.js:753:32) 2016-08-03T21:05:28.747049+00:00 app[web.2]:     at includePath (/app/node_modules/parse-server/lib/RestQuery.js:644:18) 2016-08-03T21:05:28.747050+00:00 app[web.2]:     at RestQuery.handleInclude (/app/node_modules/parse-server/lib/RestQuery.js:625:22) 2016-08-03T21:05:28.747051+00:00 app[web.2]:     at RestQuery.handleInclude (/app/node_modules/parse-server/lib/RestQuery.js:634:17) 2016-08-03T21:05:28.747052+00:00 app[web.2]:     at /app/node_modules/parse-server/lib/RestQuery.js:630:22 2016-08-03T21:05:28.747052+00:00 app[web.2]:     at run (/app/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:89:22) 2016-08-03T21:05:28.747053+00:00 app[web.2]:     at /app/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:102:28

I've discovered that this error happens when I set an object attribute to nil or null, instead of using unset(:attribute) to empty it out. Crazy tho this causes my entire query (and app) to fail..

@jameslin101 you're on the right track, Can you run with VERBOSE=1 and reproduce the issue so we have the full trace of request/response?

Yes, I have this also when, for example, include'ing an array with null pointers (in the dashboard this shows as [null,null]).

@jameslin101 I have  a fix but I'm unable to write a test that would make this reproducible.

@flovilmart I don't get the error when setting a pointer field to null and then retrieving it using include as @jameslin101  suggests. I only get it when include'ing arrays with null pointers.

@doender I'm on it right now, I have a fix but it strips out the null's from the array, do you need them back or not?

I think we just implemented the same fix :)
But I would like to keep the nulls as my app relies on the length of the arrays being consistent... Cannot get that to work just yet through

Alright, I'll add that :)

Thanks guys for looking into this! I was away this weekend but can send the
log with verbose=1 later tonight if it will still be helpful
On Tuesday, September 6, 2016, Florent Vilmart<EMAIL_ADDRESS>wrote:

Alright, I'll add that :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ParsePlatform/parse-server/issues/2189#issuecomment-244969299,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABD_-Ek2dTc-tqy1rBiUrFmU5chY51kCks5qnXmugaJpZM4JDTct
.

@doender there's an explicit filter on the null and undefined values https://github.com/ParsePlatform/parse-server/blob/master/src/RestQuery.js#L567 Not sure what we should do.

Ah, I missed that, thanks!
I know for sure that the original API did return the null values though...

and makes that test fail: https://github.com/ParsePlatform/parse-server/blob/master/spec/ParseQuery.spec.js#L1621

A bit random maybe, but would the test pass if we return null, but not undefined ones?
The rationale would be that there is a difference between invalid pointers and explicit null pointers...

Yep working well!

This is gonna be in the next release.

@flovilmart Sadly I still found a related problem when including nested fields of an array of null pointers. For example, I have an object like {'list': [null, null, null]} and then query with include list.field I get:
error: Uncaught internal server error. [TypeError: Cannot read property 'field' of null] TypeError: Cannot read property 'field' of null
    at findPointers (/usr/lib/node_modules/parse-server/lib/RestQuery.js:810:25)

Alright, that's for nested includes. Can you open a new issue please? This one fixes of 1st level includes


Add the GCV repo as a submodule

Add the GCV repo as a submodule so that the development Docker Compose file will work with any additional hoop jumping.

Done in commits 40a7ba1b3e79bbe30ce90a1e49f9120358428452 and a477488759c27ba15fa80b08c320f82fcac8dc27. Closing.


Create kukullagaikas.txt

Added https://www.kukullagaikas.com/ from Spain

@sanmibuh I am sorry, your website says that you teach students in primary school only. Do you have high school students, too?

Hi,
Yes. In my town (Etxebarri - Bizkaia - Spain) the school have 3 building:
• Main building: Kukullaga HLHI for primary school
• Seconday building: IES Etxebarri BHI for Early Childhood and high school
•Tertiary building: CEI Jose Miguel de Barandiaran for only Early Childhood.
Both 3 building are part of Kukullaga Ikas.

@sanmibuh Thank you for the clarification. Pull request merged.


docs(transformItems): add a section in prepare for v3

This section documents the move to transformItems in "prepare for v3". It's also a good time to think if we want deprecate all transforrmData? And how?

Thanks for the review @Haroenv, I've updated my prettier config accordingly :)

Thanks for the suggestions @samouss and @francoischalifour (go back to holidays 🌴). I didn't go completely into new syntax tricks and kept some old school elements, let me know  :)


Assign comment for query, so it will make debugging easier

new Query("Users")
.Comment("Fetch invalid users")
.WhereTrue("Invalid");

We can log it using
queryFactory.Logger = (compiled, query) =>
{
    logger.LogInformation("// " + query.GetComment() + "\n" + compiled.ToString() + "\n", compiled.Bindings);
};

Output
// Fetch invalid users
SELECT * FROM [Users] WHERE [Invalid] = 1

It already had a QueryComment property, but I added GetComment anyway. And to avoid a null reference exception I made those changes.


"user" can not be used as a tenant name

Exception when user of tenant user logs in.

user created:

auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: Creating new user...
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: Reading request...
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: ... request is:
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: {'name': 'Faber', 'username': 'faber', 'email'<EMAIL_ADDRESS>'confirmEmail'<EMAIL_ADDRESS>'profile': 'user', 'service': 'admin', 'id': 'b16f6d0f-6064-5143-cba9-676f99400a35'}
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: Inserting user into database...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Checking user data...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user data is OK.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Checking whether user already exist...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user doesn't exist.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Checking whether user e-mail is already being used...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user e-mail is not being used.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Creating user instance...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user instance was created.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: User data is: faber created by admin
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Configuring Kong...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... Kong was successfully configured.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Adding new user to database session...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... new user was added to database session.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Committing database changes...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... database changes were committed.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Configuring user profile...
auth_1                        | [09/05/19 - 13:32:51] |RelationshipController| INFO: user faber added to group user by admin
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user profile was configured.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Configuring user password...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... user password was configured.
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: Sending tenant creation message to other components...
auth_1                        | [09/05/19 - 13:32:51] |CRUDController| DEBUG: ... tenant creation message was sent.
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: ... user data was inserted into the database.
auth_1                        | [09/05/19 - 13:32:51] |webRoutes| DEBUG: ... new user was created.

user updated via GUI:

auth_1                        | [09/05/19 - 13:41:23] |CRUDController| INFO: user faber updated by admin
auth_1                        | [09/05/19 - 13:41:23] |CRUDController| INFO: {'oldUser': {'id': '4', 'name': 'Faber', 'username': 'faber', 'service': 'admin', 'email'<EMAIL_ADDRESS>'profile': 'user', 'created_date': '2019-05-09 13:32:51.208109', 'created_by': '1'}, 'newUser': {'name': 'Usuário', 'username': 'faber', 'service': 'admin', 'email'<EMAIL_ADDRESS>'profile': 'user'}}

user tenant updated via API: tenant user

auth_1                        | [09/05/19 - 13:44:57] |CRUDController| INFO: user faber updated by admin
auth_1                        | [09/05/19 - 13:44:57] |CRUDController| INFO: {'oldUser': {'id': '4', 'name': 'Usuário', 'username': 'faber', 'service': 'admin', 'email'<EMAIL_ADDRESS>'profile': 'user', 'created_date': '2019-05-09 13:32:51.208109', 'created_by': '1'}, 'newUser': {'service': 'user', 'email'<EMAIL_ADDRESS>'name': 'Usuário', 'profile': 'admin', 'username': 'faber'}}
auth_1                        | [09/05/19 - 13:44:57] |CRUDController| INFO: will emit tenant lifecycle event user - CREATE
auth_1                        | [09/05/19 - 13:44:57] |KafkaPublisher| DEBUG: Publishing event: kafka:9092, dojot.tenancy: {"type": "CREATE", "tenant": "user"}
auth_1                        | [09/05/19 - 13:44:57] |messenger| INFO: Trying to publish something on kafka,                      current producer-topics: {'dojot.tenancy': {'dojot-management': 'e453bc62-db0c-42db-bd56-8b759a978d1d', 'admin': 'c444613f-63fc-4f97-939a-93007966672b'}}
auth_1                        | [09/05/19 - 13:44:57] |messenger| INFO: Published message: {'type': 'CREATE', 'tenant': 'user'} on topic e453bc62-db0c-42db-bd56-8b759a978d1d
auth_1                        | [09/05/19 - 13:44:57] |KafkaPublisher| DEBUG: data published

user logged in:

auth_1                        | [09/05/19 - 13:49:26] |AuthenticationController| INFO: user faber loged in

reported ERROR

device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Retrieving templates.
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Initializing tenant context...
device-manager_1              | [2019-05-09 13:49:26,430] ERROR in app: Exception on /template [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 387, in flask_get_templates
device-manager_1              |     result = TemplateHandler.get_templates(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 86, in get_templates
device-manager_1              |     init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 84, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)
device-manager_1              | [2019-05-09 13:49:26,506] ERROR in app: Exception on /device [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/DeviceHandler.py", line 940, in flask_get_devices
device-manager_1              |     result = DeviceHandler.get_devices(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/DeviceHandler.py", line 254, in get_devices
device-manager_1              |     tenant = init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 95, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Retrieving templates.
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Initializing tenant context...
device-manager_1              | [2019-05-09 13:49:26,514] ERROR in app: Exception on /template [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 387, in flask_get_templates
device-manager_1              |     result = TemplateHandler.get_templates(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 86, in get_templates
device-manager_1              |     init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 95, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Retrieving templates.
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Initializing tenant context...
device-manager_1              | [2019-05-09 13:49:26,524] ERROR in app: Exception on /template [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 387, in flask_get_templates
device-manager_1              |     result = TemplateHandler.get_templates(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 86, in get_templates
device-manager_1              |     init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 95, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Retrieving templates.
device-manager_1              | [09/05/19 - 13:49:26] |TemplateHandler| DEBUG: Initializing tenant context...
device-manager_1              | [2019-05-09 13:49:26,605] ERROR in app: Exception on /template [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 387, in flask_get_templates
device-manager_1              |     result = TemplateHandler.get_templates(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 86, in get_templates
device-manager_1              |     init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 95, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)
device-manager_1              | [09/05/19 - 13:49:32] |TemplateHandler| DEBUG: Retrieving templates.
device-manager_1              | [09/05/19 - 13:49:32] |TemplateHandler| DEBUG: Initializing tenant context...
device-manager_1              | [2019-05-09 13:49:32,118] ERROR in app: Exception on /template [GET]
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | psycopg2.ProgrammingError: syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |
device-manager_1              |
device-manager_1              | The above exception was the direct cause of the following exception:
device-manager_1              |
device-manager_1              | Traceback (most recent call last):
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1982, in wsgi_app
device-manager_1              |     response = self.full_dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1614, in full_dispatch_request
device-manager_1              |     rv = self.handle_user_exception(e)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1517, in handle_user_exception
device-manager_1              |     reraise(exc_type, exc_value, tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/_compat.py", line 33, in reraise
device-manager_1              |     raise value
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1612, in full_dispatch_request
device-manager_1              |     rv = self.dispatch_request()
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/flask/app.py", line 1598, in dispatch_request
device-manager_1              |     return self.view_functions[rule.endpoint](**req.view_args)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 387, in flask_get_templates
device-manager_1              |     result = TemplateHandler.get_templates(request)
device-manager_1              |   File "/usr/src/app/DeviceManager/TemplateHandler.py", line 86, in get_templates
device-manager_1              |     init_tenant_context(req, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 117, in init_tenant_context
device-manager_1              |     init_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 95, in init_tenant
device-manager_1              |     switch_tenant(tenant, db)
device-manager_1              |   File "/usr/src/app/DeviceManager/TenancyManager.py", line 73, in switch_tenant
device-manager_1              |     session.execute("SET search_path TO %s" % tenant)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/scoping.py", line 153, in do
device-manager_1              |     return getattr(self.registry(), name)(*args, **kwargs)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1176, in execute
device-manager_1              |     bind, close_with_result=True).execute(clause, params or {})
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 948, in execute
device-manager_1              |     return meth(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
device-manager_1              |     return connection._execute_clauseelement(self, multiparams, params)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
device-manager_1              |     compiled_sql, distilled_params
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception
device-manager_1              |     exc_info
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
device-manager_1              |     reraise(type(exception), exception, tb=exc_tb, cause=cause)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise
device-manager_1              |     raise value.with_traceback(tb)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
device-manager_1              |     context)
device-manager_1              |   File "/usr/src/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
device-manager_1              |     cursor.execute(statement, parameters)
device-manager_1              | sqlalchemy.exc.ProgrammingError: (psycopg2.ProgrammingError) syntax error at or near "user"
device-manager_1              | LINE 1: SET search_path TO user
device-manager_1              |                            ^
device-manager_1              |  [SQL: 'SET search_path TO user'] (Background on this error at: http://sqlalche.me/e/f405)

Ticket analysis meeting (May, 22nd): Changed column.


Connect to Rails server from another machine

I have a Ruby on Rails server running on Bash, and I cannot connect to the server from another machine on the same network. I am able to connect to the server from another machine when I run the server from my Ubuntu virtual machine. I know the server is running successfully because I can connect to it from my local machine, just not another machine on the network.
Does Bash on Windows allow inbound connections?

Yes this should work. You will need to make an inbound firewall exemption to allow access for whichever port you are trying to connect to.

That worked! Thank you!! :)


rbac: Update ClusterRole rules for ocs-operator

This

adds support for list, watch for storageclasses.storage.k8s.io
adds rules for noobaas.noobaa.io
s/cephobjectstore/cephobjectstores/

The CSV has been regenerated with these changes.
Fixes #85

/cc @jarrpa
Can you merge this?


Enhancing a lil -.github/workflows/linter.yml

Issue Description:
If we do not implement the changes, the GitHub Action will only run on push and pull requests. This means that the linter will not be run if the user manually triggers the workflow. Additionally, the linter will not be able to check for the presence of the flake8 binary, so it may fail if the binary is not installed. Finally, the linter will not be able to use a configuration file to customize its settings.
Here are some of the potential consequences of not implementing the changes:
The linter may not be run on all changes, which could lead to errors being introduced into the code.
The linter may not be able to check for the presence of the flake8 binary, which could lead to the linter failing.
The linter may not be able to use a configuration file to customize its settings, which could limit the linter's effectiveness.
Expected Behavior:
here are some suggestions for changes in the GitHub Action:
The on section should be updated to include the workflow_dispatch event. This will allow the linter to be run manually, as well as on push and pull requests.
The steps section should be updated to include a step that checks for the presence of the flake8 binary. This will prevent the linter from running if the binary is not installed.
The run command in the Lint with flake8 step should be updated to use the -c option to specify a configuration file. This will allow the user to customize the linter's settings.
Current Behavior:
The original code will only run on push and pull requests. This means that the linter will not be run if the user manually triggers the workflow. Additionally, the linter will not be able to check for the presence of the flake8 binary, so it may fail if the binary is not installed. Finally, the linter will not be able to use a configuration file to customize its settings.
Here is the behavior of the original code:
The on section of the GitHub Action specifies that the linter will only run on push and pull requests.
The steps section of the GitHub Action does not include a step that checks for the presence of the flake8 binary.
The run command in the Lint with flake8 step does not use the -c option to specify a configuration file.
Labels:
enhancement

sorry i published a wrong issue


Import API step?

Hi, I have created all of the setup and stuck at the API import step in Flow, where does the json file come from? I tried creating from blank bu then the connector has no actions which I assume are in the API file. thanks for any info to resolve this.

sorry, just fund this under the closed issues


test: Added regression tests for currency input

Regression tests added for currency input widget

/ci-test-limit

/ci-test-limit

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


Question / Suggestion

Any intention to add Biomes O' Plenty wood signs in future versions? (redwood sign, fir sign, etc.)
I was looking for a mod that adds these in MC v1.16.4 and surprisingly I can't find one.
I realize text may not be legible on some, but half the time builders use these is for detailing, leaving them blank.
Thank you for consideration.

I was under the assumption that biomes o' plenty already has their own signs?

I was under the assumption that biomes o' plenty already has their own signs?

They don't, I searched the JEI item list for "sign". =(

They don't, I searched the JEI item list for "sign". =(

If they can do that too, even better. That's very cool. I'll keep my fingers crossed. =)

If they can do that too, even better. That's very cool. I'll keep my fingers crossed. =)

Oh god I didn't realize I needed chain signs until now...

Oh god I didn't realize I needed chain signs until now...


⚠ SceneTime has degraded performance

In dd733fa, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 7904 ms

Resolved: SceneTime performance has improved in 989b086 after 8 minutes.


Release v0.1.1

Also adds pre-commit config for markdownlint.
[v0.1.1] - 2024-02-16
Fixed

CLI run-workflow dropped an s from json.loads, and the help text on the
timout argument was
incorrect. (#5)
Return correct execution([-1]), as new Step Function executions are
appended to the executions list, from the StateDB
Item. (#6)
Enable both call CLI to set exit status code based of Deployment.call,
and exception raised from subprocess.check_call if used as a
library. (#7

Test fail due to: getmoto/moto#7198 (moto v5 replaces individual decorators with single mock_aws decorator)


SyntaxError: Unexpected token '}'. Expected a statement as the body of a for loop.

I run react-native init TestProject to create a project, then I run the app with iOS and it works fine.
I add socket.io-client in my dependencies, and run npm install.
"dependencies": {
  "react-native": "^0.13.2",
  "socket.io-client": "^1.3.7"
}

And add
window.navigator.userAgent = "react-native";
var io = require('socket.io-client/socket.io');

var TestProject = React.createClass({
...

I got
SyntaxError: Unexpected token '}'. Expected a statement as the body of a for loop.

I use socket.io before, and it works. However, every my React Native project that uses socket.io is broken now. So strange...
Line 60582 of http://localhost:8081/index.ios.bundle?platform=ios&dev=true is
for(length = members.length;property = members[--length];hasProperty.call(object,property) && callback(property))}}else

It seems that many ; symbol is gone in my js bundle file.

I am seeing this too (without socket.io). There is something unexpected happening with the bundled JavaScript -- we should run a parser over it to see if the bundled JS is invalid.

Looks like the packager could be stripping out newlines that ASI relied on, or perhaps is inserting a closing curly brace before a newline that triggered ASI?
function hmmm() { for (var i = 0; i < 10; i++); }
undefined

function hmmm() { for (var i = 0; i < 10; i++) }
VM262:2 Uncaught SyntaxError: Unexpected token }(…)InjectedScript._evaluateOn @ VM100:875InjectedScript._evaluateAndWrap @ VM100:808InjectedScript.evaluate @ VM100:664

cc @martinbigio any commits come to mind?

I just narrowed this down and came here to report it and found this bug.  My repro steps were just to create a freshly inited project and add socket.io-client, with the corresponding require() in my index.ios.js.  The last time I tried this was in 0.4.4, which I think was pre-babel, and it worked then.

@ide  Thanks for confirming this issue.
Is there any way to temporarily solve the problem?
Use the past react-native version in package.json? Or, downgrade react-native-cli?

I came up with a hacky workaround.  There's this in socket.io.js, line 6395:
for (length = members.length; property = members[--length]; hasProperty.call(object, property) && callback(property));

Modifying it to include an empty for loop body did the trick.  Looking at the output of the packager, it looks like the transformation caused the semicolons to get stripped from this line and the one immediately following it, and the two following closing braces to get stuck on the same line, resulting in a transformation from:
        for( ... );
    };
}

to:
    for( ... ) }}

@ntuckerxx Thanks, the hack works.
I modify 3 places.
Line 6395, 6624, 6632 in socket.io.js (package version 1.3.7)
make for( ... ); to for( ... ){}

looks like the problem was fixed on babel 5.8.33.

I too noticed this issue come up when using socket.io
You shouldn't have to really make any changes. I made sure to update all my dependencies and homebrew (although it might be unrelated) and restarted my computer to get it to disappear.
@oney Are you still having issues?

No, updating packages solves the problem.


WIP: Jenkins Implementation Testing

Testing Jenkins builds on SSB

When this becomes more stable and it is clear that we want go to forward with it, please consider squashing your commits. Thanks!


More than one file was found with OS independent path 'error_prone/Annotations.gwt.xml

More than one file was found with OS independent path 'error_prone/Annotations.gwt.xml

Can you clarify which project you're building? Sounds like it may be similar to https://github.com/googlesamples/androidtv-sample-inputs/issues/49, but I don't see the same problem building any of the projects with Android Studio 4.1

This is a cool Japanese guy. His solution works for me. Please refer to this link.
Here's the patch
chang@zbook:~/git-root/androidtv-sample-inputs$ git diff
diff --git a/app/build.gradle b/app/build.gradle
index 4651b79..f380054 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -18,6 +18,13 @@ android {
             proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
         }
     }
+
+    packagingOptions {
+        exclude 'error_prone/Annotations.gwt.xml'
+        exclude 'third_party/java_src/error_prone/project/annotations/Annotations.gwt.xml'
+        exclude 'third_party/java_src/error_prone/project/annotations/Google_internal.gwt.xml'
+        exclude 'jsr305_annotations/Jsr305_annotations.gwt.xml'
+    }
 }

 ext {


AllowShortFunctionsOnASingleLine was twice.

-- Code style of document was confusing.
-- Added link to documentation for current version.

Any plans to move to the newer clang-format?

Any plans to move to the newer clang-format?

It would be fine, let me try to format with clang V10 and test it internally. Once OK, I would switch to this V10 version.

Any plans to move to the newer clang-format?

It would be fine, let me try to format with clang V10 and test it internally. Once OK, I would switch to this V10 version.

@Hadatko , testing with Clang V10 formatted code is OK, we can use it, I will provide an update early next week together with other changes for 1.8.0 release.

Do not forget update wiki, run_clang_format.py, and current new yaml which should format code automatically. Hope it will work now.


Replace all FreeSurfer calls with python

Feature Description
We call FreeSurfer binaries in a few places e.g. to binarize, map images, compute centroids of labels. All this can easily be implemented directly. We should drop FreeSurfer as a dependency as it is too large.
Maybe also some other dependencies can be dropped (transform3d) ?

The above freesurfer programs have been replaced by custom implementation or functions from e.g. the scipy package. Changes live now in the dev branch and have undergone initial testing. They will be subject to more comprehensive testing prior to release of version 2.0, and will eventually be merged into the stable branch, which is the future default branch.

This has been merged now, which closes the issue.


Add .stylelintrc and .clangd file type detection

This adds filetype detection for .stylelintrc and .clangd files.  Below are links to their docs if you are interested.

https://stylelint.io/user-guide/configure/
https://clangd.llvm.org/config#files

Please add entries in the filetype test: src/testdir/test_filetype.vim

Tests added