@markbates @bketelsen @bscott this is where i am on the flash helper, i'll continue tomorrow with the iterator implementation, look forward for your feedback.

This is my first attempt at supporting named routes as well as route helper functions available on the view, for more context please look into #210.

cc @markbates

Description

When executing "buffalo test" with a configured cockroachDB v2.0.6 the data will not get truncated after each test. The Buffalo Auth Plugin generates multiple tests to be sure the user object is not already saved in the database before testing some logic. If I execute one test it will pass, with executing the test suite most will fail. If I run the same tests on a cockroachDB v1.1.9 everything works all fine.

Steps to Reproduce the Problem

Please describe in painful detail what you did (so others can play along with you) to get to this point. This includes things like the exact command(s) you used, or the curl command you used, that sort of thing.

1. Create a new project with "buffalo new coke --db-type cockroach"
2. Make sure the Cockroach DB is running.
3. Generate authentication with the buffalo auth plugin
4. Create databases with "buffalo db create -a"
5. Run tests("buffalo test"), some of them will fail because they expect the database to be empty.
6. Configure a postgre database with "buffalo db g config"
7. Create databases with "buffalo db create -a"
8. Run tests("buffalo test"), the tests pass all

Expected Behavior

After each test the cockroach database should truncate the created rows.

Actual Behavior

After each test the cockroach database keeps the data.

Info

### Buffalo Version
v0.13.2

### App Information
Pwd=/Users/dorus/go/src/github.com/edudorus/asom
Root=/Users/dorus/go/src/github.com/edudorus/asom
GoPath=/Users/dorus/go
Name=asom
Bin=bin/asom
PackagePkg=github.com/edudorus/asom
ActionsPkg=github.com/edudorus/asom/actions
ModelsPkg=github.com/edudorus/asom/models
GriftsPkg=github.com/edudorus/asom/grifts
VCS=git
WithPop=true
WithSQLite=false
WithDep=false
WithWebpack=true
WithYarn=false
WithDocker=true
WithGrifts=true
WithModules=false

### Go Version
go version go1.11.1 darwin/amd64

### Go Env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/dorus/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/dorus/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.11.1/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.11.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_5/7c3lr50s2wzgmw_y31t1r6400000gn/T/go-build684181983=/tmp/go-build -gno-record-gcc-switches -fno-common"

### Node Version
v11.0.0

### NPM Version
6.4.1

### Yarn Version
Yarn Not Found

### PostgreSQL Version
pg_ctl (PostgreSQL) 10.5

### MySQL Version
mysql  Ver 8.0.12 for osx10.14 on x86_64 (Homebrew)

### SQLite Version
3.24.0 2018-06-04 14:10:15 95fbac39baaab1c3a84fdfc82ccb7f42398b2e92f18a2a57bce1d4a713cbaapl

### Dep Version
could not find a Gopkg.toml file

### Dep Status
could not find a Gopkg.toml file

### go.mod
module github.com/edudorus/asom

Problem:

When executing command to start local buffalo dev server, get an error when expecting normal start.

Output:

$ buffalo dev

Buffalo version 0.7.1

There was a problem starting the dev server: Unknown

Details: Go Version: 1.7.4 Buffalo Version: 0.7.1 MacOS: Sierra ( 10.12.1 )

I am getting error below while running buffalo dev and buffalo generate on a fresh buffalo new project.

Error: you need to be inside your buffalo project path to run this command

Buffalo Version

v0.9.4

Go Version

go version go1.9 linux/amd64

package actions import "github.com/gobuffalo/packr" // GENERATE FILE // Do NOT hand edit this file // It is recommended that you do not check into this file into SCM. // We STRONGLY recommend you delete this file after you have built your // Go binary. You can use the "packr clean" command to clean up this, // and any other packr generated files. func init() { packr.PackJSONBytes("../templates", "D:\Go\GOPATH\src\oschina.net\lanybass\erciyibiao\templates_flash.html", ""..."") packr.PackJSONBytes("../templates", "D:\Go\GOPATH\src\oschina.net\lanybass\erciyibiao\templates\application.html", ""..."") packr.PackJSONBytes("../templates", "D:\Go\GOPATH\src\oschina.net\lanybass\erciyibiao\templates\index.html", ""..."") }

the slashes in D:\ should be replaced with \ or /

I am writing this issue to track/manage a set of PRs of module updating (mainly for security bugfix) for gobuffalo families.

Related PRs

• https://github.com/gobuffalo/github_flavored_markdown/pull/5
• https://github.com/gobuffalo/tags/pull/138
• https://github.com/gobuffalo/helpers/pull/19
• https://github.com/gobuffalo/plush/pull/147

Next

• buffalo and pop
• genny, fizz, buffalo-pop, cli will be checked if they need to be updated.

Hi. I made this PR as a proposal for the auto generated resources test.

This work was based on Toodo, and I try to validate the common types when generating a resources, because the Type from Prop Struct doesn't return if is nulls or not, I added a new one called "OriginalType" for validation on the template.

Hello,

I'm getting panic in Debug logger when a simple worker completes the job

level=debug time="2022-04-17T22:20:12Z" msg="completed job %!s(PANIC=String method: runtime error: invalid memory address or nil pointer dereference)

That's the culprit and this code panics too

Hello, I am trying to build by project with golang ~1.16beta1~ 1.16.0 (using the alpine based docker image) and I get the following error:

buffalo build -v
DEBU[2021-01-05T07:39:43Z] Step: e1807c46
DEBU[2021-01-05T07:39:43Z] Chdir: /test/xxx
DEBU[2021-01-05T07:39:43Z] File: /test/xxx/main.go
DEBU[2021-01-05T07:39:43Z] File: /test/xxx/a/aa.go
DEBU[2021-01-05T07:39:43Z] File: /test/xxx/buffalo_build_main.go
DEBU[2021-01-05T07:39:43Z] File: /test/xxx/migrations/.pop-tmp.md
DEBU[2021-01-05T07:39:43Z] Exec: go build -v -tags development -o bin/xxx
go: updates to go.mod needed; try 'go mod tidy' first
DEBU[2021-01-05T07:39:43Z] Rollback: main.go
DEBU[2021-01-05T07:39:43Z] File: /test/xxx/main.go
DEBU[2021-01-05T07:39:43Z] Delete: a/aa.go
DEBU[2021-01-05T07:39:43Z] Delete: buffalo_build_main.go
DEBU[2021-01-05T07:39:43Z] Delete: migrations/.pop-tmp.md
DEBU[2021-01-05T07:39:43Z] Exec: go mod tidy
Usage:
  buffalo build [flags]

Aliases:
  build, b, bill, install

Flags:
      --clean-assets               will delete public/assets before calling webpack
      --dry-run                    runs the build 'dry'
      --environment string         set the environment for the binary (default "development")
  -e, --extract-assets             extract the assets and put them in a distinct archive
  -h, --help                       help for build
      --ldflags string             set any ldflags to be passed to the go build
      --mod string                 -mod flag for go build
  -o, --output string              set the name of the binary
  -k, --skip-assets                skip running webpack and building assets
      --skip-build-deps            skip building dependencies
      --skip-template-validation   skip validating templates
  -s, --static                     build a static binary using  --ldflags '-linkmode external -extldflags "-static"'
  -t, --tags string                compile with specific build tags
  -v, --verbose                    print debugging information

ERRO[0000] Error: exit status 1

A strange thing is that echoing $? returns 255, not 1

Running go mod tidy does not solve the issue. Running buffalo dev works fine The project builds fine with golang 1.15.5 and the same buffalo versio (0.16.18)

What can I check to provide more useful infos/solve this ?

test repo: https://github.com/giulianozor/buffalotest

thanks

Update: running go get -u, buffalo fix buffalo update does not fix the issue Update 2: if I run buffalo build --dry-run it seems to complete without error, but obviously no binary is produced

Hi there,

Thanks for your work, at first :) I ran into problems just executing the following command: $ buffalo create db -a OR

$ buffalo db drop -a

I have the following database.yml:

development:
  dialect: postgres
  database: myAppdb
  user: user
  password: password
  host: 127.0.0.1
  pool: 5

test:
  url: {{envOr "TEST_DATABASE_URL" "postgres://user:[email protected]:5432/myApp_test?sslmode=disable"}}

production:
  url: {{envOr "DATABASE_URL" "postgres://user:[email protected]:5432/myApp_production?sslmode=disable"}}

I get:

$ buffalo db drop -a
v3.41.3

couldn't drop database myApp_test: error dropping PostgreSQL database myApp_test: pq: authentification par mot de passe échouée pour l'utilisateur  « user »
couldn't drop database myApp_production: error dropping PostgreSQL database myApp_production: pq: authentification par mot de passe échouée pour l'utilisateur  « user »
couldn't drop database myAppdb: error dropping PostgreSQL database myAppdb: pq: la base de données « user » n'existe pas

Meaning: buffalo seems to understand postgres://user:password as postgres://DATABASEr:password !

Any help, please ?

What is being done in this PR?

This PR adds a check during decoding which will return nulls.Time as a NULL value (i.e. its value for Valid will be false). Without this check, the value of nulls.Time{} will be:

{
  Time: 0001-01-01 00:00:00 +0000 UTC,
  Valid: true,
}

This ends up storing the value 0001-01-01 00:00:00 +0000 UTC in the database, as opposed to a NULL value.

What are the main choices made to get to this solution?

One option was to make the model Bindable and write a custom Bind() method which could handle empty values, but the default Bind handler does so much that bypassing it seemed extreme.

What was discovered while working on it? (Optional)

Type in here a description of the discoveries made while working on this PR.

List the manual test cases you've covered before sending this PR:

Fizz (using Postgres):

create_table("people") {
	t.Column("id", "uuid", {primary: true})
	t.Column("name", "string", {"size": 128})
	t.Column("birthday", "date", {"null": true})
	t.Timestamps()
}

Model:

type Person struct {
	ID uuid.UUID `json:"id" db:"id"`
	Name  string `json:"name" db:"name"`
	Birthday nulls.Time `json:"birthday" db:"birthday"`
	CreatedAt time.Time `json:"created_at" db:"created_at"`
	UpdatedAt time.Time `json:"updated_at" db:"updated_at"`
}

Plush form:

<%= f.InputTag("Birthday", {"type":"date"}) %>

What is being done in this PR?

This PR fixes issue #1904. And fix the bug caused by one of the previous pr that trace will only appear on development but not test environment.

What are the main choices made to get to this solution?

Without traces it's much harder to debug. The doc is also misleading that we will get a trace but in fact we didn't. This PR fix that issue.

https://gobuffalo.io/documentation/request_handling/errors/#default-error-handling-development

List the manual test cases you've covered before sending this PR:

The tests are covered in unit tests.

On dev, test: when handler return error being (pkg/errors or context.Error()) if it contains stack trace then it should return that stack trace. On other env, trace is hidden.

Description

Currently MIME support is through mail/internal/mail/message.go, an internal package. So if I wanted to create my own Sender/BatchSender implementation with MIME support, I would need to duplicate code. Options I see:

• Add a function to mail.Message to convert it to []byte with MIME data
• Add a function to mail package that takes in a mail.Message and converts it to []byte with MIME data

Thanks!

Additional Information

No response

Description

Description

Buffalo version is: v0.18.12

I want the buffalo server as a backend of nginx, and follow the instruction from #2022 , adding a Options.Prefix: '/prefix', then all request returns 404 no matter a '/prefix' is prepended in the request or not.

I found this useful guideline to configure with the nginx https://gobuffalo.io/documentation/deploy/proxy/ , but the rule inside my organization requires a prefix route config.

Expected Behavior

Expected to configure a reverse proxy route with prefix .

Actual Behavior

web requests are broken after the prefix is configured. API requests should append a '/' char at the end of the path.

To Reproduce

1. Add a prefix in actions/App.go

func App() *buffalo.App {
	appOnce.Do(func() {
		app = buffalo.New(buffalo.Options{
			Env:         ENV,
			SessionName: "_tmon_session",
			Prefix:      "/prefix/",
		})
}

2. run buffalo routes to verify:

before adding prefix:

  % buffalo routes
METHOD | HOST                  | PATH                    | ALIASES | NAME                   | HANDLER
------ | ----                  | ----                    | ------- | ----                   | -------
GET    | http://127.0.0.1:3000 | /                       |         | rootPath               | proj/actions.HomeHandler
POST   | http://127.0.0.1:3000 | /api/v1/user/users/     |         | apiV1UserUsersPath     | proj/actions/user.CreateUserHandler

after adding the prefix:

% buffalo routes
METHOD | HOST                  | PATH                           | ALIASES | NAME                         | HANDLER
------ | ----                  | ----                           | ------- | ----                         | -------
GET    | http://127.0.0.1:3000 | /prefix/                       |         | prefixPath                   | proj/actions.HomeHandler
POST   | http://127.0.0.1:3000 | /prefix/api/v1/user/users/     |         | prefixAPIV1UserUsersPath     | proj/actions/user.CreateUserHandler

4. check the welcome page, the returned links do not contain the '/prefix':

% curl -L  http://127.0.0.1:3000/prefix
<pre>
<a href="assets/">assets/</a>
<a href="robots.txt">robots.txt</a>
</pre>

# but http://127.0.0.1:3000/prefix/ , with an ending '/' , returns 404.

3. http://127.0.0.1:3000/prefix/assets/ redirected with 301 code to http://127.0.0.1:3000/prefix/assets/assests then 404 code.

4. http://127.0.0.1:3000/prefix/robots.txt works.

5. The API works only postpended with '/'.

This causes a 404 code :

curl -XPOST -L  http://127.0.0.1:3000/prefix/api/v1/user/users

this works :

curl -XPOST -L  http://127.0.0.1:3000/prefix/api/v1/user/users/

Additional Context

Details

Paste the output of `buffalo info` here!

Description

How to set a popup window after executing remote:true

<a href="/xx" data-remote="true" onsuccess??>

Additional Information

No response

Description

Cron-style periodic workers are required by many applications. Less robust solutions can be concocted with PerformIn, which leaves room for a more explicit way to express job run periods.

Additional Information

I opened this Issue to reference https://github.com/gobuffalo/buffalo/pull/2308