I've recently started using CVS for personal projects and I'm running into a problem with exporting by a tag. I commit all changes, but only tag files for production (PRD) when ready. I use
cvs export -rPRD module_name
and this works well, except I realized that when I cvs remove filename and commit, it is still included in subsequent exports.
How do I stop the export from including removed files? Is there a different way, like somehow specifying a tag and a revision, that might do this correctly? I have tried cvs export -Dnow -rPRD module_name, but this always exports nothing.
Related
This is an unusual one.
I commited a git branch, merged it, then hit undo on the merge. If I roll back to the commit (that had just been working) I get the error:
Uncaught TypeError: Cannot read properties of undefined (reading 'includes')
at UniqueComponentName (UniqueComponentName.js:13:1)
Line 13 is the opening declaration of the functional component:
export const UniqueComponentName = ({ side, mode, menuJSON, pcbData, ...props }) => {
I thought, initially, it was a problem with an 'includes' in the component but trial and error led me to discover the following:
A brand new component named UniqueComponentName, made with a
template that works under any other name, still throws this error.
If I don't include the UniqueComponentName component in any other
component, the app performs fine.
As soon as I include it, the error above is thrown. Again, the
contents of UniqueComponentName are irrelevant as I can literally
copy and paste another working component and the error comes up.
I'm wondering if it's possible that the merge and undo merge corrupted some reference to UniqueComponentName? It's a long shot, I'm aware, but I'm there has been a lot of work since the last commit.
Further info:
If of relevance:
Reactjs is running off the standard create-react-app server locally.
I have been staging commits locally, and using a 3rd party build
pipeline to run builds on anything I push to github. The builds are hosted an a remote server that isn't involved here. As far as I
know, there's no production builds locally : I just hit save on any
file as I'm working on it and see webpack compiles, browser updates,
etc.
I'm considering starting up a fresh create-react-app project and bringing in all the /src files from the current project, to see if mt theory holds up.
The error is caused by create-react-app serving old bundle files.
Those files are located in the node_modules/.cache/ folder.
Solution;
Delete the node_modules/.cache/ folder
Restart your dev-server
React should now re-create all the bundle files, sourcemaps, etc..
- Old git issue with some in-depth details
I have a big problem that often confuses me.
From time to time, while importing code, the import does not work and the development environment does not find the files. I work at IntelliJ IDEA.
To find a file, I first export it:
export let Filename =
and I import in the file necessary for me, but when I register a file name, ide for me does not look and it is necessary to write independently. But when I write the path to a file manually, I get the error that there is no such file. What could be the problem?
Having issues running gatsby build with gatsby-starter-wordpress-advanced theme:
Error: ENOENT: no such file or directory, open 'C:\Users\Tobias\Desktop\Gatsby\gatsby-starter-wordpress-advanced\.template-cache\tmp-\.js'"
I figured this might be a problem with the path. The path should rather look like:
writing tmp-new-page/ template: open '.template-cache/tmp-new-page.js'
See repo: https://github.com/henrikwirth/gatsby-starter-wordpress-advanced/blob/master/create/utils.js
Line 53 you find the function createPageWithTemplate. I've tried console.log(page.uri) to see what's going on. It outputs the filename correctly. I've also tried with gatsby clean to clear the cache. It seems to be some kind of backslash issue where the path comes with a \ .js at the end instead of sample-page.js:
no such file or directory, open 'C:\Users\Tobias\Desktop\Gatsby\gatsby-starter-wordpress-advanced\.template-cache\sample-page\.js'
The issue have been resolved. The problem was related to update in WPGraphQL WordPress plugin. Had to update the paths, because the page.uri is different in the newer versions of WPGraphQL. Before it was just: some-page now it is /some-page/.
Secondly in the page template creation process the theme was using the uri, therefore, this messed up the paths for the template files. This has been switched to page.slug instead now and some extra checks, to make sure the frontPage is not ending up producing a wrong path.
The master branch of the starter theme have been updated.
While trying to solve another problem (inadvertently over-wrote /constants/index.js without realizing it), I re-named the constants directory constants2. After restoring index.js, I changed the directory name back to constants.
Now, when RN resolves the path to /constants/Layout.js, it's throwing
undefined is not an object (evaluating '_constants2/default.tabBarHeight')
Changing the name back to constants2 doesn't help.
I have followed all of the instructions for clearing caches (npm and yarn), including deleting the temp cache directory. I have searched the contents of the files in my project and in the cache directory for the string constants2 and nothing found. I have upgraded everything possible.
I'm at wit's end. Where could this old path be stored?? I renamed the directory within Atom and I'm wondering if that might be the source of the trouble. Platform is Windows 10.
Solved this, but I'm not sure why.
I changed this:
import Layout from '../constants';
import Colors from '../constants';
import Images from '../constants';
To this:
import { Colors, Images, Layout } from '../constants';
and the problem went away. Shouldn't either one have worked? And I still can't see why it was still referencing the former path.
I am new to Go and AppEngine. I am trying to figure out how to create packages but I keep running into conflicts. My directory structure is below:
GOPATH
third-party-libs
app
app.yaml
controllers
default.go -- package controllers
models
models.go -- package models
templates
templates.go -- package templates
I am importing the templates package as follows import ("app/templates") inside default.go
When I do goapp serve I get this error:
Failed parsing input: app file templates.go conflicts with
same file imported from GOPATH
I have tried a bunch of things and nothing has worked so far. These are things I have tried:
Changed the templates directory to apptemplates and the corresponding file to apptemplates.go, changed package name to apptemplates. I imported it as app/apptemplates
I tried different combinations by changing the file name but not the package name, vice versa, etc. Either it does not find the file or has a conflict.
I am importing html/template in my templates.go file. So I commented out the entire file just keeping the package declaration but did not make the conflict go away
I thought may be another file is named templates.go but when I do this (at the GOPATH level) find . -name "*.go" | grep "templates.go" I only see the one file I have created.
I am confused as to how packages are created. I have changed the name to something generic so it does not look like a naming issue. Can someone please tell me how I can debug this error?
Thanks!
Rename the package to a non-conflicting name as in #1. Import the package using the path "apptemplates".
Packages inside of the application directory (the directory containing app.yaml) are imported with a path relative to the application directory. See Organizing Go Apps for the complete details.