Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

checkInFromUrlAsync generates a bad filename inside the incoming folder #1006

Open
GiacomoManzoli opened this issue Jul 19, 2019 · 0 comments

Comments

@GiacomoManzoli
Copy link

commented Jul 19, 2019

BIMServer version / Environment
1.5.150 and 1.5.157 on macOS 10.14, started from .jar release.

Describe the bug
ServiceInterface.checkInFromUrlAsync generates the wrong file name.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the BIMServer Console application;
  2. Use the ServiceInterface to check in a new revision.

Expected behavior
The original file name was 2019-07-16-15-37-25-Villetta [AC21, QTY, 2X4].ifc so the expected file name should be 2019-07-19-15-07-13-933-2019-07-16-15-37-25-Villetta [AC21, QTY, 2X4].ifc (like it was with version 1.5.96) or something similiar (like with checkInFromFile).

Screenshots
Sample call (note that the spaces on the filename are escaped with %20):
Schermata 2019-07-19 alle 14 58 23

checkInFromUrl from BIMvie.ws (it gives a different result)

Schermata 2019-07-19 alle 14 59 03

Schermata 2019-07-19 alle 14 59 13

Result with checkInFromFile from BIMvie.ws (it changes the file name since it replaces all the whitespaces with "_")

Schermata 2019-07-19 alle 15 19 16

Additional context
.

Other
it's not critical, but the incoming folder is useful if you have to migrate the project from an installation to another (it's faster to use the original IFC rather then to export the one stored in the database)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.