Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Profile picture
LackadaisicalOtter14
Moderator
1 Question, 4 Answers
  Active since 10 January 2023
  Last activity one year ago

Reputation

0

Badges 1

4 × Eureka!
0 Votes
10 Answers
923 Views
0 Votes 10 Answers 923 Views
I originally posted in but have reposted here upon request! 😸 Hey guys! We are trialling the ClearML session as a workflow for team to train their models. I...
2 years ago
0 I Originally Posted In

Hey,

Do not worry about the SSH problem I mentioned, I understand now, thank you!

Regarding the ldconfig warning supression, I tested it and it works as expected!
I have made a PR request.

Thanks for your help AgitatedDove14 😊

2 years ago
0 I Originally Posted In

Hey,
Sorry for delay in replying.
The line causing problems is line 484 in the interactive_session_task
'echo "ldconfig" >> /etc/profile && '
When a user logs in, due to a custom cuda/torch version being used, when a user logs in; they are greeted with
` /sbin/ldconfig.real: File /lib/x86_64-linux-gnu/libnvidia-cfg.so.470.63.01 is empty, not checked.
/sbin/ldconfig.real: File /lib/x86_64-linux-gnu/libnvidia-compiler.so.470.63.01 is empty, not checked.
/sbin/ldconfig.real: ...

2 years ago
0 I Originally Posted In

Hey thanks informing me of this.
However, this doesn't help need to remove ldconfig from /etc/profile which is put there by the interactive_session_task 😕

2 years ago
0 I Originally Posted In

That would be great! Might have to use  2>/dev/null  in some of my bash scripts  😊

One other question regarding connecting. We have setup sshd inside the docker image we are using. I see that when we try to connect over port 22, it forwards to the host machine. I believe this is due to mounting ports on the host; which is possible as the spun up container has the capabilities:
'--cap-add=net_admin', '--cap-add=sys_module

Is there a way to disable this behaviour, and let the...

2 years ago