[SUPPORT]flink-cdc-2.4 and flink-1.17.1 and hudi-0.14.0, the jvm metaspace of JobManager maybe memory lake

here is the memory summary, I think it do not need 200+ MB for metaspace

here is the DAG:

here is the sql:
CREATE TABLE ods (   id                                  DECIMAL(20, 0),   company_id                          DECIMAL(20, 0),   company_type                        TINYINT,   company_name                        STRING,   company_name_english                STRING,   establish_date                      TIMESTAMP(3),   register_addr                       STRING,   register_capital_amt                DECIMAL(20, 0),   register_capital_currency           INT,   actual_capital_amt                  DECIMAL(20, 0),   actual_capital_currency             INT,   company_registation_status          STRING,   company_logo_url                    STRING,   company_shortname                   STRING,   company_phone                       STRING,   company_email                       STRING,   company_website                     STRING,   social_security_headcount           BIGINT,   business_type_id                    DECIMAL(20, 0),   original_type                       STRING,   tyc_credit_rating                   INT,   longitude_by_baidu_api              DECIMAL(20,15),   latitude_by_baidu_api               DECIMAL(20,15),   unified_social_credit_code          STRING,   org_type                            STRING,   is_micro_enterprise                 TINYINT,   industry_national_std_lv1_code      STRING,   industry_national_std_lv2_code      STRING,   industry_national_std_lv3_code      STRING,   business_areacode_00                STRING,   business_areacode_01                STRING,   business_areacode_02                STRING,   crawl_time                          TIMESTAMP(3),   province_base_by_register_institute STRING,   create_time                         TIMESTAMP(3),   update_time                         TIMESTAMP(3),   op_ts TIMESTAMP(3) METADATA FROM 'op_ts' VIRTUAL,   PRIMARY KEY (id) NOT ENFORCED ) WITH (   'connector' = 'mysql-cdc',   'hostname' = 'ee59dd05fc0f4bb9a2497c8d9146a53cin01.internal.cn-north-4.mysql.rds.myhuaweicloud.com',   'port' = '3306',   'username' = 'jdhw_d_data_dml',   'password' = '2s0^tFa4SLrp72',   'database-name' = 'company_base',   'table-name' = 'company_index',   'server-id' = '6128',   'scan.startup.mode' = 'earliest-offset' ) 2023-12-05 16:39:28.061 [INFO] [flink-akka.actor.default-dispatcher-4] (HudiJob.java:38) - sql:  CREATE TABLE dwd(   id                                  DECIMAL(20, 0),   company_id                          DECIMAL(20, 0),   company_type                        TINYINT,   company_name                        STRING,   company_name_english                STRING,   establish_date                      TIMESTAMP(3),   register_addr                       STRING,   register_capital_amt                DECIMAL(20, 0),   register_capital_currency           INT,   actual_capital_amt                  DECIMAL(20, 0),   actual_capital_currency             INT,   company_registation_status          STRING,   company_logo_url                    STRING,   company_shortname                   STRING,   company_phone                       STRING,   company_email                       STRING,   company_website                     STRING,   social_security_headcount           BIGINT,   business_type_id                    DECIMAL(20, 0),   original_type                       STRING,   tyc_credit_rating                   INT,   longitude_by_baidu_api              DECIMAL(20,15),   latitude_by_baidu_api               DECIMAL(20,15),   unified_social_credit_code          STRING,   org_type                            STRING,   is_micro_enterprise                 TINYINT,   industry_national_std_lv1_code      STRING,   industry_national_std_lv2_code      STRING,   industry_national_std_lv3_code      STRING,   business_areacode_00                STRING,   business_areacode_01                STRING,   business_areacode_02                STRING,   crawl_time                          TIMESTAMP(3),   province_base_by_register_institute STRING,   create_time                         TIMESTAMP(3),   update_time                         TIMESTAMP(3),   op_ts TIMESTAMP(3),   PRIMARY KEY (id) NOT ENFORCED ) WITH (   'connector' = 'hudi',   'path' = 'obs://hadoop-obs/hudi_ods/company_index',   'table.type' = 'MERGE_ON_READ',   -- index   'index.type' = 'BUCKET',   'hoodie.bucket.index.num.buckets' = '32',   -- write   'write.tasks' = '2',   'write.task.max.size' = '512',   'write.merge.max_memory' = '0',   'write.precombine' = 'true',   'write.precombine.field' = 'op_ts',   -- compaction   'compaction.async.enabled' = 'false',   'compaction.schedule.enabled' = 'true',   'compaction.trigger.strategy' = 'num_or_time',   'compaction.delta_commits' = '3',   'compaction.delta_seconds' = '3600',   -- clean & archive   'clean.async.enabled' = 'true',   'clean.retain_commits' = '10',   'archive.min_commits' = '20',   'archive.max_commits' = '30',   -- hive   'hive_sync.enabled' = 'true',   'hive_sync.mode' = 'hms',   'hive_sync.metastore.uris' = 'thrift://<IP_ADDRESS>:9083',   'hive_sync.db' = 'hudi_ods',   'hive_sync.table' = 'company_index',   'hive_sync.table.strategy' = 'RO',   'hive_sync.skip_ro_suffix' = 'true' )
INSERT INTO dwd SELECT id, company_id, company_type, company_name, company_name_english, CAST(CONVERT_TZ(CAST(establish_date AS STRING), 'Asia/Shanghai', 'UTC') AS TIMESTAMP(3)) establish_date, register_addr, register_capital_amt, register_capital_currency, actual_capital_amt, actual_capital_currency, company_registation_status, company_logo_url, company_shortname, company_phone, company_email, company_website, social_security_headcount, business_type_id, original_type, tyc_credit_rating, longitude_by_baidu_api, latitude_by_baidu_api, unified_social_credit_code, org_type, is_micro_enterprise, industry_national_std_lv1_code, industry_national_std_lv2_code, industry_national_std_lv3_code, business_areacode_00, business_areacode_01, business_areacode_02, CAST(CONVERT_TZ(CAST(crawl_time AS STRING), 'Asia/Shanghai', 'UTC') AS TIMESTAMP(3)) crawl_time, province_base_by_register_institute, CAST(CONVERT_TZ(CAST(create_time AS STRING), 'Asia/Shanghai', 'UTC') AS TIMESTAMP(3)) create_time, CAST(CONVERT_TZ(CAST(update_time AS STRING), 'Asia/Shanghai', 'UTC') AS TIMESTAMP(3)) update_time, CAST(CONVERT_TZ(CAST(op_ts AS STRING), 'Asia/Shanghai', 'UTC') AS TIMESTAMP(3)) op_ts FROM ods

what jvm cmd can I used for dump the metaspace layout ?

It seems supportted since JDK 11: https://stuefe.de/posts/metaspace/analyze-metaspace-with-jcmd/ with cmd: VM.metaspace

It seems supportted since JDK 11: https://stuefe.de/posts/metaspace/analyze-metaspace-with-jcmd/ with cmd: VM.metaspace

yeah, but we are still JDK8, is there any same issue about metaspace lake?

Found some doc on the web: https://blog.gceasy.io/2022/08/23/inspect-the-contents-of-the-java-metaspace-region/

Found some doc on the web: https://blog.gceasy.io/2022/08/23/inspect-the-contents-of-the-java-metaspace-region/
let me try with -verbose:class

Found some doc on the web: https://blog.gceasy.io/2022/08/23/inspect-the-contents-of-the-java-metaspace-region/

hi danny, here is my class load log, from today 00:00:00

So do you have any clues why the meta space is increasing?

So do you have any clues why the meta space is increasing?

I added this vm options:
-Dsun.reflect.inflationThreshold=2147483647 -XX:SoftRefLRUPolicyMSPerMB=2000
it seems like has some effection, I will keep my eyes on for a while~


Add missing icons in shared/common

What does this pull request change?
Adds missing icons needed by shared/common, but contributed by other plugins
Why is this pull request needed?
Issues related to this change

We can do this. But I think the correct pattern should be that the "other plugins", import their own icons from eds.

We can do this. But I think the correct pattern should be that the "other plugins", import their own icons from eds.

The problem here is that these icons are needed by common, but they are "acceidentally" included in one or several of the other plugins. In my app I have removed almost all other plugins    (by rm -rf in Dockerfile) => Then we get a compilation error in shared/common. Another solution is to remove the reference to these icons in common.


[Bug]: new idps start flow is not returning idpidToken

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
v2.36.0-rc.2
Describe the problem caused by this bug
I call the endpoint an it is returning:
{
   "details": {
      "sequence": "167",
      "changeDate": "2023-08-31T10:16:29.492140Z",
      "resourceOwner": "229802663141703709"
   },
   "authUrl": "STUFFS"
}

It is missing the idpid intent part.
To reproduce
Create an apple idpid and try it with rest api
Screenshots
No response
Expected behavior
No response
Operating System
Docker on ubuntu
Relevant Configuration
No response
Additional Context
No response

Sorry my bad, i was misunderstanding how the api works.


chore(deps): update common-dev-assets digest to 2365130

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
90ac0db -> 2365130

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This issue has been resolved in version 1.9.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Xamarin Forms Compatibility

So just a heads up, the xamarin android support packages and xamarin forms packages have a version dependency and due to this Xamarin Forms projects are still on the 2.3.0 versions of the support library packages. This makes the new version of these bindings incompatible with forms projects. Just thought i'd give you a heads up.

+1 blocking integration of Urban Airship with a Xamarin Forms app.

Version 2.2.1 of the NuGet package is the latest with Xamarin Forms Compatibility.

@JaridKG and @edandersen Looking into it. Our SDK uses a few APIs in newer versions but Ill see what 2.3.0 equates to. Thanks for reporting this.

No problem, there is an upcoming forms release that may fix this issue but at the moment it is blocking because I can't pull in the android fragment support nuget

@JaridKG Do you have a ticket number of forum post you can link me to about the xamarin forms update? We are trying to develop a PCL for the component and it would be awesome if it was actually able to be used in forms

I cant find it now sorry. However checking out the package dependencies https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS>-pre2 it appears users building MonoAndroid7 android apps will be able to update the android packages as necessary, not being bound to a specific version

@JaridKG Thank you! It looks like it should be ok. We will try testing the PRE version to verify it works fine and if not we will try to contact Xamarin for help.

Looks like https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS> might of fixed the issue. Closing for now but please open if it still is causing conflicts.

I am having this issue as well. I cannot update the support libraries as I have other things in my Xamarin Forms Android project that relay on the 23.3.0 support libraries. I started a support request with Urban Airship on a solution. Any suggestions as I need to get android push notifications setup asap.
I have tried to use version 2.2.1 of the urban airship library but I get these warnings below in the log and nothing happens when I send the notification. If you think a more in depth explanation would be useful I can send you want I sent support.
AndroidManifest.xml missing required service: com.urbanairship.analytics.EventService
AndroidManifest.xml missing required receiver: com.urbanairship.push.GcmPushReceiver
I googled these errors and one solution was to add them to the manifest but this does not seem to work. So not sure how to fix this. Any ideas?

Also is there a sample project that uses xamarin forms and the newest urban airship sdk and portable library that actually works?
I tried ot make a new xamarin forms project and put the newest sdk in it with android 7.0 and the newest support libraries but I am getting all kinds of weird compile errors. Is this just me?
Thanks,
Bob

@Bobisback What version of Xamarin forms are you trying to use? Whats your min android SDK version set to? It appears to be fixed with https://www.nuget.org/packages/Xamarin.Forms/<IP_ADDRESS> but only for MonoDroid7.

I have the latest version of Xamarin forms, <IP_ADDRESS>. I am compiling agaist 7.0, and my target sdk is 7.0. But I have other dependancies on the android support library that provide core functionality in my project, including maps, permissions, and some other things. If i try to update I get all kinds of dependency errors. I will post the log. So I am not sure I can just update the support library.
Is it possible to get a stripped down version of the urban airship sdk that only compiles against the 23.3.0 support library? Would it be possible for me to try and download the current sdk and give it a shot?
The issue is that even though xamarin forms supports it nothing else that depends on xamarin forms supports it. So I either loss core functionality and get notifications, or I leave out the notifications and keep my core functionality.
Attempting to gather dependency information for package 'urbanairship.4.2.2' with respect to project 'CitizensConnectMobileApp.Platform.Android', targeting 'MonoAndroid,Version=v6.0'
Attempting to resolve dependencies for package 'urbanairship.4.2.2' with DependencyBehavior 'Lowest'
Unable to find a version of 'Xamarin.Android.Support.v4' that is compatible with 'Plugin.Permissions 1.1.7 constraint: Xamarin.Android.Support.v4 (>= <IP_ADDRESS>)', 'urbanairship 4.2.2 constraint: Xamarin.Android.Support.v4 (>= 24.2.1)', 'Xamarin.Android.Support.Animated.Vector.Drawable 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Android.Support.Design 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Android.Support.v7.AppCompat 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Android.Support.v7.MediaRouter 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Android.Support.v7.RecyclerView 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Android.Support.Vector.Drawable 23.3.0 constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.Forms <IP_ADDRESS> constraint: Xamarin.Android.Support.v4 (= 23.3.0)', 'Xamarin.GooglePlayServices.Base <IP_ADDRESS> constraint: Xamarin.Android.Support.v4 (>= <IP_ADDRESS>)', 'Xamarin.GooglePlayServices.Basement <IP_ADDRESS> constraint: Xamarin.Android.Support.v4 (>= <IP_ADDRESS>)', 'Xamarin.GooglePlayServices.Maps <IP_ADDRESS> constraint: Xamarin.Android.Support.v4 (>= <IP_ADDRESS>)', 'Xamarin.GooglePlayServices.Measurement <IP_ADDRESS> constraint: Xamarin.Android.Support.v4 (>= <IP_ADDRESS>)'.
========== Finished ==========

Not to mention I just tried to create a new xamarin forms project and add the sdk and I was still getting compiling errors. Do you guys have a Xamarin Forms sample with your sdk in it that works?

@Bobisback The dependency issues you posted above can be resolved by updated your support libraries. Those seem to be the only ones that are requiring a specific version. The rest are >=.
Support libraries are generally backwards compatible so you should not have any issues with updating them. It is also best practice to match the support library version with compileSdkVersion. Your current compileSDKVersion is 25, so I would recommend that you update your support libraries.
We currently do not have a xamarin forms sample that I can share. I created a quick xamarin forms project, added the UA SDK and portable library and had 0 build issues. Could you post your output for the new forms sample you created?

I am trying to update my support libraries right now, I am just getting dependency error after dependency error. Most of them read similar to this:
Attempting to gather dependency information for package 'Xamarin.GooglePlayServices.Base.32.961.0' with respect to project 'CitizensConnectMobileApp.Platform.Android', targeting 'MonoAndroid,Version=v7.0'
Attempting to resolve dependencies for package 'Xamarin.GooglePlayServices.Base.32.961.0' with DependencyBehavior 'Lowest'
Unable to find a version of 'Xamarin.Android.Support.Compat' that is compatible with 'Xamarin.Android.Support.Core.UI 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Core.Utils 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Design 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Fragment 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Media.Compat 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Transition 25.1.1 constraint: Xamarin.Android.Support.Compat (= 25.1.1)', 'Xamarin.Android.Support.v4 25.1.1 constraint: Xamarin.Android.Support.Compat (= 25.1.1)', 'Xamarin.Android.Support.v7.AppCompat 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.v7.Palette 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.v7.RecyclerView 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)', 'Xamarin.Android.Support.Vector.Drawable 24.2.1 constraint: Xamarin.Android.Support.Compat (= 24.2.1)'.
========== Finished ==========
So what I am going to do is delete all packages and remove all references and then try to systematically add everything back in. Maybe this will fix it.

Would you recommend updating to the very latest or just what the current sdk needs?

@Bobisback In v24 of the support library they broke everything out into different modules, so I can definitely see the upgrade packages thing stumbling.
I would upgrade to the latest if you can. I am not sure about any known issues, but they tend to make bug fixes every release - https://developer.android.com/topic/libraries/support-library/revisions.html

Ok, I will post back with results. I am reinstalling everything now. Honestly it is probably just some dust clogging up visual studio, I started this project back in forms version 1.4 so hahaha.

@rlepinski Well this is a problem. So I use HttpClient throughout the application. Not being able to use it on android would be a huge issue. Any suggestions?
Attempting to gather dependency information for package 'Microsoft.Net.Http.2.2.29' with respect to project 'CitizensConnectMobileApp.Platform.Android', targeting 'MonoAndroid,Version=v7.0'
Attempting to resolve dependencies for package 'Microsoft.Net.Http.2.2.29' with DependencyBehavior 'Lowest'
Resolving actions to install package 'Microsoft.Net.Http.2.2.29'
Resolved actions to install package 'Microsoft.Net.Http.2.2.29'
Install failed. Rolling back...
Package 'Microsoft.Bcl.Build.1.0.14' does not exist in project 'CitizensConnectMobileApp.Platform.Android'
Could not install package 'Microsoft.Bcl.Build 1.0.14'. You are trying to install this package into a project that targets 'MonoAndroid,Version=v7.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
========== Finished ==========

Never-mind, got it figured out. For reference: https://bugzilla.xamarin.com/show_bug.cgi?id=43070
"More recent versions of NuGet 2.12, 3.4 and 3.5 all fail to install Microsoft.Bcl.Build  1.0.14 into an Android project for some reason.
Xamarin Studio 6.0.1 which uses NuGet 2.8.7 works fine. This also affects Visual Studio so it looks like a change in NuGet has caused a problem.
Xamarin Studio 6.0.2 which uses NuGet 2.12 fails.
Xamarin Studio 6.1 which uses NuGet 3.4.3 fails.
Visual Studio 2015 with the latest beta of NuGet 3.5 also fails.
A workaround is to install the latest Microsoft.Bcl.Build 1.0.21 NuGet package first before installing Microsoft.Net.Http."

@Bobisback Yep, I was just reading that bug report. Glad you figured it out.

@rlepinski So I completely reinstalled everything. Now I am getting 200+ errors related to xamarin android and Xamarin forms missing. They are installed via nuget. I searched google with no luck. Any ideas? I tried clearing the resharper cache. Restarting the computer, restarting visual studio, double checking that I have all the 7.0 apis from teh android sdk manager. What else could cause the xamarin forms from building?

I fixed it by manually adding references to Mono.Android, Mono.Android.Export and some mcslib or something. I found this by comparing project files to see what was missing from the references list.
Now i just have 11 errors related to custom renderer. Something about needing to reference System.ObjectModel. But that is not in my references before.

So I fixed everything by creating a new xamarin forms project. Then editing the android project file to find the missing references and moving these references into my android project file. Magic, no more errors!
<Reference Include="Mono.Android" />
<Reference Include="mscorlib" />
<Reference Include="System" />
<Reference Include="System.Core" />
<Reference Include="System.ObjectModel" />
<Reference Include="System.Xml.Linq" />
<Reference Include="System.Xml" />

Now I am getting a '"java.exe" exited with code 2' error, which means to many refrences. i am guessing it is from updating the google play services. Just not sure how to strip out the extra references. Muti-dexing gives me a error. Proguard gives me a error. Now sure what to do next.

Ok so I solved it with mutidex, which apparently uses proguard as I had to install the updated 7.0 pro-guard package. I also had to move my android sdk to a path that has no spaces or special characters. Otherwise it would error lol.
I am not getting notifications :D
Thanks for all the help.

Awesome, glad you got it working.
Are you pulling in the full google play services or individual modules? If the former you might be able to reduce your method count under the dex limit.

I think i am only pulling in the modules, the name of the package is not "all" so. But I am also using maps and based on my googling it references alot of google play services.
On another note my debugging stopped working now :( someerror about the debugger is broken and to repair or reinstall it hahaha if it is not one thing it is another.

Here are all the packages I am referencing for google play services. I looked through them and all the stuff I have installed have hard dependancies on each one so. Guessing I do not have much choice.

Though I wonder which is better, mutidexing or trying to use pro guard to strip away used code.

@Bobisback Usually you would only use pro guard for a release build, so it probably wont work great for development. You most likely are stuck with multidex for the time unless you are willing to remove some dependencies. Here is the Android doc on multidex - https://developer.android.com/studio/build/multidex.html. I do not have any experience using it with Xamarin.

Ya I noticed that proguard was not working with dev. So mutidexing it is. No big deal lol. As long as people know that compile my project to make sure the android sdk has no spaces or special characters in the path. Otherwise they will get some super weird errors lol. I am just happy it is working and so is my employer. If it cost me debugging in android so be it hahaha (I am repairing visual studio now... fingers crossed).

So just for completeness and then i will stop spamming this thread. Turns out when I was fumbling around with the android project settings I accidentally changed the "debugger" settings to c++, changing it back to .Net (Xamarin) made it work great. hahahah

And now my push notifications do not work again, man I hate android.....

@Bobisback, lets open up a new issue if you are having issues. Will need verbose logs. Try to prevent posting any secrets/keys.

I am not sure, it is working again. I do not know what the hell is going on with it. Sometimes I get the message sometimes I don't. iOS gets it every time though. It would seem if I send a test message it works? Maybe? But if I do a actual message it doesn't work. But if I do a test message then a actual message it works.... idk hahahaha

With android I've noticed you have to completely uninstall the app and reinstall it if you are debugging to that device. After a couple "debug" sessions the channel ID stops receiving notifications for some reason (pretty sure its an android issue not UA but I don't really know). I just uninstall and reinstall when i'm testing the pushes on android and get a new channel ID. iOS the channel ID never changes and always works

I found a solution if you are using android 7.0
https://github.com/urbanairship/xamarin-component/issues/60


Chrome  Refused to get unsafe header "Content-Range

What is the expected behavior? (add screenshot)
Display pdf file in Webpage in angular2 (its a problem with pdf.js I think) dosnt work in Chrome.
What went wrong? (add screenshot)
Refused to get unsafe header "Content-Range" than trying to get the pdf file.
In FireFox it works (After setting the Expose Headers) without problems only Chrome/Vivaldi dont get it.  Following the tutorials and the github topics I set the headers in apache like this:
Header always set Access-Control-Allow-Origin "*"
Header always set Access-Control-Allow-Methods "POST, GET, OPTIONS, DELETE, PUT"
Header always set Access-Control-Max-Age "1000"
Header always set Access-Control-Allow-Headers "Range, Origin, X-Requested-With, Content-Type, Accept, Authorization"
Header always set Access-Control-Expose-Headers: "Content-Length, Content-Encoding, Accept-Ranges, Content-Range"

Still not working.
Any idea ?
EDIT, here the response Header. Range is an allowed header, but Content-Range is missing.
Accept-Ranges:bytes
Access-Control-Allow-Headers: **Range**, Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers
Access-Control-Allow-Methods:POST, GET, OPTIONS, DELETE, PUT
Access-Control-Allow-Origin:*
Access-Control-Expose-Headers:**Accept-Ranges, Content-Encoding, Content-Length**
Access-Control-Max-Age:1000
Content-Length:65536
Content-Range:bytes 0-65535/1228809
Content-Type:application/pdf
Date:Thu, 22 Jun 2017 12:29:31 GMT
ETag:"12c009-52c75353ea3b0"
Last-Modified:Tue, 23 Feb 2016 19:46:39 GMT
Server:Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/7.1.4

Works now in Chrome, in Vivaldi it still not works.. so probably a error of vivaldi. Can be closed.


Store Gateway: Inconsistent error handling on series limits

https://github.com/thanos-io/thanos/pull/6171 changed the Series request to return gRPC status code ResourceExhausted when limit is reached.
However, we didn't do the same thing for LabelValues and LabelNames request, but they will also potentially hit the series limit when matchers are specified. Now LabelNames and LabelValues returns Internal and Aborted error respectively.
https://github.com/thanos-io/thanos/blob/main/pkg/store/bucket.go#L1577
https://github.com/thanos-io/thanos/blob/main/pkg/store/bucket.go#L1765

@yeya24 nice find! We will try to get some new team members to work on this, if you don't mind. Otherwise I'm happy to my time to fix it.

We probably want to do the same for bytesLimiter also

Looks like with #6330 and #6325 merged we can close this, am I right, @yeya24?

Yes, thanks for the reminder.


Feature Request: helm lint should verify that values used in charts are present in values.yaml

Hi! I'd like to see helm lint perform some checks against the values.yaml and the templates, namely that any usage of .Values.someField is cross-checked against the values.yaml file to make sure that it indeed contains someField.
Now, I know that this is sort of complex due to the nature of templating, but in a first iteration, I think a check that just verifies that any direct reference of a value (using .Values.someField) is backed up by a real value.
If there's interest in a feature like this, I would like to submit a PR to implement it

It is frequently expected that the default values provided with a chart are incomplete. And that the user (chart installer) is expected to provide additional values.  For this reason I don't think it really works for lint to verify that the default values are complete.
Better I think would be to provide a jsonschema with the chart. Which verifies values at install time.


BackgroundLocator.isRegisterLocationUpdate() returning false even if notification is showing.

Hello! I'm having trouble connecting to the service after the app has been terminated by Android. If I let the app run in the background for about 15 minutes, the app is terminated by Android, however, the foreground service and location tracking is still operating. When I launch the app again, I want to know if the service is active but BackgroundLocator.isRegisterLocationUpdate() returns false. Has anybody else had the same issues? Is there anything I can do about this?

Your problem should be fixed with PR #120;


Enhancement Request: numbers next to host/service dials

It's nice seeing these dials, but if we can get totals enabled or allowed, that would be nice to see, especially for large deployments. I see this works on hover-over, but making something permanent would be nice for tv displays.

This is a duplicate of #101


Doc Feedback: 6.5.0 mentioned rather than 6.6.0

Location : https://ei.docs.wso2.com/en/latest/micro-integrator/administer-and-observe/using-the-analytics-dashboard/
Starting the Analytics Worker¶
Note
Be sure to start the Analytics worker before starting the Micro Integrator.
Download and install WSO2 Enterprise Integrator **6.5.0**. The location of your WSO2 EI 6.5.0 installation will be referred to as <EI_6.5.0_HOME> from hereon.
Open a terminal and navigate to the <EI_6.5.0_HOME>/wso2/analytics/bin directory.

and typo
To allow the Micro Integrator server and the Analytics server to communicate using SSL, the digital certifacates should be shared by the two servers. See the instructions on adding SSL certificates to keystores.

Fixed the typo.
Thanks for reporting.
Note that we have kept we are generally referring to the EI 6.x.x Analytics profile. However, the links lead to the latest release of the EI 6.x.x family (which is EI 6.6.0).


getting Permission Groups for Sponge

How do you get a specific player's permission group. I'm familiar with spigot's implementation which is:
PermissionUser player = PermissionsEx.getUser(targetPlayer)
player.getGroups()
but I'm unsure with Sponge. Is there a similar implementation for sponge? And if so, where can I find more documentation about it.
Thanks

Use Sponge's Permissions API -- It's documented in Sponge's documentation.
Generally, what you'd do is something like:

public List<Subject> getGroups(Subject user) {
    final PermissionService serv = this.service; // pre-collected variable
    return user.getParents().stream()
        .filter(subj -> subj.getContainingCollection().equals(serv.getGroupsGollection()))
        .collect(Collectors.toList());
}


fix(esm): allow import from mocha in parallel

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions.

Description of the Change
Fixes the issue where import { describe, it } from 'mocha' doesn't work with --parallel when using es modules by proxying describe, it and friends to their actual contextual counterpart.
Alternate Designs
There is not much else we can do I think, other than going full blown esm (for example, using package exports).
Why should this be in core?
Its imported from core (bare 'mocha').
Benefits
Allows import {...} from 'mocha' in an es module setting with parallel
Possible Drawbacks
More code to maintain
Applicable issues
Closes #4559, should be a patch release.

Of course, my new test is failing on node 10 😇 Will have a look at that soon (probably need to enable --experimental-modules)

I ended up skipping the tests on node 10. Importing esm style from a cjs module is supported from node 12.

@nicojs Are describe, it, ... still on global scope with this solution?
import { describe, it } from 'mocha': we don't need an ESM entry point anymore to achieve this?

@juergba Oh, I didn't notice.
This is rich! What happened is interesting. Node.js has this mechanism when you import a CJS file in that it parses it and tries to determine what the named exports are. It uses a very basic parser that looks for standard patterns like exports.abc = ... and others.
What happened was that previously, that parser chocked on the mocha entry point, and defaulted to only default exports. But @nicojs's changes are making that parser very happy, so suddenly it's OK, and mocha is doing named exports from CJS.
Note that my PR is still better because each of the entry points ('/tdd, '/qunit...) exports only the correct test functions per-interface, and does it without the CJS parsing thing (slightly faster), whereas this PR exports them ALL.
But it's definitely progress!

Yeah, I think what was happening is that when you import {describe, it} from mocha the first time, the ESM - CJS interop layer retrieves the named exports, and caches them in ESM land. This is why, in parallel mode, the first job works and the second one does not, because the tests get added to the old suite (cached describe and it).
This PR fixes that, because it allows describe and it to be cached forever. They will never change since they just proxy to whatever suite is loading at that moment in time. I was actually surprised to see this wasn't done already.

@giltayar can you build your ESM entry points on top of this PR? Or does it prevent it in anyway?

[...] whereas this PR exports them ALL

Do we have any negative implications on that?
@nicojs could you have a short look on our watcher, please? I remember difficulties with the UI loading. Maybe we can simplify some coding?

@juergba of course. Once this lands, my PR will return to what it was initially: making Mocha a dual-mode library with real ESM entry points that align with the stamdard interfaces. I will remove all the crud from there that pertains to fixing the problem that this PR fixed (much more elegantly).
But that PR now becomes less urgent, and is now a PR that just fine tunes the entry points to be more "correct" and not exposes all test functions of all the interfaces, but exposes entry points for each interface that expose only the functions for that entry point. The main entry point will still expose everything, for backward compatibility.

It would be awesome to get some feedback regarding the watcher and especially lib/browser-entry.js .
Our browser tests are weak and I want to make sure to not add any regressions with this PR. Thank you.

Hi  @juergba 👋, I've taken a look.

browser-entry.js: wow I haven't taken a proper look at that file yet. It has some hacks (no offense whatsoever),

It overrides mocha.ui and forces a emit of pre-require.mocha.ui = function(ui) {
 Mocha.prototype.ui.call(this, ui);
 this.suite.emit('pre-require', global, null, this);
 return this;
};

This allowed the beforeEach, describe etc to be exported in the previous setup. With this new code change, it still works the same way, except there is the proxy function in between, i.e. these functions are now cacheable.
However, I think I did break something for both browser and non-browser environments:

$ git checkout fix/import-parallel
$ npm run start -- build
$ node -p 'require("./mocha").setup("bdd").Mocha.describe'
 [Function]
$ git checkout master
$ npm run start -- build
$ node -p 'require("./mocha").setup("bdd").Mocha.describe'
[Function] { skip: [Function], only: [Function] }

So apparently the old describe, it etc have functions that are no longer exposed with this PR. We will need to fix that! Is there a way to see an extensive list of these functions?
lib/cli/watch-run.js: The way I understand the watch is that this feature is only supported for commonjs scenarios (there is currently no way to clear from the ESM cache, right @giltayar ?). They should still work with the proxying mechanism because test files are cleared from the require cache and then reloaded. If they use const {describe} = require('mocha') syntax, they should still be allowed to do so, at least, that's what I can deduct from this comment:  // this `require` is needed because the require cache has been cleared.  the dynamic
  // exports set via the below call to `mocha.ui()` won't work properly if a
  // test depends on this module (see `required-tokens.spec.js`).
  const Mocha = require('../mocha');

Ok, i've added proxying of describe.only and friends. I think I've got everything covered except for it.retries and describe.retries. I'm not familiar with that part of our API. @juergba should those also be covered? What .retries mean in this context?
Looking at https://mochajs.org/#retry-tests I can only find this.retries.

@nicojs thank you for your comments. I try to answer some of your questions.
I understand now that we are only talking about the require interface.
The keywords describe etc. will remain in global scope and therefore we don't put at risk neither our browser nor watcher nor parallel workers.
lib/cli/watch-run.js: yes, our watcher is limited to CJS, we have documented that somewhere. Nevertheless some users run ESM in parallel mode, which seems to work. The ESM cache is "cleared" by killing the worker processes on each re-run.
retries(n): has no effect on a passing test. A failing test is re-run max. n times, until it passes or n is reached. In lib/interfaces/bdd.js you see that it.retries exists, but describe.retries does not. I have never used it.retries() yet.
I will need more time to review/test your recent additions. The topic is still fuzzy to me. Where does this context object comes from? IMO we don't need to export each and every alias, eg. describe yes, but it's alias context no.

Thanks for your explanation @juergba
I've tried to add it.retries to the test but it fails because the context seems to always be undefined. This already was the case before this change, so I don't think it ever worked with cjs require syntax,

Where does this context object comes from? IMO we don't need to export each and every alias, eg. describe yes, but it's alias context no.

What do you mean by context? This PR keeps a local variable called currentContext, which is the current mocha context object for the file that is being loaded, but it doesn't export that.
I agree that not every alias needs exporting. Users who are using the "bdd" UI probably don't want suite and test. However, I don't think we can do anything about it without bigger changes. The way I understand it is that, for the cjs-esm bridge to work, your exports should be cacheable. Since one process could run mocha once for a "bdd" project and once for a "tdd" project in the same process (using the programmatic API), I don't see any other way.
One thing we could do is export suite/test from 'mocha/tdd' and export describe/it from 'mocha/bdd', something like that. But that would mean a bigger (breaking?) change.

@nicojs when I test:
const ste = require('mocha').describe;

ste('test suite', () => {
    it('test', () => {
        console.log('running the test');
    });
});

In Mocha v.8.3.0 the test passes, with this branch the result is TypeError: ste is not a function.
The same with import {describe,it} from "mocha";. v8.3.0. is working and this branch fails.
(this synthax already works in v8.3.0 @giltayar 😵😈)
Am I doing something wrong? Or do your test use the global keywords, not the required/imported ones?

Some additional information:

I installed this branch locally with npm install https://github.com/mochajs/mocha#2b608c31:  above test runs succcessfully.
this branch in my local git clone: I changed to const ste = require('./mocha/lib/mocha').describe; and test also passes.
test/integration/fixtures/common-js-require.fixture.js: this test fails in local git clone

    1) Uncaught error outside test suite:
         Uncaught TypeError: Cannot read property 'apply' of undefined

I've tried to add it.retries [...]: I agree, doesn't seem to work, so we just ignore it as before.
I suggest adding xdescribe, since we are already exporting xit.
Exporting named functions eg. exports.describe = function describe(...args) {  would make debugging easier.

@juergba the error in test/integration/fixtures/common-js-require.fixture.js is per-spec. The test in that fixture has a delayed run and according to https://mochajs.org/#delayed-root-suite, you need to add a --delay. Adding that option when running the test removed the failure. Not sure,BTW, why that option is needed. It is used in mocha.js, in this line of the prerequire hook:
    context.run = mocha.options.delay && common.runWithSuite(suite);

If I remove the mocha.options.delay &&, everything works without the --delay flag.
This could be something that was introduced because there was no proxy? As a hack? Something that maybe isn't needed anymore?

The reason why I've added --delay was so I could test that exporting run would also work. The test is now testing every single export. I've added a remark in a comment to make this more clear.

I suggest adding xdescribe, since we are already exporting xit.

I did that now. Note that this is technically a new feature since it wasn't exported before.


Flexbox exercises : Updating index.html

Complete the following REQUIRED checkboxes:

[ /] I have thoroughly read and understand The Odin Project Contributing Guide
[/ ] The title of this issue follows the location for request: brief description of request

The following checkbox is OPTIONAL:

[/ ] I would like to be assigned this issue to work on it

1. Description of the Feature Request:
One  is missing , so it can behaves as expected
2. Acceptance Criteria:

3. Additional Information:

I have already submit the correction on one of my  repositories

Good morning!
For sure on the last part there is one  missing in the solution.html
, this causes the header to behave differently as expected.
I just added it so it changes the size if the window is manipulated.
I forked the project and update this :)
El El lun, jun. 6, 2022 a la(s) 11:09 a.m., Uday Mehtani <
@.***> escribió:

Hi @rommo-e https://github.com/rommo-e! Can you please explain this
issue with more details?
—
Reply to this email directly, view it on GitHub
https://github.com/TheOdinProject/css-exercises/issues/181#issuecomment-1147622113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AORIP65JTFON2V7ZXLQXWKTVNYPCZANCNFSM5XVDYBXA
.
You are receiving this because you were mentioned.Message ID:
@.***>


GitHub.smimesign 0.2.0-rc1, fixes #187533

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[X] Is there a linked Issue? #187533

Manifests

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Automatic Validation ended with:

Executable C:\Program Files\smimesign\smimesign.exe returned exit code: 1

(Automated response - build 897.)

The return code appears to work as intended; the program complains about missing parameters.

Hi @no-preserve-root,
Our validation pipeline was built with Windows Forms in mind, and expects programs to return a zero error code when run without arguments. But most CLI applications return an error when run without arguments. Some have an exit code as high as 254, so I usually pass applications whose exit code is less than 4 digits.
Apologies for the delay - please understand that the previous reply was posted by my hourly automation, and that I'm just now getting to this PR.

Verify:
This application presents a message box:

Clicking Yes gives:

But really, it's a tray-based app:


Using Observable: reject-first logic makes it impossible to track partially succeeded tasks

Thanks for this great tool we are happy with most cases! However, when we dig deeper when using Observable with multiple tasks running in parallel, if partial success/failure happens, the context object which is available in resolve cannot be retrieved from the catch part. So is it correct this means context is only working when all_success case happens? It's not usable when any failure happens?

I figured it out: the ListrError class object actually contains the context.
{
  context,
  errors,
  ...
}

Close this issue


$ missing at runtime despite ProvidePlugin

Webpack seems to not notice the use of globals intended to be provided by ProvidePlugin if they are not at the top-level of the file?
In the config I have:
new webpack.ProvidePlugin({
  $: 'jquery'
}),

If the source file uses "$" at the top-level things are fine; if the first use is in a callback then there are problems. E.g.,
console.log($); // If I comment this out, the call below fails (ReferenceError: $ is not defined)

class Foo {
  post() {
    $.ajax(); // Error here if log above is commented out.
  }
}

webpack 1 doesn't understand ES6 syntax. webpack 2 will do.


remove newline at the end of runner output

This comes into play when the Task outputs plain text message and has an error code.
#!/usr/bin/ruby

puts "failure message"
exit 1

before
{"Error": "failure message\n"}

after
{"Error": "failure message"}

alt: we can put the chomp into the Task


[TASK] Frontend: change requests to use new GET /api/v1/version endpoint (if necessary)

It was not necessary. Closing it.


UHDM::instance::vpiDefFile is blank

In elaborated designs, the vpiDefFile is always blank (along with vpiDefLineNo). This seems like a bug according to the IEEE 1800 doc.

Fixed by #1603  in Surelog

Nice, thanks!


eni: infinite trigger resync node when eni count of node is reached eni limits

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

If node need more ip to allocation but no eni is available, it need create more eni.
But the count of eni in instance is reached eni limits, so  n.ops.CreateInterface  and n.createInterface(ctx, a.allocation) alway return error and  https://github.com/cilium/cilium/blob/2cacf2bc62faed23c2137382d720a8314c8f1108/pkg/ipam/node.go#L485-L498 https://github.com/cilium/cilium/blob/2cacf2bc62faed23c2137382d720a8314c8f1108/pkg/ipam/node.go#L813-L840
maintainIPPool return error and alway trigger resync node
https://github.com/cilium/cilium/blob/2cacf2bc62faed23c2137382d720a8314c8f1108/pkg/ipam/node.go#L845-L867
https://github.com/cilium/cilium/blob/2cacf2bc62faed23c2137382d720a8314c8f1108/pkg/ipam/node.go#L893-L921

Cilium Version
master  2cacf2bc62faed23c2
Kernel Version
no
Kubernetes Version
no
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think to fix like this in handleIPAllocation, nodehandler add a method IsReachENILimits() to test whether reach the limit.
If reach the limit, not to create eni  return false, nil.
func (n *Node) handleIPAllocation(ctx context.Context, a *maintenanceAction) (instanceMutated bool, err error) {
	scopedLog := n.logger()
	if a.allocation == nil {
		scopedLog.Debug("No allocation action required")
		return false, nil
	}

	// Assign needed addresses
	if a.allocation.AvailableForAllocation > 0 {
		a.allocation.AvailableForAllocation = math.IntMin(a.allocation.AvailableForAllocation, a.allocation.MaxIPsToAllocate)

		err := n.ops.AllocateIPs(ctx, a.allocation)
		if err == nil {
			n.manager.metricsAPI.IncAllocationAttempt("success", string(a.allocation.PoolID))
			n.manager.metricsAPI.AddIPAllocation(string(a.allocation.PoolID), int64(a.allocation.AvailableForAllocation))
			return true, nil
		}

		n.manager.metricsAPI.IncAllocationAttempt("ip assignment failed", string(a.allocation.PoolID))
		scopedLog.WithFields(logrus.Fields{
			"selectedInterface": a.allocation.InterfaceID,
			"ipsToAllocate":     a.allocation.AvailableForAllocation,
		}).WithError(err).Warning("Unable to assign additional IPs to interface, will create new interface")
	}

	if !n.nodehandler.IsReachENILimits() {
   	err = n.createInterface(ctx, a.allocation)
   	return err == nil, err
   }
   return false, nil
}

Generally speaking, we already in-cooperate the limits here:
https://github.com/cilium/cilium/blob/24a7e412b1196e829d76c22ad44613d56937d58b/pkg/aws/eni/node.go#L259
And the code should bail out here:
https://github.com/cilium/cilium/blob/eac0dee9d6110d340ea7df6885486b4327052d2f/pkg/ipam/node.go#L472-L484
So it would be interesting to know under what circumstances the AvailableInterfaces field is not set up correctly.

Sorry, I misunderstand. that is not consider that condition. https://github.com/cilium/cilium/blob/24a7e412b1196e829d76c22ad44613d56937d58b/pkg/aws/eni/node.go#L259

Generally speaking, we already in-cooperate the limits here:
https://github.com/cilium/cilium/blob/24a7e412b1196e829d76c22ad44613d56937d58b/pkg/aws/eni/node.go#L259
And the code should bail out here:
https://github.com/cilium/cilium/blob/eac0dee9d6110d340ea7df6885486b4327052d2f/pkg/ipam/node.go#L472-L484
So it would be interesting to know under what circumstances the AvailableInterfaces field is not set up correctly.

@wu0407 Great! Just to double check, did you encounter any issues? We did have bugs in the past where the limit wasn't properly respected and we did enter a faulty resync loop. If that happened to you, it would be useful to understand why, as there might be an undiscovered bug.


libtiff: add patches for many related CVEs

Description of changes
https://nvd.nist.gov/vuln/detail/CVE-2023-0795
https://nvd.nist.gov/vuln/detail/CVE-2023-0796
https://nvd.nist.gov/vuln/detail/CVE-2023-0797
https://nvd.nist.gov/vuln/detail/CVE-2023-0798
https://nvd.nist.gov/vuln/detail/CVE-2023-0799
https://nvd.nist.gov/vuln/detail/CVE-2023-0800
https://nvd.nist.gov/vuln/detail/CVE-2023-0801
https://nvd.nist.gov/vuln/detail/CVE-2023-0802
https://nvd.nist.gov/vuln/detail/CVE-2023-0803
https://nvd.nist.gov/vuln/detail/CVE-2023-0804
Built passthru.tests on indicated platforms.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Hmm this set of patches don't appear to solve https://gitlab.com/libtiff/libtiff/-/issues/499 or https://gitlab.com/libtiff/libtiff/-/issues/495 for me

Looks like I just needed to include the tiffcrop portion from https://gitlab.com/libtiff/libtiff/-/commit/d63de61b1ec3385f6383ef9a1f453e4b8b11d536

Built on aarch64-linux and aarch64-darwin on master.

Looks like we never backported these.


Fix Error Handling On Creation Failure

I see we are not propagating the volume provisioning error from node agent to controller to enable volume rescheduling on some other node (as we used to do with lvm localpv plugin). Can we fix it to enable rescheduling on provisioning failure to some other node?
https://github.com/openebs/device-localpv/blob/5212adbb17b9089426b00ba1f5da6b1366f2214b/pkg/mgmt/volume/volume.go#L75-L98

VolumeError needs to be returned from the node agent similar to done in LVM local PV here.


add routeDepth into stubRouterContext method

Hello,
If you want to test an element with <RouteHandler /> component in it, you need in additional the routeDepth into stubRouterContext.
I don't know the side effects but this was proposed by @taurose in the issue I have created: https://github.com/rackt/react-router/issues/1055
Best.

thanks :)


Prisma Integration How to

I've created projects using graphqlgen (https://oss.prisma.io/graphqlgen/)_ and using prisma init (https://www.prisma.io/docs/1.22/get-started/01-setting-up-prisma-new-database-JAVASCRIPT-a002/)
It is not at all clear to me how to configure each and what prisma generate does vs graphqlgen. I can't be the only one that's thoroughly confused by how to setup a project correctly. Currently, the prisma docs just say  graphqlgen exists but not how to do anything with it. The graphqlgen docs don't mention Prisma at all.
Updating the guides on how to integrate both would be really helpful to myself and others. If this documentation exists somewhere already, please send me to it. I'm so confused.

I got it all figured out now, but not without some significant struggle that could have been avoided. I was able to do it by looking at a lot of different projects. I guess what's really not made clear is the work flow for adding to the database and what each generation tool does.
I wish I focused on that project. The readme does have the correct process for developing. I guess I'm suggesting this process be added to the official documentations / tutorial pages.