These are chat archives for highfidelity/hifi

26th
Jun 2017
Sachin Mahapure
@sachinmahapure
Jun 26 2017 15:47

The URL (https://hifi-content.s3.amazonaws.com/liv/dev/demo/demo.js ) mentioned in the ticket (https://worklist.net/21399) is showing below content:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>liv/dev/demo/demo.js</Key>
<RequestId>5B6C82C7DEDC1E03</RequestId>
<HostId>
L+UjOaptdwv9XxZiIsEJvYlW3TPE91z2SdxSRIPtglvgkDOigAi/lrlCLw33IYOfID0jn8MU8xI=
</HostId>
</Error>

If we are running the script from given URL using MENU/EDIT/Running Scripts… of tablet UI, it shows “https://hifi-content.s3.amazonaws.com/liv/dev/demo/demo.js failed to load.”

Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:03
I'm getting the following error when I use cmake to build the project files: CMake Error at C:/Program Files/CMake/share/cmake-3.8/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find GLM (missing: GLM_INCLUDE_DIRS)
Melissa Brown
@themelissabrown
Jun 26 2017 20:10
Hi Jeffrey are you on the windows build?
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:17
yes
The clone I downloaded over the weekend had no troubles building project files and compiling but when I setup today with 21402 branch, I got this error.
I work for RickDaniels, so it's through his github repo
Clément Brisset
@Atlante45
Jun 26 2017 20:26
Hi @JeffHiebert_GP_twitter,
Could you clean your build directory and sent me the full output of your cmake command?
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:28

C:\HighFidelity\build>cmake .. -G "Visual Studio 12 Win64"
-- The C compiler identification is MSVC 18.0.40629.0
-- The CXX compiler identification is MSVC 18.0.40629.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at C:/Program Files/CMake/share/cmake-3.8/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find GLM (missing: GLM_INCLUDE_DIRS)
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.8/Modules/FindPackageHandleStandardArgs.cmake:377 (_FPHSA_FAILURE_MESSAGE)
cmake/modules/FindGLM.cmake:24 (find_package_handle_standard_args)
cmake/macros/IncludeGLM.cmake:12 (find_package)
assignment-client/CMakeLists.txt:22 (include_glm)

-- Configuring incomplete, errors occurred!
See also "C:/HighFidelity/build/CMakeFiles/CMakeOutput.log".

Clément Brisset
@Atlante45
Jun 26 2017 20:39
What's your cmake version?
We've been know to have issues with CMake 3.9.
If that is the version you are using, I'd suggest trying with cmake 3.8.
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:44
I installed 3.8 from the link on the high fidelity build page
Clément Brisset
@Atlante45
Jun 26 2017 20:47
Ok, can you send me this file: C:/HighFidelity/build/CMakeFiles/CMakeOutput.log or paste the content here?
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:47
Clément Brisset
@Atlante45
Jun 26 2017 20:50
Hmmm, nothing helpful in there unfortunately.
Do you see anything inside ext/vc12/glm/project/. This should be inside your build folder.
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:58
I don't see an ext dir in C:/HighFidelity/
Clément Brisset
@Atlante45
Jun 26 2017 20:59
Should be in C:/HighFidelity/build judging from your cmake command.
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 20:59
Not there either
Clément Brisset
@Atlante45
Jun 26 2017 21:00
That very odd.
Just as a sanity check, could you try to build the official repo's master branch?
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:07
I'm a git novice, what's the command for that? or should I just clone https://github.com/highfidelity/hifi.git to another directory?
Clément Brisset
@Atlante45
Jun 26 2017 21:07
Do you have any changes you care about on that branch?
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:08
no changes
Clément Brisset
@Atlante45
Jun 26 2017 21:09
git remote add upstream https://github.com/highfidelity/hifi.git
git fetch upstream
git reset --hard upstream master
I didn't run those commands, hopefully I got them right first try, let me know.
git diff upstream/master should show no changes.
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:11
C:\HighFidelity>git reset --hard upstream master
fatal: ambiguous argument 'upstream': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Clément Brisset
@Atlante45
Jun 26 2017 21:12
Arf, it's a slash instead of a space. My bad.
git reset --hard upstream/master
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:15
cmake worked no problem
so, is something wrong with the 21402 branch?
Clément Brisset
@Atlante45
Jun 26 2017 21:17

Ok, there must be an issue with the code you were working of. I'd suggest RickDaniels update his master branch by pulling from our repo.
Simply do this once to add the URL of the upstream repo:

git remote add upstream https://github.com/highfidelity/hifi.git

Then do:

git checkout master
git pull upstream master
git push

Anytime you want to update from upstream.

Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:19
Ok. I'll give that a shot.
Clément Brisset
@Atlante45
Jun 26 2017 21:19
I just went to RickDaniels' repo to checkout what could be wrong with branch 21402, but I couldn't find such a branch on Github.
Jeffrey Hiebert
@JeffHiebert_GP_twitter
Jun 26 2017 21:22

I was given an email with info from themelissabrown that had the following: New branch 21402 created for repo git://github.com/rickdaniels/hifi.git on your GitHub account
We have created a new branch 21402 on your git://github.com/rickdaniels/hifi.git repo in your GitHub account.

Please refer to the following basic commands to work with your new branch:

Locally clone your fork: git clone git://github.com/rickdaniels/hifi.git
From your cloned copy, set the master repo as upstream: git remote add upstream git://github.com/highfidelity/hifi.git
Make sure you're using the latest code: git pull upstream master
Checkout the correct branch: git checkout 21402

that's as much as I know
Clément Brisset
@Atlante45
Jun 26 2017 21:41
Oh wow, how unlucky.
Here is what happened.
Those instructions are wrong or the service that is supposed to create that branch for you is broken.
If the branch had been created correctly, that would have been fine.
If you were meant to create the branch yourself, the correct command was git checkout -b 21402
So in the absence of a branch, it looked for a commit.
And as it turns out, there is a commit that has a short hash matching that worklist jobs' number.
So instead of creating a new branch based of the current master, you checked out that commit.
The only issue is that that commit is dated from July 2014:
commit 21402e3ff1e539244cf877e093f01121e20bdbca
Author: wangyix <wangyix@gmail.com>
Date:   Thu Jul 24 14:50:13 2014 -0700

    cleaned up some stuff
Melissa Brown
@themelissabrown
Jun 26 2017 21:42
@Atlante45 that's a worklist auto generated message
Clément Brisset
@Atlante45
Jun 26 2017 21:43
@themelissabrown Do you know if Worklist still auto generate the branch the contractors are supposed to work on?
Melissa Brown
@themelissabrown
Jun 26 2017 21:43
it does
but every once in a while, WL has issues. I suspect server load. I should have guessed that was the problem in the first place
Clément Brisset
@Atlante45
Jun 26 2017 21:46
Ok
@JeffHiebert_GP_twitter to fix this, here is what you should do:
git checkout -b 21402
git fetch upstream
git reset --hard upstream/master
git push -u origin 21402
this will create a clean branch named 21402 to work of of and push it to the github repo.