Issue with Redis pipelining?

PGSync version: 2.1.10
Postgres version: 13.4
Elasticsearch version: 7.15.0
Redis version: 6.2
Python version: 3.7
Problem Description:
Using multiple schemas in single config. Initial load works great. Normal sync runs fine for a while until a large influx of records come through and pgsync enters a broken state. Once in this state, the queue stops being processed and the Redis pending continuously grows. The bulk pop pipeline does not pull any records from the queue (nor does it trim). However, executing a lrange manually will return results.
Error Message (if any):
2022-01-25 22:26:16.535:INFO:elasticsearch: POST https://es:9200/something-1/_search?scroll=5m&size=1000 [status:200 request:0.142s]
2022-01-25 22:26:16.576:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0
2022-01-25 22:26:16.617:INFO:elasticsearch: DELETE https://es:9200/_search/scroll [status:200 request:0.142s]
2022-01-25 22:26:16.619:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0
2022-01-25 22:26:16.677:INFO:elasticsearch: DELETE https://es:9200/_search/scroll [status:200 request:0.141s]
2022-01-25 22:26:16.679:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0
2022-01-25 22:26:16.720:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0
2022-01-25 22:26:16.762:INFO:elasticsearch: POST https://es:9200/something-2/_search?scroll=5m&size=1000 [status:200 request:0.143s]
2022-01-25 22:26:16.780:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0
Syncing something Xlog: [91] => Db: [12,489] => Redis: [total = 1,131 pending = 11,358] => Elastic: [6,570] ...
Syncing something Xlog: [4] => Db: [12,489] => Redis: [total = 12,489 pending = 0] => Elastic: [56] ...
2022-01-25 22:26:16.820:INFO:elasticsearch: POST https://es:9200/something-1/_search?scroll=5m&size=1000 [status:200 request:0.143s]
Syncing something Xlog: [37] => Db: [12,489] => Redis: [total = 10,578 pending = 1,911] => Elastic: [136] ...
2022-01-25 22:26:16.822:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0

Strange: bulk_pop nsize: 0. Could be a red herring... Redis poller thread handling the index in question could have died?
Querying queue directly on Redis server:
<IP_ADDRESS>:6379> llen queue:something2
(integer) 11358

Seems to work fine with a single schema.

Scratch that, problem remains even with single index
Syncing db Xlog: [22] => Db: [3,142] => Redis: [total = 1,001 pending = 2,141] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,142] => Redis: [total = 1,001 pending = 2,141] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,142] => Redis: [total = 1,001 pending = 2,141] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,177] => Redis: [total = 1,001 pending = 2,177] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,250] => Redis: [total = 1,001 pending = 2,250] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,311] => Redis: [total = 1,001 pending = 2,311] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,392] => Redis: [total = 1,001 pending = 2,393] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [3,741] => Redis: [total = 1,001 pending = 2,741] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [4,573] => Redis: [total = 1,001 pending = 3,573] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [5,139] => Redis: [total = 1,001 pending = 4,138] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [5,605] => Redis: [total = 1,001 pending = 4,604] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [6,178] => Redis: [total = 1,001 pending = 5,178] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [6,674] => Redis: [total = 1,001 pending = 5,674] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,612] => Redis: [total = 1,001 pending = 6,611] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [7,631] => Redis: [total = 1,001 pending = 6,631] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [8,366] => Redis: [total = 1,001 pending = 7,366] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [9,037] => Redis: [total = 1,001 pending = 8,036] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [9,734] => Redis: [total = 1,001 pending = 8,733] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [10,185] => Redis: [total = 1,001 pending = 9,184] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [10,585] => Redis: [total = 1,001 pending = 9,584] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [10,962] => Redis: [total = 1,001 pending = 9,961] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,239] => Redis: [total = 1,001 pending = 10,239] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,295] => Redis: [total = 1,001 pending = 10,295] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,330] => Redis: [total = 1,001 pending = 10,329] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,330] => Redis: [total = 1,001 pending = 10,329] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,330] => Redis: [total = 1,001 pending = 10,329] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,448] => Redis: [total = 1,001 pending = 10,447] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [11,807] => Redis: [total = 1,001 pending = 10,807] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [12,171] => Redis: [total = 1,001 pending = 11,170] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [12,262] => Redis: [total = 1,001 pending = 11,262] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [12,907] => Redis: [total = 1,001 pending = 11,906] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [13,268] => Redis: [total = 1,001 pending = 12,267] => Elastic: [26,680] ...
Syncing db Xlog: [22] => Db: [13,633] => Redis: [total = 1,001 pending = 12,632] => Elastic: [26,680] ...
2022-01-26 19:14:02.229:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.957s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [27,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [27,680] ...
2022-01-26 19:14:04.716:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.944s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [28,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [28,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [28,680] ...
2022-01-26 19:14:07.480:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.954s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [29,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [29,680] ...
2022-01-26 19:14:09.802:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.008s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [30,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [30,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [30,680] ...
2022-01-26 19:14:12.506:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.966s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [31,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [31,680] ...
2022-01-26 19:14:14.868:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.975s]
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [32,680] ...
Syncing db Xlog: [22] => Db: [13,927] => Redis: [total = 1,001 pending = 12,926] => Elastic: [32,680] ...
Syncing db Xlog: [22] => Db: [14,006] => Redis: [total = 1,001 pending = 13,005] => Elastic: [32,680] ...
2022-01-26 19:14:17.468:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.125s]
Syncing db Xlog: [22] => Db: [14,139] => Redis: [total = 1,001 pending = 13,139] => Elastic: [33,680] ...
Syncing db Xlog: [22] => Db: [14,676] => Redis: [total = 1,001 pending = 13,675] => Elastic: [33,680] ...
Syncing db Xlog: [22] => Db: [15,004] => Redis: [total = 1,001 pending = 14,004] => Elastic: [33,680] ...
Syncing db Xlog: [22] => Db: [15,413] => Redis: [total = 1,001 pending = 14,412] => Elastic: [33,680] ...
2022-01-26 19:14:21.607:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.373s]
Syncing db Xlog: [22] => Db: [15,697] => Redis: [total = 1,001 pending = 14,697] => Elastic: [34,680] ...
Syncing db Xlog: [22] => Db: [16,005] => Redis: [total = 1,001 pending = 15,005] => Elastic: [34,680] ...
Syncing db Xlog: [22] => Db: [16,484] => Redis: [total = 1,001 pending = 15,483] => Elastic: [34,680] ...
2022-01-26 19:14:24.462:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.183s]
Syncing db Xlog: [22] => Db: [16,484] => Redis: [total = 1,001 pending = 15,483] => Elastic: [35,680] ...
Syncing db Xlog: [22] => Db: [16,484] => Redis: [total = 1,001 pending = 15,483] => Elastic: [35,680] ...
2022-01-26 19:14:26.794:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.085s]
Syncing db Xlog: [22] => Db: [16,484] => Redis: [total = 1,001 pending = 15,483] => Elastic: [36,680] ...
Syncing db Xlog: [22] => Db: [16,484] => Redis: [total = 1,001 pending = 15,483] => Elastic: [36,680] ...
Syncing db Xlog: [22] => Db: [16,548] => Redis: [total = 1,001 pending = 15,547] => Elastic: [36,680] ...
2022-01-26 19:14:29.603:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.005s]
Syncing db Xlog: [22] => Db: [16,826] => Redis: [total = 1,001 pending = 15,826] => Elastic: [37,680] ...
Syncing db Xlog: [22] => Db: [17,201] => Redis: [total = 1,001 pending = 16,200] => Elastic: [37,680] ...
Syncing db Xlog: [22] => Db: [17,529] => Redis: [total = 1,001 pending = 16,528] => Elastic: [37,680] ...
2022-01-26 19:14:33.289:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.013s]
Syncing db Xlog: [22] => Db: [17,796] => Redis: [total = 1,001 pending = 16,796] => Elastic: [38,680] ...
Syncing db Xlog: [22] => Db: [18,153] => Redis: [total = 1,001 pending = 17,153] => Elastic: [38,680] ...
Syncing db Xlog: [22] => Db: [18,482] => Redis: [total = 1,001 pending = 17,483] => Elastic: [38,680] ...
Syncing db Xlog: [22] => Db: [18,689] => Redis: [total = 1,001 pending = 17,689] => Elastic: [38,680] ...
Syncing db Xlog: [22] => Db: [18,975] => Redis: [total = 1,001 pending = 17,974] => Elastic: [38,680] ...
2022-01-26 19:14:38.202:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.991s]
Syncing db Xlog: [22] => Db: [19,378] => Redis: [total = 1,001 pending = 18,379] => Elastic: [39,680] ...
Syncing db Xlog: [22] => Db: [19,970] => Redis: [total = 1,001 pending = 18,970] => Elastic: [39,680] ...
Syncing db Xlog: [22] => Db: [20,731] => Redis: [total = 1,001 pending = 19,730] => Elastic: [39,680] ...
Syncing db Xlog: [22] => Db: [21,255] => Redis: [total = 1,001 pending = 20,255] => Elastic: [39,680] ...
2022-01-26 19:14:41.999:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:0.979s]
Syncing db Xlog: [22] => Db: [21,647] => Redis: [total = 1,001 pending = 20,647] => Elastic: [40,680] ...
Syncing db Xlog: [22] => Db: [22,286] => Redis: [total = 1,001 pending = 21,286] => Elastic: [40,680] ...
Syncing db Xlog: [22] => Db: [23,198] => Redis: [total = 1,001 pending = 22,198] => Elastic: [40,680] ...
Syncing db Xlog: [22] => Db: [24,012] => Redis: [total = 1,001 pending = 23,012] => Elastic: [40,680] ...
2022-01-26 19:14:46.546:INFO:elasticsearch: POST https://es:9200/db-idx/_bulk?refresh=false [status:200 request:1.035s]
Syncing db Xlog: [22] => Db: [24,493] => Redis: [total = 1,001 pending = 23,493] => Elastic: [41,680] ...
Syncing db Xlog: [22] => Db: [25,334] => Redis: [total = 1,001 pending = 24,334] => Elastic: [41,680] ...

Is this issue easily reproducible from your end?
Perhaps we can introduce some logging to narrow down the cause.

Yes, this happens always. Let me know what you'd like to patch in for logging.

Can you add some logging into this method such as:
def bulk_pop(self, chunk_size: Optional[int] = None) -> List[dict]:
    """Remove and return multiple items from the queue."""
    chunk_size: int = chunk_size or REDIS_CHUNK_SIZE
    pipeline = self.__db.pipeline()
    print(f'pipe {chunk_size}')
    pipeline.lrange(self.key, 0, chunk_size - 1)
    print(f'range: {chunk_size - 1}')
    pipeline.ltrim(self.key, chunk_size, -1)
    print(f'ltrim: {chunk_size}')
    items: List[List[bytes], bool] = pipeline.execute()
    logger.debug(f"bulk_pop nsize: {len(items[0])}")
    print(f"bulk_pop nsize: {len(items[0])}"}
    return list(map(lambda x: json.loads(x), items[0]))

and send the output ?

Absolutely.
I will get this for you ASAP, likely tomorrow morning.
Thank you!

Attached is a full run.
You can see there's one tick with bulk_pop nsize: 1000 and then bulk_pop never seems to be called again.
log.txt

Scratch that, bulk_pop is being called again.... but almost exactly at 15 minutes intervals...

Here is my Env config
ELASTICSEARCH_TIMEOUT=60
ELASTICSEARCH_TIMEOUT=600
ELASTICSEARCH_QUEUE_SIZE=4
ELASTICSEARCH_THREAD_COUNT=4
QUERY_CHUNK_SIZE=5000
ELASTICSEARCH_CHUNK_SIZE=1000
ELASTICSEARCH_STREAMING_BULK=False
REDIS_POLL_INTERVAL=0.01

Just to note, I've experimented a bit with the configuration without luck. Even with REDIS_CHUNK_SIZE=10000 it seems that the bulk_pop, processing of the records, and insertion of the documents in to ES happen near instantaneous. I am unable to figure out what is happening between ticks.

are you running this in docker?
are we sure there is no env var defined somehwere in the config?
The fact that this is being called at intervals of 15 mins leads me to suspect REDIS_POLL_INTERVAL is in use.
Can you experiment with changing REDIS_POLL_INTERVAL to a low value like 10 secs and see the impact.
Perhaps even printing out the value of REDIS_POLL_INTERVAL on statrup

This is being run in docker. The interval appears to change proportionally with REDIS_CHUNK_SIZE
I will experiment changing REDIS_POLL_INTERVAL

Changing REDIS_POLL_INTERVAL does not seem to make a difference. I am seeing a large amount of these POST and DELETE requests (seen below) that happen in between bulk_pop. I am not familiar with the ES library, but from a quick glance, these appear to be internal functions of the ES library you're using. I've tried both ELASTICSEARCH_STREAMING_BULK True and False and many different values for ELASTICSEARCH_CHUNK_SIZE (between 1 and 100000) without any luck.  They will eventually process, but it may take 10 minutes or longer for each full scan to complete before the next tick to process the queue.
Are there any optimizations that can be made to reduce the amount of data scanned?
Can we make the scan page size configurable?
Can this process be entirely disabled if running in standalone mode?
Can we add extra concurrency at any of these blocking processes?

Sorta the same problem on my side as well. During the initial data loading/snapshot, with debug log enabled, There are only logs for elastic search POST API calls, nothing about Redis. Then after the document count reaches the expected count (~236million), then there is just continuous spam of 2022-04-26 05:40:24.669:DEBUG:pgsync.redisqueue: bulk_pop nsize: 0, Like 100's of times per second.

@jpughcs @toluaina could the issue be due to the Redis version? you are using 6.2 and I am trying with 5.0.5, while the documentation says 3.1.0.

what I see now is that my Redis is basically blank, There are no keys at all. This during the initial loading. I don't get what is wrong. There are no errors related to Redis in debug log at all except 2022-04-26 11:23:25.939:DEBUG:pgsync.urls: Connecting to Redis without password.

@jpughcs @toluaina could the issue be due to the Redis version? you are using 6.2 and I am trying with 5.0.5, while the documentation says 3.1.0.

I've tried 3.x, 5.x, 6.x
I don't think the root of my issue is necessarily related to Redis. I've been using a workaround successfully, removing these three lines (the first one here is the culprit: the post-batch, catch-up sync), which allows me to essentially just schedule a full sync every five minutes or so. This hammers ES pretty hard, but it works for me in the meantime as my document count is relatively low and there's no need (yet) to have near-realtime updates. I don't think this will work for you with ~236 million records :( unless you just need to batch load your data and call it a day.


Sieve of Atkin

fix #5139

@sairish2001 I think that this can come under Level 3 as I have added 50 lines of code....That is just a suggestion
Thank You

@sairish2001 I think that this can come under Level 3 as I have added 50 lines of code....That is just a suggestion
Thank You

Rule has changed for this Repository and one more repository related with DSA.
No PR will be of Level3 and all the PR's merged before ,levels for that will be reduced by 1. like for level3 -> level2... level2-> level1....like wise

@sairish2001 is that neo algo?? the other repo?


Remove round to 2 decimals

Issue:
width: 70px; // now transforms to width: 4.38rem
which in reality is 70.08px
so if the round would return the full value like 4.375rem the final value would be 70px.
base px: 16.

I have updated the plugin and now there should not have this problem.
Thanks !!!


unknown field Env in struct literal of type wasm.Runner

Version
1.21.0
What happened?
First time I ran go install github.com/sqlc-dev/sqlc/cmd/sqlc@latest
but download is not completed.
github.com/sqlc-dev/sqlc/internal/cmd
C:\Users........\go\pkg\mod\github.com\sqlc-dev\sqlc@v1.21.0\internal\cmd\generate.go:395:5: unknown field Env in struct literal of type wasm.Runner
Relevant log output
> go install github.com/sqlc-dev/sqlc/cmd/sqlc@latest
go: downloading github.com/sqlc-dev/sqlc v1.21.0
go: downloading github.com/cubicdaiya/gonp v1.0.4
go: downloading github.com/google/cel-go v0.18.0
go: downloading github.com/jackc/pgx/v5 v5.4.3
go: downloading github.com/mattn/go-sqlite3 v1.14.17
go: downloading github.com/spf13/cobra v1.7.0
go: downloading google.golang.org/grpc v1.57.0
go: downloading google.golang.org/protobuf v1.31.0
go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20230803162519-f966b187b2e5
go: downloading golang.org/x/text v0.12.0
go: downloading github.com/riza-io/grpc-go v0.2.0
go: downloading github.com/inconshreveable/mousetrap v1.1.0
go: downloading github.com/jackc/pgpassfile v1.0.0
go: downloading github.com/jackc/pgservicefile v0.0.0-20221227161230-091c0ba34f0a
go: downloading golang.org/x/crypto v0.9.0
go: downloading github.com/stoewer/go-strcase v1.2.0
go: downloading github.com/antlr/antlr4/runtime/Go/antlr/v4 v4.0.0-20230321174746-8dcc6526cfb1
go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20230803162519-f966b187b2e5
go: downloading github.com/jinzhu/inflection v1.0.0
go: downloading github.com/pingcap/tidb/parser v0.0.0-20230815160630-b69fa21942d1
go: downloading golang.org/x/net v0.10.0
go: downloading github.com/golang/protobuf v1.5.3
go: downloading golang.org/x/exp v0.0.0-20230724220655-d98519c11495
go: downloading github.com/pingcap/errors v0.11.5-0.20210425183316-da1aaba5fb63
go: downloading github.com/pingcap/failpoint v0.0.0-20220801062533-2eaa32854a6c
go: downloading github.com/pingcap/log v1.1.0
go: downloading github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec
go: downloading go.uber.org/atomic v1.11.0
go: downloading go.uber.org/zap v1.25.0
go: downloading gopkg.in/natefinch/lumberjack.v2 v2.2.1
go: downloading github.com/benbjohnson/clock v1.3.5
go: downloading go.uber.org/multierr v1.11.0
# github.com/sqlc-dev/sqlc/internal/cmd
C:\Users\.....\go\pkg\mod\github.com\sqlc-dev\sqlc@v1.21.0\internal\cmd\generate.go:395:5: unknown field Env in struct literal of type wasm.Runner

Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
No response
What operating system are you using?
Windows
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

Fixed in https://github.com/sqlc-dev/sqlc/pull/2725
Before the next release, please run go install github.com/sqlc-dev/sqlc/cmd/sqlc@main


Add freeze and thaw functionality to spl-token cli

Add ability to initialize mint with freeze authority (set to same as mint authority for now; SetAuthority work as part of #502 will allow greater control)
Add freeze and thaw subcommands to cli app
Add "frozen" marker to accounts output, when relevant

Fixes #365
Toward #502

The only minor nit I have is wrt. the user needing to provide the mint address to freeze/thaw. It's an extra RPC call but from the token account address itself the mint can be determined without the user -- solana freeze blah account then gets reduced to solana freeze account

Completely fair, will update. I was trying to stay consistent with mint-to... I'm a little torn about the need for the mint address param in mint-to subcommand, but it definitely makes more sense in that case.

The only minor nit I have is wrt. the user needing to provide the mint address to freeze/thaw. It's an extra RPC call but from the token account address itself the mint can be determined without the user -- solana freeze blah account then gets reduced to solana freeze account

Actually, this will be much easier once solana-client v1.3.12+ is published, using: https://github.com/solana-labs/solana/blob/64af7127234ee0510cae3adfa18271ba437672bd/client/src/rpc_client.rs#L734
Publishing an updated solana-client depends on a new spl-token on crates.io that reverts the multisig Instruction names (and also accommodates the new xChecked Instruction names). So I'm going to merge this as-is with a note to update/simplify when solana-client is published.


Upgrade to Ubuntu 18.04 LTS on Toshiba 2 Chromebook

Please paste the output of the following command here: sudo edit-chroot -all

Please describe your issue:
I have a Toshiba 2 Chromebook where the hardware still works perfectly, but the Ubuntu version (16.04 LTS) will reach end of support in a few months. I have tried to upgrade to 18.04 LTS a few times, but always with issues. Would you know whether there will be support for a newer version of Ubuntu any time soon, so that I do not need to try and flash the bios to keep the laptop working?
If known, describe the steps to reproduce the issue:

@froukehe0,

I have tried to upgrade to 18.04 LTS a few times, but always with issues.

Yes, release upgrades are often problematic, it's best just to do a fresh install of Bionic Beaver / 18.04.
However, be aware it is not fully supported but has been reported to work pretty well, I can attest to that.
The next Ubuntu release that the crouton devs will support will be Focal Fossa / 20.04.
See this issue for more details about that and a timeline.

FOCAL FOSSA! · Issue #4265 · dnschneid/crouton

Your 'Toshiba 2 Chromebook' will hit it's Auto Update Expiration (AUE) date this year it appears:

Toshiba
AUE

Chromebook 2
Sep 2021

Chromebook 2 (2015 Edition)
Jun 2021

That does not mean it will not keep working, it just won't be guaranteed to receive updates after that time, in most cases Google will provide updates to these devices after the AUE date, often up to a year afterward.
Hope this helps,
-DennisLfromGA

@froukehe0,

I have tried to upgrade to 18.04 LTS a few times, but always with issues.

Yes, release upgrades are often problematic, it's best just to do a fresh install of Bionic Beaver / 18.04.
However, be aware it is not fully supported but has been reported to work pretty well, I can attest to that.
The next Ubuntu release that the crouton devs will support will be Focal Fossa / 20.04.
See this issue for more details about that and a timeline.

FOCAL FOSSA! · Issue #4265 · dnschneid/crouton

Your 'Toshiba 2 Chromebook' will hit it's Auto Update Expiration (AUE) date this year it appears:

Toshiba
AUE

Chromebook 2
Sep 2021

Chromebook 2 (2015 Edition)
Jun 2021

That does not mean it will not keep working, it just won't be guaranteed to receive updates after that time, in most cases Google will provide updates to these devices after the AUE date, often up to a year afterward.
Hope this helps,
-DennisLfromGA


Allow Apps to override clean and menuconfig targets in makefile

This allows app specific Makefile's to override the clean and menuconfig targets.

@sakumisue any problems with this? basically allows a project "Makefile" to specify targets for make clean or make menuconfig and not get a warning from Make as we do now:
/home/fish/bl808/OBLFR/../bl_mcu_sdk/project.build:51: warning: ignoring old recipe for target 'clean'
/home/fish/bl808/OBLFR/cmake/project.build:28: warning: overriding recipe for target 'clean'
/home/fish/bl808/OBLFR/../bl_mcu_sdk/project.build:51: warning: ignoring old recipe for target 'clean'

Recommend you to use other name.

these targets are "almost" industry standard. Most people expect make clean to clean up build files etc.
This change does not alter the behavior on bl_mcu_sdk apps and make clean etc works as it does today. It just allows third party repositories/code override if they need to.


Is it possible to integrate with another Nodejs app or Sails.js app

Something like mounting in some path.
example.com/kb

There isn't a way currently, but I see how that would be useful.
Some files/ideas on how to integrate:

all the routes in app.js (app.get, app.post) could have a "mount path"
the mount path will default to "/" in the configuration files

Yes, in example/server.js :
remove
var server = app.listen(app.get('port'), function () {
exports the app
exports.app = raneto(config);
In your node app
	var raneto = require('./example/server').app;
	app.use('/help/', raneto);

You will also need to install the missing dependencies manually.

Thank you for the info @dam1
I'll add this to the documentation update megathread.
We're moving to a separate repo for the example.
This is similar to your use-case so let's add it to the docs
Sails would be out of scope for now
Closing this, please continue discussion in megathread or re-open with further questions


Couldn't load the plugin

Hi @Morgan-6Freedom
Yes, unfortunately, it's a known issue of ChatGPT. I've just extended docs with how it can be resolved, you can find it here:
https://docs.askthecode.ai/authentication/#couldnt-log-in-with-plugin
Steps are:

Change the browser language to English.
If the browser translation feature is turned on and set to a language other than English, change it to English as well.

It should fix the issue. If not, please ping me back.

I have same problem as I am a asia user.

Hi @wastu01,
Have you tried the solution mentioned above? If you've changed your browser language to English and ensured that the browser translation feature is also set to English, it should resolve the issue. If it doesn't help, please ping me here.

My browser (and OS) are both set to English, while also using an English locale (US).
I'm using Firefox and I don't have any browser translation feature/plugins enabled (Firefox Translate is off as well) and I got the same message upon trying to reinstall at least half a dozen times. I just subscribed for the extended API usage and now I simply can't use it because apparently the plugin can't login.

Hi @nmindz,
I've tested the plugin reinstallation on my end and also received the same error. However, despite the error message, the plugin actually got installed and I was able to use it. In fact, this response has been created using the GitHub issues feature of the plugin.
Can you verify if the plugin has actually not been installed on your side? After receiving the error, is the plugin not available in your list of plugins?
I've also checked the OpenAI forum and found several reports from users about this issue starting from yesterday:

Plugin Installation Failed Again - 2023-10-21
OAuth Failures on All Apps - Error in OAuth Callback: Could Not Log in to Plugin
Getting this Error: "Couldn't Log in with Plugin" when Installing Plugins since Yesterday that Require Login

I'm sorry for the inconvenience. It looks like OpenAI is currently experiencing some issues with their OAuth functionality for plugins.

For me, it looks this way: the error is shown, but the plugin is available in the list of plugins and can be used.

Also I've tried the same with my other plugins and for all of them experienced the same behavior: received the error message, but the plugin actually got installed.
Could you please verify that the plugin is not actually installed for you?

I fixed that problem by changing the browser language to English. hope this can be a user friendly plugin in future. no change language anymore.

Hi @wastu01,
I'm glad to hear that you managed to resolve the issue by changing the browser language to English.
I apologize for the inconvenience you faced.
It's worth noting that the issue seems to be on the OpenAI side rather than the plugin itself. Multiple developers of other plugins have also reported that some of their users experience this issue. It appears that this problem occurs when users are redirected from the login page back to the ChatGPT window.
Thank you for your understanding.

Ok

@nmindz I can see that you've subscribed and the rate limits are displayed correctly (max quota is 200):

However, it's worth mentioning that your signing method is email and not Github, so querying private repositories won't be possible.
Also, please note that the subscription is not shared between the login methods. So, if you decide to log in with your Github account instead of email, it will consider you as a separate user (and thus with a separate free subscription).
If you want to use your Github account instead, I can refund this payment (it can take 5-10 days to be credited back to your bank account), so you can create a subscription for the Github account.
Could it be that you tried to use the Github account yesterday, and that's the reason why it considered you on the free plan?
Regarding the potential issue with the output, if it's possible and doesn't contain sensitive or personal data, it would be very helpful if you could share your conversation. This way, I can check how the requests to the plugin appear. And since you are using email authentication, I assume you are querying a public repository, so I will be able to reproduce and debug the case. Sharing the conversation would greatly help in understanding if there are any issues.
To share the conversation, you can use the Share feature of ChatGPT located at the top-right corner. If you prefer, you can also share it with me privately via email<EMAIL_ADDRESS>Regarding the differences in the request count, there could be multiple reasons:

The primary reason is that I released a new version of the plugin yesterday with enhanced search functionality, improved handling of large repositories, and a commit analysis feature (though the documentation hasn't been updated for these changes yet).

It seems like ChatGPT has also been undergoing a series of releases over the past few days. At times, it produces error responses in plugin usages and has started to display a peculiar error popup during plugin installation.

@dsomok About the sub: it's fine. 🙂
About the auth methods (email/Github) I figured so, but too bad that was after I had already paid for the sub. Either way it wasn't/isn't a problem since I was mainly interested in a higher quota, not necessarily private repos.

I just sent you the shared chats at your e-mail.
Feel free to reach out if you have more questions and/or need anything else. 😉
I realized (after a few attempts) that for whatever reason (despite having context from AskTheCode) having plugins enabled (becoming worse the more plugins you have) seriously hindered GPT's ability to produce usable code in the last few days.
It might be one of their recent updates like you mentioned, but maybe a too big context just isn't feasible anymore (like it used to be a few months ago with GPT). Or I'm just bad at prompting. 😅

@nmindz I've released a new version of the plugin that should address the issue you've encountered with the samples you provided. I've also sent you an email with a sample conversation using the new version of the plugin for your review.
Regarding your observation about the impact of enabled plugins on context size, I assume that the OpenAPI schemas of the enabled plugins are loaded into the context, probably not as raw OpenAPI schemas but rather in a processed form, something similar to the way functions are defined when using OpenAI API. This would inform the model about the plugins' capabilities, their endpoints, and the conditions for triggering them. Consequently, this does indeed reduce the available context size—the more plugins enabled, the more significant the reduction.
Please test the updated version of the plugin and let me know if it resolves your issue.


messenger for Ubuntu Linux

Messenger for Ubuntu Linux does not play my voice messages for some reason (but sends them OK). Why is this?

Because of the lib used only support open-source codec. We need to change it manually to use the proprietary codecs. Will be in the next beta.


zig build install -Drelease -Dconfig=production

Hi @cb22, I have built the TigerBeetle from source (zig build install -Drelease -Dconfig=production) but it seems to be giving errors.
I have attached the details here
/home/sandeepka/Desktop/tigerbeetle-0.15.3/build.zig:1014:22: error: expected 2 arguments, found 3
const self = @fieldParentPtr(FailStep, "step", step);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/sandeepka/Desktop/tigerbeetle-0.15.3/build.zig:1039:22: error: expected 2 arguments, found 3
const self = @fieldParentPtr(ShellcheckStep, "step", step);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/sandeepka/Desktop/tigerbeetle-0.15.3/build.zig:1091:22: error: expected 2 arguments, found 3
const self = @fieldParentPtr(GitCloneStep, "step", step);

Hi @sandeepanumula8690,
TigerBeetle depends on Zig 0.11.0, not 0.12.0 (yet) -- they are not compatible.


api eth_getTransactionReceipt aways return fixed contractAddress "0x6295ee1b4f6dd65047762f924ecd367c17eabf8f"

Describe the bug
when invoke eth_getTransactionReceipt api to get contractAddress, it aways return fixed contractAddress “0x6295ee1b4f6dd65047762f924ecd367c17eabf8f”， no matter which deploy contract transaction.

has fixed


dockerd configuration reloading section missing options that get reloaded

File: engine/reference/commandline/dockerd.md, CC @mstanleyjones
Hi!
The configuration reloading section here lists which prefs are reloaded when the dockerd process receives a SIGHUP:
https://docs.docker.com/engine/reference/commandline/dockerd/#configuration-reloading
However it appears there are a few entries missing from that list, such as:

Daemon shutdown timeout
Insecure registries
Registry mirrors

For the full list of settings that get reloaded, see:
https://github.com/moby/moby/blob/master/daemon/reload.go
Many thanks!

Issue moved to docker/cli #590 via ZenHub


Handled Exceptions show fine but no Crashes

Hi,
I'm using the prerelease version and followed the readme but no crashes appear in Firebase Console.
The managed exceptions show fine. There are no errors in the log to indicate something is missing.
Have you got an idea of what I can try to fix this?
Many thanks.

I'm having same issue

Same issue :-(


Do you plan to maintain this actively?

There are so many version of ngx-international-phone-number. I am confused which one to use.

I had forked into my own version to address some issues I was encountering with the original, primarily I started out wanting to separate country code from the phone input. Also I just wanted to try my hand at creating an npm package. I can't say how actively I'll be maintaining it in my spare time, but if some show stoppers come up I'll do my best to investigate.

Thanks. I will try to play a part too, during my free time.
On Tue, 12 Nov 2019, 5:51 AM esoyke<EMAIL_ADDRESS>wrote:

I had forked into my own version to address some issues I was encountering
with the original, primarily I started out wanting to separate country code
from the phone input. Also I just wanted to try my hand at creating an npm
package. I can't say how actively I'll be maintaining it in my spare time,
but if some show stoppers come up I'll do my best to investigate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/esoyke/ngx-international-phone-number2/issues/1?email_source=notifications&email_token=ABRK4QE3ANIY7RAXQ7EZJFDQTHHU7A5CNFSM4JLP46WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDYIDJQ#issuecomment-552632742,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRK4QG4FGNDSDJ3N2BGTILQTHHU7ANCNFSM4JLP46WA
.


Rename file_descriptor to file_description_ref

After #3712  renamed previous FileDescriptor to FileDescriptionRef, several variables still use the old name file_descriptor and should be updated to file_description_ref to avoid confusion. This is a simple cleanup task, but I am currently focused on other work, so I am just opening this issue for anyone who might be interested in helping.

That's a very long variable name, so we can also consider something like fd. That doesn't disambiguate between "file descriptor" and "file description", but we have types to help make that distinction, so maybe we don't have to repeat this in the variable name as well.

I'm willing to take this on - seems pretty straightforward. From a quick look, there's one variable named exactly file_descriptor which is a FileDescriptionRef (in fs.rs), but several named file_description which are FileDescriptionRef (in fs.rs and fd.rs). Should both cases be renamed, or only file_descriptor?

I think there is one in fd.rs https://github.com/rust-lang/miri/blob/335c91c7f57942f61fc9712b8b13e84fffc0a365/src/shims/unix/fd.rs#L414 I personally don't find the naming of file_description confusing, but I am happy to see it being changed if it would be clearer. Maybe fd_ref would work if we were to change it? But I am not really good in naming variables, so cc @RalfJung :)

Sorry, yes, I meant fd.rs for that first one, just mixed up the file names. fd_ref would match up with some other parts of the code, like these two:
https://github.com/rust-lang/miri/blob/335c91c7f57942f61fc9712b8b13e84fffc0a365/src/shims/unix/fd.rs#L335
https://github.com/rust-lang/miri/blob/335c91c7f57942f61fc9712b8b13e84fffc0a365/src/shims/unix/linux/epoll.rs#L277

I did a bunch more renaming in https://github.com/rust-lang/miri/pull/3867 to hopefully make things more consistent wrt file description vs file descriptor: the latter (of type i32) are now called fd_num. We should only use them in the outer layers of the shims anyway, internally in Miri everything should be file descriptions.


Compatibility issues persist with os.execute

sh: line 1: cls: command not found
os.execute(clearCommand) still does not work for Unix.

cls on /bin/sh for Linux returns code 127, so presumably
if not os.execute(clearCommand)
on line 6 may not evaluate to true, hence
clearCommand = "clear"
on line 7 may not be executed for Unix systems.

i fixed it try again


Don't recommend 'monitor' function

Apparently, the 'monitor' that we recommend (Assignment 6) is not really working as it should. It doesn't respond to the number of warmup steps.
Here's a GH issue from three years ago where a Stan dev recommends against it: https://github.com/stan-dev/rstan/issues/759
If this is still the case I think we shouldn't recommend that function to students.

Great! Yes, I dont use it myself. Can you do a Pr to fix this?

What should we recommend instead? Or should we just remove the hint?

What is it used for, traceplots and Rhats and the like? I don't remember.

The assignment seems to ask the students for $\hat R$ only:

Then we maybe just remove the recommendation, or alternatively add that you can get the samples for Rhat with the extract function.

Yes. I can fix this.

Fixed in e9681c0


feat(material/progress-bar) : add height and border-radius properties in mat-progress-bar widget component.

I added the height and border-radius parameters to the component, which allows me to have a rendering like this.

Hi @andrewseguin, I hope that you're doing well. I need a title bit your help. In local, when i want to test, it don't work. And after the PR it seems that there are tests that don't work.


Add deb and debsrc stats

I've modified Debian stats in order to check for deb param.
I've also added a card for debsrc, but the call to the service fails:

Fixes #836

Added https://github.com/clearlydefined/service/pull/647 to address.


tinyMCE codesample plugin

Hi,
Does anyone know how to enable the codesample plugin in tinyMCE ?

Hello Muhammed.
Please use the mailing list for general questions: https://groups.google.com/forum/#!forum/mezzanine-users


Fixed workflow permissions and pinned actions

SUMMARY

Fixed workflow permissions - https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
Pinned workflow actions - https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@eschutho Could I please get some 👀 ? Thanks


[DOC] Documentation of non-obvious behaviour of mutex priority dis-inheritance

Describe the issue
FreeRTOS mutexes do priority inheritance. However, they do only somewhat rough priority disinheritance when releasing. In particular, xSemaphoreGive is a macro which calls xQueueGenericSend, which calls prvCopyDataToQueue, which calls xTaskPriorityDisinherit, which only disinherits priority if no other mutexes are held. It makes sense to do this (maintaining a data structure that would let you figure out the proper priority to disinherit to based on the current waiters on the remaining held mutexes would be complicated and expensive), but it’s not at all obvious that a priority-inheriting mutex would do this (the intuitive behaviour would be that the giver’s priority drops to the maximum of all waiters for all still-held mutexes), and as far as I can tell, it’s not documented in the manual. I think it should be, because it sometimes matters (it caused a difficult-to-find bug in my code, where I expected “give mutex immediately followed by take mutex” to result in the mutex being handed off to a task with a higher base priority, but it wasn’t actually handed off because the yielder held another irrelevant mutex at the same time which prevented its priority from being disinherited and therefore prevented a task switch from happening).
Reference
Priority inheritance is primarily documented on this page, so I think that’s where it would make sense to describe this. Maybe also here, here, here, and here, which also mention priority inheritance in a shorter form.

@Hawk777 Thanks for the in-depth description. I'll work with our docs team to get this updated.

I've been taking a look through the code and found another unexpected disinheritance behavior here which is called when a task waiting for the mutex completes its wait for the mutex (or times out). In this case the priority once again will not be reset when more than one mutex is held.
I'll be working on a write up of this issue to give to our documentation team. I'm hoping to get this updated within the next week or two (our documentation receives updates weekly).

@kstribrnAmzn good catch, that is a similar issue, it looks like when a waiter times out, the holder’s priority drops to the highest of any remaining waiter for that mutex, when in an ideal world it should drop to the highest of any remaining waiter for any mutex it holds, not just the one for which the timeout occurred.

I think the behavior is slightly different from what you've described (and even more basic). When there are more than 1 mutexes still held, the priority does not get disinherited.
It gets calculated to be disinherited here, but because more than one mutex is held the tasks priority will not be updated by this line. This is tested by the test_vTaskPriorityDisinheritAfterTimeout_success3 unit test found here. In this test even though it could 'disinherit' to a higher priority it won't because the more than one mutex is held.

The kernel book is updated. I'm working with our doc writer to get the website updated in the next week or so.

Sorry for the slow closure if this issue. We had an issue with the way we were translating our web pages. I've fixed this which will allow our website updates to resume. The website should be updated with this information in the next week or two.

Well that was quite the rigmarole. Our website update process was quite broken so I had to fix that before the docs could go live. I'm happy to report that they are now live. The non-obvious behavior is documented here in the 'Simplified Priority Inheritance' section.
Links have also been added to this section on the following pages:

https://beta-ts-mirror-site.amazonaws.com/xSemaphoreCreateRecursiveMutex.html
https://beta-ts-mirror-site.amazonaws.com/xSemaphoreCreateMutexStatic.html
https://beta-ts-mirror-site.amazonaws.com/xSemaphoreCreateRecursiveMutex.html

Thank you!


redshift: fix broken icons

Motivation for this change
To fix the broken icons that show up in the tray when using the redshift-gtk application.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Redshift uses SVG icons and librsvg therefore needs to be available and the GDK_PIXBUF_MODULE_FILE variable set in the wrapper.

Cool. Thanks!


VirtualFunction generator bug

If the virtual function has a procedure, the generator does not append ";" at the end of the function declaration.
void generate(std::ostream& os) const override {
        os << "virtual ";
        generate_prototype(os);

        if (m_procedure.empty()) {
            os << " = 0;\n";
        }
}

Fixed in 56b7336bab16757913e19603f412e87c70ee4d75. Thanks for letting me know!


Remove side effect on axis parameter in Quaternion.RotationAxisToRef(…)

See https://forum.babylonjs.com/t/unexpected-side-effect-of-quaternion-rotationaxis/52622
This PR just fixes Quaternion.RotationAxis(...) and Quaternion.RotationAxisToRef(...).
The other 3 suspect lines in the file mentioned in my initial post are not handled here.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15381/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15381/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15381/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15381/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15381/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15381/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15381/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15381/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15381/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15381/merge/testResults/webgpuplaywright/index.html

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15381/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.


When i try to do something myslef it says somthing

it says luckperms Please Note That Server Operator status has no effect on sponge permission check when a permission plugin is installed please edit user data directly. PLEAse help

Well, like the note says:

Server Operator status has no effect on sponge

i.e. there is no /op in sponge servers. And as stated in the wiki:

This is an intentional behaviour of SpongeForge. As soon as a permission plugin is installed, it will disable the OP system.
To fix this, give the groups and users the required permissions for the plugins. If you want OP-like permissions, you can use the wildcard * but this is considered bad practice.


Feature/5101 ck editor option to resize images on upload

Closes #5101
This PR is built on PR #5122 which was submitted for #5100, but is not necessarily related.
Summary
This PR adds settings for:

Image Resize Width On Upload
Image Resize Height On Upload
And will resize any uploaded image to fit within these dimension on upload.

Since pictures are becoming larger and larger, it can be important on many portals, to have this automatic resize option, to allow users uncapable of resizing images themselves, to upload reasonably sized images.

Looks good to me but not sure how this works with the other PR with regards to merge conflicts.

Thanks, I have been wondering that too, but given the fact that the changes from #5122 are also shown in the changes here, it looks like the easiest thing would be to just merge this one.
The reason I made two, was that I assumed one PR for 2 issues wouldn't be the right either...

Just chiming in on the logistics of the "stacked commits".  We can still manage these PRs independently.  The branch for this PR will just need to be rebased once #5122 is merged.

I agree, let's resolve #5122 and come back to this one, happy to help with the rebase if any conflicts arise.
@skamphuis I guess here you started this branch from the other branch instead of starting over from fresh develop.

I merged the most recent develop branch into this one before crafting the pull request, so merging should be fairly easy and without conflicts?

@skamphuis I guess here you started this branch from the other branch instead of starting over from fresh develop.

It seemed to me that both would be more related than they actually turned out be.
I appreciate all your (and @donker , @david-poindexter ) efforts to get this merged in, by the way.

@skamphuis looking at the conflicts did you:
A: use different variable names on the 2 PRs ?
B: They represent 2 different things and they are both to keep ?

Sorry, I am not super familiar here with all the possible settings in this area :)

@skamphuis looking at the conflicts did you:
A: use different variable names on the 2 PRs ?
B: They represent 2 different things and they are both to keep ?

Sorry, I am not super familiar here with all the possible settings in this area :)

B.
I introduced the ...OnUpload field to specify the size to resize to in upload. The other ones already existed and specify the default size for the Resize option in the image browser.

@valadas I obviously messed up trying to rebase this thing on release/9.11.0 as there are now a lot of changed files.
Do you have any advice?

Not knowing what went wrong, it's hard to advise on it. But above you have the list of commits, if you know the ones that should be part of this unit of work, you can copy their hash code, create a new clean branch based on release/9.11.0 and then cherry-pick those hashes into it to redo a new pr.  https://git-scm.com/docs/git-cherry-pick

Not knowing what went wrong, it's hard to advise on it. But above you have the list of commits, if you know the ones that should be part of this unit of work, you can copy their hash code, create a new clean branch based on release/9.11.0 and then cherry-pick those hashes into it to redo a new pr.  https://git-scm.com/docs/git-cherry-pick

Not knowing what went wrong, it's hard to advise on it. But above you have the list of commits, if you know the ones that should be part of this unit of work, you can copy their hash code, create a new clean branch based on release/9.11.0 and then cherry-pick those hashes into it to redo a new pr. https://git-scm.com/docs/git-cherry-pick

That turned out to be easier than I thought. New PR is #5128 . I'll close this one.
Thanks.


[VL] Gluten-it: --auto-cluster-resource to automatically set up CPU cores and memory sizes for local cluster

When --local-cluster and --auto-cluster-resource are both set, cluster CPU cores / heap memory sizes / off-heap memory sizes will be automatically configured using the maximum available resource information fetched from OS API.
Basically, up to all CPU cores and 80% total RAM memory will be used to run benchmarks when the options are turned on.

Is it a spark feature?

Is it a spark feature?

No, it's gluten-it's feature for better testing.


Use the google sheets api

Hello,
I want to use your code with the google sheets api, downloaded from https://www.nuget.org/packages/Google.Apis.Sheets.v4/
But when I loaded the DLL with the Labview ".NET constructor" I got this message : "An error occured trying to load the assembly" in "objects" section.
Someone can test it or help me?
Thanks.

I'm getting the same problem. It doesn't let me use the .dll file. Have you figure out anything about this?

Hello Joseph280996, I'm glad to see I'm not alone. I didn't move forward with this issue. I tried with 32bits, 64 bits OS and labview versions. I contacted the french NI support but they don't figure out it.
I will probably save my data in an SQL database and import these in the Google environnement.


Open second window as an Administrator

VSCode Version: Code - Insiders 1.14.0-insider (6afdf303bb8f70d840c12a43c036e98a9da50d41, 2017-07-05T08:33:33.146Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

angular2-snippets
dan
1.0.15

githistory
don
0.2.1

python
don
0.6.7

Angular1
joh
0.2.0

Angular2
joh
2.3.3

mssql
ms-
1.0.0

csharp
ms-
1.11.0

PowerShell
ms-
1.4.1

team
ms-
1.119.0

debugger-for-chrome
msj
3.1.6

vscode-icons
rob
7.10.1

vscode-gulp
tan
0.0.4

Hi, I do not seem to be able to open an additional window as an administrator.
First case scenario, if VS code is already open normally, i cannot open a window as an administrator.
Second case is when it is already opened as an administrator - same repro steps
Steps to Reproduce:
1.Pin VS Code to your task bar (to make this simpler)
2. Right click on VS Code icon in your taskbar
3. On the context menu, right click the "Visual Studio Code - Insiders" menu item (3rd from the bottom) and select Run as administrator, VS code opens
4. repeat step 2 and 3.
Expected:
5. A second window opens as administrator
Actual:
5. Nothing seems to happen

Reproduces without extensions: Yes/No

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.


Added Thai translation for Navigation & Diplomat section

@wteja could you sign our CLA so we can accept your PR?

@Bryukh ok, I just accepted and signed it.

Thanks!


Use exactly matching tags for triq dependencies

Otherwise rebar thinks there is a conflict:
ERROR: Conflicting dependencies for triq: [{"From: hyper",
                                            {[],
                                             {git,
                                              "https://github.com/apache/couchdb-triq",
                                              {tag,"v1.2.0"}}}},
                                           {"From: asf2",
                                            {".*",
                                             {git,
                                              "https://github.com/apache/couchdb-triq.git",
                                              {tag,"v1.2.0"}}}}]

should be ok +1


File support

It would be great if it would get file support at some point, f.e. to use for pdf files.

Implemented.

awesome, thanks.


JavaScript

JavaScript
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

Prework for this section has been completed.


Refactor authentication response in AuthController

This pull request refactors the authentication response in the AuthController to return a JSON response instead of using the custom response method. This improves consistency and follows best practices for API responses.

Next, it will be merge with BaseTrait


test: benchmark alien-signals

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

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

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
1138

Relevant Lines:
1138

💛  - Coveralls


Support inverted arguments for BoolParameter

Add two command-line arguments for BoolParameter's instead of one, specifically one to set it to True (e.g, --foo) and another (--no-foo) to set it to False. This is necessary because BoolParameter currently uses argparse's "store_true" action, which does not take a parameter. This change allows BoolParameter's to have a default of True and still be settable to False.
For cases where an inverted argument does not make sense, the caller should set omit_inverted_argument=True on the BoolParameter. (For example, this has been done for the --help and --help-all options, as --no-help is of no help at all.)

This is a great idea!

This implementation looks nice and clean. Just some minor inline comments:

The reason I like this patch is that I've by now repeatedly told other PR senders that "No, you're not allowed to have True as a default for your BoolParameter". But with this patch we could allow it from now on.

This is a reasonably big change (not in code size), but in what we communicate are good practices to the luigi users. I remember @erikbern saying some time that BoolParameters should always be false by default. But I don't know if he meant that as a "that's good design in general" or "due to current luigi limitations that's the only implementation that works out".

Understood. I agree that existing community usages may have a part to play in whether this PR should be accepted or not.
As an anecdotal data point, at my employer (Foursquare), we use Luigi and I have seen our developers confused on multiple occasions by not really being able to set default=True on BoolParameter. (The confusion stemming from the BoolParameterbehaving differently from every otherParameter` subclass in Luigi.)

And this PR is an attempt to improve the API to remove that source of confusion.

I agree with @tdyas on this, as someone who used Luigi heavily while working with @erikbern . It doesn't break the existing semantics, and it does exactly what I had assumed it would have done when I first started using Luigi: adds a --no-xyz argument, which is a de-facto standard for GNU tools and elsewhere.
The only reason default=True was a bad practice is because it lacked this implementation, and we had to do dumb hacks like create argument variables named no_this and disable_that.

Thank you both @tdyas and @a1k0n for sharing your design thoughts, they sound sane to me. I'll just give @erikbern until tomorrow to chime in. Otherwise I'll merge this tomorrow once you fix the build.

i'm fine with this

Adding the --no-xyz arguments seems to confuse argparse's parse_known_args method. I'll have to dig into why argparse is confused.
runtests.py: error: ambiguous option: --n could match --no-scheduler-record-task-history, --no-lock, --no-worker-no-install-shutdown-handler, --no-no-lock, --no-RangeBase-reverse, --no-worker-count-uniques, --no-scheduler-prune-on-get-work, --no-RangeDaily-reverse, --no-local-scheduler, --no-worker-retry-external-tasks, --no-RangeHourlyBase-reverse, --no-take-lock, --no-RangeDailyBase-reverse, --no-scheduler-prune-done-tasks, --no-RangeHourly-reverse, --no-parallel-scheduling, --no-TestNotificationsTask-raise-in-complete, --no-worker-keep-alive, --no-assistant

i'm guessing no argument can be a prefix of another

So I dug in further, and it seems like a bug in argparse. The error occurs during the call to parse_known_args in CmdlineParser.__init__. That method is trying to determine the root_task to use. argparse should really not throw an error about an ambiguous option when invoked via parse_known_args. It should just mark the option in question as unknown.
I can get the failing test to pass by renaming the n option in SomeTask in cmdline_test.py to something else (e.g., z).
This still brings up an issue about whether this will break Luigi for anybody who has a task with a "n" parameter.

And this issue is known to the Python developers: https://bugs.python.org/issue19814
And apparently only warrants a warning in the documentation.

Please let me know if you need any help. Otherwise I'm patiently waiting for something that builds. :)

As it turns out, the test I added wasn't actually testing whether a BoolParameter with default=True could be set to False by option. This uncovered some places where checks for truthy values had to actually check for None.
I also merged all of the other commits into the commit adding the inverted argument support.

There was also a test failure locally for me with test/file_test.py which seems unrelated to my change since the tests in that file don't deal with parameters. It could be an issue with my local setup so will wait for the Travis build to see if that is the case.

CI tests passed.

I'm still a bit worried about we suddenly dropping support for parameters with names like n and I'm not fond of you renaming a local variable to an all caps name (n --> N). Would it not just be much easier if you only had the --no-boolparam option only if default=True? Alternatively you could another option add_negative_cli_flag with a value False as default.

 But I'm afraid people are going to start to say their stuff broke and this would need to be reverted in haste if we break compatibility.

apparently python 3.5 added a flag to argparse allow_abbrev=False that turns off the prefix matching. too bad it wasn't earlier
the correct way would probably be to first change luigi's behavior so that prefix flags throw a deprecation warning for a few months and then an exception
btw reminds me – maybe it's time to publish a new version of luigi to pypi?

So the solution for now it seems is to just add a --no-FOO option for BoolParameter's with default=True?

Yea. I would be more comfortable that way actually @tdyas

Resolved by #2427


qf_init: Do not use fallocate on macOS

Fix the error: use of undeclared identifier 'fallocate'
macOS does not have fallocate. It does have fcntl F_PREALLOCATE.
See for example https://github.com/trbs/fallocate/blob/master/fallocate/_fallocatemodule.c#L59

Commented out fallocate call. It was an optimization and doesn't affect the functionality.


Support extraction of non-textual data types

Currently, Hakuin can only extract text columns.
Support extraction of other data types, such as integers, floats, bytes, dates, etc.

Hakuin can now extract integer columns.
Implemented in dc0bc22

Hakuin can now extract binary data (blobs).
Implemented in 34e11cf

Hakuin can now extract floats.
Implemented in 5983e5f


3.0

Hey, thank you for testing and contributing to wavesurfer.js!
Please make sure you can check all of these points below before opening an issue:
(You don't have to post this section)

[ ] I have checked the FAQ and it doesn't solve my problem.
[ ] I have checked the documentation and it doesn't solve my problem
[ ] I have searched for already open issues which desribe my problem.
[ ] The issue I'm having is related to and caused by wavesurfer.js, not by other software (which maybe packages and uses wavesurfer incorrectly) – In that case you should open the issue on the respective project pages.

Please make sure you provide the following information (if applicable):
Wavesurfer.js version(s):
Browser and operating system version(s):
Code needed to reproduce the issue:
(Please reduce your code as much as possible and only post the minimum code needed to reproduce the issue. A Code pen is an excellent way to share such code)
Use behaviour needed to reproduce the issue:

see #1651


Allow more config options for ServerConfig, or allow passing our own Koa instance.

Hi there,
I've been looking for a way to generate a typescript server from an openapi schema that wasn't express based for a while now, and I am happy I found this tool, as it supports both Koa and Zod which are two library I have been using heavily in my projects, so big thanks for making it.
Now I am working on a project where I need to specify additional options to the Koa instance, one being the host options and the ability to use a custom function for the listen callback. Both of these are pretty important requirements for my project, due to how we want our output being presented to the console. Because my project makes use of node clusters, calling the startServer function means that every web cluster instance is now outputting the line server listening: ... which is not ideal, and there is no options to prevent this.
So having the option to override the default as a field in the ServerConfig type would be a good compromise, unless of course you have a better solution in mind.
Thanks

As it would happen I've been experimenting with ways to improve this over in https://github.com/mnahkies/openapi-code-generator/pull/88
(I've also been a bit lazy and let that PR grow in scope - I'll probably chop it up before merging)
The first commit is the main one relevant to your needs: https://github.com/mnahkies/openapi-code-generator/pull/88/commits/d181bd8ae52bbb86bf8db4b0d42fa83f1a655270
It separates the construction of the router and starting of the server - this pretty much leaves you free to construct your Koa instance as you see fit, with the caveat that it relies on a body parsing middleware being mounted.
Eg: your entrypoint could look like:
async function main(){
  const app = new Koa()
  app.use(koaBody())

  const router = createRouter({...})

  app.use(router.allowedMethods())
  app.use(router.routes())

  ...do whatever you like with `app`
}

It also removes that console.log you mentioned (https://github.com/mnahkies/openapi-code-generator/pull/88/commits/01367a7af108a52f7d10ff7cb250b8155ee96605)
Other things happening in that PR, that I'll probably split out to separate changes:

Wrapping the raw Zod errors to indicate what part of the request caused these (https://github.com/mnahkies/openapi-code-generator/pull/88/commits/bb056e9bb315dac5a8c7250d77b8984dbcd73926)
Introducing a "responder" parameter (https://github.com/mnahkies/openapi-code-generator/pull/88/commits/b83d3625a2d591ed54a04c0d7e489aac9229ac38)

Motivation for the wrapped errors is to support error handling middleware like:
export async function errorMiddleware(ctx: Context, next: Next) {
    try {
        await next()
    } catch (err) {
        if (
            KoaRuntimeError.isKoaError(err) &&
            err.phase === "request_validation"
        ) {
            ctx.status = 400
            ctx.body = {
                message: "request validation failed",
                code: 400,
                meta:
                    err.cause instanceof ZodError
                        ? { issues: err.cause.issues }
                        : {},
            } satisfies t_Error
            return
        }

        ctx.status = 500
        ctx.body = {
            message: "internal server error",
            code: 500,
        } satisfies t_Error
    }
}

Eg: treat request validation as a client error, and other errors as internal server errors. You'd probably have your own client errors in the mix as well, but something like this feels like a good baseline to me.
I'm not certain if I'm happy with the responder pattern change yet, and would be interested in your thoughts if you have any. After that change a request handler looks something like:
export const getTodoLists: GetTodoLists = async ({ query }, respond) => {
    const pageSize = query.size ?? 10

    const lists = await prisma.todoList.findMany({
        take: pageSize,
        skip: query.cursor ? 1 : 0,
        cursor: query.cursor ? { id: query.cursor } : undefined,
        orderBy: { created_at: "desc" },
    })

    return respond.with200.body({
        items: lists.map(dbListToApiList),
        cursor: lists[lists.length - 1]?.id ?? null,
        pageSize,
    })
}

Where respond has typed properties based on the openapi spec. My motivation for this was to try and get better intellisense / autocomplete in my editor, and it feels a bit terser as well.
I didn't know this had any users yet, so any user feedback is useful!

I am happy to hear you already had thought about this and even have something in the works, that's pretty good news. So far what you put seems like something I would be happy with.
That being said, I do have some questions about that Error Handling middleware you presented there, is that going to be optional or configurable? I ask because in my project I follow DDD/Hexagonal architecture, so I have my own app error handling with my own structures, and with being the case, the output to the user doesn't contain all the fields I would like to have. So of course being able to provide my own even if mostly based on your current one, with some minor changes to how the output looks would definitely fit my needs more.
The response part is pretty different to what I have seen other projects do, so I am interested in how that would work, based on how it looks though, would there be .body and a .header as well? Idk if maybe something like
response.with(200, {
   body: {},
   headers: {}.
});

One other thing while not on topic for this specific issue, but I thought I might mention, is the ability to have the openapi.yaml or openapi.json file byte encoded into the generated files, so that it could be served at something like /api/openapi.json, this could be something enabled with a flag such as --embedSpec or something like that.
Appreciate the quick reply:)

I've split up that PR, and merged the changes relevant to your original post in #88 - released in https://github.com/mnahkies/openapi-code-generator/releases/tag/v0.1.1
Example of new usage: https://github.com/mnahkies/openapi-code-generator/blob/c2a0ae50e2ff9e81181f032ca514a1e974f08321/integration-tests/typescript-koa/src/petstore-expanded.yaml.ts#L51-L59
The other two changes I mentioned are now WIP in these PR's:
#95 - feat!: throw discriminable errors indicating point of failure
#96 - feat!: responder pattern
Feel free to take a look and provide feedback - the error handling middleware is very much optional and BYO, the motivation of the change is to provide additional context on the thrown errors to enable creating such middleware, but I don't think it's possible to generate a meaningful global error handler without making too many assumptions about the API spec in the generator.
Still working out the details for the responder pattern one, response headers are something that's still on the TODO list.
For the surfacing of the openapi.yaml spec, I do have #81 for adding support for redoc which is kinda similar. I'm still working out what the boundary/scope of the project should be for stuff like this though. I like redoc, but many people prefer swagger-ui - how should a library like this avoid forcing too many choices like that on people.

Awesome, I will be giving the new version ago soon, very happy to see this change. After looking at the PR for the responder type, that made it much easier to understand what you were going for, and this seems perfectly usable to me, even more usable once header support makes it.
While supporting stuff like swagger-ui and redoc sounds interesting, though what I was asking for was simply allowing to serve the spec file as a resource, so other projects could just generate the client from that spec, and you know the spec served will work for that specific version. There are cases where someone is running an outdated version of project for specific reasons and it would be a problem if the project itself only hosted the up to date version of the spec, so generating it for older versions would cause incompatibilities, so that would be my main reason for having this feature.
I appreciate all the work going into this, I have high hopes for this library.


Crash (Somewhat expected something to break)

Server log: http://pastebin.com/1ZBdDNaa
Client didn't crash
Summary of what I was doing and the results:
So I have a digger age made by Mystcraft (haven't looked into DimLets as of yet) and made a FunkyLocomotion FrameQuarry (just a moving set of BuildCraft Mining Wells) and I decided I'd like to be able to freely teleport to/from this moving monster. So I made 2 dialing devices, matter receivers and transmitters, and set them up in my base and on the moving quarry. I initially ran into a problem with the frame and chunk loading because of how they handle one-another, but managed to resolve that as far as I'm aware (could be a cause of this, maybe?). After that was resolved I dialed a link to my base and tested it a few times with moving and it worked fine, so I decided it was time to let it auto-run while I left the dimension. This is when strange things started happening. First up was that the client got kicked by the server for an internal exception, but neither crashed, when I tried using the transmitter to teleport back to my base. So I rejoined, everything seemed fine, but only half the quarry had moved, so I placed more chunk loaders to keep all 4 chunks loaded at all times regardless. After that I set the quarry to run automatically again, and left the dimension - successfully this time - but when I loaded into my base (Another MystCraft age, one that had Bright Lighting so that everything is lit up even if it's dark) and it was almost completely darkened out, so I knew something was up. The server crashed seconds later.
I'll provide any further information upon request, but just a heads up about this.
Using:
RFTools v2.80
CoFH Core 3.0.0RC7-211
Thermal Dynamics 1.0.0RC7-98
It appears to be a problem regarding your transmitter and a ThermalDynamics conduit, so I can go bug CoFH about it if you think it's all on them.
Edit: Server now crashes on startup, goodbye to that dimension.

Um. This is a bit confusing. Maybe I don't 100% understand what is going on but how do you conclude this is a problem with the transmitter and the conduit? Could just as well be an issue with the funkylocomotion thing I would say. Crashlogs would be useful in any case if you still have those.

I did include a crash log?

Server log: http://pastebin.com/1ZBdDNaa
Apologies for calling it the server log, I realize that they are 2 separate things.

The problem is most likely caused by ThermalDynamics being confused by being moved and trying to get information from the old location. Sounds more like a problem with ThermalDynamics here.

Alrighty.

Just a heads up, this probably isn't fixable. We are already doing cast checks everywhere possible. But I concur that it's not on RFTools, just vanilla MC and how tile entities are tracked.


v1.0.0

Checklist

[X] Used a 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.

The link above https://conda-forge.org/docs/conda_smithy.html#how-to-re-render for rerendering does not exist.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like I wasn't able to push to the v1.0.0 branch of libsemigroups/libsemigroups-feedstock. Did you check the "Allow edits from maintainers" box?


Update Alert_Nested.md

:warning: Validation status: warnings

File
Status
Preview URL
Details

APEXTest/CATSTesting/Alert-Cases/Alert_Nested.md
:warning:Warning

Details

APEXTest/CATSTesting/Alert-Cases/Alert_Nested.md

Line 15: [Warning] Invalid file link:(~/Alert-Cases/Link.md).
Line 44: [Warning] Invalid file link:(~/Reference-Files/Images/flowers.jpg).
Line 188: [Warning] Invalid file link:(~/Reference-Files/Images/flowers.jpg).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

APEXTest/CATSTesting/Alert-Cases/Alert_Nested.md
:warning:Warning

Details

APEXTest/CATSTesting/Alert-Cases/Alert_Nested.md

Line 15: [Warning] Invalid file link:(~/Alert-Cases/Link.md).
Line 44: [Warning] Invalid file link:(~/Reference-Files/Images/flowers.jpg).
Line 188: [Warning] Invalid file link:(~/Reference-Files/Images/flowers.jpg).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Input stream line position and read term start and end lines

As a future enhancement, it would be quite useful if we could call the stream_property/2 predicate to get the current line and if the read_term/3 predicate could support an option to get the term start and ending lines. In my particular case, Logtalk uses these features to pinpoint warnings and errors when compiling a file. When we use the sandbox in the Tau Prolog website, warnings and errors tell us the source file line number. Thus, I assume the some of the necessary bits to support these features are already present internally?

Yes, currently the tokens store that information. What is the convention for this property? For the same stream, SWI-Prolog gives me '$stream_position'(57,1,57,57) and GNU Prolog '$stream_position'(57,57,0,57).

From the ISO Prolog standard perspective, the position/1 property value is not specified. You can regard it as an opaque term and then have a small set of predicates to access the information in there. This works well and enables changing position information without breaking existing code. On the other hand, there's not that much to tell about a stream position. We have line numbers and possibly column numbers for text streams. Thus, you can always go with a simple term like position(Line,column) for the stream_property/2 predicate position/1 property. For read_term/3, ideally we have not just the start position or the end position of the term but both.

Btw, you can look inside the logtalk3/adapters files and see how different Prolog systems do it (search the files for the predicates '$lgt_stream_current_line_number' and '$lgt_read_term'.

Added stream_position_data/3 built-in predicate.
stream_position_data(?Field, +Pos, -Data). Field is one of line_count, line_position or char_count.

There seems to be an initialization bug when reading the first term from a stream:
.../node_modules/tau-prolog/modules/core.js:7848
					if(last_token.line_position === last_token.len)
					              ^

TypeError: Cannot read property 'line_position' of null
    at read_term/3 (.../node_modules/tau-prolog/modules/core.js:7848:20)

Thanks. Fixed!

Looking into the implementation of the read_term/3 predicate, it seems like all the necessary bits to support a term_position(Position) option are there. This option would return the same opaque term  returned by the stream_property(Stream, position(Position)). Worthwhile if Position would be the start of the term not counting any whitespace or comments that precede it (something that is not possible by calling the stream_property/2 predicate).


Initial documentation

High level list (can be split into smaller issues)

[x] #265
[x] #268
[ ] #269
[ ] #270
[ ] #271
[x] #272
[x] #273

Incredibly simple proposal:  OpenDP currently has some jupyter notebooks in python/examples/. It would be very easy to use Binder and include links to that from the documentation, making quick-starts even easier. (Binder will build and host docker containers that run jupyter notebooks, so that you can run them a webpage, without having to download everything and run jupyter yourself).
OpenDP Binder Link


how to use customDataSourceRenderer  at setDataSouce ?

i have a customDataSourceRenderer and it works great at initiation. How can i make calendar use my customDataSourceRenderer at all setDataSource method calls ?

thanks.

HI, do you mean something like when you change the year that the customDataSourceRenderer is not being used or something like that? If it's use the event yearChanged
You can see it by example on #71

I'm trying something like this;
$('#calendar').calendar({
customDataSource: aCustomEventSource,
customDataSourceRenderer: function(element, date, events) {
//some custom styling here
}
});
//customDataSourceRendering succeeded here.
....
.somethingHappenedAtMyRuntime(function (){
newCustomEventSource = $.get("/newEventLİst");
$('#calendar').data('calendar').setDataSource(newCustomEventSource);
//customDataSourceRendering failed here!!
})


fix(karma): fixes webpack error "Module not found"

"Module not found: Error: a dependency to an entry point is not allowed" was the full error.
There seemed to be an issue with app.spec.js living in ./app/ while using the var context = require.context('./', true, /\.spec\.js$/); test registration pattern.

Coverage remained the same at 24.933% when pulling d401ab3d0a158bcee230315e37e5bdf9fe97b63d on webpack-testing-fixes into a32d5bb270f462774f4678e98d7221ee22bd4d40 on master.


realpath: add -L and -P command-line arguments

This is my second attempt at adding these, see pull request #2530. (In this one I have tried to minimize the changes to uucore::fs to only the changes required to get the new features to work.)
Partially resolves issue #2253.
This pull request adds the -L (logical) and -P (physical) command-line arguments to realpath. The -L option makes the program resolve ".." components before symbolic links. The -P option makes the program resolve symbolic links as they are encountered. This also changes the default behavior of realpath from the -L behavior to the -P behavior. This matches the behavior of GNU realpath. I don't fully understand all the things that -L is supposed to do, but this is a start, and seems to match the basic tests in the GNU coreutils test suite.

I guess you saw that some of the windows tests are failing

    test_realpath::test_logical
    test_realpath::test_logical_overrides_physical
    test_realpath::test_physical
    test_realpath::test_physical_default
    test_realpath::test_physical_overrides_logical

Well... I just merged https://github.com/uutils/coreutils/pull/2459 which basially implemented the same feature. I wasn't aware that this PR existed as well. Is there a difference in functionality between this PR and the other one? Maybe we can at least keep the tests from this PR.

Is there a difference in functionality between this PR and the other one? Maybe we can at least keep the tests from this PR.

I don't think there is a difference in functionality. It looks like that other pull request was able to resolve the Windows issues I was having here. The only additional test cases in this pull request are for -L overriding -P, and vice versa, which doesn't seem all that valuable. But I can add them in a new pull request if desired. Otherwise, I'm just going to close this.


Inconsistent debugger status when debuggee is paused/continued really fast

I am in a situation where my debugger (codelldb) attaches to a gdbserver instance in a paused state and immediately continues it (as part of the connection steps). This causes two DAB events to be sent really fast to VSCode: paused & continued. It appears that the processing of the continued event is much faster than the paused event and both are treated asynchronously so the VSCode UI ends up in a "paused" state even though the debuggee really is in a "running" state. I found that adding a Queue in the style of outputQueue in vs/workbench/contrib/debug/browser/debugSession.ts would serialize the processing of these status events and keep the end result coherent and I'm sending a PR with that proposed solution.

Temporarily reverting this due to https://github.com/microsoft/vscode/issues/181485- I will restore it with a better fix for the underlying issue


chromePackage

not sure but seems chromePackage not working.
I can not see that task available in sbt console.

Could you provide more information? What error do you have? Could you upload the project configuration which doesn't work?

could it be that you forgot to enable the plugin for your project? Your build.sbt should look something similar to this https://github.com/lucidd/chrome-system-monitor/blob/master/build.sbt

It simply says that that task does not exist.
On 7:01AM, Sat, May 7, 2016 Roen00<EMAIL_ADDRESS>wrote:

Could you provide more information? What error do you have? Could you
upload the project configuration which doesn't work?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/lucidd/scala-js-chrome/issues/6#issuecomment-217629034

yep. good. thx.


error using my own trained model to test.

Hi,
I've trained a model following the toy example. And using the model to test the iiit5k data. While error happens:
"../Attention-OCR/src/model/model.py" line 182, in init
self.saver_all = tf.train.Saver(tf.all_variables())
an exception is throwed:
tensorflow.python.framework.errors.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shap=[1024] rhs shape=[2048]
When using the author's model trained on Synth 90K to test iiit5k , everythin is ok and finally get "2034.98 out of 3000 correct".
Could anybody explain this? Thanks a lot.

I got a similar error when trying to run with the pre-trained model (http://www.cs.cmu.edu/~yuntiand/model.tgz)
File ".../tensorflow/Attention-OCR/src/model/model.py", line 191, in init
self.saver_all.restore(self.sess, ckpt.model_checkpoint_path)
File "../tensorflow/lib/python2.7/site-packages/tensorflow/python/training/saver.py", line 1105, in res
tore
...
File ".../tensorflow/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 728, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shape= [39,20] rhs shape= [39,10]
here's my command
python src/launcher.py --phase=test --visualize --data-path=evaluation_data/svt/test.txt --data-base-dir=evaluation_data/svt --log-path=log.txt --load-model --model-dir=model --output-dir=results

Make sure that the model parameters (such as target embedding size, number of hidden units) are set the same as in the training phase. When loading a model that has different structure from the current paramters, a mismatch of shape would occur.

@da03 I used your pre-model with SVN data to test, i meet a problem when the program run for a short time and stop
 Attention-OCR-master/src/model/model.py:381:VisibleDeprecationWarning:using a non-integer number will result in an error in the future
attention_orig[i]=attention[i/4-1]
 Attention-OCR-master/src/model/model.py:388:VisibleDeprecationWarning:using a non-integer number will result in an error in the future
attention_orig[i]=attention[i/4-1]

the result has some output but not all, just 200/647

See #12 . Seems that the new keras version is different from the old one. I know that it is really annoying, but both keras and tensorflow have changed their interface since this code was released. I would suggest re-training a model from scratch.


Integration with LTN Combinator

LTN Tracker had an integration with the LTN Combinator mod.  If an LTN combinator was attached to the LTN stop, then you could view and change the settings on the LTN Combinator from the LTN Tracker UI.
I suggest that you add this feature to LTN Manager.

This is already in. Shift+click the station's name.

Hmm... that doesn't seem to do the same thing.  Shift clicking the station name just takes me to the map view of the station.  LTN Tracker opened the combinator UI for the LTN combinator, without going to map view.

Ah.  Perhaps that's it.  I am on 0.1.10.  I thought I was up to date because it doesn't show in the "Updates" tab.  But... I am running Factorio version 0.18.21, because a lot of mods broke on 0.18.22, and I haven't tested them on 0.18.22 yet.  I see that the latest version has a dependency on a more current version of Factorio.
Thanks for your help, sorry about the confusion!


Update build to use jessie and add separate wheezy build container

Update calico/build to use jessie, add a new wheezy build container (for building older versions of calicoctl)

Lgtm


the cell index is not consequent when create tiles

**Godot version:3.1.2
OS/device including version:
Issue description:
When create tile use the new single tile button, the cell index is not consequent after delete some tiles.
Steps to reproduce:

add some new tiles
delete some tiles
add some new tiles

the cell index of the tile is not consequent, the index of deleted cell will not used.
Minimal reproduction project:

Changing the way tile indexes are generated can have effects on existing tilemaps. If you delete a tile, it's normal that there are non-contiguous indexes, because if you shift the others down to fill the gap, it will destroy your tilemaps.
Now, knowing that there can be holes anyways, I wonder why you would want indexes to be re-used with new tiles.  What is the actual problem you are trying to solve?

it's quite easy to make a mistake when drag and select a region to make a tile, so delete it and select it again happened very frequently.
So even before filling any tiles in the map, the tileset I got is full of holes. It's very ugly and not easy to check the range of index.

If I deselect a tile by mistake, it's possible to select it again as the same index, that really broke the code.

It's interesting because up to now, I've always used the conversion workflow where you convert scenes with named nodes into tiles. Which means every tile had a name, and I never had to worry about IDs.
But if you make your tiles by barely selecting them around and not giving them any name that you choose, I feel using whatever ID the engine gives you is quite some trouble... I'm not really used to the new tiles editor tbh

I'm also used to the original way to make tileset.
I do not mean, when delete a tile, all the other tiles should be shift to keep the index consequent.
What I suggest is, for example, I have created tiles with index from 0 to 9, then I delete the tile 0 by mistake, I would like to select it again as tile 0, but now it is tile 10.
Maybe it would be better to let the  id configurable. Also take the above example,When I select the tile 0 again, the new id would be 10, but we can change it to 0 manually.

Actually when taking a quick look I think you can still give a name to tiles:

Yes,  the name can be customized. But the name of the tile can not be get from a cell directly, it require an additional step by calling the tile_get_name in TileSet.
If the TileMap have api like get_cell_name(cell), the name of the tile can also to be used to determine which tile is in the selected cell.

In my TileSet I have the tile_ids 1, 2, 4 and 5. It seems that when I use world_to_map and get_cellv, when the position is over a blank tile, it somehow returns with 3.
`func is_on_ladder() -> bool:
var value = false
var tile_id = tilemap.get_cellv(tilemap.world_to_map(position))
if tile_id != TileMap.INVALID_CELL:
	print(tile_id) # -> prints 3
	if tilemap.tile_set.tile_get_name(tile_id) == "ladder":
		value = true

return value`

My problem is, that 3 actually is not INVALID_CELL (-1), so I get lots of errors Condition ' !tile_map.has(p_id) ' is true. returned: String()
Any ideas how to fix?

Is there any way to intentionally fill gaps in IDs by now? A project I'm working on bases physics on tile IDs, specifically acting as a heightmap, and it's frustrating to have to recreate from scratch every time an ID is off-by-one.

you can renumber and pack and reorder by editing this list at end of file... maybe bit easier then recreate from scratch
[resource]
sources/0 = SubResource("TileSetAtlasSource_bqlht")
sources/1 = SubResource("TileSetAtlasSource_7tsy3")
sources/2 = SubResource("TileSetAtlasSource_yrua3")
sources/3 = SubResource("TileSetAtlasSource_0kgob")
sources/4 = SubResource("TileSetAtlasSource_i7o2d")
sources/5 = SubResource("TileSetAtlasSource_b32ox")
sources/6 = SubResource("TileSetAtlasSource_fi2r4")
sources/7 = SubResource("TileSetAtlasSource_ihee1")
sources/8 = SubResource("TileSetAtlasSource_0tsdn")
sources/9 = SubResource("TileSetAtlasSource_wl51w")


azureml.widgets doesn't work in Azure notebook

when running the following in Azure Notebook, it says "No module named 'azureml.widgets'"
from azureml.widgets import RunDetails
RunDetails(local_run).show()
When I try to run the command to install the widget within jupyter environment, I get the following error.
module 'azureml' has no attribute 'widgets'
Please fix this so we can run this in Azure Notebook

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 68a3df81-6871-c443-c413-16bb97982bd4
Version Independent ID: 5030fc51-ec28-d96e-fe85-a06a8fa1ce6f
Content: Tutorial: Train a classification model with automated machine learning - Azure Machine Learning service
Content Source: articles/machine-learning/service/tutorial-auto-train-models.md
Service: machine-learning
GitHub Login: @nacharya1
Microsoft Alias: nilesha

@maximuslee1226
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate
@nacharya1 Hi, can you please take a look of this issue? If I should assign to other employee, please tell me. Thanks.

The newest sdk change with azureml.widgets is not yet deployed to Azure Notebooks. Please try to use azureml.train.widgets

I tried it and it's giving me error displaying widget. the below is the code that I executed.
from azureml.train.widgets import RunDetails
RunDetails(local_run).show()
Error displaying widget
Thanks,

@maximuslee1226 please put any notebook issues here. https://github.com/Azure/MachineLearningNotebooks/issues and refer to the notebook in question.
This is not a documentation bug. Thanks for your report.  #please-close

@maximuslee1226
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

I'm having the same issue

@aribornstein - please post this SDK issue: https://github.com/Azure/MachineLearningNotebooks/issues


Error deploying/starting business network on Composer Playground

I followed this guide to deploy a HLFV1.1 network with composer on IBM Kubernetes Service but am getting the following error when trying to deploy a network:

Error trying to start business network. Error: No valid responses from any peers. Response from attempted peer comms was an error: Error: 2 UNKNOWN: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm ERR! code ENOTFOUND npm ERR! errno ENOTFOUND npm ERR! network request to https://registry.npmjs.org/composer-common failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2018-09-28T16_23_46_620Z-debug.log "

Steps to reproduce:

Follow guide at https://ibm-blockchain.github.io/ for creating the network on a free cluster
Go to your playground instance and try deploying a business network

@odrodrig @timroster This is due to changes in the way IBM K8s handles creation of new containers now. Because of this change it no longer possible to run node.js chaincode in this environment.
As a result support for Composer has been removed and the scripts updated to reflect this.