Version 6.15.1 does not work in Internet Explorer 11

Version 6.15.1 does not seem to work in Internet Explorer 11 on Windows 10 21H2.
To Reproduce
Steps to reproduce the behavior:

Go to https://openlayers.org with Internet Explorer 11.
See errors SCRIPT1002: Syntax error ol.js (2,1386) and SCRIPT5009: ol is not defined openlayers.org (244,3)

Expected behavior
OpenLayers 6.15.1 works in Internet Explorer 11.

In the legacy build there is a block of code which is not transpiled.  The messages in it correspond to quick-lru https://github.com/sindresorhus/quick-lru/blob/main/index.js which is a dependency of geotiffjs.  I'm not sure why it was not transpiled.

https://blogs.windows.com/windowsexperience/2022/06/15/internet-explorer-11-has-retired-and-is-officially-out-of-support-what-you-need-to-know/


Atom/RSS feed

I really like it when good blogs have RSS (or atom, whatever) feeds that I can subscribe to, it means I don't need to miss a post but I also don't have to hand out my email or anything.
I have RSS on my own blog which I am trying to migrate from hugo to zine, and the lack of RSS feed generation is stopping me.

Take a look at https://github.com/kristoff-it/kristoff.it.
The current way of generating an RSS feed is by generating it as an alternative of a section page. This is not a solution that covers 100% of usecases, so hopefully it's enough for you. If it's not, let me know.

I'll try it out, thanks!

It works, thanks @kristoff-it .
Only thing I am missing from Hugo is the ability to put the whole content in the RSS feed. I can likely do without this for now.
Here's my rss.xml template:
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Home on mfashby.net</title>
    <link>https://mfashby.net/</link>
    <description>Recent content in Home on mfashby.net</description>
    <language>en-gb</language>
    <lastBuildDate>Sun, 03 Mar 2024 19:31:27 +0000</lastBuildDate>
    <atom:link href="https://mfashby.net/index.xml" rel="self" type="application/rss+xml"/>
    <item inline-loop="$page.subpages()">
      <title var="$loop.it.title"></title>
      <link var="$loop.it.permalink()"></link>
      <pubDate var="$loop.it.date.formatHTTP()"></pubDate>
      <guid var="$loop.it.permalink()"></guid>
      <description var="$loop.it.description"></description>
      <content:encoded var="$loop.it.content"></content:encoded> <!-- This doesn't work, an empty tag is emitted -->
    </item>
  </channel>
</rss>


Lint schema

BTW I branched off the wrong branch, so need to wait for merge of PR #196 first
Related issues
Refs: #none
Describe the changes made in this pull request
This PR adds a simple linter for the schema file, to see that the keys are sorted and indented right
Instructions to review the pull request
look at the github action results for linting / lint schema (will fail until we fix #148 / PR #218)

Merging with expected linting failures (should pass once #218 is merged).

Yay, now onward to merging #218. Can you do the honour, @jspaaks?


Order params in the query strings for the clients we maintain

Cloudflare (and potentially other CDNs) do not threat query string independently of the param order, which will result in cache misses if different clients are building the query strings with the params in different order.
We should ensure that our client set URL query parameters in a consistent order, e.g. by ordering them.

[ ] add a note about this in our dcos

Opened https://github.com/electric-sql/electric/pull/2044 to address this - not sure what the note in the docs should be and where?


Don't generate error types

We shouldn't be generating CloudError&CloudErrorBody types.

Requires https://github.com/Azure/autorest.modelerfour/

We can also do the analysis on C# generator side.


Maybe field type doesn't respect null check

/* @flow */

// This works:
class Foo {
  test(n: ?number): boolean {
    if (n == null) {
      return false;
    } else {
      return n > 10;
    }
  }
}

// This doesn't work:
class Foo {
  n: ?number;

  test(): boolean {
    if (this.n == null) {
      return false;
    } else {
      return this.n > 10;
    }
  }
}

A workaround:
/* @flow */

class Foo {
  n: ?number;

  test(): boolean {
    var n = this.n;
    if (n == null) {
      return false;
    } else {
      return n > 10;
    }
  }
}

Which version of flow are you using? I believe this should be fixed by @bhosmer in 0.1.3. Non local variable refinement works slightly differently, but I believe he's handled this case.
I do need to publish an updated binary for 0.1.3...that is being tracked by https://github.com/facebook/flow/issues/206

I can confirm that this appears to be working in 0.1.4 :+1:


Refactor/promisify strategies

Closes #25

I 🎩'd and everything works as expected, but I am hesitant about including handy-redis as a dependency

LGTM! I 🎩'd the auth flow as well as the login flow, then logged in again in an incognito window and everything works as expected.


1.20.1的版本在哪里下载

You can find older builds of Floodgate-Fabric on modrinth: https://modrinth.com/mod/floodgate. Do note that these are not supported, and will receive no backports of fixes from our side.


gapi.client.request() and REST args

Hello,
I was wondering where I could look up the correspondence between the terms used in Rest and the .request() args.
I am specifically interested in Cloud Storage & Downloading data: how to specify the save-to-location?
Thank you

There is no save to location since the GAPI client provides the response body to the caller(as opposed to curl which writes out to a file). I am closing this for now, but if you still need help with this question, please reopen.


Core introduction method

As specified in https://w3c.github.io/wot-discovery/#introduction-core-rd-sec, the Thing Description of a Thing Description Directory may be advertised using the CoRE Link format and the CoRE Resource Directory. In Zion we can have two modes:

[ ] Zion registers itself into another CoRE Resource Directory
[x] Zion host also a CoRE Resource Directory endpoint and automatically register its TD.

Re-opening cause #29 implemented one of the two features

* [ ]  Zion registers itself into another CoRE Resource Directory

The process to do this is described in RFC 9176, section 5. For the implementation we could either let the TDD discover local CoRE-RDs (e.g., via mDNS/DNS-DS or CoAP multicast) where is then going to register or define a registration URL via the config.
However, I assume this feature is not the most important one to add at the moment.

The process to do this is described in RFC 9176, section 5. For the implementation we could either let the TDD discover local CoRE-RDs (e.g., via mDNS/DNS-DS or CoAP multicast) where is then going to register or define a registration URL via the config.

However, I assume this feature is not the most important one to add at the moment.

Yes, exactly we can start from the configuration and later improve with automatic discovery. As you can see we labeled the issue with low priority but if there is anyone interested we can change it.


Surprising evictions and compaction on-demand downloading

Related to the incident 2023-04-17 morning: https://neondatabase.pagerduty.com/incidents/Q2LQO0GX7ISSN8
Incident was created because of we were trashing (evicting downloaded layers too soon). This is unexpected and not supposed to happen. It seems alert worked ok.
Need to investigate why would we want to evict these L0. One possible is that the tenant was inactive completly, but still we would had expected the access imitation to take care of this. Perhaps the layers had data, which was not needed by our imitations?

Logs
flushing of each layer:

2023-04-10T23:03:00.167935Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-0000000002371E99-0000000002374B99}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-10T23:13:00.178425Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-0000000002374B99-0000000002374C19}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-11T09:59:38.293469Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-0000000002374C19-0000000002376179}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-11T10:09:38.426559Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-0000000002376179-0000000002377A91}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-12T07:56:55.379204Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-0000000002377A91-00000000023790B1}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-12T08:06:55.679191Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-00000000023790B1-00000000023C1679}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679

evictions:

2023-04-13T08:44:36.424876Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19 residence_millis=207096250
2023-04-13T08:44:36.424856Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99 residence_millis=207696262
2023-04-13T08:44:36.424899Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179 residence_millis=168298136
2023-04-13T08:44:36.424921Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91 residence_millis=167698000
2023-04-13T08:44:36.424946Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1 residence_millis=89261048
2023-04-13T08:44:36.425096Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679 residence_millis=88660748

finale with compaction and eviction:

2023-04-17T04:04:31.864853Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-00000000023C7851-00000000023C78D1}: Rebuilt layer map. Did 1 insertions to process a batch of 1 updates.
2023-04-17T04:04:31.865005Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-00000000023C7851-00000000023C78D1}: scheduled layer file upload<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C7851-00000000023C78D1
2023-04-17T04:04:31.865024Z  INFO layer flush task{tenant=X timeline=Y}:flush_frozen_layer{tenant_id=X timeline_id=Y layer=inmem-00000000023C7851-00000000023C78D1}: scheduling metadata upload with 67 files (1 changed)
2023-04-17T04:04:40.581860Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:40.581855Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:40.581850Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:40.581830Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:40.581870Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679
2023-04-17T04:04:40.581864Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:40.608240Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:40.608322Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91}: Rebuilt layer map. Did 8 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.636355Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:40.636408Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1}: Rebuilt layer map. Did 7 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.642368Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:40.642563Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99}: Rebuilt layer map. Did 11 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.646876Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:40.647031Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179}: Rebuilt layer map. Did 9 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.671917Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:40.671981Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19}: Rebuilt layer map. Did 10 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.707297Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99 residence_millis=68
2023-04-17T04:04:40.707549Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19 residence_millis=41
2023-04-17T04:04:40.707701Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179 residence_millis=65
2023-04-17T04:04:40.707916Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91 residence_millis=105
2023-04-17T04:04:40.708015Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: evicted layer after known residence period layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1 residence_millis=77
2023-04-17T04:04:40.708062Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: eviction iteration complete stats=EvictionStats { candidates: 5, evicted: 5, errors: 0, not_evictable: 0, skipped_for_shutdown: 0 }
2023-04-17T04:04:40.708056Z  INFO eviction_task{tenant_id=X timeline_id=Y}:eviction_iteration{policy_kind="LayerAccessThreshold"}: Rebuilt layer map. Did 11 insertions to process a batch of 5 updates.
2023-04-17T04:04:40.736351Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679
2023-04-17T04:04:40.736402Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679}: Rebuilt layer map. Did 6 insertions to process a batch of 1 updates.
2023-04-17T04:04:40.736794Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:40.736791Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:40.736781Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:40.736801Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:40.736797Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:40.736865Z ERROR compaction_loop{tenant_id=X}: Compaction failed, retrying in 2s: Compaction requires downloading multiple times (last was 5 layers), possibly battling against eviction
2023-04-17T04:04:42.891825Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:42.891821Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:42.891817Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:42.891813Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:42.891792Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact requires download of<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:42.904880Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:42.904937Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179}: Rebuilt layer map. Did 9 insertions to process a batch of 1 updates.
2023-04-17T04:04:42.905140Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:42.905177Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19}: Rebuilt layer map. Did 10 insertions to process a batch of 1 updates.
2023-04-17T04:04:42.905524Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:42.905560Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91}: Rebuilt layer map. Did 8 insertions to process a batch of 1 updates.
2023-04-17T04:04:42.906185Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:42.906219Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1}: Rebuilt layer map. Did 7 insertions to process a batch of 1 updates.
2023-04-17T04:04:42.906578Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99}: download complete: /storage/pageserver/data/tenants/X/timelines/Y/000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:42.906613Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}:download_remote_layer{tenant_id=X timeline_id=Y layer=000000000000000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99}: Rebuilt layer map. Did 11 insertions to process a batch of 1 updates.
2023-04-17T04:04:42.906955Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:42.906944Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: Starting Level0 compaction in LSN range 0/2371E99-0/23C78D1 for 10 layers (10 deltas in total)
2023-04-17T04:04:42.906978Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C2D59-00000000023C4729
2023-04-17T04:04:42.906975Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C1679-00000000023C2D59
2023-04-17T04:04:42.906972Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679
2023-04-17T04:04:42.906968Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:42.906965Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:42.906962Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:42.906959Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:42.906984Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C7851-00000000023C78D1
2023-04-17T04:04:42.906981Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: compact includes<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C4729-00000000023C7851
2023-04-17T04:04:42.908581Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file upload 000000067F00000005000004DF000000000E-030000000000000000000000000000000002__0000000002371E99-00000000023C78D1
2023-04-17T04:04:42.908870Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: Rebuilt layer map. Did 2 insertions to process a batch of 11 updates.
2023-04-17T04:04:42.908883Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduling metadata upload with 58 files (11 changed)
2023-04-17T04:04:42.908944Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002377A91-00000000023790B1
2023-04-17T04:04:42.908941Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002376179-0000000002377A91
2023-04-17T04:04:42.908932Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374C19-0000000002376179
2023-04-17T04:04:42.908929Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002374B99-0000000002374C19
2023-04-17T04:04:42.908925Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__0000000002371E99-0000000002374B99
2023-04-17T04:04:42.908960Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C7851-00000000023C78D1
2023-04-17T04:04:42.908957Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C4729-00000000023C7851
2023-04-17T04:04:42.908954Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C2D59-00000000023C4729
2023-04-17T04:04:42.908950Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023C1679-00000000023C2D59
2023-04-17T04:04:42.908948Z  INFO compaction_loop{tenant_id=X}:compact_timeline{timeline=Y}: scheduled layer file deletion<PHONE_NUMBER>00000000000000000000000000-FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF__00000000023790B1-00000000023C1679

Important thing about logs:

ERROR about compaction battling with eviction (first time for this)
the resulting L1 is 000000067F00000005000004DF000000000E-030000000000000000000000000000000002__0000000002371E99-00000000023C78D1

this does not contain DBDIR
could it be that it contained only updates to existing data, no relation size changes
=> this might be reproducable in a test case

Discussed together that this issue is separate from check_availability #4061 because the log doesn't have basebackup.

Let's close this as this is old and we've since fixed and learned a lot of stuff:

fixed the compaction loop mentioned here
the layer rework is in place (downloads no longer rebuild LayerMap)


Update Charles to version 3.11

Thank you for the contribution. It was merged directly as b41778c8a5a06fbfe2ac7c5dbaad2700371d63ca to keep commit history cleaner. Your contribution is still credited to you.


Add PostgreSql server table

Describe the new table
Need to query the PostgreSql table to query and verify the CIS section 4.3 (PostgreSQL Database Server)
References
Section 4
We need to achieve some of the steps as per CIS recommendation
4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server (Automated)
4.3.2 Ensure 'Enforce SSL connection' is set to 'ENABLED' for MySQL Database Server (Automated)
4.3.3 Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.4 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.5 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.6 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.7 Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server (Automated)
4.3.8 Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled (Manual)
4.4 Ensure that Azure Active Directory Admin is configured (Automated)
4.5 Ensure SQL server's TDE protector is encrypted with Customer-managed key (Automated)

https://github.com/turbot/steampipe-plugin-azure/pull/64
This will unblock following CIS recommendations
Section 4

4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server (Automated)
4.3.3 Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.4 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.5 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.6 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server (Automated)
4.3.7 Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server (Automated)
4.3.8 Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled (Manual)

https://github.com/turbot/steampipe-plugin-azure/pull/66
This will unblock following CIS recommendations
Section 4

4.3.2 Ensure 'Enforce SSL connection' is set to 'ENABLED' for MySQL Database Server (Automated)

#67
This will unblock following CIS recommendations
Section 4
4.4 Ensure that Azure Active Directory Admin is configured (Automated)
4.5 Ensure SQL server's TDE protector is encrypted with Customer-managed key (Automated)

Ensure that Azure Active Directory Admin is configured (Automated)
select
  name,
  id
from
  azure_sql_server
where
  server_azure_ad_administrator is not null;

Ensure SQL server's TDE protector is encrypted with Customer-managed key (Automated)
select
  name,
  encryp ->> 'kind' as encryption_kind,
  encryp -> 'properties' ->> 'serverKeyType' as encryption_key_type,
  encryp -> 'properties' ->> 'uri' as key_uri
from
  azure_sql_server,
  jsonb_array_elements(encryption_protector) as encryp
where
  encryp ->> 'kind' = 'azurekeyvault'
  and encryp -> 'properties' ->> 'serverKeyType' = 'AzureKeyVault'
  and encryp -> 'properties' ->> 'uri' is not null;


Prevent draft posts from being federated when deleted

Fixes #1030.
Proposed changes:

Added status transition handling in schedule_post_activity() to prevent federation of draft posts.
Added test coverage for post status transitions.

Other information:

[x] Have you written new tests for your changes, if applicable?

Testing instructions:

Create a draft post
Create a published post
Select both posts in the admin list view
Bulk delete them
Verify that:

The published post sends a Delete activity to followers
The draft post is deleted without federation

We do not really know the state, a draft had before the delete. A post could have been published, migrated to a draft and then deleted. In this case we have to send a Delete.

migrated to a draft

Can you tell me more about that? Something that skips transition_post_status()?

@obenland if a post status is changed from "publish" to "draft", it will not deleted from the fediverse. If the user then deletes the draft, has the former status "draft" and will not be send a Delete to the fediverse.
In this case the fediverse will keep the draft post for ever.

That makes sense, thanks. Sounds like the switch to the federated check should cover that?

it will set when the post/comment will be federated, so I would assume yes :)


nixos/stirling-pdf: init module

Description of changes

Add a NixOS module for Stirling PDF.
It is derived from https://github.com/NixOS/nixpkgs/pull/305307 but with simplified options and updated dependencies.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1872

Hi, I've just seen this PR, I must admit that it feels very weird to have no attribution and no mention for what is essentially a direct copy of my work...
In the future I guess I will only publish modules under a restrictive license until they are merged in a version of nixpkgs

@Tom-Hubrecht Sorry for letting you feel uncomfortable about it. I thought you would be notified when I added a hyperlink to your PR as you should be able to see it your original PR as well. As suggested above, I should have added a Co-Author field. I'll keep that in mind in the future.


RFFT2

Hello, sorry for the maybe trivial question.
I don't understand how torch.fft.rfft2 works, it is clear that it performs the FFT on two dimensions of real function but i don't found how it is indexed. In particular in your code, for examples in \fourierflowmodules/zongyi_fno/grid_2d.py, you take the Fourier coefficients indexed for out_ft[:, :, :self.n_modes, :self.n_modes] and out_ft[:, :, -self.n_modes:, :self.n_modes]. Calling i the first index that you extract and j the second, so (if I understand well) you extract the first and the last n_nodes from the tensor out_ft. In the theory we have to extract all value of i, j such that |i| < n_modes and the same for j. For j using the Hermitian symmetry for real valued function in out_ft there is only positive value for j, so it is clear that the implementation extraction corresponds to the theory. Instead, is for me unclaear, if the implementation extraction of i correspond to the theory extraction. Refurmulating my question is unclear if the implementation extraction --> out_ft[:, :, :self.n_modes, :self.n_modes] and out_ft[:, :, -self.n_modes:, :self.n_modes] corresponds to the theory extraction --> |i| < n_modes. I don't found any information about that... so I ask you if you already think about that and if you find some information about this details of the torch.fft.rfft2 implementation.
Thank you in advance.
Best regards,
Massimiliano Ghiotto

Resolved, I think that it is due to the periodicity of the modes.


Add input and box tests

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[X] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[X] I accept that @willmcgugan may be pedantic in the code review.

Description
I have added test_box.py with additional box.py tests and I have added a basic test for console.input() in test_console.py for issue #37.
Unfortunately, the total coverage didn't change from 94% but hope it helps in the long run. Let me know if I should change anything. Thanks!

Every line counts, thanks!


JavaCompile ignores custom -sourcepath since 7.0

The -sourcepath specified in CompileOptions for a JavaCompile task seems to be ignored starting in Gradle 7.0.
Expected Behavior

Up to Gradle 6.9.1, the custom source path was passed to the compiler as expected.
Current Behavior

Starting with 7.0, the task fails with and running with debug logging enabled reveals that -sourcepath D:\GW2ToolBelt\GW2ML\src\main\java-jdk9 is used instead of -sourcepath D:\GW2ToolBelt\GW2ML\src\main\java;D:\GW2ToolBelt\GW2ML\src\main\java-jdk9.
Context

I ran into this issue while updating from Gradle 6.8.2 to 7.2 in a project that uses a custom compileJava9 task to compile a module descriptor for a multi-release jar:
val compileJava9 = create<JavaCompile>("compileJava9") {
    destinationDirectory.set(File(buildDir, "classes/java-jdk9/main"))

    val java9Source = fileTree("src/main/java-jdk9") {
        include("**/*.java")
    }

    source = java9Source
    options.sourcepath = files(sourceSets["main"].java.srcDirs) + files(java9Source.dir)

    classpath = files()

    options.release.set(9)

    afterEvaluate {
        options.compilerArgs.add("--module-path")
        options.compilerArgs.add(compileJava.get().classpath.asPath)
    }
}

The full project is available at https://github.com/GW2ToolBelt/GW2ML/tree/f7fa2104772345f249ad1d28199376aff7391545.
Steps to Reproduce

Clone https://github.com/GW2ToolBelt/GW2ML
Run gradlew compileJava9 --debug

Something like that should fix it:
+++ b/build.gradle.kts
@@ -65,12 +65,7 @@ tasks {
     val compileJava9 = create<JavaCompile>("compileJava9") {
         destinationDirectory.set(File(buildDir, "classes/java-jdk9/main"))

-        val java9Source = fileTree("src/main/java-jdk9") {
-            include("**/*.java")
-        }
-
-        source = java9Source
-        options.sourcepath = files(sourceSets["main"].java.srcDirs) + files(java9Source.dir)
+       source = (files(sourceSets["main"].java.srcDirs) + files("src/main/java-jdk9")).asFileTree

         classpath = files()

@TheMrMilchmann can you explain the use case, why you decided to use options.sourcepath and not source for JavaCompile? I would like to understand the use case and what is correct way of handling it.

I'm not sure if I recall all issues that factored into this decision but I do remember that there were several issues when using source. One important effect of specifying these files in options.sourcepath instead of source is that the compiled results include just the compilation results of the files present in the actual "Java 9"-specific sources. Additional required files are silently compiled by javac. (It is actually fairly tricky to track which source file a class belongs to which makes creating the actual archive non-trivial.)
Also, now that I'm reading the spec again, I think that the output could potentially reuse the compilation results from the "common" compilation if they were added to the classpath. This could be especially useful when working with larger projects that don't want to recompile everything just to build a handful of version-specific classes for MR jars. (I'll have to experiment some more once this issue is fixed.)

Fwiw, sourcepath is overwritten in JavaCompile#createSpec when building a module: https://github.com/gradle/gradle/blob/6cba9aaa19d95b050ea0a39399ca2a285f2d36f8/subprojects/language-java/src/main/java/org/gradle/api/tasks/compile/JavaCompile.java#L298-L300
So it looks like the "culprit" is the change of inferModulePath's default from false to true in Gradle 7.0, and indeed adding modularity.inferModulePath.set(false) to the task fixes the build.


Merge master into dev-1.21 - 2/26/21

Merge master into dev-1.21 to keep in sync - SIG-Release 1.21 Docs team 2/26/21
/cc @reylejano @mvortizr @tengqm @PI-Victor

Thank you for doing the branch sync
/lgtm

Thanks @ChandaniM123 .
/approve


Creating Dynamic Fields using  FormlyExtension events

use PanelWrapperComponent as a type and rely on FormlyExtension events: https://stackblitz.com/edit/angular-o29jy7-c48t1g?file=src/app/panel-wrapper.component.ts
Originally posted by @aitboudad in https://github.com/ngx-formly/ngx-formly/issue_comments/709649147
FormlyExtension events seem to fire even if a section is hidden using hideExpression. How can I populate fields only if the section is not hidden?
I want to add new form fields within an accordion after getting API data. So that means I need to update the FormGroup after the prePopulate function fires.
In the example below, I tried to mock an API call by using a setTimeout within an ngOnInit to mimic updating the field at a future time.
https://stackblitz.com/edit/angular-o29jy7-k18kwu?file=src%2Fapp%2Fpanel-wrapper.component.ts

I want to add new form fields within an accordion after getting API data. So that means I need to update the FormGroup after the prePopulate function fires.

Then you need to rebuild the form manually, that's possible but you may rely on an internal API (will be exposed in v6):
-- this.prePopulate(this.field);
++ (<any> this.options)._buildForm(true);

I see. I did notice this method but it was private.  I'm glad it will be exposed in the next version.  Thank you!

@aitboudad
In the StackBlitz of the OP an initialization of the fieldGroup in prePopulate was made. I remember doing this myself some time ago and noticed strange behaviour.
I adapted the SB: https://stackblitz.com/edit/angular-o29jy7-tzpbxr?file=src%2Fapp%2Fpanel-wrapper.component.ts
Doing an initialization in prePopulate, works, but the timeout update is not visable
Remove the initialization in prePopulate and the timeout update works
Why is it that when updating/initializing the fieldGroup in prePopulate further updates do not work?
What is allowed in prePopulate? What is strictly forbidden or better not be done in prePopulate?

@FritzHerbers prePopulate is called during the build step and its sync so using setTimeout inside prePopulate  may not work as expected. So in case, a timeout is needed, move the initialization part to ngOnInit and use the _buildForm call.
In the future, we may consider returning an observable from extension events.

@aitboudad
Maybe I was not clear in my comment.
The prePopulate in my SB is sync it initializes a formGroup. There is a timeout set in ngOninit(), which tries to update the formGroup.
When formGroup is set in prePopulate, the overwriting in the timeout section does not work, the form is not updated/visualized.
When there is no formGroup initialisation in prePopulate, the setting/updating of formGroup in the timeout section is working and visualized.
Why is it that when updating/initializing the fieldGroup in prePopulate further updates do not work?
What is allowed in prePopulate? What is strictly forbidden or better not be done in prePopulate?

Because when you call _buildForm the prePopulate will be called but not ngOnInit as the field is already rendered.


Use env variable names for GitHub related endpoints

linked to https://github.com/step-security/secure-workflows/issues/65


Remove IMASdd dependency

@adrianaghiozzi IMASdd seems to be imported but not used... am I wrong? Can we then remove it as a dependency?

Just removed it in this commit: https://github.com/ProjectTorreyPines/RABBIT.jl/commit/3a6f0321321cc222c9430edaf21112f76aa16716
Do I now need to change the version number in the Project.toml/do any other steps to make sure these changes are picked up in the registry?

you should be able to do
make register_patch repo=RABBIT

in the FUSE directory and that should take care of everything


Fix a11y issues

Instead of just disabling the nags, i just fixed the issues (except for the modal I couldn’t  quite decide how to do that).

todo
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/
https://youtu.be/JS68faEUduk?si=OWWDZug8qYJaHms-

Ready to merge tbh

Made some tweaks to retain some more of the design when not using accessibility features. Code in ShareModal doesn't seem to work, so I'm reverting that. Thanks for the PR!


Neighbor-based code

Could you please also provide neighbor-based (Item KNN) code in this repo ?

My implementation of itemKNN can be found in my another project:
https://github.com/hexiangnan/sigir16-eals/blob/master/src/algorithms/ItemKNN.java
On Tue, Aug 29, 2017 at 5:41 PM, ihong chen<EMAIL_ADDRESS>wrote:

Could you please also provide neighbor-based (Item KNN) code in this repo ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hexiangnan/neural_collaborative_filtering/issues/6,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGxjhNrsRQZNKYfbpI0k9OfxkqML_uIks5sc9zNgaJpZM4PFpLt
.

--
Best Regards,
Xiangnan He


Restructure multi-image examples to hide fastapi import

Type of Change

[ ] New example
[x] Example updates (Bug fixes, new features, etc.)
[ ] Other (changes to the codebase, but not to examples)

Follow-up to https://github.com/modal-labs/modal-examples/pull/951. A few examples were still failing with the 2024.10 Image Builder because they had multiple images and imported fastapi in global scope, so the imports failed when running on the images without it.

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-fd94655.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-6cf14d4.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-e170d02.modal.run

Confirmed that these all pass with the 2024.10 builder version

Dropping that commit now

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-1e390bd.modal.run


Some sites always return a hit

Great idea and Initiative! However some sites always seem to give a hit. I tried several times with random usernames, and these always pop up. I have no idea how to get around this nor fix it, that's something for far more clever and bright minds to do.
cat L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g.txt
############################# 11/10/2023, 08:22 AM #############################
https://www.facebook.com/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.khanacademy.org/profile/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://steamcommunity.com/id/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.ebay.com/usr/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://medium.com/@L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.instagram.com/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.codecademy.com/profiles/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.mixcloud.com/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://account.xbox.com/en-US/Profile?gamertag=L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://socialclub.rockstargames.com/member/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g
https://www.coursera.org/user/L2IPgt4fDIsTPpjPjn3Qf3LC4MrYQpOKK8ECCHScg7g

most of the false results are fixed now, but Facebook and Khan Academy sites are still prone to false positives


ci: use pnpm/action-setup

This should resolve the following error when running CI on Windows.
corepack enable
     |  ~~~~~~~~
     | The term 'corepack' is not recognized as a name of a cmdlet, function, script file, or executable program. Check
     | the spelling of the name, or if a path was included, verify that the path is correct and try again.

Closing as included elsewhere, thanks for all the help! ❤


400: "Bad Request" when Refreshing token

The plugin continually throws a 400: "Bad Request" error when refreshing token.
Log below:
[1/14/2023, 12:59:31 PM] [Miele@home] Refreshing token...
[1/14/2023, 12:59:32 PM] [Miele@home] Miele API request https://api.mcs3.miele.com/thirdparty/token failed with status 400: "Bad Request"
[1/14/2023, 1:29:31 PM] [Miele@home] Refreshing token...
[1/14/2023, 1:29:32 PM] [Miele@home] Miele API request https://api.mcs3.miele.com/thirdparty/token failed with status 400: "Bad Request"

I'm seeing the same thing.


How to hide default labels in grok

Hello All,
I want to hide default labels in Grok Exporter output.
My Output is:

WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:2002/console/login/LoginForm.jsp",instance="muclhp522:9968",job="grok"}	0
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3011/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	1
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3011/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	0
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3012/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	0
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3011/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	0
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3012/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	0
WLSRESTARTFLAG{exported_instance="https://<IP_ADDRESS>:3011/weblogicStatus/index.html",instance="muclhp522:9968",job="grok"}	0
I don't want the labels - instance and job in Prometheus output as this is causing difficulties in setting up alerts in alertmanager.
How can i hide them ? I don't want them to get printed.
Thanks
Priyotosh

I don't think these labels are generated by grok_exporter. To see the labels generated by grok_exporter, go to http://localhost:9144/metrics (or whatever you configured in the server section). If these labels are not there, they are added by another component, maybe by the Prometheus server itself.

Prometheus also provides a relabel configuration, which might help you. Look for relabeling here: https://prometheus.io/docs/prometheus/latest/configuration/configuration

The instance label is a special case, because it is generated by Prometheus after relabeling. As the documentation says:

After relabeling, the instance label is set to the value of __address__

A detailed explanation can be found on Brian's blog post "life of a label".
However, in most cases it should not be necessary to drop the instance label. You can probably use a PromQL query to get the results you want even if you keep the instance label in the metrics.


Improve docs re suffixed responders

[ ] Add an example to the suffix kwarg docstring for add_route()
[ ] Add a section about suffixed responders to the routing page

I can take this one if you still need someone to

That would be awesome @MinesJA !
Go ahead!

Just submitted. First time submitting so let me know if I'm missing anything. Thanks!