Bounds ?

Hi,
is it possible to open the modal not entirely fullscreen
~Marc ?

Will be interesting make the modal inside an element, too.
For example: make the modal fill the entire body, but not the header

In the Plugin js file, change the value of width from 100% to your desired size and position it with top, left property. :)

Thanks for that Fahim, very helpful!
Is there a way to have modals of different sizes? By editing the JS file directly, I now have the modal in the dimensions I want. But for some types of secondary content, I want something that's smaller, more like a tooltip. I don't want that showing at the same size as my "primary" modals.
Any help would be appreciated!


[bug] Filter options

Hey, when using the /pcd filter, there seems to be a bug happening with the global removal box.
To reproduce:

tick global to display all cooldowns
untick global to remove all cooldowns
tick a single cooldown
result: all cooldowns of the selected profession from step 3 will be displayed

https://imgur.com/a/HQXra8M

Hi,
Yes, I realized I broke some filter functionality when I made the cataclysm version.
I will try to have a fix one of the coming days, if not tonight.


[Bug] Use javaAPI to directly obtain the error result

Search before asking

[X] I searched in the issues and found nothing similar.

Paimon version
0.8.1
Compute Engine
Flink 1.17.2 and JavaAPI
Minimal reproduce step

use flink sql-client to create and insert table:

CREATE CATALOG paimon_minio WITH (
    'type' = 'paimon',
    'warehouse' = 'file:///mnt/datadisk1/wuwenchi/tmp/warehouse'
);

CREATE TABLE `paimon_minio`.`db1`.`tb1` (
  `s` string,
  `ts1` TIMESTAMP(6),
  `ts2` TIMESTAMP(6) WITH LOCAL TIME ZONE
) WITH (
  'write-only' = 'true',
  'file.format' = 'parquet'
  );

insert into `paimon_minio`.`db1`.`tb1` values ('flink:2024-01-02 10:04:05.123456789',timestamp '2024-01-02 10:04:05.123456789',timestamp '2024-01-02 10:04:05.123456789');

then use JavaAPI according to https://paimon.apache.org/docs/0.8/program-api/java-api/#batch-read

    public void read() throws TableNotExistException, IOException {
        Map<String, String> props = new HashMap<>();
        props.put("warehouse", "file:///mnt/datadisk1/wuwenchi/tmp/warehouse");

        CatalogContext ctx = CatalogContext.create(new Options(props));
        Catalog catalog = CatalogFactory.createCatalog(ctx);
        Table table = catalog.getTable(Identifier.create("db1", "tb1"));

        ReadBuilder rb = table.newReadBuilder();
        List<Split> splits1 = rb.newScan().plan().splits();
        TableRead read = rb.newRead();
        RecordReader<InternalRow> reader = read.createReader(splits1);
        reader.forEachRemaining(record -> {
            System.out.println(record.getString(0));

            Timestamp ts1 = record.getTimestamp(1, 6);
            System.out.println(ts1);

            Timestamp ts2 = record.getTimestamp(2, 6);
            System.out.println(ts2);
        });
    }

print in console:
flink:2024-01-02 10:04:05.123456789
2024-01-02T10:04:05.123456
2024-01-02T02:04:05.123456

It is right for s and ts1, but it is wrong for ts2, we expect 2024-01-02T10:04:05.123456 for ts2.
Is this 8 hours missing a time zone?
What doesn't meet your expectations?
Use JavaAPI to directly obtain the correct result.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Hi @wuwenchi , if the type is timestamp with local zone, you should use a zone id to convert it to string.
For example:
LocalDateTime.ofInstant(timestamp.toInstant(), ZoneId.systemDefault()).toString().


Playground: JavaScript Error Triggers on Import Declarations Regardless of Placement at Top Level

Attempting to run code with imports yields a JavaScript syntax error in the logs, preempting and preventing execution as a result.

Repro:
Attempting to run the Function Chaining example will yield the same error (using Firefox 90.0.1 64-bit).

Expected behavior:
JavaScript syntax error should only trigger if an import function exists outside of allowed area (top level of module).
Actual behavior:
JavaScript syntax error acts as if its import functions are not at the top of the code space.

The playground only gets the types for imports, and doesn't handle the bundling of libraries for web - so you cannot run the javascript. For these cases I recommend using the export to code sandbox or stackblitz feature too get  full sandbox


Update SpawnPointSystem.cs

About the PR
It would be more logical to start by trying to throw the player at a late join point and not throw him anywhere. For the most part, this is necessary in case of adding new professions, but not having the desire to add a marker for a new profession to each card.

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: Fixed spawn when no find spawner!

This is a web edit. Test your changes locally and then make a new PR.

Это веб-редактирование. Протестируйте свои изменения локально, а затем создайте новый PR.

I tested it locally, it's just more convenient for me to open the PR in the web version.

github sends a link to make a pr when you push and theres a big green button on the repo, its pretty easy


add github workflow for automated docker build

Hi,
This sets up automated multiarch build (based on this article)
You will need to create a docker hub access token and create the corresponding github repository secrets: DOCKER_USERNAME and DOCKER_PASSWORD
Cheers,
Pierre

Amazing, sorry I just saw this.  I will review and approve when I have some time in the evening.  Nice work!


Feature request: Add draft-04 schema support

Hi! I am trying to use action to verify the API doc file which follows the OpenAPI 3.0.1 schema (Schema reference).
      - name: Verify api-doc.json
        uses<EMAIL_ADDRESS>        with:
          mode: "fail"
          comment: "true"
          files: "api-doc.json"
          json_schema: "./schemas/open-api-3_0.json"
          json_schema_version: "draft-04"

But it gives an error:
Warning: json_schema_version 'draft-04' is not supported. Defaulting to 'draft-07'

/home/runner/work/_actions/GrantBirki/json-yaml-validate/v3.0.0/node_modules/ajv/dist/core.js:147
                throw new Error(`no schema with key or ref "${schemaKeyRef}"`);

So it looks like OpenAPI 3.0.1 use draft-04 json schema which is supported by Ajv according to the documentation but not supported by the json-yaml-validate. I have tried to use other schemas in the json_schema_version like draft-07 but it doesn't work. It would be great and very appreciable to add support for draft-04 for the json_schema_version parameter.

This does appear to be possible and something I can work on in the future: https://github.com/ajv-validator/ajv-draft-04

@kirpichyov I have published a pre-release -> v3.2.0. Would you be able to try this out and see if it works for your use case and let me know how it goes? Thanks! 🙇

It works now, thanks!


Start file system at fixed position in Flash

Hi,
I am using flashless MCU with QSPI external flash, program is running in XIP mode, the flash I am using is 512 MBytes from Gigadevice GD25S512MD, main software is located at the beginning of the flash, How to tell LittleFS to start file system at fixed address in Flash ?
My software is located @ address 0 mapped to 0x60000000
I would like LittleFs starting @address 0x20000 for exemple.
Thanks

Hi @safirxps, littlefs takes a block device and uses the full range of addresses. But you control this block device, so if you wanted to you can map the addresses littlefs is using to any address on the underlying storage.
Here's a quick example of how you could map the addresses to omit 0-0x20000:
#define READ_SIZE 1
#define PROG_SIZE 1
#define ERASE_SIZE 4096
#define APP_SIZE 20*ERASE_SIZE
#define FLASH_SIZE 512*ERASE_SIZE

int bd_read(const struct lfs_config *c, lfs_block_t block,
        lfs_off_t off, void *buffer, lfs_size_t size) {
    // calculate new block address
    return real_bd_read(c, block - (APP_SIZE/ERASE_SIZE), off, size);
}

struct lfs_config cfg = {
    .read_size = READ_SIZE,
    .prog_size = PROG_SIZE,
    .block_size = ERASE_SIZE,
    .block_count = (FLASH_SIZE - APP_SIZE) / ERASE_SIZE, // omit first 20 blocks from size
    .read = bd_read,
    .prog = bd_prog,
    .erase = bd_erase,
};

Note you need to make sure the offset is aligned to the block size (erase size) or else bad things will happen!

HI Geky,
Many thanks I will try, by the way I am little confused with the sector size, block size etc for this flash http://www.elm-tech.com/en/products/spi-flash-memory/gd25s512m/gd25s512m.pdf page 9 any further help will be very appreciated.
Rgds
David

Hi Geky,
Thanks for your answer, I will try. By the way I am little confused with this flash http://www.elm-tech.com/en/products/spi-flash-memory/gd25s512m/gd25s512m.pdf page 9 could you help me to configure in LittleFS the config block for sector, block etc.; ?
Rgds
David

Yeah, the names storage devices use for different block sizes is a mess.
Looking at that datasheet, the GD25S512M can do byte-level read and writes, and can erase 4KiB sectors. So something like this should work:
read_size = 1
prog_size = 1
cache_size = anything from 1 to 4096, larger values use more RAM but may be faster
block_size = 4096

As for the other sizes in the datasheet:
The page size is how many bytes can be programmed at once. You should take special care to send multiple program operations for any programs > page size (littlefs guarantees alignment, but may send larger buffers).
The difference in sector size vs block size is the amount of bytes erased in a single command. Block erases can get you faster erase throughput, but littlefs doesn't take advantage of this so it's probably not worth implementing.

There's an open source implementation of a SPI driver in Mbed OS, it may be useful as a reference:
https://github.com/ARMmbed/mbed-os/blob/master/components/storage/blockdevice/COMPONENT_SPIF/SPIFBlockDevice.cpp#L285

Hi geky
I am experiencing one problem using LittleFs is there any forum somewhere or it is possible to  ask in this issues board ?
Thanks

Creating an issue is the best place right now.
I'm considering creating a gitter for littlefs, but it doesn't exist yet.

Hi Geky,
On the first question of this post your answered : return real_bd_read(c, block - (APP_SIZE/ERASE_SIZE), off, size);
Are you sure it is block minus (APP_SIZE/ERASE_SIZE) ?
thanks

Oh! My bad. You are right, I believe that should be block + (APP_SIZE/ERASE_SIZE).


Hello author, could you provide the trained weights? Thank you very much!

Hello author, can I infer the result using data with only low images and no high images

Hello,May I ask which journal your paper has been submitted to?


[COLRv1] Add tests for coincident stops and angles

Adjust PaintSweepGradient implementation to not reverse color stops when not needed. Matches FireFox behavior. See Skia change under review for implementing the same change [1].
[1] https://skia-review.googlesource.com/c/skia/+/790456

Thanks for the quick review.


Archive analyzer throws exception while reading archive

Recently We have been facing issues while performing scan for some of our images. The error looks something like below
[INFO] Analysis Started
[ERROR] Exception reading archive '.wh.nginx-1.18.0-2.el7.ngx.x86_64.rpm'.
[WARN] An error occurred while analyzing '<workspace_directory>/<image_path>/layer.tar' (Archive Analyzer).

We are aware of this change that took effect with v8.0.2.
We are suspecting that the issue is the dependency check is unable to read a zipfile in the tarfile.
Can something be done to resolve this issue?
Not sure but eventually on passing '--zipExtensions "rpm" ' to our scan command , it does not throws this exception. I am not able to co relate this. please help me to understand it.
Similarly for .tar.gz file extension.
[INFO] Analysis Started
[ERROR] Exception reading archive '.wh.jdk-19_linux-x64_bin.tar.gz'.
[WARN] An error occurred while analyzing '<workspace_directory>/<image_path>/layer.tar' (Archive Analyzer).

P.S. We are currently using v8.1.2

Can anyone please provide any comments ?

Pretty sure you have it figured out - something cannot be correctly extracted from layer.tar. You might get more details with the --log odc.log option.

@jeremylong shouldn't this be considered as a bug since the archive analyzer is unable to extract files properly ?

Can anyone look into this issue ?

We use apache compress - if you look at their jira there are a few issues with decompressing some archives. One example is COMPRESS-562 and COMPRESS-513. I don't have your archive file so I can't open a defect with their project.
In the meantime you could configure the failOnError option.

@jeremylong how can we use failOnError option on the CLI when passing in parameters ?

Sorry - the failOnError is a configuration on the Maven or Gradle plugins. If this is on the CLI, the report should still be generated. As such, you can either ignore the error. Or alternatively, you could un-tar the file before running ODC.

@jeremylong we are getting error for extraction this time.
[ERROR] Exception extracting archive 'testtar.tar'
...
[ERROR] java.io.IOException: Truncated TAR archive

we tried to exclude that using --exclude **/*testtar.tar (with and without quotes both tried) but still its getting picked up and reporting same error. This is somewhat painful. We're unable to exclude stuff .
Please provide some solution here.
Thanks

I am also facing the similar issue,
I tried adding tar, zip, tgz extensions like below as argument and all of the scans finished with zero scans/findings.
'--zipExtensions "rpm","gz","zip","tgz","tar" '
Please suggest a way to get rid of this issue.

From the documentation:

Argument Name
Parameter
Description

--zipExtensions
<strings>
A comma-separated list of additional file extensions to be treated like a ZIP file, the contents will be extracted and analyzed.

So I might suggested:
--zipExtensions "rpm,gz,zip,tgz,tar"

regarding the exclude --exclude **/testtar.tar should work - unless the tar is actually contained within another archive.

Hi @jeremylong ,
I have tried the solution below suggested but still the scan results are coming blank but I am expecting some results out of this scan because if I remove tgz,zip,tar from --zipExtensions it is producing some scan results and scan fails in between with tar extraction/reading exception.

From the documentation:
Argument Name	Parameter	Description
--zipExtensions		A comma-separated list of additional file extensions to be treated like a ZIP file, the contents will be extracted and analyzed.
So I might suggested:
--zipExtensions "rpm,gz,zip,tgz,tar"

Please find the logs from my scan
18:58:53  2023-05-03 13:28:39,544 - INFO - Running scan with: /tmp/dependency-check/bin/dependency-check.sh --propertyfile /owasp-client/owasp-configuration.properties --log /owasp-client/workspace --noupdate --disableCentral --disableOssIndex --disableYarnAudit --out /owasp-client/workspace/reports --exclude **/*zookeeper-3.4.13* --exclude **/*zookeeper-3.4.14* --zipExtensions "rpm,gz,tgz,zip,tar" --disableNodeAudit --disableNodeJS --suppression /owasp-client/suppress.xml  --suppression /customizations/owasp-scan/suppress.xml --format "ALL" --prettyPrint --scan /owasp-client/workspace/data/ocir --project test
18:59:25  [INFO]
18:59:25
18:59:25  Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.
18:59:25
18:59:25
18:59:25     About ODC: https://jeremylong.github.io/DependencyCheck/general/internals.html
18:59:25     False Positives: https://jeremylong.github.io/DependencyCheck/general/suppression.html
18:59:25
18:59:25  💖 Sponsor: https://github.com/sponsors/jeremylong
18:59:25
18:59:25
18:59:25  [INFO] Analysis Started
18:59:25  [INFO] Finished Archive Analyzer (0 seconds)
18:59:25  [INFO] Finished File Name Analyzer (0 seconds)
18:59:25  [INFO] Finished Dependency Merging Analyzer (0 seconds)
18:59:25  [INFO] Finished Version Filter Analyzer (0 seconds)
18:59:25  [INFO] Finished Hint Analyzer (0 seconds)
18:59:25  [INFO] Created CPE Index (2 seconds)
18:59:25  [INFO] Finished CPE Analyzer (2 seconds)
18:59:25  [INFO] Finished False Positive Analyzer (0 seconds)
18:59:25  [INFO] Finished NVD CVE Analyzer (0 seconds)
18:59:25  [INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
18:59:25  [INFO] Finished Known Exploited Vulnerability Analyzer (0 seconds)
18:59:25  [INFO] Finished Unused Suppression Rule Analyzer (0 seconds)
18:59:25  [INFO] Analysis Complete (2 seconds)
18:59:25  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-report.xml
18:59:25  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-report.html
18:59:25  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-report.json
18:59:25  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-report.csv
18:59:25  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-report.sarif
18:59:26  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-jenkins.html
18:59:26  [INFO] Writing report to: /owasp-client/workspace/reports/dependency-check-junit.xml
18:59:28  2023-05-03 13:29:28,001 - INFO - The scan completed
18:59:28  2023-05-03 13:29:28,001 - INFO - Goodbye

regarding the exclude --exclude **/testtar.tar should work - unless the tar is actually contained within another archive.

Yes this tar is an archive inside another archive. Is there any way to exclude this file from being scanned ?

In regards to
So I might suggested:
--zipExtensions "rpm,gz,zip,tgz,tar"

Would that be a redundant of the default values - https://jeremylong.github.io/DependencyCheck/analyzers/archive-analyzer.html?
OWASP dependency-check includes an analyzer an archive analyzer that will attempt to extract files from the archive that are supported by the other file type analyzers.

Files Types Scanned: ZIP, EAR, WAR, JAR, SAR, APK, NUPKG, TAR, GZ, TGZ, RPM

Additional file extensions for ZIP archives can be added, see the configuration section in the Maven, Ant, or CLI interfaces for more information on configuration.

@himanshukumar4642 - at the moment, no, there is no way to exclude an archive contained in another archive.

@jeremylong when can we expect any fix for this issue ?
The issues which you pointed above with the compressor seems to be created way long back and still in OPEN state.
Please provide any suggestion .
Thanks

@jeremylong can you provide any ETA for the fix ? We are really facing serious issues.
Thanks


QtWebKit needs to be deprecated

QtWebKit was deprecated in Qt 5.6. We are now using an outdated unofficial port:
https://github.com/NixOS/nixpkgs/blob/b0705bcbcebfea359643112fd200b549035d9503/pkgs/development/libraries/qt-5/5.12/default.nix#L40-L49
In some cases, applications already provide support for using QtWebEngine instead, we just need to enable it. The advantage of using QtWebEngine is that it is supported by the Qt upstream.
This issue is to track progress (or lack thereof) in deprecation of QtWebKit.
Overview
Legend: ✔ - dependency can be removed, ✘ - no straightforward solution was found, ? - dependency can be removed at a cost

[x] apitrace - ✔ judging by upstream git master it doesn't need qtwebkit
[ ] apmplanner2
[x] bibletime - #125162
[ ] blink - python
[ ] cadence - python
[x] calibre - #79608 #92118
[ ] calligra - #102490 ? ["QWebPage needed for webpage plugin"] (https://github.com/KDE/calligra/blob/2c601b660e8845ca3ffeeb1509db386bfcddec70/CMakeLists.txt#L1023)
[ ] capybara-webkit - ruby
[ ] cb2bib - ✔ https://www.molspaces.com/cb2bib/doc/overview/ Requirements: "QtWebKit or QtWebEngine library (optional) to compile cb2Bib Annote viewer"
[ ] copyq - ? https://github.com/hluk/CopyQ/issues/540 . Also in readme it says following about the dependencies: "Optionally QtWebKit (more advanced HTML rendering)"
[ ] brewtarget - ✔ qtwebkit is not in the list of the dependencies
[x] digikam - #53083
[x] freecad - #98845
[x] frescobaldi - #76889
[x] ghostwriter - 6b73aa91e0438f5d84c1d4d1ff1e648b9f554d29
[ ] google-musicmanager - ✘ see comment below
[x] golden-cheetah - #76172
[ ] goldendict - ✘ https://github.com/goldendict/goldendict/issues/677
kde

[ ] alkimia - #201953
[x] k3b - #103164
[x] kdenlive - 2ff2ef1a52acb7264f014e6f77bfe2c4776a78e4
[x] kdevelop5 - ✔ both QtWebKit and QtWebEngine are supported https://github.com/KDE/kdevelop/blob/5e17ba4cd7a50816825a279c70a6b1c64a701926/kdevplatform/documentation/CMakeLists.txt#L3-L16
[ ] kdewebkit - #201953
[ ] kmymoney - #201953
[ ] kreport - #102490 https://phabricator.kde.org/T3565
[ ] konqueror - #102490
[x] marble - #94826
[x] messagelib - c2366ae35036be6e1b26ec36ad6c9cf4d346ed27
[ ] rocs - #102490

[ ] kexi - ✘ upstream task https://phabricator.kde.org/T10389
[x] ksysguard, libksysguard - 505f0c2232b9b09b259e2c3279fd3c0d5a67cbfb
[ ] lsd2dsl
[ ] mendeley - ✔ our current expression depends on both qtwebkit and qtwebengine, AUR manages with qtwebengine only https://aur.archlinux.org/packages/mendeleydesktop/
[x] merkaartor -  #135925
[ ] mindforger - #122476
[ ] minizincide - expression we have depends on both qtwebengine and qtwebkit
[x] musescore - #52835
[ ] mythtv - ✘ https://github.com/MythTV/mythtv/blob/master/mythtv/configure#L6526
[x] nextcloud-client - #75202
[ ] nixnote2 - ✔ should be already using QtWebEngine https://github.com/notepadqq/notepadqq/projects/1
[x] nmapsi4 - #59266
[x] notepadqq - ✔ should be using qtwebengine already https://github.com/notepadqq/notepadqq/blob/master/README.md#build-it-yourself
[ ] oilrush
[ ] openshot-qt - ✔ OpenShot/openshot-qt#3604
[x] owncloud-client - #75206
[x] p4v - #110168
[ ] phantomjs2 - ✘ https://github.com/ariya/phantomjs/issues/14366
[x] psi-plus - 8f5bafe599fff1917130d2fa8cc7080bfc44ed2e
[x] rstudio - #59512
[ ] shotcut - ✘ https://forum.shotcut.org/t/is-that-any-plan-for-porting-from-qt-webkit-to-qt-webengine/5816
[ ] scudcloud - ✘ python, abandonware https://github.com/raelgc/scudcloud/issues/628
[ ] sigil - ✘ no port to QtWebEngine so far
[x] skrooge - #55930
[ ] sleepyhead - ✔ very light use of QWebView can be fixed to use QtWebEngine with some simple patches from https://gitlab.com/sleepyhead/sleepyhead-code/merge_requests/21
[ ] smtube - ✘ no traces of QtWebEngine support in svn trunk
[ ] subsurface - ?  "QtWebKit is needed, if you want to print"
[x] supercollider - #63812
[ ] swift-im - ✘ dependency on QtWebKit is mentioned in https://github.com/swift/swift/blob/master/README.md and https://wiki.xmpp.org/web/Summer_of_Code_2017#Design_a_Chat_View_Free_of_QtWebKit.2FQtWebEngine
[ ] teamviewer - ✘ checked version 15.0.8397: still links to libQt5WebKitWidgets.so.5 libQt5WebKit.so.5
[x] toggldesktop - #54587
[ ] trojita - ✘ https://bugs.kde.org/show_bug.cgi?id=365299
[ ] qlandkartegt - ✔
[ ] qmc2 - ✘ no traces of QtWebEngine support in SVN trunk
[x] qsyncthingtray - supports qtwebkit optionally
[ ] qtwebkit-plugins
[ ] quiterss - ? migrate to https://github.com/QuiteRSS/quiterss2 ?
[ ] wkhtmltopdf - ✘ https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3391, needs to be ported to qt5 though
[x] yacas - https://github.com/NixOS/nixpkgs/pull/147826
[x] zeal - ✔ https://github.com/zealdocs/zeal/pull/1125

How to help?

Take an open item from the list that doesn't have a comment, google "<itemname> qtwebengine" and "<itemname> qtwebkit". Report what you find (or add a comment if you can edit the post).
Take an open item from the list that does have a comment and ping a maintainer if the fix is possible. Alternatively try fixing it yourself.

I don't think we'll be able to kill the dependency easily in google-musicmanager, since we're already on Google's latest release, which lists this as an explicit dependency:
$ curl http://dl.google.com/linux/musicmanager/deb/dists/stable/main/binary-amd64/Packages
Package: google-musicmanager-beta
Version: 1.0.467.4929-r0
Architecture: amd64
Maintainer: Google Music Team<EMAIL_ADDRESS>Installed-Size: 16766
Pre-Depends: dpkg (>= 1.14.0)
Depends: libc6 (>= 2.16), libexpat1 (>= 2.0.1), libflac8 (>= 1.3.0), libgcc1 (>= 1:4.1.1), libidn11 (>= 1.13), libqt5core5a (>= 5.2.0), libqt5gui5 (>= 5.0.2) | libqt5gui5-gles (>= 5.0.2), libqt5network5 (>= 5.0.2), libqt5webkit5, libqt5widgets5 (>= 5.2.0), libstdc++6 (>= 4.6), libvorbisfile3 (>= 1.1.2), xdg-utils (>= 1.0.2)

We are now using an outdated unofficial port

Not unofficial – endorsed by Qt: https://code.qt.io/cgit/qt/qtwebkit.git/ And currently in the process of a massive overhaul thanks to Patreon funding.

@KAMiKAZOW This is definitely a good news for qtwebkit and its users. However, we are using a specific 5.212-alpha version that is outdated and contains known CVE's. Looking at the repo at your link, it doesn't seem to contain any significant update to address those issues. I doubt anyone would endorse this software in its current state.

Looking at the repo at your link, it doesn't seem to contain any significant update to address those issues.

The development happens here on Github. "My" link was solely a reference proving that it's not unofficial but instead adopted by upstream Qt.
As you can read under https://github.com/qtwebkit/qtwebkit/blob/qtwebkit-dev/ReadMe.md#this-repository-development the qtwebkit-dev branch is the update to current WebKit master.

zeal ported to qtwebengine (https://github.com/zealdocs/zeal/pull/1125), not released yet.

Freecad will be ported with the 0.19 release https://github.com/FreeCAD/FreeCAD/commit/75fd7231e05be6a7fcd76cd2c00f9eda0bef2f28, not released yet

messagelib no longer depends on qtwebengine since https://github.com/NixOS/nixpkgs/commit/c2366ae35036be6e1b26ec36ad6c9cf4d346ed27

freecad no longer depends on qtwebkit since we switched to the 0.19 prerelease in #98845/#100972.

The issue for OpenShot linked in the description is outdated; it's been superseded by https://github.com/OpenShot/openshot-qt/pull/3604.

no straightforward solution was found

example: https://github.com/scrapinghub/splash/issues/349
splash is not in nixpkgs. its needed for the legacy project portia (a GUI for scrapy)

p4v doesn't depend on qtwebkit since #110168.

apitrace is done: #201032

teamviewer builds and runs fine without qtwebkit in version 15.29.4
I cannot test the connectivity, though, since I don't have a teamviewer partner to test it with

@das-g How are you going with fixing the kmymoney build?  I'm hitting build errors in my attempts to build against qtwebengine.

@aidalgol working on it, should be ready in some minutes.

@aidalgol PR to switch kmymoney from qtwebkit to qtwebengine: https://github.com/NixOS/nixpkgs/pull/201953

qgis depends on it and isn't in the main list.
Looks like it can build with QtWebEngine but won't work due to some bugs, see https://github.com/qgis/QGIS/commit/7c1d6165f127f682399f694d2a37377525eaba5d

yacas does not rely on QtWebKit, since PR #147826 got merged.
I think we can tick its box :ballot_box_with_check:

QLandkarte GT hasn't seen any updates since 2015 and can therefore probably be considered unmaintained/abandoned:
https://sourceforge.net/projects/qlandkartegt/
On the AUR (patches fetched from there) it has been unmaintained as well:
https://aur.archlinux.org/packages/qlandkartegt
I'd suggest changing the ✔ to a ✘ for its entry.

copyq does not rely on QtWebKit, since PR https://github.com/NixOS/nixpkgs/pull/130670 got merged.
I think we can tick its box :ballot_box_with_check:

Issue for a port from QtWebKit to QtWebEngine for kexi and kreport are still open:
pkgs/development/libraries/kreport/

Qtwebkit has been marked insecure since #201028. No point in trying to check every single box.

Fantastic :sweat_smile:
Thanks for the notice!


backup: use S3 path instead of internal scheme

ref: https://github.com/coreos/etcd-operator/issues/1763

Ready to review.

LGTM


Why ❔
To improve performance numbers.

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.

@0xVolosnikov PTAL.


[SYSTEMML-545] Document Scala build support in Eclipse

Added document with screen captures to help developers prepare their Eclipse development environment to handle Scala in the SystemML code base.  Note developers can choose to skip the Scala components such that the JDT will continue to be used when working inside Eclipse.  Specific Eclipse and Scala plugin versions are also recommended.  See https://github.com/apache/incubator-systemml/pull/70 for detailed discussion including additional documentation plus the actual updated pom.xml which enables building Scala.

@gweidner Great share.  LGTM

@Wenpei Thank you!  You really did all the heavy lifting in updating the pom.xml for Scala plus your new Scala code looks good.  Thanks again for all your work.

@gweidner, @Wenpei  Great, thanks for getting the Eclipse integration worked out in prep for the Scala addition!

Merged.  Thanks @gweidner!


Checking in source code instead of tar file

Hi, thank you so much for sharing this great software freely with the community. I was wondering if your development team would be willing to check in the matlab files themselves instead of a tar file? Version control would make more sense on that level and it would also enable commands like git grep. I would be happy to make a pull request making that change as well. Although it might make more sense to rename the repository if you make that change. Note that github can create tar files for you for tagged releases

Alex
We would prefer to keep things simple at this stage.
The software package is divided into multiple directories and has over 600 component (m-)files.
A single download is surely the best way for users to install the software.
---David

From: Alex Lindsay @.***>
Sent: 24 April 2024 16:52
To: mcbssds/IFISS_download
Cc: Subscribed
Subject: [mcbssds/IFISS_download] Checking in source code instead of tar file (Issue #1)
Hi, thank you so much for sharing this great software freely with the community. I was wondering if your development team would be willing to check in the matlab files themselves instead of a tar file? Version control would make more sense on that level and it would also enable commands like git grep. I would be happy to make a pull request making that change as well. Although it might make more sense to rename the repository if we make that change. Note that github can create tar files for you for tagged releases
—
Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/mcbssds/IFISS_download/issues/1__;!!PDiH4ENfjr2_Jw!FCigrqQGk9q8nRyHw0OFhzW-UnCmgmX6LUVXmwj3NLY3qJw6HrGLb12i_9dLUdjT5mJ3EWcQAGEo4jjRSjpyCROSxnWWn6Uf$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AYZSJCABWMTK4O54ULRXO33Y67INLAVCNFSM6AAAAABGXGHJQ6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3DCNRTGEZTAMQ__;!!PDiH4ENfjr2_Jw!FCigrqQGk9q8nRyHw0OFhzW-UnCmgmX6LUVXmwj3NLY3qJw6HrGLb12i_9dLUdjT5mJ3EWcQAGEo4jjRSjpyCROSxgzVeCfc$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

A user can choose to download a single zipped file if they want. See screenshot below. Git is designed for tracking changes to large numbers of files. The software package I lead has 40,839 files currently checked in with more added every day.

Whether you check-in the 600 files with git and do git clone, or clone the tar file and then untar, the result is the same in terms of final file count for the user isn't it? But in the former, it's only one step

As I said, I very much appreciate you guys sharing your code, so I will be happy even if you don't change anything. It was just a suggestion

No problem. We will leave the setup as it is for now ... and monitor the download activity.
---David

From: Alex Lindsay @.***>
Sent: 29 April 2024 21:51
To: mcbssds/IFISS_download
Cc: David Silvester; Comment
Subject: Re: [mcbssds/IFISS_download] Checking in source code instead of tar file (Issue #1)
As I said, I very much appreciate you guys sharing your code, so I will be happy even if you don't change anything. It was just a suggestion
—
Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/mcbssds/IFISS_download/issues/1*issuecomment-2083640908__;Iw!!PDiH4ENfjr2_Jw!A17ca1tE_nhqhFpsIFuyZBNLHRCzoR7-16rH2WlA0omF38LOg0lW9nNJnoP4OetcXv5K3IoqmaBdH-3ojNBgdJPNCYzIFBL3$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AYZSJCFJMFQMG7ESZGJFGJ3Y72XGXAVCNFSM6AAAAABGXGHJQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGY2DAOJQHA__;!!PDiH4ENfjr2_Jw!A17ca1tE_nhqhFpsIFuyZBNLHRCzoR7-16rH2WlA0omF38LOg0lW9nNJnoP4OetcXv5K3IoqmaBdH-3ojNBgdJPNCd4ZG6SR$.
You are receiving this because you commented.Message ID: @.***>


delete all data in smart contract when re-deploy?

is there anyway to delete all data in smart contract table, when re-deploying(cause of code modification) it??

cleos set contract account -c

cleos set contract account -c

@helperShang's command is for clearing contract from account, but not clearing table. There's no convenient way to clear table yet.

One of the possible ways is to make an action to delete one or more rows, and then execute it multiple times until all rows are removed.
If you have further questions please ask https://eosio.stackexchange.com/


Hindi Readme for multilinguals

New Readme can be written in Hindi to help multilinguals.

Please assign me this issue under iwoc and easy/medium/hard.

Hi @A91y,
I don't think there is a current need for README.md in Hindi.


MAINT: Standardize reader get value methods.

The daily/session bar reader's spot_price took the same parameters and
returned the same kind of output as the minute bar reader's get_value.
Standardize on one method to make a common interface, which may be
formally factored out in a later patch; to help enable writing reader
implementations or mixins which can be agnostic to the bar frequency.

Coverage decreased (-0.001%) to 86.215% when pulling 71a34bf7acc23523a485f84879ec8945ecdceaf8 on spot-price-get-value into eba78aec1bb869c73bf930dccd1fe676669ff74d on master.

Coverage decreased (-0.001%) to 86.215% when pulling 71a34bf7acc23523a485f84879ec8945ecdceaf8 on spot-price-get-value into eba78aec1bb869c73bf930dccd1fe676669ff74d on master.

Coverage decreased (-0.001%) to 86.215% when pulling 71a34bf7acc23523a485f84879ec8945ecdceaf8 on spot-price-get-value into eba78aec1bb869c73bf930dccd1fe676669ff74d on master.


Use Github Issues for release description setting

It'd be great if you could have a running changelog in a Github issue, and then use it when creating the release… so it's created with a fully fleshed out description as soon as it's created, no manually editing after the fact.
I tested it manually using https://github.com/buildkite/agent/issues/322 and https://github.com/buildkite/agent/issues/32 by hitting "edit" and copy and pasting the issue description into the release description, then commenting on each issue to link to the release, and finally closing the issue.
Perhaps something like:
--link-issue "$VERSION Changelog"
And it'd just search for the first issue with that name.

Yeah I would love it if you could just pass in a blob of text.


Switch to use ampl-asl instead of ampl-mp

See https://github.com/conda-forge/staged-recipes/pull/28198#issue-2655999717 . This is the first step in solving https://github.com/conda-forge/ipopt-feedstock/issues/55 . I wanted to enable the support for it on Windows, but then I noticed that the vendored CMake build system that we are using does not have proper support for it. Probably the proper solution is to switch to use the upstream autotools-based build system also on Windows, but anyhow I do no think we need to wait to switch to ampl-asl .

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Requires https://github.com/conda-forge/ampl-asl-feedstock/pull/1 .

Requires conda-forge/ampl-asl-feedstock#1 .

Done. @conda-forge/ipopt the CI is green and the PR is ready for review/discussion, thanks!

@conda-forge-admin, please rerender

Similar PR on homebrew: https://github.com/Homebrew/homebrew-core/pull/197123 .

@conda-forge-admin please rerender

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!


Update to Tensorflow 2.0

I updated this to Tensorflow 2.5, with the Automatic Update tool from Google. I also removed the models that come with it, and increased its FPS and removed the rendering.

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。

Thank you so much. It ran on my machine!


doc: add "Stored and View Schema" doc for tree

Document for #9234.

@CraigMacomber, @DLehenbauer: I dropped some comments in - hope that is ok and hope they are useful.

@CraigMacomber To see whether this schema definition is versatile enough for our use cases, I tried to write a prototype of a schema converter that converts a PropertyDDS to the proposed Schema definition. If you have some time, I would appreciate if you could have a short look at the converter(https://github.com/ruiterr/FluidFramework/blob/PropertyDDSSchemaConverter/experimental/PropertyDDS/packages/property-dds/src/convertSchema.ts) to check, whether I correctly understood the schema definition.
I noticed a few aspects while trying to map the schemas:

How would we handle inheritance (and maybe also the related schema versioning)? The current schema definition allows me to declare a set of compatible types for a field. In principle, I could create the list of all valid types from the inheritance chain and put this into the set. Unfortunately, this would not be very extensible. The moment a new type is added that inherits from a base type, all schemas referencing the base type would have to be updated to reflect this new addition to the set of allowed types. In addition to that, it would potentially be a quite large list, which would be duplicated in many places in all schemas. I think we should introduce some mechanism to declare dependencies between the schemas.
Which key should I use for the default entry (in explicity sequences and strings)? At the moment, I arbitrarily choose "entries", but this risks, that every application uses a different key name, making interoperability difficult. It probably would make sense to have a default in the schema language, which indicates that this is a node that is a pure container for a sequence (and does not allow other traits).
Which value type should I use for the string defintion? At the moment, there is no character type. Do we need to add that?
Value currently only supports number. In PropertyDDS we have more fine grained number types. I assume, that we will provide pre-registered default schemas for those, which build on top of the schema language, but already specify the actual data type in a common well understood way?

Generally, it seems that most of the current PropertyDDS schema can be mapped to your proposed schema defintion (one way, it is not a bijection, many schemas could not be projected back into the PropertyDDS system).
There are a few concepts I didn't map, but these are probably on a higher level of abstraction and there is no intention to include them in this low level schema definition?

Annotations
Length constraints for arrays / strings
Constants
Values for enums
Default values

Is there a plan where this additional information within the schema would be stored? I assume, we would need to still store this information together with the compiled schema, having something like a source schema plus a compiled schema in the document.

@ruiterr :

How would we handle inheritance (and maybe also the related schema versioning)? The current schema definition allows me to declare a set of compatible types for a field. In principle, I could create the list of all valid types from the inheritance chain and put this into the set. Unfortunately, this would not be very extensible. The moment a new type is added that inherits from a base type, all schemas referencing the base type would have to be updated to reflect this new addition to the set of allowed types. In addition to that, it would potentially be a quite large list, which would be duplicated in many places in all schemas. I think we should introduce some mechanism to declare dependencies between the schemas.

I'd assume an actual schema language (embedded DSL or otherwise) would provide a way to reuse lists of type in multiple places (we did with for whiteboard), as well as deal with cross schema dependencies (including co-recursive ones). I'm going to consider those schema language issues, which I've been trying to scope out of this document.
In response to the rest of this I have:

Added the following sections to the doc:

Do we need bounded open polymorphism?
Approaches for bounded open polymorphism (this includes for example of explicitly listing all the types as one option, but provides some others as well)
Inheritance Notes

Updated the "Design-pattern apps can use to handle schema migrations" section to have a lot more detail, and cover how it relates to versioning.

Which key should I use for the default entry (in explicity sequences and strings)? At the moment, I arbitrarily choose "entries", but this risks, that every application uses a different key name, making interoperability difficult. It probably would make sense to have a default in the schema language, which indicates that this is a node that is a pure container for a sequence (and does not allow other traits).

I have been using "children" if there isn't something more specific that makes sense for the particular domain. As Daniel pointed out, "Items" makes sense for Json's array better than children. I think in the case where the tree is locally made entirely out of that one sequence, calling it "items" makes sense. Anyway, I don't expect this case to actually come up a lot (I expect most cases will not need an intermediate node to allow representing a difference between an empty sequence and "null"), but if it does, we should think about it more.

Which value type should I use for the string defintion? At the moment, there is no character type. Do we need to add that?

The set of value types in my example is pretty much a placeholder. If you do want to make an editiable string using them though there is an example of that in SchemaExamples.ts. I Assume we will want something smarter value wise before we commit to document compatibility (In M2), and would like to scope that out of this PR.

Value currently only supports number. In PropertyDDS we have more fine grained number types. I assume, that we will provide pre-registered default schemas for those, which build on top of the schema language, but already specify the actual data type in a common well understood way?

Yes.

There are a few concepts I didn't map, but these are probably on a higher level of abstraction and there is no intention to include them in this low level schema definition?

Annotations
Length constraints for arrays / strings
Constants
Values for enums
Default values

TreeSchema.extraGlobalFields now has some documentation about annotations.
More length constraints (beyond what multiplicity allows), if desired, should be possible to add in the future. If we want to enforce them during merges, we probably want to handle them at this level. If we just want to check them on read, that would be easier, but both could be done, but thats more of a M2 or M3 discussion. I have added this (and some other things) to the schedule section accordingly.
I think constants, enums and default values are fine to leave for after M3. I've added some stuff about them in the schedule section. I'm not clear on what you mean by constants, but I'm guessing its ok to delay worrying about for now: if not let me know and we can discuss earlier.

Is there a plan where this additional information within the schema would be stored? I assume, we would need to still store this information together with the compiled schema, having something like a source schema plus a compiled schema in the document.

The "Places we can store stored schema information" section covers what our options here are. My example implementation doesn't currently have an opinion on which of those we support extra data being stored in. I suspect the first/easiest place to store such data is in the source as code, and make it available on the view schema only. The ability to store extra data in the schema themselves in a way thats guaranteed to make for all apps using the document  (as part of stored schema, in some schema store, or in code with a hash check or something) could be added latter.
I don't have time today to look at your code: I'll review it and post my thoughts on it once I have time.

I'd assume an actual schema language (embedded DSL or otherwise) would provide a way to reuse lists of type in multiple places (we did with for whiteboard), as well as deal with cross schema dependencies (including co-recursive ones).

I am mainly concerned with the case, where we have schema-on-write and the schemas are stored within the document (or a central repository). For pure application specific, on-read schemas, it would certainly be possible to compile these sets of compatible types on the fly from some other schema representation (in our case, we for example could do it based on the schemas registered in the PropertyFactory). However, once the schemas are stored in the document, this dynamic compilation would no longer work. If a new type is added, the application would have to update all schemas within the document that reference this .
I assume that the documents would contain the schema using the representation you proposed here? Or do you assume it would be dynamically created from the DSL?

Build a nominal open polymorphism system into the schema, allowing types to explicitly declare they are a member of a particular typeset/interface. Compatibility between stored and view schema can include checking these align.

That is the approach I had in mind. I was pondering to add the concept of a type-group, which can be referenced in the set of types. Schemas can be added to the type group and thus would automatically be valid everywhere, the group is referenced. I agree that the term inheritance is probably not correct here, since this is a more generic concept, since it does not specify in which way the types are related, only that all of them might appear. In contrast inheritance implies, that the types are compatible (and potentially even share code).

I have been using "children" if there isn't something more specific that makes sense for the particular domain.

I guess it doesn't matter much, which term we use, but it should be declared in the schema.ts as a constant, so that it is used everywhere.

Anyway, I don't expect this case to actually come up a lot (I expect most cases will not need an intermediate node to allow representing a difference between an empty sequence and "null"), but if it does, we should think about it more.

My impression was, that this is actually very common. In my schema conversion it applies to every string and every array node (you could potentially avoid it in the case, where the string/array is marked as required in the schema, but for dynamic or optional ones it is needed and thus for simplicity of implementaiton it probably should always be used).

I'm not clear on what you mean by constants, but I'm guessing its ok to delay worrying about for now: if not let me know and we can discuss earlier.

Constants is a feature supported by the PropertyDDS schema language. It adds constant values to the data structure at runtime, which are specified in the schema. Those are not stored in the actual document. Use cases for this were things like adding a unit or documentation field. They therefore have some overlap with annotations, but they have some additional complexity, because parent schemas are allowed to overwrite the value of constants in the nested schemas (which I guess is a bit like the structural typing you mentioned). Since this does not affect the actual data in the document, it probably doesn't relate to the discussion here and I am also not sure, whether we would like to support this in the future or should instead use a different mechanism.
In the section on migration you suggest:

Author new more flexible schema with same type identifier.

I am wondering, whether we should use the same type identifier or a new one (potentially using the type-group mechanism to declare compatibility). In PropertyDDS, we have always created a new type (using semver to indicate that the type is compatible), but admittedly I didn't yet consider in much detail, how a sysem with in-place updates of types would work.
So, I'd like to more clearly understand the different pros and cons for both approaches:
Creating a new type

Many different versions of the schema can coexist in the same document and still be conformant to the schema(s)
In references / schemas / application code it is possible to explicitly specify which version is the minimum requirement for compatibility
Type identifiers are compatible between documents (i.e. two documents referring to the same version of a schema reference exactly the same data layout). This makes it easier to copy / move data between documents. Similarly, type identifiers can more easily related to external systems (e.g. the table layout in a relational database that is updated based on data from Fluid).
Creates a clear order in which the schemas are updated

More tedious for application authors (they have to maintain a list of all the schema versions and add version numbers when they reference types)
Requires a mechanism to handle bounded open polymorphism to be feasible.

Updating existing type

Simpler for application authors
No need to update references to the schema / use a polymorphism mechanism

Coexistance of schema versons in one document is difficult. Either all new fields are marked as optional (in which case there could be instances in which some random subset of the optional fields is not filled, which does not correspond to the order in which the schema was updated) or the old data would be out-of-schema once the schema is updated. In the latter case we would either have to accept a schema violation or migrate all data within the document.

I think in general, the approach how we handle schema updates (having the application support the old and new schema / having a migration handler) is probably very similar in both cases.
@CraigMacomber @DLehenbauer Do you see other pros- and cons- for the different approaches?
@CraigMacomber In the design document, you mention "schematize" several times. Is this / will the be part of Fluid / the SharedTreeDDS or is this a higher level abstraction that should not be part of the design document on this level?

I'd assume an actual schema language (embedded DSL or otherwise) would provide a way to reuse lists of type in multiple places (we did with for whiteboard), as well as deal with cross schema dependencies (including co-recursive ones).

I am mainly concerned with the case, where we have schema-on-write and the schemas are stored within the document (or a central repository). For pure application specific, on-read schemas, it would certainly be possible to compile these sets of compatible types on the fly from some other schema representation (in our case, we for example could do it based on the schemas registered in the PropertyFactory). However, once the schemas are stored in the document, this dynamic compilation would no longer work. If a new type is added, the application would have to update all schemas within the document that reference this .
I assume that the documents would contain the schema using the representation you proposed here? Or do you assume it would be dynamically created from the DSL?

Yes, my schema types are what would be stored in the document (though serialized or course: could be done by replacing the maps with objects, the sets with arrays and using JSON). See StoredSchemaRepository for details on how thats handled/updated.
I have also added StoredSchemaRepository.spec.ts which has a full executable example (as a test) going through schema changes with both stored and view schema. I think that should be easier to understand that my various descriptions of the process in the doc.

Build a nominal open polymorphism system into the schema, allowing types to explicitly declare they are a member of a particular typeset/interface. Compatibility between stored and view schema can include checking these align.

That is the approach I had in mind. I was pondering to add the concept of a type-group, which can be referenced in the set of types. Schemas can be added to the type group and thus would automatically be valid everywhere, the group is referenced. I agree that the term inheritance is probably not correct here, since this is a more generic concept, since it does not specify in which way the types are related, only that all of them might appear. In contrast inheritance implies, that the types are compatible (and potentially even share code).

We designed, but never implemented, an approach like this for view schema in whiteboard: I think it should work well for their use cases. Adding it to the stored schema is practical as well.
If you are happy with this approach, I think we can consider bounded open polymorphism solved for now since we have at least one design we are confident we can add when it's time to implement it (prioritization for implantation and considering alternatives can happen in the M1-M2 timeframe).

I have been using "children" if there isn't something more specific that makes sense for the particular domain.

I guess it doesn't matter much, which term we use, but it should be declared in the schema.ts as a constant, so that it is used everywhere.

Added to the new Builders.ts file along with some other handy constants.

Anyway, I don't expect this case to actually come up a lot (I expect most cases will not need an intermediate node to allow representing a difference between an empty sequence and "null"), but if it does, we should think about it more.

My impression was, that this is actually very common. In my schema conversion it applies to every string and every array node (you could potentially avoid it in the case, where the string/array is marked as required in the schema, but for dynamic or optional ones it is needed and thus for simplicity of implementaiton it probably should always be used).

Yes, those are good places to use that pattern. I guess in practice you have a lot more of those cases than I expected.

I'm not clear on what you mean by constants, but I'm guessing its ok to delay worrying about for now: if not let me know and we can discuss earlier.

Constants is a feature supported by the PropertyDDS schema language. It adds constant values to the data structure at runtime, which are specified in the schema. Those are not stored in the actual document. Use cases for this were things like adding a unit or documentation field. They therefore have some overlap with annotations, but they have some additional complexity, because parent schemas are allowed to overwrite the value of constants in the nested schemas (which I guess is a bit like the structural typing you mentioned). Since this does not affect the actual data in the document, it probably doesn't relate to the discussion here and I am also not sure, whether we would like to support this in the future or should instead use a different mechanism.

Ok. We should be able to add support for that at either the view or stored schema level should use-cases arise.
I think we can lump it in with the concept of storing arbitrary extra data in the schema since it doesn't interact with data's schema compliance or merging.

In the section on migration you suggest:

Author new more flexible schema with same type identifier.

I am wondering, whether we should use the same type identifier or a new one (potentially using the type-group mechanism to declare compatibility). In PropertyDDS, we have always created a new type (using semver to indicate that the type is compatible), but admittedly I didn't yet consider in much detail, how a sysem with in-place updates of types would work.
So, I'd like to more clearly understand the different pros and cons for both approaches:
Creating a new type
Pro

Many different versions of the schema can coexist in the same document and still be conformant to the schema(s)
In references / schemas / application code it is possible to explicitly specify which version is the minimum requirement for compatibility
Type identifiers are compatible between documents (i.e. two documents referring to the same version of a schema reference exactly the same data layout). This makes it easier to copy / move data between documents. Similarly, type identifiers can more easily related to external systems (e.g. the table layout in a relational database that is updated based on data from Fluid).
Creates a clear order in which the schemas are updated

Con

More tedious for application authors (they have to maintain a list of all the schema versions and add version numbers when they reference types)
Requires a mechanism to handle bounded open polymorphism to be feasible.

Updating existing type Pro

Simpler for application authors
No need to update references to the schema / use a polymorphism mechanism

Con

Coexistance of schema versons in one document is difficult. Either all new fields are marked as optional (in which case there could be instances in which some random subset of the optional fields is not filled, which does not correspond to the order in which the schema was updated) or the old data would be out-of-schema once the schema is updated. In the latter case we would either have to accept a schema violation or migrate all data within the document.

I think in general, the approach how we handle schema updates (having the application support the old and new schema / having a migration handler) is probably very similar in both cases.
@CraigMacomber @DLehenbauer Do you see other pros- and cons- for the different approaches?

Your list seems correct. One minor difference in how I was thinking about it:
My perspective has been that you use in place updates of schema as the mechanism to handle updates which get new types (update the parent's field's allowed types: this is always compatible with existing document content so its legal).
Your note that it requires open bounded polymorphism is a good one: in place updates are just one way to implement open bounded polymorphism. Updating type sets (as discussed above) is really a special subset of inplace updates, and could be useful here as well.
I think in general we have to support both, since they work well together:

in place updates are can be used to prevent new type changes from bubbling up to the root, or to handle them at the root, as well as handling cases where a new field really is semantically optional, and adding new content types in existing places.
new identifier when making incompatible changes (so data in the document is never out of schema): use an in-place update as well on its parent to allow the new type there.

@CraigMacomber In the design document, you mention "schematize" several times. Is this / will the be part of Fluid / the SharedTreeDDS or is this a higher level abstraction that should not be part of the design document on this level?

I want to develop schematize as a general purpose schema on read system for trees: it takes some kind of tree, a library for applying some schema system to that tree, and a collection of handlers for violation.
Then, as part of Fluid Tree, we can use support consumers what want to use schematize by writing support for using it with our schema system and tree type. I think it should be optional, but the encouraged way to abstract legacy schema handling, and any other schema on read use-cases.
For ease of development, it will likely initially live in a subfolder inside of Fluid Tree (after its ported out if whiteboard), but someday might get its own package.


Check if isInteger is supported and add alternative function

In 24h mode, the script uses isInteger which is not supported by IE11.
I added an alternative check for these cases.

Sorry to replay late. Thanks for your contribute!


Add Smoke/E2E CI Automation

We need CI automation to deploy a testing environment (#131) and execute smoke tests (#100).  This should be executed when a PR is opened, when a PR receives a new commit, and after a PR is merged into main.   Tests triggered by PRs should block the PR until the tests pass.  Tests triggered on merges to main should post the pass/fail of the test as a notification to project owners/admins.

WIP PR: https://github.com/openshift/release/pull/19714

Testing deployment of an aws ec2 instance (t1.micro size) and ssh accessibility.
Was held up due to a bug that resulted in tests not being run, but still reporting success. This is due to a regression bug in validation, where tests that have the same name as an image defined in the ci-operator conifg file will be run.  Validation is supposed to fail fast on these cases, but does not.  Was able to suss out the bug with the help of 2 of the architects.

https://github.com/openshift/release/pull/21499 Adds execution of openshift/origin (release-4.7) k8s and openshift conformance tests.


feat: working file system rendering and current working directory

Summary
Closes #80

Renders a file system object using the React D3 Tree library
Responsive positioning for the D3 tree based on refs from the Task component
Added SVGs to represent the file system objects
Implemented FileSystemRender class with FileSystemNode class
The FileSystemNode class creates the custom D3 Tree nodes with the images (and alt texts) and labels
Added method to convert the FileSystem objects into RawNodeDatum objects for rendering with the d3 library (and memorized it since this is an expensive operation)
Added lodash to get a deep copy for file system (states should be immutable)

Test Plan

Testing is done on the Searching page with a useEffect and a setTimeout to simulate changing aspects of the file system after some time (3 seconds
Changes current working directory to a hidden one using it's path, removes a file, and adds a new one

How it looks now on desktop and mobile:

Some future TODOs:

Make the stroke have the gradient like in the Figma design( I went with one of the blueish colors from Figma for now).
Make the graph centered (it's kind of roughly centered now)


[code][low prio] MysqlGameAdapter: Features seem to saved in column "dataset"

Looking at MysqlGameAdapter::setFeatures() is confusing, as the column dataset is used. As far as I understand, the features are not stored in the database at all, but retrieved from the ML server. Maybe this could be made clearer with comments in the code.

On the game creation form, the dataset field also has feature set as background text.


Completed Rock Paper Scissor

@Yangani: Thanks for submitting a pull request. During the next couple of weeks, this repository is going to have a major overhaul. When that process is over, please submit another pull request with any changes you feel would benefit the repo. I'll make sure that it takes less time to get a reply :).


PathHistogram and PathDensityHistogram API are not consistent

Problem
PathDensityHistogram.add_trajectory() and PathDensityHistogram.add_data_to_histogram() work with Trajectory objects and lists of them.
PathHistogram.add_trajectory() and PathDensityHistogram.add_data_to_histogram() expect a list of list (actually an iterable of an iterable).
This situation makes it strange to create a histogram of p(r|TP) if you expect the interface of PathDensityHistogram.
Proposed solution(s)

create a subclass from PathHistogram that takes cvs at initializing time and creates a histogram of p(r|TP). I volunteer to do that.
also make PathHistogram dependant on a cv when initialized, then it can map the snapshots itself to a list of lists
change function names to make the difference more clear
let the user decide if normalization should be on a per trajectory level or on a per snapshot level, such that you can get out p(r|TP) from PathDensityHistogram (that defies the definition of PathDensityHistogram)

For the time being, these things need to stay as-in, because we don't want to change the API. However, I agree that the nomenclature is a little weird. This is something that we should revisit as part of the 2.0 updates, when we next make major changes to the API.

Sorry for the long delay; this actually could have been done a while ago, now that I'm taking time to think about it!
I think the best approach is what I hinted at in the TODO just above PathDensityHistogram:
https://github.com/openpathsampling/openpathsampling/blob/fad5de181ffbbc2f54d3ad0f5c12c0e1758db3a4/openpathsampling/analysis/path_histogram.py#L293-L296
So this is essentially your option 1 (and, to an extent, 4):

TrajectoryHistogram includes the trajectory -> path in CV space logic. No defaults -- user just sets per_traj and interpolate. That's a subclass of PathHistogram and a superclass of PathDensityHistogram.
PathDensityHistogram is the subclass that defines per_traj=True and defaults to interpolate=True (with the option to change)
FreeEnergyHistogram (I was thinking of this for free energy plots based on the reweighted path ensemble; maybe you have a better name?) is the subclass that defined per_traj=False and at least defaults to interpolate=False (possibly even defines it as necessarily so? Is there a reason to do per_traj=False and interpolate=True? Seems like that would be misleading if bin resolution can resolve a barrier that might be crossed in one step.)


Updated microsoft-azure-attestation's readme.md for the integration with Occlum

Purpose
Updated README.md for the integration sample code for doing Microsoft Azure Attestation in Occlum
Does this introduce a breaking change?

[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

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

How to Test
N/A
What to Check
Verify that the updates provides clear and relevant information.

LGTM

@kroshkina-ms  - "Azure Attestation integration in Occlum" looks good to me too


Soft thresholding aka L1 regularization

The Lasso can easily be implemented using a squared error (LinearRegression) loss and soft thresholding on the weights (i.e. setting weights between -t and t to zero in the backward pass). Is this possible to implement?

yes, you can.
you can reference Ftrl(Optimizer)https://github.com/dmlc/mxnet/blob/master/python/mxnet/optimizer.py

The Ftrl optimizer doesn't work:
import mxnet as mx
import numpy as np

data = np.random.rand(500,3)
sumlab1 = (data[:,0]+data[:,1])
sumlab2 = sumlab1 + np.transpose(np.random.rand(500,1)*0.1)
label = np.transpose(sumlab2)

batch_size = 50
ntrain = int(data.shape[0]*0.8)
train_iter = mx.io.NDArrayIter(data[:ntrain, :], label[:ntrain], batch_size, shuffle=True,label_name='lin_reg_label')
eval_iter = mx.io.NDArrayIter(data[ntrain:, :], label[ntrain:], batch_size)

X = mx.sym.Variable('data')
Y = mx.symbol.Variable('lin_reg_label')
fully_connected_layer  = mx.sym.FullyConnected(data=X, name='fc1', num_hidden = 1)
lro = mx.sym.LinearRegressionOutput(data=fully_connected_layer, label=Y, name="lro")

model = mx.mod.Module(
    symbol = lro ,
    data_names=['data'],
    label_names = ['lin_reg_label']# network structure
)

model.fit(train_iter, eval_iter, optimizer='Ftrl',
            optimizer_params={'learning_rate':0.01},
            num_epoch=100)

AttributeError: type object 'NDArray' has no attribute 'abs'

@patwa67 , I have fixed it in my project, and you can refer to https://github.com/moveforever/mxnet/commit/b822e95b4fa176a462221347dc40ab0c42a2058f

How do I get that change into my MXNet installation?

copy file python/mxnet/optimizer.py

copy file python/mxnet/optimizer.py into lib/python2.7/site-packages/mxnet-0.9.5-py2.7.egg/mxnet

There is no change in:
https://github.com/dmlc/mxnet/blob/master/python/mxnet/optimizer.py
Do you mean another file?

I don't have:
site-packages/mxnet-0.9.5-py2.7.egg/mxnet/
Can I just create these or do I need to install something?

OK, I just replaced in dist-packages/mxnet/
However, it was necessary change to:
from .ndarray import abs as ABS


Akash Chintaluri's Commit

Name: Akash Chintaluri
Reg No: RA2211003011525
I/II/III Year: II Year
SRMIST email<EMAIL_ADDRESS>Issue solved (mention it like #1):
was not able to solve.
Describe your changes/approach even if you were not able to complete
the field for geoid separation was wrong. trying fixing it for test 2.
tried changing content of latitude(3) and longitude(5) direction fields and added few boolean variables in gga_t struct
for test 1

changes were made in gps.c


Code run time Error (livechat-widget' is not a known element)

Describe the bug
We try to test LiveChat on our application but it did not work, tried to run code but that time showed an error.
We have referenced the document for implementation.
https://github.com/livechat/chat-widget-adapters
To Reproduce
Steps to reproduce the behavior:
See error:
error NG8001: 'livechat-widget' is not a known element:
1. If 'livechat-widget' is an Angular component, then verify that it is part of this module.
2. If 'livechat-widget' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
Screenshots

Version:
-Angular Version 9

Hello @AmolShinde11 👋
Sad to hear that you have encountered an error with our package.
Unfortunately, as for now, this package is aimed to support the last two Angular versions: 12 and 13 as below 12 the output produced by@angular/compiler@13 seems to be incompatible with the lower version.
The dependence on specific Angular version is emphasized using peerDependecies inside packages package.json as you can see here: https://github.com/livechat/chat-widget-adapters/blob/832c5cafc34c48950ef1112c9c9b2f335f340558/packages/widget-angular/package.json#L33
Because your request targets a version lower than the currently supported ones, this issue will not have a high priority. I won't close it right away and I will try to do some debugging first and we will see if we can do anything more to actually support a wider range of Angular versions.
Feel free to propose your solution if you will have one or provide any more details if some will be available 🙂

Closing as for now we are not officially supporting the Angular versions lower than 12.
The issue will be reopened If we will introduce support for Angular 11.


Firestore publisher SaveAll

related #1779
saveAll for publisher input

@meltsufin @elefeint PTAL, it's now using the streaming API


Properly track ontology versions

Official releases of ontologies should be released via GitHub Releases. Staging and production releases should be made available in staging and gh-pages branches along with the continuous integration results.

Need to specify the "master" version of the ontology and the language it is in.
I prefer that the ontologies all be in OWL.
Regardless of the language, there are multiple reifications of the ontologies (.owl, .rdf, ...) and a particular one should be declared as the master document.
Perhaps create a subfolder for "other_reifications".

We should use code that lets us output via command line and owlapi to different formats:
https://github.com/ghxiao/owl-toolkit

@jpsluka We are making RDF/OWL be the "master" file format.
@bherr2 Can you confirm the following branch structure?

master (Stable code, but not yet released)
dev (Unstable code)
staging (Stable code, released?)
gh-pages (Documentation?)

master (Stable, most up-to-date code, but not necessarily released)
develop (Unstable, in development code) -- Every one of our projects calls it develop, not dev just our preference.

We only need staging and gh-pages IF we are generating things using Continuous Integration and pushing them automatically (ie running tests, generating documentation, compiling the rdf and different reifications, etc). At this stage, it doesn't seem likely that we'll have that. If we can get that far, here's how it would work:
Whenever a commit is pushed to develop this would be picked up by Travis CI. It would then run the doc generator, run any tests we have setup, and compile the rdf + reifications. If successful, it'd push the generated files to staging. Then netlify.com would see the new push to staging and host that branch as a website.
Whenever a commit is pushed to master the same process would be kicked off, but instead pushed to gh-pages which is then picked up and hosted by github.io.
So:

staging (Built documentation and ontologies from develop)
gh-pages (Built documentation and ontologies from master)

When a tag is pushed, a similar process is spun off, but instead of pushing the results to a branch, its pushed to a tag which becomes part of the release.

I can help setup Travis CI, but the only way that'll work is if the documentation and ontology generation workflow can actually be run on the command line.

I agree that we're not that far yet for the CI, but I'm working on restructuring the code to be able to do this. So I think we should push this to the next release possibly and just rename the dev branch to develop.


dry config and make it responsive

Closes https://github.com/PostgREST/postgrest-docs/issues/662

The configs now look better but I think the List of Parameters section needs subsections. Like server configs, pool configs, etc.


TypeError: create_model() missing 1 required positional argument: 'model_name'

[x ] This is actually a bug report.
[ ] I am not getting good LLM Results
[ ] I have tried asking for help in the community on discord or discussions and have not received a response.
[x ] I have tried searching the documentation and have not found an answer.

What Model are you using?

[x ] gpt-3.5-turbo
[ ] gpt-4-turbo
[ ] gpt-4
[ ] Other (please specify)

Describe the bug
A clear and concise description of what the bug is.
astream partial stopped working
To Reproduce
Steps to reproduce the behavior, including code snippets of the model and the input data and openai response.
import instructor
from pydantic import BaseModel

client = instructor.from_openai(openai.OpenAI())

class User(BaseModel):
    name: str
    age: int

user_stream = client.chat.completions.create_partial(
    model="gpt-4-turbo-preview",
    messages=[
        {"role": "user", "content": "Create a user"},
    ],
    response_model=User,
)

for user in user_stream:
    print(user)
    #> name=None age=None
    #> name=None age=None
    #> name=None age=None
    #> name=None age=None
    #> name=None age=25
    #> name=None age=25
    #> name=None age=25
    #> name=None age=25
    #> name=None age=25
    #> name=None age=25
    #> name='John Doe' age=25
    # name=None age=None
    # name='' age=None
    # name='John' age=None
    # name='John Doe' age=None
    # name='John Doe' age=30
    ```

**Expected behavior**
A clear and concise description of what you expected to happen.

it streams

**Screenshots**
If applicable, add screenshots to help explain your problem.

def test_instructor():
    import openai
    import instructor
    from pydantic import BaseModel

    client = instructor.from_openai(openai.OpenAI())

    class User(BaseModel):
        name: str
        age: int

  user_stream = client.chat.completions.create_partial(

        model="gpt-3.5-turbo",
        messages=[
            {"role": "user", "content": "Create a user"},
        ],
        response_model=User,
    )

tests/text/test_instructor.py:15:

../../.cache/pypoetry/virtualenvs/llmtext-HjOqM6W8-py3.11/lib/python3.11/site-packages/instructor/client.py:135: in create_partial
response_model = instructor.Partial[response_model]  # type: ignore

cls = <class 'instructor.dsl.partial.Partial'>, wrapped_class = <class 'test_instructor.test_instructor..User'>
def __class_getitem__(
    cls,
    wrapped_class: type[T_Model] | tuple[type[T_Model], type[MakeFieldsOptional]],
) -> type[T_Model]:
    """Convert model to one that inherits from PartialBase.

    We don't make the fields optional at this point, we just wrap them with `Partial` so the names of the nested models will be
    `Partial{ModelName}`. We want the output of `model_json_schema()` to
    reflect the name change, but everything else should be the same as the
    original model. During validation, we'll generate a true partial model
    to support partially defined fields.

    """

    make_fields_optional = None
    if isinstance(wrapped_class, tuple):
        wrapped_class, make_fields_optional = wrapped_class

    def _wrap_models(field: FieldInfo) -> tuple[object, FieldInfo]:
        tmp_field = deepcopy(field)

        annotation = field.annotation

        # Handle generics (like List, Dict, etc.)
        if get_origin(annotation) is not None:
            # Get the generic base (like List, Dict) and its arguments (like User in List[User])
            generic_base = get_origin(annotation)
            generic_args = get_args(annotation)

            # Recursively apply Partial to each of the generic arguments
            modified_args = tuple(
                (
                    Partial[arg]
                    if isinstance(arg, type) and issubclass(arg, BaseModel)
                    else arg
                )
                for arg in generic_args
            )

            # Reconstruct the generic type with modified arguments
            tmp_field.annotation = (
                generic_base[modified_args] if generic_base else None
            )
        # If the field is a BaseModel, then recursively convert it's
        # attributes to optionals.
        elif isinstance(annotation, type) and issubclass(annotation, BaseModel):
            tmp_field.annotation = Partial[annotation]
        return tmp_field.annotation, tmp_field

  return create_model(

        __model_name=(
            wrapped_class.__name__
            if wrapped_class.__name__.startswith("Partial")
            else f"Partial{wrapped_class.__name__}"
        ),
        __base__=(wrapped_class, PartialBase),
        __module__=wrapped_class.__module__,
        **{
            field_name: (
                _make_field_optional(field_info)
                if make_fields_optional is not None
                else _wrap_models(field_info)
            )
            for field_name, field_info in wrapped_class.model_fields.items()
        },
    )  # type: ignore

E       TypeError: create_model() missing 1 required positional argument: 'model_name'
../../.cache/pypoetry/virtualenvs/llmtext-HjOqM6W8-py3.11/lib/python3.11/site-packages/instructor/dsl/partial.py:292: TypeError

switching pydantic version to 2.7.* fixed it, the problem happens on pydantic version 2.8.*

hey @vikyw89 , I tried running the code snippet above and didn't get any issues. Any other ways to reproduce the error?
import instructor
from pydantic import BaseModel
import openai

client = instructor.from_openai(openai.OpenAI())

class User(BaseModel):
    name: str
    age: int

user_stream = client.chat.completions.create_partial(
    model="gpt-4-turbo-preview",
    messages=[
        {"role": "user", "content": "Create a user"},
    ],
    response_model=User,
)

for user in user_stream:
    print(user)

This was my shell output
> uv pip list | grep pydantic

pydantic                      2.7.3
pydantic-core                 2.18.4
pydantic-extra-types          2.8.0

 > python3 test.py

name=None age=None
name=None age=None
name=None age=None
name=None age=None
name=None age=25
name=None age=25
name=None age=25
name='' age=25
name='John' age=25
name='John Doe' age=25
name='John Doe' age=25

Use pydantic 2.8.*


named parameters support

Thinking a bit out loud here:
Instead of having to keep track of parameter positions in a query it would be useful to use named parameters, i.e.
SELECT * FROM users WHERE lname = :lname AND fname = :fname

Then you'd have a hash of params, in any order and may have unused entries, that would be combined  for the result.
%{id: 1234, fname: "Charlie", lname: "Brown", dog: "snoopy", adversary: "Lucy"}

Under the covers this would get converted to a tuple that can then run as a normal pg query:
{"SELECT * FROM users WHERE lname = $1 AND fname = $2",["Brown", "Charlie"]}

Here's a rather terse way of doing it that I banged out this afternoon.
  def convert_named_params(query, opts) do
    named_param_regex = ~r/:(\w+)/i

    # do the regex and convert the results to a map of {:atom, string}
    m = Regex.scan(named_param_regex, query)
    |> Enum.map(fn([v, a]) -> {String.to_atom(a), v} end)

    # replace the named params in the query with $1...$n
    {q, _} = Enum.reduce(m, {query, 1}, fn({_,v}, {q, i}) -> {String.replace(q, v, "$#{i}"), i + 1 } end)

    # create a list of options to be used as params
    o = Enum.map(m, fn({k,_}) -> opts[k]  end)

    {q, o}
  end

I like it - we could do this for the SQL files as well. Want to keep rolling and spin a PR?

I'll work on a PR, it's going to be next week though, things are a bit crazy right now.

Closing for now - feel free to reopen.


[BUG] Does not resolve plug-in generated classes correctly tailwindcss-radix

See quick-start demo:
https://github.com/max-pod/example-failing-tailwind-no-custom-classname/tree/main
Error:
  39:7  error  Classname 'translate-x-radix-toast-swipe-move-x' is not a Tailwind CSS class!  tailwindcss/no-custom-classname
  39:7  error  Classname 'radix-state-closed:animate-hide' is not a Tailwind CSS class!       tailwindcss/no-custom-classname
  39:7  error  Classname 'radix-state-open:animate-slideIn' is not a Tailwind CSS class!      tailwindcss/no-custom-classname
  43:9  error  Classname 'drop-shadow-sharp/25' is not a Tailwind CSS class!                  tailwindcss/no-custom-classname
  43:9  error  Classname 'hover:drop-shadow-sharp/75' is not a Tailwind CSS class!            tailwindcss/no-custom-classname

Expected: Identify the plugin's generated classes.
Packages (all updated): https://github.com/max-pod/example-failing-tailwind-no-custom-classname/blob/main/package.json
Config:
Tailwind: https://github.com/max-pod/example-failing-tailwind-no-custom-classname/blob/main/tailwind.config.cjs
ESLint: https://github.com/max-pod/example-failing-tailwind-no-custom-classname/blob/main/.eslintrc.json
Thanks!

@max-pod
https://www.youtube.com/watch?v=ZlvtFelM8iY


conformance testing with kyverno and chainsaw

We need to add tests for:

All policies in kyverno/kyverno and kyverno/policies with reports-server installed.
Checks for all upgrade and downgrade scenarios.

Both standard and migration tests have been added, closing.


Upgrade/Change Weaviate Schema to Use text-embedding-3-small

Description

Original issue discussed here
Indirectly related issue about cost reduction (new model 5x cheaper but better accuracy)

Technical Changes

Just schema.json -- this changes the vectorizer used during ingestion AND during the retrieval

on ingestion a new index is created if it doesn't exist before. During retrieval this index's vectorizer is used for vectorizing user query

Tests & Evaluation

TBD

closes #286

Evaluation is on hold as the cloud cluster (not local) is on an older version of Weaviate that does not support the new model. I am trying to get access to the remote weaviate cluster from IT. Will be blocked until then


Banned after new update

I'm not sure if this is a coincidence or not, but the first time I ran the map after the new Pokemon Go update my map account got banned. Anyone else having this problem? Should we refrain from using the map until there's an update?

yep, same problem

yeah i created 3 accounts just for using with the map - 1 is banned and the other 2 i have to often login to the pokemon go app with those accounts just to solve the captcha - which is a real pain in the ass btw due to the fact that i can only solve the audio captcha option coz the 'choose an image' option is always half off screen and i can't click the ok button. way to go niantic.
i was kinda hoping the app would be cautious enough not to trigger any ban-worthy behavior.


Failed to activate the node-resolver package

[Enter steps to reproduce:]

...
...

Atom: 1.20.1 x64
Electron: 1.6.9
OS: Microsoft Windows Server 2008 R2 Datacenter
Thrown From: 'node-resolver' package vundefined
Stack Trace
Failed to activate the node-resolver package
At Cannot read property 'command' of undefined

TypeError: Cannot read property 'command' of undefined
    at Object.exports.activate (/packages/node-resolver/index.js:12:21)
    at Package.module.exports.Package.activateNow (~/AppData/Local/atom/app-1.20.1/resources/app/src/package.js:253:25)
    at ~/AppData/Local/atom/app-1.20.1/resources/app/src/package.js:225:38
    at Package.module.exports.Package.measure (~/AppData/Local/atom/app-1.20.1/resources/app/src/package.js:99:21)
    at ~/AppData/Local/atom/app-1.20.1/resources/app/src/package.js:218:32
    at Package.module.exports.Package.activate (~/AppData/Local/atom/app-1.20.1/resources/app/src/package.js:215:40)
    at PackageManager.module.exports.PackageManager.activatePackage (~/AppData/Local/atom/app-1.20.1/resources/app/src/package-manager.js:645:40)
    at ~/AppData/Local/atom/app-1.20.1/resources/app/node_modules/settings-view/lib/package-manager.js:535:35
    at exit (~/AppData/Local/atom/app-1.20.1/resources/app/node_modules/settings-view/lib/package-manager.js:128:22)
    at triggerExitCallback (~/AppData/Local/atom/app-1.20.1/resources/app/src/buffered-process.js:338:17)
    at ~/AppData/Local/atom/app-1.20.1/resources/app/src/buffered-process.js:359:17
    at Socket.<anonymous> (~/AppData/Local/atom/app-1.20.1/resources/app/src/buffered-process.js:220:15)
    at emitOne (events.js:101:20)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:501:12)

Commands
     -6:09.9.0 diagnostics:fix-all-in-current-file (input.hidden-input)
  2x -5:25.5.0 tree-view:remove (span.name.icon.icon-file-directory)
     -2:59.5.0 core:confirm (input.hidden-input)
     -2:39.2.0 core:backspace (input.hidden-input)
     -2:36.7.0 core:confirm (input.hidden-input)

Non-Core Packages
atom-ide-ui 0.4.0
atom-material-syntax 1.0.6
atom-material-syntax-dark 1.0.0
atom-material-ui 2.0.4
atom-typescript 11.0.9
busy-signal 1.4.3
ide-typescript 0.1.6
intentions 1.1.5
linter 2.2.0
linter-ui-default 1.6.10
mac-os-ui 0.3.0
node-resolver 1.0.1

Thanks for contributing!
It appears that this is being caused by the node-resolver package, not Atom itself. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down. You should file this issue on their repository so they can either fix the problem or tell us where the problem is coming from. The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme.


Am I still supposed to use the karma-coverage fork?

I'm trying karma coverage 0.3.1. karma-runner/karma-coverage/pull/130 was merged, but I'm getting the following error:
ERROR [coverage]: [TypeError: Cannot read property 'split' of undefined]
TypeError: Cannot read property 'split' of undefined
    at HtmlReport.Report.mix.writeDetailPage (/Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:395:30)
    at /Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:472:26
    at SyncFileWriter.extend.writeFile (/Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/util/file-writer.js:57:9)
    at FileWriter.extend.writeFile (/Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/util/file-writer.js:147:23)
    at /Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:471:24
    at Array.forEach (native)
    at HtmlReport.Report.mix.writeFiles (/Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:465:23)
    at /Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:467:22
    at Array.forEach (native)
    at HtmlReport.Report.mix.writeFiles (/Users/lukescott/Documents/Projects/webconnex/director-js/node_modules/istanbul/lib/report/html.js:465:23)

It works with the fork though.

I don't know... I will be testing this tonight

+1 Also getting exact error/stacktrace using<EMAIL_ADDRESS>

+1 I can report the same, works fine with fork, does not work against<EMAIL_ADDRESS>

Everything is working fine for me without using the fork.

Not seeing this error now using<EMAIL_ADDRESS>

No need for the fork anymore :) If there is the need change something to make it work, please open a PR/issue on karma/karma-coverage

No need for the fork anymore :) If there is the need change something to make it work, please open a PR/issue on karma/karma-coverage

If this is the case, could you update the README to indicate this @douglasduteil?
Thanks!

I can confirm I didn't need the douglasduteil/karma-coverage#next fork.

@Sjors what version of karma-coverage are you using? I have still problem that my code is showing as ES5 and not ES6 (I have opened issue in karma-coverage plugin)

I just tried to switch to<EMAIL_ADDRESS>and my code started showing ES5 instead of ES6. Looks like we still need the fork?

Having the same problem with 0.5.3. I see ES5 code instead of ES6.

Is this a problem with isparta or karma-coverage? +1 to fixing this either way.

+1


Cirrus CI for Windows Builds

Cirrus CI recently added support for Windows Docker containers. This change configures Cirrus CI so Puppeteer CI builds for Windows platform are executed in a controlled dockerized environment.
Cirrus CI has a slightly faster build start time than the current CI thanks to light Docker containers. Build times itself are also comparable with the current VM-based CI. Another advantage could be in future to unify CI builds for Linux and Windows platforms since Cirrus CI supports both of them.
Here is a Cirrus CI build for this change:

I was testing Windows Docker support on this repository and decided to share the results. Feel free to close the PR if not interested in a better CI. Didn't want to waste my work 😅
In case you will merge the PR. Don't forget to install Cirrus CI application from Github Marketplace as described in Quick Start guide.

Should this be closed in favor of #2181?


Cassandra 16259 3.11

Fix the histogram merge of the table metrics
Fix the counting of cells per partition

Merged manually.


Unable to install submodules

Issue while updating submodules
Command : git submodule update --init --recursive
Output:
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:tendermint/ledger-validator-app.git' into submodule path '/home/shikhar/go/src/github.com/ledger-cosmos/src/ledger-val' failed
Failed to clone 'src/ledger-val' a second time, aborting
Cloning into '/home/shikhar/go/src/github.com/ledger-cosmos/deps/nanos-secure-sdk'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

The submodules seen to be using SSH instead of HTTP.
I will update that to avoid these issues. In the meantime, a workaround is to connect to github with SSH credentials.
https://help.github.com/en/enterprise/2.16/user/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent

Cool, thanks.