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
Answered
Hi, I Have A Question Regarding Trains And Git. If I Make Changes To A File And Run It Using Trains (Without Pushing The Changes To Github), What Version Of The Script Is Running? It Seems That Every Change I Make Need To Be Added, Committed And Pushed Be

Hi, I have a question regarding trains and git. If I make changes to a file and run it using trains (without pushing the changes to GitHub), what version of the script is running? It seems that every change I make need to be added, committed and pushed before running, otherwise the changes are ignored.

  
  
Posted 4 years ago
Votes Newest

Answers 14


I guess. maybe I'll just stash.
Not a big fan of notebooks X git so I attempt to push these less frequently.

  
  
Posted 4 years ago

Can you get rid of some of these large changes, or are they inherent to your solution?

  
  
Posted 4 years ago

SuccessfulKoala55 when running a changed script without adding committing and pushing the changes are not applied. I do have '# WARNING! git diff too large to store, clear this section to execute without it.' due to unsaved notebook changes.
I guess that's the issue?

  
  
Posted 4 years ago

I think you are talking about separate problems - the "WARNING DIFF IS TOO LARGE" is only a UI issue, that you can't see hte diff in the UI - correct me if I'm wrong with this

Maria seems to be saying that the execution FAILS when she has uncomitted changes, which is not the expected behavior - am I right maria?

  
  
Posted 4 years ago

The execution uses an older version that is committed.

  
  
Posted 4 years ago

Yup 🙂

  
  
Posted 4 years ago

Do you have any idea as to why does that happen SuccessfulKoala55

  
  
Posted 4 years ago

(I'm working with maria)

essentially, what maria says is when she has a script with uncomitted changes, when executing remotely, the script that actually runs on the remote machine is without the uncomitted changes

e.g.:
Her git status is clean, she makes some changes to script.py and executes it remotely. What gets executed remotely is the original script.py and not the modified version she has locally

  
  
Posted 4 years ago

Hi GleamingGiraffe20 ,
When you run an experiment with uncommitted changes using Trains, Trains will store the uncommitted changes as part of the experiment details (as well as the git repository and commit these changes are based on, of course).
When you clone this experiment and run it using Trains Agent, the agent will pull the required Git repository in the specified commit, and apply the uncommitted changes.
How did you run the experiment for the second time?

  
  
Posted 4 years ago

If it's just a UI issue, than this is still unsolved.

  
  
Posted 4 years ago

WackyRabbit7 you were not entirely correct - the message WARNING! git diff too large to store is actually placed there by Trains SDK instead of the actual diff since the diff is too large and is not sent to the server (which is what I thought initially)

  
  
Posted 4 years ago

Oh, sorry! it's actually very simple

  
  
Posted 4 years ago

Oh I get it, I thought it is only a UI issue... but it actually doesn't send it O_O

  
  
Posted 4 years ago

The limit is 500000 bytes

  
  
Posted 4 years ago
940 Views
14 Answers
4 years ago
one year ago
Tags