profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/acelot/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

acelot/automapper 47

Declarative data mapper for PHP 7

acelot/resolver 11

Dependency auto resolver for PHP 7 and 8

acelot/kohana-email 4

Kohana 3.3 email module (using Swift mailer)

acelot/graphql-articles 3

Articles GraphQL Service

acelot/helpers 2

Useful, well documented and tested PHP functions for everyday use

acelot/search-schema 2

Declarative SQL query builder for PHP 7

acelot/middleware-dispatcher 1

PSR-15 compliant middleware dispatcher for PHP 7

acelot/assert 0

Declarative validator for PHP 7

acelot/bulletphp 0

A resource-oriented micro PHP framework

startedwhsv26/functional

started time in 23 days

issue commentdavidpdrsn/juniper-from-schema

Interface field resolving causes "Concrete type is not handled by instance resolvers on GraphQL union"

This issue is fixed in juniper by https://github.com/graphql-rust/juniper/commit/7597523720b24e9dda3a4e0c94067b852f02465c This commit was included in the release https://github.com/graphql-rust/juniper/compare/juniper-v0.15.7...master

acelot

comment created time in 23 days

issue openedGoogleContainerTools/skaffold

Cannot push images to local repository

Expected behavior

Skaffold should upload the newly built images to the local repository

Actual behavior

Skaffold builds the image successfully, but cannot load it due to an error:

could not push image "localhost:5000/xxx:mytag-g567e04fa9a-dirty": An image does not exist locally with the tag: localhost:5000/xxx:mytag-g567e04fa9a-dirty

Information

  • Skaffold version: v1.30.0
  • Operating system: Arch Linux 5.13.12-arch1-1 #1 SMP PREEMPT Wed, 18 Aug 2021 20:49:03 +0000 x86_64 GNU/Linux
  • Installed via: Downloaded from the official site
  • Contents of skaffold.yaml:
apiVersion: skaffold/v2beta7
kind: Config
build:
deploy:

.sync_folders: &sync_folders
  - src: app/**
    dest: /app

- name: dev-local
  build:
    artifacts:
      - image: xxx/xxx
        context: ../.
        sync:
          manual: *sync_folders
        docker:
          dockerfile: Dockerfile
    local:
      push: true
  deploy:
    helm:
      releases:
        - name: xxx-service
          chartPath: yyy/yyy
          upgradeOnChange: true
          version: ~3.0.1
          remote: true
          namespace: xxx
          valuesFiles:
            - ./values.yaml
          artifactOverrides:
            image.fullname: xxx/xxx
          setValues:
            image.pullPolicy: IfNotPresent
          wait: true
      flags:
        install:
          - --atomic
          - --create-namespace
        upgrade:
          - --atomic

Steps to reproduce the behavior

I'm trying to use skaffold with podman and k3s.

  • To store the built images, I deployed a local repository via command:
podman run -d --name registry -p 5000:5000 -v $HOME/podman/library:/var/lib/registry --restart=always registry:2
  • Then I have added my local registry to the podman /etc/containers/registries.conf:
# # An array of host[:port] registries to try when pulling an unqualified image, in order.
unqualified-search-registries = ["localhost:5000", "docker.io", "registry.fedoraproject.org", "registry.access.redhat.com", "quay.io"]
  • Also I added my registry to the k3s mirrors /etc/rancher/k3s/registries.yaml and restarted k3s service:
mirrors:
  localhost:5000:
    endpoint:
      - "http://localhost:5000"
  • Made my registry the default registry for the skaffold in ~/.skaffold/config
global:
  default-repo: localhost:5000
  insecure-registries:
  - localhost:5000
  survey:
    last-prompted: "2021-08-23T14:30:04+07:00"
  collect-metrics: true
  update:
    last-prompted: "2021-08-25T22:38:14+07:00"
  • Now I'm trying to build my image and deploy to k3s:
→ skaffold dev -p dev-local

Listing files to watch...
 - xxx/xxx
Generating tags...
 - xxx/xxx -> localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty
Checking cache...
 - xxx/xxx: Not found. Building
Starting build...
Building [xxx/xxx]...
Sending build context to Docker daemon  434.6MB
STEP 1/20: <...many steps here...>
COMMIT localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty
Getting image source signatures
Copying blob sha256:814bff7343242acfd20a2c841e041dd57c50f0cf844d4abd2329f78b992197f4
<...many blobs here...>
Copying config sha256:2f7066935df60b7d95176f90582ffe1907be0c48df6bcaf0c45445f5eac8ac10
Writing manifest to image destination
Storing signatures
--> 2f7066935df
Successfully tagged localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty
2f7066935df60b7d95176f90582ffe1907be0c48df6bcaf0c45445f5eac8ac10
Successfully built 2f7066935df6
The push refers to repository [localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty]
Building [xxx/xxx]...
Canceled build for xxx/xxx
could not push image "localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty": An image does not exist locally with the tag: localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty

My comments

It's very strange that the error says that the image was not found locally, although the built image exists, if you check through the podman images:

→ podman images
REPOSITORY              TAG                      IMAGE ID      CREATED         SIZE
localhost:5000/xxx_xxx  mytag-g567e04fa9a-dirty  2f7066935df6  22 minutes ago  1.78 GB

And doubly strange that I can push the image manually:

→ podman push localhost:5000/xxx_xxx:mytag-g567e04fa9a-dirty --tls-verify=false
Getting image source signatures
Copying blob <...many blobs here...>
Copying blob 5753b2c5db63 done  
Copying config 2f7066935d done  
Writing manifest to image destination
Storing signatures

Additionally, I would like to say that my local repository is available from the k3s and images are successfully pulled from there.

created time in 23 days

issue commentdavidpdrsn/juniper-from-schema

Support reading schema from multiple files

Any news on this?

LucasPickering

comment created time in 2 months

issue commentbitnami/bitnami-docker-mysql

Newly introduced usage of lsof breaks container startup

I am experiencing this problem too.

OS:

→ uname -a
Linux homepc 5.13.5-arch1-1 #1 SMP PREEMPT Sun, 25 Jul 2021 18:02:58 +0000 x86_64 GNU/Linux

Docker:

→ docker version
Client:
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.16.4
 Git commit:        f0df35096d
 Built:             Fri Jun  4 08:14:39 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.4
  Git commit:       b0f5bc36fe
  Built:            Fri Jun  4 08:14:24 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.5.4
  GitCommit:        69107e47a62e1d690afa2b9b1d43f8ece3ff4483.m
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b638
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

I'm running my containers in local K8S cluster via kind.

→ kind version 
kind v0.11.1 go1.16.4 linux/amd64
kleini

comment created time in 2 months

issue commentgraphql-rust/juniper

Interface field resolving causes "Concrete type is not handled by instance resolvers on GraphQL union"

@tyranron Can't wait for the release to check out the fix :)

acelot

comment created time in 2 months

created tagacelot/resolver

tag2.4.0

Dependency auto resolver for PHP 7

created time in 2 months

release acelot/resolver

2.4.0

released time in 2 months

push eventacelot/resolver

acelot

commit sha da1cb96c8126306aac7df89db123451330bf358f

PHP 8 support

view details

Valeriy Protopopov

commit sha ddfedf134f57411cb8f20e03356edefb62d1498d

Merge pull request #2 from acelot/php-8-support PHP 8 support

view details

push time in 2 months

PR merged acelot/resolver

PHP 8 support
+91 -50

0 comment

11 changed files

acelot

pr closed time in 2 months

issue commentgraphql-rust/juniper

Interface field resolving causes "Concrete type is not handled by instance resolvers on GraphQL union"

@BeneSim agree with you. For me, the absence of this feature is a show stopper, because all my API is focused on interfaces.

acelot

comment created time in 2 months

PR opened acelot/resolver

PHP 8 support
+91 -50

0 comment

11 changed files

pr created time in 2 months

push eventacelot/resolver

acelot

commit sha da1cb96c8126306aac7df89db123451330bf358f

PHP 8 support

view details

push time in 2 months

create barnchacelot/resolver

branch : php-8-support

created branch time in 2 months

push eventacelot/resolver

Sergey Parfenov

commit sha b7e9f78e46c611557377aa29dba399c1f6f7aa18

Add php8 support: replaced deprecated function

view details

Valeriy Protopopov

commit sha e6985874aeee7d8cf38964aa8ab250e0ed97983f

Merge pull request #1 from sparfenov/master Add php8 support: replaced deprecated function

view details

push time in 2 months

PR merged acelot/resolver

Add php8 support: replaced deprecated function

Fixed warning on php8: Deprecated: Method ReflectionParameter::getClass() is deprecated in /app/vendor/acelot/resolver/src/Definition/Traits/ArgumentsTrait.php on line 112

+6 -6

0 comment

2 changed files

sparfenov

pr closed time in 2 months

PublicEvent

issue comment99designs/gqlgen

Cannot understand how to split schema.graphql

Yes, it is possible to split the schema. Just place notes query into separate file:

schema.graphql

scalar Time

type Query

type Mutation

notes.graphql

extend type Query {
    notes: [Note!]!
    noteById(id: ID!): Note
}

extend type Mutation {
    createNote(input: CreateNotePayload!): Note!
    updateNote(id: ID!, input: UpdateNotePayload!): Note!
    deleteNote(id: ID!): DeleteNoteResponse
}
maxifom

comment created time in 3 months

startednodkz/conf-talks

started time in 3 months

issue comment99designs/gqlgen

Define field complexity via directive

I read the documentation and realized that the gqlgen already provides a very convenient interface for setting the complexity via schemaConfig.Complexity.*. But we can go further and make this feature even more convenient by letting the gqlgen generate files with complexity functions and prompt the user for complexity on demand.

As a variant we can add a field to @goModel directive:

directive @goField(
    forceResolver: Boolean
    forceComplexity: Boolean
    name: String
) on INPUT_FIELD_DEFINITION | FIELD_DEFINITION

So we can use this to mark a field, that the field have custom complexity function:

type Query {
  findSomething(filter: Filter!) {
    someField
  } @goModel(forceResolver: true, forceComplexity: true)
}

The generator, in turn, will generate the corresponding functions:

// Field resolver
func (r *queryResolver) FindSomething(ctx context.Context, obj *model.Query, filter *model.Filter) (model.SomethingList, error) {
	panic("Not implemented")
}

// Field complexity function
func QueryFindSomethingComplexity(childComplexity int, filter *model.Filter) int {
	panic("Not implemented")
}

And automatically bind this function to complexity resolver in generated runtime:

func (e *executableSchema) Complexity(typeName, field string, childComplexity int, rawArgs map[string]interface{}) (int, bool) {
	ec := executionContext{nil, e}
	_ = ec
	switch typeName + "." + field {

	case "Query.findSomething":
		args, err := ec.field_Query_findSomething_args(context.TODO(), rawArgs)
		if err != nil {
			return 0, false
		}

		return gen.QueryFindSomethingComplexity(childComplexity, args["filter"].(gen.Filter)), true
       <...>
acelot

comment created time in 3 months