Investigate what happens in the Client when a note is created and consumed in the same transaction

While working on #617 I noticed a possible problem inside sync_state_once. I think that if a note is committed and consumed in the same block, the Client may not behave as we expect. Basically because the calls to committed_note_updates and consumed_note_updates will be using the same Expected note stored instead of applying the transformations sequentially.
We should look into this and add a test that checks this case. I think the MockChain is perfect for testing this, as we can easily construct a node state where this happens, instead of relying on subsequent transactions happening on the same block.

I think such scenarios shouldn't happen. The only way for a note to be created and consumed in the same block, is if if the note is an input into a transaction as an un-authenticated note. But such notes should be "erased" by the node. cc @Mirko-von-Leipzig in case I'm misstating something.

That is correct; though I don't quite understand the context. Does the client only generate authenticated notes?


DB connection not initiated in api/statistics/total.js for next.js.

Description
When user opens localhost:3000 of next.js version in index.js file have /api/statistics/totals url which is calling api/statistics/total.js and in this file db connection is not made due to which getting MongooseError: Operation stats.findOne() buffering timed out after 10000ms error.
Screenshots

Additional information
No response

Good spot, thank you 👍
Would you like to fix it or I can do it?

Please assign it to me I will fix it.

Sure, assigned to you 👍

Hi @eddiejaoude,
If @jasham not working on this issue. Can I pick this issue?

Hello @prajapati55 this issue is fixed please have a look https://github.com/EddieHubCommunity/LinkFree/pull/1615

Resolved in #1615

@jasham Thanks for informing.


[INSTALL][ubuntu Ubuntu 20.04 LTS] fiftyone.core.config.FiftyOneConfigError: MongoDB could not be installed on your system. Please define a database_uri in your fiftyone.core.config.FiftyOneConfig to connect to yourown MongoDB instance or cluster

System information

OS Platform and Distribution : Linux ubuntu Ubuntu 20.04 LTS

Python version (python --version): 3.8

FiftyOne version (fiftyone --version):

FiftyOne installed from (pip or source): pip

Commands to reproduce
first
pip install fiftyone

then
import fiftyone

or
fiftyone --version

Describe the problem
error message
Traceback (most recent call last):
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/odm/database.py", line 200, in establish_db_conn
    _db_service = fos.DatabaseService()
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/service.py", line 80, in __init__
    self.start()
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/service.py", line 209, in start
    super().start()
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/service.py", line 118, in start
    + self.command,
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/service.py", line 238, in command
    DatabaseService.find_mongod(),
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/service.py", line 286, in find_mongod
    raise ServiceExecutableNotFound("Could not find `mongod`")
fiftyone.core.service.ServiceExecutableNotFound: Could not find `mongod`

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "download.py", line 32, in <module>
    import fiftyone
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/__init__.py", line 25, in <module>
    from fiftyone.__public__ import *
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/__public__.py", line 16, in <module>
    _foo.establish_db_conn(config)
  File "/home/ubuntu/anaconda3/envs/pytorch1.12/lib/python3.8/site-packages/fiftyone/core/odm/database.py", line 206, in establish_db_conn
    raise FiftyOneConfigError(
fiftyone.core.config.FiftyOneConfigError: MongoDB could not be installed on your system. Please define a `database_uri` in your `fiftyone.core.config.FiftyOneConfig` to connect to yourown MongoDB instance or cluster

Other info/logs
already installed pymongo or fiftyone-db

Hi @lynshwoo2022. Can you share your /etc/os-release file? Ubuntu 20.04 should be supported.
cat /etc/os-release

Also, a workaround is to install fiftyone-db==0.4

thanks，i'll try fiftyone-db==0.4
ubuntu version：

fiftyone-db==0.4 works, confusing, why ubuntu20 is not supported by up-to-date version

ubuntu20 is supported. You may be working in a restricted network, which prevented the MongoDB download. The URL is found [here].(https://github.com/voxel51/fiftyone/blob/e53596a757ed202857f477b83300f4cc42c6101e/package/db/setup.py#L73)
fiftyone-db==0.4 does not require downloading on install, but limits support to only ubuntu20 and ubuntu18


Fix realised Maven module metadata not adding variants from rules

If there were no variants in the component metadata and no variants
were added by the derivation strategy, RealisedMavenModuleResolveMetadata
would ignore additional variants produced by component metadata rules.
This was inconsistent with the behavior of the default (lazy)
implementation.
Fix the inconsistency by adding the variants produced by the component
metadata rules during realization even if the variant's own variants
are empty.

Fixes https://github.com/gradle/gradle/issues/20145
⚠ Not safe to merge
Merging the fix right now would deteriorate the issue https://github.com/gradle/gradle/issues/20145 by spreading the manifestation from just dependencies resolved from local repositories to all dependencies. We need to figure out the timeframe for fixes in the Kotlin and/or AGP before we can safely merge the fix.

@bot-gradle test ReadyForRelease

OK, I've already triggered the following builds for you:

ReadyForRelease build

Merged via #28287


Fix RDoc deprecation warning

Fixes the following deprecation warning that appears when running e.g.
"rake -T":
rake/rdoctask is deprecated.  Use rdoc/task instead (in RDoc 2.4.2+)
Closes #2.

Hi there! We’re doing some open source maintenance work and closing old PRs. If you would still like this PR to be merged in, please re-open it by 2-weeks-from-today. Thanks!


[BUG] Opensearch version 1.2.4 fails  java.lang.IllegalArgumentException: indexCreatedVersionMajor is in the future: 9

Describe the bug
running opensearch 1.2.4 from docker-compose.yml file leads to error java.lang.IllegalArgumentException: indexCreatedVersionMajor is in the future: 9
To Reproduce
Steps to reproduce the behavior:

Just use docker compose up with docker-compose.yml

Expected behavior
openseach should be running without errors
Host/Environment (please complete the following information):

OS:  Windows 10 Entreprise & Rancher Desktop
Version:  Windows 10  & Rancher Desktop 1.6.2

Additional context
docker-compose.yml file :
version: "3.8"
services:
  opensearch-node:
    image: opensearchproject/opensearch:1.2.4
    container_name: opensearch-node
    environment:
      - cluster.name=opensearch-cluster
      - node.name=opensearch-node
      - discovery.seed_hosts=opensearch-node
      - cluster.initial_master_nodes=opensearch-node
      - bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m"
      - plugins.security.ssl.http.enabled=false
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
        hard: 65536
    volumes:
      - opensearch-data1:/usr/share/opensearch/data
    ports:
      - "<IP_ADDRESS>:${OPENSEARCH_NODE_PORT_HOST}:${OPENSEARCH_NODE_PORT_CONTAINER}"
      - "<IP_ADDRESS>:${OPENSEARCH_PERFORMANCE_ANALYZER_PORT_HOST}:${OPENSEARCH_PERFORMANCE_ANALYZER_PORT_CONTAINER}"
    networks:
      - pipeline-net

  opensearch-dashboards:
    image: opensearchproject/opensearch-dashboards:1.2.0
    container_name: opensearch-dashboards
    ports:
      - "<IP_ADDRESS>:${OPENSEARCH_DASHBOARD_PORT_HOST}:${OPENSEARCH_DASHBOARD_PORT_CONTAINER}"
    environment:
      OPENSEARCH_HOSTS: '["http://opensearch-node:${OPENSEARCH_NODE_PORT_CONTAINER}"]'
    networks:
      - pipeline-net

volumes:
  opensearch-data1:

networks:
  pipeline-net:

docker compose up logs :

opensearch-node        | [2023-01-31T09:00:15,428][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] Clustername: opensearch-cluster
opensearch-node        | [2023-01-31T09:00:15,433][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] Directory /usr/share/opensearch/config has insecure file permissions (should be 0700)
opensearch-node        | [2023-01-31T09:00:15,433][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] File /usr/share/opensearch/config/kirk-key.pem has insecure file permissions (should be 0600)
opensearch-node        | [2023-01-31T09:00:15,434][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] File /usr/share/opensearch/config/root-ca.pem has insecure file permissions (should be 0600)
opensearch-node        | [2023-01-31T09:00:15,434][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] File /usr/share/opensearch/config/kirk.pem has insecure file permissions (should be 0600)
opensearch-node        | [2023-01-31T09:00:15,434][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] File /usr/share/opensearch/config/esnode.pem has insecure file permissions (should be 0600)
opensearch-node        | [2023-01-31T09:00:15,434][WARN ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node] File /usr/share/opensearch/config/esnode-key.pem has insecure file permissions (should be 0600)
opensearch-node        | [2023-01-31T09:00:15,571][INFO ][o.o.p.c.PluginSettings   ] [opensearch-node] Config: metricsLocation: /dev/shm/performanceanalyzer/, metricsDeletionInterval: 1, httpsEnabled: false, cleanup-metrics-db-files: true, batch-metrics-retention-period-minutes: 7, rpc-port: 9650, webservice-port 9600
opensearch-node        | [2023-01-31T09:00:16,035][INFO ][o.o.i.r.ReindexPlugin    ] [opensearch-node] ReindexPlugin reloadSPI called
opensearch-node        | [2023-01-31T09:00:16,036][INFO ][o.o.i.r.ReindexPlugin    ] [opensearch-node] Unable to find any implementation for RemoteReindexExtension
opensearch-node        | [2023-01-31T09:00:16,051][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node] Loaded scheduler extension: opendistro-index-management, index: .opendistro-ism-config
opensearch-node        | [2023-01-31T09:00:16,055][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node] Loaded scheduler extension: opendistro_anomaly_detector, index: .opendistro-anomaly-detector-jobs
opensearch-node        | [2023-01-31T09:00:16,080][INFO ][o.o.j.JobSchedulerPlugin ] [opensearch-node] Loaded scheduler extension: reports-scheduler, index: .opendistro-reports-definitions
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [aggs-matrix-stats]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [analysis-common]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [geo]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [ingest-common]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [ingest-geoip]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [ingest-user-agent]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [lang-expression]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [lang-mustache]
opensearch-node        | [2023-01-31T09:00:16,083][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [lang-painless]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [mapper-extras]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [opensearch-dashboards]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [parent-join]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [percolator]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [rank-eval]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [reindex]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [repository-url]
opensearch-node        | [2023-01-31T09:00:16,084][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded module [transport-netty4]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-alerting]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-anomaly-detection]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-asynchronous-search]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-cross-cluster-replication]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-index-management]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-job-scheduler]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-knn]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-observability]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-performance-analyzer]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-reports-scheduler]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-security]
opensearch-node        | [2023-01-31T09:00:16,085][INFO ][o.o.p.PluginsService     ] [opensearch-node] loaded plugin [opensearch-sql]
opensearch-node        | [2023-01-31T09:00:16,118][DEPRECATION][o.o.d.c.s.Settings       ] [opensearch-node] [node.max_local_storage_nodes] setting was deprecated in OpenSearch and will be removed in a future release! See the breaking changes documentation for the next major version.
opensearch-node        | [2023-01-31T09:00:16,136][INFO ][o.o.e.NodeEnvironment    ] [opensearch-node] using [1] data paths, mounts [[/usr/share/opensearch/data (/dev/sdb)]], net usable_space [229.8gb], net total_space [250.9gb], types [ext4]
opensearch-node        | [2023-01-31T09:00:16,137][INFO ][o.o.e.NodeEnvironment    ] [opensearch-node] heap size [512mb], compressed ordinary object pointers [true]
opensearch-node        | [2023-01-31T09:00:16,179][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [opensearch-node] uncaught exception in thread [main]
opensearch-node        | org.opensearch.bootstrap.StartupException: java.lang.IllegalArgumentException: indexCreatedVersionMajor is in the future: 9
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) ~[opensearch-cli-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.cli.Command.main(Command.java:101) ~[opensearch-cli-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        | Caused by: java.lang.IllegalArgumentException: indexCreatedVersionMajor is in the future: 9
opensearch-node        |         at org.apache.lucene.index.SegmentInfos.<init>(SegmentInfos.java:169) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:327) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:64) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:61) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:720) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:84) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:64) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |         at org.opensearch.gateway.PersistedClusterStateService.nodeMetadata(PersistedClusterStateService.java:302) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:441) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.env.NodeEnvironment.<init>(NodeEnvironment.java:357) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.node.Node.<init>(Node.java:414) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.node.Node.<init>(Node.java:319) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:412) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |         ... 6 more
opensearch-node        |         Suppressed: org.apache.lucene.index.CorruptIndexException: checksum passed (df1bd64c). possibly transient resource issue, or a Lucene or JVM bug (resource=BufferedChecksumIndexInput(NIOFSIndexInput(path="/usr/share/opensearch/data/nodes/0/_state/segments_5")))
opensearch-node        |                 at org.apache.lucene.codecs.CodecUtil.checkFooter(CodecUtil.java:466) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:434) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:64) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:61) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:720) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:84) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:64) ~[lucene-core-8.10.1.jar:8.10.1 2f24e6a49d48a032df1f12e146612f59141727a9 - mayyasharipova - 2021-10-12 15:13:05]
opensearch-node        |                 at org.opensearch.gateway.PersistedClusterStateService.nodeMetadata(PersistedClusterStateService.java:302) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:441) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.env.NodeEnvironment.<init>(NodeEnvironment.java:357) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.node.Node.<init>(Node.java:414) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.node.Node.<init>(Node.java:319) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:412) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) ~[opensearch-cli-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.cli.Command.main(Command.java:101) ~[opensearch-cli-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        |                 at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101) ~[opensearch-1.2.4.jar:1.2.4]
opensearch-node        | uncaught exception in thread [main]
opensearch-node        | java.lang.IllegalArgumentException: indexCreatedVersionMajor is in the future: 9opensearch-node        |         at org.apache.lucene.index.SegmentInfos.<init>(SegmentInfos.java:169)
opensearch-node        |         at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:327)
opensearch-node        |         at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:291)
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:64)
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader$1.doBody(StandardDirectoryReader.java:61)
opensearch-node        |         at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:720)
opensearch-node        |         at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:84)
opensearch-node        |         at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:64)opensearch-node        |         at org.opensearch.gateway.PersistedClusterStateService.nodeMetadata(PersistedClusterStateService.java:302)
opensearch-node        |         at org.opensearch.env.NodeEnvironment.loadNodeMetadata(NodeEnvironment.java:441)
opensearch-node        |         at org.opensearch.env.NodeEnvironment.<init>(NodeEnvironment.java:357)
opensearch-node        |         at org.opensearch.node.Node.<init>(Node.java:414)
opensearch-node        |         at org.opensearch.node.Node.<init>(Node.java:319)
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242)
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242)
opensearch-node        |         at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:412)
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:178)
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:169)
opensearch-node        |         at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:100)
opensearch-node        |         at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)opensearch-node        |         at org.opensearch.cli.Command.main(Command.java:101)
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:135)
opensearch-node        |         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:101)
opensearch-node        | For complete error details, refer to the log at /usr/share/opensearch/logs/opensearch-cluster.log
opensearch-dashboards  | {"type":"log","@timestamp":"2023-01-31T09:00:17Z","tags":["error","opensearch","data"],"pid":1,"message":"[ConnectionError]: connect ECONNREFUSED <IP_ADDRESS>:9200"}

Yes I Created an index with opensearch 2.x but I deleted the docker image and container and cleaned the docker cache, and started the docker compose a second time with version 1.2.0

There is a way to reset the volume or remove this index ?

The Docker documentation should be able to help you. docker volume rm opensearch-data1 may well be what you need but please don't run that command if you have data you want to keep in that volume.

Closing this issue. Please reopen if you think there is a bug or issue in OpenSearch.


Tiling texture works on canvas when replacing textures

Tiling sprite should keep track of texture changes and update the fill pattern when using the canvas renderer
Fixes #4085

I thought i reviwed it already

You did, I was asked to do it on the dev branch instead of the master.

You did, I was asked to do it on the dev branch instead of the master.

Thanks again @robertbak for contributing!


Metadata initialization fails when member metadata includes its declaring type

Relates to Issue #3348:

When a program uses modules, all entities will be wrapped with require(["Module"], function(m) { .... } ); to resolve all dependencies first. The problem is that metadata must be initialized after entities are created. The require function changes normal flow of initialization and leads to errors.

The fix for #3348 helps when there are no members referring not initialized types. If such members exist, the issue is reproducible - it causes Bridge to add non-initialized namespace into a metadata class:
// ...
var $m = Bridge.setMetadata,
    $n = [System,Demo];      // Error: "Demo" is not defined
$m("Demo.App", function () { ... });
$m("Demo.Test", function () { ... });

Steps To Reproduce

Create a solution with 2 Bridge projects named Demo and PrinterModule.
Add the following lines to PrinterModule/App.cs to define a module:

using Bridge;
using System;

namespace PrinterModule
{
    [Module(ModuleType.AMD, "PrinterModule")]
    public class Printer
    {
        public void Print(string msg)
        {
            Console.WriteLine(msg);
        }
    }
}

Reference PrinterModule project from Demo project.
Add the following lines to Demo/App.cs

using PrinterModule;

namespace Demo
{
    public class App
    {
        public static void Main()
        {
            var test = new Test();
            test.PrintInfo();
        }
    }

    public class Test
    {
        // Comment the field below to make the issue disappear.
        public static Test Instance = new Test();

        public void PrintInfo()
        {
            var p = new Printer();
            var type = GetType();

            p.Print(type.FullName + " contains " + type.GetMethods().Length + " method(s).");
        }
    }
}

Rebuild the solution
Add require.js script to the generated HTML file in Demo project:

<!DOCTYPE html>

<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta charset="utf-8" />
    <title>Demo</title>

    <script src="bridge.js"></script>
    <script src="bridge.console.js"></script>
    <script src="bridge.meta.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.5/require.js"></script>
    <script src="PrinterModule.js"></script>
    <script src="Demo.js"></script>
    <script src="Demo.meta.js"></script>
</head>
<body>
</body>
</html>

Open that HTML file in browser.

Expected Result
No errors. Console output:
Demo.Test contains 1 method(s).

Actual Result
Console output:
Demo.Test contains 0 method(s).

2 Errors:
Uncaught ReferenceError: Demo is not defined
    at Demo.meta.js:6
    at Object.Bridge.assembly (bridge.js:3288)
    at Demo.meta.js:1

Uncaught TypeError: Cannot read property 'appendChild' of null
    at ctor.init (bridge.console.js:314)
    at new ctor (bridge.console.js:215)
    at Function.get [as instance] (bridge.console.js:22)
    at Function.logBase (bridge.console.js:90)
    at Function.error (bridge.console.js:122)
    at bridge.console.js:83

See also

https://github.com/Retyped/Retyped/issues/52#issuecomment-384375995

Fixed! Deck had to include changes in order to match the end-of-metadata string, but then all looks great!
The fix will make it to the next Bridge release.


Filter upcoming conference from past conferences overview

This PR adds a filter to the past.md template to show only events that have a past date-end in their header, removing future events.
It follows the approach described here: https://maedi.com/code/filter-by-date/
Fixes #178

@bwbohl Could you have a look?

Thanks for looking at that @bwbohl .
However, I can't reproduce your issue. When I run it locally, all the conferences are sorted chronologically:

Where do you get the twirked order?

however it happened when I ran it locally… let try this and see what happen online, agree?

Yes, agree :)

(PS: How do you run a PR locally? Is there anywhere a good explanation how to checkout a PR to test it?)

I use the GitHub Desktop App for this

(OK, thanks, found also a way without GH Desktop App: https://stackoverflow.com/a/30584951)

Feel free to merge this PR whenever you want

Thank you. :) Order is correct in my browser, for you, too?

yes correct here ;-) thanks for implementing!

Perfect, thanks.


⚠ Bofrost.de has degraded performance

In 3373010, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1440 ms

Resolved: Bofrost.de performance has improved in 0a6dbad.


Limit number of parallel formatting processes

Currently running conjure compilation freezes up the system completely. This seems to due to a combination of the number of processes that get run & internal tooling to monitor process syscalls. E.g. running ps aux | grep GoetheMain | wc -l takes a few minutes to run (returning numbers in the 200-400 range).
In one large internal project my computer ends up crashing after ~12 minutes before finishing compilation. The only solution right now is to use a JVM version before 16.
With this PR, the compilation finishes without issue and is still CPU-bound.

The problem is that there are unbounded callers into the format function, I don't think the library itself should be responsible for providing a limit. In the failing case we'd still be creating 200-400 threads waiting to launch the forked process, which I'd still consider a bug.
Secondly, the way this PR reduces the GoetheMain processes in the conjure-java example is fragile, and depends on a classloader being reused in a way that's not guaranteed, such that plugin changes may have spooky effects on projects that rely on the limit


refactor(kernels::grisubal): clean-up overlapping grid generation code

remove intremediate struct BBox2
encapsulate all code used to compute dimensions of the overlapping grid in a single function: compute_overlapping_grid
replace all (T, T) by [T; 2] to reflect the dimension of the map / geometry

Scope

[x] Code

Type of change

[x] Refactor

Codecov Report
Attention: Patch coverage is 0% with 53 lines in your changes missing coverage. Please review.

Project coverage is 74.39%. Comparing base (80fc822) to head (74214a7).

Files
Patch %
Lines

honeycomb-kernels/src/grisubal/model.rs
0.00%
38 Missing :warning:

honeycomb-kernels/src/grisubal/kernel.rs
0.00%
14 Missing :warning:

honeycomb-kernels/src/grisubal/mod.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #138      +/-   ##
==========================================
+ Coverage   74.35%   74.39%   +0.03%
==========================================
  Files          31       31
  Lines        3744     3742       -2
==========================================
  Hits         2784     2784
+ Misses        960      958       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


cratedb: init at 5.9.3

Closes #116533 after over 3 years (!)
Should probably also add a service module

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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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.

Note: I'm aware that version 5.9.5 has been released, but I don't really want to sit for 40+ minutes just to get the new hashes. Perhaps @r-ryantm would be so kind as to do that for me one day


GSE124395 - LiverCellAtlasHeterogeneity

Project short name:
LiverCellAtlasHeterogeneity
Primary Wrangler:
Ami
Secondary Wrangler:
Associated files

Google Drive:
https://docs.google.com/spreadsheets/d/1XwG0r35wRprCjAYl_TmRnDZgip9Pcro77ZEVb1hU0oU/edit#gid=2062586540

Published study links

Paper: https://www.nature.com/articles/s41586-019-1373-2

Accessioned data: GSE124395

Key Events

[ ] Convert published metadata to HCA spreadsheet
[ ] Manually curate dataset to meet HCA metadata standard
[ ] Collect any matrix and cell-type annotation files
[ ] Upload sheet to validate metadata
[ ] Check linking using ingest graph validator
[ ] Transfer raw files to ingest to validate data files
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

Need author information.

Obtained info from authors (Nadim Aizarani)

7706e2b2-4f83-48cf-bf4d-6814025a6787

Project:

Add as a supplementary link http://human-liver-cell-atlas.ie-freiburg.mpg.de/ as it includes interactive data exploration tools that might be useful for other researchers

Protocols

You could add this Publication DOI doi.org/10.21203/rs.2.9620/v1 to the following protocols, as it includes detailed information for all the steps performed in this paper

dissociation_protocol_liver
all the FACS protocols
library_preparation_protocol
sequencing_protocol

Analysis file

If the file GSE124395_celseq_barcodes.192.txt.gz contains cell barcodes, I would change the content description and ontologies to cell barcode (EFO:0010198). The current content description (sample ID) is defined as "Name or other identifier of an entry from a biosample database", whereas cell barcode is defined as "A short nucleotide sequence that is added during a single cell library preparation to identify reads from an individual cell."

Thanks @ipediez I have made these changes.

data files are syncing to ingest

submitted.

exported to hca dcp

R16 ReExport Successful

Looks fine in the browser


typo

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2574

Relevant Lines:
2600

💛  - Coveralls


Re-enable ANCM IIS Tests

After upgrading from the 2.2 to 3.0 SDK, we noticed that all IIS tests started failing (and probably many other people too due to 50 issues being created). The reason is https://github.com/aspnet/websdk/issues/422. There isn't a great way to work around this, especially for out of process as ANCM just runs whatever value is in the process path.

I will go through and close all RAAS issues once 3.0 passes.

Tracking https://github.com/aspnet/websdk/issues/422.
Once we get the websdk update, we'll re-enable the tests.

Tests are currently running.


Update CSLFT

Hello!
I am currently out of the office on vacation, thanks for
reaching out. I won't be able to review this matter until
Monday, September 18. If you need assistance, don't hesitate to
get in touch with Marcos Castillo.
Kind regards,
On Tue, 29 Aug 2023 12:09:45 -0700, Michael Johnson
@.***) wrote:

Merged #111 https://github.com/ytgov/sfa-client/pull/111 into
test.
—
Reply to this email directly, view it on GitHub
https://github.com/ytgov/sfa-client/pull/111#event-10224881880,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAPUYVM6VJZT7I577O6MKDXXY47RANCNFSM6AAAAAA3642T4I.
You are receiving this because you authored the thread.[image:
]Message ID:
@.***>


tf.train.import_meta_graph should be parallelized

Hey guys, I've been wondering whether it's possible the tf.train.import_meta_graph to be parallelized across multiple cores. When I load a complex model it takes too long and I only see one of my 24 cores being utilized to 100%.
Environment info
Operating System: CentOS
Installed version of CUDA and cuDNN:
Not applicable
Minimal example:
sess = tf.Session()
new_saver = tf.train.import_meta_graph('my-model.meta')
new_saver.restore(sess, tf.train.latest_checkpoint('./'))
all_vars = tf.get_collection('vars')
for v in all_vars:
    v_ = sess.run(v)
    print(v_)

Any plans on changing that in the near future?

When I see one core being utilized, my first suspicion is that work is done in Python. Python has chosen to remain in the punch-card age and only use 1 core for its processing, citing GIL issues. So the way to troubleshoot this is:
python -m cProfile -o slow.prof script.py
pip install snakeviz
snakeviz slow.prof

This may help you find a bottleneck, possibly something inefficient is being done in Python (I used this technique to speed up session.run from 120 usec to 60 usec by cutting out some unneeded Python calls). Longer term solution may be to rewrite metagraph loading in C++, someone from TF team may know if there are plans

@yaroslavvb thanks for the input. I'll definitely have a look into it.

PS, we also ran into MetaGraph slowness issue, we have to turn it off for reinforcement learning scripts -- https://github.com/openai/universe-starter-agent/blob/master/worker.py#L18

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Selectively Disabling Tab Clicks

The application that I'm developing will have three viewable panes/tabs.
When the system starts I want to start on Tab #1, with #2 & #3 disabled.
Then once criterion have been satisfied, I want to make #2 clickable as well.
Then a button within Tab #2 will move the view to Tab #3 and disable 1&2.
Is this possible? If so, could someone point me towards info/examples that demonstrate this?

There is no APi for it but  can do it with a little trick:
    lv_tabview_ext_t * tv_ext = lv_obj_get_ext_attr(tv1);
    char ** btnm_map = (char**)lv_btnm_get_map(tv_ext->btns);       /*Get the button matrix's descriptor*/
    btnm_map[1][0] |= LV_BTNM_INACTIVE_MASK;                        /*Make the 2th button inactive by modifying the control byte*/

Note that, still you will be able to slide to the inactive tab.
If it works well, you can add API for it if you want!

You can disable sliding with lv_tabview_set_sliding.
You can add tabs on the fly but there is no animations right now. What kind of animation do you imagine?

Thanks to your documentation online I did find and employ that function.
Tangent: I believe the Container website documentation has Enums that are incorrect. If my memory serves me I copied one out and it had an unnecessary "_contain" or something like that they I had to remove.
I tried the various themes to see how the tabs looked, but for some reason the Materials theme init wasn't being found, but all the others were. And they were enabled in the conf file. Have you encountered that before?
I was thinking something fairly simple. If it were an addition on the edge I'd add the tab and resize the tabs bar so nothing visibly changed. Then I'd resize the bar so it fit the screen eventually showing the new tab. Removal from the edge could be the reverse.
An alternative would just be to animate the width of the tab so it shifted between full with and 0 width. Just off the top of my head that's what I thought.

On Oct 5, 2018, at 01:10, Gabor Kiss-Vamosi<EMAIL_ADDRESS>wrote:
You can disable sliding with lv_tabview_set_sliding.
You can add tabs on the fly but there is no animations right now. What kind of animation do you imagine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Found problem and solution to above mentioned Materials theme issue. Filed #444

Hi,
I fixed the LAYOUT enum names. Thank you!
Animations:
The possibilities to animate the bar are limited because the bar is a Button matrix object and you can set only the ration between the width of the buttons on it. You can use numbers between [1..7] to set the relative width of the buttons so an animation on it would be quite stepped.
However, an animation on the content page's width sounds well!

When I went to compile the button disabling code, it wouldn't compile because:
lv_page_ext_t * tv_ext = lv_obj_get_ext_attr(tabview);
throws

error: invalid conversion from 'void*' to 'lv_page_ext_t*' [-fpermissive]
lv_page_ext_t * tv_ext = lv_obj_get_ext_attr(tabview);

This seems like it shouldn't be difficult to resolve, like by casting the type from void * to the other, but I haven't managed to reason out what it should be. If the solution is obvious to you, I could use the assistance :-)

Great! :)


Expand ~ in rust-analyzer.raLspServerPath

See https://github.com/rust-analyzer/rust-analyzer/issues/1423#issuecomment-504645478.

This should happen here: https://github.com/rust-analyzer/rust-analyzer/blob/7d79be32801036c39507fe96f87ed316e3934662/editors/code/src/server.ts#L23
I bet there's a nodejs function for this.

Ugh: https://stackoverflow.com/questions/21077670/expanding-resolving-in-node-js

A workaround could to be add PATH<EMAIL_ADDRESS>to ~/.pam_environment. It's a bit finicky, though: it seems to add it twice, and doesn't work with su -l. It works over SSH, though.


Typescript version advancement to 2.9.x

Bug, feature request, or proposal:
Feature
What is the expected behavior?
Angular updated it's typescript dependency from 2.7.x to 2.9.x yesterday with 6.0.9 release.
Is Angular Material following anytime soon?
What is the current behavior?
Typescript dependency locked to 2.7.x
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.0.9
Material 6.3.3

@IlCallo According to the Changelog, TypeScript 2.9 will come with Angular 6.1.0, which is now in RC0.
Angular 6.0.9 is still using TypeScript 2.7.

You're right, I didn't notice their master branch is for 6.1.x and not for 6.0.x.
Anyway I saw a PR has already be made for the version bump, that's great :)

@crisbeto Any news on this?

@jelbourn @crisbeto will the TypeScript 2.9 support land in a 6.x.x version? Or do we need to wait for version 7?

The TypeScript version will be bumped to 3.1 in 7.0.

@crisbeto thanks for the quick reply!


fix(curriculum): update descriptions and tests for business card lab

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56868

@ilenia-magoni updated PR.


Fix/namespace not exist

fix the #4854
when wen install a chart, we can set the namespace what used to store
the release, when the release is not exist, the other k8s resource will
be created. but the release will be created failed. and a check before
we install the chart.

Hey @jianliao82, sorry for not getting back to you sooner. The team has been focusing for the past few months on getting Helm 3 out the door, and that has meant it's been harder to find time to review feature additions for Helm 2.
Helm 2.15 is soon to be released, and will be the last feature release for Helm 2. Because of the time commitment required to rebase this and test it, we won't be able to find the time to review this. The good news is that this bug is no longer present in Helm 3 and no longer requires addressing.
Thanks!


Added examples for sentry:project:create action and unit tests.

Hey, I just made a Pull Request!

Added examples for sentry project creation scaffolder action. And added the tests for the action code.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Seems you'll want to rebase on a fresh master; some conflict crept in.

@freben I think is done now

@backstage-service does this PR should be merged?

The maintainers are off this week - we'll get back on the reviews soon!

@freben I think is done now

Could you please sync with the master once more 🙏🏻 ?

rudely rebased, let's see how it goes

Man I'm mystified by these build errors. I don't get them locally. Gonna have to get back to this later it seems.

alright one more try, rewriting the test to use msw2 😅

Sorry guys. I've been busy with work. I'll update when I have some time.

No worries, this seems to have been some REALLY weird msw problem that was env specific, not your fault. Seems to be about to go green now, I'll merge later on if it does


Add something like  to available pattern variables

Original:
https://twitter.com/anzwdev/status/978936415445798913

Will solve it by:

New default setting: objectNameShort
objectName is the original objectname.


Indication for upvoting posts

When clicking the upvote button, the button doesn't change. After a second you get a toast saying the upvote was successful.
Issue number 1 is there is no indication that this post is now upvoted.
Issue number 2 is when clicking the upvote button again, I expect to remove the upvote from the post. Like I am used to from a lot of other apps. But instead what happens is I get the same toast saying the upvote was successful.
Other than that the app is a joy to use. Thank you!

Well, I don't think this is technically possible.
This is because we use the API to retrieve the posts which doesn't include a flag on whether you liked it already.
We could of course store it just locally but it wouldn't be synced with the webpage or other clients you use.
A way to technically archive this is to not use the API but instead request the webpage and parse the HTML.
This also has it's own set of trait-ofs like, the App might break if the website gets an update (probably unlikely with HN). And maybe beeing slower.
Source: I implemented some improvements on the toasts and wanted to implement that feature too 😅

Yeah this issue is annoying and as you say @flofriday syncing is probably the biggest issue - here some background updating of liked posts or whatever seems like a lot of work for a small gain. The feature request is however totally reasonable.


There are many deprecated resources related to S3

Describe the Feature
There are a lot of warnings being generated by the module in version 0.82.5
Here's a partial example related to "aws_s3_bucket" resource

acl argument is deprecated, Use the aws_s3_bucket_acl resource instead
Use the aws_s3_bucket_versioning resource instead
cdn.logs/main.tf line 1, in resource "aws_s3_bucket" "default": Use the aws_s3_bucket_server_side_encryption_configuration resource instead

Basically there are deprecated arguments in the following modules/resources:

https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/0.82.5/main.tf#L325
https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/0.82.5/main.tf#L232

Expected Behavior
There's a way to replace the aws_s3_bucket resource (https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/0.82.5/main.tf#L232) with terraform-aws-s3-bucket module and with this specific tag (https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/tree/v3.0.1)
Also we'll need to implement something similar for https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/0.82.5/main.tf#L326
Use Case
Removing the warnings which are generated by the module
Describe Ideal Solution

Use terraform-aws-s3-bucket module  instead of the aws_s3_bucket resource and the same goes for logs module

Alternatives Considered
No response
Additional Context
No response

Agree, my problem is
resource "aws_s3_bucket" "origin"
Use the aws_s3_bucket_cors_configuration resource instead


Store Custom Actions per model

See the discussion on #212 .
It should be possible to store custom actions locally within a model, similar to how BPA rules can be stored locally.
In addition, when doing this, there should be an option to store the actions in a separate script file, to make source control easier.

just to clarify, each model custom action should have its own separate .cs script file

From a security pov, having custom actions automatically compiled upon model metadata load is not advised (malicious users could sneak in assembly code that is executed automatically once the code is compiled). Closing this.


server: support return simplified metrics and gzip compression

What is changed and how it works?

Issue Number: ref #12355
What's Changed:

Cherry pick #12356 #12417 #12671
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
None

/merge

/merge


Update dwsql-pipelines.yml

Why make this change?

updating it to not to source secrets from pipeline

What is this change?

removing dependence on pipeline variable

How was this tested?

running the pipeline

/azp run


Formatting of Generated Code is Ugly

Describe the bug
When generating code using 2.0.0-dev.28, the output of rust_ffi.g.dart is ugly with weird indentation. A example snippet:
@freezed
                 class CustomError with _$CustomError implements FrbException {
                     const factory CustomError.error0(  String field0,) = CustomError_Error0;
 const factory CustomError.error1(  int field0,) = CustomError_Error1;
                }

Steps to reproduce
Use flutter_rust_bridge_codegen = "=2.0.0-dev.28"  as a build dependency and generate for the following code:
pub enum CustomError {
    Error0(String),
    Error1(u32),
}

pub fn return_err_custom_error() -> Result<u32, CustomError> {
    Err(CustomError::Error1(3))
}

I generated using build.rs:
use lib_flutter_rust_bridge_codegen::codegen;
use lib_flutter_rust_bridge_codegen::codegen::Config;
use anyhow;

fn main() -> anyhow::Result<()> {
  // Tell Cargo that if the input Rust code changes, rerun this build script
  println!("cargo:rerun-if-changed=src/api");

  codegen::generate(
    Config::from_config_file("./flutter_rust_bridge.yaml")?.unwrap(),
    Default::default(),
  )

}

Configuration is uncomplicated:
rust_input: src/api/**/*.rs
dart_output: ../libtest/lib/src/rust_bindings/
local: true

Logs
Cannot do right now sorry. Probably doesn't matter.

Expected behavior
No response
Generated binding code
No response
OS
Linux Debian 12
Version of flutter_rust_bridge_codegen
2.0.0-dev.28
Flutter info
No response
Version of clang++
No response
Additional context
No response

Hi, could you please paste the full codegen logs? (I suspect there may be some warnings) In addition, if you use command line instead of build.rs, does this problem still occurs?

I ran with cargo build and when I generated into an empty directory, there are no warnings and curiously no rust_ffi.g.dart generated. The generated files are OK:
        ▾ api/
            main.dart
            main.freezed.dart
          frb_generated.dart
          frb_generated.io.dart
          frb_generated.web.dart

I tried generating into the previous v1 directory again and rust_ffi.g.dart wasn't changed this time, so I don't know how that got corrupted previously. I suppose it's prudent to ask people to remove all v1 generated files before running v2.

No issue using flutter_rust_bridge_codegen generate either, so not sure what happened before.

I suppose it's prudent to ask people to remove all v1 generated files before running v2.

Looks reasonable! Feel free to PR to modify https://cjycode.com/flutter_rust_bridge/guides/miscellaneous/upgrade/v2


Overhaul GValue bindings

Here's the best compromise between type safety and ergonomics I've managed to achieve.
cc #73
Examples:
    let mut value = glib::Value::from(Some("Hello world !"));
    println!("gvalue.get example: {}", value.typed::<String>().unwrap().get().unwrap());

    let mut int = glib::Value::from(1);
    int.typed_mut::<i32>().unwrap().set_some(&2);
    assert_eq!(int.get(), Some(2));

    for i in 0..10 {
        let iter = right_store.append(None);
        right_store.set_value(&iter, 0, &i.into());
    }

Supporting gtk update: https://github.com/gkoz/gtk-rs-gtk/tree/value

Missing re-exported value I guess.

I think it's done now. Can't easily run cargo test in travis because of older glib and g_type_init issue but added to appveyor.

All right. It's the pthread linking errors again. I guess I'll remove the CI changes from this PR.

Writing the docs made me realize that borrowing the value to get TypedValue might not be the best idea. Instead Value could be converted to TypedValue, which would deref to Value.

Now TypedValue contains Value and derefs to it.


Provide a basic configurability modal

The first version of the configurability should contain the following:

A gear wheel icon.
A way to provide high contrast colors to help colorblind people. This should be applied uniformly to all the screens (solved shabdak, help modal etc.)

Remember that this only the first version. We'll look at the local storage saving separately.

We will also make the number of letters of a word configurable.


The way to select particular features from CSV file

Hi,
I'm new to ML stuff but decided to start with your library.
I have a question:
Given this dataset: https://archive.ics.uci.edu/ml/datasets/student+performance
I'm trying to make a linear regression to predict grade (G3) for students based on several features from this dataset.
I want to use to the following features: G1, G2, studytime, failures, absences.
How I can define which columns of the csv file need to use as features for dataset?
It seems to me the CSVLoader treats all columns which are not response names as features.
This leads to the exception because it's trying to convert all features to double:
Exception in thread "main" java.lang.NumberFormatException: For input string: "course"
	at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2043)
	at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110)

I've seen examples on python with Pandas library where you can pick the columns for features and another column for result.
Is it possible to do kind of like that with Tribuo?

Yep, but to process csvs where you don't want to use all the columns then you need to use RowProcessor rather than the simple CSVLoader. If you instantiate a CSVDataSource you can pass it a RowProcessor instance which controls how columnar data is parsed. The RowProcessor accepts a fieldProcessorMap which gives the mapping between feature fields and the processor used to convert the String in that field into a list of Tribuo features, and a ResponseProcessor which you can use to pick the response column. The RowProcessor is very flexible so there are lots of other parameters but that should be sufficient to get you going.

Great, this is very clear. I appreciate it.

I'll add docs to the RowProcessor constructors in the docs pass this week.

Hi @Craigacp - I'm in the same boat, trying to get started with Tribuo and some basic CSV files with non-double Feature values. I've been working my way through the library but it would be great to have some code samples using RowProcessor etc. - had a quick look in the docs and tests but couldn't see anything obvious. Are there plans to build out the docs or have I just missed something?

I'm writing a tutorial on the RowProcessor at the moment, it should land in a public branch sometime early next week.


Upgrade dialog choose any course run

What are the relevant tickets?
Fix https://github.com/mitodl/hq/issues/3671 and partially https://github.com/mitodl/hq/issues/3109
Description (What does it do?)
Changes the enroll now button to open the dialog whever there is more then one course run available for enrollment.
In the dialog the dropdown select course run shows all enrollable course runs.
If the course is upgradable then:

the button to enroll is enabled
the course run has a label (can upgrade)
The payment info is displayed.

Screenshots (if appropriate):

How can this be tested?
There are few scenarios to test:

All course runs for a given course don't have products but are enrollable
One course run has product and other not, but both are enrollable
two course runs both have products both are enrollable, but only one is upgradable (meaning payment_deadline is in the future)
Has one enrollable course run with no product
Has one enrollable and upgradable run
has two runs both self paced and enrollable ( and upgradable?)

If we want to have the select, not having something selected by default it would look something like this:

We could try to add a default "nothing selected" option. And then we would need to disalbe all the buttons in the dialog:

@annagav this works for me, but I'd like to tweak the "nothing selected" text to be something based on best practices.
@mbilalmughal can you weigh in on this?
Some context: customer support has brought up that we get a number of tickets from learners who enroll without realizing what course dates they are signing up for. CS would like to cut down on these tickets and they have suggested that we not provide a default course run in situations when there are multiple runs like this. Learners would be required to make an active choice between the runs.
In the past, I had been reluctant to make this change, since it adds friction to the enrollment process, but now that I've seen the frustration it is causing customer support, I'm willing to try something like this.

I think this will address https://github.com/mitodl/hq/issues/3400 as well.

@mbilalmughal Thanks for the feedback. The only thing is that when the run is not selected we can't show the price and certificate availability info since it depends on the run selected. So it would look a bit different on my screenshots.

Perhaps just make the date field required ?
I don't think users will understand "can upgrade". What is that supposed to do ?

Perhaps just make the date field required ?
I don't think users will understand "can upgrade". What is that supposed to do ?

We are trying to mark courses that could be upgraded for a certificate track. What wording do you think would be better?

Instead of marking the ones that can be upgraded with (can upgrade), we can mark the ones that can't be upgraded with (no certificate available) -- which matches the text in the info box when there is no certificate.

For the same course, you can upgrade for some runs but other runs ? I did't know that was the case

This shouldn't happen, but we've had edge cases where the course team has left enrollment open in one of the runs after the course upgrade deadline. This is what happened with https://github.com/mitodl/hq/issues/3671

Latest screenshots:

@pdpinch @mbilalmughal could you review the latest screenshots?

@collinpreston this is ready for review now.

@pdpinch just my opinion, but feels a bit confusing to have the disabled "Enroll and pay" button.  I don't think it's natural to identify that the "Enroll for free" link is what should be clicked on.

I don't think it's natural to identify that the "Enroll for free" link is what should be clicked on when a course does not offer an upgraded enrollment.

What are our options?
@mbilalmughal what do you think?

I don't think it's natural to identify that the "Enroll for free" link is what should be clicked on when a course does not offer an upgraded enrollment.

What are our options?
@mbilalmughal what do you think?

I agree with @collinpreston. It doesn't make sense to disable it.
@pdpinch if you remember, we added the disabled button state just to ensure the user selects the date first. Nothing else is required. If you are okay with it, let's remove the disabled button state.

@collinpreston If there is no upgradable run the dialog should look like this:

We could remove the "without certificate" part.

@collinpreston I updated the description with test scenarios and corresponding pictures.


Query param to exclude a source

Problem

As the number of sources in Openverse grows, it may prove beneficial to API users and the frontend to be able to exclude sources, as opposed to limiting results by a list of included sources.
A primary use case I see for this is to omit Flickr, if one doesn't want to see content that can vary greatly in quality, as opposed to the other, more consistent platforms.

I'm curious about learning how our ES integration works so I'd like to poke around on this one if that's okay!

@sarayourfriend I'm so sorry I didn't see your comment here! Feel free to push your work on top of this PR or make a new one so that we can compare approaches.


fix: add confirm password to account create

fixes #6

:tada: This PR is included in version 1.1.10 :tada:
The release is available on:

1.1.10
GitHub release
1.1.10

Your semantic-release bot :package::rocket:


Refs #33497 -- Added connection pool support for PostgreSQL.

@apollo13 has done all the hard work in this PR: https://github.com/django/django/pull/16881 hoping to push it over the line.
Also hope the tests are testing the right thing, tried to take inspiration from psycopg_pool tests: https://github.com/psycopg/psycopg/blob/52ed68a9d699c1e43e07a4d04441534197552de5/tests/pool/test_pool.py#L103
But let me know what I'm missing - very new space for me 👍
Related ticket: https://code.djangoproject.com/ticket/33497

Lovely, thank you for picking up my work.

Fwiw, while it is nice if the test suite runs with a pool enabled I don't think it is a requirement to get this merged. The test suite is rather special after all. Nevertheless it might also show us bugs in the implementation.
On Wed, Dec 13, 2023, at 22:26, Sarah Boyce wrote:

@.**** commented on this pull request.
In tests/backends/postgresql/tests.py
https://github.com/django/django/pull/17594#discussion_r1425902114:

@@ -223,6 +223,82 @@ def test_connect_non_autocommit(self):
finally:
new_connection.close()

@unittest.skipUnless(is_psycopg3, "psycopg3 specific test")
def test_connect_pool(self):

   from psycopg_pool import PoolTimeout

   new_connection = connection.copy()

   self.assertIsNone(new_connection.pool)

   new_connection.settings_dict["OPTIONS"]["pool"] = {

       "min_size": 2,

       "timeout": 0.1,

   }

   new_connection._connection_pools = {}

I investigated and cache.tests.DBCacheWithTimeZoneTests was failing
because it was running createcachetable management command on test
setUp (which then creates a database connection in the pool). If I add
similar logic to _close_all_connections which I am running on on the
test database cloning/creating methods, then this all passes.
I think these issues are more around test state clean up which I guess
I'm still trying to figure out.
I can add tests around the timezone setting so I don't remove the logic again 😁
—
Reply to this email directly, view it on GitHub
https://github.com/django/django/pull/17594#discussion_r1425902114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAT5C3RKLYVTNGHM6G6C2TYJIMRLAVCNFSM6AAAAABAPRHCS6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOOBQGUYTOMJRGY.
You are receiving this because you were mentioned.Message ID:
@.***>

@apollo13a fait tout le travail acharné dans ce PR : #16881 dans l'espoir de le faire franchir la ligne.
J'espère également que les tests testent la bonne chose, j'ai essayé de m'inspirer des psycopg_pooltests : https://github.com/psycopg/psycopg/blob/52ed68a9d699c1e43e07a4d04441534197552de5/tests/pool/test_pool.py#L103
Mais faites-moi savoir ce qui me manque - un tout nouvel espace pour moi 👍
Billet associé : https://code.djangoproject.com/ticket/33497

really glad to see that y can continue where x left off

I tried to run our test suite with "pool": True with no luck :disappointed: :
FAILED (failures=103, errors=14, skipped=506, expected failures=7)

Also, it crashes when destroying test databases:
$./runtests.py backends
....
FAILED (failures=7, errors=2, skipped=82)
Destroying test database for alias 'default'...
Destroying test database for alias 'default'...
discarding closed connection: <psycopg.Connection [BAD] at 0x7fdc8b99dff0>
Traceback (most recent call last):
  File "django/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
  File "python3.10/site-packages/psycopg/cursor.py", line 737, in execute
    raise ex.with_traceback(None)
psycopg.OperationalError: consuming input failed: decryption failed or bad record mac

The backend postgres tests are not designed to pass with a pool as they for example check that there is no pool and change the settings. The test cleanup would also not work as it's relying on the tests being ran not as a pool.
Were your test failures mostly timezone tests (if you ignore the backend tests)?

FAILED (failures=102, errors=13, skipped=380, expected failures=7)

I have basically the same. I can try to rewrite the backend tests that they would pass with the change of underlying settings (but might be quite a lot of test changes).
This 80f11f5ec3938bad12a97b6be447fb65ca63ef7b toke care of the timezone tests but then I was warned that getting the test suite to pass with a connection pool might not be what we should aim for. So I don't really know if I should continue with it 🤔
@felixxm what do you think?

The backend postgres tests are not designed to pass with a pool as they for example check that there is no pool and change the settings.

As for me this is unexpected :thinking: Cannot we adjust them to work? by using a connection copy and changing OPTIONS.

I have basically the same. I can try to rewrite the backend tests that they would pass with the change of underlying settings (but might be quite a lot of test changes). This 80f11f5 toke care of the timezone tests but then I was warned that getting the test suite to pass with a connection pool might not be what we should aim for. So I don't really know if I should continue with it 🤔 @felixxm what do you think?

Not sure what the plan was, but are we going to document that users cannot test their apps when connection pooling is enabled? They can encounter the same issues.
Some failures are really suspicious, e.g. backends.tests.BackendTestCase.test_is_usable_after_database_disconnects:
  File "/django/tests/backends/tests.py", line 486, in test_is_usable_after_database_disconnects
    self.assertFalse(connection.is_usable())
AssertionError: True is not false

Why connection is usable after _close()? Maybe I'm missing something.

Ah that is because the connection isn't closed on close but only returned to the pool. I guess we really have to set self.connection to None afterwards since we no longer own it and adjust the remaining code to handle None there then (eg in is_usable)

So, I had some time and managed to get the testsuite passing with pooling enabled. During that I discovered one bug in the implementation that we should discuss (see below). I opened a PR against this PR, see https://github.com/sarahboyce/django/pull/10 for the details.
The code looks clean imo but there are a few things that might need some improving (note that by default the whole testsuite does not run under pooling, so the issues don't show up and even when they show up, this is basically Django testing transaction behavior. Endusers will probably never see that).
I am getting:

rolling back returned connection: <psycopg.Connection [INTRANS] (user=florian database=test_django_test_1) at 0x7f61920c5690>

for the following two tests:

test_hooks_cleared_on_reconnect
test_atomic_prevents_queries_in_broken_transaction_after_client_close

Both tests explicitly close the connection (and as such return it to the pool) while a transaction is active. So the warning is expected and the only thing I can think of is using filterwarnings to filter out those pgpool warnings here. But as said above I don't think this is necessary since that is not a default configuration we run the tests against.
I had the same warning for test_skip_class_unless_db_feature but I was able to fix it via https://github.com/sarahboyce/django/pull/10/commits/962566c4b62ef48fbdae1cb2ff75ed69147d186c -- this wouldn't hurt in current main either, @felixxm do you want an extra cleanup PR for that one or can we just keep it as extra commit in this PR?
test_atomic_prevents_queries_in_broken_transaction_after_client_close exposed one bug. Because we set connection = None in _close after we returned the connection to the pool (to ensure we do not use it…), we were able to reopen a connection inside an atomic. Essentially this means that
        with transaction.atomic():
            Reporter.objects.create(first_name="Archibald", last_name="Haddock")
            connection.close()
            # The connection is closed and the transaction is marked as
            # needing rollback. This will raise an InterfaceError on databases
            # that refuse to create cursors on closed connections (PostgreSQL)
            # and a TransactionManagementError on other databases.
            with self.assertRaises(Error):
                Reporter.objects.create(first_name="Cuthbert", last_name="Calculus")

no longer raises. Without pooling self.connection is not None and as such opening a new cursor raises. I was able to fix this in ensure_connection by adding:
        if self.in_atomic_block and self.closed_in_transaction:
            raise ProgrammingError("Cannot open a new connection in an atomic block.")

Basically use the existing hints to determine if we closed inside a transaction and error out. I am wondering if it would make sense to move this solely into the postgres backend. In the end though the check is not wrong but instead of relying on the database adapter to throw errors for closed connections we error out realy -- sounds okay?
I had to rewrite a few postgres tests to use a non-pooling connection because the pool doesn't tolerate changes to the settings dict like presented (see https://github.com/sarahboyce/django/pull/10/commits/bbd5c5db2c3523b1e0b02e3242ae5c1aa5d2c34d for details). There might be some ways to rewrite them in a pooling way, this way we can reuse the existing tests to test whether timezones & assume_role work instead of adding new ones. I don't have strong feeling either way though.
I will do some manual testing against a simple app, but so far so good.
One thing left on the todo: Incorporate health checking directly into the pool (supported as of 2.0)

Btw we should probably create a new ticket for this so we have something to mark as "ready to review"? :D

I had the same warning for test_skip_class_unless_db_feature but I was able to fix it via sarahboyce@962566c -- this wouldn't hurt in current main either, @felixxm do you want an extra cleanup PR for that one or can we just keep it as extra commit in this PR?

Merged in 6e520d953773d25a3d3484db67feed446aca0bc1.

Thanks for all the work on this! Is there any update on when it will be merged in and included in a Django Release?

No, we don't give any ETAs since we are doing this in our free time. If you want to get this in faster, please test it and review the code.
On Wed, Jan 31, 2024, at 16:45, Rohan Challa wrote:

Thanks for all the work on this! Is there any update on when it will be
merged in and included in a Django Release?
—
Reply to this email directly, view it on GitHub
https://github.com/django/django/pull/17594#issuecomment-1919375167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAT5C7FYRA6EPESGIZFDOTYRJRKHAVCNFSM6AAAAABAPRHCS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJZGM3TKMJWG4.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm finding this does the trick to limit PG connections when running under ASGI (in that not every request grabs a new connection). Awesome work; much less complicated than pg_bouncer for most needs
Here's my test repo using the patch branch if anyone wants to extend: https://github.com/gerardrbentley/demo-django

Hi!
First of all, thanks for all the work that's being done on this.
I'm looking to use this thread pool in the future, in combination with gevent. After some local testing, I found out the current solution opens a new threadpool on every new request, which for my use case is the same as using persistent connections.
Is this something that can/will be considered in the requirements? Is this threadpool even something that can be used with gevent in the first place?
Thank you :pray:

As far as I know Django doesn't support gevent officially. So no, this is not something I would consider, I have no idea how gevent works. That said if the existing thread locals do work, I am kinda surprised since I am not doing anything magic (I think).

@yorickr

I'm looking to use this thread pool in the future, in combination with gevent. After some local testing, I found out the current solution opens a new threadpool on every new request, which for my use case is the same as using persistent connections.

I think gevent should work without any problem (and correctly) with this implementation, can you provide a way to reproduce what you're seeing?

I started working on this patch .... :construction:

Fair enough:)
On Thu, Feb 22, 2024, at 15:31, Mariusz Felisiak wrote:

@.**** commented on this pull request.
In django/db/backends/postgresql/base.py
https://github.com/django/django/pull/17594#discussion_r1499337320:

@@ -256,7 +255,9 @@ def get_database_version(self):
def get_connection_params(self):
settings_dict = self.settings_dict
# None may be used to connect to the default 'postgres' db

   if settings_dict["NAME"] == "" and not

settings_dict["OPTIONS"].get("service"):

   if settings_dict["NAME"] == "" and not

settings_dict.get("OPTIONS", {}).get(
Sure, maybe it's not needed. However, it has nothing to do with
connection pooling, so we should merge it as a separate cleanup.
—
Reply to this email directly, view it on GitHub
https://github.com/django/django/pull/17594#discussion_r1499337320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAT5C6BXZ6YMBD6SZ5VKGDYU5JCLAVCNFSM6AAAAABAPRHCS6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQOJWGAYDMMJXGE.
You are receiving this because you were mentioned.Message ID:
@.***>

Superseded by #17914.


Add-DbaAgReplica - Fix bug when endpoint is created

Type of Change

[x] Bug fix (non-breaking change, fixes # )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Unit test is included
[ ] Documentation
[ ] Build system

If endpoint is created, the variable $epUrl was not set.

Hi @potatoqualitee - Cross Platform Import does not finish. Can you have a look?

Ok, works now.

Reasonable solution, thank you, Andreas! 👌🏼


Can items be deleted?

Hi,
Is there a way to delete items?  Like if we accidentally type in too many of an item (like 200k+), is there a way in the program to delete them? ie: if we enter -9999 and inject, will this remove it?
Or is there another way?  Thanks

Sell them. The client app has a sell tab.

Thanks Shal!  I tried to use, but when I enter in a number; ie:  if i specify 200000 for the 10+1 tickets, the program always crashes

ooh nvm.  please ignore.  I figured it out.  Thank you Shal!


Update build-openblas.sh

Updating openBLAS to a newer version helps with the issue of not detecting some hardware (at least on my new laptop). I'm running with this on my Ubuntu laptop and everything seems to be okay.

@pcagas I tried building in this branch on Perlmutter by

removing my old gkylsoft/OpenBlas* directories
running the mkdeps machine file
running the configure machine file
doing make -j 32 install

and I encountered this error:
zero/mat.c:18:11: fatal error: cblas.h: No such file or directory
   18 | # include <cblas.h>
      |           ^~~~~~~~~
compilation terminated.
make: *** [Makefile:131: cuda-build/zero/mat.c.o] Error 1
make: *** Waiting for unfinished jobs....

When you did this, did you try this with a clean or new gkylsoft and/or build/cuda-build?

I see the problem. When downloading OpenBLAS on Perlmutter with
curl -L https://github.com/xianyi/OpenBLAS/releases/download/v0.3.15/OpenBLAS-0.3.23.tar.gz > OpenBLAS-0.3.23.tar.gz

it produces the file OpenBLAS-0.3.23.tar.gz, but the next step
gunzip -f OpenBLAS-0.3.23.tar.gz

yields
gzip: OpenBLAS-0.3.23.tar.gz: not in gzip format

I don't know how to fix this yet.

i see, there's an error in the curl command, it still has 3.15 in it. I'll fix and try it.

@manauref oh, that is embarrassing, my bad!

To answer the question, yes, it was a clear install. I couldn't install gkyl at all before changing the openBLAS version.


doesn't work on macox

Like this~

+1

Sorry, this only supports Window's APIs to handle windows transparency, since Sublime Text uses its own window manager for unix/linux OSes, so I can't make it transparent on those operating systems, and sublime programmers are not going to implement that feature AFAIK, at least in the near future.
Maybe you should try Afloat


Parameter arrays for faster executemany()

Fix for https://github.com/mkleehammer/pyodbc/issues/120 using parameter arrays.
This feature defaults to off (using the existing execute()-in-a-loop) but may be enabled by setting Cursor.fast_executemany = True.

Also relates to #62


Fixed minor bug in README sample

Summary
Updated the code for initial state as described by issue #225
Details and comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Music

****
https://g.dev/ferg83
€ Hello Kyle83420;

````

> - [ ] - - # @Kyle83420 ~~````

````~~![Screenshot_20230807_094541_Wikipedia.jpg](https://github.com/Kyle83420/fantastic-adventure/assets/124255786/ec05018b-dcca-4d93-a3a4-04dd5a7ef51b)

Any pointers on how to run the tool correctly much appreciated;


Translate attributes

Re-opening this issue, PR #106 only added support in the frontend exporter, not in the engine.


[transactional-test] Add missing API function (#82)_41

Motivation
Add missing API function (https://github.com/move-language/move/pull/82)
Have you read the Contributing Guidelines on pull requests?
Yes

/canary

:sunny: Canary successful

/land


Vulnerability warnings (Container Registry vulnerability scanning)

I just pushed the 2.16.2 docker image to our Google Cloud Container Registry and it reported 61 vulnerabilities.
High | 7.1 | — | glibc | CVE-2019-25013
Medium | 4.6 | — | systemd | CVE-2019-3844
Medium | 4.6 | — | systemd | CVE-2019-3843
Medium | 5 | — | pcre3 | CVE-2020-14155
Medium | 5.9 | — | glibc | CVE-2020-1751
Medium | 5 | — | libidn2 | CVE-2019-12290
Medium | 5 | — | glibc | CVE-2021-3326
Medium | 6.4 | — | libbsd | CVE-2019-20367
Medium | 4.3 | — | libgcrypt20 | CVE-2019-12904
Medium | 6.8 | — | gcc-8 | CVE-2018-12886

(The number in the second column is CVSS score.)
I did not assess the critically of any of the issues, they might not affect anything at all. I thought I share it with you, though.

Hey Peter,
Thanks for sharing! I'd not worry much about the vulnerabilities you listed:

GLib: imgproxy uses the latest version built from the source. However, the system version of it is included in the image, that's why the scanner reports CVE. But, again, imgproxy doesn't use the system version.
"gcc-8": it doesn't look like this CVE can be used in the container. Also, there's no Go base image with a newer GCC, so it looks like this can be quickfixed. Anyway, it's ARM-only.
All other listed libs are not used by imgproxy. You can check this with ldd.

@DarthSim looking at the same issue (security scanner tagging issues), it seems there's a bunch of them in the latest version of the image. Is the image not meant to be used for production deploys?
Namely, I can see a bunch of tools I didn't expect to see in a production-ready image, especially considering Imgproxy is a static binary. For example, perl, tar, gpg, these are all present in the image, but I don't really see why. Is the binary doing exec() on them in some way? Is the image maybe meant for development only and not recommended for production deployments? Thanks.

Our Docker image is absolutely ready for production and is used by tons of companies of different scales in production.
If you take a look at the found vulnerabilities, you'll find that all of them don't have fixes at the moment. We update all the packages on every build, and we use the latest available versions of all the libraries we build from the source, so when fixed versions are available, we'll upgrade to them.
Also, all the vulnerabilities but one is low severity. The only medium-severity vulnerability is found in a Go package. Unfortunately, scanners that don't work with source code can't determine if the vulnerable code is actually used. And imgproxy doesn't use the vulnerable code from aws-sdk-go/service/s3/s3crypto exactly because it is vulnerable.
imgproxy's Docker image is based on the official Debian image which contains some stuff that imgproxy doesn't actually use. Yet this stuff is needed for things like a package manager. We could probably build a "clean" image that wouldn't contain anything but imgproxy itself and its dependencies, but this would incomplex extending the image by our users.

OK, so if I understood correctly, you recommend building the clean version of the image ourselves. Thanks!

I honestly don't see any reason for that. I recommend using our official Docker image since I can't guarantee proper work otherwise.

We're doing image scanning so these false positives create overhead and "known bad" state which might mean some "unknown bad" slips by, not to mention the image size.
It gives me an opportunity to try out Chiselled Ubuntu images.
Will try it out and if it makes sense, we could PR the clean image Dockerfile you could offer side by side with the existing image.


VidGear with v4l2loopback

Is possible to use the module with v4l2loopback? I've working for a while without success, I'm trying to send the NetGear output trough ffmpeg with the tcp protocol but without success. Would be nice if the somehow the module had the capability to write strait to the v4l2loopback devices. Anyway the vidgear is simplifying thing a lot, thank you for the hard work.

Is possible to use the module with v4l2loopback?

@wpcasarin Yes, you can easily with WriteGear API's Compression Mode with FFmpeg backend, that supports URLs. See an twitch example here and convert it according to your need for v4l2loopback.


Helper lines object counter

Show the selected helper line object (rectangle or hexagon) on the status bar.

How this works in Tiled:

If the helper line is disabled (what is the default value) the helper line object counter will not be show on the status bar.
I added 2 new field where can enable helper lines.

These offset spinners will add offset to the counter.
The helper lines settings will be hide if the helper lines checkbox is disabled:

Looks good, I am hesitant as this is very project specific features but I see no harm in adding it. I may rework the debug rendering later to break the debug render options into separate windows.

Looks good, I am hesitant as this is very project specific features but I see no harm in adding it. I may rework the debug rendering later to break the debug render options into separate windows.

I tried to made it general as I could that anyone else could use it, but later if you think we can remove the helper lines feature or part of this feature, because I can use it in my fork.


Corrected source to sources in the code for the file_transcribe inter…

…face.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


exercise 4.8

this is your picture

this is my picture

but we both don't get the picture in the book like this

I think this https://github.com/ShangtongZhang/reinforcement-learning-an-introduction/issues/39 may help.

@ShangtongZhang thank you!


[JS] model 'gemma' not found, try pulling it first

Describe the bug
when i click [Run] on the flow, there is an error showing that model 'gemma' not found, try pulling it first
To Reproduce
following the genkit init steps and use the default ollama way to start genkit start.
(in fact i 've got ollama installed and serving, and gemma:7b has been pulled before ollama serve)
Expected behavior
start my flow rightly (or show me how to check my ollama models are ready for genkit.
Screenshots
.
Runtime (please complete the following information):

OS: [e.g. Windows]
Version [10]

** Node version

v18.19.1

Additional context
can the ollama plugin be more easier to debug.

ok, i figured it out. in the configureGenkit.plugins[0].ollama.models, we should set name to gemma:7b, and in the defineFlow's async callback we should use model: 'ollama/gemma:7b' in the generate method.
thats all, thanks~


#25 Removes the example project by splitting into another repo.

New location for examples https://github.com/fullstack-development/pab-api-js-examples


Amg/simple taxonomy mappings

closes: https://github.com/Shopify/multi-channel-management/issues/579
Adds taxonomy mappings to visualizer web app, improves performance and dev environment for Jekyll site by:

moved to BEM css pattern to simplify selectors for performance gains

when toggling visibility using JS selectors a hidden & visible class is used explicitly reducing style rendering times
removed wrapping "card" container around app as it was causing unnecessary DOM reflow events

moved to standardized data-* attribute for JS consumption
caching DOM reads after first paint. This reduces task length on the main thread

where possible DOM reads are done before writes. ex
renderPage uses either yieldToMain or schedular when available to break of tasks on main thread. The aim is 60fps, 16ms per task
adding eslint and prettier to dev environment. I left it optional by not running pnpm install in dev up

Testing the app:

dev up
dev build
make sure the local Jekyll server is running from the Procfile

either run the server command explicitly jekyll serve --source docs --port 2399 or within vscode Spin tools internally

navigate to http://localhost:2399/

Sometimes in Spin (internally) the port stops forwarding to your local computer and visiting http://localhost:2399/ will not load anything. Deleting the port and re-adding it within the vscode PORTS tab will fix it.

This may be a bug in the mappings data, but we should be showing public IDs here...

Odd that looks like an older version of the app...


ISPN-7218 FIFO command does not wait for topology

https://issues.jboss.org/browse/ISPN-7218

Integrated, thanks Pedro!


Equivalent to OptionButton for checkboxes

Godot version:
Godot 3.2-dev master 2019-08-01 (3a6102a6f716904bb158819146e3fed7590b8106)
Issue description:

The OptionButton (a.k.a. drop down menu) uses radio buttons
It would be nice if we could have a class derived from OptionButton (or the other way round) that supports checkboxes.
This problem was encountered when improving the filter for the GDNativeLibrary dock #30923.
In this PR a MenuButton was used but isn't ideal as the operations had to be done manually.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Backends do not report per-shot measurements

What is the expected enhancement?
We need to return per-shot measurements from the backends. Use cases include random number generation.
To support this, we should update the two local qasm simulators, the IBMQ backends, and the result object.

closing as duplicate of #1063


fix: responsive faq section

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Hi! I want to work on this issue Assign me!

Hi! I want to work on this issue Assign me!

It's a Pull Request, I have already finished this issue that's why i make a PR. so if you want to work then find other issue in our website and make an issue.

Hi! I want to work on this issue Assign me!

It's a Pull Request, I have already finished this issue that's why i make a PR. so if you want to work then find other issue in our website and make an issue.

Sorry I did not see that i have open issuse check plz


Fix find_elements using array and params starting with $

Hello,
I started using marionette, but crashed when using find_elements, also I was getting empty properties from elements.
Please review this small changes I did, which made it work perfectly now.
I'm running it in crystal 1.8.2.
Thanks,

btw, I notice that when using the shard, old version is downloaded, without any of the current master changes.
should we also change the version?

This shard is currently largely unmaintained, but I have plans to change that. Merging this will be a good start, but yes we do also need a version bump. Taking on a co-maintainer wouldn't be out of the question.

thanks for merging, I'm using it, so if I find anything wrong I will fix it.


If I have the URL to a data vault, is there any way for me to deduce the owner/controller of the data vault itself?

If I have the URL to a data vault, is there any way for me to deduce the owner/controller of the data vault?
Hopeful answer: no
It's expected that I can deduce the name of the server provider but not the actual owner/controller of the data vault?

@agropper let's stick with the definitions in the Spec...

Encrypted Data Vaults fulfill the low-level encrypted storage role

@mwherman2000 With all due respect to you and to the layers diagram slide, I see a charter for a specification with only two layers: A (storage) Server (the policy enforcement layer) and a Client (the policy decision layer).
We can write options into the Server API but that doesn't make them a separate layer.
We can then start to label different Clients differently depending on what options of the Server they support. This naming exercise could add clarity or it could harm the value of the standard as a label for interoperability.

I see a charter for a specification with only two layers: A (stor

We can write options into the Server API but that doesn't make them a separate layer.
We can then start to label different Clients differently depending on what options of the Server they support. This naming exercise could add clarity or it could harm the value of the standard as a label for interoperability.

@mwherman2000 With all due respect to you and to the layers diagram slide, I see a charter for a specification with only two layers: A (storage) Server (the policy enforcement layer) and a Client (the policy decision layer).

@agropper Do you have a link?

@mwherman2000 https://docs.google.com/presentation/d/1ksKal62ZiApX09Nejm4RSqHzHJbgwpu_l2Ho64_ePKU/edit#slide=id.gb2d2b0f28a_0_0 labels the actors in six use-cases. The EDV is always as server. There are various clients to the EDV depending on the use case.

https://drive.google.com/file/d/1vf2CsD9QZstzrd6CJ4WFVHw0WKwwNLHf/view
On Mon, Mar 1, 2021 at 7:36 PM mwherman2000<EMAIL_ADDRESS>wrote:

@agropper https://github.com/agropper you mentioned/referenced a
statement in a charter
Do you have a link to the charter you referenced?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/decentralized-identity/confidential-storage/issues/197#issuecomment-788445832,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABB4YPI7OEWBV4YFUA36R3TBQXJ3ANCNFSM4YNIPAIA
.

@ajunge The referenced charter makes no reference to 2 layers being a storage server and a client per one of your original comments

Create one or more specifications to establish a foundational layer for secure data storage (including personal data), specifically
data models for storage and transport, syntax, data at rest protection, CRUD API, access control, synchronization, and at least a
minimum viable HTTP-based interface compatible with W3C DIDs/VCs.
The Identity Hubs and Encrypted Data Vaults documents will be used as a use case, requirements, and technical input for the
collaborative effort.