Moving resource renames dependents to *.depren

Godot version
v4.0.alpha.custom_build [f4b0c7a1e]
System information
Arch Linux 5.15.34-1-lts
Issue description
Note that the scene and script were not open.

Steps to reproduce

Move the script to a different directory or move the entire directory

Minimal reproduction project
test1.zip

Can you reproduce this on 3.4.4?

Cannot reproduce in 3.4.4 nor 3.5.beta4

This still seems to be happening on alpha 7.

cc @timothyqiu

@markdibarry Can you provide some instructions on how to reproduce it? The steps in OP works fine for me.

I haven't delved into a new project to make a minimal reproduction, but here's a project with a build off of cbdc33b.
In this case, MetalHockeyStick.tscn is an inherited scene from HockeyStick.tscn.
https://user-images.githubusercontent.com/21325943/166110068-36f05e8d-2626-4fa5-9636-950a459d6d07.mp4

Built from a commit yesterday, and still having the issue. Created a minimal repro:
Depren_bug.zip

I am unable to reproduce the extra .depren file with the MRP on Arch Linux. Maybe only reproducible on Windows? (I don't have access to a Windows machine right now, so I am not sure.)

I am on a Windows machine, so that may be the case.

I cannot reproduce on Arch (same setup as original post)

Did a fresh build this morning on another Windows machine, and MRP still has the issue, so I guess we can confirm it's Windows (not sure about Mac) specific.

CC @godotengine/windows

Seems like ResourceLoaderText is holding multiple references to the source file, and one unref is not enough (before making FileAccess/DirAccess ref. counted, close call was leaving a bunch of invalid file access handles).


program not responding and Finder becomes white

Issue Type: Bug
Yesterday, after opening the C file, mac set asleep. With awaking mac today morning, the program is not responding. After the forced termination, the desktop becomes white. Restarting Finder is also invalid. Finally, only restored mac solved this problem
VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T07:04:11.329Z)
OS version: Darwin x64 16.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 4, 2

Memory (System)
16.00GB (4.30GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron -psn_0_299081

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

code-gnu-global
aus
0.2.2

vscode-markdownlint
Dav
0.20.0

cpptools
ms-
0.18.1

(1 theme extensions excluded)

Do you meant that you think vscode breaking caused finder to break and you needed to restart to fix your mac?

Do you meant that you think vscode breaking caused finder to break and you needed to restart to fix your mac?

Yes, but not break exactly, Finder is serving fine, just the desktop becomes white. The white  can not be fix even restart Finder.

FYI @bpasero, looks like maybe a macOS bug? Not sure this is actionable on our end.

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


Handling iOS Smart Invert with accessibilityIgnoresInvertColors

Is it possible to set the accessibilityIgnoresInvertColors property of Image view on iOS to ensure that the images are not inverted when using Smart Invert on iOS in particular

Turns out it's as simple as adding accessibilityIgnoresInvertColors={true} to the element (it works on fast-image just like any other element).


Create script to "prep" hosted service items for extract

The publishing process in the Ops Server config scripts for publishing hosted services requires identifying the "original" (i.e. referred to as "orphaned") hosted service item, but there is no way to  identify between the "original" hosted service items and those items referencing hosted service URL created by "saving layer" in web map. So we need to add an identifier (i.e. "Hosted Service" tag) on each hosted service item in the source portal before extracting the portal items.

Script has been created. Exists in elinz/ops-server-config (v.next branch).

Verified.


fix: duplicate key

Rationale
Close #1205
Detailed Changes
Introduce such mechanism to ensure the shared storage won't be still in use after table is closed:
Do reference count for the table-level usage of the wal & object store (shared storages), and wait for all the references dropped before close table.
Test Plan

Should pass all the tests in the ci.
The relevant logs should occur when table is closed.

More code refactoring about TableData, TableImpl and Instance is necessary before this changeset.


请问，怎么样通过docker-compose一键部署

目前没折腾，我考虑下

wget https://github.com/IITII/pic_online_backend/blob/main/docker-compose.yml
docker-compose up -d

运行报错如下：
[2023-06-25T12:20:22.754Z] INFO  pic/$NODE: Service '$node' started.
[2023-06-25T12:20:22.754Z] WARN  pic/FILE: Deal finish, time: 0.02s
[2023-06-25T12:20:22.758Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
[2023-06-25T12:20:22.758Z] WARN  pic/FILE: Deal finish, time: 0.00s
[2023-06-25T12:20:22.765Z] INFO  pic/REGISTRY: 'file' service is registered.
[2023-06-25T12:20:22.765Z] INFO  pic/FILE: Service 'file' started.
[2023-06-25T12:20:22.766Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
[2023-06-25T12:20:22.767Z] INFO  pic/REGISTRY: 'api' service is registered.
[2023-06-25T12:20:22.768Z] INFO  pic/API: Service 'api' started.
node:events:491
throw er; // Unhandled 'error' event
^
Error: EISDIR: illegal operation on a directory, read
Emitted 'error' event on ReadStream instance at:
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -21,
code: 'EISDIR',
syscall: 'read'
}
Node.js v18.16.1

文件夹映射问题？你子目录里面有软链？
docker-compose logs > log.log 还有启动命令都贴出来
你也可以手动把 entrypoint 改成bash 手动去访问目录， 看看是否正常

pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:36:54.632Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:36:54.634Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:36:54.635Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:36:54.636Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:36:54.636Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:36:54.640Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:36:54.640Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:36:54.648Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:36:54.649Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:36:54.650Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:36:54.653Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:36:54.769Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:36:54.770Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:36:54.783Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:36:54.783Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:54.784Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:36:54.784Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:36:54.784Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:54.784Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:36:54.788Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:36:54.788Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:54.788Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:36:54.789Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:36:54.789Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:54.965Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:36:54.974Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:36:54.975Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:36:54.975Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:36:54.976Z] WARN  pic/FILE: Cache init failed: Unexpected end of JSON input
pic_online  | [2023-06-26T01:36:54.977Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:36:54.977Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:36:54.982Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:36:54.982Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:36:54.983Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:36:54.985Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:36:54.986Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:36:56.412Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:36:56.414Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:36:56.414Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:36:56.415Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:36:56.416Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:36:56.419Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:36:56.419Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:36:56.427Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:36:56.428Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:36:56.429Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:36:56.432Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:36:56.554Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:36:56.555Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:36:56.569Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:36:56.570Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:56.570Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:36:56.570Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:36:56.570Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:56.571Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:36:56.574Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:36:56.575Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:56.575Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:36:56.575Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:36:56.575Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:56.751Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:36:56.759Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:36:56.761Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:36:56.761Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:36:56.762Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:36:56.762Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:36:56.768Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:36:56.768Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:36:56.769Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:36:56.770Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:36:56.771Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:36:58.233Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:36:58.235Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:36:58.235Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:36:58.237Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:36:58.237Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:36:58.240Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:36:58.241Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:36:58.248Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:36:58.249Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:36:58.250Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:36:58.253Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:36:58.370Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:36:58.371Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:36:58.384Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:36:58.385Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:58.385Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:36:58.385Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:36:58.385Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:58.385Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:36:58.389Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:36:58.389Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:58.390Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:36:58.390Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:36:58.390Z] INFO  pic/API:
pic_online  | [2023-06-26T01:36:58.574Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:36:58.583Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:36:58.584Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:36:58.584Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:36:58.585Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:36:58.586Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:36:58.590Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:36:58.591Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:36:58.592Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:36:58.593Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:36:58.593Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:37:00.256Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:37:00.257Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:37:00.258Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:37:00.259Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:37:00.260Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:37:00.263Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:37:00.263Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:37:00.271Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:37:00.272Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:37:00.273Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:37:00.276Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:37:00.396Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:37:00.397Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:37:00.410Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:37:00.410Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:00.411Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:37:00.411Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:37:00.411Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:00.411Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:37:00.415Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:37:00.415Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:00.416Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:37:00.416Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:37:00.416Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:00.590Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:37:00.598Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:37:00.599Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:37:00.600Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:37:00.601Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:37:00.601Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:37:00.606Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:37:00.606Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:37:00.608Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:37:00.609Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:37:00.610Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:37:02.672Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:37:02.674Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:37:02.674Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:37:02.676Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:37:02.676Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:37:02.679Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:37:02.680Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:37:02.687Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:37:02.688Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:37:02.689Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:37:02.692Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:37:02.810Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:37:02.811Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:37:02.824Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:37:02.824Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:02.824Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:37:02.825Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:37:02.825Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:02.825Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:37:02.829Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:37:02.829Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:02.829Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:37:02.830Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:37:02.830Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:03.013Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:37:03.022Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:37:03.023Z] WARN  pic/FILE: Deal finish, time: 0.02s
pic_online  | [2023-06-26T01:37:03.023Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:37:03.025Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:37:03.025Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:37:03.030Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:37:03.030Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:37:03.032Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:37:03.033Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:37:03.034Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:37:05.872Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:37:05.874Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:37:05.874Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:37:05.876Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:37:05.876Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:37:05.879Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:37:05.880Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:37:05.887Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:37:05.888Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:37:05.889Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:37:05.892Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:37:06.008Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:37:06.009Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:37:06.023Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:37:06.023Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:06.024Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:37:06.024Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:37:06.024Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:06.024Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:37:06.028Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:37:06.028Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:06.029Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:37:06.029Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:37:06.029Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:06.201Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:37:06.210Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:37:06.211Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:37:06.212Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:37:06.213Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:37:06.213Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:37:06.218Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:37:06.219Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:37:06.220Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:37:06.221Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:37:06.222Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1
pic_online  |
pic_online  | ><EMAIL_ADDRESS>start
pic_online  | > node App.js
pic_online  |
pic_online  | [2023-06-26T01:37:10.668Z] INFO  pic/BROKER: Moleculer v0.14.29 is starting...
pic_online  | [2023-06-26T01:37:10.670Z] INFO  pic/BROKER: Namespace:
pic_online  | [2023-06-26T01:37:10.670Z] INFO  pic/BROKER: Node ID: pic
pic_online  | [2023-06-26T01:37:10.672Z] INFO  pic/REGISTRY: Strategy: RoundRobinStrategy
pic_online  | [2023-06-26T01:37:10.672Z] INFO  pic/REGISTRY: Discoverer: LocalDiscoverer
pic_online  | [2023-06-26T01:37:10.675Z] INFO  pic/BROKER: Cacher: MemoryCacher
pic_online  | [2023-06-26T01:37:10.676Z] INFO  pic/BROKER: Serializer: JSONSerializer
pic_online  | [2023-06-26T01:37:10.683Z] INFO  pic/BROKER: Validator: FastestValidator
pic_online  | [2023-06-26T01:37:10.684Z] INFO  pic/TRACER: Tracing: Enabled
pic_online  | [2023-06-26T01:37:10.685Z] INFO  pic/TRACER: Tracing exporter: ConsoleTraceExporter
pic_online  | [2023-06-26T01:37:10.688Z] INFO  pic/BROKER: Registered 14 middleware(s).
pic_online  | [2023-06-26T01:37:10.810Z] INFO  pic/API: API Gateway server created.
pic_online  | [2023-06-26T01:37:10.811Z] INFO  pic/API: Register route to '/limit'
pic_online  | [2023-06-26T01:37:10.823Z] INFO  pic/API: ♻ Generate aliases for '/limit' route...
pic_online  | [2023-06-26T01:37:10.824Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:10.824Z] INFO  pic/API: Register route to '/dev'
pic_online  | [2023-06-26T01:37:10.825Z] INFO  pic/API: ♻ Generate aliases for '/dev' route...
pic_online  | [2023-06-26T01:37:10.825Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:10.825Z] INFO  pic/API: Register route to '/admin'
pic_online  | [2023-06-26T01:37:10.829Z] INFO  pic/API: ♻ Generate aliases for '/admin' route...
pic_online  | [2023-06-26T01:37:10.829Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:10.829Z] INFO  pic/API: Register route to '/api'
pic_online  | [2023-06-26T01:37:10.830Z] INFO  pic/API: ♻ Generate aliases for '/api' route...
pic_online  | [2023-06-26T01:37:10.830Z] INFO  pic/API:
pic_online  | [2023-06-26T01:37:11.002Z] INFO  pic/REGISTRY: '$node' service is registered.
pic_online  | [2023-06-26T01:37:11.011Z] WARN  pic/FILE: Read finish, time: 0.01s dir: 0, file: 0, dir: /pic/data/images
pic_online  | [2023-06-26T01:37:11.012Z] WARN  pic/FILE: Deal finish, time: 0.01s
pic_online  | [2023-06-26T01:37:11.012Z] INFO  pic/$NODE: Service '$node' started.
pic_online  | [2023-06-26T01:37:11.014Z] WARN  pic/FILE: Read finish, time: 0.00s dir: 0, file: 0, dir: /pic/data/video
pic_online  | [2023-06-26T01:37:11.014Z] WARN  pic/FILE: Deal finish, time: 0.00s
pic_online  | [2023-06-26T01:37:11.019Z] INFO  pic/REGISTRY: 'file' service is registered.
pic_online  | [2023-06-26T01:37:11.019Z] INFO  pic/FILE: Service 'file' started.
pic_online  | [2023-06-26T01:37:11.020Z] INFO  pic/API: API Gateway listening on http://<IP_ADDRESS>:8089
pic_online  | [2023-06-26T01:37:11.021Z] INFO  pic/REGISTRY: 'api' service is registered.
pic_online  | [2023-06-26T01:37:11.022Z] INFO  pic/API: Service 'api' started.
pic_online  | node:events:491
pic_online  |       throw er; // Unhandled 'error' event
pic_online  |       ^
pic_online  |
pic_online  | Error: EISDIR: illegal operation on a directory, read
pic_online  | Emitted 'error' event on ReadStream instance at:
pic_online  |     at emitErrorNT (node:internal/streams/destroy:151:8)
pic_online  |     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
pic_online  |     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
pic_online  |   errno: -21,
pic_online  |   code: 'EISDIR',
pic_online  |   syscall: 'read'
pic_online  | }
pic_online  |
pic_online  | Node.js v18.16.1

构建镜像：
docker build -t iitii/pic_online .
运行实例:
docker run -itd --name pic001 -p 8089:8089 iitii/pic_online:latest
访问http://ip:8089/pic
这样是可以运行的。
就是通过docker-compose启动报上面的错，一直重启

通过如下命令启动，图片加载不出来  docker run -itd --name pic_online1 -p 8089:8089 -v /home/user01/images:/pic/data/images -e MOLECULER_DDNS_ENABLE:false iitii/pic_online:latest
Uncaught (in promise) Error: Image failed to load!And failed src was: http://<IP_ADDRESS>:8089/images/5_008.jpg
    at vendor.571e4b47.js:62:75741
    at Z._log (vendor.571e4b47.js:62:76377)
    at vendor.571e4b47.js:62:75724
(anonymous) @ vendor.571e4b47.js:62
_log @ vendor.571e4b47.js:62
(anonymous) @ vendor.571e4b47.js:62
Promise.catch (async)
_setImageSrc @ vendor.571e4b47.js:62
(anonymous) @ vendor.571e4b47.js:62
(anonymous) @ vendor.571e4b47.js:62
vendor.571e4b47.js:62 Uncaught (in promise) Error: Image failed to load!And failed src was: http://<IP_ADDRESS>:8089/images/5_010.jpg
    at vendor.571e4b47.js:62:75741
    at Z._log (vendor.571e4b47.js:62:76377)
    at vendor.571e4b47.js:62:75724

需要指定 NAS_DOMAIN 为实际 ip 或者 域名. ip 推荐为容器 ip. 如果是 host 模式, 可以写宿主机 ip

我更新了 compose 文件和 镜像, 待会重新拉取下试试吧 @zolagz @yyqAlisa


Error on migration generation

Getting this error:
nicolaswidart@Nicolass-Mac-mini-2 ~/Sites/Maatwebsite/TrendsShop/TrendsShop (master●)$ art module:migration add_products_table Product                                                             [ruby-2.0.0p481]

  [Pingpong\Generators\Exceptions\InvalidMigrationNameException]

Hm looks like migrations need to start with create_


bug creating thumbnail for rgb tiff

🐛 Bug
haven't had the time to dig into it yet, but loading this tiff from the cellpose test data causes an exception in thumbnail creation (i think it has to do with it being an RGB tiff):
https://www.dropbox.com/s/93fqj6usq26u980/000_img.tif?dl=0
Traceback (most recent call last):
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/_qt/qt_viewer.py", line 947, in dropEvent
    self.viewer.open(filenames, stack=bool(shift_down))
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/components/viewer_model.py", line 857, in open
    self._add_layers_with_plugins(
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/components/viewer_model.py", line 930, in _add_layers_with_plugins
    added.extend(self._add_layer_from_data(*_data))
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/components/viewer_model.py", line 1004, in _add_layer_from_data
    layer = add_method(data, **(meta or {}))
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/components/viewer_model.py", line 695, in add_image
    layer = Image(data, **kwargs)
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/image/image.py", line 290, in __init__
    self._update_dims()
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/base/base.py", line 570, in _update_dims
    self.refresh()
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/base/base.py", line 974, in refresh
    self._update_thumbnail()
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/image/image.py", line 740, in _update_thumbnail
    self.thumbnail = colormapped
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/base/base.py", line 735, in thumbnail
    thumbnail = np.pad(thumbnail, pad_amounts, mode='constant')
  File "<__array_function__ internals>", line 5, in pad
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/numpy/lib/arraypad.py", line 743, in pad
    pad_width = _as_pairs(pad_width, array.ndim, as_index=True)
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/numpy/lib/arraypad.py", line 514, in _as_pairs
    raise ValueError("index can't contain negative values")

> /Users/talley/Dropbox (HMS)/Python/forks/napari/napari/layers/base/base.py(735)thumbnail()
    733         padding_needed = np.subtract(self._thumbnail_shape, thumbnail.shape)
    734         pad_amounts = [(p // 2, (p + 1) // 2) for p in padding_needed]
--> 735         thumbnail = np.pad(thumbnail, pad_amounts, mode='constant')
    736
    737         # blend thumbnail with opaque black background

ipdb> padding_needed
array([  31,    0, -509])
ipdb> self._thumbnail_shape
(32, 32, 4)
ipdb> thumbnail.shape
(1, 32, 513)

I have the same issue, but it seems unrelated to TIFF. Reproduced with:
import napari
import numpy as np

image = np.random.random((1024, 1024, 50))
viewer = napari.view_image(image, rgb=True)

Confirmed on current HEAD.

this is "fixed" in that a better error message is now given in #4630
ValueError: 'rgb' was set to True but data does not have suitable dimensions.


Main Menu Crash: ConcurrentModificationException on Asynchronously building [color] search tree

Game crashes as soon as main menu should be shown.
Vanilla Fix mod handle the crash, so i still could play.
Crash stack trace:
java.util.ConcurrentModificationException: null
	at java.util.WeakHashMap$HashIterator.remove(WeakHashMap.java:821) ~[?:1.8.0_51]
	at zone.rong.loliasm.client.sprite.FramesTextureData.onClientTick(FramesTextureData.java:34) ~[FramesTextureData.class:?]
	at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_3440_FramesTextureData_onClientTick_ClientTickEvent.invoke(.dynamic) ~[?:?]

Considering stack trace pointing to loliasm, this fatal happens right after this line, so i though HEI is actual issue reason:
[pool-13-thread-1/INFO] [HadEnoughItems]: Asynchronously building [color] search tree...

I tried to reload game and got same crash at exact same place.
debug.log

Fixed in dev: https://github.com/LoliKingdom/LoliASM/issues/84


Use dnspython fork fixing the crashes on multicasts

dnspython has a bug which causes ArchiveBot jobs to crash in certain circumstances (see ArchiveTeam/wpull#365). This bug was fixed on the master branch nearly two years ago, yet there is still no release containing this fix. When asked about this in early August, the author said he's planning for a release in early September.
*tumbleweed*
This switches ArchiveBot pipelines to a fork of dnspython which is simply the last release (from mid-2016) plus the relevant bug fix.
Todos before merging:

[ ] Test it. The dnspython test suite passes. I haven't tested the script in https://github.com/ArchiveTeam/wpull/issues/365#issuecomment-429622772 yet. It also needs testing in combination with the pipeline/wpull.
[ ] Figure out the upgrade path. My guess is that it requires a manual pip uninstall dnspython followed by reinstalling using pipeline/requirements.txt.

With the release of dnspython 1.16.0, this should be obsolete, but I haven't tested wpull with that version yet, so I'll leave the PR open for now.

We recently had a crash on Igloo-EU-Hetz02 which is running dnspython 1.16 so this appears to still be an issue.
I'll try and do some more debugging with the development environment we now have

@Ghostofapacket Igloo-EU-Hetz02 is running dnspython 1.15.0 or older based on the line numbers in the traceback (e.g. job f9jpjzgietqs4fokdqxjc8lw). Note that wpull depends on dnspython3, not dnspython; dnspython3 is a transitional package nowadays (i.e. simply depends on dnspython) and still at version 1.15.0 on PyPI. One would have to manually break that dependency and install the newer dnspython version.


1.5 breaks Markdown Preview

When trying to preview a markdown doc using the extension below, the preview panel doesn't open and the following is logged to the console:
Uncaught ReferenceError: baseUrl is not definedVM466:3 (anonymous function)thirdparty.min.js:556 n.accessthirdparty.min.js:557 n.fn.extend.attrmain.js:149 _loadDocmain.js:278 _setPanelVisibilitymain.js:318 _toggleVisibilitythirdparty.min.js:557 n.event.dispatchthirdparty.min.js:557 r.handle
~~~~

https://github.com/gruehle/MarkdownPreview

Key extensions should be tested and extension owners should be notified.

Filed PR upstream, gruehle/MarkdownPreview/pull/88

Closing as not core brackets issue.


No rounded star icon (Firefox 79.0) -> unusable

Hello,
I use this add-on on a Mac running the latest version of Firefox without a problem.
I have just installed it on a PC running Windows 10 and Firefox 79.0. But the specific rounded star icon does not appear.
I have uninstalled and reinstalled the add-on without success. The add-on cannot really be used in that state.
The URL bar with the add-on installed:

Hello,
Finally, after rummaging through the different options (there are "manage the add-on" in Firefox and the settings of the add-on, which confused me), I finally got to activate the icon.
Strange that it was not activated by default.
Issue solved, then.


RFC - simply make format || Please let me know if this is bad idea

Simply running make format which is defined as the following in Makefile.
poetry run black .
poetry run ruff --select I --fix .

When I run make lint on local, there are always hundreds of reformat warnings.  (screenshot below) This seems very annoying as it also hides the .py files which we want to keep format up to date.
It looks like all formatted files are Jupiter notebook notes.
Please let me know if this is a bad idea. I don’t want to introduce any trouble to our community or maintainers as so many files are touched… Please let me know if there is a workaround to mute all warnings and still keep everything clean. Thank you so much!

you have the extension installed that runs format on notebooks - if we want that we should enable it directly

@hwchase17 yeah, make format reminded me in the past that it skipped all jupyter files because of lack of module and it provided a command to install it. I followed the command and enabled it. Since then, my make line result is full with 200+ notebook reformat needed warnings. it’s very hard to find which .py file I also need to reformat.
what’s your suggestion here? Should I disable my jupyter extension instead? Thanks!

doesn’t look like we want to include jupyter notebooks in format control from what hwchase17 shared above. gonna abandon this PR.


chore: add create component client function

Stack:

#1756 ⬅
#1755

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


[JOSS review] test_readNwb fails on first run

The test suite checks whether reading the test.nwb file works, but this file is created by test_writeNwb which does not necessarily run before it (at least on my machine, tests run in alphabetical order).
openjournals/joss-reviews#4706

Thanks for the catch. This has been fixed at c8226f0

Thanks, that fixed the issue for me.


Support for Pandas Dataframes and Set Preprocessing to None

Is your feature request related to a problem? Please describe.
It seems like most (if not all) ART classes expect numpy array inputs in order to correctly create classifiers and adversarial samples. I've only noticed this issue occurring when creating classifiers or using some of the adversarial attacks. Issues I've run into occur because pandas dataframes have different indexing rules (e.g. using .iloc[index] instead of [index]) or are missing expected attributes (e.g. dtype).
The preprocessing parameter is set by default to (0,1), which indicates no change is made to the input. This causes some of the issues described above. Setting the value to None, causes it to skip the preprocessing step, which seems to behave equivalently to (0,1).
Describe the solution you'd like
Support for pandas dataframe inputs for ART classes. One way might be to create a separate input class, which checks the variable type (numpy array or dataframe) and handles it appropriately. This would be beneficial as new input variables can be added in a centralized location and gives users flexibility to add new custom input types.
Additional context
One way to reproduce the issue is to first create a classifier that accepts pandas dataframes. Convert it to an ART classifier. Then call either the predict() or fit() functions. An error will be thrown as part of the preprocessing step. In the preprocessing step, the code checks for the dtype attribute, which dataframes do not have. The current workaround is to set preprocessing to None.
Another issue arises in the Zoo attack. The code indexes the input on line 203
x_batch = x[batch_index_1:batch_index_2]
For numpy arrays, it behaves as expected and returns an array slice with a len equal to the batch size. For pandas dataframes, it returns a 0 size array, which later causes an error on line 205 due to a 0 size array being passed.

Hi @keykholt Thank you for proposing this very useful new feature and for working on implementing it! Let us know anytime if you need any help.


Mo' colors, mo' problems (extended color support?)

Howdy!
First off I want to say thanks for all your hard work on Ratatouille and ExTermbox! They're both really awesome and useful packages.
Now onto my issue 😈
I was wondering if we this could be relaxed to accept any valid color in the extended color palette instead of only the eight, definitely supported everywhere but limited, colors:
https://github.com/ndreynolds/ratatouille/blob/3617e4a8832db596703877615adcdcc50c6e5875/lib/ratatouille/renderer/attributes.ex#L8-L14
I noticed ExTermbox doesn't have any problem with accepting valid integers outside of the eight named colors, but because of that validation Ratatouille does not. I'm imagining something like this would remedy it:
diff --git a/lib/ratatouille/renderer/attributes.ex b/lib/ratatouille/renderer/attributes.ex
index ee1f26b..18403c3 100644
--- a/lib/ratatouille/renderer/attributes.ex
+++ b/lib/ratatouille/renderer/attributes.ex
@@ -6,10 +6,11 @@ defmodule Ratatouille.Renderer.Attributes do
   alias Ratatouille.Constants

   @valid_color_codes Constants.colors() |> Map.values()
+  @valid_color_codes_extended 0x11..0xe8
   @valid_attribute_codes Constants.attributes() |> Map.values()

   def to_terminal_color(code)
-      when is_integer(code) and code in @valid_color_codes do
+  when is_integer(code) and code in @valid_color_codes or @valid_color_codes_extended do
     code
   end

I'd be happy to push a PR if you're interested in this approach, or if you can give some guidance on an approach you'd like (or even why this is all a terrrrrrible idea).
Thank you for your time.

Hi @tehprofessor!  Sorry for the delay here!  Yep, I think this was just an oversight.  I haven't needed to venture outside of the 8 colors yet myself in my projects.  Your proposed changes to loosen the validations look very reasonable.  Happy to merge that if you push up a PR.
Please let me know if you run into any other limitations like this.  This sort of feedback is really helpful :)

Hi @tehprofessor , do you have any progress on your PR mentioned above? I just did some little attempts to remove the validations but with no luck. I'm thinking about diving deeper.

@ndreynolds Sorry the delay on my part! Ha 😄 life comes at you fast. I'll get those changes pushed this weekend, thank you for the reply.
@qhwa removing the validation causes a lot of other breakage if I remember correctly. The above diff was the simplest way I found to accomplish adding the extended colors.


formula: enable unity builds in std_meson_args

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Enabling unity builds^1 can help cut down build times and can
produce faster code.
The downsides of enabling this (e.g. slower incremental rebuilds, larger
memory requirements) aren't as significant for us, so let's enable it by
default.
This can break compilation of some software, so let's add an opt-out.

     Per the relevant section of and text in the Wikipedia article linked in this PR discussed thread's OP, enabling unity builds has potential detrimental effects on program correctness or can otherwise cause miscompilation.  If Homebrew decides to allow unity builds, it should be on a formula-by-formula basis until it can be proven that the potential compilation issues that can manifest with unity builds aren't a problem in most cases, at which point flipping the default might be considered, but only if applying it wouldn't be something that formula authors should think about carefully when writing new formulas to contribute to Homebrew/homebrew-core or their own, third-party taps.  Since there's a non-trivial chance that it would be, considering making unity builds the default behavior, even for a single build system, should, in all likelihood, be met with great skepticism.
     Also, despite the speed-ups they're reported to bring in spite of this, unity builds defeat build parallelism beyond the number of partial unity build files allocated.  (Meson's documentation, also linked to in the OP, states that the build system defaults to using 4sub-unity build jobs.)  This behavior may prove at least partially unintuitive to users who expect higher build parallelism, either generally or for specific  compilation workloads.  Both end users and CI provide machines woth multi-core CPUs; let's not under-utilize/waste them.
     Letting formula authors request unity builds for their formula(s) could still be made easier by providing a new argument to 'std_meson_args.'
     (One further aside:  The kind of developers I've heard advocate for unity builds most often tend to be from a certain class of game developer.  Most formulas aren't for game software.)

Since there's a non-trivial chance that it would be

What makes you say that the chance is non-trivial? Neither of the sources I cite suggest it is.

This behavior may prove at least partially unintuitive to users who expect higher build parallelism, either generally or for specific compilation workloads. Both end users and CI provide machines woth multi-core CPUs; let's not under-utilize/waste them.

The overwhelming majority of Homebrew users don't build formulae from source, so I don't think this is really a significant consideration here.

@carlocab:

Since there's a non-trivial chance that it would be

What makes you say that the chance is non-trivial? Neither of the sources I cite suggest it is.

     From your first reference, Wikipedia's article on unity builds, namely its section titled 'Effects:'

Unity builds have also potentially dangerous effects on the semantics of programs. Some valid C++ constructs that rely on internal linkage may fail under a unity build, for instance clashes of static symbols and symbols defined in anonymous namespaces with the same identifier in different files. If different C++ files define different functions with the same name, the compiler may unexpectedly resolve the overloading by selecting the wrong function, in a way that was not possible when designing the software with the files as different translation units. Another adverse effect is the possible leakage of macro definitions across different source files.[2]

     Also, quoting @eli-schwartz since he explained the concerns I share well:

At the end of the day, whether unity builds works is dependent on the project itself.

I would be very, very wary of making this the default, because I suspect nowhere near the majority of projects compile successfully without leakage between TU-scoped code and local variables. Although this would probably just result in very visible compile errors. 😎

I could see a program slipping past this sanity check and appearing to compile just fine but actually mis-compiling not being any fun trying to debug.  It's a ticking time bomb, ready to blow up in somebody's face.  Don't take the risk; it's too much of one.

The overwhelming majority of Homebrew users don't build formulae from source, so I don't think this is really a significant consideration here.

     This change would also affect builds in bottle CI, would it not?  The number of end users building from source is thus irrelevant.

The overwhelming majority of Homebrew users don't build formulae from source, so I don't think this is really a significant consideration here.

To go further: we also do not support any errors that occur when building from source.

This change would also affect builds in bottle CI, would it not?

And it can be reverted if that's a problem.

The number of end users building from source is thus irrelevant.

@RandomDSdevel that you personally run/ran a fork of Homebrew to build from source seems relevant to note here.

@carlocab I defer to whatever you think best given the above, here. It may be safer to start being opt-in or having this controlled by an environment variable that we can play around with in test-bot and/or homebrew/core but I don't have strong feelings either way. Giving this a ✅ but will leave it up to you to decide when/if to merge (but hold off until next tag regardless, thanks).

@carlocab thoughts on merging or closing this?

Closing this out for now. @carlocab feel free to reopen whenever you're ready to merge.


Workspace symbols not finding all symbols with same name

rust-analyzer version: d6ed146a1 2022-02-22 stable
rustc version: rustc 1.59.0 (9d1b2106e 2022-02-23)
I'm looking for the signature function, so I type it in, but only the Signature struct is found:

If I type in additional text that isn't in the Signature struct name, other results appear, but I'm not able to get to the function named signature, since it doesn't have any extra text to match on:

The project I'm using is Nushell

The # trick does not work in VSCode anymore. Quoting the manual:

Note that filtering does not currently work in VSCode due to the editor never sending the special symbols to the language server. Instead, you can configure the filtering via the rust-analyzer.workspace.symbol.search.scope and rust-analyzer.workspace.symbol.search.kind settings.

I guess I'm a little confused.  Im currently a beta tester for a new text editor that just added a bunch of Rust support via rust-analyzer and it suffers from the same exact issue of not being able to find all symbols of with same name as others, so I would think it's not a VS Code-specific issue, I just reported it using that editor.  I could be misunderstanding this though..

The workspace symbol search by default only searches for types, not functions. In most editors you can append # to widen the search:

But you can also configure it to search in all symbols by default using the settings mentioned above.

Ah ok, I understand now.  My apologies for misinterpreting it and thanks for explaining it to me.  I suppose this should just be closed then.


[PF2E] Bug with system hidden visual

In the PF2E system, when a creature is hidden from another the system applies a "you can hear them but not see them" effect to the token. Using Perceptive, when a creature hides it doesn't show that visual effect until you mouse over the token and then it does, but you have to mouse over it again every time you select the token again. Without perceptive the visual is always there any time you have your token selected and another token is hidden from you. Video below:
https://github.com/Saibot393/perceptive/assets/99048395/66675f8b-178c-48be-acfb-e1a0a17257b4
Also noticed an issue in the case of using Sneak. In this example, Mee'lokk has used Sneak to try to become undetected. He failed but didn't critically fail the sneak check against the Black Tear Cutthroat, so he should become hidden from it (not necessarily other creatures). It also doesn't seem to remove both undetected and hidden if the creature critically fails the sneak check.
Some of this stuff may be too complicated to fix in the module, and if so please just close the issue. One of the PF2E system devs as part of his extra life charity goal this year is going to be implementing system based detection so we'll have it that way eventually anyway.

I will look into it and see what i can do

On problem is, that i can not apply different effects in relation to different tokens. I can therefore not really solve the second problem you described, considering that critical fails are alway in relation to a different tokens perception


Entity definitions (metadata) URL

In order to create a proxy using some tool like OData v4 Client Code Generator (https://marketplace.visualstudio.com/items?itemName=bingl.ODatav4ClientCodeGenerator) We need to provide Entity Definitions.
I have found this: http://localhost:7048/DynamicsNAV110/api//beta/$metadata, but this shows global definitions for all published APIs. Is there a way to get definition for a single entity?

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

ID: 17c4eef7-2ff2-eeeb-d285-095002e99475
Version Independent ID: 2beae6be-8b5f-2a48-4b68-81810248b8f6
Content: Endpoints for the APIs for Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central - Dynamics NAV
Content Source: dynamics-nav/endpoints-apis-for-dynamics.md
Product: dynamics-nav-2018
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for your feedback. We do not support $metadata for a single entity for the API.


activateSort in aria:List not taken into account with default template

The activateSort property of the @aria:List widget was not taken into account with the default list template. There was also an issue with the way the arrow up and arrow down keys were working when the list is sorted. This PR fixes those problems.

@ymeine Thank you for your review and your nice comment!


Jakarta EE 9 integration

Hi
Do you have any plans regarding Jakarta EE 9 integration (namely JAX-RS 3.0) for you swagger-jaxrs2/swagger-integration-modules?
JAX-RS 3.0 was released in November 2020 and some JAX-RS provides already support it (for example, Jersey). Unfortunately the latest of swagger-jaxrs2 (2.1.6) still use JAX-RS 2 as compile dependency and it leads to run-time conflicts with Jersey when application starts.

Please see comments in #3836; closing as duplicate, please add any comments/questions to #3836, I am adding a reference to your comment there.

Please see comments in #3836; closing as duplicate, please add any comments/questions to #3836, I am adding a reference to your comment there.


Add loopback test for SLINK

This PR shows how SLINK can be tested from the testbench. It assumes that there is a SW loopback in the CPU which has yet to be implemented. @stnolting I could use some help with that. Once that is done, the verification components need to be connected to the CPU instead of directly to each other as it's done now. See TODO in the testbench.

This is great! Especially the thing with the random traffic generation, since this is something that verifies the correct stream handshake and also the stream software handling.
Just one questions: what is this? (could you provide a link to the according documentation?)
stall_config => new_stall_config(0.05, 1, 10)

Right now, the simple testbench as well as the advanced one do the same thing. This is good for understanding VUnit (this is good for me! :smile:) but I think we should actually use the VUnit features to do advanced verification.
So I think we should have a new test program (processor_check_xyz?) only for this testbench setup. Then we could focus more on verification of things like streaming and external bus accesses.

Just one questions: what is this? (could you provide a link to the according documentation?)
stall_config => new_stall_config(0.05, 1, 10)

It means "has a 5% probability of generating an stall that lasts between 1 and 10 cycles". See https://github.com/VUnit/vunit/blob/master/vunit/vhdl/verification_components/src/axi_stream_pkg.vhd#L22-L26.
This is the array_axis_vcs example from VUnit with the stall probability of the slave set to 0% or 50%:

It is exactly the same test, it's also a loobpack (but implemented in hardware, instead of a CPU). You can see that execution time is 9us without stall (with probability 0%) and 16us otherwise.

Right now, the simple testbench as well as the advanced one do the same thing. This is good for understanding VUnit (this is good for me! 😄) but I think we should actually use the VUnit features to do advanced verification.
So I think we should have a new test program (processor_check_xyz?) only for this testbench setup. Then we could focus more on verification of things like streaming and external bus accesses.

Absolutely agree. That was the purpose when maintaining a VUnit testbench and also a simple one. After this PR is merged, we should use Wishbone and AXI-Lite VCs for testing the external interface and the bridge. Then, we can remove all the interface related code from the simple testbench.

It means "has a 5% probability of generating an stall that lasts between 1 and 10 cycles". See https://github.com/VUnit/vunit/blob/master/vunit/vhdl/verification_components/src/axi_stream_pkg.vhd#L22-L26.

Thanks for clearing!

After this PR is merged, we should use Wishbone and AXI-Lite VCs for testing the external interface and the bridge. Then, we can remove all the interface related code from the simple testbench.

:+1: :smile:

@stnolting Note that this addition doesn't do anything useful yet. There is a need for a SW test that creates that loopback and once that is done the verification components need to be connected to the SLINK of the CPU. Right now they are only talking directly to each other

Yeah I know and that's ok for now. We need to agree on a concept how to actually utilize the verification features provided by this testbench from a CPU point of view.
Just some ideas :thinking:

create something like sw/example/processor_check2 to have one "large" program that handles all the bus/stream related testings
create several simple programs to test only one thing at a time and execute them all in a CI batch

I like the idea of creating several simple programs instead of a large one. That allows some of the tests to fail without breaking all of them. We want to be able to know whether some bug affects all the peripherals/features or just a few of them.
BTW, tests on Windows are failing. I think we forgot to update https://github.com/stnolting/neorv32/blob/master/.github/workflows/Windows.yml#L104-L113 in some of the latest PRs. @stnolting, @LarsAsplund mind having a look at it?

I like the idea of creating several simple programs instead of a large one. That allows some of the tests to fail without breaking all of them. We want to be able to know whether some bug affects all the peripherals/features or just a few of them.

Me too! We could keep everything in sw/example/processor_check and create one unified main.c and select the according test via a compile switch. Or we could have several sub-folders: one for each test.
I would also like to keep the current processor check to be run using the simple testbench and use the new tests to target only the VUnit-based testbench.

BTW, tests on Windows are failing. I think we forgot to update https://github.com/stnolting/neorv32/blob/master/.github/workflows/Windows.yml#L104-L113 in some of the latest PRs. @stnolting, @LarsAsplund mind having a look at it?

I think there is just a flag missing. I will fix that.

Agree, better start with several small tests to verify individual features. Once we have that we can start thinking about stress tests where we run many things at the same time.

I am not sure yet how to separate the tests. Different files? Different folders? Different flags? :thinking:
As soon as there is a perspective, we can start with testing the stream interface in a new feature branch.

@stnolting, I think the point is to have different tests as different main functions in separated files. It's ok if they share headers and some common utils. Then, one step in the job can be used for building all the hex files. Last, the run.py in VUnit can be used for assinging one hex to each run. In order to do that, we should address #35, so we can reuse the same synthesis/compilation of the RTL sources.
Optionally, we can run VUnit in parallel. However, VUnit can internally paralelise the tests, so I think we won't need more than one job for now. That is, the 2 cores in the machine are enough for getting some time reduction.

With regard to this specific issue, the test is a loopback, so you only need to implement a software function that checks whether something was received and push it back. The VUnit testbench can take care of finalising the simulation after all the data has been sent, received and checked. Therefore, the software can be infinite. That is, first it executes the fixed tests, and then it goes into an infinite loop waiting for AXI Stream data.
That is not the best solution, but it's the simplest for having the VUnit VCs used for something useful. After that, we can focus on #35 and revisit the software and tests.

I think the point is to have different tests as different main functions in separated files. It's ok if they share headers and some common utils. Then, one step in the job can be used for building all the hex files. Last, the run.py in VUnit can be used for assinging one hex to each run. In order to do that, we should address #35, so we can reuse the same compilation of the RTL sources.

:+1:

With regard to this specific issue, the test is a loopback, so you only need to implement a software function that checks whether something was received and push it back. The VUnit testbench can take care of finalising the simulation after all the data has been sent, received and checked. Therefore, the software can be infinite. That is, first it executes the fixed tests, and then it goes into an infinite loop waiting for AXI Stream data.

Good idea, but the current testbench is waiting for a final report, which is printed via UART after the main function has returned. So we cannot use an eternal stream echo loop here. Anyway, I am sourcing out all tests into separated chunks right now. I'm still not sure how to manage all that, but soon we will have a more flexible test program (hopefully 😉)  - also for the stream echo.

Note that the number of data elements that the VCs will send (and expect to receive) through the loopback is defined in the testbench. Hence, you don't need an infinite software procedure, you can set a for loop to n iterations (IIRC, it was set to 100).

We< can set that number from the command line to get a single source.


README badge broken

Small issue, but yeah

@bengreenier This doesn't seem to be fully resolved- The "REPL Build" badge is broken, and the logo doesn't look nice on dark theme:

For images for dark theme, GitHub recently released a feature for that: https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/

@kotx Unfortunately the badges are dependent on shields.io right now, because our workflows aren't named clearly, and GitHub doesn't support name changes as part of their workflow badges, it seems.
Perhaps you are experiencing this issue they mention:

If your GitHub badge errors, it might be because you hit GitHub's rate limits.

I do see them rendering just fine for me:

We currently only have a dark icon for bebop, and creating a light version wasn't in scope i'm afraid. I personally don't think it looks too bad, but maybe we can find time to make a lighter version in the future - Thanks for that feedback and link!


Change size verification of the test to consistent.

The current test uses a mix of assertTrue() and assertEquals() for size assertion.
Change this to consistently use only assertEquals().

Looks good, except that the changes to EmailTest.java have got the wrong indentation. Please can you check and adjust? Thanks

I fixed it.
Thank you so much for checking!

Codecov Report

Merging #158 (8ce86e1) into master (567095f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #158   +/-   ##
=========================================
  Coverage     65.87%   65.87%
  Complexity      305      305
=========================================
  Files            18       18
  Lines          1052     1052
  Branches        138      138
=========================================
  Hits            693      693
  Misses          280      280
  Partials         79       79

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@violetbeach
TY


Update "Configuring server MIME types" article

Request type

[ ] New documentation
[x] Correction or update

Details
The article Properly configuring server MIME types has been incrementally updated over the last 15 years, but it is probably out of date in significant ways. It needs to be reviewed and updated.

@chrisdavidmills I would like to tackle this one

@caraya you are assigned; thanks for helping out!

In reviewing the file there are a lot of issues that will require discussion and full re-writes and probably discussion on what needs to go in this article.
For example, the sample .htaccess file (https://wiki.developer.mozilla.org/en/Sample_.htaccess_file) is not really a .htaccess file but a discussion on what can go into one.  Should we write a full .htaccess file or just concentrate on mime types?
The page is Apache specific. Should we also address NGINX too?
Do we need to keep the historical note about Firefox loading CSS files even if they had the wrong MIME type?
When I worked on Javascript, I did the edits and adds directly on the Wiki, is that still the way to go?

@chrisdavidmills
In reviewing the file there are a lot of issues that will require discussion and full re-writes and probably discussion on what needs to go in this article.

That is fair enough, @caraya . Some of our articles have gone rather out of date.

For example, the sample .htaccess file (https://wiki.developer.mozilla.org/en/Sample_.htaccess_file) is not really a .htaccess file but a discussion on what can go into one. Should we write a full .htaccess file or just concentrate on mime types?

I would provide a full sample .htaccess file, which shows the most important things you should include, and then describe what each bit does, why it is important, etc. The current state of things is a bit misleading.

The page is Apache specific. Should we also address NGINX too?

Probably a good idea, with NGINX being increasing popular.

Do we need to keep the historical note about Firefox loading CSS files even if they had the wrong MIME type? It may lead to confusion

No. Sounds out of date to me.

When I last worked on MDN, I did the edits and adds directly on the Wiki, is that still the way to go?

Yes, that's fine. I am happy to review it there too.

@chrisdavidmills
Ready for review. Still working on .htaccess and nginx equivalency

Thanks @caraya , this looks really good. I've given it a copy edit and tightened up the language a bit.
It would also be nice for @hamishwillee to give this a check over.

@chrisdavidmills @caraya Subedited. I found the English confusing in several parts about whether we were talking about the server or the browser.
In particular I changed the titles of the headings about getting MIME types to make it clear that one is what you set in the server and the other is how you check the MIME type of files your recieved.
There are two significant broken links in https://wiki.developer.mozilla.org/en-US/docs/Learn/Server-side/Configuring_server_MIME_types#How_to_set_up_your_server_to_send_the_correct_MIME_types

If you're using the Apache web server, simply copy this sample .htaccess file to the directory, which contains the files that you want to work with or the parent directory if there are many such directories.

This says you can copy the htaccess file at the link BUT the link is to an obselete MDN doc. The doc is also not something you can copy - its a kind of guide. This needs to be fixed.
Further the NGINX link doesn't exist yet. FYI though, I I renamed snipet > snippets
FWIW I think this is a useful doc. However this is about my existing level of knowledge about MIME types already, so I couldn't say if we were missing anything.

Thanks @hamishwillee !
The two broken links to the example files are because @caraya is still working on them, I believe.

Hi @caraya (@chrisdavidmills)
In that case this will need just a little more work:

The doc says "If you're using the Apache web server, simply copy this Apache configuration examples to the directory, ..."

This links to the top of the doc, which is a set of examples (not just one file you can copy)
You need to perhaps modify this to link to the specific section - e.g. something like: "If you're using the Apache web server, simply copy the section of the .httacces file here: Apache .htaccess Configuration Snippets >Serve resources with the proper media types (a.k.a MIME types) ....

What you might do instead is copy the relevant section into "Configuring Server MIME types" and then have the example files just as "Related links" at the end.
Chris, This page also needs to be "un archived". How does that work?

Chris, This page also needs to be "un archived". How does that work?

To unarchive, it just needs to be moved out of /Archive/ to somewhere else. Should we put this page under /Server-side/ as well? What do you think we should call it?

@chrisdavidmills Thanks!

To unarchive, it just needs to be moved out of /Archive/ to somewhere else.

FYI, I don't think I have necessary rights to do this.

Should we put this page under /Server-side/ as well?

You mean under https://developer.mozilla.org/en-US/docs/Learn/Server-side ? That seems sensible.
Further down the track we might want to expand on our docs. We could perhaps put this in a grouping parent - e.g. /Learn/Server-side/Apache or e.g. _/Learn/Server-side**/Servers**? Maybe too early?
My concern with this doc is that it feels like an orphan. Nowhere do we introduce Apache, Nginx and other alternatives.
Minimally perhaps we could add a section about popular web servers in https://developer.mozilla.org/en-US/docs/Learn/Server-side/First_steps/Introduction ?

What do you think we should call it?

My preference is Apache Configuration: .htaccess (to perhaps one day be accompanied by  Apache Configuration: httpd.conf). If you prefer something more verbose: Apache Server Configuration using .htaccess files

@hamishwillee, @chrisdavidmills

This links to the top of the doc, which is a set of examples (not just one file you can copy)

I was waiting to get the final location before changing the link.  I like the idea of linking directly to the mime type configuration directly.

OK, article moved:
https://developer.mozilla.org/en-US/docs/Learn/Server-side/Apache_Configuration_htaccess
Thanks folks!

@caraya did you ever get round to finishing this one?

@caraya did you ever get round to finishing this one?

The Apache configuration is done. The Nginx is taking way longer than expected. We can close this one and I'll open a new ticket when the Nginx configuration reference is completed.

Sounds good. The article update looks great, BTW, thanks @caraya !


/anaconda3/lib/python3.11/site-packages/causal_conv1d_cuda.cpython-311-x86_64-linux-gnu.so: undefined symbol: _ZN3c107WarningC1ENS_7variantIJNS0_11UserWarningENS0_18DeprecationWarningEEEERKNS_14SourceLocationENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb

I want to ask does anyone know how to solve this problem

me too.


Image/file validation error

#Image/file validation is not working.
Steps for recreating the issue.
=> Use any component of your plugin (i.e. genericForm)
=> just add a <input type="file"> field in a HTML form for image upload
=> add a required and image rule in component required|image
=> submit the form
it won't work
after digging a lot. I see that you have used post() function inside the magicForm.php class for retrieving form data.
The post() function won't accept image input and it is just there for accepting post input.
So to fix that I have created a PR. please accept it and add it to your new version.
Thanks

#226

Hi! I saw your post and I have a doubt related to it...
How can I make file upload required on a Form within magic forms plugin?
Any help will be very welcome!
Thank you in advance!


[BZ-996210] upgrade batik from 1.6-1 to 1.7

the artifacts in version 1.7 (and depMgmt) are
imported from ip-bom

apache-fop, avalon-framework and xmlgraphics-common
were upgraded as well to aligh the dependencies
correctly

this PR needs to be merged together with the one for jbpm-designer

PR for jpm-designer: https://github.com/droolsjbpm/jbpm-designer/pull/50

Can we get this merged?

@ge0ffrey I would be more than happy to do that. But we need fixes in jbpm-designer, so @tsurdilo or @jlindop would need to take another look at that.

I am closing this. It has been around for more than a year and it will likely never be merged. I am keeping the branch around just in case.


Can't load Arial Black as SKTypeface on Windows 10 machine

Description
When specifying the font family name of "Arial Black" on a Windows 10 machine (or Windows Server 2016), SkiaSharp selects "Segoe UI" instead.
Code
SKTypeface tf = SKTypeface.FromFamilyName("Arial Black", SKFontStyleWeight.Bold, SKFontStyleWidth.Normal, SKFontStyleSlant.Upright);

The resulting SKTypeface has these properties:

When loading "Arial Black" as a System.Drawing.FontFamily like this:
FontFamily fontFamily = new FontFamily("Arial Black");

It correctly finds the font:

Expected Behavior
SkiaSharp should be able to find the "Arial Black" font family.
Actual Behavior
SkiaSharp selects the default "Segoe UI" font family.
Basic Information

Version with issue:  1.60.3
IDE:  Visual Studio
Platform Target Frameworks:

Windows Classic:  .NET Framework 4.7.2

Additional Information
While browsing the Fonts folder in Windows, I noticed that the only font that appears in the main list is "Arial":

But when you double-click on "Arial," it then displays "Arial Black" in that list:

Does that have something to do with why SkiaSharp can't find that font? But why can System.Drawing.FontFamily find the font, but SkiaSharp can't?

VS bug #735691

For anyone else experiencing the same problem, I realized that the SKFontStyleWeight enum has a Black value. I ended up having to detect if the incoming font family name is "Arial Black", and if so, I change the font family name to "Arial" and set the weight to SKFontStyleWeight.Black. That made the resulting font appear like it was set to Arial Black.
SKFontStyleWeight weight = fontFamilyName == "Arial Black" ? SKFontStyleWeight.Black : SKFontStyleWeight.Normal);
string skiaFontFamilyName = fontFamilyName == "Arial Black" ? "Arial" : fontFamilyName;
SKTypeface tf = SKTypeface.FromFamilyName(skiaFontFamilyName, weight, SKFontStyleWidth.Normal, SKFontStyleSlant.Upright);

The question still remains for me: why can't SkiaSharp handle "Arial Black" but System.Drawing.FontFamily can?

Have you tried specifying the font name as "Arial-Black"?

@neodynamic, I just tried your suggestion, but it still returned Segoe UI. Thanks for the idea.

This sounds very interesting... I will see what I can find out.
I asked on the forums and we can see what the developers say: https://groups.google.com/forum/#!topic/skia-discuss/56foxa1fCoQ

GDI+ handles font families differently it uses different families for styles like narrow or black. DirectWrite or other frameworks just have one FontFamily Arial and uses styles for all different combinations of narrow, black, etc. So skia`s behavior looks right to me. Brothing the font with the explorer just showed how the font family is organized correctly.

That really the issue here. TECHNICALLY skia is right. But, we are in the old world and it is unexpected. Google mentions that they have an extra layer over the font to read the prefix/suffix to read the weight and spacing: eg "Arial BLACK EXPANDED"

I ran into the same issue. My vote is to handle this in SkiaSharp so that the correct family and weight are chosen.

For future reference, you can solve this problem (on Windows) by combing SKFontManager.FontFamilies, SKFontManager.GetFontStyles, and reading the 'name' and 'STAT' tables via SKTypeface.TryGetTableData. An outline to build a font cache with names matching GDI+ would be:

Load all available fonts (SKFontManager.FontFamilies).
For each font, load all available styles (SKFontManager.GetFontStyles). This gives you all the necessary axis values to implement the "Regular/Bold/Italic/BoldItalic" font model.
For each font style combo read its 'name' and 'STAT' table and assign the name of that font style combo according to the STAT documentation. You only have to look at weight (eliding bold [700]) and width to match GDI+ naming.
Construct a cache keyed on the family name. Make the resolved font bold/italic via SKFontManager.MatchTypeface.


SvgXml Not Displaying Image but Shows Fine in Browser, etc

I am using react-native-svg version 12.1.1, and while SVGs for most images work fine, there is one image that is not displaying correctly and I cannot figure out why.
Here is the XML:
<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 90.88 90.88"><defs><style>.cls-1{fill:#571aff;}</style></defs><title>telos-logo</title><path class="cls-1" d="M45.53,90.88a47.65,47.65,0,0,1-18.94-3.59A42.36,42.36,0,0,1,3.19,63.06,48.54,48.54,0,0,1,0,45.44,48.55,48.55,0,0,1,3.19,27.81,42.36,42.36,0,0,1,26.59,3.59,47.65,47.65,0,0,1,45.53,0,47.65,47.65,0,0,1,64.47,3.59a43,43,0,0,1,14.3,9.77,41.94,41.94,0,0,1,9,14.45,49.87,49.87,0,0,1,3.1,17.62,49.86,49.86,0,0,1-3.1,17.62,41.91,41.91,0,0,1-9,14.45,43,43,0,0,1-14.3,9.77A47.65,47.65,0,0,1,45.53,90.88Z"/></svg>

It displays just fine in a browser, for example at the following link:
https://raw.githubusercontent.com/telosnetwork/images/master/chain_icons/telos-logo-circle.svg
So why is this library unable to display it correctly? I can only assume it has something to do with the  element, or something like that. Could you guys try to display it and see if it works for you?
Any help would be appreciated.

@kylanhurt could you share a code example of how you use react-native-svg?

I'm facing a similar issue with the following svg
<!-- Generator: Adobe Illustrator 24.2.1, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
	 viewBox="0 0 24 24" style="enable-background:new 0 0 24 24;" xml:space="preserve">
<style type="text/css">
	.st0{fill:#26A472;}
</style>
<path class="st0" d="M12,2c-1.4,0-2.5,1.1-2.5,2.5S10.6,7,12,7s2.5-1.1,2.5-2.5S13.4,2,12,2z M20.3,6.5c-0.4-1.1-1.5-1.7-2.6-1.3
	l-1.6,0.6c-0.2,0.1-0.3,0.2-0.4,0.4c-0.7,1.4-2.1,2.3-3.7,2.3c-1.6,0-3-1-3.7-2.3C8.2,6.1,8.1,5.9,7.9,5.9L6.3,5.3
	C5.2,4.9,4,5.4,3.7,6.5C3.3,7.5,3.8,8.6,4.8,9L8,10.3v3.1l-2,5.7c-0.4,1,0.2,2.1,1.2,2.5c1,0.4,2.1-0.2,2.5-1.2L11,17
	c0.2-2.8,2.3-5.2,5-5.8v-0.9L19.2,9C20.2,8.6,20.7,7.5,20.3,6.5z M23,17.5c0,3-2.5,5.5-5.5,5.5S12,20.5,12,17.5s2.5-5.5,5.5-5.5
	S23,14.5,23,17.5z M20.9,15.1c-0.2-0.2-0.5-0.2-0.7,0l-3.6,3.6l-1.6-1.6c-0.2-0.2-0.5-0.2-0.7,0c-0.2,0.2-0.2,0.5,0,0.7l2,2
	c0.2,0.2,0.5,0.2,0.7,0l4-4C21,15.7,21,15.3,20.9,15.1z"/>
</svg>

I think the problem is that this file style element included in this file

I also have this issue

Has this been solved or something?
I'm facing similar issues here. While most of the images work fine, others don't show up.
Checking the svg from both images... I've found out that the one which is displaying fine has the witdh and height properties in it. Whereas, the one which is not being displayed, haven't got those properties in them.
I believe that could be the reason why it's not showing up. However, I can't change width and height on the svgs, because I'm getting them from an api call.
Any clues on what we should do in this case? Hey kylanhurt, have you been abled to solve this issue?
Thank you

Hello @kylanhurt,
I checked your SVG on this platform. Our SVG library exhibited the same behavior.
As @ejrb mentioned, if you want to add style properties to your SVG, you can use the SvgCss component. If you encounter any issues, please feel free to open a new problem report.
Thank you.


Progress Reporting for Long Running Operations + Custom Commands

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

Please fix CI first.

@oakeyc please comment when we should take another look.

Codecov Report

Merging #3130 into master will increase coverage by 0.57%.
The diff coverage is 69.9%.

@@            Coverage Diff            @@
##           master   #3130      +/-   ##
=========================================
+ Coverage   70.43%     71%   +0.57%
=========================================
  Files         360     364       +4
  Lines       23759   24066     +307
  Branches     3640    3664      +24
=========================================
+ Hits        16734   17088     +354
+ Misses       5962    5893      -69
- Partials     1063    1085      +22

Impacted Files
Coverage Δ

...modules/azure-cli-shell/azclishell/az_completer.py
60.78% <100%> (+0.19%)
:arrow_up:

...torage/azure/cli/command_modules/storage/custom.py
81.89% <100%> (-0.31%)
:arrow_down:

...ules/azure-cli-shell/azclishell/gather_commands.py
37.71% <100%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/application.py
89.52% <100%> (+0.2%)
:arrow_up:

...and_modules/azure-cli-shell/azclishell/progress.py
27.86% <27.86%> (ø)

...nd_modules/azure-cli-shell/azclishell/argfinder.py
37.5% <42.85%> (+2.71%)
:arrow_up:

...mmand_modules/azure-cli-shell/azclishell/layout.py
44% <60%> (+0.84%)
:arrow_up:

...li-core/azure/cli/core/test_utils/vcr_test_base.py
69.08% <66.66%> (-0.1%)
:arrow_down:

...azure-cli-core/azure/cli/core/commands/__init__.py
84.43% <76.92%> (+0.25%)
:arrow_up:

...azure-cli-core/azure/cli/core/commands/progress.py
94.89% <94.89%> (ø)

... and 41 more

Continue to review full report at Codecov.

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

@troydai and @derekbekoe, can you please take another look

Reviewing.