Non-reliable plotting functions in ICA-AROMA

The addition of plots in ICA-AROMA 4.4.0-beta has made it more prone to fail at that point. I've seen several types of error, generally at some point of the kernel density estimation of seaborn.
About 2/3 of ds000114 subjects (e.g., sub-02) on TACC with 1.5.1rc1 gave me:
Node: fmriprep_wf.single_subject_02_wf.func_preproc_ses_test_task_overtwordrepetition_wf.ica_aroma_wf.ica_aroma
Working directory: /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/ica_aroma_wf/ica_aroma

Node inputs:

TR = 5.0
args = <undefined>
compress_report = auto
denoise_type = nonaggr
dim = <undefined>
environ = {}
feat_dir = <undefined>
fnirt_warp_file = <undefined>
in_file = <undefined>
mask = <undefined>
mat_file = <undefined>
melodic_dir = <undefined>
motion_parameters = <undefined>
out_dir = out
out_report = ica_aroma_reportlet.svg
report_mask = <undefined>

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/multiproc.py", line 69, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 479, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 569, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 662, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 382, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 767, in _run_interface
    self.raise_exception(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 704, in raise_exception
    ).format(**runtime.dictcopy()))
RuntimeError: Command:
ICA_AROMA.py -tr 5.000 -den nonaggr -i /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/ica_aroma_wf/smooth/vol0000_xform-00000_merged_cut_smooth.nii.gz -m /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/bold_std_trans_wf/_key_MNI152NLin6Asym/mask_std_tfm/ref_bold_corrected_brain_mask_maths_trans.nii.gz -meldir /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/ica_aroma_wf/melodic -mc /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/bold_hmc_wf/normalize_motion/motion_params.txt -o /scratch/03763/oesteban/fmriprep-work/ds114-sub-02/fmriprep_wf/single_subject_02_wf/func_preproc_ses_test_task_overtwordrepetition_wf/ica_aroma_wf/ica_aroma/out
Standard output:

------------------------------- RUNNING ICA-AROMA -------------------------------
--------------- 'ICA-based Automatic Removal Of Motion Artifacts' ---------------

Step 1) MELODIC
  - The existing/specified MELODIC directory will be used.
Step 2) Automatic classification of the components
  - registering the spatial maps to MNI
  - extracting the CSF & Edge fraction features
  - extracting the Maximum RP correlation feature
  - extracting the High-frequency content feature
  - classification
Found 1 file(s)
Found 10 head motion-related components in a total of 25 components.
Standard error:
/usr/local/miniconda/lib/python3.7/site-packages/numpy/lib/function_base.py:2400: RuntimeWarning: invalid value encountered in true_divide
  c /= stddev[:, None]
/usr/local/miniconda/lib/python3.7/site-packages/numpy/lib/function_base.py:2401: RuntimeWarning: invalid value encountered in true_divide
  c /= stddev[None, :]
/usr/local/miniconda/lib/python3.7/site-packages/numpy/core/_methods.py:28: RuntimeWarning: invalid value encountered in reduce
  return umr_maximum(a, axis, None, out, keepdims, initial)
/opt/ICA-AROMA/ICA_AROMA_functions.py:287: RuntimeWarning: Mean of empty slice
  return np.nanmean(max_correls, axis=0)
/opt/ICA-AROMA/ICA_AROMA_functions.py:498: RuntimeWarning: invalid value encountered in greater
  motionICs = np.squeeze(np.array(np.where((proj > 0) + (csfFract > thr_csf) + (HFC > thr_HFC))))
/usr/local/miniconda/lib/python3.7/site-packages/scipy/stats/stats.py:1713: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
  return np.add.reduce(sorted[indexer] * weights, axis=axis) / sumval
/usr/local/miniconda/lib/python3.7/site-packages/numpy/core/_methods.py:28: RuntimeWarning: invalid value encountered in reduce
  return umr_maximum(a, axis, None, out, keepdims, initial)
/usr/local/miniconda/lib/python3.7/site-packages/numpy/core/_methods.py:32: RuntimeWarning: invalid value encountered in reduce
  return umr_minimum(a, axis, None, out, keepdims, initial)
Traceback (most recent call last):
  File "/opt/ICA-AROMA/ICA_AROMA.py", line 215, in <module>
    outDir)
  File "/opt/ICA-AROMA/classification_plots.py", line 164, in classification_plot
    hist_kws={'alpha': 0.2})
  File "/usr/local/miniconda/lib/python3.7/site-packages/seaborn/distributions.py", line 215, in distplot
    bins = min(_freedman_diaconis_bins(a), 50)
  File "/usr/local/miniconda/lib/python3.7/site-packages/seaborn/distributions.py", line 39, in _freedman_diaconis_bins
    return int(np.ceil((a.max() - a.min()) / h))
ValueError: cannot convert float NaN to integer
Return code: 1

Another example: https://circleci.com/gh/oesteban/fmriprep/4286

https://github.com/maartenmennes/ICA-AROMA/pull/43


error if chart have one label

demo from site:
new Chartist.Line('.ct-chart', {
labels: ['Monday'],
series: [
[12],
]
}, {
fullWidth: true,
chartPadding: {
right: 40
}
});
the only point is to the left of the chart

in setting i have option fullWidth: true. if delete this, chart work correct

I'm also having this issue.

I also have the same issue, exactly the same problem.

this should be fixed as of 0.9.6


Fastlane pilot command stuck in loop

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Fastlane pilot to external groups stucks in infinite loop.
Observed this issue from last one day 26 June 2019.
When I tried looking in the AppStoreConnect portal, it was showing the build with processing state.

But after sometime, the build from AppStoreConnect portal disappeared.
Note that, I don't have any issues with my package and I haven't received any mail from Apple  regarding the processing failure due to package issues.
I have tried the same build with lesser version and was working fine till yesterday (25 June 2019)
Complete output when running fastlane, including the stack trace and command used

[16:29:04]: Login successful
[16:29:06]: Ready to upload new build to TestFlight (App: ***)...
[16:29:14]: iTunes Transporter successfully finished its job
[16:29:14]: Going to upload updated app to App Store Connect
[16:29:14]: This might take a few minutes. Please don't interrupt the script.
[16:31:18]: iTunes Transporter successfully finished its job
[16:31:18]: ------------------------------------------------------------------------------------------------------------------
[16:31:18]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
[16:31:18]: ------------------------------------------------------------------------------------------------------------------
[16:31:18]: Successfully uploaded the new binary to App Store Connect
[16:31:18]: If you want to skip waiting for the processing to be finished, use the skip_waiting_for_build_processing option
[16:31:18]: :train_version is no longer a used argument on FastlaneCore::BuildWatcher. Please use :app_version instead.
[16:31:20]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:31:51]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:32:22]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:32:53]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:33:24]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:33:55]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:34:26]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:34:58]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:35:29]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:36:00]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:36:31]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:37:02]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:37:34]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:38:05]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:38:36]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:39:07]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:39:38]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:40:10]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:40:41]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:41:12]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:41:43]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:42:14]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:42:45]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:43:16]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:43:47]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:44:18]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:44:48]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:45:19]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:45:50]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:46:21]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:46:52]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:47:23]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:47:54]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:48:25]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:48:56]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:49:27]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:49:58]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:50:29]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:51:00]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:51:31]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:52:02]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:52:33]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:53:04]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:53:34]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:54:05]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:54:36]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:55:07]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:55:38]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:56:09]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:56:40]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:57:11]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:57:42]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:58:13]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:58:44]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:59:15]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[16:59:46]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:00:17]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:00:48]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:01:19]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:01:50]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:02:24]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:02:56]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:03:27]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:03:58]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:04:29]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:05:00]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:05:31]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:06:02]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:06:33]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:07:04]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:07:35]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:08:06]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:08:37]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:09:08]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:09:39]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:10:10]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)
[17:10:42]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:11:14]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:11:46]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:12:18]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:12:50]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:13:22]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:13:54]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:14:26]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
[17:14:58]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.5

Ruby
2.3.7

Bundler?
false

Git
git version 2.20.1 (Apple Git-117)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.14.5 (18F203)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib

OpenSSL Version
LibreSSL 2.6.5

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.126.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.10.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.6.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.64.0

faraday
0.15.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.5

gh_inspector
1.1.3

json
<IP_ADDRESS>

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.3

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.4

bundler
2.0.2

faraday_middleware
0.13.1

naturally
2.2.0

simctl
1.6.5

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2019.0331

mime-types
3.2.2

multi_json
1.13.1

signet
0.11.0

memoist
0.16.0

os
1.0.1

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.2.0

google-cloud-core
1.3.0

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

io-console
0.4.5

libxml-ruby
2.9.0

psych
<IP_ADDRESS>

generated on: 2019-06-26

Also I see the infinity loop code here to check till the build exists.
https://github.com/fastlane/fastlane/blob/master/fastlane_core/lib/fastlane_core/build_watcher.rb#L21
Is this intended or do we have any future plans to timeout this after some time. @fastlaneTeam

I'm experiencing the same issue. It's been running for 25 minutes and counting

Mine went for hours last night before finally processing. Taking forever this morning too. I'm wondering if this isn't an App Store issue?

But after sometime, the build from AppStoreConnect portal disappeared.

Where did it go? Did it ever reappear or is it just gone now?

This is most likely caused by App Store Connect. Over the weekend I was seeing some processing times on my end that were reaching over an hour when they usually take about 14 minutes. If the build disappears its usually due to an issue so check your email but sometimes it could be due to something else also happening on App Store Connect.
So this is most likely not an issue with pilot itself but just something we need to be patient with 😇

But after sometime, the build from AppStoreConnect portal disappeared.

Where did it go? Did it ever reappear or is it just gone now?

@janpio yeah, as per the screenshot, the uploaded build was showing for some amount of time in the portal and then disappeared. and hence the error in the fastlane build watcher appeared like this
[17:10:10]: Waiting for App Store Connect to finish processing the new build (6.0 - 1)

[17:10:42]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)

Also I checked, the other also has seen the same build missing issue
https://forums.developer.apple.com/thread/118669
Please let me know if you have any information.

@joshdholtz okay. I will try again and see.
Can you please address this
https://github.com/fastlane/fastlane/issues/14952#issuecomment-505780549

FYI: Uploading directly to the App Store via xcode works fine so I think this has something to do with fastlane...

@adamirowe Xcode uses different methods to upload, which are unfortunately not available to fastlane (which uses iTunes Transporter - which would probably have the same problems you are observing when used directly).

@Ajaykn21 That loop has always been there. That loops check every 30 seconds (or whatever is configured) to check the status of the build. Its an endless loop because the build can take unknown amount of time to finish processing 😇 Like I mentioned earlier my builds usually take under 15 minutes but the other weekend they were taking over an hour. If it takes too long I usually just control+c out of the process but I'd be down for adding an optional timeout if that's what the people want 🙃

I got the same issue 🙃


CERTIFICATE ERROR

SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED]
Error while parsing the file './uber_10q_march_2022.pdf': [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1002)
I am getting this error while parsing if you can suggest the solution
@seldo @hexapode @erichare @yisding @hatianzhang

you need to add the certificate chain from openai to the certificates file in your conda environment


Bug: Tracer: Time gap between LambdaInvoke and Handler

Expected Behaviour
On XRay console, Trace details, I expected to see no time gap between Lambda Invoke and Lambda handler.
Current Behaviour
When I see the results of a trace I can see a gap between the start of Lambda invoke and handler. The reason for this gap is unknown.
Note1: I am using Provisioned concurrency
Note2: I've opened an AWS ticket to get an explanation for this behavior and they say this might be specific to my code, which uses Powertools to handle tracing
Note3: This gap is bigger on the first call. However, there is no static code or getParameter in this test. However, I do get a connection from a database and keep the connection for subsequent calls. The method that gets the connection is instrumented manually.
Example gap scenario on first call:
Invocation: 417ms
Handler: 279ms
gap: 138ms
The gap happens mostly before the handler:
before handler: 126ms
Code snippet
Handler instrumentation
// Decorate your handler class method
  @logger.injectLambdaContext()
  @tracer.captureLambdaHandler()
  public async handler(
    event: APIGatewayProxyEvent,
    context: Context,
  ): Promise<APIGatewayProxyResult> {
    const start = performance.now();
    console.log('Function hanlder starting...');

    const response = await super.handler(event, context);
    // Measure
    const end = performance.now();
    console.log(`Function handler executed in ${end - start}ms`);
    return response;
  }

GetConnection instrumentation (if there is a less verbose method that does not use decorators I would be glad to hear)
// get a database connection
  protected async getDbConnection(
    dbOptions: mysql.ConnectionOptions
  ): Promise<mysql.Connection> {
    // Open new subSegment
    const parentSubsegment = this.tracer?.getSegment(); // This is the subsegment currently active
    let subsegment;
    if (parentSubsegment) {
      // Create subsegment for the function & set it as active
      subsegment = parentSubsegment.addNewSubsegment(`### getDbConnection`);
      this.tracer?.setSegment(subsegment);
    }

    const dbConnection = await mysql.createConnection(dbOptions);

    // Close subSegment
    if (parentSubsegment && subsegment) {
      // Close subsegment (the AWS Lambda one is closed automatically)
      subsegment.close();
      // Set the facade segment as active again
      this.tracer?.setSegment(parentSubsegment);
    }

    return dbConnection;
  }

Steps to Reproduce

Provisioned concurrent lambda
No VPC
No static Code
No getParameter used
Tracer configured with decorator on handler method

Possible Solution
No suggestion for now
Powertools for AWS Lambda (TypeScript) version
1.12.1
AWS Lambda function runtime
16.x
Packaging format used
npm
Execution logs
INIT_START Runtime Version: nodejs:16.v20	Runtime Version ARN: arn:aws:lambda:sa-east-1::runtime:221c9e1eaf373c676cf0d1bff6642d8cb3ba2642dbad7a8c56624b0fddc4ffcd
2023-10-12T14:37:10.700Z	undefined	INFO	Before any import
2023-10-12T14:37:10.701Z	undefined	INFO	Start global context
2023-10-12T14:37:10.701Z	undefined	INFO	Before export handler
2023-10-12T14:37:10.701Z	undefined	INFO	constructor executed in 0.049075999995693564ms
2023-10-12T14:37:10.701Z	undefined	INFO	Global context executed in 0.5833669999992708ms
START RequestId: aba2e6cf-982e-4eb9-8249-1d7b11471e67 Version: 21
{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Lambda invocation event",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:44:59.783Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "event": {
        "resource": "/",
        "path": "/",
        "httpMethod": "POST",
        "headers": {
            "Accept": "*/*",
            "Content-Type": "text/xml",
            "Host": "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com",
            "User-Agent": "curl/8.0.1",
            "x-amzn-cipher-suite": "ECDHE-RSA-AES128-GCM-SHA256",
            "x-amzn-tls-version": "TLSv1.2",
            "x-amzn-vpc-id": "vpc-055f0d77c5aa8d6f9",
            "x-amzn-vpce-config": "1",
            "x-amzn-vpce-id": "vpce-0fd8d0b1be931eab1",
            "X-Forwarded-For": "<IP_ADDRESS>"
        },
        "multiValueHeaders": {
            "Accept": [
                "*/*"
            ],
            "Content-Type": [
                "text/xml"
            ],
            "Host": [
                "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com"
            ],
            "User-Agent": [
                "curl/8.0.1"
            ],
            "x-amzn-cipher-suite": [
                "ECDHE-RSA-AES128-GCM-SHA256"
            ],
            "x-amzn-tls-version": [
                "TLSv1.2"
            ],
            "x-amzn-vpc-id": [
                "vpc-055f0d77c5aa8d6f9"
            ],
            "x-amzn-vpce-config": [
                "1"
            ],
            "x-amzn-vpce-id": [
                "vpce-0fd8d0b1be931eab1"
            ],
            "X-Forwarded-For": [
                "<IP_ADDRESS>"
            ]
        },
        "queryStringParameters": null,
        "multiValueQueryStringParameters": null,
        "pathParameters": null,
        "stageVariables": null,
        "requestContext": {
            "resourceId": "v46zht1add",
            "resourcePath": "/",
            "httpMethod": "POST",
            "extendedRequestId": "MsXw3FvlGjQFVWw=",
            "requestTime": "12/Oct/2023:14:44:59 +0000",
            "path": "/prod/",
            "accountId": "272998361838",
            "protocol": "HTTP/1.1",
            "stage": "prod",
            "domainPrefix": "shrpn1l6q8",
            "requestTimeEpoch":<PHONE_NUMBER>645,
            "requestId": "6becfce3-9b53-4bbe-be99-00db25347473",
            "identity": {
                "cognitoIdentityPoolId": null,
                "cognitoIdentityId": null,
                "vpceId": "vpce-0fd8d0b1be931eab1",
                "principalOrgId": null,
                "cognitoAuthenticationType": null,
                "userArn": null,
                "userAgent": "curl/8.0.1",
                "accountId": null,
                "caller": null,
                "sourceIp": "<IP_ADDRESS>",
                "accessKey": null,
                "vpcId": "vpc-055f0d77c5aa8d6f9",
                "cognitoAuthenticationProvider": null,
                "user": null
            },
            "domainName": "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com",
            "apiId": "shrpn1l6q8"
        },
        "body": "<soap:Envelope xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">    <SOAP-ENV:Header xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"/>        <soap:Body>            <MaintenanceRequest xmlns=\"http://www.comviva.com/asa/maintenancewindow/result\">                <area_cn>21</area_cn>                <origin>API</origin>                <module_name>orchestrator</module_name>            </MaintenanceRequest>        </soap:Body></soap:Envelope>",
        "isBase64Encoded": false
    }
}

2023-10-12T14:44:59.823Z	aba2e6cf-982e-4eb9-8249-1d7b11471e67	INFO	Function hanlder starting...
{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "DEBUG",
    "message": "Getting new DB connection...",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:44:59.824Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1"
}

{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "DEBUG",
    "message": "Fetching DB options...",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:44:59.841Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1"
}

{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "DEBUG",
    "message": "Got new DB connection.",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:44:59.961Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1"
}

{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Initializing controller...",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:44:59.962Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1"
}

2023-10-12T14:44:59.963Z	aba2e6cf-982e-4eb9-8249-1d7b11471e67	INFO	initialize method executed in<PHONE_NUMBER>9996679ms
2023-10-12T14:44:59.981Z	aba2e6cf-982e-4eb9-8249-1d7b11471e67	INFO	processRequest called
{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Validate payload document",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:00.005Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1"
}

{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Execute domain service",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:00.007Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Trying to get maintenance window info by area and module...",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:00.007Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

2023-10-12T14:45:00.085Z	aba2e6cf-982e-4eb9-8249-1d7b11471e67	INFO	Function handler executed in<PHONE_NUMBER>000146ms
{
    "cold_start": true,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "aba2e6cf-982e-4eb9-8249-1d7b11471e67",
    "level": "INFO",
    "message": "Build response payload",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:00.084Z",
    "xray_trace_id": "1-6528066b-c2469549fd6df1f6f4d81d47",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

END RequestId: aba2e6cf-982e-4eb9-8249-1d7b11471e67
REPORT RequestId: aba2e6cf-982e-4eb9-8249-1d7b11471e67	Duration: 457.99 ms	Billed Duration: 458 ms	Memory Size: 256 MB	Max Memory Used: 131 MB	Init Duration: 5450.35 ms
XRAY TraceId: 1-6528066b-c2469549fd6df1f6f4d81d47	SegmentId: 47d8cf8b3c87a056	Sampled: true
START RequestId: afe0085d-6a27-47fb-9120-7d01597c8f98 Version: 21
{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "INFO",
    "message": "Lambda invocation event",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.036Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API",
    "event": {
        "resource": "/",
        "path": "/",
        "httpMethod": "POST",
        "headers": {
            "Accept": "*/*",
            "Content-Type": "text/xml",
            "Host": "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com",
            "User-Agent": "curl/8.0.1",
            "x-amzn-cipher-suite": "ECDHE-RSA-AES128-GCM-SHA256",
            "x-amzn-tls-version": "TLSv1.2",
            "x-amzn-vpc-id": "vpc-055f0d77c5aa8d6f9",
            "x-amzn-vpce-config": "1",
            "x-amzn-vpce-id": "vpce-0fd8d0b1be931eab1",
            "X-Forwarded-For": "<IP_ADDRESS>"
        },
        "multiValueHeaders": {
            "Accept": [
                "*/*"
            ],
            "Content-Type": [
                "text/xml"
            ],
            "Host": [
                "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com"
            ],
            "User-Agent": [
                "curl/8.0.1"
            ],
            "x-amzn-cipher-suite": [
                "ECDHE-RSA-AES128-GCM-SHA256"
            ],
            "x-amzn-tls-version": [
                "TLSv1.2"
            ],
            "x-amzn-vpc-id": [
                "vpc-055f0d77c5aa8d6f9"
            ],
            "x-amzn-vpce-config": [
                "1"
            ],
            "x-amzn-vpce-id": [
                "vpce-0fd8d0b1be931eab1"
            ],
            "X-Forwarded-For": [
                "<IP_ADDRESS>"
            ]
        },
        "queryStringParameters": null,
        "multiValueQueryStringParameters": null,
        "pathParameters": null,
        "stageVariables": null,
        "requestContext": {
            "resourceId": "v46zht1add",
            "resourcePath": "/",
            "httpMethod": "POST",
            "extendedRequestId": "MsXx3E0_mjQFlVA=",
            "requestTime": "12/Oct/2023:14:45:06 +0000",
            "path": "/prod/",
            "accountId": "272998361838",
            "protocol": "HTTP/1.1",
            "stage": "prod",
            "domainPrefix": "shrpn1l6q8",
            "requestTimeEpoch":<PHONE_NUMBER>016,
            "requestId": "55830c8e-7045-47fe-8610-1f0ce9365282",
            "identity": {
                "cognitoIdentityPoolId": null,
                "cognitoIdentityId": null,
                "vpceId": "vpce-0fd8d0b1be931eab1",
                "principalOrgId": null,
                "cognitoAuthenticationType": null,
                "userArn": null,
                "userAgent": "curl/8.0.1",
                "accountId": null,
                "caller": null,
                "sourceIp": "<IP_ADDRESS>",
                "accessKey": null,
                "vpcId": "vpc-055f0d77c5aa8d6f9",
                "cognitoAuthenticationProvider": null,
                "user": null
            },
            "domainName": "shrpn1l6q8.execute-api.sa-east-1.amazonaws.com",
            "apiId": "shrpn1l6q8"
        },
        "body": "<soap:Envelope xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">    <SOAP-ENV:Header xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"/>        <soap:Body>            <MaintenanceRequest xmlns=\"http://www.comviva.com/asa/maintenancewindow/result\">                <area_cn>21</area_cn>                <origin>API</origin>                <module_name>orchestrator</module_name>            </MaintenanceRequest>        </soap:Body></soap:Envelope>",
        "isBase64Encoded": false
    }
}

2023-10-12T14:45:06.038Z	afe0085d-6a27-47fb-9120-7d01597c8f98	INFO	processRequest called
2023-10-12T14:45:06.038Z	afe0085d-6a27-47fb-9120-7d01597c8f98	INFO	initialize method executed in 0.38570700003765523ms
2023-10-12T14:45:06.038Z	afe0085d-6a27-47fb-9120-7d01597c8f98	INFO	Function hanlder starting...
{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "DEBUG",
    "message": "Reusing database connection.",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.038Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "INFO",
    "message": "Validate payload document",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.039Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "INFO",
    "message": "Execute domain service",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.040Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "INFO",
    "message": "Trying to get maintenance window info by area and module...",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.041Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

2023-10-12T14:45:06.044Z	afe0085d-6a27-47fb-9120-7d01597c8f98	INFO	Function handler executed in 6.712112999986857ms
{
    "cold_start": false,
    "function_arn": "arn:aws:lambda:sa-east-1:272998361838:function:MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh:provisioned-lambda-alias",
    "function_memory_size": 256,
    "function_name": "MaintenanceWindow-IntegrationLambdaFunction434D807-kfqZPYkps7fh",
    "function_request_id": "afe0085d-6a27-47fb-9120-7d01597c8f98",
    "level": "INFO",
    "message": "Build response payload",
    "service": "MaintenanceWindow",
    "timestamp": "2023-10-12T14:45:06.044Z",
    "xray_trace_id": "1-65280672-554763a5a39a257496cc43be",
    "aws_account_id": "N/A",
    "aws_region": "sa-east-1",
    "module": "orchestrator",
    "area": "21",
    "origin": "API"
}

END RequestId: afe0085d-6a27-47fb-9120-7d01597c8f98
REPORT RequestId: afe0085d-6a27-47fb-9120-7d01597c8f98	Duration: 25.72 ms	Billed Duration: 26 ms	Memory Size: 256 MB	Max Memory Used: 132 MB
XRAY TraceId: 1-65280672-554763a5a39a257496cc43be	SegmentId: 04ad00e704b0d140	Sampled: true

If you don't mind, could you please send an email to (aws-lambda-powertools-feedback<EMAIL_ADDRESS>with the ID of the AWS Support Ticket?

@dreamorosi, the documentation above mentions a gap between the init phase and the invocation phase. This would happen because in provisioned concurrency the init phase occurs several minutes before invoke. Actually, currently the init phase is not shown in functions that have provisioned concurrency.
What I am seeing is a gap between the start of lambda invoke and the start of lambda handler.

Hi @marcioemiranda, thanks for the email and for providing the screenshot. Now we have a clearer picture of the issue.
We have started looking into it and seeing if we are able to reproduce it, but we will need some more time.
We'll continue working on this for the rest of the day but we'll likely answer on Monday next week.

@dreamorosi thanks for the update.
I was doing some investigation today, comparing timestamps from logs with timestamps from X-Ray and noticed that the log event generated by the logger utility happened before the handler start time. So I suspect the code in the decorators are causing this gap. It is bigger the first time after an INIT and lower after that, possibly because of some caching done in the decorator classes. Does that make sense? If this is the case the added latency is around 100-150ms.
Findings from my investigation:
Last INIT line        2023-10-13T22:45:36.699Z (several minutes before invocation)
Log event             2023-10-13T23:09:15.641Z (Powertools decorator. Timestamp earlier than the one reported by XRay for handler)
First line in handler 2023-10-13T23:09:15.661Z
initialize method executed in<PHONE_NUMBER>9998713ms
Last line in handler  2023-10-13T23:09:15.939Z
TraceId: 1-6529ce1b-e7bd69619d77f3e13ac0684c
Handler:
StartTime: 2023-10-13 23:09:15.660 (UTC) (compatible with timestamp from first line in handler)
EndTime:   2023-10-13 23:09:15.940 (UTC) (compatible with timestamp from last line in handler)
getDbConnection
Duration: 118ms (close to overall initialization of 139ms)
Start: 2023-10-13 23:09:15.662 (UTC) (compatible with handler timestamp)
End:   2023-10-13 23:09:15.780 (UTC)
Invocation:
StartTime: 2023-10-13 23:09:15.520 (UTC)
EndTime:   2023-10-13 23:09:15.941 (UTC)
Invocation x Handler Gap: 140ms

@dreamorosi , I've done some additional tests.
I've removed all powertools decorators and logging done by the Logger class and replaced that with console.log() calls. Then I compared the timestamps from the logs with the startTime from the Invocation segment in XRay. The gap was still there, so it seems this is not related to powertools.

Hi @marcioemiranda, thank you for sharing your latest findings - appreciate you letting us know.
We have been working on this and @leandrodamascena was able to reproduce the behavior you described. We still need to properly understand why this is happening, so in order to do this we are going to open an internal ticket to get a better idea of why we are seeing this gap.
Once we hear back from them we will share as much information as we can.
Thank you for your patience.

Oi @marcioemiranda, tudo bem?! Obrigado por reportar isto!
Now in english 😄.. I would like to ask you a favor: can you try to reproduce the same behavior again? You can run the Lambda function about 2 or 3 times where this behavior happens and provide us with the following information:
1 - requestId
2 - traceId
3 - Memory configured in Lambda
4 - time difference between the invocation and the handler
5 - a print of the xray
We have opened an internal ticket and I want to provide additional information to them.
Thanks

Oi @leandrodamascena , obrigado pela ajuda! Vejo que vc é um pai babão.. 😉
Going back to the case, here is the info you've requested.

Does this internal ticket have an id? I'd like to inform it in the original AWS ticket and also send it to the local AWS representative that is following up this project.
Thanks!

Hi @marcioemiranda - is your support ticket the same as the one you shared with me last week?
If yes, I can add an internal note and link the two tickets - I think it'd be easier than sharing the ID here.

Hi @dreamorosi , yes it is

Great, I have added an internal note and linked the two cases, the support representative on the case will be able to see it.

Unfortunately we haven't heard back from the team.
Given that we have excluded that this is a Powertools specific issue I'm going to close the issue, please feel free to get in touch again if you have additional questions, and thank you for using the project!


Docker and rpm updates

run_dockers.bsh can now auto pull the latest docker images
More verbose (and un cut) output of 64 bit rpm builds build. No more redirect to build.log
RPMs use GIT_LFS_TEST_DIR in %check

Thanks! Finally got my docker issues resolved, so I could confirm this all works.


Operations that introduce non-opaque background make unnecessary, implicit cast to double

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
  System:
    OS: macOS 12.6.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 3.44 GB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
  npmPackages:
    sharp: ^0.31.2 => 0.31.2

What are the steps to reproduce?
Hi Lovell,
while using your excellent library, we hit a problem of which I hope you can give some hints on the cause.
We try to do image manipulation in several steps, converting a sharp to a buffer and re-reading it, since we need to apply transformations in arbitrary order. To speed up converting to a buffer, we want to use uncompressed TIFF format. As soon as we add an alpha channel to the image, however, conversion of a previously written buffer back to a sharp fails.
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
This is a simplified code snippet to illustrate the issue:
    let buffer = await fs.readFileSync("random-small.jpeg"));
    buffer = await sharp(buffer)
      .tiff({compression: 'none'})
      .extend({left: 10, background: {r: 255, g: 255, b: 255, alpha: 0.5}})
      .toBuffer();
    await sharp(buffer)
      .toBuffer();

What is the expected behaviour?
With the second sharp(buffer), an error is thrown by libvips:
Error: Input buffer has corrupt header: tiff2vips: samples out of range

It seems that all components (R, G, B, and Alpha) are represented as 8-byte floats each. If no alpha is included, the conversion and re-reading works just fine with R, G, and B being represented by uchar. The issue does not appear with raw format but that one cannot handle animated images, unfortunately (https://github.com/lovell/sharp/issues/3189).

Knowing too little about JavaScript and C++, I failed to find my way through the code to see the root cause of the issue.
Do you have a hint maybe or know a way around it?
Thanks,
Stefan

This is a bit niche, but when introducing a non-opaque background colour via extend, the image was being cast to double-precision. It just so happens that the tiff saver supports this, so the output of the first step was also double precision, however the tiff loader can't open these, hence the error you saw.
Commit https://github.com/lovell/sharp/commit/9d760f39587aa986fcd9f8c854c045de44618f3f ensures the addition of a background colour always casts to the same precision as the input image, which prevents an unnecessary cast to slower double precision, thereby improving performance.
Thanks for reporting this.

Absolutely perfect, thanks a lot!

This was included as part of v0.31.3


Wake screen via MQTT

This would be an excellent feature as an alternative to using camera motion.

Already implemented :)


Add Lambda code

Adds the code that will actually push to Humio. CI checks may fail because no work has been done on the CI or IAC yet (that will be a future PR).
Also, if you could take a glance at the README currently on main and let me know if you see anything weird, that'd be great too. I just committed those directly to main as I was customizing the template.
Humio reference docs: https://docs.humio.com/reference/api/ingest/

@GaryGSC Yeah, I noticed that after I made the PR. I was going to make that switch after this if no one noticed, but I'll do it now.

A few of us have been talking about the direction here: https://byu-oit.slack.com/archives/C02689C20L9/p1626326826048800

Closing since I'm working on the infra too.

@blakemorgan - I realize the PR is closed, but I left a few more comments ☝


Less templating for the TurtleParsers.

There is now a common base class for our Turtle parsers. That way, methods involed in index building no longer have be be templated with the parser class.
The parallel parser now accepts an arbitrary sequence of \n and \r as newline, and there may be arbitrary whitespace after the final dot in a line. So far, only \n was accepted as newline, and a \t after the final dot did not work.
There is now a Boolean option parallel-parsing in the settings.json configuration file. It is true by default, which is consistent with the behavior so far.
Add extensive unit tests for the Turtle parser (both parallel and not parallel).
Remove the mmap parser becuse it was no longer needed (and probably also not working any longer).


chore: use fqdn for docker registries

Closes #76

:tada: This PR is included in version 1.0.0-dev.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Nunit test sample is wrong

the sample provided is just same as MStest, so by copying the code as provide will reflects a missing an assembly reference

@xmen824 Can you add a link to the page you're referencing? Thanks!

https://docs.microsoft.com/en-us/visualstudio/test/getting-started-with-unit-testing?view=vs-2019

Thanks! I'll update the doc.


Ghidra Disassembler and Decompiler Doesn't Recognize Puts...

To Reproduce
Steps to reproduce the behavior:

Just Write A Sample HelloWorld Program In C
Open It On Ghidra
Baaammmm... .text insted of puts...? XD

Screenshots

Retdec

IDA:

Meanwhile In Ghidra:

More info on this here: https://twitter.com/marcan42/status/1103628581060587521

Duplicate of #761
Duplicate of #1061


How do I fix this error

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
ERROR: Error: Cannot find 'dist/index.html', did you install correctly?
📝 Error Message(s) or Log
It's some thing wrong
🐻 Uptime-Kuma Version
1.10.0
💻 Operating System and Arch
Unbuntu 20
🌐 Browser
Termuis
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

What did you do beforehand?
In addtion to that, please edit your previous answer to include the details you ommited in posting the issue.


Keystore's certificate chain derived from Vault issue-certificate lacks CA authority certificate

Thank you for Spring Vault, @mp911de.  Massively helpful, especially in how the library offers a clean way to create a Keystore from the Vault pki/issue response.  I was not looking forward to rolling my own version of this with BouncyCastle, which is quite possible, but drudgery.  These creature comforts are one of the many reasons I value your work.
One feature enhancement, however, which I believe is very helpful, if not essential.  Imagine this signing scenario:
Root CA named R signs intermediate CA C1.  C1 signs Vault's PKI CSR, making Vault CA C2.  The leaf Vault generates at pki/issue, is L.  The full chain is therefore R -> C1 -> C2 -> L.
AFAICT, when Spring Vault builds the Keystore certificate chain associated with the acquired private key, it currently does not take into consideration the pki/issue response field ca_chain.  Instead, Spring Vault honors issuing_ca, which is necessary but not sufficient.  Why should Spring Vault honor ca_chain?  Consider that the Vault PKI API allows Vault operators to indicate the CA certificate that signed Vault's signing certificate.  Using the nomenclature above,  the Vault operator dictates that ca_chain would be the concatenation of C2 and C1, in PEM format, knowing that C1 signed C2.
If Spring Vault honored ca_chain, it can build a Keystore certificate chain that is sufficiently rich to allow selection of a client certificate (via a custom Java X509 KeyManager) during TLS setup, based solely on the ultimate Root CA R.  A postulated business server that challenges a Java client for a client certificate would indicate during TLS setup that it accepts any certificate rooted in a Root CA R.  Such a server may quite possibly be ignorant of  C1 and/or C2, but it knows about R (it has to know at least that much).
So by honoring ca_chain when building the Keystore, Spring Vault gives a TLS client enough material to select which client cert to return based on a single root CA.
Thanks for reading this far.

I am not 100% certain this is as great an enhancement as I had argued.  One could solve the same problem by adding C1 to the acceptable issuers on the server side.  In so doing the server would send two acceptable issuers:  C1 and the Root R.
Interested in what others think.
Thanks.

Thanks for reaching out. I think the reason for the current arrangement is that back then, when we built the support for PKI, ca_chain was either not documented or not present in earlier vault versions. Also, since our tests cases didn't cover multi-level CA arrangements, the issue never came up.
We could extend CertificateBundle to be ca-chain-aware, probably we need to look into certificate splitting, but we should have most of the code to make it work. For KeyStore creation, we can introduce two constants (full chain, issuer certificate) to control which certificates include in the KeyStore.
The utilities to create a KeyStore are intended for convenient usage so that a server or client could be launched for e.g. TLS usage without the need of further KeyStore customization.

Thank you, Mark.  Look forward to whatever you come up with.

That's in place now. Please give the upcoming 2.3.3 snapshot a try.


Remove QuickDialingView reference

Quick Description of What this is about

Removed QuickDialingActivity
Removed QuickDialingView navigation reference
Removed QuickDialingView string resources

@cedricbahirwe the ticket only mentioned QuickDialingView

@cedricbahirwe the ticket only mentioned QuickDialingView , that s why I left out the quick dial

Yes, also mentioned removing the reference to it, which are still present in the aforementioned files..
For instance, the app would crash now if you tried to navigate to that quick dialing view since the home screen has a button that tries to navigate there

@cedricbahirwe so you mean the QuickDialingView is also referenced as quickdial, one of the composable has that name?
PS: I am winning this argument

@cedricbahirwe so you mean the QuickDialingView is also referenced as quickdial, one of the composable has that name?
PS: I am winning this argument

By Reference, I meant everything(code) related to QuickDialingView, you can't just remove it then leave strings related to it or navigation code related to it

@cedricbahirwe the ticket should have your answer as description , cause I thought composable were supposed to have the same name as QuickDialingView, quickdial might be something else not even related with the QuickDialingView, that s why having both names would have helped
PS: You created these codes which means my understanding of the naming convention is still limited

let me merge it before you come back with another argument

@cedricbahirwe so you mean the QuickDialingView is also referenced as quickdial, one of the composable has that name?
PS: I am winning this argument

By Reference, I meant everything(code) related to QuickDialingView, you can't just remove it then leave strings related to it or navigation code related to it

Roger that, thanks!


Remove oudated versions of jquery & modernizr libraries

These libraries were updated in #237. I don't feel as though the theme should provide older versions for compatibility sake. Theme users can supply their own JS overrides if they wish.

Deleted them here: https://github.com/matcornic/hugo-theme-learn/pull/268
Everything seem to be working fine.


The results of nuScenes test set

Thank you for your work. What is the effect of voxel-mae in the nuScenes test set？

Hi,
We have not run Voxel-MAE on the test set but I'll update you when we have those results.


[stable/chartmuseum] Add serviceMonitor to chartmuseum chart

Signed-off-by: Philippe Dagenais<EMAIL_ADDRESS>What this PR does / why we need it:
This PR add the serviceMonitor resource to be able to scrape metrics when using the prometheus operator.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/retest

/assign @olemarkus

/ok-to-test

/lgtm
thanks!


chore: fix proto on v10.x

Closes: #XXX
What is the purpose of the change
Run make proto-all on v10.x. It is outdated now and breaking other PRs: https://github.com/osmosis-labs/osmosis/pull/2072
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

Thoughts on going with: https://github.com/osmosis-labs/osmosis/pull/2074 to get CI in?


Add analytics event for video buffering

We want to know when a video starts playing but stops.

@sayplastic we're going to tackle this this week - is there anywhere you want this logged specifically for lbry.tv?

What metrics are available, apart from the obvious time into stream/duration?
I would like to have as much data as possible, but prometheus is poll-based so I will need to implement some kind of collector endpoint on the lbrytv API side.

@sayplastic We could easily send these (probably more too but this was the first thing I saw
secondsToLoad: Total amount of time in seconds buffering took
bufferCount: Total buffer events for this source


Align Enso launcher with Truffle's AbstractLanguageLauncher

Pull Request Description
Closes #5298 by extending AbstractLanguageLauncher and thus inheriting all its functionality common for other Truffle language implementations.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] All code follows the
Scala,
Java,
[ ] Unit tests have been written where possible.

Rather than using launcher-common, let's continue with

#10374
if necessary let's handle -vm. and --inspect & co. options ourselves


Subquery column with same name of integer column table always return null

System information:

Windows 10 Home Single Language
DBeaver 6.3.5
Additional extensions: Nothing

Connection specification:

Mysql 5.7.11
Driver name: Mysql
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
When you bring a column in subquery with the same name of column table, the return is always 'null'.
Below I have a test script  to reproduce this bug.
Steps to reproduce, if exist:
CREATE TABLE test (
id SERIAL,
description VARCHAR(200),
idCity INTEGER
);
CREATE TABLE city (
id SERIAL,
name VARCHAR(200)
);
INSERT INTO test SET description = 'test 1', idCity = 1;
INSERT INTO city SET name = 'city test';
SELECT id, description, idCity,
(SELECT name FROM city WHERE test.idCity = city.id) idCity,
(SELECT name FROM city WHERE test.idCity = city.id) idCity2 FROM test;

thanks for the bug report
note:db1.7954

Fixed

Verified


valid scrape_config example

I have a prometheus-grafana setup on k8s and I have the bull pod running and it shows metrics at the /metrics endpoint and I have both scrape annotations at pod,deployment and service level.
Still on prometheus it doesnt show up, I believe I need to add a scrape config, can you assist me here?

I have prometheus running in the same AKS clusters as Bulljs, here is what i have for my prometheus config. I hope this helps.
------------------------- Bull_Q_UAT -------------------------#
- job_name: 'Bull_Q_UAT'
  static_configs:
      - targets:
          - <IP_ADDRESS>:9999
        labels:
          Env: UAT
          Page: No
          Severity: 2

@stamina11 thanks this worked.


Any plans to offer a Jakarta version?

In playing around with migrating Hibernate to Jakarta Persistence APIs I ran into trouble with our hibernate-jcache module.  The only hang up I saw was that ehcache3 uses JAXB which would need to be updated to use Jakarta's JAXB apis/impls.
Having done this for Hibernate I can offer some help/guidance.  Let me know

There are multiple things in motion in my periphery that would probably benefit from this migration, so it is likely to happen, but I can't offer a concrete timeline. That said I know of no reason why this isn't a simple migration, the disruption to user is a little harder to quantify. Given we don't bleed our usage out through API I could even in a pinch buy doing this in a dot release, but that might perturb some users.

If you want to take a peek..

the tasks are at https://github.com/hibernate/hibernate-orm/tree/wip/6.0/hibernate-orm-build/src/main/java/org/hibernate/orm/jakarta
the rules are at https://github.com/hibernate/hibernate-orm/tree/wip/6.0/rules

I've hacked up a branch: https://github.com/chrisdennis/ehcache3/tree/jakarta-jaxb that provides what I think you need. Getting this integrated is complicated though for a multitude of reasons:

We need to decide if we want to push the JTA support to use Jakarta JTA too (and how this relates to the weird Java SE JTA / Jakarta split).
We need to decide if this becomes a secondary set of artifacts, or if we version bump and hard cut.
If we version bump do we take the opportunity to drop JDK 8 support (which I think you guys would not like?).
Internally at Software AG this is also complex since Ehcache gets integrated in to a container environment where the JAXB implementation is currently centrally provided. I'd need to jump through some internal hoops to make sure that having both JAXB implementations on the classpath is okay. In a twist of fate this also might result in a cyclic dependency since there is an internal effort afoot to update to [Glassfish 6, Spring 6, Tomcat 10].

I've kicked off the effort to push on this stuff internally. If I doesn't look like it'll get resolved quickly then I'll probably (at least temporarily) move to a split artifact set (e.g. ehcache-3.9.x-jakarta.jar) in the same way that Hibernate has.

Sorry... by integrated I meant merged in to main. The current plan is for us to take the same path Hibernate has and publish jakarta classifier variants for ehcache, ehcache-xml and probably ehcache-transactions. I plan to take that on this week but my main dev machine took a (figurative) flying leap off a cliff this morning so P1 is that right now.

Any luck getting a Jakarta-compatible release?  Even a SNAPSHOT would be great for now.
Additionally, since y'all know JCache well, can you explain the optional dependency on CDI?  The JCache build says:

        <!--This is only needed if you are using a CDI based implementation of the annotations support.
            In CDI 1.1. we should be able to remove this dependency completely. -->
        <dependency>
            <groupId>javax.enterprise</groupId>
            <artifactId>cdi-api</artifactId>
            <version>1.0-SP4</version>
            <scope>provided</scope>
            <optional>true</optional>
            <exclusions>
                <exclusion>
                    <artifactId>jsr250-api</artifactId>
                    <groupId>javax.annotation</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>jboss-interceptors-api_1.1_spec</artifactId>
                    <groupId>org.jboss.spec.javax.interceptor</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>javax.inject</artifactId>
                    <groupId>javax.inject</groupId>
                </exclusion>
            </exclusions>
        </dependency>

What does "annotations support" mean here?  What does the CDI 1.1 (which has come and gone) comment mean?

I've been working this on and off in the last couple of weeks. It's gotten tied up in a long standing Gradle upgrade task and I've run in to some Gradle issues that have held me up. I'm hoping to be done by the end of the week. I have it working locally, including updating the hibernate-jcache module to use the new module and all the tests run clean (if that's any solace).
There's a bunch of stuff under javax.cache.annotation for doing annotation based caching injection - so I'm guessing this is tied to that. I will confess to not paying much attention to what was going on with this corner of the spec though. I was more focussed on trying to make sure the core stuff didn't have glaring flaws in it (apologies for failing on that front).

Wow, thanks for the quick reply @chrisdennis !
Ok, so it is only related to use of caching-specific annotations for CDI-based injection.  How common, if you know, is that in second-level caching for ORM providers?

No idea, my experience of with ORMs is so 'inside out' that I don't have a clear picture on that kind of thing. Incidentally the PR that overhauls the build system to add support for what you want is here: #2962
I've tested it locally by migrating the hibernate-jcache module to Jakarta JPA and using the new variant and it seems to work fine (tests pass in that module at least). Once this PR is merged I'll cut a pre-release and then PR my integration of this in to the Hibernate wip/6.0 branch.

That would be amazingly awesome!
We'd be able to re-enable "real" cache testing - atm we use our internal-only, intended for testing cache impl which is not really great

I've created https://github.com/hibernate/hibernate-orm/pull/4380 to cover (test?) integrating these changes in to Hibernate.

Hello,
I would like to kindly ask if there is any scheduled date for a jakarta-compatible version.
Are there any blocking issues or is it just a matter of time?
Thanks! Thomas

There is an early alpha of this published under version 3.10.0-alpha0. There is no set schedule for a GA of that right now, but there are no "blocking issues" either. The only thing really holding it up at the moment is finishing up the integration of the changes in the various internal downstream builds, and bringing the clustered components that Ehcache 3 depends on to a stable point.

Thanks for the quick reply! I will give it a try :)

The ConfigurationParser.java still has some dependencies on javax.xml.bind... within ehcache-3.10.0-alpha0.jar
e.g. import javax.xml.bind.Marshaller;
Maybe some issues with building the package because there is a java-source file with jakarta instead of javax.xml.
I think I need to wait a bit till a release is available.
Thanks for your support! Thomas

Just one thing to check. The 'default' artifacts still use javax packages. The Jakarta version are variants, to depend on them in in Maven you would need:
<dependency>
    <groupId>org.ehcache</groupId>
    <artifactId>ehcache</artifactId>
    <version>3.10.0-alpha0</version>
    <classifier>jakarta</classifier>
</dependency>

or in Gradle (where everything will work more transparently)
implementation('org.ehcache:ehcache:3.10.0-alpha0') {
    capabilities {
        requireCapability("org.ehcache:ehcache-jakarta")
    }
}

Note: I typed the above from memory... I probably put in a bunch of typos and/or mistakes.

Ah.... now it looks better. Thanks for the hint :)

@chrisdennis FYI https://github.com/spring-projects/spring-boot/issues/28800#issuecomment-1049651282

ehcache-xml, ehcache-transactions and ehcache now have Jakarta variants that can be selected using either a capability requirement in Gradle or using a classifier in Maven.

Very nice, thanks @chrisdennis!


Synthesis failed for billing

Hello! Autosynth couldn't regenerate billing. :broken_heart:
Here's the output from running synth.py:
2020-05-08 16:11:33 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php
2020-05-08 16:11:33,597 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 596, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 470, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 515, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 65, in clone
    preclone = get_preclone(url)
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 168, in get_preclone
    preconfig = synthtool.preconfig.load()
AttributeError: module 'synthtool' has no attribute 'preconfig'

Google internal developers can see the full log here.

Autosynth is still having trouble generating billing. :sob:
Here's the output from running synth.py:
2020-05-08 17:07:12 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php
2020-05-08 17:07:12,915 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php
Switched to branch 'autosynth-billing'
2020-05-08 17:07:13 [INFO] Running synthtool
2020-05-08 17:07:13,515 autosynth > Running synthtool
2020-05-08 17:07:13 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 17:07:13,516 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
tee: /tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php: Is a directory
2020-05-08 17:07:13,726 synthtool > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/Billing/synth.py.
On branch autosynth-billing
nothing to commit, working tree clean
2020-05-08 17:07:13,887 synthtool > Ensuring dependencies.
2020-05-08 17:07:13,895 synthtool > Cloning googleapis.
2020-05-08 17:07:14,237 synthtool > Generating code for: //google/cloud/billing/v1:google-cloud-billing-v1-php.
2020-05-08 17:07:18,125 synthtool > Generated code into /tmpfs/tmp/tmptk9hjp1e.
2020-05-08 17:07:18,139 synthtool > No replacements made in **/Gapic/*GapicClient.php for pattern serviceAddress =>, maybe replacement is no longer needed?
2020-05-08 17:07:18,140 synthtool > Replaced '@type string \\$serviceAddress\\n\\s+\\*\\s+The address' in src/V1/Gapic/CloudCatalogGapicClient.php.
2020-05-08 17:07:18,141 synthtool > Replaced '@type string \\$serviceAddress\\n\\s+\\*\\s+The address' in src/V1/Gapic/CloudBillingGapicClient.php.
2020-05-08 17:07:18,142 synthtool > Replaced '\\$transportConfig, and any \\$serviceAddress' in src/V1/Gapic/CloudCatalogGapicClient.php.
2020-05-08 17:07:18,142 synthtool > Replaced '\\$transportConfig, and any \\$serviceAddress' in src/V1/Gapic/CloudBillingGapicClient.php.
2020-05-08 17:07:18,143 synthtool > Replaced '^(\\s+\\*\\n)?\\s+\\*\\s@experimental\\n' in src/V1/CloudBillingClient.php.
2020-05-08 17:07:18,144 synthtool > Replaced '^(\\s+\\*\\n)?\\s+\\*\\s@experimental\\n' in src/V1/CloudCatalogClient.php.
2020-05-08 17:07:18,145 synthtool > Replaced '^(\\s+\\*\\n)?\\s+\\*\\s@experimental\\n' in src/V1/Gapic/CloudCatalogGapicClient.php.
2020-05-08 17:07:18,146 synthtool > Replaced '^(\\s+\\*\\n)?\\s+\\*\\s@experimental\\n' in src/V1/Gapic/CloudBillingGapicClient.php.
2020-05-08 17:07:18,152 synthtool > No replacements made in src/**/**/*.php for pattern Copyright d{4}, maybe replacement is no longer needed?
2020-05-08 17:07:18,153 synthtool > No replacements made in tests/**/**/*Test.php for pattern Copyright d{4}, maybe replacement is no longer needed?
2020-05-08 17:07:18,153 synthtool > Replaced 'will be removed in the next major release' in src/V1/AggregationInfo_AggregationLevel.php.
2020-05-08 17:07:18,154 synthtool > Replaced 'will be removed in the next major release' in src/V1/AggregationInfo_AggregationInterval.php.
2020-05-08 17:07:18,154 synthtool > Replaced 'will be removed in the next major release' in src/V1/PricingExpression_TierRate.php.
2020-05-08 17:07:18,155 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/AggregationInfo.php.
2020-05-08 17:07:18,156 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateBillingAccountRequest.php.
2020-05-08 17:07:18,156 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListSkusResponse.php.
2020-05-08 17:07:18,156 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListProjectBillingInfoResponse.php.
2020-05-08 17:07:18,157 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Category.php.
2020-05-08 17:07:18,157 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/PricingInfo.php.
2020-05-08 17:07:18,157 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetBillingAccountRequest.php.
2020-05-08 17:07:18,158 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ProjectBillingInfo.php.
2020-05-08 17:07:18,158 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/PricingExpression.php.
2020-05-08 17:07:18,158 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListServicesResponse.php.
2020-05-08 17:07:18,158 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Service.php.
2020-05-08 17:07:18,159 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/Sku.php.
2020-05-08 17:07:18,160 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/BillingAccount.php.
2020-05-08 17:07:18,160 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListProjectBillingInfoRequest.php.
2020-05-08 17:07:18,160 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/CreateBillingAccountRequest.php.
2020-05-08 17:07:18,161 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/GetProjectBillingInfoRequest.php.
2020-05-08 17:07:18,161 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListBillingAccountsResponse.php.
2020-05-08 17:07:18,161 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListBillingAccountsRequest.php.
2020-05-08 17:07:18,162 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/UpdateProjectBillingInfoRequest.php.
2020-05-08 17:07:18,162 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListSkusRequest.php.
2020-05-08 17:07:18,162 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/ListServicesRequest.php.
2020-05-08 17:07:18,164 synthtool > Replaced 'Generated from protobuf field ([^\\n]{0,})\\n\\s{5}\\*/\\n\\s{4}protected \\$' in src/V1/PricingExpression/TierRate.php.
2020-05-08 17:07:18,169 synthtool > No replacements made in src/**/V*/**/*.php for pattern final class, maybe replacement is no longer needed?
2020-05-08 17:07:18,175 synthtool > No replacements made in src/**/V*/**/*.php for pattern public function ([s|g]\w{3,})Unwrapped, maybe replacement is no longer needed?
2020-05-08 17:07:18,176 synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 597, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 547, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/google-cloud-php'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Weird dialog

I find this dialog somewhat confusing:

I just started GoldenGATE Editor, chose a configuration, and agreed to update the outdated local configuration.

Oh, this is a feature I put in only later, and I think so far we have only updated existing installations since ... sorry about this, you can simply hit cancel there, as there is no cached data so far. I'll add a respective check.


error in examples for writetable + can't omit quotemark

acording to the examples that should work: writetable("output.dat", df, quotemark = '', separator = ',')
though trying it told me that '' (2 single quotes) is not a valid char. seems legit so far. But how can I use nothing as quotemark?

You can use CSVFiles.jl. You can pass a nothing value for the quotechar argument to omit quotemarks.

Thanks for the report. That's a duplicate of https://github.com/JuliaStats/DataFrames.jl/issues/1080.


Not possible to use version 2<IP_ADDRESS>.104 anymore

What would you like to be added: Gramddict to work with a more recent version. I
Why is this needed: nstagram is forcing users to update instagram leaving no option

Use the last one, and tell me what is not working.. Basic jobs should be OK

same issue. 2<IP_ADDRESS>.111 version works.

Use the last one, and tell me what is not working.. Basic jobs should be OK
Error type 3. Error: Activity class {com.instagram.android/com.instagram.mainactivity.MainActivity} does not exist.

I'm only using 3 jobs and these are not working:
hashtag-posts-recent (no recent tab)
remove-followers-from-file (Object remove doesn't exists. Can't press on it!)
blogger-followers is the only "basic job" working for me.

Use the last one, and tell me what is not working.. Basic jobs should be OK

Basic Jobs are working okay. Thanks for keeping this up. I guess Meta was fighting hard yesterday. But i see this tool as the robin hood against big corp. Very great job.

Use the last one, and tell me what is not working.. Basic jobs should be OK

Error type 3. Error: Activity class {com.instagram.android/com.instagram.mainactivity.MainActivity} does not exist.

that must be an old gramaddict version, we are using monkey to call the ig app which fixes that problem

### Problem: I am getting:Opening post likers.
[03/15 09:06:47]    ERROR | Can't load likers list..
On the newest ig version.
Question: How to fix it? - maybe a older but more recent ig version OR fix gramaddict?

whatever it works under 300


Add the ability to take/see/edit the nutrition photo in the ingredients input

What

Add the ability to take/see/edit the nutrition photo in the ingredients input

Part of

#511

@monsieurtanuki The last mockup I did is this one:

@teolemon Nutrition facts have a tendency to be displayed as tall tables: really not easy to fit on small screens. With a limited added-value too, as we do not extract nutrition facts from the picture.
I rather recommend something like a "add picture" or "see picture" button on top, that would lead to the "official" image edit page:

Sound good


Explicitly set O_NONBLOCK to stdin while running tests #2

While using EpoxyDuino under WSL (Windows Subsystem For Linux) on Windows 10 (running Ubuntu 20.04) I was consistently running into https://github.com/bxparks/EpoxyDuino/issues/2.
Essentially whenever I was running tests from command line, I had to press buttons on keyboard otherwise the main loop was stuck on read. Every keypress meant one execution of the loop and feeding some input was the only way how to run the tests.
In my case explicitly setting stdin to O_NONBLOCK mode fixed the problem.
Before my fix (note the k in output; it was me pressing k to progress with the test; also notice the long duration of the test -- it was mostly waiting for my input):
mmrazik@LAPTOP:/mnt/c/github/project$ tests/SampleTest.out
kTestRunner started on 1 test(s).
kkkTest correct passed.
kTestRunner duration: 6.956 seconds.
TestRunner summary: 1 passed, 0 failed, 0 skipped, 0 timed out, out of 1 test(s).

After my fix:
mmrazik@LAPTOP:/mnt/c/github/project$ tests/SampleTest.out
TestRunner started on 1 test(s).
Test correct passed.
TestRunner duration: 0.006 seconds.
TestRunner summary: 1 passed, 0 failed, 0 skipped, 0 timed out, out of 1 test(s).

Thanks for the PR! As far as I can tell, this PR does not seem to fix #2, but it didn't make things worse. If I do something like SampleTest.out | less, I now see nothing on the less command and it terminates with an error status code, but that's better than just blocking, so I guess it's slightly better? But I will accept PR because it fixes your problem on WSL.
I think the problem with piping to less in #2 is that both the EpoxyDuino program and less attempt to read from the stdin in raw mode at the same time (since less needs to respond to keyboard inputs), and they conflict with each other. I probably need to detect this condition and do something in main.cpp, but I don't have sufficient knowledge of Linux/POSIX/Unix programming to figure this out, and it just hasn't been a high enough priority for me to spend time on it.

@bxparks seems like you are able to reproduce #2 at least with a limited success. How/what are you using?
I tried multiple things (different terminals, running on native ubuntu and not WSL, ...) but I can't reproduce. I would try to have a look but right now I am a bit stuck.

The problem seems to happen if too much data is printed to the SERIAL_PORT_MONITOR. (I have a handful of tests in one of my other projects that has between 260 to 390 tests). I created a minimal reproducible example and checked it in at examples/PipeFail. You should be able to reproduce by typing:
$ cd examples/PipeFail
$ make
$ ./PipeFail.out | less  # <-- fails
$ ./PipeFail.out < /dev/null | less # <-- succeeds
``

Thanks!
However, I have still no luck with reproducing this :( Both WSL on Win10 and Ubuntu 20.04 on bare metal works for me.
What operating system do you use?


Add Section to README on Virtus & Arrays of IDs

I think this is a not uncommon situation, and when I ran into it it took a little bit of research to find a good solution.  (I wanted to avoid the custom schools= method, since that seemed like a "last resort" solution.)
I think this technique has a lot of benefits, especially readability and the ability to easily add min/max testing.

Hey Ryan, thanks!
Can you document this in a Wiki page? This is very specific information that might blow up our README.
Also, why don't you use :prepopulate_if_empty or :populator for that? That option's intention is exactly that: process the incoming values and transform them into models. Have you considered one of those options?
Anyway, cool idea that you came up with - I never thought of that haha. :+1:

Sure, I can put that section in the Wiki.
Now, please correct me if I'm misunderstanding the feature, but prepopulating is used for setting up the form object for display but has no role in processing the received data after the data is passed back.
In this case (not uncommon, I think) the select field contains id/name pairings for already existing objects, and this data is loaded in via AJAX.
The problem I was running into was that I had to write a custom setter method to convert the array of ids back into an array of models to store.  (And this conversion or something like it had to happen since it was a HABTM.)
Using the Virtus technique above obviates the need for writing that custom setter method in (I think) a much more readable way.
That said, I haven't played around with prepopulating a lot, so please correct me if my understanding of the feature is off.

Also, as an aside, thanks for your work on Reform.  It's made my code so much more readable and maintainable since I started using it.  :+1:

@posgarou Haha, I am talking about population, not about pre-population. This is discussed in my book in chapter 5 and should clarify your misunderstandings. Please please please do let me know if it doesn't!
Thanks for your support, go spread the word!

Good to know!  Thanks!


v0.1.0

:eyes: Preview

I think that's good enough. It's pretty simple for this much text 😛

This looks good to me! Is there anything in particular here that you'd like specific feedback on?

@QuinnWilton I think it's a pretty simple spec, so I'm not surprised that there aren't big contentous issues. I guess the main thing is some people really care about maps vs tuples for extensability, but I don't think that's going to be a problem for us (she says, tempting fate)

Makes sense! Well, I've always been one to tempt fate, so what you have here looks good to me :)


scannet_means.npz and scannet_reference_means.npz

Hi @ch3cook-fdu thanks for the great work! I was able to reproduce your results on the ScanRefer dataset and now I want to try it on a new dataset. I see that you use 2 mean arrays - data/scannet/meta_data/scannet_means.npz and data/scannet/meta_data/scannet_reference_means.npz in the model, both with shape (18, 3). Could you let me know how you computed these, and how to do it for a new dataset?
Thanks!
Chandan

Thanks for your interest in our work! These .npz files are only used for VoteNet. If you are training our Vote2Cap-DETR families, these are not required. Feel free to discard any code that relates to these files.

Thanks for the quick response!


Grouping by raceclasses in starting order should be solved by adding a property to the raceclass, e.g. group.

Grouping by raceclasses in starting order should be solved by adding a property to the raceclass, e.g. group.
Originally posted by @stigbd in https://github.com/langrenn-sprint/race-service/issues/19#issuecomment-944926688

Solved by 200f7cc


Suggestion to Merge PR for Enhanced Azure.Communication.Email v1.0.0 Support

Hello,
I would like to bring to your attention a pull request in the Eiromplays/FluentEmail repository (PR #1), which refactors the AzureEmailSender to support the latest stable version of the Azure.Communication.Email package (v1.0.0). I believe integrating these changes into the jcamp-code/FluentEmail repository would not only enhance Azure integration but also improve the upgradability of the Azure.Communication.Email package.
Key Changes in the PR:

Removal of sender name from email send requests to align with Azure standards.
Transition of AzureEmailSender to a singleton registration for efficiency.
Update to the stable version of Azure.Communication.Email package, enhancing the stability and future-proofing the library.

Integrating this PR would ensure that the FluentEmail package remains compatible with the latest advancements in Azure email communication, providing a more robust and scalable solution for users.
I look forward to your evaluation and consideration of this integration.

You know, I was just looking at this.  I saw the Azure sender was using an old package.   I will get this merged too.


Android bundle size

Describe the bug
Not really a bug but the bundle size of our android app has almost doubled since 0.2.0. Wondering if anyone else found this issue?
Guessing is stripe android SDK dependant? Not sure if the issue will be mitigated on 17.1.1? Tried modifying but it errored on build
Additional context
React Native 0.64.2
buildToolsVersion 30.0.2
compileSdkVersion 30
targetSdkVersion 30
Gradle 4.1.0

I wonder if it's because of https://github.com/stripe/stripe-react-native/pull/441/commits/7b5ef7be948f0985ef4475ef69bf9ae1cccfa4ed
We'll need to investigate.

@acatalina I've checked that and turns out that this increase comes from stripe-android library and this significant difference was introduced in v16.10.0
I believe that were mandatory changes and cannot be reverted.
@michelleb-stripe  fyi

@acatalina In the latest version of the stripe-android native library we are using Jetpack Compose.  With this change the apk should turn on minify in order to remove unused code.  Unfortunately there is no way for us to do this from our library.
If you do not already have proguard enabled in your app, here are a few steps to enable it for the first time in your app.  Effectively we will enable minifyEnabled and configure it to keep everything except androidx, and not to obfuscate anything (not even androidx).
android {
...
    buildTypes {
        release {
            // This will enable the use of proguard-rules.pro and remove unused code
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            ...
        }
    }
}

and in the proguard-rules.pro file:
\# Depending on the libraries you have included in your app you might need to include other classes to keep.   After building the apk take a look at the usage.txt file generated.  If you see other package names besides androidx, add them into the proguard-rules.pro file.

\# This is helpful to identify which packages are being shrunk
-printusage usage.txt

\# This disables obfuscation, it is not needed to shrink code
-dontobfuscate

# Packages listed here with `-keep` will not have minification applied to their classes, member, or subclasses.  Notice androidx is purposefully not included in the list so used code from androidx is removed/shrunk/minified. Packages listed here and not included in your apk will have no effect and can be removed if desired.
-keep class android.** { *; }
-keep class com.** { *; }
-keep class java.** { *; }
-keep class javax.** { *; }
-keep class org.** { *; }
-keep class kotlin.** { *; }
-keep class kotlinx.** { *; }
-keep class okio.** { *; }
-keep class okhttp3.** { *; }
-keep class dagger.** { *; }
-keep class sun.** { *; }
-keep class dalvik.** { *; }
-keep class bolts.** { *; }

In doing this we have actually decreased the size of the resulting apk back to sizes from the 0.1.5 release, and in some cases it is even smaller.

ok, with this flag i can Save up to 1,5 mb.
For the future (since not everybody uses all the Stripe Payment Features) do you think is possible to "select" with a flag or an option, what to load?
For example, if I use the payment Sheet (which uses the Jetpack compose), I load that library, if i use the wallet payment only (google pay, apple pay) i don't load it, maybe it would be useful to decrease the apk size

This is something that we do have on our backlog.

This is something that we do have on our backlog.

great! :)

This is something that we do have on our backlog.

Any updates on this?


bug map._move parameter supressEvent be assigned Accidently

https://github.com/Leaflet/Leaflet/blob/4e0e97a6311e721a46699ae6e51f2c81ab348863/src/map/handler/Map.TouchZoom.js#L100 the moveFn here expect supressEvent  to be undefind but the next line this._animRequest = Util.requestAnimFrame(moveFn, this, true);
according to requestAnimationFrame function description :
The callback method is passed a single argument, a DOMHighResTimeStamp, which indicates the current time (based on the number of milliseconds since time origin).
so supressEvent  will be assign to the DOMHighResTimeStamp
maybe this is a bug

@AMDvsTMD wow very nice catch!
It would be nice if you can add a PR for this.
Change
var moveFn = Util.bind(map._move, map, this._center, this._zoom, {pinch: true, round: false});

to
var moveFn = Util.bind(map._move, map, this._center, this._zoom, {pinch: true, round: false}, undefined);


Read Before Opening YTDL Issue

Youtube is made for humans. not robots
and also youtube officially not allowing to download things from youtube
this is the reason behind this issue
I dont know what to do. I did the only thing i can do by adding saavn and deezer play.
If anyone have a solution. We are always open

HTTP Error 429: Too Many Requests or 402: Payment Required
These two error codes indicate that the service is blocking your IP address because of overuse. Usually this is a soft block meaning that you can gain access again after solving CAPTCHA. Just open a browser and solve a CAPTCHA the service suggests you and after that pass cookies to youtube-dl. Note that if your machine has multiple external IPs then you should also pass exactly the same IP you've used for solving CAPTCHA with --source-address. Also you may need to pass a User-Agent HTTP header of your browser with --user-agent.
If this is not the case (no CAPTCHA suggested to solve by the service) then you can contact the service and ask them to unblock your IP address, or - if you have acquired a whitelisted IP address already - use the --proxy or --source-address options to select another IP address.

https://github.com/ytdl-org/youtube-dl/issues/23638

Bot not support in my group

Bot not support in my group

Hello 🙄

yt-dlp 🙄


Data is being returned using Supabases's GraphiQL browser but not when I use the HTTP API

Describe the bug
Not sure if this a "bug" but data is being returned using Supabases's GraphiQL browser but not when I use the HTTP API
To Reproduce
Click here
Expected behavior
Click here
Screenshots
Click here for code snippets
Versions:

PostgreSQL: [e.g. 14.1]
pg_graphql commit ref: ea2ab60

Hi @patelc75,
By default the role used in the GraphiQL editor in the browser is the service_role, which will bypass your RLS policies. If you don't have any RLS policies no data will be returned by default. You can learn more about RLS here: https://supabase.com/docs/guides/database/postgres/row-level-security