fpoli  
                
               
                 
              
                  
                    October 23, 2020,  1:44pm
                   
                   
              1 
               
             
            
              The following Codecov page shows a “GitHub API: Forbidden” error message
GitHub API: Forbidden
**Is the path  `prusti-viper/src/encoder/procedure_encoder.rs`  a relative path in your repository?**
[Learn how to apply path fixes in your configuration](https://docs.codecov.io/docs/fixing-paths).
Please [contact support](https://codecov.io/support) for questions."
 
However, that file exists (same commit hash) and is public:
  
  
    
      // © 2019, ETH Zurich
//
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at http://mozilla.org/MPL/2.0/.
use crate::encoder::borrows::ProcedureContract;
use crate::encoder::builtin_encoder::BuiltinMethodKind;
use crate::encoder::errors::PanicCause;
use crate::encoder::errors::{EncodingError, ErrorCtxt};
use crate::encoder::foldunfold;
use crate::encoder::initialisation::InitInfo;
use crate::encoder::loop_encoder::{LoopEncoder, LoopEncoderError};
use crate::encoder::mir_encoder::{MirEncoder, FakeMirEncoder, PlaceEncoder};
use crate::encoder::mir_encoder::{POSTCONDITION_LABEL, PRECONDITION_LABEL};
use crate::encoder::mir_successor::MirSuccessor;
use crate::encoder::optimizer;
use crate::encoder::places::{Local, LocalVariableManager, Place};
use crate::encoder::Encoder;
use crate::encoder::snapshot_spec_patcher::SnapshotSpecPatcher;
 
  This file has been truncated. show original 
   
  
    
    
  
  
 
             
            
               
               
               
            
            
           
          
            
              
                tom  
                
               
              
                  
                    October 26, 2020,  2:48pm
                   
                   
              2 
               
             
            
              @fpoli , this should be resolved, are you still seeing the issue?
             
            
               
               
               
            
            
           
          
            
              
                fpoli  
                
               
              
                  
                    October 26, 2020,  3:11pm
                   
                   
              3 
               
             
            
              Yes, I still see the error if I open the link mentioned in my first message. (I even tried a different browser.)
             
            
               
               
               
            
            
           
          
            
              
                tom  
                
               
              
                  
                    October 26, 2020,  3:12pm
                   
                   
              4 
               
             
            
              @fpoli , this is typically a permissions issue. Could you try deleting your cookies and logging back in?
             
            
               
               
               
            
            
           
          
            
              
                fpoli  
                
               
              
                  
                    October 26, 2020,  3:14pm
                   
                   
              5 
               
             
            
              I tried again (without deleting cookies or logging out) and the error disappeared 
             
            
               
               
              1 Like