Describe the bug
Image file path encoding failed, when the path contains double-underline pairs, e.g. ![[double__underline__pairs.jpg]].
BUG: filename is encoded into double**underline**pairs.jpg but NOT double__underline__pairs.jpg
Similar SOLVED bugs: #100.
Example usage of such naming convention: in AI, for hyper-params. Say, we train two K-means models named kmeans, one into k=5 cluster, and another into k=10 clusters. Then, for each model, we evaluate some metrics and acquire a plot. To save the two plots with param k distinguishable from filenames, a common practice is using such a naming convention, as kmeans__k=5.jpg and kmeans__k=10.jpg, for the model into 5 and that into 10 clusters, respectively.
Samples to Reproduce
Example Screenshot (config PORT is changed to 4399):
Expected behavior
The file path encoding should work correctly, as http://localhost:4399/double__underline__pairs.jpg, but NOT http://localhost:4399/double**underline**pairs.jpg (as is shown in the reproduction example).
marridG
commented
1 year ago
Describe the bug Image file path encoding failed, when the path contains double-underline pairs, e.g.
![[double__underline__pairs.jpg]].double**underline**pairs.jpgbut NOTdouble__underline__pairs.jpgkmeans, one intok=5cluster, and another intok=10clusters. Then, for each model, we evaluate some metrics and acquire a plot. To save the two plots with paramkdistinguishable from filenames, a common practice is using such a naming convention, askmeans__k=5.jpgandkmeans__k=10.jpg, for the model into 5 and that into 10 clusters, respectively.Samples to Reproduce
Example Screenshot (config
PORTis changed to4399):Expected behavior
The file path encoding should work correctly, as
http://localhost:4399/double__underline__pairs.jpg, but NOThttp://localhost:4399/double**underline**pairs.jpg(as is shown in the reproduction example).The image should also be rendered.