spark.write.geotiff round trip

I am looking into using the geotiff writer and I discovered the following. A test resource geotiff (COG) is read and then without modification written in the GeoTiffDataSourceSpec.  The  output of the writer is distorted... I'll provide links to previews of the images as well as the output that I get for reference.
The output tif is larger, as entire tiles are written. It has the same datatype and nodata value for each band.
The gdalinfo output for both is below. The writer outputs a file named example-geotiff.tiff
$ gdalinfo core/src/test/resources/LC08_RGB_Norfolk_COG.tiff
Driver: GTiff/GeoTIFF
Files: core/src/test/resources/LC08_RGB_Norfolk_COG.tiff
Size is 1028, 989
Coordinate System is:
PROJCS["WGS 84 / UTM zone 18N",
    GEOGCS["WGS 84",
        DATUM["WGS_1984",
            SPHEROID["WGS 84",6378137,298.257223563,
                AUTHORITY["EPSG","7030"]],
            AUTHORITY["EPSG","6326"]],
        PRIMEM["Greenwich",0,
            AUTHORITY["EPSG","8901"]],
        UNIT["degree",0.0174532925199433,
            AUTHORITY["EPSG","9122"]],
        AUTHORITY["EPSG","4326"]],
    PROJECTION["Transverse_Mercator"],
    PARAMETER["latitude_of_origin",0],
    PARAMETER["central_meridian",-75],
    PARAMETER["scale_factor",0.9996],
    PARAMETER["false_easting",500000],
    PARAMETER["false_northing",0],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]],
    AXIS["Easting",EAST],
    AXIS["Northing",NORTH],
    AUTHORITY["EPSG","32618"]]
Origin =<PHONE_NUMBER>00000000000,4109985.000000000000000)
Pixel Size = (30.000000000000000,-30.000000000000000)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  COMPRESSION=DEFLATE
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (  364455.000, 4109985.000) ( 76d31'33.12"W, 37d 7'35.07"N)
Lower Left  (  364455.000, 4080315.000) ( 76d31'13.92"W, 36d51'32.56"N)
Upper Right (  395295.000, 4109985.000) ( 76d10'43.57"W, 37d 7'49.33"N)
Lower Right (  395295.000, 4080315.000) ( 76d10'28.74"W, 36d51'46.68"N)
Center      (  379875.000, 4095150.000) ( 76d20'59.84"W, 36d59'41.37"N)
Band 1 Block=256x256 Type=UInt16, ColorInterp=Red
  NoData Value=0
  Overviews: 514x495, 257x248, 129x124, 65x62, 33x31
Band 2 Block=256x256 Type=UInt16, ColorInterp=Green
  NoData Value=0
  Overviews: 514x495, 257x248, 129x124, 65x62, 33x31
Band 3 Block=256x256 Type=UInt16, ColorInterp=Blue
  NoData Value=0
  Overviews: 514x495, 257x248, 129x124, 65x62, 33x31

$ gdalinfo example-geotiff.tiff
Warning 1: TIFFReadDirectory:Sum of Photometric type-related color channels and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels as ExtraSamples.
Driver: GTiff/GeoTIFF
Files: example-geotiff.tiff
Size is 1280, 1024
Coordinate System is:
PROJCS["WGS 84 / UTM zone 18N",
    GEOGCS["WGS 84",
        DATUM["WGS_1984",
            SPHEROID["WGS 84",6378137,298.257223563,
                AUTHORITY["EPSG","7030"]],
            AUTHORITY["EPSG","6326"]],
        PRIMEM["Greenwich",0,
            AUTHORITY["EPSG","8901"]],
        UNIT["degree",0.0174532925199433,
            AUTHORITY["EPSG","9122"]],
        AUTHORITY["EPSG","4326"]],
    PROJECTION["Transverse_Mercator"],
    PARAMETER["latitude_of_origin",0],
    PARAMETER["central_meridian",-75],
    PARAMETER["scale_factor",0.9996],
    PARAMETER["false_easting",500000],
    PARAMETER["false_northing",0],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]],
    AXIS["Easting",EAST],
    AXIS["Northing",NORTH],
    AUTHORITY["EPSG","32618"]]
Origin =<PHONE_NUMBER>00000000000,4109985.000000000000000)
Pixel Size = (24.093750000000000,-28.974609375000000)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (  364455.000, 4109985.000) ( 76d31'33.12"W, 37d 7'35.07"N)
Lower Left  (  364455.000, 4080315.000) ( 76d31'13.92"W, 36d51'32.56"N)
Upper Right (  395295.000, 4109985.000) ( 76d10'43.57"W, 37d 7'49.33"N)
Lower Right (  395295.000, 4080315.000) ( 76d10'28.74"W, 36d51'46.68"N)
Center      (  379875.000, 4095150.000) ( 76d20'59.84"W, 36d59'41.37"N)
Band 1 Block=1280x3 Type=UInt16, ColorInterp=Gray
  NoData Value=0
Band 2 Block=1280x3 Type=UInt16, ColorInterp=Undefined
  NoData Value=0
Band 3 Block=1280x3 Type=UInt16, ColorInterp=Undefined
  NoData Value=0

I'm looking around a little bit and I see for the RasterFrame that's read it has heterogenous tile sizes:
+--------+--------+-----+
|tileRows|tileCols|count|
+--------+--------+-----+
|221     |4       |1    |
|221     |256     |4    |
|256     |4       |3    |
|256     |256     |12   |
+--------+--------+-----+

When writing, the following is used to set the default full resolution output size.
https://github.com/locationtech/rasterframes/blob/develop/datasource/src/main/scala/astraea/spark/rasterframes/datasource/geotiff/DefaultSource.scala#L59-L60
Looking at the gdal info you can see that it must be 5 by 4 tiles, and tile size is 256 thus you get Size is 1280, 1024
So the tile layer metadata is not reliable in this case of heterogenous tile sizes. One could just enforce homogenous tile sizes on reading if the cell type has NoData. But that would not solve the general problem.
Related to #31 ??  Which seems to have the opposite problem that homogenous tile sizes with NoNoData cell type results in improper values.

I was able to get the output rows and columns from the RasterFrame itself but the output is still incorrect.  It is now the correct number of rows and columns, and the pixel size is correct.
However the distortion still remains and the image looks quite similar.
The problem seems to be that the tile layer metadata from the GeoTiffRelation is arguably incorrect and certainly inconsistent with the actual Tile locations. It has the Extent of the input geotiff as its Extent. But TileLayerMetadata does not really understand heterogenous tile sizes, so when we try to recover the location of the Tile bounds or centers, they will necessarily be equally spaced in the total number of columns and rows.  However the heterogenous tile sizes means they are not actually so, because the Extent does not consider that.
So this is realated to #31. The case where there is NoData we can safely expand the Extent to capture the "overlap" of the last column or row - either by making the Tiles all the same size, or by recalculating the bounds. In the NoNoData case it is still difficult to generalize.

FWIW, The file I downloaded from drive is not a COG. Does't mean there's not a bug, just that it's in a different part of the code.
$ validate_cloud_optimized_geotiff.py example-geotiff.tiff
example-geotiff.tiff is NOT a valid cloud optimized GeoTIFF.
The following errors were found:
 - The file is greater than 512xH or Wx512, but is not tiled
 - The file is greater than 512xH or Wx512, but has no overviews

Sorry, I was testing the wrong file. The test (input) file is a COG:
$ validate_cloud_optimized_geotiff.py LC08_RGB_Norfolk_COG.tiff
LC08_RGB_Norfolk_COG.tiff is a valid cloud optimized GeoTIFF

It was the file that RF wrote that was not a COG.

Currently seeing some distortion in output

Side by side:  https://cdn.knightlab.com/libs/juxtapose/latest/embed/index.html?uid=b56c070c-86be-11e8-b263-0edaf8f81e27

Thanks for the juxtapose view.... I never would have picked up on that.

@vpipkt If you had to guess, do you think this is a read-side error or a write side error?

I would say write side
On Sun, Jul 15, 2018, 10:08 Simeon H.K. Fitch<EMAIL_ADDRESS>wrote:

@vpipkt https://github.com/vpipkt If you had to guess, do you think
this is a read-side error or a write side error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/locationtech/rasterframes/issues/68#issuecomment-405094527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHb-L0mM6rJB9GVXw-ki4lo1iM7kjPO9ks5uG0zNgaJpZM4VH4-g
.

@metasim can you re-open this issue?

This is being picked up by https://github.com/locationtech/rasterframes/pull/231


Connection to the database fails in production

In the Log: MySQLdb._exceptions.OperationalError: (1045, "Access denied for user 'X'@'Y' (using password: YES)")

The problem was that the db-configuration was mounted to the wrong location inside the pod due to the refactoring "tira-application" => "application"


Changes to allow mocked builds

Thank you a lot for contributing to Cosmos Voyager!

Here are the changes I needed to be able to make our mocked release build. It adds a mocked option in config.toml which disables the LCD and enables the mock renderer connector.
Issue

closes: ISSUE
Screenshots

❤ Thank you!

Attempting to make a build with this branch
yarn build --gaia=~/gaia/gaia_mac_decb23bed0179244e4f42d697dcd4bf759200a2d  --platform=darwin --network=app/networks/mock

I run into errors though:
Wed Jan 31 2018 14:42:18 GMT+0800 (+08) Running Cosmos-UI
main-process: initializing data directory (/Users/pz/.Cosmos)
main-process: mainWindow opened
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: Initializing baseserver with remote node <IP_ADDRESS>:46657
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""client" "init" "--home" "/Users/pz/.Cosmos/baseserver" "--chain-id" "gaia-2" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: Loading validator set from tendermint rpc...

main-process: gaia:
Important: if this is incorrect, all interaction with the chain will be insecure!
  Given validator hash valid: 007859825B35B26F1942909D249FA6A6BF5FD363
Is this valid (y/n)?

main-process: approving hash 007859825B35B26F1942909D249FA6A6BF5FD363
main-process: gaia exited with code 0
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia: 2018/01/31 14:42:19 Serving on ":9071"

Wed Jan 31 2018 14:43:15 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:43:15 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 14:44:21 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:44:21 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 14:46:07 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:46:07 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 14:51:56 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:51:56 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 14:56:22 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:56:23 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 14:57:51 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Downloads/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Downloads/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Downloads/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 14:57:51 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 15:13:30 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 15:13:30 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Wed Jan 31 2018 15:20:49 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/01/31 15:20:49 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Thu Feb 01 2018 01:21:08 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64_0.4.0/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/02/01 01:21:08 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Thu Feb 01 2018 10:59:14 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/02/01 10:59:14 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Thu Feb 01 2018 11:01:18 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/02/01 11:01:18 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Thu Feb 01 2018 11:01:33 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/02/01 11:01:33 Serving on ":9071"

main-process: gaia server ready
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: 11:05:48 AM <IP_ADDRESS>:46657 is down
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: 11:05:50 AM <IP_ADDRESS>:46657 is alive
main-process: quitting running baseserver
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code null
main-process: gaia: 2018/02/01 11:05:50 Serving on ":9071"

main-process: gaia server ready
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: 11:05:51 AM <IP_ADDRESS>:46657 is alive
main-process: quitting running baseserver
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Users/pz/Projects/cosmos-ui/builds/Cosmos-darwin-x64/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code null
main-process: gaia: 2018/02/01 11:05:51 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver
Thu Feb 01 2018 11:12:11 GMT+0800 (+08) Running Cosmos-UI
main-process: root exists (/Users/pz/.Cosmos)
main-process: configs are compatible with current app version
main-process: starting app
main-process: dev mode: false
main-process: winURL: file:///Applications/Cosmos.app/Contents/Resources/app/dist/index.html
main-process: spawning /Applications/Cosmos.app/Contents/Resources/app/bin/gaia with args ""version""
main-process: gaia: v0.5.0

main-process: gaia version: "v0.5.0", expected: "v0.5.0"
main-process: Picked seed: <IP_ADDRESS>:46656 of <IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656,<IP_ADDRESS>:46656
main-process: starting gaia server with nodeIP <IP_ADDRESS>:46657
main-process: startBaseserver /Users/pz/.Cosmos/baseserver
main-process: spawning /Applications/Cosmos.app/Contents/Resources/app/bin/gaia with args ""rest-server" "--port" 9071 "--home" "/Users/pz/.Cosmos/baseserver" "--node" "<IP_ADDRESS>:46657""
main-process: gaia exited with code 0
main-process: gaia: 2018/02/01 11:12:11 Serving on ":9071"

main-process: gaia server ready
main-process: killing baseserver

I think we still want to merge this, but we want to turn off some of the switches. Namely set mocked = false, re-enable the develop-only flag for the staking and proposal pages, etc.

I'll work on getting this into a merge-eable state.


CSS heart beating animation

Describe the project you want to add with tech stack

Expected behavior

Screenshots (optional)

Additional context (optional )

@pranjay-poddar  Pls assign me this issue I wanted to work on this

@pranjay-poddar plz assign me this issue  i like to work

@pranjay-poddar  thanks for assigning me this issue , I wanted to ask that if this issue is labelled to HSCO and level of the Issue is mentioned or not

@pranjay-poddar  thanks for the PR, I think we can Close this Issue for Better Workflow of the Repository as the PR is merged
What do you think!!!!!


fix: Fix enableTelemetry apiVersion and ARM template

Reason for Change:

Specifying feature flag enableTelemetry: True would cause the ARM template deployment to fail. This PR bumps the api version and removes the DeploymentARMResource alias to fix the issue.
Issue Fixed:

Credit Where Due:
Does this change contain code from or inspired by another project?

[x] No
[ ] Yes

If "Yes," did you notify that project's maintainers and provide attribution?

[ ] No
[ ] Yes

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Notes:

Verified successful run with ADO PR E2E pipeline


YARN-10549. Decouple RM runner logic from SLSRunner

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 18s

trunk passed

+1 :green_heart:
compile
0m 32s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 26s

trunk passed

+1 :green_heart:
mvnsite
0m 33s

trunk passed

+1 :green_heart:
javadoc
0m 31s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
0m 52s
/branch-spotbugs-hadoop-tools_hadoop-sls-warnings.html
hadoop-tools/hadoop-sls in trunk has 2 extant spotbugs warnings.

+1 :green_heart:
shadedclient
20m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 24s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
compile
0m 20s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 20s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 24s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
0m 51s

the patch passed

+1 :green_heart:
shadedclient
20m 12s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m 16s
/patch-unit-hadoop-tools_hadoop-sls.txt
hadoop-sls in the patch passed.

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

84m 13s

Reason
Tests

Failed junit tests
hadoop.yarn.sls.TestReservationSystemInvariants

hadoop.yarn.sls.TestSLSDagAMSimulator

hadoop.yarn.sls.TestSLSStreamAMSynth

hadoop.yarn.sls.TestSLSRunner

hadoop.yarn.sls.TestSLSGenericSynth

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4113

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f988e313597e 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ad9f50f5209642a31015c4f0cff32e8b3d27bb8b

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/1/testReport/

Max. process+thread count
545 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-sls U: hadoop-tools/hadoop-sls

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 36s

trunk passed

+1 :green_heart:
compile
0m 32s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 26s

trunk passed

+1 :green_heart:
mvnsite
0m 33s

trunk passed

+1 :green_heart:
javadoc
0m 31s

trunk passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
0m 52s
/branch-spotbugs-hadoop-tools_hadoop-sls-warnings.html
hadoop-tools/hadoop-sls in trunk has 2 extant spotbugs warnings.

+1 :green_heart:
shadedclient
20m 26s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 23s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
compile
0m 20s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 20s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 15s

the patch passed

+1 :green_heart:
mvnsite
0m 23s

the patch passed

+1 :green_heart:
javadoc
0m 22s

the patch passed with JDK Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 19s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
0m 53s

the patch passed

+1 :green_heart:
shadedclient
19m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
12m 10s

hadoop-sls in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

96m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4113

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 3fe77f0e5035 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9b95715a0f6be4ea47e2c8bf38cf930de7dabedb

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.14+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/2/testReport/

Max. process+thread count
543 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-sls U: hadoop-tools/hadoop-sls

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4113/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks for the change @szilard-nemeth and the review @brumi1024 it looks good to me. Spotbugs errors will be fixed in the followups and I have fixed the whitespace error before committing to trunk.


Obsolete property

WindowsAzureActiveDirectoryBearerAuthenticationOptions.Audience is obsolete, use WindowsAzureActiveDirectoryBearerAuthenticationOptions.TokenValidationParameters instead.

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

ID: 1d91e987-b3aa-d12b-6400-5f477e827202
Version Independent ID: e0efa72d-1e7c-b2d2-4ad9-ad51334e3da6
Content: Build a .NET web API that integrates with Azure AD for authentication and authorization
Content Source: articles/active-directory/develop/quickstart-v1-dotnet-webapi.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

@ktilk Thanks for your feedback! We will investigate and update as appropriate.

@ktilk Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

Step 3 -
4. From the Settings page, select Required Permissions, and then select Add. Locate and select the To Do List Service, add the Access TodoListService permission under Delegated Permissions, and then select Done.
The To Do List Service is greyed out and cannot be selected. How do I fix this?

Hi Team,
I have followed all the instructions that are stated. After I login with my credentials it gives back an Unauthorized access error.

Getting unauthorized access after successfully running the code.

Please reassign the issue to @jmprieur to evaluate if the archived v1 sample will be updated.

Did anyone ever figure out the Step 3 issue that Ghander and Gavimoss had?  I'm running into the same thing, and I don't see any follow-ups here.  Ghander or Gavimoss, did either of you have luck figuring this out?

@russwilsonii: We are going to update the steps with the new portal experience soon
Meanwhile:

if you want to use Azure AD v1.0, I'd advise you rather look at the README.md of the following (more recent) sample: https://github.com/azure-samples/active-directory-dotnet-native-desktop
but if you are open to using the Microsoft Identity Platform v2.0, I'd recommend you have a look to the following sample, which is even more recent and better: https://github.com/Azure-Samples/active-directory-dotnet-native-aspnetcore-v2

BTW, I proposed a PR to fix the original issue #28539

cc: @CelesteDG

#please-close

Microsoft - stop posting shit that is outdated or doesn't work.
Thanks,

A Progammer


Start FAQ Page, Mostly with EV Questions

Overview
Adds an FAQ page and links it in the header - this page answers a lot of the common questions I have gotten particularly about electric vehicles, and I plan on adding more info about renewable energy.
Starts on issue #30 but doesn't close it out yet. I'm opening this PR now since there's already a lot of text that might take us some time to discuss, but I think this starter FAQ is better than not having one.
Demo
Check out the Netlify - this is mostly a giant text page
Notes
Optional. Ancillary topics, caveats, alternative strategies that didn't work out, anything else.
Testing Instructions

Load the Netlify and confirm you can go to /faq from the header
Confirm the page is readable on desktop and mobile
Actually read all the text.

@derekeder - I responded to your feedback but I'm not at home to run the yarn format command. Do you mind running that on this branch and pushing it up?


cereal could not find any output serialization functions for the provided type and archive combination.

i don't get why i have this error, because i have a  serialize function in both my classes.
class A: public std::enable_shared_from_this<A> {
  public:
	std::string __class__;
	int  __classid__;
	bool __initialized__;
	std::shared_ptr<std::vector<int>>  y;
	std::shared_ptr<std::vector<int>>  x;
	std::shared_ptr<std::vector<std::shared_ptr<A>>>  children;
	template <class Archive>
	void serialize( Archive & ar ) {
		ar(y,x,children);
	}
	A* __init__(std::shared_ptr<std::vector<int>> x, std::shared_ptr<std::vector<int>> y);
	void foo(int start, int end);
	void bar(int start, int end);
	bool operator != (std::nullptr_t rhs) {return __initialized__;}
	bool operator == (std::nullptr_t rhs) {return !__initialized__;}
	A() {__class__ = std::string("A"); __initialized__ = true; __classid__=0;}
	A(bool init) {__class__ = std::string("A"); __initialized__ = init; __classid__=0;}
	std::string getclassname() {return this->__class__;}
};

class Container: public std::enable_shared_from_this<Container> {
  public:
	std::string __class__;
	int  __classid__;
	bool __initialized__;
	std::shared_ptr<std::vector<std::shared_ptr<std::vector<std::shared_ptr<A>>>>>  lst;
	template <class Archive>
	void serialize( Archive & ar ) {
		ar(lst);
	}
	Container* __init__(std::shared_ptr<std::vector<std::shared_ptr<std::vector<std::shared_ptr<A>>>>> lst);
	bool operator != (std::nullptr_t rhs) {return __initialized__;}
	bool operator == (std::nullptr_t rhs) {return !__initialized__;}
	Container() {__class__ = std::string("Container"); __initialized__ = true; __classid__=1;}
	Container(bool init) {__class__ = std::string("Container"); __initialized__ = init; __classid__=1;}
	std::string getclassname() {return this->__class__;}
};

main code

int main() {
	auto t = __clock__();
	/* lst = vector of vectors to: std::shared_ptr<A> */
	auto lst = std::make_shared<std::vector<std::shared_ptr<std::vector<std::shared_ptr<A>>>>>(std::vector<std::shared_ptr<std::vector<std::shared_ptr<A>>>>{});
	for (int i=0; i<100; i++) {
		std::vector<std::shared_ptr<A>> _comp_objs; /*comprehension*/
		for (int i=0; i<150; i++) {
			_comp_objs.push_back(make_A(i, (i * 10)));
		}
		auto objs = std::make_shared<std::vector<std::shared_ptr<A>>>(_comp_objs);
		lst->push_back(objs);
		for (auto &o: (*objs)) { /*loop over heap vector: A*/
			for (auto &oo: (*objs)) { /*loop over heap vector: A*/
				if (( o != oo )) {
					o->children->push_back(oo);
				}
			}
		}
	}
	std::ofstream os("/tmp/out.cereal", std::ios::binary);
	cereal::BinaryOutputArchive archive( os );
	auto con = [&](){auto _ = std::shared_ptr<Container>(new Container()); _->__init__(lst); return _;}();
	archive((*con));
	std::cout << (__clock__() - t) << std::endl;
	return 0;
}

It appears that you're attempting to serialize a shared_ptr.  If you aren't including the cereal/types/memory.hpp header, there won't be a serializer for that.

i already am including memory.hpp, here's what i'm including from ceral
#include <cereal/cereal.hpp>
#include <cereal/types/memory.hpp>
#include <cereal/types/base_class.hpp>
#include <cereal/archives/binary.hpp>

What about cereal/types/vector.hpp?  It seems the 'lst' variable being serialized has a vector, so that include is needed before the first file.
If that doesn't work, please share the entire error message including all the template errors.  They are equally as useful to read.  Additionally, a much simplified version of the code to reproduce this would also be helpful.

thanks, including #include <cereal/types/vector.hpp> fixed my problem.
i guess it might help to update the docs that for each standard container type, you need to include it from cereal/types


Limit type visibility

The mere presence of a type in a project should not expose that type to every file i.e. types should not be global.
Luanalysis should (recursively) pull in types when it sees a require. Additionally, we should provide some mechanism to allow consumers to avoid type name collisions.
e.g.
local Map = require("Map")
local LibraryMap = require("library/Map") ---@prefix Library

---@type Map
local myMap = Map()

---@type LibraryMap
local libraryMap = LibraryMap()

Just a hypothetical solution, other languages allow individual types to be renamed. The above is fairly low friction though.
Additionally, we may want to define types that we never export to consumers i.e. consider adding local types like:
---@local alias Builder fun(): void

If this was to go ahead, we'd also need something like:
---@require "some-userdata-type"
---@require "some-legacy-global"

To ensure that types that are available globally in a Lua context (not required) can be utilised.
Could see this becoming cumbersome in some environments though, so would be wise to offer some mechanism to import types project wide as well.


Failed to build OpenSSL on NDK

Hunter failed to build OpenSSL on NDK (r18).
  [hunter ** FATAL ERROR **] Build step failed (dir: /Users/usrn/.hunter/_Base/b732407/4e02b95/527d8b0/Build/OpenSSL
  [hunter ** FATAL ERROR **] [Directory:/Users/usrn/.hunter/_Base/Download/Hunter/0.23.11/b732407/Unpacked/cmake/projects/OpenSSL]
  ------------------------------ WIKI -------------------------------
      https://github.com/ruslo/hunter/wiki/error.external.build.failed
  -------------------------------------------------------------------
  CMake Error at /Users/usrn/.hunter/_Base/Download/Hunter/0.23.11/b732407/Unpacked/cmake/modules/hunter_wiki.cmake:12 (message):
  Call Stack (most recent call first):
    /Users/usrn/.hunter/_Base/Download/Hunter/0.23.11/b732407/Unpacked/cmake/modules/hunter_fatal_error.cmake:20 (hunter_wiki)

Then I tried to run cmake --build Build/ and got something like this:
    LD_LIBRARY_PATH=.: /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_DYNAMIC_ENGINE -DOPENSSL_PIC -DOPENSSLDIR="/Users/usrn/.hunter/_Base/b732407/4e02b95/527d8b0/Build/OpenSSL/Install/ssl" -DENGINESDIR="/Users/usrn/.hunter/_Base/b732407/4e02b95/527d8b0/Build/OpenSSL/Install/lib/engines-1.1" -Wall -O3 -pthread -isystem /Users/usrn/Library/Android/sdk/ndk-bundle/sysroot/usr/include/aarch64-linux-android -g -DANDROID -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -Wa,--noexecstack -Wformat -Werror=format-security --sysroot=ccc -isystem /Users/usrn/Library/Android/sdk/ndk-bundle/sysroot/usr/include -isystem /Users/usrn/Library/Android/sdk/ndk-bundle/sysroot/usr/include/aarch64-linux-android --target=aarch64-none-linux-android24 --gcc-toolchain=/Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64 -fPIC -o apps/openssl apps/app_rand.o apps/apps.o apps/asn1pars.o apps/ca.o apps/ciphers.o apps/cms.o apps/crl.o apps/crl2p7.o apps/dgst.o apps/dhparam.o apps/dsa.o apps/dsaparam.o apps/ec.o apps/ecparam.o apps/enc.o apps/engine.o apps/errstr.o apps/gendsa.o apps/genpkey.o apps/genrsa.o apps/nseq.o apps/ocsp.o apps/openssl.o apps/opt.o apps/passwd.o apps/pkcs12.o apps/pkcs7.o apps/pkcs8.o apps/pkey.o apps/pkeyparam.o apps/pkeyutl.o apps/prime.o apps/rand.o apps/rehash.o apps/req.o apps/rsa.o apps/rsautl.o apps/s_cb.o apps/s_client.o apps/s_server.o apps/s_socket.o apps/s_time.o apps/sess_id.o apps/smime.o apps/speed.o apps/spkac.o apps/srp.o apps/ts.o apps/verify.o apps/version.o apps/x509.o -L. -lssl -L. -lcrypto -ldl -pthread -latomic --sysroot=/Users/usrn/Library/Android/sdk/ndk-bundle/sysroot
    clang: warning: argument unused during compilation: '-Wa,--noexecstack' [-Wunused-command-line-argument]
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find crtbegin_dynamic.o: No such file or directory
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -ldl
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -ldl
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -lc
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find -ldl
    /Users/usrn/Library/Android/sdk/ndk-bundle/toolchains/aarch64-linux-android-4.9/prebuilt/darwin-x86_64/lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld: cannot find crtend_android.o: No such file or directory
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

According the experience of fixing libxml on NDK (https://github.com/hunter-packages/libxml2/issues/2). I'm sure the --sysroot is wrong again.
Then I tried to print CMAKE_SYSROOT and CMAKE_SYSROOT_COMPILE. Both points to the same "/Users/usrn/Library/Android/sdk/ndk-bundle/sysroot", and that's wrong. It should be something like "/Users/usrn/Library/Android/sdk/ndk-bundle/platforms/android-24/arch-arm64".
The last --sysroot in the last executed command comes from the EX_LIBS variable defined in Makefile.
    ....
    PLIB_LDFLAGS=
    EX_LIBS= -ldl -pthread -latomic --sysroot=/Users/usrn/Library/Android/sdk/ndk-bundle/sysroot
    LIB_CFLAGS=-fPIC -DOPENSSL_USE_NODELETE
    ....

However, it seems the wrong --sysroot doesn't come from hunter. Because I tried set all --sysroot to something else in hunter_dump_cmake_flags.cmake. And the EX_LIBS never changes.
I also tried to change the --sysroot value to "/Users/usrn/Library/Android/sdk/ndk-bundle/platforms/android-24/arch-arm64" (in EX_LIBS) and executed make manually, and it passed the building process.
So the question is, how can I fix hunter to set the --sysroot value correctly? Thanks.

Both points to the same "/Users/usrn/Library/Android/sdk/ndk-bundle/sysroot", and that's wrong. It should be something like "/Users/usrn/Library/Android/sdk/ndk-bundle/platforms/android-24/arch-arm64"

Are you using CMake-based NDK toolchain or Android Studio toolchain? According to this comment the sysroot value you're looking for is in CMAKE_EXE_LINKER_FLAGS variable:

https://github.com/hunter-packages/libxml2/issues/2#issuecomment-410318743

So the question is, how can I fix hunter to set the --sysroot value correctly? Thanks

OpenSSL use custom build scheme, so the first question is how OpenSSL should be build with NDK r18.

Not sure where to pass the --sysroot parameter to configure in hunter

OpenSSL build schemes:

https://github.com/ruslo/hunter/blob/305e1831180a1f80128c5f0e9a0e10b8b928342b/cmake/projects/OpenSSL/hunter.cmake#L387-L403

CMAKE_EXE_LINKER_FLAGS will be available after this command:

https://github.com/ruslo/hunter/blob/305e1831180a1f80128c5f0e9a0e10b8b928342b/cmake/projects/OpenSSL/schemes/url_sha1_openssl.cmake.in#L58-L60

See:

https://github.com/ruslo/hunter/blob/305e1831180a1f80128c5f0e9a0e10b8b928342b/cmake/modules/hunter_dump_cmake_flags.cmake#L62-L75

@ruslo  Thanks for the tips. I can make it work now by replace
https://github.com/ruslo/hunter/blob/305e1831180a1f80128c5f0e9a0e10b8b928342b/cmake/projects/OpenSSL/schemes/url_sha1_openssl.cmake.in#L104
to
STRING(REGEX REPLACE ".*[ ]--sysroot[ ]([A-Za-z0-9/-]+)[ ]?.*" "\\1"
       SYSROOT ${CMAKE_EXE_LINKER_FLAGS})
if (${SYSROOT} STREQUAL ${CMAKE_EXE_LINKER_FLAGS})
  set(SYSROOT ${CMAKE_SYSROOT})
endif()
list(APPEND configure_opts "-latomic --sysroot=${SYSROOT}")

Basically I tried to extract the sysroot from  CMAKE_EXE_LINKER_FLAGS and fallback to CMAKE_SYSROOT if failed. Is that ok to submit a PR?

@ruslo Just tried. It's working, too.
list(APPEND configure_opts "-latomic ${CMAKE_EXE_LINKER_FLAGS}")

Since the fix is quite simple, I think it's faster for you to fix it instead of a PR. What do you think?

Since the fix is quite simple, I think it's faster for you to fix it instead of a PR. What do you think?

Don't see the difference, I will run all tests anyway.

BTW, I tested the modified code by running
cmake --build app/.externalNativeBuild/cmake/debug/arm64-v8a

So Android Studio won't overwrite the scheme file.

This is how I added OpenSSL
hunter_add_package(OpenSSL)
find_package(OpenSSL REQUIRED)
target_link_libraries(moui-app PRIVATE OpenSSL::SSL OpenSSL::Crypto)

Fix available in  https://github.com/ruslo/hunter/releases/tag/v0.23.25

Works perfectly. Thanks.


Use 'debug' level logging on Windows when user chooses "debug"

Currently, we use "Trace" level and this is simply too much.

Resolved in adguard-windows/pull-requests/307


Added Taxi Fare Calculator

Fixes Issue🛠

Closes #399
Description👨💻

Calculates the cost of taxi ride based on distance, base fare and time.
Type of change📄

[X] New feature (non-breaking change which adds functionality)

How this has been tested✅

This has been tested on local machine and works perfect.
Checklist✅

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have added demonstration in the form of GIF/video file
[X] I am an Open Source Contributor

Screenshots/GIF📷

Merged!! Congrats on getting your PR merged to this repo under IWOC 2.0 🎉🎉 @Abidsyed25


Render current version in dashboard footer

I always found this a helpful way to know what version I'm looking at. Right now the site is auto-deploying from main, but there's no real indication that anything's changed.

Closed by a4f0617e3db05262ef7913ba816de72a51753a3f


Warn on "bad behavior" when using configure-on-demand

There are some rules that builds need to follow to be able to safely use configure on demand.  Many builds probably don't realize they violate our assumptions.
Given this build:
./a/build.gradle
sourceSets.main.output.dir 'anotherDir'

./b/build.gradle
task broken {
   inputs.files project(":a").sourceSets.main.output
   doLast {
      assert inputs.files.files.find { it.absolutePath.contains("anotherDir") }
   }
}

./build.gradle
subprojects {
   apply plugin: 'java'
}

./settings.gradle
include 'a', 'b'

Running gradle :b:broken -Dorg.gradle.configureondemand=true fails the build when configure-on-demand is enabled.
gradle :b:broken works.
Expected Behavior
Gradle should warn when a build author has done something that's likely broken/wrong with configure-on-demand enabled.
Current Behavior
The Gradle build may or may not work depending on how the build is executed.
One big problem with this is the use of allprojects{} and subprojects{} mostly negates the benefits of using configure on demand since we need to partially configure all the subprojects.  But ignoring that, this build fails when org.gradle.configureondemand=true because there's a  dependency between a and b that requires a to be fully configured.  The b project "reaches into" project a and grabs the output directory for the main source set.  Without configure-on-demand, this works because the source set output is a "live" collection and a would be fully configured.
Context
I just helped diagnose problems with a build that had several references similar to this and configure-on-demand enabled.
The appropriate way to handle this is to use a project dependency between the two projects. That would allow Gradle to see the dependencies and fully configure project a.
To avoid surprises for other builds, I think if we separated the ProjectFinder-like parts of DefaultProject into a separate service that could be injected into the project, we could emit a warning whenever Project.project(...) is called with configure-on-demand enabled without affecting DependencyHandler.project(...) (which is OK to call).  There might be other things we could do to tell that "half-configured" projects were used and fail the build.
Steps to Reproduce (for bugs)
See example above.

We need to discourage users from reaching into sibling projects in general. The above example is a special case that works without configure-on-demand, but most cases of reaching into sibling projects will break no matter if configure-on-demand is used or not.


XAPK Downloaded, But Output Says It Did Not

I get a perfectly downloaded .xapk file, however the output from the console stated it could not save it.
Waiting...
Downloading co.[redacted].app...
Could not save co.[redacted].app...

Fixed the underlying issue.  Thanks!


Add Tomcat Native Libraries

Closes #19
Closes #23

This isn't ready yet:
22-Apr-2016 20:32:36.114 SEVERE [main] org.apache.catalina.core.AprLifecycleListener.init An incompatible version 1.1.34 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.2.2

Trying to figure out a good way to verify that it actually worked so we can have the build fail (or write a test to verify that it's functioning properly).

I've got my fingers crossed -- just pushed an update that should give us some success here.

(Travis was all green, but https://github.com/docker-library/official-images/pull/1656 exists now, so I've restarted them :tada:)

LGTM


feat: Restoring most recently closed tabs (#400)

Happy Hacktoberfest!
I love the look of this code editor and wanted to contribute in my own small way. I arbitrarily set the cache maximum to ten so it doesn't start filling up profusely over long periods of development. If that's not necessary, I don't mind revising it at all!

Happy hacktoberfest
Everything looks good to me! thank you for contributing ❤
The cache maximum is a good addition as well, will add that param to the editor config later...


Add live demo section to gh-pages

The landing page should be served over planktos if the browser supports it. Also a live demo section should be added that informs the viewer that the page was downloaded from peers.

Also, some crash reporting should be added

This should be moved to high priority in alpha.


BNGetTypeReferenceId returning incorrect reference for type with definitions from debuginfo and platform types

Version and Platform (required):

Binary Ninja Version: 4.1.4959-dev, 9475ceaa
OS: macos
OS Version: 14.4
CPU Architecture: arm64

Bug Description:
Using NamedTypeReferenceType.target(bv) fails to get a reference to the correct type.
Steps To Reproduce:

Have a type that is defined in both the platform types and the debug information. (platform.windows-kernel-x86_64 has multiple placeholder types such as _EPROCESS. The imported PDB will cause a _EPROCESS_1 to be defined.)
Attempt to follow the target of a NamedTypeReferenceType that should reference a type from the debug information that is renamed with _1 using the .target(bv) method.
See that the returned type is not the correct type.

Expected Behavior:
When a NamedTypeReferenceType's name is '_ETHREAD_1' I would expect the .target(bv) method to return the type object for _ETHREAD_1, instead of _ETHREAD.
Screenshots:
A console session showing the incorrect behavior:
>>> e1 = bv.get_type_by_name('_EPROCESS_1')
>>> e1
<type: immutable:StructureTypeClass 'struct _EPROCESS_1'>
>>> e1.members[18]
<struct _ETHREAD_1* RotateInProgress, offset 0x4d8>
>>> e1.members[18].type
<type: immutable:PointerTypeClass 'struct _ETHREAD_1*'>
>>> e1.members[18].type.target
<type: immutable:NamedTypeReferenceClass 'struct _ETHREAD_1'>
>>> e1.members[18].type.target.target(bv)
<type: immutable:StructureTypeClass 'struct _ETHREAD'>
# The above returned type is not the _ETHREAD_1 Type

>>> e1.children[18].children[0].target(bv)
<type: immutable:StructureTypeClass 'struct _ETHREAD'>
>>> e1.children[18].children[0].name
'_ETHREAD_1'
# The above name is the correct name, but the type returned from target is _ETHREAD not _ETHREAD_1

>>> e1.children[18].children[0].type_id
'platform.windows-kernel-x86_64:["_ETHREAD"]'
# The above type_id is not the type_id that is expected. The _ETHREAD_1 should be from the debuginfo

>>> bv.get_type_by_name('_ETHREAD_1').width
2200
>>> e1.children[18].children[0].target(bv).width
1
>>> bv.get_type_by_name('_ETHREAD').width
1

A console session showing that target does not work when working directly on a type from debuginfo:
>>> dbge1 = bv.debug_info.get_type_by_name('PDB', '_EPROCESS')
...
>>> dbge1
<type: immutable:StructureTypeClass 'struct'>
>>> dbge1.children[18].children[0]
<type: immutable:NamedTypeReferenceClass 'struct _ETHREAD'>
>>> dbge1.children[18].children[0].target(bv) == None
True

Additional Information:
A workaround is to use bv.get_type_by_name or bv.debug_info.get_types_by_name with the name, instead of using .target(bv) on a NamedTypeReferenceType
https://github.com/Vector35/binaryninja-api/issues/5083
The above issue is related.

Can confirm. It looks like, when a PDB is imported, while references to types are renamed to deconflict (that's where all the _1 comes from) they don't have their ids remapped too.


Maximum call stack size exceeded when defining too many fields

Bug description
I am currently developing a relatively intricate object using Prisma and integrating it with SQL (Postgres). The table I'm working with is quite complex, and I've been adding fields dynamically as per the requirements.
After investigating, I have identified that the issue stems from adding new records. I'm curious to know if there is a limitation on the number of fields I can have in a model.
   const res = await this.prisma.property.create({       data: {         ...propertyReformulated,       },     });
the stack i am workin on is Postgress Prisma NestJs
what i get after runing my Nest application using NestJs  with npm run start:dev
i am getting Maximum call stack size exceeded

How to reproduce

Expected behavior
No error
Prisma information

model Property {
  id                      String                    @id
  type                    PropertyType
  size                    Int
  images                  String[]
  furnished               Boolean
  numberOfPeepleSutbleFor Int
  houseMate               Gender[]
  flexibleCancellation    Boolean
  discription             String
  rules                   String[]
  livingRoom              state
  toilet                  state
  kitchen                 state
  kitchenware             state
  bathroom                state
  basement                state
  balcony                 state
  parking                 Boolean
  garden                  state
  wifi                    Boolean
  bed                     Boolean
  TV                      Boolean
  badroomLock             Boolean
  closet                  Boolean
  desk                    state
  dishwasher              Boolean
  acsessFrindly           Boolean
  houseRules              String
  agePrefrenceMin         Int
  agePrefrenceMax         Int
  genderPrefrence         Gender
  tenantType              TenantType[]
  suitableForCouples      Boolean
  documentsRequiredToBook DocumentsRequiredToBook[]
  minimunStay             Int
  deposits                Int
  electricity             Int
  water                   Int
  gas                     Int
  internet                Int
  broadcastingFee         Int
  cancellation            String[]
  administrationFee       Int
  estimatedBills          Int

  bedroms                   Int
  bedroomLock               Boolean
  centralHeating            Boolean
  flooring                  String?
  livingRoomFurniture       Boolean
  airConditioning           Boolean
  washingMachine            Boolean
  dryer                     Boolean
  playingMusicalInstruments Boolean
  pets                      Boolean
  smoking                   Boolean
  rentAmount                Int
}

enum DocumentsRequiredToBook {
  ProofOfIdentity
  ProofOfEnrolment
  ProofOfOccupation
  ProofOfIncome
}

enum TenantType {
  Students
  Working_Professionals
}

enum state {
  Privet
  Shaerd
  None
}

enum PropertyType {
  Room
  Apartment
  Studio
  House
}

export type Property = {
  id: string
  type: PropertyType
  size: number
  images: string[]
  furnished: boolean
  numberOfPeepleSutbleFor: number
  houseMate: Gender[]
  flexibleCancellation: boolean
  discription: string
  rules: string[]
  livingRoom: state
  toilet: state
  kitchen: state
  kitchenware: state
  bathroom: state
  basement: state
  balcony: state
  parking: boolean
  garden: state
  wifi: boolean
  bed: boolean
  TV: boolean
  badroomLock: boolean
  closet: boolean
  desk: state
  dishwasher: boolean
  acsessFrindly: boolean
  houseRules: string
  agePrefrenceMin: number
  agePrefrenceMax: number
  genderPrefrence: Gender
  tenantType: TenantType[]
  suitableForCouples: boolean
  documentsRequiredToBook: DocumentsRequiredToBook[]
  minimunStay: number
  deposits: number
  electricity: number
  water: number
  gas: number
  internet: number
  broadcastingFee: number
  cancellation: string[]
  administrationFee: number
  estimatedBills: number
  bedroms: number
  bedroomLock: boolean
  centralHeating: boolean
  flooring: string | null
  livingRoomFurniture: boolean
  airConditioning: boolean
  washingMachine: boolean
  dryer: boolean
  playingMusicalInstruments: boolean
  pets: boolean
  smoking: boolean
  rentAmount: number
}

/**
 * Enums
 */

export const DocumentsRequiredToBook: {
  ProofOfIdentity: 'ProofOfIdentity',
  ProofOfEnrolment: 'ProofOfEnrolment',
  ProofOfOccupation: 'ProofOfOccupation',
  ProofOfIncome: 'ProofOfIncome'
};

export type DocumentsRequiredToBook = (typeof DocumentsRequiredToBook)[keyof typeof DocumentsRequiredToBook]

export const Gender: {
  Male: 'Male',
  Female: 'Female',
  ND: 'ND'
};

export type Gender = (typeof Gender)[keyof typeof Gender]

export const PropertyType: {
  Room: 'Room',
  Apartment: 'Apartment',
  Studio: 'Studio',
  House: 'House'
};

export type PropertyType = (typeof PropertyType)[keyof typeof PropertyType]

export const TenantType: {
  Students: 'Students',
  Working_Professionals: 'Working_Professionals'
};

export type TenantType = (typeof TenantType)[keyof typeof TenantType]

export const state: {
  Privet: 'Privet',
  Shaerd: 'Shaerd',
  None: 'None'
};

export type state = (typeof state)[keyof typeof state]

Environment & setup

OS:
Database:
Node.js version:

Prisma Version
prisma                  : 4.15.0
@prisma/client          : 4.15.0
Current platform        : debian-openssl-3.0.x
Query Engine (Node-API) : libquery-engine 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.15.0-28.8fbc245156db7124f997f4cecdd8d1219e360944
Studio                  : 0.484.0

Can you please share the full error message you are getting?
Did I understand that you get this error message when you try to start your application via npm run start:dev?
What typescript version is your project using? Does it work if you downgrade to the previous minor version (e.g. from 5.1.x to 5.0.x)?

Thanks. Can you still take a look at my original questions?
https://github.com/prisma/prisma/issues/19774#issuecomment-1592721811

Hi @ibrahimgb, could you please share the full error message you are getting, and reply with more information to this comment? Thank you.

Hi @ibrahimgb, any chance you could reply with more info, as asked above? Thank you!

Hey @ibrahimgb, we're closing this issue for unresponsiveness, as we cannot proceed further with the information currently available. Should be able to collect and provide the information requested in previous messages, please leave a comment, and we will gladly re-open this issue :)


Replace .catch with ['catch'] for IE9 Support

@pornel Is it possible to merge this? the ['catch'] is forward compatible! I tested it in non IE9 browsers. Thank you!


TLS validation on new connections

See more deep description of changes in commit messages, here is some compressed copypaste
Big refactor of generate_tls_keys.sh

Put cert name into CN (like "Test leaf certificate (acra-server)")
Generate certificate database for OpenSSL so its OCSP server can work with it, also required to generate CRL
Add certs "ocsp-responder" and "acra-writer-revoked"; the second one is for tests to make sure acra-server handles revoked certificates
Generate CRL (Certificate Revocation List) containing that one revoked certificate, signed by CA

Start OCSP & CRL servers when teststing with TLS enabled
Update tests/test.py:

Add global vars containing OCSP certificate and key, as well as certificate database
Add function to launch openssl ocsp server along with acra-server and acra-connector, but only if TLS is enabled
Use Python's package http to create HTTP server, CRL verifier will be able to fetch CRL from there

Implement all the things
This PR contains implementation of TLS certificate validators using using OCSP protocol (RFC6960) and CRLs (RFC5280). It includes mentioned validators implementation, as well as way to configure them in Acra (server and connector) using command line flags.
OCSP flags (with default value and description):

--tls_ocsp_url, "", OCSP service URL
--tls_ocsp_client_url, "", OCSP service URL, for client/connector certificates only
--tls_ocsp_database_url, "", OCSP service URL, for database certificates only
--tls_ocsp_required, "denyUnknown", How to treat certificates unknown to OCSP: <denyUnknown|allowUnknown|requireGood>
denyUnknown -> deny certificate if OCSP server responded with "unknown"
allowUnknown -> allow certificate not known by OCSP server, but all servers returning "unknown" is considered an error
requireGood -> all OCSP servers we know about (the one from configuration and those listed in certificate) should respond with "good", otherwise reject the certificate
--tls_ocsp_from_cert, "prefer", How to treat OCSP server described in certificate itself: <use|trust|prefer|ignore>
use -> use OCSP servers from certificates, but after the one from configuration (if configured)
prefer -> like use but try those from certificate first
trust -> like prefer, but don't even try configured server if the one from certificate tells us the certificate is valid
ignore -> don't use OCSP servers from certificates
--tls_ocsp_check_only_leaf_certificate, false, Put 'true' to check only final/last certificate, or 'false' to check the whole certificate chain using OCSP

CRL flags (with default value and description):

--tls_crl_url, "", URL of the Certificate Revocation List (CRL) to use
--tls_crl_client_url, "", URL of the Certificate Revocation List (CRL) to use, for client/connector certificates only
--tls_crl_database_url, "", URL of the Certificate Revocation List (CRL) to use, for database certificates only
--tls_crl_from_cert, "use", How to treat CRL URL described in certificate itself: <use|trust|prefer|ignore>
use -> use CRL distribution point(s) servers from certificates, but after the one from configuration (if configured)
prefer -> like use but try those from certificate first
trust -> like prefer, but don't even try configured CRL URL if the one from certificate does not contain the certificate
ignore -> don't use CRL distribution points from certificates
--tls_crl_check_only_leaf_certificate, false, Put 'true' to check only final/last certificate, or 'false' to check the whole certificate chain using CRL
--tls_crl_cache_size, 16, How many CRLs to cache in memory (use 0 to disable caching)
--tls_crl_cache_time, 0, How long to keep CRLs cached, in seconds (use 0 to disable caching, maximum: 300 s)

Please note that client- and DB-specific URIs are only configurable in acra-server; acra-connector does not have these "two sides" so there is only one URI for OCSP and one for CRL.
Integration tests (tests/test.py), when launching acra-server or acra-connector, add a couple of options to either enable both verifiers (if TLS was enabled in tests) or disable verification completely. Disabling by default is done to avoid situations where test certificate contains some OCSP or CRL URIs and Acra cannot access them since appropriate services were not started thus denying actually valid test certificates and failing the tests.
There are also unit tests (network/{ocsp_test.go,crl_test.go}) to cover the behavior of both verifiers.
TODO:

[X] Update error messages
[X] Update help text about CLI flags
[X] Add certificate group that contains intermedidate CA (it existed at some point, can be used in integration or go tests, but the tool that generated them was kinda too complex, and there were too many redundant files generated, I guess generate_tls_keys.sh should be updated, or some simple util written for that purpose instead)
[ ] Add few integration tests (there were attempts, but the fact that tests/test.py sets up SSL/TLS configuration on script start, not inside tests, does not allow writing custom tests that use custom certificates, for example to test acra-server + acra-connector with revoked certificate; possible simple solution is to skip these new tests by default but run them (and only them) separately from inside the .circleci/integration.sh script after usual tests)
[ ] Different random updates based on comments (mostly done)
[ ] Update changelog

This PR will likely have some little conflicts with #435, so one of us will have to merge master into PR's branch.
And based on all this mess, I guess #435 will be merged first and then I'll update this PR's branch (:

@ilammy, I believe that single ultimate CRL/OCSP cant be used for the case that you mentioned. We can perform blacklisting on per-certificate basis, which means that if some itermediate CA is compromised, we should blacklist each certificate issued by this CA. Each CA ideally should have own correspondent CRL/OCSP instance, because parent (root) CA has no clue about certificates issued by child (intermediate) CA.
I found very good explanation of recursive algorithm described in RFC 5280 (tools.ietf.org/html/rfc5280#page-71) that should be applied to verification of end-user certificate issued by intermediate CA (which has parent  root cert) on stackoverflow: https://stackoverflow.com/questions/19962069/how-does-certificate-revocation-work-with-intermediate-cas


Config to say yes please kill the running process every time

At the moment each time we press 'run' (next to the main fn) we get a dialog box asking if we'd like to kill the current process or not.
Config to say yes please kill the running process every time would be great.

That's an editor issue: https://github.com/microsoft/vscode/issues/32264


[release-1.26] [occm] Use standard service account name in OCCM helm chart

What this PR does / why we need it:
This is a cherry-pick of:

#2332
#2347

Which issue this PR fixes(if applicable):
fixes #2440
Special notes for reviewers:
At the time #2332 was merged the CI was sadly somewhat broken and missed a spurious space. This has been fixed in #2347 which is also included here to ensure that CI is passing.
As discussed, I bumped the helm chart version to 2.26.5.
I've also tested this helm chart version in a new 1.26 cluster and was unable to reproduce the bug fixed in #2332.
Please let me know if you'd like me to combine (i.e. squash/fixup) both commits in here into a single, correct, one.
Release note:
ACTION REQUIRED: Please note that you might have to delete the `cloud-controller-manager` service account in the `kube-system` namespace if it exists, as upgrading with helm would fail otherwise.

/lgtm

/approve


docs: Edit document to correctly.

"@scully/init" is not available anymore.

F:\HieuNV2\portfolio>ng add @scully/init
Unable to fetch package metadata: 404 Not Found - GET https://registry.npmjs.org/@scully%2Finit - Not found
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


':pay_android:compileDebugKotlin' Error after Flutter 3.0 Upgrade

Using latest everything to include Flutter 3.0 and I'm getting the following error unless pay package still depends on early dependencies:
What went wrong:
Execution failed for task ':pay_android:compileDebugKotlin'.
A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

I used GitHub Action and its the same error as indicated from the log:
Run flutter build apk --release
💪 Building with sound null safety 💪
Running Gradle task 'assembleRelease'...
/opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/mobile_scanner-1.1.0/lib/src/mobile_scanner.dart:50:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.

'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/hostedtoolcache/flutter/3.0.1-stable/x64/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance?.addObserver(this);
^
/opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/mobile_scanner-1.1.0/lib/src/mobile_scanner.dart:134:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/hostedtoolcache/flutter/3.0.1-stable/x64/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance?.removeObserver(this);
^
/opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/card_swiper-2.0.3/lib/src/custom_layout.dart:36:20: Warning: Operand of null-aware operation '!' has type 'WidgetsBinding' which excludes null.
'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/hostedtoolcache/flutter/3.0.1-stable/x64/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance!.addPostFrameCallback(_getSize);
^
/opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/card_swiper-2.0.3/lib/src/transformer_page_view/transformer_page_view.dart:540:22: Warning: Operand of null-aware operation '!' has type 'WidgetsBinding' which excludes null.
'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/hostedtoolcache/flutter/3.0.1-stable/x64/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance!.addPostFrameCallback(_onGetSize);
^
/opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/card_swiper-2.0.3/lib/src/transformer_page_view/transformer_page_view.dart:554:22: Warning: Operand of null-aware operation '!' has type 'WidgetsBinding' which excludes null.
'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/hostedtoolcache/flutter/3.0.1-stable/x64/packages/flutter/lib/src/widgets/binding.dart').
WidgetsBinding.instance!.addPostFrameCallback(_onGetSize);
^
Note: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-3.1.15/android/src/main/java/io/flutter/plugins/firebase/firestore/FlutterFirebaseFirestorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
warning: [options] source value 7 is obsolete and will be removed in a future release
warning: [options] target value 7 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
3 warnings
warning: [options] source value 7 is obsolete and will be removed in a future release
warning: [options] target value 7 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
3 warnings
warning: [options] source value 7 is obsolete and will be removed in a future release
warning: [options] target value 7 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
3 warnings
Note: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/location-4.4.0/android/src/main/java/com/lyokone/location/FlutterLocation.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
e: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/pay_android-1.0.6/android/src/main/kotlin/io/flutter/plugins/pay_android/PayMethodCallHandler.kt: (50, 69): Type mismatch: inferred type is Activity? but Activity was expected
e: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/pay_android-1.0.6/android/src/main/kotlin/io/flutter/plugins/pay_android/PayMethodCallHandler.kt: (69, 74): Type mismatch: inferred type is String? but String was expected
e: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/pay_android-1.0.6/android/src/main/kotlin/io/flutter/plugins/pay_android/PayMethodCallHandler.kt: (73, 34): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type Map<String, Any>?
e: /opt/hostedtoolcache/flutter/3.0.1-stable/x64/.pub-cache/hosted/pub.dartlang.org/pay_android-1.0.6/android/src/main/kotlin/io/flutter/plugins/pay_android/PayMethodCallHandler.kt: (74, 34): Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type Map<String, Any>?

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':pay_android:compileReleaseKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Try:

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

Get more help at https://help.gradle.org

BUILD FAILED in 3m 44s
Running Gradle task 'assembleRelease'...                          225.1s
Gradle task assembleRelease failed with exit code 1
Error: Process completed with exit code 1.

pay: 1.0.9 and pay_android: 1.0.7 are now published, addressing this issue.
Thank you.


Github Url for dotnetapp-4.7 sample is Incorrect

The URI given in Readme.md for the dotnetapp-4.7 is Incorrect

Git clone this repository or otherwise copy this sample to your machine: git clone
https://github.com/dotnet/dotnet-framework-docker-samples/dotnetapp-4.7

This issue has been addressed with Microsoft/dotnet-framework-docker#126


Handle untracked flake files elegantly

garner commands usually (re)generate a flake.nix, and then uses that. If, however, the flake.nix is untracked (as usually it will be the first time around), nix complains about a non-existent flake.nix - which is very confusing.
Find a nicer system for this. For example:

Warn that flake.nix must be added
Automatically git add --intent-to-add the flake.nix file.

Fixed in #214.


An interrupt was produced by #39

When running pnpm run dev I get the following error, which prevents the dev server from evenstarting:

Contentlayer config change detected. Updating type definitions and data...
This error shouldn't have happened.

I'm trying to use Contentlayer with Next.js 14.2.5 (app router). Here's the corresponding stack trace:
╥
╠══╦══╗
║  ║  ║
║  ║  ╠─An interrupt was produced by #39.
║  ║  ║
║  ║  ▼
║  ║
║  ╠─An unchecked error was produced.
║  ║
║  ║ TypeError: Cannot read properties of undefined (reading 'type')
║  ║     at fieldListItemsToCoreFieldListDefItems (file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@contentlayer+source-files@0.3.4_esbuild@0.18.20/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:248:28)
║  ║     at fieldDefEntryToCoreFieldDef (file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@contentlayer+source-files@0.3.4_esbuild@0.18.20/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:159:13)
║  ║     at file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@contentlayer+source-files@0.3.4_esbuild@0.18.20/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:26:9
║  ║     at Array.map (<anonymous>)
║  ║     at next (file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@contentlayer+source-files@0.3.4_esbuild@0.18.20/node_modules/@contentlayer/source-files/src/schema/provideSchema.ts:25:70)
║  ║     at Generator.next (<anonymous>)
║  ║     at ISuspend.factory (file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@effect-ts+system@0.57.5/node_modules/@effect-ts/system/_src/Effect/gen.ts:135:28)
║  ║     at FiberContext.evaluateNow (file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@effect-ts+system@0.57.5/node_modules/@effect-ts/system/_src/Fiber/context.ts:1173:51)
║  ║     at file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@effect-ts+system@0.57.5/node_modules/@effect-ts/system/_src/Fiber/context.ts:576:33
║  ║     at file:///Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/@effect-ts+system@0.57.5/node_modules/@effect-ts/system/_src/Support/Scheduler/index.ts:15:9
║  ║
║  ║ Fiber: #41 (started at: 2024-08-05T07:26:03.063Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #41 (started at: 2024-08-05T07:26:03.063Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #41 (started at: 2024-08-05T07:26:03.063Z) was spawned by:
║  ║
║  ║ Fiber: #39 (started at: 2024-08-05T07:26:03.062Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #39 (started at: 2024-08-05T07:26:03.062Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #39 (started at: 2024-08-05T07:26:03.062Z) was spawned by:
║  ║
║  ║ Fiber: #37 (started at: 2024-08-05T07:26:03.062Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #37 (started at: 2024-08-05T07:26:03.062Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #37 (started at: 2024-08-05T07:26:03.062Z) was spawned by:
║  ║
║  ║ Fiber: #26 (started at: 2024-08-05T07:26:03.058Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #26 (started at: 2024-08-05T07:26:03.058Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #26 (started at: 2024-08-05T07:26:03.058Z) was spawned by:
║  ║
║  ║ Fiber: #5 (started at: 2024-08-05T07:26:02.755Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #5 (started at: 2024-08-05T07:26:02.755Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #5 (started at: 2024-08-05T07:26:02.755Z) was spawned by:
║  ║
║  ║ Fiber: #0 (started at: 2024-08-05T07:26:02.746Z) was supposed to continue to: <empty trace>
║  ║
║  ║ Fiber: #0 (started at: 2024-08-05T07:26:02.746Z) Execution trace: <empty trace>
║  ║
║  ║ Fiber: #0 (started at: 2024-08-05T07:26:02.746Z) was spawned by: <empty trace>
║  ▼
▼

OS: darwin 23.6.0 (arch: arm64)
Process: /Users/D/.local/share/fnm/node-versions/v20.15.1/installation/bin/node /Users/D/Git/vilkinsons/vilkinsons.com/node_modules/.pnpm/next@14.2.5_@opentelemetry+api@1.9.0_react-dom@18.3.1_react<EMAIL_ADDRESS>Node version: v20.15.1
Contentlayer version: 0.3.4

This is a newly-bootstrapped project, with some example content thrown in the contentlayer.config.ts file and a package.json which contains:
"dependencies": {
   "contentlayer": "^0.3.4",
   "date-fns": "^3.6.0",
   "next": "14.2.5",
   "next-contentlayer": "^0.3.4",
   "react": "^18.3.1",
   "react-dom": "^18.3.1"
 },
 "devDependencies": {
   "@types/node": "^20.14.14",
   "@types/react": "^18.3.3",
   "@types/react-dom": "^18.3.0",
   "eslint": "^8.57.0",
   "eslint-config-next": "14.2.5",
   "typescript": "^5.5.4"
 }

If I can usefully provide any more information, please let me know.
I suspect my issue relates to (if not is duplicative of) https://github.com/contentlayerdev/contentlayer/issues/659

Any solution to this yet? I'm having the same issue. For me it seems to be related to trying to set up images. in the docs it's set up like this for the contentlayer.config:
fields: {     image: { type: string },   },
But that throws the error
ReferenceError: string is not defined
When I change is to
fields: {     image: { type: "string" },   },
I get the exact same error. I've tried this using 0.3.4 and 0.3.2 using Node v16.17.0


[Bug]: Can't deploy hello world axum app

What happened?
I followed the basic shuttle project instructions :

cargo install cargo-shuttle
cargo shuttle init
cargo shuttle deploy
cargo deploy --allow-dirty

Version
v0.33.0
Which operating system(s) are you seeing the problem on?
macOS
Which CPU architectures are you seeing the problem on?
ARM64
Relevant log output
2023-11-21T04:23:47.595+01:00 [Deployer]  INFO Starting deployment
2023-11-21T04:23:47.595+01:00 [Deployer]  INFO shuttle_deployer::handlers: Deployer version: 0.33.0
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Deployment ID: 7f003c3c-1cb5-4290-a135-ec77e3c4de3d
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Service ID: 01HFQWSN2FZHQTHRDHWTDZ76VS
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Service name: backend-test
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Project ID: 01HFQWPSX14Q9WEYYTMH9RA8NA
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Project name: backend-test
2023-11-21T04:23:47.596+01:00 [Deployer]  INFO shuttle_deployer::handlers: Date: 2023-11-21T03:23:47Z
2023-11-21T04:23:57.381+01:00 [Deployer]  INFO Entering Queued state
2023-11-21T04:23:57.381+01:00 [Deployer]  INFO Waiting for queue slot
2023-11-21T04:23:57.382+01:00 [Deployer]  INFO Entering Building state
2023-11-21T04:23:57.382+01:00 [Deployer]  INFO Building project
2023-11-21T04:23:57.382+01:00 [Deployer]  INFO shuttle_deployer::deployment::queue: Extracting files
2023-11-21T04:23:57.383+01:00 [Deployer]  INFO shuttle_deployer::deployment::queue: Building deployment
2023-11-21T04:23:57.433+01:00 [Deployer]       Failed to fetch crates
2023-11-21T04:23:57.501+01:00 [Deployer]  INFO Releasing queue slot
2023-11-21T04:23:57.502+01:00 [Deployer]  WARN shuttle_deployer::deployment::queue: {error="Serde JSON error: EOF while parsing a value at line 1 column 0"} could not release build slot
2023-11-21T04:23:57.502+01:00 [Deployer]  INFO Entering Crashed state
2023-11-21T04:23:57.502+01:00 [Deployer]  INFO Build failed
2023-11-21T04:23:57.502+01:00 [Deployer] ERROR shuttle_deployer::deployment::queue: {error="Build error: `cargo metadata` exited with an error:     Updating `shuttle-crates-io-mirror` index\nerror: failed to select a version for the requirement `serde = \"^1.0.193\"` (locked to 1.0.193)\ncandidate versions found which didn't match: 1.0.192, 1.0.191, 1.0.190, ...\nlocation searched: `shuttle-crates-io-mirror` index (which is replacing registry `crates-io`)\nrequired by package `backend-test v0.1.0 (/opt/shuttle/shuttle-builds/backend-test)`\nperhaps a crate was updated and forgotten to be re-vendored?\n"} Service build encountered an error

Duplicate declaration

[X] I have searched the issues and there are none like this.

Same thing happens to me when I try to deploy a project that uses a recent version of any crate, even after waiting 12 hours since the release.
¿How much time does the mirror need to update dependencies?

Hey! Sorry about this, we're experiencing occasional failures when our mirror is automatically synced, which leads to it quickly falling behind in crate versions. We're planning to migrate off this mirror in this week's release. In the meantime, the mirror is now fully synced.

Newest release no longer uses the mirror.


fix(versions): update Activiti/activiti-dependencies versions into develop

UpdateBot pushed maven dependency: org.activiti:activiti-core-dependencies to: 7.1.108

UpdateBot commands:
updatebot push-version --kind maven org.activiti:activiti-core-dependencies 7.1.108 --merge false


Added test-scope to test dependencies

This request looks good. Thanks for doing that! Do you agree to license this and any other contributions  to this project under the same MIT license the project is under (https://github.com/noelherrick/jell/blob/master/LICENSE)?

Sure, I agree to license this under the MIT license. This is my first pull-request and steps in Git Hub, do I have to do anything else to set the license?

Nope! I think your commenting is enough. Merged.


enabling horizontal drag and vertical drag

Hi Team,
I am using this awesome plugin, but the UI requirement changed a bit.
So I Must enable this plugin for horizontal drag and drop as well, so I changed the css through display:inline-block.
Horizontal dragging, I have to place the dragged element for a while and then it allows for drop and in some cases, it doesn't allow it to be dropped. I have to retry it again  and then I see the space for dropped. I have not added any delay in the code.However vertical drag and drop works just fine. Any comments?
Here: I am trying to drag an element from second row to first element, but I get the drop element for others instead of first

If f you see am trying to replace the first element, but the adjacent elements drop location opens up

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.


Add support for a backup-uri option to fall back on error

Summary: We would like to be able to configure a fallback uri that the config server would use if an error occurs when contacting the primary uri. Our config server needs to be highly available.
I saw two other requests that looked related, but it didn't appear as though they were implemented, and I didn't see a workaround: https://github.com/spring-cloud/spring-cloud-config/pull/1220 and https://github.com/spring-cloud/spring-cloud-config/issues/617#issuecomment-275436934.
We should be able to provide this any place we can provide the uri parameter. For example:
      server:
        composite:
        -
          type: git
          basedir: ${spring.cloud.config.server.git.basedir}
          uri: ${DefaultURI}
          uri-backup: ${BackupURI}

          repos:
            Messaging:
              pattern: Msg*
              searchPaths: "*, Common/*"
              basedir: ${basedirParent}\\baseMessaging
              uri: ${DefaultURI}
              uri-backup: ${BackupURI}
        -
          type: git
          basedir: ${basedirParent}\\baseShared
          uri: ${DefaultURI}
          uri-backup: ${BackupURI}

I am not sure how this should tie in with falling back to the local cache. It could be:

Try primary uri.
If error, use local cache.
If nothing in the local cache, use the backup uri.

or:

Try primary uri.
If error, try the backup uri
If error, use the local cache if available.

I think this duplicates #617

Is that one still open? If so, yes, this is a duplicate. My apologies. I thought that one was closed for some reason.