multiarch build added

Summary
Repo's first PR. what has been done:

[x] fork of https://github.com/postmanlabs/httpbin
[ ] setup of a github actions pipeline to build multi-arch images.

Full changelog

[Implement ...]
[Fix ...]

Issues resolved
Fix #XXX
Documentation

[ ] Link to the website documentation PR

Testing

[ ] Unit tests
[ ] E2E tests
[ ] Manual testing on Universal
[ ] Manual testing on Kubernetes

 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.


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Mon Mar 14 2016 15:52:44 GMT-0400 (Eastern Summer Time)
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (C:\Users\Danny\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (C:\Users\Danny\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470


[Feature]: Puppeteer.connect should be supported with BiDi protocol

Feature description
Puppeteer.connect should be supported via BiDi protocol.
When Puppeteer.connect is called with {protocol: webDriverBiDi}, a new BiDi connection should be established.
Actual behaviour: new CDP connection is established.

Add support .connect  for FF

Closing as completed by #11451.


Error: Cannot find local build configuration 'gcc.bldconf' for package bench.

c99eea62513359006e63ef7ebca2d468e31ff28f
gcc 6.3.0, Ubuntu 16.04.
Commands:
. env.sh
parsecmgmt -a build

Outcome:
[PARSEC] Packages to build:  bench
/data/git/parsec-benchmark/bin/parsecmgmt: line 1252: /data/git/parsec-benchmark/config/packages/bench.pkgconf: No such file or directory

[PARSEC] [========== Building package bench [1] ==========]
[PARSEC] [---------- Analyzing package bench ----------]
/data/git/parsec-benchmark/bin/parsecmgmt: line 820: /data/git/parsec-benchmark/config/packages/bench.pkgconf: No such file or directory
/data/git/parsec-benchmark/bin/parsecmgmt: line 834: [: ==: unary operator expected
[PARSEC] Error: Cannot find local build configuration 'gcc.bldconf' for package bench.

Same issue.
Commands:
./parsecmgmt -a build
Console:
[PARSEC] Packages to build:  bench
./parsecmgmt: line 1252: /git/parsec-benchmark/bin/../config/packages/bench.pkgconf: No such file or directory
[PARSEC] [========== Building package bench [1] ==========]
[PARSEC] [---------- Analyzing package bench ----------]
./parsecmgmt: line 820: /git/parsec-benchmark/bin/../config/packages/bench.pkgconf: No such file or directory
./parsecmgmt: line 834: [: ==: unary operator expected
[PARSEC] Error: Cannot find local build configuration 'gcc.bldconf' for package bench.

@smazigh btw, I have some stuff working at: https://github.com/cirosantilli/parsec-benchmark (not all), and will review and accept pull requests.

Thank you !


ci: release 0.18.2

:robot: I have created a release beep boop
0.18.2 (2024-10-21)
Bug Fixes

address CVE-2023-39325 found by https://github.com/canonical/oci-factory/actions/runs/11406456591/job/31741561258 (a68d463)
deps: update ui deps (6228aa2)
return error is no login_challenge or return_to (1efbff4)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/canonical/identity-platform-login-ui/releases/tag/v0.18.2 :sunflower:


Issue Building on Fork via npm vs. git+ssh or git+https

If I have an empty node_modules directory, and I add to my package.json
"dependencies": {
  "material-ui": "v0.14.4"
}

and then run
npm install
I will be able to run my project (which depends on material UI) without any errors.
However, if I use git+ssh or git+https and npm install the same tag, I run into all sorts of trouble:
"dependencies": {
    "material-ui": "git+https://git@github.com:callemall/material-ui.git#v0.14.4",
}

For starters - and I am aware this is likely an npm-related problem - I have to
cd node_modules/material-ui
npm install && npm run build

But this is not a huge issue, as I can script this if I have to. However, the components all just seem to break and become unresponsive due to an Invariant Violation.
The error I keep seeing is:
"Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner)."
Again, with absolutely no difference in the codebase - simply pulling the package from git vs. npm. Is there some sort of script you are using before publishing to npm that we don't have access to? Maybe something in the CI process? Something that strips out calls to require "react" before publishing to npm?
I am trying to utilize my own fork and depend on it on a local project, whose changes may or may not eventually be pull-requested to this master project if they seem useful. The goal is:

create a fork of Material UI
make customizations, modifications, improvements
npm install the master branch of my material UI fork in my project so I can keep developing my fork within my project

Maybe you have a different recommendation/approach as to how one might develop against their own fork of material-ui?

@netpoetica you can build locally in it's own directory (pull the repo directly, do not build it in /node_modules/) it and use npm link or publish it to your own namespace on npm.

Hey @nathanmarks I appreciate the solution, thanks! But I am curious if anyone can explain what the actual issue here is. It looks to me like maybe callemall team has some kind of deploy server that is running some script before an "npm publish" that we can't see - that's the only reasonable solution I have been able to come up with as to why that error is present under the two different circumstances.

@netpoetica Things can break if you do npm install && npm build inside a node_modules/xxxxxx folder because of how NPM manages project dependencies.

But I am curious if anyone can explain what the actual issue here is.

Here is the issue https://github.com/callemall/material-ui/issues/2818. React is installed twice.
The easiest fix is to remove the react folder under the material-ui folder?

Ah, I see. But why does the build behavior differ when installed from git+ssh vs. npm? To me this means the published package must differ from the release tags.
If I make 2 clones of my project. One of them has a package.json that says:
"dependencies": {
  "material-ui": "v0.14.4"
}

and then I go into the other clone, and change that package.json like so:
"dependencies": {
    "material-ui": "git+https://git@github.com:callemall/material-ui.git#v0.14.4",
}

and then run "npm install" in both, one will generate a build (from npm, the first one), and one won't (the git+https, the second one). Additionally, the first one won't give me that error but the second one will.

Also just FYI, the solution above does work for getting it operational. I just have a script that does this:
#!/bin/bash

#
# ./bin/update-mui
#

rm -rf node_modules/material-ui && npm install --production && cd node_modules/material-ui && npm install && npm run build && rm -rf node_modules/react

With the package.json wired up via git+ssh to the development branch of my fork. I am still very curious about the last question I asked, but just as an FYI yes it can be worked around.

I guess the prepublish task is the difference really. lib/ gets put into the npm version of this project but not in the tagged release. What happens is, prepublish builds lib/ packages it with the rest of the code when publishing, but doesn't include node_modules dir, so you don't run into this problem with node_modules/react. Gonna mark this closed


MouseMirror won´t load on Raspberry Pi 4 (ARM64)

Window setup used: https://worproject.com/
Problems:

Driver install confirmation dialog shown on screen
Driver won´t load

The MouseMove driver doesn´t suffer from these problems.

Logitech wireless mouse:
HID\VID_046D&PID_C52E&REV_2301&MI_01&Col01
HID\VID_046D&PID_C52E&MI_01&Col01
HID\VID_046D&UP:0001_U:0002
HID_DEVICE_SYSTEM_MOUSE
HID_DEVICE_UP:0001_U:0002
HID_DEVICE

MouseMirror_arm64.zip

The driver failed to load due to the signature being invalidated after editing the INF file.


add location by sending more Model attributes as a body json/dict

have not being able to add location by passing more zscaler location model attributes as such as: upBandwidth, country, sslScanEnabled, etc....
it is possible do send as json body all these location model settings using Postman to create a location. Is there an way to do the same using pyzscaler add_location function ?

I've been looking into this one and I think I'll take three actions here:

I will update the locations endpoint to accept the new attributes
I'll try find a way to keep on top of modifications to Zscaler's API endpoints as they will randomly add new parameters without any obvious update to tell endusers
I'm going to add a 'raw' override capability for all pyZscaler methods. This will allow you to skip args/kwargs and just pass a raw JSON structure in whatever manner you like. This would allow you to use pyZscaler and immediately implement any new parameters that may have come out before we have time to update the SDK

@fabiano-lima what do you think of the 3rd option, do you think you'd find that useful?
sorry for the late reply, I haven't had a lot of time lately but there are a lot of updates coming today hopefully 😃

Okay it's been a while since I've looked at the zia.locations module.
The code is pretty simple here:
        payload = {
            "name": name,
        }

        # Add optional parameters to payload
        for key, value in kwargs.items():
            payload[snake_to_camel(key)] = value

        return self._post("locations", json=payload)

We start the payload with the only required argument to create a location, which is name. From there any kwarg that you add will be converted to camelcase and fed into the payload. So if you wanted to set any of the parameters you've specified it might look like this:

zia.locations.add_location(name='My Location', up_bandwidth=30000, down_bandwidth=30000, country='FIJI')

I'll update the docstrings so it's a bit clearer and I'll still consider the raw json option, but most of the methods will let you add an arbitrary number of kwargs over and above what I've actually documented.
Will that fit your use-case @fabiano-lima for now?

Thank you @mitchos , appreciate you taking the time to check this issue. Also the pyZscaler is helping a lot on my project.
Have tested the line you suggested, but not working as expected, following some tests:
from pyzscaler.zia import ZIA

payload = {
   "name":"My Location",
   "upBandwidth":10000,
   "dnBandwidth":10000,
   "country":"FIJI",
   "vpnCredentials":[
      {
         "id":valid_id,
         "preSharedKey":"XXXXX",
         "type":"UFQDN",
<EMAIL_ADDRESS>      }
   ]
}

with ZIA(api_key='key', cloud='zscaler', username='username', password='pass') as zia:

    # 1st try
	zia.locations.add_location(name='My Location', up_bandwidth=30000, dn_bandwidth=30000, country='FIJI')

	# 2nd try
	zia.locations.add_location(name='My Location', up_bandwidth=30000, dn_bandwidth=30000, country='FIJI', vpn_credentials={'id': valid_id, 'type': 'UFQDN'})

	# 3rd try
    zia.locations.add_location(name='My Location', ip_addresses=['<IP_ADDRESS>'], ports=[], vpn_credentials={'id': valid_id, 'type': 'UFQDN'})

	# 4th try
    zia.locations.add_location(name='My Location', ipAddresses=['<IP_ADDRESS>'], ports=[], vpnCredentials={'id': valid_id, 'type': 'UFQDN'})

	# 5th try
	zia.locations.add_location(name='My Location', ip_addresses=['<IP_ADDRESS>'], ports=[], vpnCredentials={'id': valid_id, 'type': 'UFQDN'})

	# 6th try
	zia.locations.add_location(name='My Location', ip_addresses=['<IP_ADDRESS>'], vpn_credentials={'id': valid_id, 'type': 'UFQDN'})

	7th try
	zia.locations.add_location(name='My Location', **payload)

Responses:

# 1st try
SDK PyZscaler> python .\add_location.py
[400: POST] https://zsapi.zscaler.net/api/v1/locations body=b'{"code":"INVALID_INPUT_ARGUMENT","message":"At least an IP Address, Port, VPN Credential or Virtual Zen/Cluster is required, name: My Location"}'
SDK PyZscaler>

# 2nd to 6th tries:
SDK PyZscaler> python .\add_location.py
[400: POST] https://zsapi.zscaler.net/api/v1/locations body=b'{"message":"Request body is invalid."}'
SDK PyZscaler>

# 7th try
# No response, neither any location created on zscaler cloud
SDK PyZscaler> python .\add_location.py
SDK PyZscaler>

I am using pyZscaler for GET locations and other functions, but for Add/Post using another methods as Postman where I am able to send all the parameters, including the location name on the Body as a Json (as the payload example on the tests)

Hi @fabiano-lima so it just comes down to the vpn_credentials parameter, which needs to be a list as you can add multiple credentials to a single location.
This worked for me:
zia.locations.add_location(
        name="My Location",
        up_bandwidth=30000,
        dn_bandwidth=30000,
        country="FIJI",
        vpn_credentials=[{"id": "<id>", "type": "UFQDN"}],
    )

which results in:
 {
    "id": "<id>",
    "name": "My Location",
    "non_editable": False,
    "parent_id": 0,
    "up_bandwidth": 30000,
    "dn_bandwidth": 30000,
    "country": "FIJI",
    "language": "NONE",
    "tz": "GMT",
    "geo_override": False,
    "latitude": 0.0,
    "longitude": 0.0,
    "vpn_credentials": [{"id": "<id>", "type": "UFQDN", "fqdn": "<fqdn>"}],
    "auth_required": False,
    "ssl_scan_enabled": False,
    "zapp_ssl_scan_enabled": False,
    "xff_forward_enabled": False,
    "other_sub_location": False,
    "ec_location": False,
    "surrogate_ip": False,
    "idle_time_in_minutes": 0,
    "surrogate_ip_enforced_for_known_browsers": False,
    "surrogate_refresh_time_in_minutes": 0,
    "kerberos_auth": False,
    "digest_auth_enabled": False,
    "ofw_enabled": False,
    "ips_control": False,
    "aup_enabled": False,
    "caution_enabled": False,
    "aup_block_internet_until_accepted": False,
    "aup_force_ssl_inspection": False,
    "iot_discovery_enabled": False,
    "aup_timeout_in_days": 0,
    "child_count": 0,
    "match_in_child": False,
    "static_location_groups": [],
    "dynamiclocation_groups": [{"id": "<id>", "name": "Server Traffic Group"}],
    "exclude_from_dynamic_groups": False,
    "exclude_from_manual_groups": False,
    "profile": "SERVER",
}

I'll update the documentation and add an example as this is a pretty common usage.
Let me know how you get on with that?


Security email not working

I have reported a issue through huntr.dev platform which might have tried contacting on the email<EMAIL_ADDRESS>I have also tried to contact as well but the mailer daemon threw back an error email  "Diagnostic-Code: Host not reachable." Is the email active?
Meanwhile can you please take a look at https://www.huntr.dev/bounties/1-guzzle/psr7/
Thanks.

Please email me directly at hello at gjcampbell dot co dot uk. We don't handle bounties via third party sites.

@GrahamCampbell emailed you.

I haven't received anything. Did you get the email address right?

Rechecked, email is correct and mail delivery was successful. Maybe it went to spam folder?

Our new security contact email is<EMAIL_ADDRESS>:)


Remove PIL dependency

PIL has a huge overhead in addition to the tensorflow one - so far too slow for operation on real-time camera video input. The python work can be done using pure OpenCV, which proves much quicker. Are you able to update your sample python code to match?

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

ID: 754dd7d5-dd8b-4a75-5d79-0ba621a847cd
Version Independent ID: 3cca3535-1c16-2da1-46c6-421cbf808bc3
Content: Tutorial: Run TensorFlow model in Python - Custom Vision Service
Content Source: articles/cognitive-services/Custom-Vision-Service/export-model-python.md
Service: cognitive-services
GitHub Login: @areddish
Microsoft Alias: areddish

@jtlz2 Thanks for the feedback. We are investigating into the issue and will update you shortly.

@jtlz2 Thanks for your inputs, I was able to run this tutorial using OpenCV imread and get the same predictions.
Replaced
imageFile = "<path to your image file>"
image = Image.open(imageFile)

With
def cv2_open(filename):
    img = cv2.imread(filename)
    return cv2.cvtColor(img, cv2.COLOR_BGR2RGB)

image = cv2_open("path_to_image")

My model was trained to recognize Bougainvillea  trees from images, Loading images using PIL or OpenCV was not an issue in my case but I was curious to check if predictions are effected with the change though.
Prediction values with PIL:

Predication values with cv2:

I did not find any similar tutorial for videos in the documentation for custom AI but the references from OpenCV for video are helpful. Also a Jupyter notebook from custom vision examples to use its API might help as it uses cv2 too.
@areddish Could you please let us know if there are any plans to update the tutorial for real time video input?

Test

@jtlz2 Thanks for the feedback, I've added a work item to track PIL vs OpenCV usage in our samples and code.
@RohitMungi-MSFT For now the service is image-only and we don't have any video samples. To use a video source you would need to extract frames from the video and send to the service. There are no plans to update this tutorial for video at this time.

@areddish Thank you Andrew.
@jtlz2
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Train 'Mission Classifiers'

Train 3 binary 'Mission Classifiers' i.e one classifier for AHL, AFS, ASF:

Start with simple keyword matching approach
Try more advanced methods such as embeddings + classifiers or fine-tuning a transformer model

If more training data is needed, we can use LLMs to label more data.

Thanks for creating the issue @Jack-0-0 !
FYI a simple version of keyword matching is already implemented in the enrichment pipeline


Http Status is sent in the response body of SCIM2 error response

Sending HTTP status code in error response is redundant.
{     "schemas": [         "urn:ietf:params:scim:api:messages:2.0:Error"     ],     "detail": "Group with name: PRIMARY/aysh_local_manager_01 already exists in the system.",     "status": "409" }

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


clean up mash post processing

@rfeng2023 i fixed the merge conflict by pushing your version directly to main. Please sync with main now.


SyntaxError: The requested module '@aws-amplify/platform-core' does not provide an export named 'CallerDirectoryExtractor'

I created a lambda function using gen2 as follow:
amplify/functions/send-link-file/resource.ts file:
`import { defineFunction } from '@aws-amplify/backend';

export const sendReportEmail = defineFunction({
  name: 'send-report-email',
  entry: './handler.ts',
  timeoutSeconds: 180
});`

hander.ts file:

import {SendRawEmailCommand, SESClient, } from '@aws-sdk/client-ses';
import { CreateForm1 } from './pdf';

const sesClient = new SESClient({region: 'ap-south-1'});

export const handler = async (event: any, context: any) => {
// rest of the logic...

return 'success';

}

backend.ts file:
import { defineBackend } from '@aws-amplify/backend';
import {Effect, PolicyStatement} from "aws-cdk-lib/aws-iam"
import { auth } from './auth/resource.js';
import { data } from './data/resource.js';
import { sendLinkEmail } from './functions/send-link-email/resource';
import { sendReportEmail } from './functions/send-report-email/resource';

const backend = defineBackend({
  auth,
  data,
  sendLinkEmail,
  sendReportEmail
});

Everything works well in sandbox. But while deployment, I am getting following error:

2024-09-22T19:41:30.538Z [INFO]: # Executing command: npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID --debug

54 2024-09-22T19:41:55.774Z [INFO]: [DEBUG] 2024-09-22T19:41:55.773Z: npm

55 2024-09-22T19:41:55.780Z [INFO]: [DEBUG] 2024-09-22T19:41:55.774Z: WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>
56 2024-09-22T19:42:00.121Z [INFO]: [DEBUG] 2024-09-22T19:42:00.120Z: /codebuild/output/src4216656133/src/medical-amplify/node_modules/@aws-amplify/backend-function/src/factory.ts:35

57 CallerDirectoryExtractor,
    ^

59 SyntaxError: The requested module '@aws-amplify/platform-core' does not provide an export named 'CallerDirectoryExtractor'

60 at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)

61 at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)

Expected behavior
As it works well in the sandbox. This should deploy correctly.
Screenshots

Desktop (please complete the following information):

OS: IOS
Browser Chrome

How can I solve this issue?

Hey @jitinrathi910949, thank you for reaching out. Could you run npx ampx info and provide us the output? Additionally, could you verify if the aws-cdk and aws-cdk-lib are currently installed in the project?

Hi @ykethan ,
Yes I have both the packages installed.
Here is the output for npx ampx info
System:
  OS: macOS 14.5
  CPU: (8) arm64 Apple M1
  Memory: 140.33 MB / 8.00 GB
  Shell: /bin/bash
Binaries:
  Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
  Yarn: 3.6.4 - ~/.yarn/bin/yarn
  npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.3.0
  @aws-amplify/backend: 1.2.1
  @aws-amplify/backend-auth: 1.1.4
  @aws-amplify/backend-cli: 1.2.6
  @aws-amplify/backend-data: 1.1.3
  @aws-amplify/backend-deployer: 1.1.2
  @aws-amplify/backend-function: 1.4.0
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.1
  @aws-amplify/backend-secret: 1.1.1
  @aws-amplify/backend-storage: 1.1.2
  @aws-amplify/cli-core: 1.1.2
  @aws-amplify/client-config: 1.3.0
  @aws-amplify/deployed-backend-client: 1.4.0
  @aws-amplify/form-generator: 1.0.1
  @aws-amplify/model-generator: 1.0.6
  @aws-amplify/platform-core: 1.1.0
  @aws-amplify/plugin-types: 1.2.1
  @aws-amplify/sandbox: 1.2.1
  @aws-amplify/schema-generator: 1.2.2
  aws-amplify: 6.6.0
  aws-cdk: 2.159.1
  aws-cdk-lib: 2.158.0
  typescript: 5.6.2
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Hey @jitinrathi910949, thank you for reaching out. Could you run npx ampx info and provide us the output? Additionally, could you verify if the aws-cdk and aws-cdk-lib are currently installed in the project?

Hi @ykethan ,
Yes I have both the packages installed.
Here is the output for npx ampx info
System:
  OS: macOS 14.5
  CPU: (8) arm64 Apple M1
  Memory: 140.33 MB / 8.00 GB
  Shell: /bin/bash
Binaries:
  Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
  Yarn: 3.6.4 - ~/.yarn/bin/yarn
  npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.3.0
  @aws-amplify/backend: 1.2.1
  @aws-amplify/backend-auth: 1.1.4
  @aws-amplify/backend-cli: 1.2.6
  @aws-amplify/backend-data: 1.1.3
  @aws-amplify/backend-deployer: 1.1.2
  @aws-amplify/backend-function: 1.4.0
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.1
  @aws-amplify/backend-secret: 1.1.1
  @aws-amplify/backend-storage: 1.1.2
  @aws-amplify/cli-core: 1.1.2
  @aws-amplify/client-config: 1.3.0
  @aws-amplify/deployed-backend-client: 1.4.0
  @aws-amplify/form-generator: 1.0.1
  @aws-amplify/model-generator: 1.0.6
  @aws-amplify/platform-core: 1.1.0
  @aws-amplify/plugin-types: 1.2.1
  @aws-amplify/sandbox: 1.2.1
  @aws-amplify/schema-generator: 1.2.2
  aws-amplify: 6.6.0
  aws-cdk: 2.159.1
  aws-cdk-lib: 2.158.0
  typescript: 5.6.2
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Hey @jitinrathi910949, thank you for the information. Could you try removing the local node_modules and package-lock.json and reinstall them with latest versions of Amplify backend packages.

@ykethan @jitinrathi910949 I was also experiencing this issue after updating my @aws-amplify/backend to 1.2.2 a couple of weeks ago. After following @ykethan's package upgrade and removing node-modules looks like it finally deployed successfully, so that fixed my problem.

@ChristopherGabba thank you for the confirmation, closing the issue do reach out if you are still experiencing this.


Script to mesure reproducibility

This PR introduces a script to apply data augmentation to images and recompute metrics. The output file contains the mean and standard deviation of all metrics (avd, dice, lfdr, ltpr, mse, n_gt, n_pred, precision, recall, rvd, specificity, vol_gt, vol_pred, csa_gt, csa_pred, absolute_csa_diff, relative_csa_diff). The script takes as input one or multiple config files (-c), the number of iterations (-n) and the path (or paths) to the output file containing the results.
This PR also fixes the RandomAffine undo method. When applying affine_transform the translation is performed followed by the rotation and scaling transforms. To undo these transforms, the scaling and rotation transforms need to be undone, then undo translation.

use python for that

Updated here:  1059ad1

i would use -angle-corr 0 to prevent adding variance related to centerline fitting (same thing below)

Updated here: 3b05bfb


WL-5264 Add to database build script.

Looks fine to me, I'll merge once the build completes successfully.


Tokio Sync Feature incompatible

Hey there,
first of all: thanks for this amazing repo and the effort to make tokio compatible with the ESP-IDF ecosystem.
I may have found a gotcha while experimenting around with the setup:
Enabling and using the sync feature in tokio produces linking failures:
      /nix/store/s01q3syxbcw426nb6r2jv9034igafy28-esp32-toolchain-20230208/bin/../lib/gcc/riscv32-esp-elf/12.2.0/../../../../riscv32-esp-elf/bin/ld: /nix/store/s01q3syxbcw426nb6r2jv9034igafy28-esp32-toolchain-20230208/bin/../lib/gcc/riscv32-esp-elf/12.2.0/../../../../riscv32-esp-elf/lib/rv32imc_zicsr_zifencei/ilp32/no-rtti/libc.a(lib_a-fclose.o): in function `_fclose_r':
          /builds/idf/crosstool-NG/.build/riscv32-esp-elf/src/newlib/newlib/libc/stdio/fclose.c:73: warning: pthread_setcancelstate is not implemented and will always fail
       ...

probably due to the use of system threads, which need to be patched for linking with ESP-IDF (related https://github.com/ivmarkov/rust-esp32-std-demo/issues/24)
Maybe it is possible to somehow also apply the linker patches to the inner workings of tokio / sync?
The consequence of this incompatibility is that any library depending on sync will fail to build, most prominently hyper and subsequently most of the available HTTP Server Frameworks depending on it (axum etc.)
Would be happy to contribute!

I'm really not sure why the sync feature of tokio in particular would cause anything like this, and I can't reproduce here: https://github.com/jasta/esp32-tokio-demo/tree/sync-test.  Maybe something is wrong with your project set-up?

Ok closing for now, feel free to re-open if you learn more


remove username from logging

@PoshChan-Staging please remind me 1 minute

@PoshChan please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@PoshChan-Staging please remind me in 1 minute

@SteveL-MSFT, will remind you in 1 minute

@SteveL-MSFT, this is the reminder you requested 1 minute ago


"The table (not available) does not exist in the current database."

Bug description
Updated Prisma from v5.4.2 to v5.7.0 to test out the "relationJoins" preview feature. Most queries work as expected but there was one that gave me this error when executing a findMany operation:
The table `(not available)` does not exist in the current database.

This happens locally and when deployed to App Engine on GCP.
How to reproduce
Upgrade to v5.7.0 and enable the "relationJoins" preview feature.
Expected behavior
The query should "just work" and return the correct data as before when using the previous versions of Prisma.
Prisma information

For brevity I am not including the entire schema and instead including the models that are related to the query in question that has caused the error I am seeing. Let me know if you need me to include more.
datasource db {
    provider = "postgresql"
    url      = env("DATABASE_URL")
}

generator client {
    provider        = "prisma-client-js"
    output          = "../src/generated/client"
    previewFeatures = ["fullTextSearch", "postgresqlExtensions", "relationJoins"]
    extensions      = [pg_trgm]
}

model SalesOrder {
    id                        String               @id @default(uuid())
    internalId                String?
    referenceId               String?
    author                    User                 @relation(fields: [authorId], references: [id])
    authorId                  String
    distributor               Distributor?         @relation(fields: [distributorId], references: [id])
    distributorId             String?
    location                  Location?            @relation("Locations", fields: [locationId], references: [id], onDelete: Cascade)
    locationId                String?
    pickUpLocation            Location?            @relation("PickupLocations", fields: [pickUpLocationId], references: [id], onDelete: Cascade)
    pickUpLocationId          String?
    deliveryPlan              DeliveryPlan?        @relation(fields: [deliveryPlanId], references: [id])
    deliveryPlanId            String?
    company                   Company              @relation(fields: [companyId], references: [id])
    companyId                 String
    salesOrderItems           SalesOrderItem[]
    deliveryDate              DateTime
    paymentMethod             PaymentMethod        @default(CASH)
    distributorAdvancePayment Decimal?             @default(0)
    totalPaidAmount           Decimal?             @default(0)
    totalDueAmount            Decimal?             @default(0)
    totalAmount               Decimal?             @default(0)
    totalBuyingAmount         Decimal?             @default(0)
    transportFareAmount       Decimal?             @default(0)
    discount                  Decimal?             @default(0)
    discountAmount            Decimal?             @default(0)
    deliveryCharge            Decimal?             @default(0)
    additionalNotes           String?
    internalNotes             String[]
    attachments               Attachment[]
    status                    SalesOrderStatus
    subStatus                 SalesOrderSubStatus?
    deliveryStatus            String?
    deliveryTrackingId        String?
    deliveryTrackingUrl       String?
    deliveryOrderId           String?
    deliveryConsignment       Json?
    flagReason                String?
    onHoldReason              String?
    shortId                   Int
    isStockTransfer           Boolean              @default(false)
    isReturn                  Boolean              @default(false)
    transactions              Transaction[]
    parentSalesOrder          SalesOrder?          @relation("SalesOrderChildren", fields: [parentSalesOrderId], references: [id])
    parentSalesOrderId        String?
    salesOrders               SalesOrder[]         @relation("SalesOrderChildren")
    copyCount                 Int                  @default(0)
    staleness                 Int                  @default(0)
    createdAt                 DateTime             @default(now())
    updatedAt                 DateTime             @updatedAt
    orderDate                 DateTime
    exportedForDeliveryAt     DateTime?
    followUpDate              DateTime?
    unloadedAt                DateTime?
    deliveredAt               DateTime?
    approvedAt                DateTime?
    onHoldAt                  DateTime?
    processedAt               DateTime?
    shippedAt                 DateTime?
    inTransitAt               DateTime?
    flaggedAt                 DateTime?
    returnedAt                DateTime?
    damagedAt                 DateTime?
    cancelledAt               DateTime?
    metadata                  Json?
    deliveryArea              Json?
    deliveryPlanItems         DeliveryPlanItem[]
    truckPlateNumber          String?
    loadingBay                String?
    district                  String?
    preferredDeliveryPartner  String?
    deliveryPartner           DeliveryPartner?     @relation(fields: [preferredDeliveryPartner], references: [id])
    source                    OrderSource?         @default(WEBSITE)
    printedAt                 DateTime?
    integration               Integration?         @relation(fields: [integrationId], references: [id])
    integrationId             String?
    isDeliveryFree            Boolean              @default(false)
}

model Location {
    id                                  String                               @id @default(uuid())
    internalId                          String?
    internalName                        String?
    referenceId                         String?
    label                               String?
    description                         String?
    type                                LocationType                         @default(GENERAL)
    address                             String
    district                            String?
    division                            String?
    postCode                            String?
    country                             String?
    contactPerson                       String?
    phone                               String?
    latitude                            Decimal
    longitude                           Decimal
    company                             Company                              @relation(fields: [companyId], references: [id])
    companyId                           String
    deletedAt                           DateTime?
    createdAt                           DateTime                             @default(now())
    updatedAt                           DateTime                             @updatedAt
    locationSalesOrders                 SalesOrder[]                         @relation("Locations")
    pickUpSalesOrders                   SalesOrder[]                         @relation("PickupLocations")
    distributors                        Distributor[]
}

model Distributor {
    id                      String        @id @default(uuid())
    name                    String
    disabled                Boolean       @default(false)
    managerName             String?
    managerTitle            String?
    phone                   String?
    email                   String?
    additionalInformation   String?
    locations               Location[]
    type                    CustomerType  @default(DISTRIBUTOR)
    paymentMethod           PaymentMethod @default(CASH)
    paymentTerms            Int?
    salesOrders             SalesOrder[]
    lastSalesOrderCreatedAt DateTime?
    createdAt               DateTime      @default(now())
    updatedAt               DateTime      @updatedAt
    accountManagerId        String?
    accountManager          User?         @relation("AssignedDistributors", fields: [accountManagerId], references: [id])
    userId                  String
    user                    User          @relation(fields: [userId], references: [id])
    companyId               String
    company                 Company       @relation(fields: [companyId], references: [id])
    shortId                 Int           @unique @default(autoincrement())
    internalId              String?
    internalName            String?
    metadata                Json?
    customerTag             CustomerTag?  @relation(fields: [customerTagId], references: [id])
    customerTagId           Int?
    smsCount                Int           @default(0)
}

const productInclude = {
	productSpecifications: {
		include: {
			specification: {
				select: {
					label: true,
					type: true
				}
			}
		}
	}
} as Prisma.ProductInclude
if (bulkReadSalesOrderDto.inventory) {
	productInclude.inventoryItems = {
		where: {
			quantity: {
				gt: 0
			}
		}
	}
}
const findManyArgs = {
	where: {
		id: {
			in: bulkReadSalesOrderDto.ids
		},
		companyId: cid
	},
	include: {
		company: true,
		deliveryPlan: true,
		distributor: {
			include: {
				accountManager: true,
				locations: {
					where: {
						type: LocationType.BILLING
					}
				}
			}
		},
		location: true,
		pickUpLocation: true,
		transactions: true,
		salesOrderItems: {
			include: {
				product: {
					include: productInclude
				},
				salesOrderItemSpecifications: {
					include: {
						specification: {
							select: {
								label: true,
								type: true
							}
						}
					}
				},
				packaging: true,
				inventoryBatchItem: true
			}
		},
		deliveryPartner: {
			select: {
				id: true,
				name: true,
				type: true,
				partnerId: true,
				disabled: true
			}
		}
	}
} as Prisma.SalesOrderFindManyArgs
const salesOrders = await this.prisma.salesOrder.findMany(findManyArgs)

Here is the generated query from the Prisma logger:
SELECT
  "t1"."id",
  "t1"."internalId",
  "t1"."referenceId",
  "t1"."authorId",
  "t1"."distributorId",
  "t1"."locationId",
  "t1"."pickUpLocationId",
  "t1"."deliveryPlanId",
  "t1"."companyId",
  "t1"."deliveryDate",
  "t1"."paymentMethod" :: text,
  "t1"."distributorAdvancePayment",
  "t1"."totalPaidAmount",
  "t1"."totalDueAmount",
  "t1"."totalAmount",
  "t1"."totalBuyingAmount",
  "t1"."transportFareAmount",
  "t1"."discount",
  "t1"."discountAmount",
  "t1"."deliveryCharge",
  "t1"."additionalNotes",
  "t1"."internalNotes",
  "t1"."status" :: text,
  "t1"."subStatus" :: text,
  "t1"."deliveryStatus",
  "t1"."deliveryTrackingId",
  "t1"."deliveryTrackingUrl",
  "t1"."deliveryOrderId",
  "t1"."deliveryConsignment",
  "t1"."flagReason",
  "t1"."onHoldReason",
  "t1"."shortId",
  "t1"."isStockTransfer",
  "t1"."isReturn",
  "t1"."parentSalesOrderId",
  "t1"."copyCount",
  "t1"."staleness",
  "t1"."createdAt",
  "t1"."updatedAt",
  "t1"."orderDate",
  "t1"."exportedForDeliveryAt",
  "t1"."followUpDate",
  "t1"."unloadedAt",
  "t1"."deliveredAt",
  "t1"."approvedAt",
  "t1"."onHoldAt",
  "t1"."processedAt",
  "t1"."shippedAt",
  "t1"."inTransitAt",
  "t1"."flaggedAt",
  "t1"."returnedAt",
  "t1"."damagedAt",
  "t1"."cancelledAt",
  "t1"."metadata",
  "t1"."deliveryArea",
  "t1"."truckPlateNumber",
  "t1"."loadingBay",
  "t1"."district",
  "t1"."preferredDeliveryPartner",
  "t1"."source" :: text,
  "t1"."printedAt",
  "t1"."integrationId",
  "t1"."isDeliveryFree",
  "SalesOrder_company"."__prisma_data__" AS "company",
  "SalesOrder_deliveryPlan"."__prisma_data__" AS "deliveryPlan",
  "SalesOrder_distributor"."__prisma_data__" AS "distributor",
  "SalesOrder_location"."__prisma_data__" AS "location",
  "SalesOrder_pickUpLocation"."__prisma_data__" AS "pickUpLocation",
  "SalesOrder_transactions"."__prisma_data__" AS "transactions",
  "SalesOrder_salesOrderItems"."__prisma_data__" AS "salesOrderItems",
  "SalesOrder_deliveryPartner"."__prisma_data__" AS "deliveryPartner"
FROM
  "public"."SalesOrder" AS "t1"
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t4"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t3"."id", 'phone', "t3"."phone",
                'name', "t3"."name", 'tag', "t3"."tag",
                'address', "t3"."address", 'latitude',
                "t3"."latitude", 'longitude', "t3"."longitude",
                'country', "t3"."country", 'currency',
                "t3"."currency", 'disabled', "t3"."disabled",
                'website', "t3"."website", 'createdAt',
                "t3"."createdAt", 'updatedAt', "t3"."updatedAt"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t2".*
                FROM
                  "public"."Company" AS "t2"
                WHERE
                  "t1"."companyId" = "t2"."id"
                  /* root select */
                  ) AS "t3"
              /* inner select */
              ) AS "t4"
          /* middle select */
          ) AS "t5"
      /* outer select */
      ) AS "SalesOrder_company" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t8"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t7"."id", 'internalId', "t7"."internalId",
                'deliveryDate', "t7"."deliveryDate",
                'companyId', "t7"."companyId", 'shortId',
                "t7"."shortId", 'status', "t7"."status",
                'loadState', "t7"."loadState", 'runIds',
                "t7"."runIds", 'usableTruckWeights',
                "t7"."usableTruckWeights", 'createdAt',
                "t7"."createdAt", 'updatedAt', "t7"."updatedAt",
                'customized', "t7"."customized",
                'scalar', "t7"."scalar", 'mode',
                "t7"."mode", 'cancellationReason',
                "t7"."cancellationReason"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t6".*
                FROM
                  "public"."DeliveryPlan" AS "t6"
                WHERE
                  "t1"."deliveryPlanId" = "t6"."id"
                  /* root select */
                  ) AS "t7"
              /* inner select */
              ) AS "t8"
          /* middle select */
          ) AS "t9"
      /* outer select */
      ) AS "SalesOrder_deliveryPlan" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t12"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t11"."id", 'name', "t11"."name",
                'disabled', "t11"."disabled", 'managerName',
                "t11"."managerName", 'managerTitle',
                "t11"."managerTitle", 'phone', "t11"."phone",
                'email', "t11"."email", 'additionalInformation',
                "t11"."additionalInformation",
                'type', "t11"."type", 'paymentMethod',
                "t11"."paymentMethod", 'paymentTerms',
                "t11"."paymentTerms", 'lastSalesOrderCreatedAt',
                "t11"."lastSalesOrderCreatedAt",
                'createdAt', "t11"."createdAt",
                'updatedAt', "t11"."updatedAt",
                'accountManagerId', "t11"."accountManagerId",
                'userId', "t11"."userId", 'companyId',
                "t11"."companyId", 'shortId', "t11"."shortId",
                'internalId', "t11"."internalId",
                'internalName', "t11"."internalName",
                'metadata', "t11"."metadata", 'customerTagId',
                "t11"."customerTagId", 'smsCount',
                "t11"."smsCount", 'accountManagerId',
                "t11"."accountManagerId", 'accountManager',
                "Distributor_accountManager"."__prisma_data__",
                'locations', "Distributor_locations_m2m"."__prisma_data__"
              ) AS "__prisma_data__",
              "t11"."accountManagerId"
            FROM
              (
                SELECT
                  "t10".*
                FROM
                  "public"."Distributor" AS "t10"
                WHERE
                  "t1"."distributorId" = "t10"."id"
                  /* root select */
                  ) AS "t11"
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "t16"."__prisma_data__"
                    FROM
                      (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'id', "t15"."id", 'internalId', "t15"."internalId",
                            'name', "t15"."name", 'email', "t15"."email",
                            'phone', "t15"."phone", 'disabled',
                            "t15"."disabled", 'role', "t15"."role",
                            'companyId', "t15"."companyId",
                            'permissionGroupId', "t15"."permissionGroupId",
                            'vehicleTypes', "t15"."vehicleTypes",
                            'createdAt', "t15"."createdAt",
                            'updatedAt', "t15"."updatedAt",
                            'team', "t15"."team", 'lastUnassignedTripId',
                            "t15"."lastUnassignedTripId", 'metadata',
                            "t15"."metadata"
                          ) AS "__prisma_data__"
                        FROM
                          (
                            SELECT
                              "t14".*
                            FROM
                              "public"."User" AS "t14"
                            WHERE
                              "t11"."accountManagerId" = "t14"."id"
                              /* root select */
                              ) AS "t15"
                          /* inner select */
                          ) AS "t16"
                      /* middle select */
                      ) AS "t17"
                  /* outer select */
                  ) AS "Distributor_accountManager" ON true
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "Distributor_locations"."__prisma_data__"
                    FROM
                      "public"."_DistributorToLocation" AS "t18"
                      LEFT JOIN LATERAL (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'id', "t20"."id", 'internalId', "t20"."internalId",
                            'internalName', "t20"."internalName",
                            'referenceId', "t20"."referenceId",
                            'label', "t20"."label", 'description',
                            "t20"."description", 'type', "t20"."type",
                            'address', "t20"."address", 'district',
                            "t20"."district", 'division', "t20"."division",
                            'postCode', "t20"."postCode", 'country',
                            "t20"."country", 'contactPerson',
                            "t20"."contactPerson", 'phone',
                            "t20"."phone", 'latitude', "t20"."latitude",
                            'longitude', "t20"."longitude",
                            'companyId', "t20"."companyId",
                            'deletedAt', "t20"."deletedAt",
                            'createdAt', "t20"."createdAt",
                            'updatedAt', "t20"."updatedAt"
                          ) AS "__prisma_data__",
                          "t20"."id"
                        FROM
                          (
                            SELECT
                              "t19".*
                            FROM
                              "public"."Location" AS "t19"
                            WHERE
                              "t18"."B" = "t19"."id"
                              /* root select */
                              ) AS "t20"
                      ) AS "Distributor_locations" ON true
                    WHERE
                      (
                        "t18"."A" = "t11"."id"
                        AND "public"."Location"."type" = CAST(
                          $1 :: text AS "public"."LocationType"
                        )
                      )
                  ) AS "Distributor_locations_m2m_1"
              ) AS "Distributor_locations_m2m" ON true
              /* inner select */
              ) AS "t12"
          /* middle select */
          ) AS "t13"
      /* outer select */
      ) AS "SalesOrder_distributor" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t25"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t24"."id", 'internalId', "t24"."internalId",
                'internalName', "t24"."internalName",
                'referenceId', "t24"."referenceId",
                'label', "t24"."label", 'description',
                "t24"."description", 'type', "t24"."type",
                'address', "t24"."address", 'district',
                "t24"."district", 'division', "t24"."division",
                'postCode', "t24"."postCode", 'country',
                "t24"."country", 'contactPerson',
                "t24"."contactPerson", 'phone',
                "t24"."phone", 'latitude', "t24"."latitude",
                'longitude', "t24"."longitude",
                'companyId', "t24"."companyId",
                'deletedAt', "t24"."deletedAt",
                'createdAt', "t24"."createdAt",
                'updatedAt', "t24"."updatedAt"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t23".*
                FROM
                  "public"."Location" AS "t23"
                WHERE
                  "t1"."locationId" = "t23"."id"
                  /* root select */
                  ) AS "t24"
              /* inner select */
              ) AS "t25"
          /* middle select */
          ) AS "t26"
      /* outer select */
      ) AS "SalesOrder_location" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t29"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t28"."id", 'internalId', "t28"."internalId",
                'internalName', "t28"."internalName",
                'referenceId', "t28"."referenceId",
                'label', "t28"."label", 'description',
                "t28"."description", 'type', "t28"."type",
                'address', "t28"."address", 'district',
                "t28"."district", 'division', "t28"."division",
                'postCode', "t28"."postCode", 'country',
                "t28"."country", 'contactPerson',
                "t28"."contactPerson", 'phone',
                "t28"."phone", 'latitude', "t28"."latitude",
                'longitude', "t28"."longitude",
                'companyId', "t28"."companyId",
                'deletedAt', "t28"."deletedAt",
                'createdAt', "t28"."createdAt",
                'updatedAt', "t28"."updatedAt"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t27".*
                FROM
                  "public"."Location" AS "t27"
                WHERE
                  "t1"."pickUpLocationId" = "t27"."id"
                  /* root select */
                  ) AS "t28"
              /* inner select */
              ) AS "t29"
          /* middle select */
          ) AS "t30"
      /* outer select */
      ) AS "SalesOrder_pickUpLocation" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t33"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t32"."id", 'authorId', "t32"."authorId",
                'payerId', "t32"."payerId", 'payerResource',
                "t32"."payerResource", 'payeeId',
                "t32"."payeeId", 'payeeResource',
                "t32"."payeeResource", 'paymentOption',
                "t32"."paymentOption", 'paymentStatus',
                "t32"."paymentStatus", 'type', "t32"."type",
                'additionalNotes', "t32"."additionalNotes",
                'amount', "t32"."amount", 'salesOrderId',
                "t32"."salesOrderId", 'purchaseOrderId',
                "t32"."purchaseOrderId", 'createdAt',
                "t32"."createdAt", 'updatedAt',
                "t32"."updatedAt"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t31".*
                FROM
                  "public"."Transaction" AS "t31"
                WHERE
                  "t1"."id" = "t31"."salesOrderId"
                  /* root select */
                  ) AS "t32"
              /* inner select */
              ) AS "t33"
          /* middle select */
          ) AS "t34"
      /* outer select */
      ) AS "SalesOrder_transactions" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t37"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t36"."id", 'productId', "t36"."productId",
                'salesOrderId', "t36"."salesOrderId",
                'packageQuantity', "t36"."packageQuantity",
                'packageId', "t36"."packageId",
                'quantity', "t36"."quantity", 'quantityUnit',
                "t36"."quantityUnit", 'totalWeight',
                "t36"."totalWeight", 'totalWeightUnit',
                "t36"."totalWeightUnit", 'totalVolume',
                "t36"."totalVolume", 'totalVolumeUnit',
                "t36"."totalVolumeUnit", 'discount',
                "t36"."discount", 'discountAmount',
                "t36"."discountAmount", 'price',
                "t36"."price", 'buyingPrice', "t36"."buyingPrice",
                'productUnit', "t36"."productUnit",
                'deliveredQuantity', "t36"."deliveredQuantity",
                'deliveredPackageQuantity', "t36"."deliveredPackageQuantity",
                'flaggedQuantity', "t36"."flaggedQuantity",
                'createdAt', "t36"."createdAt",
                'updatedAt', "t36"."updatedAt",
                'inventoryItemId', "t36"."inventoryItemId",
                'inventoryBatchItemId', "t36"."inventoryBatchItemId",
                'approvedQuantity', "t36"."approvedQuantity",
                'approvedPackageQuantity', "t36"."approvedPackageQuantity",
                'isUpsell', "t36"."isUpsell", 'productId',
                "t36"."productId", 'product', "SalesOrderItem_product"."__prisma_data__",
                'salesOrderItemSpecifications',
                "SalesOrderItem_salesOrderItemSpecifications"."__prisma_data__",
                'packageId', "t36"."packageId",
                'packaging', "SalesOrderItem_packaging"."__prisma_data__",
                'inventoryBatchItemId', "t36"."inventoryBatchItemId",
                'inventoryBatchItem', "SalesOrderItem_inventoryBatchItem"."__prisma_data__"
              ) AS "__prisma_data__",
              "t36"."productId",
              "t36"."id",
              "t36"."packageId",
              "t36"."inventoryBatchItemId"
            FROM
              (
                SELECT
                  "t35".*
                FROM
                  "public"."SalesOrderItem" AS "t35"
                WHERE
                  "t1"."id" = "t35"."salesOrderId"
                  /* root select */
                  ) AS "t36"
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "t41"."__prisma_data__"
                    FROM
                      (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'id', "t40"."id", 'summary', "t40"."summary",
                            'name', "t40"."name", 'companyId',
                            "t40"."companyId", 'imageUrls',
                            "t40"."imageUrls", 'price', "t40"."price",
                            'salePrice', "t40"."salePrice",
                            'resellPrice', "t40"."resellPrice",
                            'purchasePrice', "t40"."purchasePrice",
                            'retailPrice', "t40"."retailPrice",
                            'distributorPrice', "t40"."distributorPrice",
                            'dealerPrice', "t40"."dealerPrice",
                            'traderPrice', "t40"."traderPrice",
                            'microEntrepreneurPrice', "t40"."microEntrepreneurPrice",
                            'corporatePrice', "t40"."corporatePrice",
                            'eCommerceCustomerPrice', "t40"."eCommerceCustomerPrice",
                            'currency', "t40"."currency", 'sku',
                            "t40"."sku", 'barcode', "t40"."barcode",
                            'position', "t40"."position", 'shelfLife',
                            "t40"."shelfLife", 'category', "t40"."category",
                            'subCategory1', "t40"."subCategory1",
                            'subCategory2', "t40"."subCategory2",
                            'subCategory3', "t40"."subCategory3",
                            'subCategory4', "t40"."subCategory4",
                            'subCategory5', "t40"."subCategory5",
                            'parentProductId', "t40"."parentProductId",
                            'internalId', "t40"."internalId",
                            'industry', "t40"."industry", 'deleted',
                            "t40"."deleted", 'createdAt', "t40"."createdAt",
                            'updatedAt', "t40"."updatedAt",
                            'metadata', "t40"."metadata", 'type',
                            "t40"."type", 'integrationId', "t40"."integrationId",
                            'productSpecifications', "Product_productSpecifications"."__prisma_data__",
                            'inventoryItems', "Product_inventoryItems"."__prisma_data__"
                          ) AS "__prisma_data__",
                          "t40"."id"
                        FROM
                          (
                            SELECT
                              "t39".*
                            FROM
                              "public"."Product" AS "t39"
                            WHERE
                              "t36"."productId" = "t39"."id"
                              /* root select */
                              ) AS "t40"
                          LEFT JOIN LATERAL (
                            SELECT
                              COALESCE(
                                JSON_AGG("__prisma_data__"),
                                '[]'
                              ) AS "__prisma_data__"
                            FROM
                              (
                                SELECT
                                  "t45"."__prisma_data__"
                                FROM
                                  (
                                    SELECT
                                      JSON_BUILD_OBJECT(
                                        'productId', "t44"."productId", 'specificationCompanyId',
                                        "t44"."specificationCompanyId",
                                        'specificationKey', "t44"."specificationKey",
                                        'value', "t44"."value", 'unit', "t44"."unit",
                                        'specificationCompanyId', "t44"."specificationCompanyId",
                                        'specificationKey', "t44"."specificationKey",
                                        'specification', "ProductSpecification_specification"."__prisma_data__"
                                      ) AS "__prisma_data__",
                                      "t44"."specificationCompanyId",
                                      "t44"."specificationKey"
                                    FROM
                                      (
                                        SELECT
                                          "t43".*
                                        FROM
                                          "public"."ProductSpecification" AS "t43"
                                        WHERE
                                          "t40"."id" = "t43"."productId"
                                          /* root select */
                                          ) AS "t44"
                                      LEFT JOIN LATERAL (
                                        SELECT
                                          COALESCE(
                                            JSON_AGG("__prisma_data__"),
                                            '[]'
                                          ) AS "__prisma_data__"
                                        FROM
                                          (
                                            SELECT
                                              "t49"."__prisma_data__"
                                            FROM
                                              (
                                                SELECT
                                                  JSON_BUILD_OBJECT(
                                                    'label', "t48"."label", 'type', "t48"."type"
                                                  ) AS "__prisma_data__"
                                                FROM
                                                  (
                                                    SELECT
                                                      "t47".*
                                                    FROM
                                                      "public"."Specification" AS "t47"
                                                    WHERE
                                                      (
                                                        "t44"."specificationCompanyId" = "t47"."companyId"
                                                        AND "t44"."specificationKey" = "t47"."key"
                                                      )
                                                      /* root select */
                                                      ) AS "t48"
                                                  /* inner select */
                                                  ) AS "t49"
                                              /* middle select */
                                              ) AS "t50"
                                          /* outer select */
                                          ) AS "ProductSpecification_specification" ON true
                                      /* inner select */
                                      ) AS "t45"
                                  /* middle select */
                                  ) AS "t46"
                              /* outer select */
                              ) AS "Product_productSpecifications" ON true
                          LEFT JOIN LATERAL (
                            SELECT
                              COALESCE(
                                JSON_AGG("__prisma_data__"),
                                '[]'
                              ) AS "__prisma_data__"
                            FROM
                              (
                                SELECT
                                  "t53"."__prisma_data__"
                                FROM
                                  (
                                    SELECT
                                      JSON_BUILD_OBJECT(
                                        'id', "t52"."id", 'productId', "t52"."productId",
                                        'quantity', "t52"."quantity", 'wastageQuantity',
                                        "t52"."wastageQuantity", 'expiredQuantity',
                                        "t52"."expiredQuantity", 'locationId',
                                        "t52"."locationId", 'companyId',
                                        "t52"."companyId", 'batchNumber',
                                        "t52"."batchNumber", 'createdAt',
                                        "t52"."createdAt", 'updatedAt',
                                        "t52"."updatedAt"
                                      ) AS "__prisma_data__",
                                      "t52"."quantity"
                                    FROM
                                      (
                                        SELECT
                                          "t51".*
                                        FROM
                                          "public"."InventoryItem" AS "t51"
                                        WHERE
                                          "t40"."id" = "t51"."productId"
                                          /* root select */
                                          ) AS "t52"
                                      /* inner select */
                                      ) AS "t53"
                                WHERE
                                  "t53"."quantity" > $2
                                  /* middle select */
                                  ) AS "t54"
                              /* outer select */
                              ) AS "Product_inventoryItems" ON true
                          /* inner select */
                          ) AS "t41"
                      /* middle select */
                      ) AS "t42"
                  /* outer select */
                  ) AS "SalesOrderItem_product" ON true
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "t57"."__prisma_data__"
                    FROM
                      (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'salesOrderItemId', "t56"."salesOrderItemId",
                            'specificationCompanyId', "t56"."specificationCompanyId",
                            'specificationKey', "t56"."specificationKey",
                            'value', "t56"."value", 'unit', "t56"."unit",
                            'specificationCompanyId', "t56"."specificationCompanyId",
                            'specificationKey', "t56"."specificationKey",
                            'specification', "SalesOrderItemSpecification_specification"."__prisma_data__"
                          ) AS "__prisma_data__",
                          "t56"."specificationCompanyId",
                          "t56"."specificationKey"
                        FROM
                          (
                            SELECT
                              "t55".*
                            FROM
                              "public"."SalesOrderItemSpecification" AS "t55"
                            WHERE
                              "t36"."id" = "t55"."salesOrderItemId"
                              /* root select */
                              ) AS "t56"
                          LEFT JOIN LATERAL (
                            SELECT
                              COALESCE(
                                JSON_AGG("__prisma_data__"),
                                '[]'
                              ) AS "__prisma_data__"
                            FROM
                              (
                                SELECT
                                  "t61"."__prisma_data__"
                                FROM
                                  (
                                    SELECT
                                      JSON_BUILD_OBJECT(
                                        'label', "t60"."label", 'type', "t60"."type"
                                      ) AS "__prisma_data__"
                                    FROM
                                      (
                                        SELECT
                                          "t59".*
                                        FROM
                                          "public"."Specification" AS "t59"
                                        WHERE
                                          (
                                            "t56"."specificationCompanyId" = "t59"."companyId"
                                            AND "t56"."specificationKey" = "t59"."key"
                                          )
                                          /* root select */
                                          ) AS "t60"
                                      /* inner select */
                                      ) AS "t61"
                                  /* middle select */
                                  ) AS "t62"
                              /* outer select */
                              ) AS "SalesOrderItemSpecification_specification" ON true
                          /* inner select */
                          ) AS "t57"
                      /* middle select */
                      ) AS "t58"
                  /* outer select */
                  ) AS "SalesOrderItem_salesOrderItemSpecifications" ON true
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "t65"."__prisma_data__"
                    FROM
                      (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'id', "t64"."id", 'name', "t64"."name",
                            'productId', "t64"."productId",
                            'type', "t64"."type", 'width', "t64"."width",
                            'widthUnit', "t64"."widthUnit",
                            'height', "t64"."height", 'heightUnit',
                            "t64"."heightUnit", 'length', "t64"."length",
                            'lengthUnit', "t64"."lengthUnit",
                            'volume', "t64"."volume", 'volumeUnit',
                            "t64"."volumeUnit", 'size', "t64"."size",
                            'sizeUnit', "t64"."sizeUnit", 'createdAt',
                            "t64"."createdAt", 'updatedAt',
                            "t64"."updatedAt"
                          ) AS "__prisma_data__"
                        FROM
                          (
                            SELECT
                              "t63".*
                            FROM
                              "public"."Package" AS "t63"
                            WHERE
                              "t36"."packageId" = "t63"."id"
                              /* root select */
                              ) AS "t64"
                          /* inner select */
                          ) AS "t65"
                      /* middle select */
                      ) AS "t66"
                  /* outer select */
                  ) AS "SalesOrderItem_packaging" ON true
              LEFT JOIN LATERAL (
                SELECT
                  COALESCE(
                    JSON_AGG("__prisma_data__"),
                    '[]'
                  ) AS "__prisma_data__"
                FROM
                  (
                    SELECT
                      "t69"."__prisma_data__"
                    FROM
                      (
                        SELECT
                          JSON_BUILD_OBJECT(
                            'id', "t68"."id", 'inventoryItemId',
                            "t68"."inventoryItemId", 'packageId',
                            "t68"."packageId", 'productId',
                            "t68"."productId", 'locationId',
                            "t68"."locationId", 'companyId',
                            "t68"."companyId", 'quantity', "t68"."quantity",
                            'wastageQuantity', "t68"."wastageQuantity",
                            'expiredQuantity', "t68"."expiredQuantity",
                            'manufactureDate', "t68"."manufactureDate",
                            'expiryDate', "t68"."expiryDate",
                            'batchNumber', "t68"."batchNumber",
                            'createdAt', "t68"."createdAt",
                            'updatedAt', "t68"."updatedAt"
                          ) AS "__prisma_data__"
                        FROM
                          (
                            SELECT
                              "t67".*
                            FROM
                              "public"."InventoryBatchItem" AS "t67"
                            WHERE
                              "t36"."inventoryBatchItemId" = "t67"."id"
                              /* root select */
                              ) AS "t68"
                          /* inner select */
                          ) AS "t69"
                      /* middle select */
                      ) AS "t70"
                  /* outer select */
                  ) AS "SalesOrderItem_inventoryBatchItem" ON true
              /* inner select */
              ) AS "t37"
          /* middle select */
          ) AS "t38"
      /* outer select */
      ) AS "SalesOrder_salesOrderItems" ON true
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSON_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t73"."__prisma_data__"
        FROM
          (
            SELECT
              JSON_BUILD_OBJECT(
                'id', "t72"."id", 'name', "t72"."name",
                'type', "t72"."type", 'partnerId',
                "t72"."partnerId", 'disabled', "t72"."disabled"
              ) AS "__prisma_data__"
            FROM
              (
                SELECT
                  "t71".*
                FROM
                  "public"."DeliveryPartner" AS "t71"
                WHERE
                  "t1"."preferredDeliveryPartner" = "t71"."id"
                  /* root select */
                  ) AS "t72"
              /* inner select */
              ) AS "t73"
          /* middle select */
          ) AS "t74"
      /* outer select */
      ) AS "SalesOrder_deliveryPartner" ON true
WHERE
  (
    "t1"."id" IN (
      $3, $4, $5, $6, $7, $8, $9, $10, $11, $12,
      $13, $14, $15, $16, $17, $18, $19, $20,
      $21, $22, $23, $24, $25, $26, $27, $28,
      $29, $30, $31, $32, $33, $34, $35
    )
    AND "t1"."companyId" = $36
  )

From the Logger in GCP I see this log from Postgres before the error is thrown:
db=postgres,user=postgres ERROR:  missing FROM-clause entry for table "Location" at character 6743

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.7.0

Prisma Version
prisma                  : 5.7.0
@prisma/client          : 5.7.0
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v18.7.0
Query Engine (Node-API) : libquery-engine 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.7.0-41.79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Default Engines Hash    : 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Studio                  : 0.495.0
Preview Features        : fullTextSearch, postgresqlExtensions, relationJoins

That is one juicy Prisma Client query, and the generated SQL query as well.
Thanks for all this information, we are going to look into it.

Don't know if this is helpful or not, we've encountered the same problem when doing a test-upgrade to v5.7:

Let me know if we can add some more details here that @Crymzix has not already added :+1:

Did you also enable the relationJoins preview feature @BracketJohn when you got that?

I am also getting this error after enabling "relationJoins". it works fine if I remove "relationJoins" from preview features.
PrismaClientKnownRequestError:
Invalid `prisma.user.findUnique()` invocation:

The table `(not available)` does not exist in the current database.
    at si.handleRequestError (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:6817)
    at si.handleAndLogRequestError (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:6151)
    at si.request (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:5859)
    at async l (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:130:10025)
    at async D (/home/sck/Projects/shop/.next/server/pages/api/graphql.js:3397:13179)
    at async m (/home/sck/Projects/shop/.next/server/pages/api/graphql.js:3397:11389)
    at async f (/home/sck/Projects/shop/.next/server/pages/api/graphql.js:3397:11200)
    at async _ (/home/sck/Projects/shop/.next/server/pages/api/graphql.js:3397:17015) {
  code: 'P2021',
  clientVersion: '5.7.0',
  meta: { modelName: 'User', table: '(not available)' }
}

query is:
    const userResp = await prisma.user.findUnique({
      where: {
        id: userID,
      },

      select: {

        followings: {
          where: {
            age: null,
          },

          select: {
            id: true,
          }
        },

      }
    })

Hey, we are releasing a 5.7.1 patch for this bug. Make sure to try it out as soon as it's out to confirm it's fixed! Thanks for the report 🙏

Hi there, I'm still encountering this bug on 5.7.1, but with a different query
PrismaClientKnownRequestError:
Invalid `prisma.question.findUnique()` invocation:

The column `t8.id` does not exist in the current database.
    at si.handleRequestError (<redacted>/node_modules/@prisma/client/runtime/library.js:125:6817)
    at si.handleAndLogRequestError (<redacted>/node_modules/@prisma/client/runtime/library.js:125:6151)
    at si.request (<redacted>/node_modules/@prisma/client/runtime/library.js:125:5859)
    at async l (<redacted>/node_modules/@prisma/client/runtime/library.js:130:10025)
    at async eval (<redacted>/src/lib/datamodel/v0/question/reader.ts:141:26)
    at async Proxy._transactionWithCallback (<redacted>/node_modules/@prisma/client/runtime/library.js:130:8688)
    at async PrismaQuestionReader.getQuestionNavigationData (<redacted>/src/lib/datamodel/v0/question/reader.ts:140:14)
    at async load (<redacted>/src/routes/(app)/projects/[id]/questions/[questionId]/+page.server.ts?sentry-auto-wrap:41:36) {
  code: 'P2022',
  clientVersion: '5.7.1',
  meta: { modelName: 'Question', column: 't8.id' }
}

The query I'm using is:
const question = await tx.question.findUnique({
        where: {
          id: questionId
        },
        include: {
          section: {
            include: {
              questions: {
                orderBy: {
                  gridExtractionMetadata: {
                    answerRow: 'asc'
                  }
                }
              }
            }
          }
        }
      })

Hi there, I'm still encountering this bug on 5.7.1, but with a different query
PrismaClientKnownRequestError:
Invalid `prisma.question.findUnique()` invocation:

The column `t8.id` does not exist in the current database.
    at si.handleRequestError (<redacted>/node_modules/@prisma/client/runtime/library.js:125:6817)
    at si.handleAndLogRequestError (<redacted>/node_modules/@prisma/client/runtime/library.js:125:6151)
    at si.request (<redacted>/node_modules/@prisma/client/runtime/library.js:125:5859)
    at async l (<redacted>/node_modules/@prisma/client/runtime/library.js:130:10025)
    at async eval (<redacted>/src/lib/datamodel/v0/question/reader.ts:141:26)
    at async Proxy._transactionWithCallback (<redacted>/node_modules/@prisma/client/runtime/library.js:130:8688)
    at async PrismaQuestionReader.getQuestionNavigationData (<redacted>/src/lib/datamodel/v0/question/reader.ts:140:14)
    at async load (<redacted>/src/routes/(app)/projects/[id]/questions/[questionId]/+page.server.ts?sentry-auto-wrap:41:36) {
  code: 'P2022',
  clientVersion: '5.7.1',
  meta: { modelName: 'Question', column: 't8.id' }
}

The query I'm using is:
const question = await tx.question.findUnique({
        where: {
          id: questionId
        },
        include: {
          section: {
            include: {
              questions: {
                orderBy: {
                  gridExtractionMetadata: {
                    answerRow: 'asc'
                  }
                }
              }
            }
          }
        }
      })

Indeed, I continue to encounter the aforementioned issue despite the update, as it has partially resolved some of the errors. However, the problem persists, particularly when implementing a WHERE clause that verifies a field within an inner relation.

Despite implementing the update, the aforementioned issue persists, albeit with certain errors partially resolved. Regrettably, the problem lingers, particularly when incorporating the orderBy clause into my queries, as indicated by @michaelchen01
The column `t4.ownerID` does not exist in the current database.
    at si.handleRequestError (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:6817)
    at si.handleAndLogRequestError (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:6151)
    at si.request (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:125:5859)
    at async l (/home/sck/Projects/shop/node_modules/@prisma/client/runtime/library.js:130:10025)
    at async u (/home/sck/Projects/shop/.next/server/pages/api/graphql.js:3397:13118) {
  code: 'P2022',
  clientVersion: '5.7.1',
  meta: { modelName: 'User', column: 't4.ownerID' }
}

I neither select nor utilize the ownerID in the where/select/orderBy clause whatsoever. It is worth noting that the message correctly states that ownerID does not exist in the User table. However, as previously mentioned, I do not include it in my selection nor employ it in the queries. Furthermore, in the absence of relationJoins this findUnique query executes without any issues. Therefore, it appears that relationJoins is somehow merging different tables.

Thanks @michaelchen01 and @SC0d3r, seems we did not get all the cases then :( Can one of you please open a new issue for this? We would like to reproduce and then hopefully fix this - and that works better with the full information. So please make sure that we have a full query and schema to reproduce the error, optimally even a reproduction project in a Github repo. Thanks!


Possible to run on ATtiny?

Hey,
I've been looking through the code to see if it is possible to run this code on an ATtiny (1614 for instance) and was curious if you had any input. I would love to run this code on an ATtiny with a FTDI chip (or any other USB to Serial converter). I see that there are a lot of instances of it mentioning being compiled on Series-0 and Series-1 tinyAVR devices. I understand that your modifications use Port C (on the ATmega devices) and I don't really need that sort of feedback for my implementation. Just curious what you think.
Thoughts?

Yes, I've had a version of this firmware running a on an ATtiny1604 (with optiboot) and used an FTDI LC231X Module for the serial connection to the PC. For target power cycle, I used an external power switch. The Nano HV Programmer uses Port C on the ATmega328P for target power and power-cycle. I didn't release anything as I've decided to opt for the AVR DA for a more advanced programmer with the capability of setting the target voltage from 3V-5V in a few mV per step.  Neat thing is that the AVR DA could also operate from 3V-5V without changing the MCU frequency, which saves level translator switching components.
In order to use the ATtiny1614 as a programmer,#if defined (__AVR_ATtiny1614__) wrappers around the required programmer functions and code blocks need to be added to the firmware.

Is there any reason you used Optiboot? Is it needed for something that I'm not thinking about?

Optiboot allowed programming with the FTDI serial adapter (like an Arduino) and using the UPDI pin configured as Reset, which is connected to an auto-reset circuit and DTR. When auto-reset is disabled, the ATtiny with jtag2updi firmware operates as a programmer. When auto-reset is enabled, the programmer's firmware is updated during an upload.
You could avoid optiboot if you dedicate an extra pin configured with a reset interrupt function.

I was thinking I could just keep the UPDI port for uploading.
The problem I am having is that even though I think I've made all the proper changes to the code, it doesn't seem to respond to anything. I got a bunch of avrdude: jtagmkII_getsync(): sign-on command: status -1 errors when trying to program another ATtiny with it. I put an oscilloscope probe on the TX and RX pins (between the FTDI chip and the ATtiny programmer) but it seems that it doesn't respond. I've attached a picture of the oscilloscope output on the FTDI chip. Not sure if that is helpful.

Yeah, data flow back to the serial port won't happen until after sign-on.
I have all the pieces tested that would match up with the features of the Nano HV UPDI Programmer ... so I'll do some copy and paste from my various revisions and come up with something to publish. This should be easier to work with for your implementation. However, may need a week at the most.

Thanks so much. I can't wait!

Its ready ... see Wiki for documentation.

Sweet! I'll try it out tonight. How did you create that pinout chart? I've seen them all over but want to know how they are made.

Just an original pinout edited with Paint 3D. I stumbled upon an open source application and youtube video a while back, but can't think of what its called.


Always output FObject id

Ref

https://nanopay.atlassian.net/browse/NP-2889

Issues

JSON output for model having multipart id doesn't contain the properties (of the multipart id) on update

Changes

Always output id although it can be transient or multipart id to ensure that the entry/record is identifiable on replay.

Do not merge. I want to look into this a bit first.


Swagger file validation issues for fileshare acl

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
When we create fileshare spec with swagger validation enabled, below 2 issues are faced

tenantId is treated as mandatory which is not correct
accessCapability is treated as string which should be array of string

Swagger files snapshots:

What you expected to happen:
Swagger file updated needed for

Removing tenantId from "required" list
Updating accessCapability type to array of strings

Probable fix which need to be checked further

How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Hotpot(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Fixed, Closing now!!!


Click Handling can't distinguish identical tasks

If I have a list with identical tasks, like so:

[ ] Task A
[ ] Task B

[ ] Task C
[ ] Task A

And I click the checkbox of the bottom-most Task A, it will bring up the mark modal, but it will mark the TOP-most Task A as completed. Instead of marking the task my cursor is clicking, it will find the first task in the document matching the task text and mark that one as completed. If there are multiple Task A's, it will always mark the first Task A instead of the correct one under the cursor. This behavior is not observed when just right-clicking and selecting the TC modal from the context menu.
I understand this is probably a symptom of how the addon works (searching for the task text in order to select it), but is it possible to fix?
TC is the only community plugin I have installed.
TC version 1.0.13
Obsidian version 1.4.16

I'll see what I can do. I think the issue (if you want to play with some inspection) is the data available in the event to figure out which task it is). There is meta-information in reading mode, IIRC, that is not present in live preview.

Hmm. I can't reproduce this with 1.0.16 against 1.5.7.
Reading mode or Live preview?

I can't reproduce this issue.


Enhance pm_data_complete to deal with exception

Functionality for PM2.5 CAAQS calculation has been implemented, including evaluating data completeness criteria. However, pm_data_complete currently does not deal with the exception to the data completeness criteria as outlined in the Guidance Document (pages 11). It should be enhanced to do so.

The rcaaqs README demonstrates the pm_data_complete function and highlights the step where, at this time, the exception is captured. This issue should incorporate this step into the pm_data_complete function.
`## Then join the results to the data completeness data frame and select
only the results that are valid. This process could be more efficent
ann_98_per <- left_join(ann_98_per, pm_completeness,
by = c("ems_id", "year"))
ann_98_per <- filter(ann_98_per, use_annual | (exceed & annual_valid))
glimpse(ann_98_per)
#> Observations: 23
#> Variables: 15
#> $ ems_id                "0220205", "0310162", "0310162", "0310162...
#> $ year                  2012, 2011, 2012, 2013, 2011, 2012, 2013,...`


remove soil plant hydrology example

Purpose
We are not actively using the soil-plant hydrology only example. It is useful primarily for debugging but we havent used it in a while. the realism is quite limited (prescribed evaporation, for example) so we dont think it will be that useful.
To-do
Content
Removes the soil_plant_hydrology_model.jl
Moves the root_flux_per_ground_area and the RootExtraction source definitions to soil_canopy_model.jl (previously, both soil+plant models used the same methods and those were defined in soil_plant_hydrology_model.jl)
Removes the experiment from buildkite which runs the simulation.
Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[X] I have read and checked the items on the review checklist.

bors r+


Can't get 4.2-snapshot with Travis

Your instructions suggest this should work:
-  SWIFT_VERSION=DEVELOPMENT-SNAPSHOT-2018-06-20-a
(as part of the ENV)
But I get this error:
We don't have build instructions for DEVELOPMENT-SNAPSHOT-2018-06-20-a.

Any way to get this snapshot installed? Or maybe I'm doing something else wrong.
https://github.com/mxcl/PromiseKit/blob/master/.travis.yml#L37
Thanks!

https://swift.org/builds/development/ubuntu1610/swift-DEVELOPMENT-SNAPSHOT-2018-06-20-a/swift-DEVELOPMENT-SNAPSHOT-2018-06-20-a-ubuntu16.10.tar.gz

Looks like the snapshot is not reflected in https://github.com/kylef/swiftenv-api yet.

I added recent snapshots by hand so that should work now.
/cc @kylef

Aah, this is where it looks. Can I add this to the docs? Maybe under the install section?

I think that makes sense in regards to documenting where the versions are looked up, the API is somewhat auto updating (checks for new versions every ~20 minutes and publishes them to the API). There was a hiccup with my network on that particular day that caused a few days delay.
NOTE, all major versions of Swift can be installed from binaries without querying the API. They contain "cache" URLs for the swift binaries found in
https://github.com/kylef/swiftenv/tree/master/share/swiftenv-install. If the version isn't found in the cache contained in swiftenv releases it will be looked up via the API (this can be due to newer released versions that what swiftenv is aware of at installation time).


Disable cookie page notification banner autofocus

Stop the notification banner used in the example from stealing focus when the iframe loads.
This is consistent with the approach used in other auto-focusing components in the Design System – for example, the ‘success’ example in the notification banner component guidance.

You can preview this change here:
Built with commit 755df6f2ceacb4d902409ecd80e458d0fbb8a6c1
https://deploy-preview-1497--govuk-design-system-preview.netlify.app


Fix ViewGroup.removeView NullPointerException (#450)

Just add a null check.
Connection with issue(s)
Resolve issue #450

Because my latest commit changed a lot of things, I will add manually this fix in the next one! Thanks 👍


[Config] TOML Configs for master-datasources.xml

The corresponding TOML configs in the master-datasources.xml are required as they are referred in [1]:

maxActive
maxWait
minIdle
maxIdle
testOnBorrow
validationInterval
validationQuery
MaxPermSize

[1] https://is.docs.wso2.com/en/5.9.0/administer/performance-tuning/#jdbc-pool-configuration

These properties has to be defined under the [database.identity_db.pool_options].
[database.identity_db.pool_options]
maxActive = ""
maxWait = ""
minIdle = ""
maxIdle = ""
testOnBorrow = ""
validationInterval  = ""
validationQuery = ""
MaxPermSize = ""

Note that these configs will be applied to the  identity_db. We need to configure the same for the other dbs

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Serious Sam 3 anonymous download

Serious Sam 3 dedicated server no longer needs a username and password due to politely asking for it to be added to the Anonymous Dedicated Server Comp. This is just a low priority heads up.

https://github.com/dgibbs64/linuxgsm/commit/33765d9e83703827eb999c46c940dec74cfc38ce


Hub is using stale PR message

Hello, I've been seeing a strange issue with hub where it's stuck with an old PR message. No matter what branch I'm trying to send a pull request from, it's always showing that same old PR message.
Update: Uninstalling hub and re-installing didn't fix the issue. And it has also started giving me this error:
Error creating pull request: Unprocessable Entity (HTTP 422)
Invalid value for "head"

I am also having this issue.

Hi @Saketme, I'm sorry that you're having trouble. Can you try removing the file .git/PULLREQ_EDITMSG from your repo and trying again? Does the stale pull request message persist even after you've sucessfully opened a pull request? What OS is this on and which hub version are you using?

So lately this has stopped happening. I'm no longer seeing stale messages and I don't know how to reproduce it. I'll try removing PULLREQ_EDITMSG the next it happens.
Also, the -a flag seems to have stopped working for assigning someone to a PR. I know it's not a stable feature, but I just wanted to confirm if I'm doing something wrong?

I'm already looking into problems with -a. I will make a new prerelease once that's fixed. But if you have no other issues, please close this one. If you do have other issues, please enable debug mode with HUB_VERBOSE=1 hub ... and send any info that stands out to you. Thanks!

Sure


read_launch_plists.py Throws an Error

Error is in line 87:  iterator should return strings, not bytes (did you open the file in text mode?)
Tested in a VM, so it's the default experience if you open on the stock OS. Also I'm using the version of python that comes with the dev tools. I think a script like this ought to work OOTB.

I am not even sure the launchd stuff is useful anymore, as it was implemented long before SIP and other protections, features and startup methods existed. The guide no longer has references to any of the files either. The Services section probably needs a refresh and, as part of it, we can decide to fix or remove these files. What do you think?

Yeah if it was up to me I would just remove it.


DSA <IP_ADDRESS> Approximation Algorithms Example Problems - Video

Description
Briefly explain the examples of approximation algorithms.

Task

[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to the Issue Guidelines.
Do not use assign command for this issue. Follow the above procedure.
In case you see that the issue has already been assigned, try to request for a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

I want to work on this Kindly assign to me.
Harsh Chaudhary
DSA Batch-1

/assign

I dont have 3 opened issues.I only have one issue assigned previously so plz dont change and re assign it to me.U can chk my profile it has only one opened issue

I want to work on this Kindly assign to me.
Harsh Chaudhary
DSA Batch-1

Assigning this issue to you @Harsh-Chaudhary7, all the best!

Can I get this issue ? but i'm not DSA Batch

Go ahead @ShraddhaMeshram27

Sorry Ma'am, I am working on 2 issues on my domain now hence cannot take up this issue.
Thank you for your concern 🙏.