Search and Config menus are not shown

Issue / Feature
When I add the package to my app, the search and config menus are not shown in the appbar, instead an overflow menu is shown with "Go Back". The sample app and the FlutterEbookApp are working fine. I don't know what am I missing.
Platform (android, iOS or both)
Android - didn't check on iOS
**Steps to reproduce / Describe in detail **
I'm following the tutorial. I don't know what am I missing:
app\build.gradle
buildTypes {
        release {
            signingConfig signingConfigs.signConfig
            minifyEnabled false
            shrinkResources false
        }
        debug {
            minifyEnabled false
            shrinkResources false
        }
    }

pubsec.yaml
dependencies:
  flutter:
    sdk: flutter
...
  epub_viewer: ^0.1.9

Usage:
EpubViewer.setConfig(
                            identifier: 'androidBook',
                            themeColor: Theme.of(context).accentColor,
                            scrollDirection: EpubScrollDirection.VERTICAL,
                            enableTts: false,
                            allowSharing: true,
                          );
                          await EpubViewer.openAsset(
                            'assets/TheSilverChair.epub',
                          );

// Get locator which you can save in your database
                          EpubViewer.locatorStream.listen((locator) {
                            print(
                                'LOCATOR: ${EpubLocator.fromJson(jsonDecode(locator))}');
                            // convert locator from string to json and save to your database to be retrieved later
                          });

The menus are shown in the release build not the debug build.


Angular(@latest) - cli implementation

Configuration:

PDF.js version: 1.8.593

Hi,
Not really sure where to raise this, but I am having issues using Pdf.js with Angular-cli. I kinda got it working in chrome, but on IE and edge it just doesn't load and throws an exception. I am sure i am not implementing it correctly.
In the .angular-cli.json i have implemented the following scripts:

In my component i have imported the following:

And obviously in my index.html I have put the following Meta tag
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
In edge i get the following error:

Which seems to be when trying to stream the PDF data into scope. In IE pollyfills seems to be giving the issue:

Thanks,
Justin

Can you provide complete source code for the example that reproduces the issue?

Hi,
My company is blocking stuff like plunker. I will have to reproduce at home. Is there no documentation that demonstrates a step by step CLI integration with the viewer and thumbnail control.
Thanks,
Justin Darmanovich

Closing since no response has been provided and specific Angular questions are out of scope for PDF.js itself. Note that we have a Webpack example at https://github.com/mozilla/pdf.js/tree/master/examples/webpack, which may help you.


Problems accessomg multi asset based wallets on mobile

A user reported (on community tech support) an issue while trying to access his wallet on Yoroi mobile device after sending it a NFT:
unknown:ReactNative: Row too big to fit into CursorWindow requiredPos=0, totalRows=1

Unfortunately he does not have his mnemonics to try and access it from another wallet/CLI/etc so he is stuck waiting to be able to access his funds.
Logcat from android device
2021-08-22 14:03:36.524 22767-22849/? W/CursorWindow: Window is full: requested allocation 2241428 bytes, free space 2096658 bytes, window size 2097152 bytes
2021-08-22 14:03:36.524 22767-22849/? E/SQLiteQuery: exception: Row too big to fit into CursorWindow requiredPos=0, totalRows=1; query: SELECT key, value FROM catalystLocalStorage WHERE key IN (?)
2021-08-22 14:03:36.525 22767-22849/? W/unknown:ReactNative: Row too big to fit into CursorWindow requiredPos=0, totalRows=1
    android.database.sqlite.SQLiteBlobTooBigException: Row too big to fit into CursorWindow requiredPos=0, totalRows=1
        at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
        at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1001)
        at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:838)
        at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
        at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:153)
        at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:140)
        at com.reactnativecommunity.asyncstorage.AsyncStorageModule$1.doInBackgroundGuarded(AsyncStorageModule.java:142)
        at com.reactnativecommunity.asyncstorage.AsyncStorageModule$1.doInBackgroundGuarded(AsyncStorageModule.java:119)
        at com.facebook.react.bridge.GuardedAsyncTask.doInBackground(GuardedAsyncTask.java:36)
        at com.facebook.react.bridge.GuardedAsyncTask.doInBackground(GuardedAsyncTask.java:20)
        at android.os.AsyncTask$3.call(AsyncTask.java:394)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at com.reactnativecommunity.asyncstorage.SerialExecutor$1.run(SerialExecutor.java:25)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:923)

Is the same error reported a lot of times and not addressed.

Hi, @rdlrt! Thank you for providing the details and the logs especially!
We are now actively investigating this issue so the fix might be coming out soon.

@rdlrt , if you will see anyone reporting this issue as well, plz refer them to this issue now 🙌

@rdlrt how many transactions, nfts did the user have at the time of the issue?

@efegure @manupmt @realbluehead , moving the discussion here from https://github.com/Emurgo/yoroi-mobile/issues/1572
Can you plz provide some information on how many different token types or separate NFTs there have been in your wallet when you were trying to restore it in the mobile app?

The problem occurs after having around 50 NFTs, I guess, but if yoroi can't sustain NFTs you should provide this service, anyway I've changed to desktop yoroi and is still verry verry slow, can't believe it, it's like a pc back in "95, I'm verry disappointed..to say the least

@vsubhuman I have a total of 386 tokens in my wallet, I deleted the app twice and restored using my passphrase, first time opening the app works, after killing it and reopening it the error starts to happen.

Thank you, @efegure! We now have a fix candidate for it ready, if everything is good we might have it included in the next update

@vsubhuman I have a total of 386 tokens in my wallet, I deleted the app twice and restored using my passphrase, first time opening the app works, after killing it and reopening it the error starts to happen.

makes sense.
reading from disk is the problem, and that doesn't happen until the second loading of a wallet.

on which versions of android are people experiencing the problem?

on which versions of android are people experiencing the problem?

From here we know @efegure had it on 11: https://github.com/Emurgo/yoroi-mobile/issues/1572
@manupmt @realbluehead, can you please clarify which version you are using?
@rdlrt , if you have any information on which versions people are reporting it from - that would help.

Apologies, somehow I overlooked notifications from this ticket 🙁

@rdlrt , if you have any information on which versions people are reporting it from - that would help.

I will ask others, but the 2 I know so far have been on Android 11 too - do we need specific build numbers?

Looks like all that I have conversation with from community TS had already upgraded to Android 11

I will ask others, but the 2 I know so far have been on Android 11 too - do we need specific build numbers?

Thank you, @rdlrt ! No need for specific build versions

Hello @vsubhuman, is the new version with this update released yet ?

Hi, @efegure, it is not released yet, but is being prepared. Please look out for the version 4.4, this will be release in ~1-2 days from now, if all the testing goes well.


Updated percona-xtradb-cluster to support tolerations & affinity

Updated percona-xtradb-cluster StatefulSet and Values to support tolerations & affinity

/reopen


Upgrade jsoup dependency

Purpose

Upgdare jsoup dependency version to 1.15.3 to fix the vulnerability.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2997911596

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2997911596
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2997911596

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2997911596
Status: success


Viewer.html of 2.4.456 is not working for multiple prints

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome 81
Operating system and its version: Windows 10
PDF.js version: 2.4.456
Is a browser extension: No

Steps to reproduce the problem:

Make the following code changes to  viewer.js.
//add the function below
function receiveMessage(event) {
var selfDomain = window.location.origin ? window.location.origin : (window.location.protocol + '//' + window.location.hostname + (window.location.port ? ':' + window.location.port : ''));
if(event.origin === selfDomain && event.data){
if(event.data['cmd'] === "SET_PDF_BLOBURL"){
var ctxBlobUrl = event.data['url'];
webViewerLoad(null,ctxBlobUrl);
}
}
}
// Modify webviewerload function like below
function webViewerLoad(event,ctxPDFPrintBlobUrl) {
let config = getViewerConfiguration();
window.PDFViewerApplication = pdfjsWebApp.PDFViewerApplication;
window.PDFViewerApplicationOptions = pdfjsWebAppOptions.AppOptions;
if(ctxPDFPrintBlobUrl){
config.ctxPDFBlobUrl = ctxPDFPrintBlobUrl;
}
pdfjsWebApp.PDFViewerApplication.run(config);
}
//Modify webViewerInitialized function like below
function webViewerInitialized() {
var appConfig = PDFViewerApplication.appConfig;
var file;
if(appConfig.ctxPDFBlobUrl){
file = appConfig.ctxPDFBlobUrl;
}else{
let queryString = document.location.search.substring(1);
let params = (0, _ui_utils.parseQueryString)(queryString);
file = 'file' in params ? params.file : _app_options.AppOptions.get('defaultUrl');
}
//....rest of the function as is
Load viewer.html in an iframe and pass blob url via postmessage.
pagesloaded event in parent page should get triggered.

What is the expected behavior? (add screenshot)
pagesloaded event handler should get called
What went wrong? (add screenshot)
pagesloaded event handler does not get called. However same changes in 2.3.200 version's viewer.html is working fine.
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Also when will 2.4.456 will be stable ?

Please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


Add alerts command to compare alerts

Relatively simple. The query basically looks for alerts that are generated by Prometheus but not the ruler, or the opposite.
More or less done but could do with some clean up and I haven't included the vendor changes since I vendored a lot of alertmanager stuff when I was still going down that route so I need to fix that first.
Signed-off-by: Callum Styan<EMAIL_ADDRESS>

updated, not many changes and no vendor updates needed afaict
ptal @gotjosh

If we're going to do this evaluating PromQL rules, could this be an alert and not a new job?
The idea behind the new job was that we could hit the Alertmanager API, which I think we should do to ensure we measure as close to what the users will see.

I guess the question here is, why is it a "bad alert" in the first place? Would be great to somehow explain the rationale behind a mismatching alert.

The thing is right now we don't know if we have alerts that should be generated by both sources but are not for one reason or another, or if there are actually some set of alerts that will never be generated by one source. One example was that API server alert because we had a config issue that meant we never got the metrics required to evaluate the alert properly.

There's something else, running this against one of our clusters it seems like there are 55 occurrences of this? Is the logic accurate?

If the cluster you ran it against doesn't have any alerts from the Ruler that's about what I'd expect to see. It's just running a query that shows you any alerts that are not in both the set of source=ruler and source!=ruler. Very basic.

If we're going to do this evaluating PromQL rules, could this be an alert and not a new job?

Sure, it might be a little noisy but I'm imagining this isn't an alert we'd send to the pager anyways. My plan was to, if we wanted this to be automated in some way, have it run as a short lived job and push to a pushgateway. The reason being, as I outlined above that there may be alerts we run across that maybe should only be generated by one of the two sources, we'll likely want some of config file for this job that contains an ignore list. That just feels cleaner to me than including an alertname!=x,y,z label matcher in the query that we update regularly, but I'm not really sold either solution would be incredibly useful as an automated job after running the code in this PR, and an earlier implementation that did hit the Alertmanager APIs instead.

The idea behind the new job was that we could hit the Alertmanager API, which I think we should do to ensure we measure as close to what the users will see.

The reason I didn't continue with an AM API based implementation is that it was just going to be much more time involved, for example requiring either manually matching up alerts within alert groups(or relying on the internal implementation detail that they're sorting for now), than I assumed we wanted to spend at the moment while just testing whether the ruler and AM work as expected internally. The query used in this PR gets us the same results based on my understanding of what we wanted from this tool.
I can go back down the AM API route if you feel strongly about it @tomwilkie


On the tests page(s) update links to data to relevant "Data" page when available

On the current tests page, after each test description we say "Data collected by [xxxx] is available...". Replace these with links to the "Data" page when content on the data page is ready

Let's evaluate whether this is relevant in a redesign of each tests' page

The page Data > GCS has links to all tests' raw data. Each test page has a link to raw and where relevant, queryable data.  I think we're good on this and can reopen a new issue if needed.


Tab closes without having used the Devtools, whenever executing injected disable-devtool.min.js

I injected the latest version of disable-devtool into a random web page, a Stack Overflow page to be specific, with a chrome extension. For now, it's just an extension that disables the Devtools as its only functionality.
However, immediately after the injection was done and disable-devtool was executed, before I could even try to use the Devtools, the tab was closed by disable-devtool.
I have made a minimal version of the extension which has only a dozen lines of code for the purpose of recreating the issue.

You can use it as follows: Extract the attached ZIP file > Go to the extensions page of Chrome > Enable the Developer Mode > Click Load Unpacked > Select the folder which was extracted from the ZIP archive.
After doing so, immediately the extension is up and running, the code will be injected into any page you refresh, and hopefully, the issue will be recreated (The tab being closed without having used the Devtools)

Disable-Devtool.zip

Fixed! Please upgrade to Version 0.1.7.


Custom Ingestion Schemas

Feature request: We are interested in two new schemes for non OOB sourcetypes on SC4S. The new source types would be Raritan and Cisco Video Expressway. Trying to perform custom config of syslog data ingestion on SC4S for these source types.
Cisco Expressway server:
Model: EXPWY-1200-K9
Software version: X12.5.9
Raritan Model and firmware information.
Model: DSX2-8
Hardware Revision: 0x83
Firmware Version: <IP_ADDRESS>.2131
Model: DSX2-16
Hardware Revision: 0x85
Firmware Version: <IP_ADDRESS>.213
Mypcapfile.docx
1

The pcap attached was a word summary of packets not the actual data can you try again with -w to generate a pcap file

For cisco express, this appears to be another packaging for cisco telepresence which is currently supported. The logs match our current samples if you find corner cases or additional events we need to handle we would be happy to address that. https://splunk.github.io/splunk-connect-for-syslog/main/sources/Cisco/#product-cisco-telepresence-video-communication-server-tvcs


fix covered theme switch popup when i18n is not setup

Didn't notice that you already got this fixed, thanks! Still keeping #783 because I think it can be full-width and show the theme name there in this case.


python311Packages.qdarkstyle: 3.1 -> 3.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.qdarkstyle is: A dark stylesheet for Python and Qt applications
meta.homepage for python311Packages.qdarkstyle is: https://github.com/ColinDuquesnoy/QDarkStyleSheet
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2 with grep in /nix/store/gi0vfnxrnip3g7dx1g9rs3ijvvfddrc4-python3.11-qdarkstyle-3.2
found 3.2 in filename of file in /nix/store/gi0vfnxrnip3g7dx1g9rs3ijvvfddrc4-python3.11-qdarkstyle-3.2

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
electron-cash
electrum
electrum-grs
electrum-ltc
python310Packages.qdarkstyle
python310Packages.spyder
python310Packages.stytra
python311Packages.qdarkstyle
python311Packages.spyder
python311Packages.stytra
smb3-foundry
spyder
vorta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gi0vfnxrnip3g7dx1g9rs3ijvvfddrc4-python3.11-qdarkstyle-3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.qdarkstyle https://github.com/r-ryantm/nixpkgs/archive/270782ec2c983ff368fd1b01e5d4373c5e87199f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/270782ec2c983ff368fd1b01e5d4373c5e87199f#python311Packages.qdarkstyle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gi0vfnxrnip3g7dx1g9rs3ijvvfddrc4-python3.11-qdarkstyle-3.2
ls -la /nix/store/gi0vfnxrnip3g7dx1g9rs3ijvvfddrc4-python3.11-qdarkstyle-3.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @nyanloutre for testing.

Result of nixpkgs-review pr 264709 at 270782ec run on x86_64-linux 1

8 packages failed to build:

electrum
electrum-grs
electrum-grs.dist
electrum.dist
python310Packages.stytra
python310Packages.stytra.dist
python311Packages.stytra
python311Packages.stytra.dist

15 packages built successfully:

electron-cash
electron-cash.dist
electrum-ltc
electrum-ltc.dist
python310Packages.qdarkstyle
python310Packages.qdarkstyle.dist
python310Packages.spyder
python310Packages.spyder.dist
python311Packages.qdarkstyle
python311Packages.qdarkstyle.dist
spyder (python311Packages.spyder)
spyder.dist (python311Packages.spyder.dist)
smb3-foundry
vorta
vorta.dist

Already on master.


Use codicon instead of raw image files

Icon images in media/ is VSCode built-in icons.
This commit will replace them with built-in icons.
ONE-vscode-DCO-1.0-Signed-off-by: Seok NamKoong<EMAIL_ADDRESS>

Could you let me know where I can find the reference? Any URL for reference would help reviewer a lot. :-)

For reviewers, detailed lists and usage of codicon can be found in https://code.visualstudio.com/api/references/icons-in-labels :)


PublicRooms Displays Incorrect Information when Editing Name

When first creating a PublicRoom system, the following will display for the name:
For the channel_name_template, enter a string, with {num} contained if you want it to be replaced with the number of active VCs.
However, when editing the name of the system, you will be met with the following:
Enter a string, with {creator} contained if you want it to be replaced with the VC creator's display name.
{creator} does not work with PublicRooms. However, it does work with PrivateRooms. The best solution in this case would be to make both options work on both systems. As both can identify the invoker of the channel creation.

Thanks for reporting this! I think I just forgot to replace a docstring, as PrivateRooms was created first and quite a bit of code was reused between them. For making the {creator} option work on both of them, I don't think I will be adding that as I don't think the point of PublicRooms reflects having a room creator's name in the channel. However, I will definitely be fixing that docstring to have the correct instructions (that should be pushed in a few minutes, at which point I will also close this issue).


IBM cloud engine runtime deployment failing

When running using the cloud_engine backend for the first time, deployment of the default (or a custom) runtime using default runtime configuration gets stuck:
2023-10-27 14:41:23,638 [DEBUG] code_engine.py:306 -- Deploying runtime: uk.icr.io/model-training/lithops-codeenigne-default-v311:3.0.2.dev0 - Memory: 256 Timeout: 600
2023-10-27 14:41:23,639 [DEBUG] code_engine.py:510 -- Creating container registry secret
2023-10-27 14:41:24,231 [DEBUG] code_engine.py:557 -- Creating job definition lithops-worker-302dev0-cf396359b1
2023-10-27 14:41:24,349 [DEBUG] code_engine.py:639 -- Checking if job definition lithops-worker-302dev0-cf396359b1 already exists
2023-10-27 14:41:24,401 [DEBUG] code_engine.py:650 -- Job definition lithops-worker-302dev0-cf396359b1 not found (404)
2023-10-27 14:41:24,779 [DEBUG] code_engine.py:603 -- Job Definition lithops-worker-302dev0-cf396359b1 created
2023-10-27 14:41:24,779 [INFO] code_engine.py:660 -- Extracting metadata from: uk.icr.io/model-training/lithops-codeenigne-default-v311:3.0.2.dev0
2023-10-27 14:41:24,782 [DEBUG] code_engine.py:760 -- Creating ConfigMap lithops-lithops-worker-302dev0-cf396359b1-metadata
2023-10-27 14:41:25,068 [DEBUG] code_engine.py:703 -- Waiting for runtime metadata
2023-10-27 14:41:25,231 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:41:27,496 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:41:35,273 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:41:45,526 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:41:55,434 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:42:05,482 [DEBUG] code_engine.py:718 -- ...
2023-10-27 14:42:15,534 [DEBUG] code_engine.py:718 -- ...

The metadata job run shows as "waiting" status from IBM and the console is stuck waiting for the response as above. Eventually the job times out on IBM and the console continues to wait. There don't seem to be any logs from the waiting job to understand why it never starts.

Sorry, I managed to find the code engine logs and think this is to do with authorising code engine to pull the container

You need to provide this https://github.com/lithops-cloud/lithops/blob/master/docs/source/compute_config/code_engine.md#configure-ibm-container-registry

Thanks @JosepSampe, I had set these and checked the API key has access to push and pull from the registry. The container build and push works fine, but it looks like the execution on code engine isn't getting permission.
I can see lithops has created an access secret, but GUI shows a warning below this in the configuration: There is a problem loading data from the registry using this access secret
Error from code engine shows:
ErrImagePull : rpc error: code = Unknown desc = failed to pull and unpack image "uk.icr.io/model-training/lithops-codeenigne-default-v311:3.0.2.dev0": failed to resolve reference "uk.icr.io/model-training/lithops-codeenigne-default-v311:3.0.2.dev0": failed to authorize: failed to fetch oauth token: unexpected status: 401 Unauthorized

I'm having the same issue when creating and running the job from the CLI, so have raised a ticket with IBM

Our account was configured to restrict authentication to allow listed IPs. Adding code engine to the allow list resolved the issue


Added flag to display a single model error for MediaLibraryPickerField

Added flag to display a single model error by LocalizationExtensionHandler if media have been removed from the field only. This ensures that no duplicate model error has displayed.
The flag is true when the field is set to remove items without localization and one or more media items cannot be localized.
Afterwards, to display a model error, this flag is checked in combination with the previously implemented checks (if field is required and any media item is selected).

Hi @sebastienros
Any comment on this pr? Can we merge it?


Enable BBOX calculation using CLI and add this to KMLExport

Good input, @yaozhihang. In fact, the calcBoundingBox method of the database util adapter is already available from the impexp-core module. I guess not much more is needed here (note that the coordinate transformation in doCalcBBOX is pointless due to 1) targetSrs = bboxSrs and 2) targetSrs.getSrid() != dbSrs.getSrid()).

Thanks for the input @yaozhihang @clausnagel
I've adjusted the bbox function a little bit (see https://github.com/3dcitydb/importer-exporter/commit/330c51e793484c8cb9131c795233754bcc3f30e6).
I also moved the function getObjectClassIds() from class BoundingBoxOperation to org.citydb.util.Util (see https://github.com/3dcitydb/importer-exporter/commit/19da04baf626449e43cce6de9983085aa90d525c).
The function calcBoundingBox() in class BoundingBoxOperation and the function doCalcBBOX() in class ImpExpCli are however not exactly the same, since the former interacts with the GUI while the latter does not (because it is for CLI). Therefore, I didn't merge both of them into a public static util method.

This PR is open for quite some time now. The CLI will be reworked substantially soon, so this PR should serve as input for this upcoming development.
On the other hand, I think this PR addresses a more general enhancement than just adding another parameter to the CLI. A KML/COLLADA/glTF export is currently only possible if you either provide a list of gml:ids or a BBOX. I think both should be optional and if omitted, the exporter should calculate the required BBOX automatically in the background. Also users of the UI would then benefit from this enhancement.
So, my recommendation is:

to close this PR without merging
to open an issue for automatically calculating the BBOX for KML/COLLADA/glTF exports if the user has not provided one
to make this option available in the new CLI

I think (2) will need some UI rearrangements. And automatically calculating a BBOX should rather be the default option, so that an explicit command-line parameter (3) might even be unnecessary. Thus, a solution for (2) would even be independent from the work on the new CLI.
Thoughts? Objections?

Of course, if the CLI will be reworked soon, there's no need to merge this branch to the current master.
I was thinking the same about the automatic BBOX calculation for KML/COLLADA/glTF exports while implementing this branch some time ago. Will have a look at it ASAP.

@clausnagel I like your proposal.
One thought: should the bbox be calculated based on all contents in database, or those features that satisfy the user-defined filters e.g. feature type filter?

@yaozhihang, well, I think if you have a filters defined, the BBox should only be calculated for the matching features. Only if no filter is specified, the BBox should be calculated based on all content in the database. Would you agree?

Closing now based on unanimous consent. The disucssion on how to automatically calculate the BBOX for KML/COLLADA/glTF exports will take place outside this PR.


node-gyp\5.11.0\include\node\node_internals.h(5): fatal error C1083: Cannot open include file: 'util.h'

Downloaded and installed the 10 GB of Visual Studio Community 2015, installed Python, set the environment variable GYP_MSVS_VERSION, and now I have this error.
How can I fix it? (windows 10 x64)

You could start by telling what exactly you're trying to do, you're leaving me guessing now.  Are you building node.js?  An add-on?  Please post the console output verbatim.

No follow-up, closing.


TopPopup White Safe Area (See Screenshot)

I created the following "alert" popup, and when it displays, the safe area at the top is white, despite my background being dark. I would expect any background to be using .clear by default. As a work around, I have implemented my own PopupConfig.

Hi. Can you share your code regarding this example? I have just tested something similar and every time the view is correct, like on the image below

@9ae8sdf76, hmm, weird, because it works in my case. Try another solution then - remove that background modifier completely from your code, and try to call this method (above your createContent() function)
func configurePopup(popup: TopPopupConfig) -> TopPopupConfig {
     popup.backgroundColour(Color("Primary Background"))
}

It works as expected when I use the configurePopup() and define the backgroundColour() myself.


Issue with unreadCount and isMarkedAsUnread

I'm working on android (java)
When I catch the GetChatHistory event, I check if there are unread messages by checking if Chat.lastReadOutboxMessageId field is the same as Chat.lastMessage.id.
I have an issue with the official Telegram chat (the one that gives me the code for the 2fa): even if I read the chat on the telegram client for android and the client for mac os and web browser, when i get the chat from GetChatHistory event, the Chat.unreadCount is still 1.  I understand that if the Chat.unreadCount equals to 1, it indicates that there's an unread message in the chat (but that actually on every client telegram I've read and it's not marked as unreaded message).
So I also tried to look at the isMarkedAsUnread field, but since it is false, this field also indicates that the chat has been read.
So I wanted to know if the Chat.unreadCount field is correct or a bug, and how can I tell if there are actually unread messages on the cat.

Chat.lastReadOutboxMessageId field is the same as Chat.lastMessage.id

Chat.lastReadOutboxMessageId is not guaranteed to be an identifier of an existing message. Read messages are the messages with messageId <= Chat.lastReadOutboxMessageId.

So I also tried to look at the isMarkedAsUnread field, but since it is false, this field also indicates that the chat has been read.

isMarkedAsUnread can be true, only if unreadCount == 0. Unread count counts only unread messages.

So I wanted to know if the Chat.unreadCount field is correct or a bug, and how can I tell if there are actually unread messages on the cat.

The Chat.unreadCount field is correct. Some Telegram messages are local and aren't synchronized between clients. Service notification about logging in on another device is one of them. It needs to be read on every client independently, so the intruder can't mark it as read or delete. There are a lot of other ways to get local messages, including addLocalMessage method.
A chat has unread messages if Chat.unreadCount > 0.

Hi @levlam, thanks for the response.
In my app I just want to keep the unreaded messages. From all chat everythings works fines, but I've this problem on the Telegram chat (and an another chat channel).
In the case of the Telegram chat, wich tells me that Chat.unreadCount = 1 how can I know that the message is local and i can assume that is read? Could I assume that if messageId <= Chat.lastReadInboxMessageId even with Chat.unreadCount = 1 the message is readed? But also in this case, I have Chat.unreadCount = 1 and the messageId grater than Chat.lastReadInboxMessageId and Chat.lastReadOutboxMessageId (wich means that is a newer message).
So, how can I check if the message is local and I can assume that is marked as read on the client?
Thanks.

If Chat.unreadCount == 1 then the message is not read. The last messageId can't be <= Chat.lastReadInboxMessageId if Chat.unreadCount == 1. The data provided by TDLib is right and consistent.

Sorry, i confuse >= with <=.
For the Telegram chat, I have the following status
Chat.lastReadInboxMessageId =<PHONE_NUMBER>64
Chat.lastReadOutboxMessageId =<PHONE_NUMBER>8
Chat.lastMessage.id =<PHONE_NUMBER>66
Chat.lastMessage.content.text = "New login..."
Chat.isMarkedAsUnread = false
Chat.unreadCount = 1
Chat.id = 777000

Where, unreadCount = 1 and lastMessage.id >= lastReadInboxMessageId. And that's right, the TDLib tells the that there is an unread message (wich is the message that comes after the 2fa code "New login. Dear XXX, we detected a login into your account from a new device on dd/mm/yyyy at hh:mm:ss UTC.")
With that, how I do with the other chats, I fetch the last message (id:<PHONE_NUMBER>66) with GetChatHistory and save to my unreadedMessages List.
The difference between the other chat and the Telegram chat is that, if on the client i read the message, I received an update on the TDLib which update the unreadCount to 0 for the appropriate that (and with that I'll remove the message from my unreadMessages List). With the Telegram chat I don't have any update for the last message (which is got readed on the clients) and it stills remain on my application marked as unread.
You tell me that the message could be a local message: how can I understand that the message that's marked as unread is actually local, so can I mark it as read on my messages list of the application?

"local" message means a message existing only on a specific device. It exists only on the current device and is effectively unread until it isn't read on the every device. If you don't want to show such messages to the user, you can just hide messages from the chat 777000, which will cover most of the cases.

ok! thank you so much for your help!

I'm reopening the issue because I'm facing with the same problem of the Telegram chat with a SuperGroup Channel chat. The unreadCount is 1, and the message on all client is marked as read (even if I clear all the cache and data and try to make the first login, the message is marked as read, how can other client can be know that if the unreadCount is still to 1?).
You told me that "local messages" are handled by the client. But how all other telegram client know that the message is readed even if is marked as unreadCount?
I need to use a collection list in my client to store the messages that the user read instead of using the unreadCount value and check the id every time to avoid this problem? I search on the tdlib sdk a solution but I don't found anything.
And, what defines a message as "local"? Why the last message of a supergroup channel is "local"?

If the unreadCount is 1 in TDLib, then there is 1 unread message in the chat. You can verify that by calling getChatHistory. Where do you see unreadCount 1 and where do you see that the message is read?

I call TdApi.GetChats for get the chat ids
Inside TdApi.Chats.CONSTRUCTOR, for each chatId I call TdApi.GetChat(chatID)
Inside TdApi.Chat.CONSTRUCTOR I get the TdApi.Chat chat object where I see that the chat type is a supergroup, and the isChannel is set to true; also the chat.unreadCount is 1 and if the chat.lastReadMessageId < chat.lastmessage.id (which is true because unreadCount is 1) I call the GetChatHistory, where i get the last message, which is the last unreaded message.

When in the other chats, like for example here, there is a message marked as unread and from the web client I read it, an event in the library is activated that tells the chat has been updated and I see the new value of unreadedCount = 0 removing the messages of the chat from my unreaded messages list.
Instead, in this chat, as in the Telegram one, from the clients the message is marked as read and even if I tried to reopen the chat (to make it look like I read the message) no event is triggered, and I don't find a way to know how to mark the message as read even if is "local" or already readed

I exit and re-enter the channel, and the value of unreadcount is now at 0, correctly. What could have been the problem? Am I to expect that could happen with other chats or channels?

If you read a message from another client, then there can be a delay before it will be marked as read on the other clients. But if both clients have reliable network connection, the delay rarely exceeds 5 seconds.

Thank you


Adding scripts to collect the data

This PR ports back some of our previous code for data generation to the main code.

Hum yeah... looks like it's the same, in that case, I would move it out of the library, these are scripts, not submodules.


loopback version updates

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

:tada: This issue has been resolved in version 7.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MouseWhell zoom or scroll

Hello,
I wish to do a zoom when pressing ctrl during mousewheel else a simple vertical scroll but i don't know how to modify the code. Can someone give me some steps please ?
I guess that i have to override onMouseWheel. Select depending if ctrl is pressed and use ProcessMouseZoom but protection is not accepted so i have a doubt. Is there any function to manage scroll too ?

Hello, and thanks for the question. I took a quick look at this, and found it reasonable easy to do by overriding OnMouseWheel. There is a caveat though - the MouseWheel event will no longer be raised unless Control is held.
You can find my implementation below - I check to see if Control is pressed and if so, use the default implementation. If it isn't pressed, I then check to see if a vertical scrollbar is present, and if so get the current AutoScrollPosition property value, offset it by the wheel delta (making sure it doesn't fall out of the boundaries of the scrollbar), and then re-apply it. Seems to work fine - you could adapt the same code to scroll the horizontal scroll, or to scroll horizontally if a vertical scrollbar isn't present.
protected override void OnMouseWheel(MouseEventArgs e)
{
  if ((Control.ModifierKeys & Keys.Control) != 0)
  {
    base.OnMouseWheel(e);
  }
  else if (this.VScroll)
  {
    Point position;
    int value;

    position = this.AutoScrollPosition;

    value = Math.Min(Math.Max(-position.Y - e.Delta, 0), this.VerticalScroll.Maximum);

    this.AutoScrollPosition = new Point(-position.X, value);
  }
}

Hope this information helps!
Regards;
Richard Moss

I will try that asap.
Thank you for your help.


examples/hello_rust: Add -O flag

Summary
The current issue with the "hello_rust_main.rs" file not building successfully is addressed by this pull request, which aims to enhance the build process by incorporating the "-O" flag into the rustc flags. This adjustment is crucial for optimizing the code at level 2, ensuring better performance and efficiency. The modifications are made in the Makefile located at apps/examples/hello_rust/Makefile
The discussion surrounding the Rust build issue can be found in the Rust-Lang issue #245, where various aspects of the problem and potential solutions are discussed. This issue highlights the importance of optimization flags in the Rust compiler and how they can impact the build process and the resulting application's performance.
The "-O" flag in rustc is used to specify the optimization level for the compiler. According to the Rust documentation, the optimization levels in rustc are loosely based on the ones that GCC has. The "-O" level, in particular, enables a broader range of optimizations compared to "-opt-level=1", aiming to provide a good balance between performance and compilation time. For more information: Rust Documentation
Incorporating the "-O" flag into the rustc flags for the "hello_rust_main.rs" file is a move to ensure that the code is optimized at a higher level, potentially leading to improved performance and efficiency. This change is expected to address the build issue by enabling more aggressive optimizations during the compilation process.
Impact
This pull request (PR) introduces a significant improvement to the build process for Rust files within the NuttX environment, ensuring successful compilation.
The impact of this PR is primarily focused on the successful build of Rust files, with no adverse effects on the NuttX kernel or the NuttX applications. This ensures that the optimization does not introduce any unintended side effects or compatibility issues within the broader NuttX ecosystem.
Testing

This fgets() code is used to test: Rust fgets() Code

extern "C" {
    pub fn printf(format: *const u8, ...) -> i32;
    pub fn puts(s: *const core::ffi::c_char) -> core::ffi::c_int;
    pub fn fgets(
        buf: *mut core::ffi::c_char,
        n: core::ffi::c_int,
        stream: *mut core::ffi::c_void
    ) -> *mut core::ffi::c_char;
    pub fn lib_get_stream(fd: core::ffi::c_int) -> *mut core::ffi::c_void;
}

printf(b"Please give your output:\n\0" as *const u8);
let stdin: *mut core::ffi::c_void = lib_get_stream(0);
let mut buf: [core::ffi::c_char; 256] = [0; 256];
if !fgets(
    &mut buf[0],
    buf.len() as i32 - 1,
    stdin
).is_null() {
    printf(b"You entered...\n\0" as *const u8);
    puts(&buf[0]);
}

Currently it fails to link with "undefined panic" Failed Build Log

rushabhvg@rushabhvg-laptop:~/nuttxspace/nuttx$ make
LD: nuttx
riscv64-unknown-elf-ld: warning: /home/rushabhvg/nuttxspace/nuttx/staging/libapps.a(hello_rust_main.rs.home.rushabhvg.nuttxspace.apps.examples.hello_rust_1.o): mis-matched ISA version 2.1 for 'i' extension, the output version is 2.0
...
riscv64-unknown-elf-ld: /home/rushabhvg/nuttxspace/nuttx/staging/libapps.a(hello_rust_main.rs.home.rushabhvg.nuttxspace.apps.examples.hello_rust_1.o): in function `no symbol':
/home/rushabhvg/nuttxspace/apps/examples/hello_rust/hello_rust_main.rs:127: undefined reference to `core::panicking::panic'
make[1]: *** [Makefile:179: nuttx] Error 1
make: *** [tools/Unix.mk:546: nuttx] Error 2\

Adding "-O" will solve the linking problem: examples\hello_rust\Makefile

RUSTFLAGS += -C panic=abort -O

We tested with QEMU:
qemu-system-riscv32 \
  -semihosting \
  -M virt,aclint=on \
  -cpu rv32 \
  -smp 8 \
  -bios none \
  -kernel nuttx \
  -nographic

The Rust build log for NuttX shows that rust apps are build successfully.

Okay, point noted down, from now onwards I will be concise and write in bullet-points.


Add global option and CLI property to suppress dumping the environment to logs

This PR adds a helm.suppressEnvironmentLogging boolean property that will suppress the environment from being dumped to the logs when the logging level is at info or higher. It also works with the command line property -PsuppressEnvironmentLogging=true.
Unit tests are included and the asciidoc documentation is updated. I hope nobody minds me introducing functional tests into the main plugin because I found them very useful when I needed to check the gradle output.
Resolves #104

Would prefer to continue the conversation in the issue.


K8s 1.29; metallb 0.13+ with CRDs

This merges into main, and then will be the basis of branch v1.29, and tag v1.29.0
Since metallb went to CRDs 2 years ago with 0.13.0 (actually .2, since .0 never officially made a release), I updated it to metallb CRDs. It was based largely on the OSS compatible code from http://github.com/kubernetes-sigs/cloud-provider-equinix-metal/ , which is licensed Apache. Not identical, though.

Something wrong with lint itself, not reporting an error but not working either. We will try to figure it out.

Now at least it is giving actual error messages. I will fix.

Excellent! All clean!
@zalmarge have a look? yes, I ran it against 1.29.1 cluster on CherryServers.
Once it is in, we can create the branch and cut a 1.29.0 release of the cloud provider.


16x

Ah TIL you chose 16x because 16x is the max speed.
I'll test it out and if no issues can release this to the store in <IP_ADDRESS>


Do not enforce descriptions as optional.

In practical cases (as observed with both Kaggle and Hugging Face), it seems descriptions are omitted (e.g., the name of the Field/RecordSet is explicit enough). This warning used to only add noise. If we want to enforce the good practice of having descriptions filled in by users, we should probably find another way.
Before
$ mlcroissant validate --jsonld https://www.kaggle.com/datasets/kaggle/meta-kaggle/croissant/download

W0327 07:26:25.947103<PHONE_NUMBER>21344 datasets.py:32] Found the following 286 warning(s) during the validation:
  -  [Metadata(Meta Kaggle) > RecordSet(CompetitionTags.csv) > Field(CompetitionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(CompetitionTags.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(CompetitionTags.csv) > Field(TagId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(CompetitionTags.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(BanTeamMergers)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(CanQualifyTiers)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(CompetitionTypeId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(DeadlineDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EnableSubmissionModelAttachments)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EnableSubmissionModelHashes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EnableTeamModels)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EnabledDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EvaluationAlgorithmAbbreviation)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EvaluationAlgorithmDescription)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EvaluationAlgorithmIsMax)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(EvaluationAlgorithmName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(FinalLeaderboardHasBeenVerified)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ForumId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(HasKernels)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(HasLeaderboard)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(HostName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(HostSegmentTitle)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(LeaderboardPercentage)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(MaxDailySubmissions)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(MaxTeamSize)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ModelSubmissionDeadlineDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(NumPrizes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(NumScoredSubmissions)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(OnlyAllowKernelSubmissions)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(OrganizationId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ProhibitNewEntrantsDeadlineDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(RewardQuantity)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(RewardType)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ScoreTruncationNumDecimals)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(Slug)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(Subtitle)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(TeamMergerDeadlineDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(TeamModelDeadlineDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(TotalCompetitors)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(TotalSubmissions)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(TotalTeams)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(UserRankMultiplier)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ValidationSetName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv) > Field(ValidationSetValue)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Competitions.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTags.csv) > Field(DatasetId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTags.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTags.csv) > Field(TagId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTags.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(AcceptedDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(DatasetId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(DatasetTaskId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(KernelId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv) > Field(SubmittedUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTaskSubmissions.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(DatasetId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(Deadline)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(Description)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(ForumId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(OwnerUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(Subtitle)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv) > Field(TotalVotes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetTasks.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(CreatorUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(DatasetId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(DatasourceVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(Description)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(LicenseName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(Slug)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(Subtitle)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(TotalCompressedBytes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(TotalUncompressedBytes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(VersionNotes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv) > Field(VersionNumber)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVersions.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVotes.csv) > Field(DatasetVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVotes.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVotes.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVotes.csv) > Field(VoteDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(DatasetVotes.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv) > Field(CreatorUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv) > Field(CurrentDatasourceVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv) > Field(Type)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Datasources.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(EpisodeId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(Index)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(InitialConfidence)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(InitialScore)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(Reward)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(State)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(SubmissionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(UpdatedConfidence)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv) > Field(UpdatedScore)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(EpisodeAgents.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv) > Field(CompetitionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv) > Field(CreateTime)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv) > Field(EndTime)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv) > Field(Type)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Episodes.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv) > Field(ForumMessageId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv) > Field(FromUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv) > Field(ToUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv) > Field(VoteDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessageVotes.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(ForumTopicId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(Medal)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(MedalAwardDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(Message)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(PostDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(PostUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv) > Field(ReplyToForumMessageId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumMessages.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(FirstForumMessageId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(ForumId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(IsSticky)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(KernelId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(LastCommentDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(LastForumMessageId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(Score)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(TotalMessages)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(TotalReplies)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv) > Field(TotalViews)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(ForumTopics.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Forums.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Forums.csv) > Field(ParentForumId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Forums.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Forums.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelLanguages.csv) > Field(DisplayName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelLanguages.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelLanguages.csv) > Field(IsNotebook)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelLanguages.csv) > Field(Name)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelLanguages.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelTags.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelTags.csv) > Field(KernelId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelTags.csv) > Field(TagId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelTags.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionCompetitionSources.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionCompetitionSources.csv) > Field(KernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionCompetitionSources.csv) > Field(SourceCompetitionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionCompetitionSources.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionDatasetSources.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionDatasetSources.csv) > Field(KernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionDatasetSources.csv) > Field(SourceDatasetVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionDatasetSources.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionKernelSources.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionKernelSources.csv) > Field(KernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionKernelSources.csv) > Field(SourceKernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersionKernelSources.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(AuthorUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(EvaluationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(IsChange)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesChangedFromFork)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesChangedFromPrevious)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesDeletedFromFork)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesInsertedFromFork)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesInsertedFromPrevious)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesUnchangedFromFork)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(LinesUnchangedFromPrevious)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(ParentScriptVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(ScriptId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(ScriptLanguageId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(Title)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(TotalLines)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(TotalVotes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv) > Field(VersionNumber)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVersions.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVotes.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVotes.csv) > Field(KernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVotes.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVotes.csv) > Field(VoteDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(KernelVotes.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(AuthorUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(CurrentKernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(CurrentUrlSlug)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(EvaluationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(FirstKernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(ForkParentKernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(ForumTopicId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(IsProjectLanguageTemplate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(MadePublicDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(Medal)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(MedalAwardDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(TotalComments)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(TotalViews)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv) > Field(TotalVotes)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Kernels.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv) > Field(Description)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv) > Field(Name)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv) > Field(Slug)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Organizations.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(IsAfterDeadline)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(PrivateScoreFullPrecision)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(PrivateScoreLeaderboardDisplay)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(PublicScoreFullPrecision)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(PublicScoreLeaderboardDisplay)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(ScoreDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(SourceKernelVersionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(SubmissionDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(SubmittedUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv) > Field(TeamId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Submissions.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(CompetitionCount)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(DatasetCount)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(Description)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(FullPath)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(KernelCount)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(Name)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(ParentTagId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv) > Field(Slug)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Tags.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(TeamMemberships.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(TeamMemberships.csv) > Field(RequestDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(TeamMemberships.csv) > Field(TeamId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(TeamMemberships.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(TeamMemberships.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(CompetitionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(IsBenchmark)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(LastSubmissionDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(Medal)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(MedalAwardDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(PrivateLeaderboardRank)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(PrivateLeaderboardSubmissionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(PublicLeaderboardRank)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(PublicLeaderboardSubmissionId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(ScoreFirstSubmittedDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(TeamLeaderId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(TeamName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv) > Field(WriteUpForumTopicId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Teams.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(AchievementType)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(CurrentRanking)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(HighestRanking)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(Points)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(Tier)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(TierAchievementDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(TotalBronze)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(TotalGold)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(TotalSilver)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserAchievements.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserFollowers.csv) > Field(CreationDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserFollowers.csv) > Field(FollowingUserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserFollowers.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserFollowers.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserFollowers.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserOrganizations.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserOrganizations.csv) > Field(JoinDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserOrganizations.csv) > Field(OrganizationId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserOrganizations.csv) > Field(UserId)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(UserOrganizations.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv) > Field(DisplayName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv) > Field(Id)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv) > Field(PerformanceTier)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv) > Field(RegisterDate)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv) > Field(UserName)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle) > RecordSet(Users.csv)] Property "https://schema.org/description" is recommended, but does not exist.
  -  [Metadata(Meta Kaggle)] Property "https://schema.org/version" is recommended, but does not exist.
I0327 07:26:25.947509<PHONE_NUMBER>21344 validate.py:53] Done.

After
$ mlcroissant validate --jsonld https://www.kaggle.com/datasets/kaggle/meta-kaggle/croissant/download

W0327 07:25:00.950064<PHONE_NUMBER>88384 datasets.py:32] Found the following 1 warning(s) during the validation:
  -  [Metadata(Meta Kaggle)] Property "https://schema.org/version" is recommended, but does not exist.
I0327 07:25:00.950336<PHONE_NUMBER>88384 validate.py:53] Done.

Oh, nice. BTW, this issue I made long ago is somewhat related, though maybe now obsolete? https://github.com/mlcommons/croissant/issues/246

@goeffthomas Thanks for making the connection. If you confirm that descriptions did account for the largest part of the noise, we can indeed close the issue.

Thanks for making the connection. If you confirm that descriptions did account for the largest part of the noise, we can indeed close the issue.

@marcenacp Done :)


Fix builtin nodes

Current coverage is 96.67% (diff: 97.56%)

Merging #773 into master will increase coverage by 0.01%

@@             master       #773   diff @@
==========================================
  Files           144        144
  Lines          5340       5361    +21
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5162       5183    +21
  Misses          178        178
  Partials          0          0

Powered by Codecov. Last update cf2aa30...ee38994


Implement Regexp#match and MatchData#[] APIs

Enable detecting matches and capturing groups.
The tests from the docs for MatchData#[] pass.
Also add:

Regexp#to_s and Regexp#inspect
MatchData#string
MatchData#regexp

This PR is in support of GH-85.


HIVE-28098: Fails to copy empty column statistics of materialized CTE

What changes were proposed in this pull request?
Makes the stats population more defensive.
https://issues.apache.org/jira/browse/HIVE-28098
Why are the changes needed?
The current implementation fails when column stats are missing.
Does this PR introduce any user-facing change?
No, it doesn't.
Is the change a dependency upgrade?
No.
How was this patch tested?
I added various test cases to cte_mat_11.q.

@kasakrisz I found the cases where HIVE-28080 doesn't work well in some complex patterns. Could you take a look when you have a chance?


Unable to render Bool value

I don't its a bug from griddle side or react but I am unable to render bool value (false) got from webapi.
Change : coldata = coldata.toString() in gridRow.jsx.js render function
after this seems to working for me

I have the same problem, too.

@amitsharma2705 coldata?

All -- I realize this issue is from some time ago but we recently have released Griddle 1.0 and are trying to make sure we are a bit better about responding to issues.
The following is for Griddle 1.0:
I would recommend creating a component as follows:
const boolData = ({value}) => <span>{ value.toString() }</span>;

and passing this in as a custom component on the column that contains boolean data.
<Griddle data={localData} plugins={[LocalPlugin]}>
  <RowDefinition>
    <ColumnDefinition id="name" customComponent={boolData} />
    <ColumnDefinition id="location.state" nested={true}/>
  </RowDefinition>
</Griddle>

Closing this one for now but please feel free to create a new issue if any problems are encountered. 👍