<EMAIL_ADDRESS>

我在使用postgres 13.4的版本（目前是最新的版本），使用flink的postgres-cdc无法获取wal日志信息。
`final Log log = LogFactory.getLog(PostgresCDC.class);
final StreamExecutionEnvironment executionEnvironment = StreamExecutionEnvironment.createLocalEnvironment();
executionEnvironment.setParallelism(1);
    final Properties properties = new Properties();
    properties.setProperty("heartbeat.interval.ms", "10000");
    final DebeziumSourceFunction<String> debeziumSourceFunction = PostgreSQLSource.<String>builder()
            .hostname("<IP_ADDRESS>")
            .port(15432)
            .database("test")
            .schemaList("public")
            .tableList("pg_cdc_source")
            .username("test")
            .password("ch199407")
            .decodingPluginName("pgoutput")
            .debeziumProperties(properties)
            .deserializer(new StringDebeziumDeserializationSchema() {
                @Override
                public void deserialize(SourceRecord record, Collector<String> out) throws Exception {
                    log.info(record);
                    log.info(out);
                    super.deserialize(record, out);
                }
            })
            .build();

    executionEnvironment.addSource(debeziumSourceFunction).print();
    executionEnvironment.execute("postgres cdc");

`
flink-cdc的版本
       <dependency>             <groupId>com.alibaba.ververica</groupId>             <artifactId>flink-connector-postgres-cdc</artifactId>             <version>1.2.0</version>         </dependency>
部分日志
16:55:57.977 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:57.977 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:57.977 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:57.977 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:57.978 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:57.978 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:57.978 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:57.978 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:57.983 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:57.983 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.blacklist" is deprecated and will be removed in future versions. Please use "table.exclude.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.blacklist" is deprecated and will be removed in future versions. Please use "table.exclude.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.whitelist" is deprecated and will be removed in future versions. Please use "schema.include.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.blacklist" is deprecated and will be removed in future versions. Please use "schema.exclude.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.whitelist" is deprecated and will be removed in future versions. Please use "schema.include.list" instead. 16:55:57.984 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.blacklist" is deprecated and will be removed in future versions. Please use "schema.exclude.list" instead. 16:55:57.984 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask - Starting PostgresConnectorTask with configuration: 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    connector.class = io.debezium.connector.postgresql.PostgresConnector 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.user = test 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.dbname = test 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    offset.storage = com.alibaba.ververica.cdc.debezium.internal.FlinkOffsetBackingStore 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    slot.name = flink 16:55:57.985 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.server.name = postgres_cdc_source 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    heartbeat.interval.ms = 10000 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    include.schema.changes = false 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.port = 15432 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    plugin.name = pgoutput 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    schema.whitelist = public 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    table.whitelist = pg_cdc_source 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    offset.flush.interval.ms =<PHONE_NUMBER>854775807 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    key.converter.schemas.enable = false 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    tombstones.on.delete = false 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.hostname = <IP_ADDRESS> 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.password = ******** 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    value.converter.schemas.enable = false 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    name = engine 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.history.instance.name = 4555c471-6f26-40a2-886b-2d1d9fab7701 16:55:57.986 [debezium-engine] INFO  i.d.connector.common.BaseSourceTask -    database.history = com.alibaba.ververica.cdc.debezium.internal.FlinkDatabaseHistory 16:55:57.998 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.whitelist" is deprecated and will be removed in future versions. Please use "schema.include.list" instead. 16:55:58.000 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.blacklist" is deprecated and will be removed in future versions. Please use "schema.exclude.list" instead. 16:55:58.000 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:58.000 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.blacklist" is deprecated and will be removed in future versions. Please use "table.exclude.list" instead. 16:55:58.001 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:58.137 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.blacklist" is deprecated and will be removed in future versions. Please use "schema.exclude.list" instead. 16:55:58.137 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.blacklist" is deprecated and will be removed in future versions. Please use "table.exclude.list" instead. 16:55:58.137 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:58.138 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.whitelist" is deprecated and will be removed in future versions. Please use "schema.include.list" instead. 16:55:58.139 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:58.139 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:58.140 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.blacklist" is deprecated and will be removed in future versions. Please use "schema.exclude.list" instead. 16:55:58.140 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.blacklist" is deprecated and will be removed in future versions. Please use "table.exclude.list" instead. 16:55:58.141 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:58.141 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "schema.whitelist" is deprecated and will be removed in future versions. Please use "schema.include.list" instead. 16:55:58.141 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.whitelist" is deprecated and will be removed in future versions. Please use "column.include.list" instead. 16:55:58.141 [debezium-engine] WARN  io.debezium.config.Configuration - Using configuration property "column.blacklist" is deprecated and will be removed in future versions. Please use "column.exclude.list" instead. 16:55:58.180 [debezium-engine] INFO  i.d.c.p.PostgresConnectorTask - user 'test' connected to database 'test' on PostgreSQL 13.4 on x86_64-apple-darwin20.4.0, compiled by Apple clang version 12.0.5 (clang-1<IP_ADDRESS>), 64-bit with roles: 	role 'test' [superuser: false, replication: true, inherit: true, create role: false, create db: false, can log in: true] 16:55:58.184 [debezium-engine] INFO  i.d.c.p.c.PostgresConnection - Obtained valid replication slot ReplicationSlot [active=false, latestFlushedLsn=LSN{0/16C3518}, catalogXmin=548] 16:55:58.184 [debezium-engine] INFO  i.d.c.p.PostgresConnectorTask - No previous offset found 16:55:58.184 [debezium-engine] INFO  i.d.c.p.snapshot.InitialSnapshotter - Taking initial snapshot for new datasource 16:55:58.205 [debezium-engine] INFO  io.debezium.util.Threads - Requested thread factory for connector PostgresConnector, id = postgres_cdc_source named = change-event-source-coordinator 16:55:58.209 [debezium-engine] INFO  io.debezium.util.Threads - Creating thread debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator 16:55:58.211 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.ChangeEventSourceCoordinator - Metrics registered 16:55:58.212 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.ChangeEventSourceCoordinator - Context created 16:55:58.215 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.snapshot.InitialSnapshotter - Taking initial snapshot for new datasource 16:55:58.215 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresSnapshotChangeEventSource - According to the connector configuration data will be snapshotted 16:55:58.216 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 1 - Preparing 16:55:58.271 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 2 - Determining captured tables 16:55:58.274 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] WARN  io.debezium.config.Configuration - Using configuration property "table.whitelist" is deprecated and will be removed in future versions. Please use "table.include.list" instead. 16:55:58.275 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 3 - Locking captured tables [] 16:55:58.276 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresSnapshotChangeEventSource - Waiting a maximum of '10' seconds for each table lock 16:55:58.297 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 4 - Determining snapshot offset 16:55:58.299 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresSnapshotChangeEventSource - Creating initial offset context 16:55:58.301 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresSnapshotChangeEventSource - Read xlogStart at 'LSN{0/16DECB0}' from transaction '555' 16:55:58.302 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresSnapshotChangeEventSource - Read xlogStart at 'LSN{0/16DECB0}' from transaction '555' 16:55:58.303 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 5 - Reading structure of captured tables 16:55:58.324 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 6 - Persisting schema history 16:55:58.324 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.r.RelationalSnapshotChangeEventSource - Snapshot step 7 - Snapshotting data 16:55:58.328 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.s.AbstractSnapshotChangeEventSource - Snapshot - Final stage 16:55:58.328 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.ChangeEventSourceCoordinator - Snapshot ended with SnapshotResult [status=COMPLETED, offset=PostgresOffsetContext [sourceInfoSchema=Schema{io.debezium.connector.postgresql.Source:STRUCT}, sourceInfo=source_info[server='postgres_cdc_source'db='test', lsn=LSN{0/16DECB0}, txId=555, timestamp=2021-08-16T08:55:58.303Z, snapshot=FALSE], partition={server=postgres_cdc_source}, lastSnapshotRecord=true, lastCompletelyProcessedLsn=null, lastCommitLsn=null, transactionContext=TransactionContext [currentTransactionId=null, perTableEventCount={}, totalEventCount=0]]] 16:55:58.329 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] WARN  i.d.r.RelationalDatabaseSchema - After applying the include/exclude list filters, no changes will be captured. Please check your configuration! 16:55:58.331 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.m.StreamingChangeEventSourceMetrics - Connected metrics set to 'true' 16:55:58.332 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.p.ChangeEventSourceCoordinator - Starting streaming 16:55:58.332 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresStreamingChangeEventSource - Retrieved latest position from stored offset 'LSN{0/16DECB0}' 16:55:58.332 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.WalPositionLocator - Looking for WAL restart position for last commit LSN 'null' and last change LSN 'LSN{0/16DECB0}' 16:55:58.333 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.PostgresReplicationConnection - Initializing PgOutput logical decoder publication 16:55:58.348 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.PostgresConnection - Obtained valid replication slot ReplicationSlot [active=false, latestFlushedLsn=LSN{0/16C3518}, catalogXmin=548] 16:55:58.351 [pool-3-thread-1] INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed 16:55:58.398 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresStreamingChangeEventSource - Searching for WAL resume position 16:56:28.496 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.WalPositionLocator - First LSN 'LSN{0/16DED10}' received 16:56:28.496 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresStreamingChangeEventSource - WAL resume position 'LSN{0/16DED10}' discovered 16:56:28.497 [pool-5-thread-1] INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed 16:56:28.502 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.PostgresReplicationConnection - Initializing PgOutput logical decoder publication 16:56:28.515 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.PostgresStreamingChangeEventSource - Processing messages 16:56:28.516 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] INFO  i.d.c.p.c.WalPositionLocator - Message with LSN 'LSN{0/16DED10}' arrived, switching off the filtering 16:56:28.529 [debezium-postgresconnector-postgres_cdc_source-change-event-source-coordinator] WARN  i.d.c.p.c.p.PgOutputMessageDecoder - Primary keys are not defined for table 'pg_cdc_source', defaulting to unique indices 16:56:28.535 [pool-7-thread-1] INFO  io.debezium.jdbc.JdbcConnection - Connection gracefully closed

not support .
support version as ablove:

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!


Custom XSL-StyleSheet for HTML-Report

Is it possible to use a custom XSL-stylesheet for generating the HTML-report?
The current report shows title "Checkstyle Results" instead of "Sonarlint Results" and did not show the issue rule number (e.g. "java:S100").

@makkimesser , fixed in version 4.2.11. Feel free to reopen the issue if something doesn't work properly.

Report looks fine now, so I have no need for custom style-sheet. Thanks for your very quick response.


[CONTRACTS] - DebtCouponManager V2 - Create uBOND token

It's just a regular ERC20 token that can be redeemed 1-1 to uAD when the TWAP is > 1
What needs to happen

Create uBOND token
Make redeeming function for uAD 1-1 when TWAP > 1

This will simply be uCR-NFTs with an expiration time far enough in the future to consider it "non expiring"


[Fix]Enable puts in Fiber.schedule block

Why
A function call puts "at_least one_argument" in a Fiber.schedule block raises an error Errno::EAGAIN.
How to reproduce
(📝 Use this repo to reproduce with a docker container.)
Run the snippet below In the root directory of this repository.
require './lib/scheduler'
thread = Thread.new do
  t = Time.now
  Fiber.set_scheduler AsyncScheduler::Scheduler.new

  Fiber.schedule do
    puts 'some string'
  end
end
thread.join

It raises an error below.
some string#<Thread:0x0000000105bb7a28 (irb):33 run> terminated with exception (report_on_exception is true):
(irb):38:in `write': Resource temporarily unavailable @ io_writev - <STDOUT> (Errno::EAGAIN)
        from (irb):38:in `puts'
        from (irb):38:in `puts'
        from (irb):38:in `block (2 levels) in <top (required)>'
(irb):38:in `write': Resource temporarily unavailable @ io_writev - <STDOUT> (Errno::EAGAIN)
        from (irb):38:in `puts'
        from (irb):38:in `puts'
        from (irb):38:in `block (2 levels) in <top (required)>'

⚠  Please note that puts works properly if it is called with no argument.
The error is raised when it is called with at least 1 augment.

details
require './lib/scheduler'
thread = Thread.new do
  t = Time.now
  Fiber.set_scheduler AsyncScheduler::Scheduler.new

  Fiber.schedule do
    puts
  end
end
thread.join

=> #<Thread:0x0000000105cc8db8 (irb):82 dead>

This does not raise an error.

What

Main causes
After 3 days of debugging, I found these to be the causes.

#puts possibly calls #io_write multiple times. (Source code: io.c/rb_io_puts)

It is intuitive that this is the case when multiple arguments are given. e.g. puts 'xxx', 'y'.
Even when only one argument is given like puts 'xxx', #io_write may be called twice. For puts 'xxx', one time for writing string xxx, and the other time for writing a line break in the end of the line.

For these multiple io_write, no mutex is used. Thus, to avoid the race condition caused by this, in "the total increase of length in i/o" and "the total length written in the current context(io_binwritev function)` are compared in io.c/io_binwritev. If they are not equal, the program stops (like the error above).

They don't use
Ref.

Ruby’s puts is not atomic
Rubyのparallelで並列処理するときにputsでLog出しするときに注意すること

Solution
This behavior of ruby would be fixed in the PR below.

https://github.com/ruby/ruby/pull/5419)
(ruby bug report) Make IO#write atomic.

I will wait this PR to be merged, and see if the bug remains.


Exception in castep parser

This happens on 6 entries.
Traceback (most recent call last):
  File "/app/nomad/processing/data.py", line 460, in parsing
    self._parser_results, logger=logger)
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1200, in parse
    self.parse_configurations()
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1051, in parse_configurations
    parse_calculation(calculation)
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 1045, in parse_calculation
    sec_scc = parse_scc(source)
  File "/usr/local/lib/python3.7/site-packages/castepparser/castep_parser.py", line 957, in parse_scc
    sec_sedc.x_castep_correction_energy = (shell[1] * energy_unit).to('J').magnitude
  File "/usr/local/lib/python3.7/site-packages/pint/quantity.py", line 660, in to
    magnitude = self._convert_magnitude_not_inplace(other, *contexts, **ctx_kwargs)
  File "/usr/local/lib/python3.7/site-packages/pint/quantity.py", line 609, in _convert_magnitude_not_inplace
    return self._REGISTRY.convert(self._magnitude, self._units, other)
  File "/usr/local/lib/python3.7/site-packages/pint/registry.py", line 947, in convert
    return self._convert(value, src, dst, inplace)
  File "/usr/local/lib/python3.7/site-packages/pint/registry.py", line 1830, in _convert
    return super()._convert(value, src, dst, inplace)
  File "/usr/local/lib/python3.7/site-packages/pint/registry.py", line 1433, in _convert
    return super()._convert(value, src, dst, inplace)
  File "/usr/local/lib/python3.7/site-packages/pint/registry.py", line 996, in _convert
    value = value * factor
TypeError: can't multiply sequence by non-int of type 'float'

The example has embargo on it.
https://nomad-lab.eu/prod/rae/reprocess/gui/entry/id/CTTru-A7REe4XWGaV-l3cA/s47fvrWr7RNl7TnmonHs7xQY0WMe/raw

@ladinesa I reprocessed the castep entries. Looks good. That was the only apparent exception.

Should be fixed in latest commit.


No resource shows in the resource group

OS: All
Resource Group Build Version: 20230214.5
Azure Container App Build Version: 20230213.10
Repro Steps:

F1 -> Azure: Delete Resource Group... -> Select subscription -> Select a resource group such as "Nicole-env2".
Pop up a delete confirmation "There is 1 resource in this resource group that will be deleted." -> Click "Cancel".
Expand the resource group "Nicole-env2".
Check whether one resource shows in this resource group.

Expect:
One resource shows in this resource group.

Actual:
No resource shows in this resource group.

I think this is expected behavior, since we're just no longer showing the filtered resources unless they enable the azureResourceGroups.showHiddenTypes setting.

Closing as this is by design.


Automated cherry pick of #8076: bugfix:commonalert

Cherry pick of #8076 on release/3.4.
#8076: bugfix:commonalert

/lgtm
/approve


Shortcut "Ctrl+[KeyC]" is turned into "Ctrl + PageDown"

Type: Bug
I have a custom keyboard layout installed (Neo 2.0) which uses letter ä for [KeyC]. Before version 1.75.0, it worked out just fined but after upgrading the combination (Ctrl + [KeyC]) doesn't work anylonger and is displayed as Ctr + PageDown.
Important to not as well is, that it is still shown as Ctrl + [KeyC] in the keys .json file.
Trying to use Ctrl + ä fails with something like "Your can't produce this combination on your keyboard" or something
VS Code version: Code 1.75.0 (e2816fe719a4026ffa1ee0189dc89bdfdbafb164, 2023-02-01T15:29:17.766Z)
OS version: Linux x64 5.19.17-2-MANJARO
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 3641)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 1, 1

Memory (System)
15.34GB (9.48GB free)

Process Argv
--unity-launch --crash-reporter-id 2688914e-7d7f-4852-879f-8ce70c8b65c3

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1cf:30587006
3biah626:30602489
89544117:30613380
pythonsymbol12:30657548
2i9eh265:30646982
vscup:30628656

I have a similar experience. When using the keyboard shortcut editor and trying to update Toggle Terminal and enter Ctrl+´ it is displayed as Ctrl+[Equal] and pressing Enter, it  becomes Ctrl-V. So if I press Ctrl+V now I toggle the terminal instead of inserting the clipboard. Initially it confused me, because Ctrl+V stated without keyboard shortcut editing to toggle the terminal.
VS Code version: 1.75.0
Ubuntu 22.04.1 LTS
Keyboard: German (no dead keys)
I could use Ctrl+´ for toggle terminal and it worked as expected.

Having the same problem using Portuguese (Portugal) layout.
From what I've noticed, CTRL+[Equal] turns into CTRL+V and CTRL+[Minus] turns into CTRL+U. Furthermore, CTRL+ALT+[Equal] turns into CTRL+ALT+« (as expected) and CTRL+ALT+[Minus] turns into CTRL+ALT+' (as expected).

Duplicate of #173325


some enums have been changed to camelCase from PascalCase

cova's build.zig is no longer valid.
/Users/p7r0x7/.cache/zig/p/122073922013698dd2c2339cb9fa37436408eb97d033f166b817d8a12193c47c2af3/build.zig:182:51: error: no field named 'Struct' in union 'builtin.Type'
    inline for (@typeInfo(generate.MetaDocConfig).Struct.fields) |field| {
                                                  ^~~~~~
/Users/p7r0x7/zig/lib/std/builtin.zig:257:18: note: union declared here
pub const Type = union(enum) {
                 ^~~~~
referenced by:
    build: /Users/p7r0x7/.cache/zig/p/122073922013698dd2c2339cb9fa37436408eb97d033f166b817d8a12193c47c2af3/build.zig:78:45
    runBuild__anon_66109: /Users/p7r0x7/zig/lib/std/Build.zig:2167:33
    9 reference(s) hidden; use '-freference-trace=11' to see all references

Appreciate you pointing this out.
The issue is much deeper than that unfortunately. I'll be doing a migration to v0.14 at some point, but I have several projects pinned to v0.13, so I want to make sure there's not any other issues I need to resolve for those first.

Yeah I assumed you knew it was deeper; haven't been able to compile my stuff for over a month, though pinning to 13 is reasonable.

Yea, hopefully not too much longer.
I've considered using builtin.version to support both, but it's used in too many areas to support a bandaid fix like that.

You could follow zig master on main and have a tagged release for 0.13.0. This way both master and 0.13.0 users could use cova.

@Ratakor  in the short term, https://github.com/Beyley/cova is also available.

You could follow zig master on main and have a tagged release for 0.13.0. This way both master and 0.13.0 users could use cova.

Appreciate you showing interest in Cova!
Normally, I would do this, however I have several projects that I've tagged to Zig v0.13.0 because they require a level of stability. As I work on these projects I also push Cova forward with features and fixes needed, so Cova main needs to be on v0.13.0 for that.
However, my plan is to do something similar soon. I'll add a branch for zig_nightly that'll effectively be the last tagged Cova release, but updated for the latest Zig. This branch won't see new features, but I'll keep it working for nightly as well as I can.


red text

Challenge Waypoint: Use a CSS Class to Style an Element has an issue.
User Agent is: Mozilla/5.0 (Windows NT 5.1; rv:41.0) Gecko/20100101 Firefox/41.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.

Looks like you copied and pasted the example code from the sidebar, which has "thin space" characters in it. Using this character as whitespace makes your css invalid. You're always better off typing the code yourself -- it's good for muscle memory and practice!
Also, the directions ask you to add the red-text class to your existing h2, not create a new one, so you'll need to delete the second one and move the class="red-test" into the first one.
Closing as not an issue with the tests, but feel free to reply if you need further clarification.
Thanks and happy coding!

hat stinks is. now I will never know what my actual problem was. Since I deleted and replaced the text. Sorry for bugging you!


Lazy Load Member list

Save lazy load member list to SQL. Add command to do it to console, so it isn't done automatically. Too many risks if it is run regularly, automatically.

Just runs on client being ready. That is good enough, I'll eventually write some command system.


[Bug]: SimpleDirectoryReader reads "once" and then says no files

Bug Description
When I run the SimpleDirectoryReader it will find files, work as intended. But if I run it again, it will complain there are no files in the directory if ran again in same Python session on same dir.
Version
llama-index==0.11.1
Steps to Reproduce
Load files with simple directory reader, do things. Run again on same documents (inefficient, yes, but has a issue) and reader.load_data() will evaluate False. Files in directory still exist on disk.
Relevant Logs/Tracbacks
documents = reader.load_data()
if not documents:
    raise ValueError("No documents found in the specified directory.")

Traceback (most recent call last):
  File "M:\ComfyUI_slow_2\execution.py", line 317, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
  File "M:\ComfyUI_slow_2\execution.py", line 192, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
  File "M:\ComfyUI_slow_2\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "M:\ComfyUI_slow_2\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
  File "M:\ComfyUI_slow_2\custom_nodes\SaltAI_Language_Toolkit\nodes\readers.py", line 1012, in read_directory
    raise ValueError("No documents found in the specified directory.")
ValueError: No documents found in the specified directory.

Hey @WASasquatch! I'm here to help with any bugs, questions, or contributions you have for llama-index. I'm looking forward to assisting you with this issue!
The issue you're encountering with SimpleDirectoryReader in llama-index==0.11.1 is due to the class caching the list of input files when it is first instantiated. Subsequent attempts to read files in the same session will use the cached list, which does not get updated.
To work around this, you need to create a new instance of SimpleDirectoryReader each time you want to read the files again in the same session. This will ensure that the directory is scanned afresh and the list of files is updated.
Here's a brief explanation of the behavior:
* When `SimpleDirectoryReader` is instantiated, it initializes the `input_files` attribute by calling the `_add_files` method, which scans the directory and caches the list of files.

* Subsequent calls to `load_data()` will use this cached list, and if the list is empty or unchanged, it will result in no files being found.

To avoid this, instantiate a new SimpleDirectoryReader like this:
from llama_index import SimpleDirectoryReader

# First read
reader = SimpleDirectoryReader(input_dir="your_directory_path")
documents = reader.load_data()

# Do some processing...

# Second read (create a new instance)
reader = SimpleDirectoryReader(input_dir="your_directory_path")
documents = reader.load_data()

This approach ensures that the directory is scanned afresh each time you want to read the files [1].
To continue talking to Dosu, mention @dosu.

I do in fact re-instantiate the simple directory reader in the method which is called each "run":
    def read_directory(self, input_directory, optional_path_list=[], recursive=False, required_ext_list=None, exclude_glob_list=None):

        if required_ext_list.strip():
            required_exts = [ext.strip() for ext in required_ext_list.split(",") if ext.strip()]
        else:
            required_exts = None

        if exclude_glob_list.strip():
            exclude = [pattern.strip() for pattern in exclude_glob_list.split(",") if pattern.strip()]
        else:
            exclude = None

        logger.info(f"Excluding: {exclude}")
        logger.info(f"Required Extensions: {required_exts}")

        if not optional_path_list:
            full_path = get_full_path(1, input_directory.strip())
            input_dir = full_path if os.path.isdir(full_path) else None
            if not input_dir:
                raise ValueError("The provided subdirectory does not exist.")

            reader = SimpleDirectoryReader(
                input_dir=input_dir,
                exclude_hidden=True,
                recursive=recursive,
                required_exts=required_exts,
                exclude=exclude
            )
        elif optional_path_list and isinstance(optional_path_list, (str, list)):

            if isinstance(optional_path_list, str):
                path_list = [optional_path_list]
            else:
                path_list = []
                for path in optional_path_list:
                    if os.path.isfile(path): # and path.startswith(folder_paths.get_input_directory()):
                        path_list.append(path)

            reader = SimpleDirectoryReader(
                input_files=path_list,
            )

        documents = reader.load_data()
        if not documents:
            raise ValueError("No documents found in the specified directory.")

        return (documents,)

So it is re-instantiated.

I think the issue is it's having a really hard time with .ipynb files.


Syntax highlighting issue on parenthesis

Description of the problem or steps to reproduce
Related parenthesis doesn't have the same color, for example in JS files. Sorry if this has already been reported but I didn't find anything about it.

Open a javascript file and see that some function opening and closing parenthesis doesn't have the same color
Specifications
Commit hash: a02ae3c (v1.3.3 installed from Brew)
OS: Mac OS Sierra 10.12.3
Terminal: default

Info of the fault above
line 10 in runtime/syntax/javascript.yaml is causing the problem as it is catching the bracket in the regex.

identifier: "[A-Za-z_][A-Za-z0-9_][[:space:]][(]"

Not sure how to cure this, as I am not very good at regex.

Try to replace regexp on line 10 with
"[A-Za-z_][A-Za-z0-9_]*[[:space:]]*"

There's a similar issue with Lua.
Matching brackets are highlighted, except if there is a string between them.

@is73 that doesn't seem to work, I'm not sure I'm proceeding properly
here is what I did :

installed go
installed micro with the go get -d github.com/zyedidia/micro/cmd/micro command
change the line in ~/go/src/github.com/zyedidia/micro/runtime/syntax/javascript.yaml according to your suggestion
run make install
run ~/go/bin/micro some/file.js
see no change in parenthesis highlighting

You need to use make with build-all and install or install-all to build the runtime files to see the changes.
e.g
make build-all
make install
or
make install-all
does all the above with one command.

You can also use make runtime to just build the runtime (this will make sure all changes to any files in runtime will be in the new build) and then make install to build.

ok thanks ! it works !
I could make a PR but this is @is73 work so I don't want to steal any credit on this, maybe @zyedidia could just add it to its code ?

It was an accident so make some PR :)

I would also add the .es[5678]? extension management, so should I make two different PRs for the same file ?

You can go ahead and do both in one PR if that's easier.

I would like to solve this in my newlisp sources to view matching paren arghhh :)

Here you go : https://github.com/zyedidia/micro/pull/868
Thanks for your help guys

Using regular expressions for syntax highlighting makes finding matching braces very hard or impossible. But we've fixed the javascript parentheses with a sort of workaround :). See #868.


[master] Improved allocation profiler settings. [6892]

Port of commit 4f4568f

Build status:

Linux
Mac
Windows
Performance


Interfaces Overview, merge DHCPv4 / DHCPv6 buttons

Having two sets of buttons implies that they only act on the respective protocol, but this is not the case.
https://github.com/opnsense/core/issues/5974#issuecomment-1225222923

Merged, thanks!


Bump to 6.29.5

Checklist

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

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

@conda-forge-admin, please rerender

I need that exact 6.29.5 version for https://github.com/conda-forge/staged-recipes/pull/21653

@conda-forge/rocksdb do you mind reviewing please?

@hmaarrfk do you mind reviewing this since this repo seems a bit unmaintained? I added myself as a maintainer.
I need that exact version for another package, but I am happy to try to build the latest version once merged here.
Also I have a question: all the compression libs (zlib, bzip2, snappy, etc) are in reqs/host, I wonder whether we should add them to reqs/run as well so people using rocksdb does not have to include them specifically. What do you think?

They are implicitly added through run_export in the respective packages.

Thanks @hmaarrfk !


Prefix support on unsafe_validate_unique

Hi,
I have added just that. Not sure about the correctness of the test though, guidance is greatly appreciated =)
Cheers,

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


 I hope you know how miniscule you would be compared to me in the afterlife. Be it Heaven or Hell, Tartarus or Elysium, Valhalla or Hel, I hope you know that even beyond reincarnation and the end itself, I will be a true and personal hater, only here to spite you out of hate, even going as far to try and learn voodoo just place curses upon you just because it would genuinely be funny.
And even then, that is not enough, no matter what, I'm always gonna be here, hating and hating, loathing your existence beyond what God himself can imagine, taking it to extreme lengths, not even things that would be traumatically affect you, that would be too easy, I want to see you always have at least a clogged nose three times a week, I want you to wake up with a calf cramp at least four times a week, I want to see you at least break your something expensive of your belongings like your monitor to your GPU itself to break at least once a month, and I want you to gain 2x the weight you'd gain from eating, and the obvious option for you of losing weight would be hindered to at least 25% the speed of what it is now, slowing your metabolism enough to make it process an entire dish of spaghetti in half a decade.

 I hope you know how miniscule you would be compared to me in the afterlife. Be it Heaven or Hell, Tartarus or Elysium, Valhalla or Hel, I hope you know that even beyond reincarnation and the end itself, I will be a true and personal hater, only here to spite you out of hate, even going as far to try and learn voodoo just place curses upon you just because it would genuinely be funny.
And even then, that is not enough, no matter what, I'm always gonna be here, hating and hating, loathing your existence beyond what God himself can imagine, taking it to extreme lengths, not even things that would be traumatically affect you, that would be too easy, I want to see you always have at least a clogged nose three times a week, I want you to wake up with a calf cramp at least four times a week, I want to see you at least break your something expensive of your belongings like your monitor to your GPU itself to break at least once a month, and I want you to gain 2x the weight you'd gain from eating, and the obvious option for you of losing weight would be hindered to at least 25% the speed of what it is now, slowing your metabolism enough to make it process an entire dish of spaghetti in half a decade.

linus torvalds is that you

that isn't even a copypasta i'm like 90% sure selene typed that up 😭

I accept both arguments.

that isn't even a copypasta i'm like 90% sure selene typed that up 😭

Selene moment


Protocol support and bump version

Why re-enable poggit CI?
It will conflict with my plugin when I merged this PR.
Please disable the poggit CI and remove .poggit.yml so that I can merge this.
Thank you for the PR.

Sorry I only saw the lint, I've disabled CI poggit

Thank you for your contribution!


Gh 1050 consistent add named operation json serialisation

Codecov Report

Merging #1057 into develop will decrease coverage by 0.02%.
The diff coverage is 14.28%.

@@              Coverage Diff              @@
##             develop    #1057      +/-   ##
=============================================
- Coverage      62.34%   62.32%   -0.03%
  Complexity      1204     1204
=============================================
  Files            545      545
  Lines          16326    16332       +6
  Branches        1896     1896
=============================================
  Hits           10179    10179
- Misses          5344     5350       +6
  Partials         803      803

Impacted Files
Coverage Δ
Complexity Δ

...gchq/gaffer/named/operation/AddNamedOperation.java
73.21% <0%> (-4.15%)
0 <0> (ø)

.../gchq/gaffer/jsonserialisation/JSONSerialiser.java
56.52% <0%> (-2.57%)
15 <0> (ø)

...ed/operation/handler/AddNamedOperationHandler.java
93.75% <100%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 000944d...8a1db22. Read the comment docs.


No hortons here

This is a PR just to remove traces of horton from the repo and replace with damspas-rd (for now).
I also updated the README a bit with @jessicahilt's quote ;)
@jhriv - let me know if you think the ansisible renaming is gonna be problematic. This was definitely a global search/replace, and a lot of it hit the ansible stuff.
@ucsdlib/developers - please review

@jhriv - I think I addressed the two issues you found. Anything else, let me know. Thanks again.


[Event Request] Table 36 SalesHeader - OpenSalesOrderStatistics

Dear AlAppExtensions Team,
We would like to request the following event Publisher in table 36 - OpenSalesOrderStatistics (ofcourse without the prefix DIN)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Cannot find module 'date-fns/format'

Hi there,
Thank you for the great tool. I have used this on my https://github.com/jellydn/grpc-demo-monorepo and it's working great until recently I got this error.
hello-twirp:dev: node:internal/modules/cjs/loader:1148
hello-twirp:dev:   throw err;
hello-twirp:dev:   ^
hello-twirp:dev:
hello-twirp:dev: Error: Cannot find module 'date-fns/format'
hello-twirp:dev: Require stack:
hello-twirp:dev: - /Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/src/flow-control/log-timings.js
hello-twirp:dev: - /Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/src/index.js
hello-twirp:dev: - /Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/bin/concurrently.js
hello-twirp:dev:     at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15)
hello-twirp:dev:     at Module._load (node:internal/modules/cjs/loader:986:27)
hello-twirp:dev:     at Module.require (node:internal/modules/cjs/loader:1233:19)
hello-twirp:dev:     at require (node:internal/modules/helpers:179:18)
hello-twirp:dev:     at Object.<anonymous> (/Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/src/flow-control/log-timings.js:31:34)
hello-twirp:dev:     at Module._compile (node:internal/modules/cjs/loader:1358:14)
hello-twirp:dev:     at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
hello-twirp:dev:     at Module.load (node:internal/modules/cjs/loader:1208:32)
hello-twirp:dev:     at Module._load (node:internal/modules/cjs/loader:1024:12)
hello-twirp:dev:     at Module.require (node:internal/modules/cjs/loader:1233:19) {
hello-twirp:dev:   code: 'MODULE_NOT_FOUND',
hello-twirp:dev:   requireStack: [
hello-twirp:dev:     '/Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/src/flow-control/log-timings.js',
hello-twirp:dev:     '/Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/src/index.js',
hello-twirp:dev:     '/Users/huynhdung/Projects/research/grpc-demo-monorepo/node_modules/concurrently/dist/bin/concurrently.js'
hello-twirp:dev:   ]
hello-twirp:dev: }
hello-twirp:dev:
hello-twirp:dev: Node.js v20.16.0
error Command failed with exit code 1.

How to reproduce:

Clone my repository
Run yarn install
Run yarn dev

Hey, I haven't debugged this issue but I'm replacing date-fns with a custom solution in 710ee55e8ca25192e14203e2738a1b5178da75ea.
This will solve your issue when the new version is released/you upgrade.

Great. Thanks. It works now after upgraded to v9 :clap:


Add standalone OAuth example

Add a small example to _examples directory (say, oauth.go and oauth_test.go) that runs small OAuth server with hardcoded credentials and tests it using httpexpect.
Server can use https://github.com/go-oauth2/oauth2
Client can use https://pkg.go.dev/golang.org/x/oauth2
Example can be based on https://github.com/go-oauth2/oauth2/tree/master/example
To use httpexpect with OAuth, you'll need to create a client using oauth2.NewClient and pass it to Config.
Also we need to add link to new example to README: https://github.com/gavv/httpexpect#examples

Hi @gavv, I've added the PR: https://github.com/gavv/httpexpect/pull/267
I'm not quite sure if the example is as expected.

@fahimbagar Thanks! Will review in upcoming days.

take your time @gavv

Landed!


Add docs for User functionality

The live docs can be found here: https://hpe-container-platform-community.github.io/hpecp-python-library/hpecp.html#
To view docs in gitpod - see here: https://github.com/hpe-container-platform-community/hpecp-python-library/blob/master/DEVELOPING.md#building-docs
This doc definition will need updating: https://raw.githubusercontent.com/hpe-container-platform-community/hpecp-python-library/master/docs/source/hpecp.rst
A new doc definition file will need to be created: hpecp.user.rst with the user documentation code.  See here for an example: https://raw.githubusercontent.com/hpe-container-platform-community/hpecp-python-library/master/docs/source/hpecp.gateway.rst

@pramaku - this may be a good one for you to look at to understand the documentation process.


Incorrect server status

Host operating system: output of uname -a
Prometheus / Grafana : Ubuntu 16.04
Flexlm: Server 2012R2
flexlm_exporter version: output of flexlm_exporter --version
Latest Docker image
What did you expect to see?
My server is UP and Running in dashboard
What did you see instead?
Server down

I think this is triad configuration related and data parsing. I have only one server
  - name: Creo
    license_server: 7788@BVS15004
    features_to_exclude: PROBUNDLE_10118,PROBUNDLE_10119,14,247,294,254,255,256,257,137,247,48,54,57,61,127,191,PROBUNDLE_10105,PROBUNDLE_10107,89,157,161,211,212,ILINK_TK_ACCESS_License,ILINK_CLIENT_License,MECMOTENG_MO,CREOSCHEM_Lite,MECMOTUI_MO,RSDESIGNER_Lite,10105,10107,10118,10119
    monitor_users: True
    monitor_reservations: True

Hi @VonOx,
Interesting, thanks for reporting!! I will be checking this next week, as I'm currently going on vacations. Could you please post the server information (~first 10 lines) of lmutil lmstat -c 7788@BVS15004 -a output here?

No problem
Output:
lmutil - Copyright (c) 1989-2017 Flexera Software LLC. All Rights Reserved.
Flexible License Manager status on Tue 5/15/2018 13:41

License server status: 7788@BVS15004
    License file(s) on BVS15004: licensing\license.dat:

  BVS15004: license server UP (MASTER) v11.12

Vendor daemon status (on BVS15004):

     ptc_d: UP v11.14.0

@VonOx  I added your case for testing. Please test if it works as intended. Thanks!


is there a way to use title on layout from front matter section?

let's say i have index.blade.php and have the following on top of the page
---
extends: _layouts.master
title: Hello World Page Title
---

my _layouts.master file looks like this
<html>
<head>
<title>{{ $page->title or '' }}</title>
</head>
<body>
@yield('body')
</body>
</html>

does it function/work this way because i can't get it to work or is it the wrong approach? how do i do something like that where i define the page's title on the page itself then apply it to the layout. if no value is given, empty string is displayed. thanks.

If you leave off the or '' part, it should work as expected.
$page is an object with dynamic properties, so using or (or isset) will always return true.  If $page->title is empty, it will automatically return null and won't error.
If you do want to specify a default for cases when title is empty, either do that in config.php, or echo {{ $page->title ?: 'The default title' }} in your template.

haha i guess i over engineered that one. thanks, that worked.


implement prefer-template lint rule

Continuing https://github.com/facebookexperimental/rome/issues/94. Working on prefer-template.  The repo currently has around 100 violations of this rule.  Still need to figure out how to autofix to avoid doing manually.  I think this seems doable if I can figure out how to map concat operands into stringTemplate quasis and expressions.

I opened https://github.com/facebookexperimental/rome/pull/157 which has the rule implemented without autofix and manual fixes to violations.


Fix the navbar to the top of the screen, so that it stays as you scroll down

It would be really cool if we could have the navbar look identical to how it is right now, but when you scroll, the navbar is 'fixed', or it scrolls with the page.

This is a "first-timers-only" issue. That means that we are requesting that only those new to open source try this one out! Please ask as many questions as you need, I am here to help you create your first contribution to open-source :D

Assigned to @iamajmalsaleem for #65! :D

Hello , please assign me this issue ,I am interested to work on this

@thatrobotdev please assign me this issue


Are models compatible with Promethion FLO-PRO002 flow cell?

Hi!
 I was recently testing out Megalodon for methylation calling, and to my great dismay found an issue on their github page explaining that it simply wasn't compatible with PromethION flow cells.
Now I am thinking of using nanopolish's call-methylation function instead. Do you know if it would work with this particular flow cell?
Thanks a lot!
Best regards,
Rene

Yes, nanopolish works with PromethION data.
Jared

On Dec 10, 2019, at 8:10 AM, snajder-r<EMAIL_ADDRESS>wrote:

Hi!
 I was recently testing out Megalodon for methylation calling, and to my great dismay found an issue on their github page explaining that it simply wasn't compatible with PromethION flow cells.
Now I am thinking of using nanopolish's call-methylation function instead. Do you know if it would work with this particular flow cell?
Thanks a lot!
Best regards,
Rene
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you so very much for your quick reply!


add comma

comma:
Reason for the change:
Link to original source:

Closes #

Hello @SendBord,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Adds A2 Trial License if none provided

Signed-off-by: Ruairi Fennell<EMAIL_ADDRESS>Description
Currently we ask the user to provide an A2 license in the Azure UI during setup. This change makes adding a License optional. If no license is added, a Trial License will be applied.
Without License:

With License:

@r-fennell does that GDPR flag get presented on the UI?

@trevorghess Yes


When Excel sheet tab names are numbers, read_excel finds those instead of using sheet as position

read_excel appears to be defaulting to looking for the sheet name but this causes a problem when sheet names are numbers themselves and I am actually asking Excel to use Sheet= as the position.

Probably related to #80 and #104

Until proven otherwise, I regard this as a duplicate of #104.


Fix otel/opentelemetry-collector-dev:latest is not backward compatible

What changes are proposed in this pull request?
Fix otel/opentelemetry-collector-dev:latest is not backward compatible using specific image tags as instructed in the original issue.
Fixes Alluxio/new-contributor-tasks#613.

@ddadaal is there a version tag we can use instead of hash value?

@yuzhu https://hub.docker.com/r/otel/opentelemetry-collector-dev/tags?page=1&name=b24db545eb56e2ee7dcf6a8f3740ce49bb80608b I don't think there is a tag to this hash.


Custom config for WP CLI

Submit a feature request or bug report

[x] I've read the guidelines for Contributing to Roots Projects
[x] This is a feature request
[x] I've read the docs and followed them (if applicable)

What is the current behavior?
I am not able to set custom configurations or my wp-cli. I need another DB Host (since I'm using Docker) for my (out-of-the-box) wp command.
What is the expected or desired behavior?
Changing the following in application.php:
/**
 * Use Dotenv to set required environment variables and load .env file in root
 */
if (WP_CLI === true) {
  $dotenv = new Dotenv\Dotenv($root_dir, '/.env.cli');
  if (file_exists($root_dir . '/.env.cli')) {
    $dotenv->load();
    $dotenv->required(['DB_NAME', 'DB_USER', 'DB_PASSWORD', 'WP_HOME', 'WP_SITEURL']);
  }
} else {
  $dotenv = new Dotenv\Dotenv($root_dir);
  if (file_exists($root_dir . '/.env')) {
    $dotenv->load();
    $dotenv->required(['DB_NAME', 'DB_USER', 'DB_PASSWORD', 'WP_HOME', 'WP_SITEURL']);
  }
}

This way I'm able to configure a custom .env.cli myself.
I am curious how you think about this. If this is a valid way of configuring I can work this out in better code in a PR.

You might be better off using WP-CLI aliases than this.

Hi @mAAdhaTTah, I don't see how WP-CLI aliases could work here for a different DB Host. Can you explain?

How about just setting the dotenv vars you want to change with environment variables before running wp-cli as phpdotenv will not override vars that are already set by default.
Something like this should work:
source .env.cli && wp ...

If that works then you could wrap that into a bash alias or something else to remove the repetition there.
Alternatively, you could add a require key to your project's wp-cli.yml file and load your cli-specific .env.cli file there
E.g.
path: web/wp/
require:
  - config/cli-bootstrap.php # create this file

config/cli-bootstrap.php
$root_dir = dirname(__DIR__);

if (file_exists($root_dir . '/.env.cli')) {
    require_once($root_dir . '/vendor/autoload.php');
    $dotenv = new Dotenv\Dotenv($root_dir, '/.env.cli');
    $dotenv->load();
    $dotenv->required(['DB_NAME', 'DB_USER', 'DB_PASSWORD', 'WP_HOME', 'WP_SITEURL']);
}

Untested, but should work

Thank you for your suggestions. Those should work and are cleaner ways. I can implement this locally, but are you guys interested in a PR to support custom config's for the WP CLI?

Sorry for the very late reply on this but we aren't interested in it at this time.


added guard for input change

relates to issue https://github.com/Alberplz/angular2-color-picker/issues/102
when selecting the whole input value and inserting new value, the dialog is undefined and error is thrown

This repository is no longer maintained. I recommend switching to https://github.com/zefoy/ngx-color-picker
It is mostly compatible with this repo, minus some bugs and plus some features.

can you update the readme with this info?


docs(README.md): Cambiar nombre

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Codecov link

Hi Kelvin,
Can you verify if you have the markdown txt from codecov? I will need it to update readme.md
Thanks

@KelvinPompey-40718390 Thank you for providing the token.


Fix: Add pcabreram1234's Portfolio.

Closes #195

@all-contributors please add @pcabreram1234 for code


Twitch authentication

Twitch authentication: https://dev.twitch.tv/docs/authentication

[ ] Figure out what type of authorization flow is required
[ ] Implement OAuth token fetch
[ ] Given an authorization code, retrieve the user's channel ID and start listening to the channel topic.

Both the authorization for the GET request to fetch the user's channel ID, and the LISTEN message to the websocket topic require user authorization. This is a manual step and cannot be done purely server side. This complicates things because we have to accept an authorization code, and go from there.
That being said, by making this take the authorization code granted by the user as input, this simplifies how to expand this project out to be used by more than one person ( #7 ) because the server component can accept incoming authorization codes and act on them.

Another piece of this is token validation. The tokens don't last very long - only a couple hours. This means that we need to implement refreshing the token

Another caveat - there are two different endpoints that need to get tokens. There is the v5 API, as well as the "new" Twitch API, with their own respective OAuth auth URLs.
Need to test to see if we are able to use just one URL for both tokens (possible 1 token with both required scopes?)

Proof of concept with a stored auth code here:
const fetch = require("node-fetch");
const WebSocket = require("ws");

// read in credentials
const credentials = require("./credentials.json")

// note: the way this is getting refactored, it assumes that the authorization
//       code already requested these scopes. Leaving this here for
//       documentation purposes, and as a sanity check on the OAuth token request.
const scopes = "channel_read+channel:read:redemptions";

// note: leaving this here so I don't have to fetch my channel ID all the time.
// const channelId = "106060203"

// connects to Twitch's WSS event stream for channel point redemptions
// TODO: figure out how to do the nonce better
function subscribeToChannelTopic(channelId, oauth_token) {

    function heartbeat() {
        message = {
            type: "PING",
        };
        console.log("SENT: " + JSON.stringify(message));
        ws.send(JSON.stringify(message));
    }
    var heartbeatInterval = 1000 * 60; //ms between PING's
    var reconnectInterval = 1000 * 3; //ms to wait before reconnect
    var heartbeatHandle;

    ws = new WebSocket("wss://pubsub-edge.twitch.tv");

    ws.onopen = function (event) {
        console.log("INFO: Socket Opened");
        heartbeat();
        heartbeatHandle = setInterval(heartbeat, heartbeatInterval);

        // When the connection is opened, fire a LISTEN event to the WSS
        let listenEvent = {
            type: "LISTEN",
            nonce: "abc123",
            data: {
                topics: [`channel-points-channel-v1.${channelId}`],
                auth_token: oauth_token
            },
        };
        ws.send(JSON.stringify(listenEvent));
    };

    ws.onerror = function (error) {
        console.log("ERR: " + JSON.stringify(error));
    };

    ws.onmessage = function (event) {
        // TODO: add Spotify integration here
        message = JSON.parse(event.data);
        console.log({ message });
        if (message.type == "RECONNECT") {
            console.log("INFO: Reconnecting...");
            setTimeout(subscribeToChannelTopic(channelId), reconnectInterval);
        }
    };

    ws.onclose = function () {
        console.log("INFO: Socket Closed");
        clearInterval(heartbeatHandle);
        console.log("INFO: Reconnecting...");
        setTimeout(subscribeToChannelTopic(channelId), reconnectInterval);
    };
}

/**
 * Get the OAuth token, given an authorization code
 * @param {*} clientId
 * @param {*} clientSecret
 * @param {*} authorizationCode
 */
async function retrieveToken(clientId, clientSecret, authorizationCode) {
    let response = await fetch(`https://id.twitch.tv/oauth2/token?client_id=${clientId}&client_secret=${clientSecret}&grant_type=authorization_code&code=${authorizationCode}&redirect_uri=https://github.com/SaxyPandaBear/TwitchSongRequests`, {
        method: "POST",
        mode: "cors"
    });
    return response.json();
}

async function getChannelId(client_id, oauth_token) {
    // note: this uses the deprecated v5 Twitch API
    let response = await fetch("https://api.twitch.tv/kraken/channel", {
        method: "GET",
        mode: "cors",
        headers: {
            "Accept": "application/vnd.twitchtv.v5+json",
            "Client-ID": client_id,
            "Authorization": `OAuth ${oauth_token}`
        }
    });
    return response.json();
}

// TODO: this works locally, but need to figure out how to accept authorization
//       codes as input server-side. For ease of use/iterations, I am storing
//       a manually fetched authorization code in my credentials file, and referencing
//       it here.
// this fetches the OAuth token, then connects to the WSS.
retrieveToken(credentials.twitch_client_id, credentials.twitch_client_secret, credentials.authorization_code)
    .then((oauth) => {
        // GET the channel ID to then feed as input to subscribe to the topic
        getChannelId(credentials.twitch_client_id, oauth.access_token).then((channel) => {
            let channelId = channel._id;
            subscribeToChannelTopic(channelId, oauth.access_token);
        });
    });

Now all that needs to be done is to figure out how to source this externally. This 100% requires some form of frontend component.

Closing this with the existence of a working POC. Will create a new issue for how to source the auth code


Support sprite animations spanning multiple rows

From feature request on SO:

I have a sprite sheet that has two rows for the same animation. Top row has 4, bottom has 3.
...
I can get it to work fine if I explicitly set each frame. It's not too bad for this one since I only have 7 of them.... but I also have some that have 100+!

Possible implementation is given in an answer.

Second request posted on forum


Fix: Helpers.IsSystemName was not used in loop through all the meshes

…from the first scene. Moreover, there was some code implementing the same functionality that the helper mentioned.

Thanks


Remove superflous text in the quickfix window

Whenever there are errors or warnings, the quickfix window contains some text at the very top like:
Reloading...
/path/to/file.hs
error - project-name

Followed by the actual useful data.
Can we remove those first lines to make the content cleaner?

mmm...
It's very sensibly!
But sorry, I like the original behavior :sob:
Because this is faithful to ghcid behavior.
I think this is kind for new comer...

I think this is kind for new comer

good point


Fix formatting regression

Bring formatting back on Windows. Regression in 0.6.0

Do you get an error when formatting on windows?

@axelson I simply can't format because the path can never match

@princemaple Can you give examples of the inputs that you're receiving for file_uri, project_dir, inputs?

I'm not sure how to log in elixir-ls directly, so I dove into sublime-lsp and logged everything out there.
From the json rpc logs I found:
rootUri: file:///C:/Users/chenp/code/project-name
projectDir: C:\\Users\\chenp\\code\\project-name
uri: file:///C:/Users/chenp/code/project-name/lib/app_web.ex
These should be the raw inputs that elixir-ls received.

FYI I set projectDir while testing different options. Previously it was null.

I've come to the conclusion that the bug is that Path.wildcard returns c:/ in lowercase.

Hi @lukaszsamson and @axelson I've sent https://github.com/elixir-lsp/elixir-ls/pull/375
Please take a look.

I've come to the conclusion that the bug is that Path.wildcard returns c:/ in lowercase.

Should we report it upstream? IMO Path module functions shouldn't mess with casing even on CI filesystems.

Should we report it upstream? IMO Path module functions shouldn't mess with casing even on CI filesystems.

Maybe.
It's hard to say what is the correct case to output C:/ in, since it's case insensitive 🤷♂
It's not really "messing" with casing, it just happens to be reporting in lower case. And lower cases works, too, if you use it to list dir or check file existence.
The real question is, is there a better way to compare path than string comparison.
It's a solved problem in many environments, e.g.

#375 replaces this one


Serialize long as 32 or 64 bit integer depending on platform

This would break exchanging data between platforms...
I guess any code that expects long to be 64 bit is sort of broken by default anyway. That said I agree that it would be better to always store long as 64 bits (with slightly different code), but a bit late for that now...

Thank you for a comment. The problem is that some external libraries work on int64_t from <cstdint> which is in fact defined as long. In U++ int64 is long long. Those types are incompatible if you work on templates. Sometimes I am enforced to use int64_t. It took me substantial amount of time why transferring data through U++ serialization resulted in serious problems. But it is ok. I will use my fork of ultimatepp in my applications. If you want you can close that PR.

That is a pretty valid argument.
I will keep thinking about it...
On Fri, Sep 6, 2024 at 6:50 PM Jakub Pawlewicz @.***>
wrote:

Thank you for a comment. The problem is that some external libraries work
on int64_t from  which is in fact defined as long. In U++ int64
is long long. Those types are incompatible if you work on templates.
Sometimes I am enforced to use int64_t. It took me substantial amount of
time why transferring data through U++ serialization resulted in serious
problems. But it is ok. I will use my fork of ultimatepp in my
applications. If you want you can close that PR.
—
Reply to this email directly, view it on GitHub
https://github.com/ultimatepp/ultimatepp/pull/204#issuecomment-2334453033,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARH234IZXA42HJ5JTB47FDZVHMO7AVCNFSM6AAAAABNYYLCR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGQ2TGMBTGM
.
You are receiving this because you commented.Message ID:
@.***>

Well, I think I have sort of solid solution evolving for this after all...
The plan is

actually remove operator%(long &) - this will make sure that no legace code breaks - developer will just be forced to use the new method. At the same time, it is also very unlikely that any 'normal' longs were ever serialised
replace with method Serialize64(long&). I guess should not be a problem for you to call that instead.

Probably also supply Serialize8/16/32/64 for all other types as synonymes, esp. int32_t and int64_t
Yep, a bit trivial solution compared to the time that has taken me to consider it, but I guess the only sound one.
What do you think?
Mirek

Huh, removing operator% breaks some implementation from Core for instance StreamContainer which is used in Vector::Serialize().
Vector<int64_t> should be serializable.

Ah, thanks, good point. Back to drawing board...
On Mon, Oct 21, 2024 at 4:37 PM Jakub Pawlewicz @.***>
wrote:

Huh, removing operator% breaks some implementation from Core for instance
StreamContainer which is used in Vector::Serialize().
Vector<int64_t> should be serializable.
—
Reply to this email directly, view it on GitHub
https://github.com/ultimatepp/ultimatepp/pull/204#issuecomment-2426876883,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARH2364FPLQUGE37QETQP3Z4UGTVAVCNFSM6AAAAABNYYLCR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWHA3TMOBYGM
.
You are receiving this because you commented.Message ID:
@.***>


Add a FreeMonitor platform API

This fix the leak of a wl_output object everytime a monitor is freed.
I haven’t checked whether other winsys need a similar custom free() (valgrind is helpful at that), but it shouldn’t hurt to add them later.

Looks good.


tests do not clean up the environment after execution

There seem to be two issues with running pycsw's test suites using paver:
paver test

The test runner starts up a local pycsw instance running on port 8000. However, it does not stop it when the tests finish.

The sqlite3 database at tests/suites/cite/data/records.db is modified by the tests and is not restored to its original state afterwards. This causes git to want to include it in commits.

@ricardogsilva thanks for the report.  Comments:

perhaps adding call_task('stop') at the end of paver test`?
iirc, I think this is not cleaned up at the end of the test so devs can inspect the database after if required. We include the cite SQLite3 DB by default to give users something default as a bootstrap and for CITE reference implementation.  I do agree it is annoying and cumbersome to have git want to include it and is error prone for git commit -am type things.  Some options on how to deal with this:

cleanup/reset the DB after testing with call_task('reset')
rename the default cite DB to tests/suites/cite/data/records.db to tests/suites/cite/data/cite.db and this never clashes
others?

git commit -am is not very wise ;)

@ricardogsilva fixed with option 2 via #370 let me know if this works for you?

Hi @kralidis
I am currently on holidays until the second week of September. I'll get back to this then ;)

Hi Tom
I'll test this out tonight (or tomorrow) and report back, or close. Thanks!

@ricardogsilva should we close this?

Yes, this is fixed now. Thanks @tomkralidis


cleanup composer.json

@tmatsuo could you merge it first?
no changes in versions

LG, merging

thx


Temporary files

Hi Philippe and Eric !
I run multi independent launches of Parcels on a cluster (one submission is realized over 4 nodes of 32 processors = 128 Parcels processes at one time), and I am experiencing a saturation of the /tmp directory (limited to 4go on each node) for some of them.
The issue is linked to size of the  "/tmp/parcels-911" directory.  I need some time to investigate on that, but :
1/ Is there a way to specify where those temporary files should be written, or is this hard coded ?
2/ Could you confirm that those temporary files are deleted after each run ? In this case a saturation should not be reached for my application I suppose (each process is quite light).
root@node-01 tmp]# ll | more
total 76060
-rw------- 1 slawchune mercator  381152 Nov  6 02:34 cc01b3e1.o
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc01Fq7L.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc01Q9bb.s
-rw------- 1 slawchune mercator  639518 Nov  6 01:02 cc09gmLV.s
-rw------- 1 slawchune mercator       0 Nov  6 03:11 cc0Chajq.s
-rw------- 1 slawchune mercator       0 Nov  6 03:09 cc0ef5dB.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0f6PaY.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0HGPRH.s
-rw------- 1 slawchune mercator   20480 Nov  6 03:08 cc0JaKzr.out
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0Jl1fc.s
-rw------- 1 slawchune mercator       0 Nov  6 03:09 cc0Ki25K.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0LH1Vk.out
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0oC2sp.out
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0QC9jN.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0Rc7va.s
-rw------- 1 slawchune mercator  118784 Nov  6 03:08 cc0sBOBs.s
-rw------- 1 slawchune mercator       0 Nov  6 03:09 cc0tStHy.s
-rw------- 1 slawchune mercator       0 Nov  6 03:54 cc0WiFqS.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc0xZ3r8.err
-rw------- 1 slawchune mercator       0 Nov  6 03:32 cc10ibgr.s
-rw------- 1 slawchune mercator  586239 Nov  6 03:08 cc14BeEZ.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc1587A2.err
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc15BmLs.out
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc15IS7V.err
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cc16Gln8.out
....

-rw------- 1 slawchune mercator       0 Nov  6 03:53 ccZzMlFk.s
-rw------- 1 slawchune mercator       0 Nov  6 03:32 cczZPC1d.s
-rw------- 1 slawchune mercator       0 Nov  6 03:08 cczZpQVn.err
drwx------ 2 root      root       16384 Mar 21  2018 lost+found
drwx------ 6 jchanut   mercator    4096 Nov  5 19:12 ompi.node-01.579
drwxr-xr-x 2 slawchune mercator 4001792 Nov  6 03:08 parcels-911
drwx------ 3 root      root        4096 Jun 22 16:00 systemd-private-1efd34c08b6a482ba7ef445b7f06af15-ntpd.s
ervice-e4bS7q

Here is the error I get in the log file  :
_"""
Traceback (most recent call last):
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/compiler.py", line 46, in compile
    subprocess.check_call(cc, stdout=logfile, stderr=logfile)
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/subprocess.py", line 271, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['gcc', '-Wall', '-fPIC', '-I/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/include', '-g', '-O3', '-m64', '-o', '/var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.so', '/var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.c', '-shared', '-m64']' returned non-zero exit status -6

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 47, in starmapstar
    return list(itertools.starmap(args[0], args[1]))
  File "/data/rd_exchange2/slawchune/SMOC_CMEMS/Validation/Parcels/Validation/launch_parcels.py", line 110, in launch_parcels
    recovery={ErrorCode.ErrorOutOfBounds: DeleteParticle} # handle out of domain particle
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/particleset.py", line 279, in execute
    self.kernel.compile(compiler=GNUCompiler())
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/kernel.py", line 159, in compile
    compiler.compile(self.src_file, self.lib_file, self.log_file)
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/compiler.py", line 59, in compile
    raise RuntimeError(err)
RuntimeError: Error during compilation:
Compilation command: gcc -Wall -fPIC -I/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/include -g -O3 -m64 -o /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.so /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.c -shared -m64
Source file: /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.c
Log file: /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.log

Log output: Cannot create temporary file in /tmp/: No space left on device

"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "multi_subprocesses_parcels.py", line 64, in <module>
    multi_subprocess_parcels(load_arg_sheet_file)
  File "multi_subprocesses_parcels.py", line 45, in multi_subprocess_parcels
    results = pool.starmap( launch_parcels.launch_parcels, args_array)
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 274, in starmap
    return self._map_async(func, iterable, starmapstar, chunksize).get()
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 644, in get
    raise self._value
RuntimeError: Error during compilation:
Compilation command: gcc -Wall -fPIC -I/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/include -g -O3 -m64 -o /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.so /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.c -shared -m64
Source file: /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.c
Log file: /var/tmp/parcels-911/3ee783d36e155b01651a4eb86e5b3743.log

Log output: Cannot create temporary file in /tmp/: No space left on device_

Thank you for your lights !

That all this is written to a subdir of /tmp/ is decided here:
https://github.com/OceanParcels/parcels/blob/6ccb27c2baae52610a02f9d8dc560367c40766b2/parcels/compiler.py#L3
https://github.com/OceanParcels/parcels/blob/6ccb27c2baae52610a02f9d8dc560367c40766b2/parcels/compiler.py#L22
and then passed on to
https://github.com/OceanParcels/parcels/blob/1a4251ce3ba496c3304958fdd4405fd3661ad695/parcels/kernel.py#L2
and
https://github.com/OceanParcels/parcels/blob/1a4251ce3ba496c3304958fdd4405fd3661ad695/parcels/rng.py#L1
Luckily, the underlying tempfile.gettempdir() checks a bunch of env vars to decide where to go: https://docs.python.org/3/library/tempfile.html#tempfile.gettempdir
You should be able to choose whatever place you want by setting, e.g., TMPDIR to a bigger device:
from os import environ
os.environ["TMPFILE"] = "/path/to/bigger/place/"

Oh that's great ! thank you !

Thanks !
I have changed the "tempfile.tempdir" to '/kara/data1/slawchune/tmp/', a disk space where all nodes can I/O. My temporary files are now well written where I want, but I still get an error :
 INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/73771dde0688b7dc73d842042ae32be8.so INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/fd9da2746e4fab6367706d60a83a7cc3.so INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/fd9da2746e4fab6367706d60a83a7cc3.so multiprocessing.pool.RemoteTraceback: """ Traceback (most recent call last):   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 119, in worker     result = (True, func(*args, **kwds))   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 47, in starmapstar     return list(itertools.starmap(args[0], args[1]))   File "/data/rd_exchange2/slawchune/SMOC_CMEMS/Validation/Parcels/Validation/launch_parcels.py", line 116, in launch_parcels     recovery={ErrorCode.ErrorOutOfBounds: DeleteParticle} # handle out of domain particle   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/particleset.py", line 280, in execute     self.kernel.load_lib()   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/kernel.py", line 163, in load_lib     self._lib = npct.load_library(self.lib_file, '.')   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/site-packages/numpy/ctypeslib.py", line 150, in load_library     return ctypes.cdll[libpath]   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/ctypes/__init__.py", line 426, in __getitem__     return getattr(self, name)   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/ctypes/__init__.py", line 421, in __getattr__     dll = self._dlltype(name)   File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/ctypes/__init__.py", line 351, in __init__     self._handle = _dlopen(self._name, mode) OSError: /kara/data1/slawchune/tmp/parcels-911/fd9da2746e4fab6367706d60a83a7cc3.so: invalid ELF header """
I have googled "invalid ELF header" and it seemed related to issues with share libraries.
Previously, when I wrote the temporary files directly on the /tmp/ of the concerned node, I also felt on some "file too short" for those temporary files on opening. Those errors are not produced on the master node, only for the slave ones. Was this ever experienced by other users ?

Here is the error, but it only happens sometimes, not always. I feel like it's related to our cluster's file system configuration I will let you know if I have some news. Thanks !
The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "multi_subprocesses_parcels.py", line 64, in <module>
    multi_subprocess_parcels(load_arg_sheet_file)
  File "multi_subprocesses_parcels.py", line 45, in multi_subprocess_parcels
    results = pool.starmap( launch_parcels.launch_parcels, args_array)
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 274, in starmap
    return self._map_async(func, iterable, starmapstar, chunksize).get()
  File "/home/slawchune/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 644, in get
    raise self._value
OSError: /kara/data1/slawchune/tmp/parcels-911/a4210cb927480a3e666f6b113700d2bf.so: file too short
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/d69c534f89c3bf2e2039f8b73d4916f1.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/47a14d0592be2b42570a52e54c796f02.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/3f53bd58cebc067709f92aacbdc09e96.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/79e5c350b41740a59bac7742a6808c37.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/b9fa2948ebf9e23e45660ce912cddc7e.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/a22d5dbaeb2d72cd2a064b35c74aca55.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/38cbf100d402ce58b43dd68e6364e746.so
INFO: Compiled JITParticleAdvectionRK4periodicBC ==> /kara/data1/slawchune/tmp/parcels-911/e107fe52185e47e4f791b4364a5c89b6.so

Hi @slawchune, is there any news on the temporary files? Is it, as you expected, related to your cluster's file system? Or something on the Parcels side?

As we haven't heard anything for a while on the status of this issue, I'm assuming it's fixed and am now closing this issue

Hi Eric and Phillip,
Really sorry, I was monopolized by urgent tasks and I had to leave aside this activity with Parcels for several months.
I've been trying to figured out again what's not working this week.  I haven't really been able to put my finger on something new. The behaviour is the same on the Meteo-France's cluster (beaufix) as on our own cluster in Mercator (kara).
From what I understood in my previous tests, it is also related to a problem with compiling a C library on the fly when calling "particleset.py" by a pool.map. In the example bellow, the compiled library that is not working (File too short error) is  "/scratch/utmp/slurm/lawchunes.63079613/parcels-10736/e3778962831448f72c46ef78d9064e9f.so"
The thing is, I do this operation on a large number of processes. But I checked, there is no difference in memory size between the".so" files that don't work, and the ones that work. There doesn't seem to be any upstream problems either.
It's always random, and the only solution I found was finally to resubmit the execution until it works. Fortunately, submissions work more often than they crash.
message : multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 119, in worker
result = (True, func(*args, **kwds))
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/home/ext/mr/smer/lawchunes/SAVE/SMOC/Validation/SCRIPTS/launch_parcels.py", line 45, in launch_parcels_one_arg
total_time_drift, file_out, id_buoy)
File "/home/ext/mr/smer/lawchunes/SAVE/SMOC/Validation/SCRIPTS/launch_parcels.py", line 143, in launch_parcels
recovery={ErrorCode.ErrorOutOfBounds: DeleteParticle} # handle out of domain particle
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/particleset.py", line 280, in execute
self.kernel.load_lib()
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/kernel.py", line 163, in load_lib
self._lib = npct.load_library(self.lib_file, '.')
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/numpy/ctypeslib.py", line 150, in load_library
return ctypes.cdll[libpath]
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/ctypes/init.py", line 426, in getitem
return getattr(self, name)
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/ctypes/init.py", line 421, in getattr
dll = self._dlltype(name)
File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/ctypes/init.py", line 351, in init
self._handle = _dlopen(self._name, mode)
OSError: /scratch/utmp/slurm/lawchunes.63079613/parcels-10736/e3778962831448f72c46ef78d9064e9f.so: file too short
"""

Here is the detail error regarding the C compilation. maybe I Misunderstood, but the.so files are compiled on the fly by a C library that the cluster can't share in subprocesses.D oes that mean more to you?
"""
Traceback (most recent call last):
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/compiler.py", line 49, in compile
    subprocess.check_call(cc, stdout=logfile, stderr=logfile)
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/subprocess.py", line 266, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/subprocess.py", line 247, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/subprocess.py", line 676, in __init__
    restore_signals, start_new_session)
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/subprocess.py", line 1228, in _execute_child
    restore_signals, start_new_session, preexec_fn)
BlockingIOError: [Errno 11] Resource temporarily unavailable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/home/ext/mr/smer/lawchunes/SAVE/SMOC/Validation/SCRIPTS/launch_parcels.py", line 50, in launch_parcels_one_arg
    total_time_drift, file_out, id_buoy, add_windage, ln_drogue_off)
  File "/home/ext/mr/smer/lawchunes/SAVE/SMOC/Validation/SCRIPTS/launch_parcels.py", line 199, in launch_parcels
    recovery={ErrorCode.ErrorOutOfBounds: DeleteParticle} # handle out of domain particle
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/particleset.py", line 319, in execute
    self.kernel.compile(compiler=GNUCompiler(cppargs=cppargs))
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/kernel.py", line 178, in compile
    compiler.compile(self.src_file, self.lib_file, self.log_file)
  File "/home/ext/mr/smer/lawchunes/miniconda2/envs/env_py35/lib/python3.5/site-packages/parcels/compiler.py", line 53, in compile
    raise RuntimeError(err)
RuntimeError: OSError during compilation
Please check if compiler exists: gcc
"""


Allow custom params to ykfde-open

Hi,
Thanks for this project,
I'm trying to use luks detached header, and so come this little patch.
This add the support of misc parameters to ykfde-open. This is already good for ykfde-format.
Example:

To be able to use a detached header:

ykfde-open -d /dev/sda2 -n luks -- --header /dev/sdb1

We can also pass more luks parameters if needed.
Regards

Hi,
I can't test try right now, but should be ok. :)