-
Notifications
You must be signed in to change notification settings - Fork 1.2k
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
compress_path() doesn't normalize some paths correctly #1041
Comments
Here's an example from a cluster: [zeek@bro-east1 site]$ ls conn-bulk.zeek |
@dopheide-esnet I just added 560ee0c, do you want to see if that fixes your issue? |
Yeah, initial test looks great. |
* origin/topic/timw/1041-compress-path: GH-1041: Move compress_path to a bif that uses normalize_path
…-changes * origin/master: (47 commits) scan.l: Remove "constant" did_module_restore logic Fix FreeBSD CI script to install right SWIG package Update submodule(s) GH-928: use realpath() instead of inode to de-duplicate scripts Update submodule(s) GH-1040: Add zero-indexed version of str_split Fix WhileStmt to call Stmt(Tag) ctor GH-1041: Move compress_path to a bif that uses normalize_path Update submodule(s) Update submodule(s) Update submodule(s) Fix --enable-mobile-ipv6 build Fix namespace of GetCurrentLocation() to zeek::detail Add backtrace() and print_backtrace() Rename BroString files to ZeekString Update NEWS entry with note about class renames Rename BroObj to Obj Rename BroString to zeek::String Move Func up to zeek namespace, rename BroFunc to ScriptFunc Mark global val_mgr as deprecated and fix uses of it to use namespaced version ...
Probably related to what @dopheide-esnet reported on Slack:
Yields the wrong results:
We already have path normalization implemented in C++ here:
zeek/src/util.cc
Line 1603 in a5a51de
And think it works correctly in this case, so would suggest not bothering to fix the script-layer version of
compress_path()
: just change it to a BIF callingnormalize_path()
.The text was updated successfully, but these errors were encountered: