profile
viewpoint
Divyendu Singh divyenduz @prisma Berlin, Germany https://www.divyendusingh.com Learn and build.

divyenduz/KeyValueDB 7

A sqlite3 interface mainly to make a small cache

divyenduz/db-migration-relation-table-to-inline 2

Example that shows migration steps from relation table to inline in context of Prisma.

divyenduz/footybot 2

Auto signup to Football meetup

divyenduz/likecsdegree.com 2

Moving some internal notes to public domain

divyenduz/blog-graphql 1

blog-graphql for course

divyenduz/chi-editor 1

Editor in typescript for funzies

divyenduz/local-databases 1

Setup varios local databases via docker

divyendu-test/gh-action-outputs-test 0

Testing @actions/core API

divyendu-test/p2-254 0

Repro for https://github.com/prisma/prisma2/issues/254

divyendu-test/p2-connect2 0

Attempt to prove that behavior has changed with Prisma $connect auto-connecting

issue openedprisma/prisma-examples

Make workflow names better

Test matrix was implemented in https://github.com/prisma/prisma-examples/pull/2180

However, job names are "path-like" and not easily readable. This issue tracks fixing them.

image

created time in 6 minutes

issue closedprisma/prisma-examples

Tests should report failure if 1 of the tests fails

Right now Actions reports the tests are succeeding, although they are clearly failing:

https://github.com/prisma/prisma-examples/issues/1652 https://github.com/prisma/prisma-examples/issues/1651

That is dangerous, as one does not really see when stuff goes wrong.

Fundamentally there are 2 problems:

  1. All tests are run in one batch, a suggestion to change that is at https://github.com/prisma/prisma-examples/issues/1653
  2. Even when one of the tests clearly fails, the test run still reports a success as a whole.

If one of the tests fails, the run should report a failure as a whole.

closed time in 8 minutes

janpio

issue closedprisma/prisma-examples

Make it easier to read test output

Right now it is one long file with output. It would be nice if there was some visual separation (some empty lines and ######################## or something) to make it easier to visually parse. Also some clear output if a "test" (run.sh for 1 folder) succeeded or failed. Test runners do that for a reason ;)

closed time in 8 minutes

janpio

issue closedprisma/prisma-examples

Change the way tests are run

Right now there is only 1 test, that loops through all folders. That is practical, because it makes sure that all examples (= folders) have the proper test configuration that then is run during the test - no one can add a test without it also being tested.

Unfortunately that leads to super busy log output and makes it hard to understand what is going on.

An alternative suggestion: The test starts with a script that tests if for all folders there is a Github Actions workflow/job that triggers the .sh file that currently would be triggered via looping through the folders. That way, the whole test run can still be failed if an example is missing.

closed time in 8 minutes

janpio

issue closedprisma/prisma-examples

Error: listen EADDRINUSE: address already in use :::4000

+++++++++++
executing .github/tests/./typescript/subscriptions-pubsub/run.sh (tests)
yarn run v1.22.5
$ npm run generate:prisma
npm WARN lifecycle The node binary used for scripts is /tmp/yarn--1603911179469-0.4817221266893308/node but npm is using /opt/hostedtoolcache/node/12.19.0/x64/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

> subscriptions-pubsub@ generate:prisma /home/runner/work/prisma-examples/prisma-examples/typescript/subscriptions-pubsub
> prisma generate

Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (version: 2.10.0) to ./node_modules/@prisma/client in 65ms

You can now start using Prisma Client in your code:

```
import { PrismaClient } from '@prisma/client'
// or const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()
```

Explore the full API: http://pris.ly/d/client
$ cross-env NODE_ENV=development tsnd --no-notify --respawn --transpileOnly ./src
Using ts-node version 8.10.2, typescript version 4.0.5
Error: listen EADDRINUSE: address already in use :::4000
    at Server.setupListenHandle [as _listen2] (net.js:1317:16)
    at listenInCluster (net.js:1365:12)
    at Server.listen (net.js:1451:7)
    at /home/runner/work/prisma-examples/prisma-examples/typescript/subscriptions-pubsub/node_modules/apollo-server/src/index.ts:127:18
    at new Promise (<anonymous>)
    at ApolloServer.<anonymous> (/home/runner/work/prisma-examples/prisma-examples/typescript/subscriptions-pubsub/node_modules/apollo-server/src/index.ts:122:11)
    at Generator.next (<anonymous>)
    at /home/runner/work/prisma-examples/prisma-examples/typescript/subscriptions-pubsub/node_modules/apollo-server/dist/index.js:18:71
    at new Promise (<anonymous>)
    at __awaiter (/home/runner/work/prisma-examples/prisma-examples/typescript/subscriptions-pubsub/node_modules/apollo-server/dist/index.js:14:12)

closed time in 9 minutes

janpio

push eventprisma/prisma-examples

Divyendu Singh

commit sha a96db3ad8e4bb295f9febc81d83a1b0be6c4dc62

feat(matrix): test matrix

view details

Divyendu Singh

commit sha 3b1dcd677b67503a2d6d643bbbb1a03c4c78a81f

chore: bump nexus-plugin-prisma

view details

push time in 9 minutes

delete branch prisma/prisma-examples

delete branch : fix_eaddrinuse

delete time in 9 minutes

PR merged prisma/prisma-examples

feat(matrix): test matrix

Fixes

  • https://github.com/prisma/prisma-examples/issues/1653
  • https://github.com/prisma/prisma-examples/issues/1663
  • https://github.com/prisma/prisma-examples/issues/2171 (indirectly)
  • https://github.com/prisma/prisma-examples/issues/1659 (currently, there are no separate slack channels, this should already start working though)
+104 -70

0 comment

16 changed files

divyenduz

pr closed time in 9 minutes

push eventprisma/prisma-examples

Divyendu Singh

commit sha f7f17375751b3953ac6276f2c7ce915f30235caa

chore: bump nexus-plugin-prisma

view details

push time in an hour

PR opened prisma/prisma-examples

feat(matrix): test matrix
+90 -56

0 comment

2 changed files

pr created time in an hour

create barnchprisma/prisma-examples

branch : fix_eaddrinuse

created branch time in an hour

delete branch prisma/prisma-examples

delete branch : divyenduz-patch-1

delete time in 17 hours

push eventprisma/prisma-examples

Divyendu Singh

commit sha 093895ade627c23f0258b076c6ee0223a0ea36ce

Update renovate.json

view details

push time in 17 hours

PR merged prisma/prisma-examples

chore: update renovate.json

nexus-prisma-plugin should work with latest Prisma again

+1 -1

0 comment

1 changed file

divyenduz

pr closed time in 17 hours

issue commentprisma/e2e-tests

check-for-update script fails with merge conflicts

Another recent instance of it https://github.com/prisma/e2e-tests/runs/1322333533?check_suite_focus=true

divyenduz

comment created time in 17 hours

PR opened prisma/prisma-examples

Update renovate.json
+1 -1

0 comment

1 changed file

pr created time in 17 hours

create barnchprisma/prisma-examples

branch : divyenduz-patch-1

created branch time in 17 hours

push eventprisma/prisma-examples

Jan Piotrowski

commit sha e1feab0859e3a8b2f5da0366169d8238c4c7a7cc

docs(README): table for badges (#2167) Co-authored-by: Divyendu Singh <singh@prisma.io>

view details

push time in 17 hours

delete branch prisma/prisma-examples

delete branch : janpio-patch-1

delete time in 17 hours

PullRequestReviewEvent

push eventprisma/prisma-examples

Divyendu Singh

commit sha 499e29d1c593ec827cc38f26fe2c39464a3960e3

Update README.md

view details

push time in 17 hours

push eventprisma/prisma-examples

Divyendu Singh

commit sha a9040f68773c84c88f90c843f16c89c732018b45

Update README.md

view details

push time in 17 hours

issue openedprisma/migrate

Error: Error in migration engine. Reason: [C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\d023a05\src\connector\mysql\error.rs:129:43] index out of bounds: the len is 1 but the index is 1

<!-- If required, please update the title to be clear and descriptive -->

Command: prisma migrate up --experimental Version: 2.9.0 Binary Version: 369b3694b7edb869fad14827a33ad3f3f49bbc20 Report: https://prisma-errors.netlify.app/report/11672 OS: x64 win32 10.0.18363

JS Stacktrace:

Error: Error in migration engine.
Reason: [C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\d023a05\src\connector\mysql\error.rs:129:43] index out of bounds: the len is 1 but the index is 1

Please create an issue in the migrate repo with
your `schema.prisma` and the prisma command you tried to use 🙏:
https://github.com/prisma/migrate/issues/new

    at ChildProcess.<anonymous> (C:\Users\abdel$\Documents\shopify_back_end\prod\prisma2.0\node_modules\@prisma\cli\build\index.js:412:153)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:482:12)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)

Rust Stacktrace:

[C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\d023a05\src\connector\mysql\error.rs:129:43] index out of bounds: the len is 1 but the index is 1

created time in 18 hours

startedyuanqing/vdx

started time in a day

issue openedprisma/prisma

Prisma and $connect behavior

Bug description

prisma.$connect() behaviour is unexpected, it blocks to acquire a connection even though a connection is available.

How to reproduce

Follow the instructions in this reproduction repro https://github.com/divyendu-test/p2-connect

Expected behavior

Prisma should be able to acquire a connection when it is available.

created time in a day

issue commentprisma/studio

`--url`

This will also enable using Prisma studio as a standalone tool to access your databases. I love the design choices of Studio as my database client because

  1. Web-based (no installation etc, OS agnostic)
  2. Ephemeral (no maintenance of connection strings on desktop etc)
janpio

comment created time in a day

issue openedprisma/docs

OS detection for OS tabs

Example: https://www.prisma.io/docs/understand-prisma/under-the-hood#prisma-engines

Opening this URL on windows opens Unix, macOS tab by default. Opening windows tabs by default will be nice for our windows users.

created time in a day

issue openedprisma/docs

OS tabs should be in sync

Example: https://www.prisma.io/docs/understand-prisma/under-the-hood#prisma-engines

On this URL, switching to windows on one tab should switch to windows for all the tabs. Usually, a user is looking at docs for a specific OS.

created time in a day

issue openedprisma/e2e-tests

Rename mssql to sqlserver

mssql was internal naming we used, public naming shoudld be sqlserver

created time in a day

pull request commentprisma/database-schema-examples

feat(sql server): adjust sql server collected schemas

Feel free to merge :)

divyenduz

comment created time in 2 days

pull request commentprisma/database-schema-examples

feat(mssql): add docker image for mssql server and sample schema

Internal message, pasting here for visibility:

image

I will raise a PR to this PR that does it for already collected schemas, @eemmiillyy or anyone contributing schemas you can follow similar conventions for future schemas please :)

eemmiillyy

comment created time in 2 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha 9feb973de20ab6bfa68553caf11225e7a2786e9e

fix: yarn lock hotfix for redwood

view details

Divyendu Singh

commit sha 79cddf0b6c3512d88e7dafa7eae90ccfdb641c7b

Merge branch 'dev' of github.com:prisma/prisma2-e2e-tests into dev

view details

push time in 2 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha 5107552868cb8d6bfb18a8509fce60541097ba65

fix: yarn lock hotfix for redwood

view details

push time in 2 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha 8659a92cf20efc964516d86e5de57368722c9d5c

fix: disable check-for-update.sh for redwood+vercel test

view details

push time in 2 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha 223291e3b7cd7ee9986ca016762ef3512fb98a87

Revert "fix: pin redwood, 0.20.x fails with a babel/core error in yarn add" This reverts commit 56b9f4c08e846409f23eb1c327915aceefda2075.

view details

push time in 2 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha 56b9f4c08e846409f23eb1c327915aceefda2075

fix: pin redwood, 0.20.x fails with a babel/core error in yarn add

view details

push time in 2 days

PullRequestReviewEvent

push eventdivyenduz/p2-connect2

Divyendu Singh

commit sha e337cc0899cae09d1e5680a94628816bbeaefaa2

Update README.md

view details

push time in 2 days

fork divyenduz/fitbit_football_tracking

Export my personnal fitbit tcx data and play with it !

fork in 2 days

startedPierreDelarroqua/fitbit_football_tracking

started time in 2 days

PullRequestReviewEvent

startedzvictor/faugra

started time in 3 days

issue commentprisma/prisma-examples

Where is prisma-generate-schema repository

Aha, now I think I remember what package this refers too. This is from Prisma 1 and that code was moved and can be found here https://github.com/prisma/prisma1/tree/master/cli/packages

It has prisma-generate-schema :)

Curious about faugra, I will check it out later.

brikou

comment created time in 3 days

pull request commentprisma/language-tools

chore: add mssql to auto-completion

Note: if link to docs is available, we should use it :)

carmenberndt

comment created time in 3 days

PullRequestReviewEvent

push eventprisma/prisma-examples

Divyendu Singh

commit sha 381b77e2a513f427b5f33b7199b686c82744a39e

chore: improve prisma-version

view details

Divyendu Singh

commit sha d66a024f963a8726826741a45c3aad3e04acd854

feat: run tests before upgrade

view details

push time in 3 days

delete branch prisma/prisma-examples

delete branch : feat_bump_with_tests

delete time in 3 days

PR merged prisma/prisma-examples

feat(upgrade): bump only when tests pass

Fixes https://github.com/prisma/prisma-examples/issues/2063

+13 -2

0 comment

2 changed files

divyenduz

pr closed time in 3 days

issue closedprisma/prisma-examples

`@prisma` deps should only be updated if tests succeed

Right now, the sync script that updates the @prisma dependencies in all example projects always runs upon new releases of Prisma.

We often had the situation (and are experiencing it right now again as of the latest 2.8.0 release), that changes in the DMMF are breaking the nexus-prisma package which is used in a number of examples. Whenever this happens, the examples don't work any more and the tests for them start failing,

Functional example projects are really important for us, so we should make sure that our sync script only updates Prisma dependencies if the tests for a project succeed.

closed time in 3 days

nikolasburk

push eventprisma/prisma-examples

Divyendu Singh

commit sha 387277ec3be5e0818088241882abc73265645193

chore: sure kill with -9 flag

view details

push time in 3 days

PR opened prisma/prisma-examples

chore: sync, use 2.10.0-dev.63
+40 -40

0 comment

19 changed files

pr created time in 3 days

create barnchprisma/prisma-examples

branch : chore_kill_9

created branch time in 3 days

PR opened prisma/prisma-examples

feaT(upgrade): bump only when tests pass

Fixes https://github.com/prisma/prisma-examples/issues/2063

+13 -2

0 comment

2 changed files

pr created time in 3 days

create barnchprisma/prisma-examples

branch : feat_bump_with_tests

created branch time in 3 days

create barnchdivyendu-test/p2-query-creates-connection

branch : master

created branch time in 3 days

created repositorydivyendu-test/p2-query-creates-connection

This repo shows that Prisma's query tries to create a connection

created time in 3 days

issue commentprisma/prisma-examples

Where is prisma-generate-schema repository

The code has moved here https://github.com/prisma/prisma/tree/master/src/packages

brikou

comment created time in 3 days

push eventprisma/e2e-tests

Divyendu Singh

commit sha a84767a4a0deebd78167f8ee53f2bd9b409c4888

fix: vercel builder by changing scoped url

view details

push time in 3 days

delete branch prisma/e2e-tests

delete branch : fix_vercel_node_builder

delete time in 3 days

PR merged prisma/e2e-tests

fix: vercel builder by changing scoped url

https://e2e-vercel-node-builder.vercel.app/ is not updating anymore, we made no changes to the test.

Updating the URL to https://e2e-vercel-node-builder.prisma.vercel.app/ as a temporary workaround.

+2 -2

0 comment

2 changed files

divyenduz

pr closed time in 3 days

create barnchprisma/e2e-tests

branch : fix_vercel_node_builder

created branch time in 3 days

push eventdivyenduz/p2-connect2

Divyendu Singh

commit sha 0eedb99ed19093eff8a40837a48b0763773d2a08

Update README.md

view details

push time in 3 days

startedkoalalorenzo/docker-aliases

started time in 4 days

startedderailed/k9s

started time in 5 days

starteduber/cadence

started time in 5 days

startedjondot/react-flight

started time in 6 days

startedjasonkuhrt/setset

started time in 6 days

issue commentprisma/prisma

.transaction([]) fails with Request Timeout Error on large dataset

@jshimko I am able to reproduce this, thanks for the reproduction.

durdenx

comment created time in 6 days

create barnchdivyenduz/p2-connect2

branch : master

created branch time in 6 days

created repositorydivyenduz/p2-connect2

Attempt to prove that behavior has changed with Prisma $connect auto-connecting

created time in 6 days

push eventdivyendu-test/p2-connect

Divyendu Singh

commit sha 50f28ddb3ec0c6c9476226b8b5a3d31927160f32

add pg

view details

push time in 6 days

create barnchdivyendu-test/p2-connect

branch : master

created branch time in 6 days

created repositorydivyendu-test/p2-connect

Trying connect + Prisma 2

created time in 6 days

PullRequestReviewEvent

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 7177a63d91edfe23fa5b912165b2fba9754fe8d1

latest dev

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 9c3cf0c847d6fa426dbd44b4d915c2cff1a05733

latest dev

view details

push time in 6 days

issue openedprisma/prisma

Prisma and Netlify, binary is not downloaded automatically since 2.8.0

Bug description

Since Prisma 2.8.0 the following schema.prisma configuration doesn't download the binary

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}

How to reproduce

  1. Deploy this project to netlify https://github.com/divyendu-test/p2-netlify-ci (fulfil the required env var from Netlify UI)
  2. It is on Prisma version 2.8.0 and the service URL after the first deploy should fail with
{"errorType":"Error","errorMessage":"\nInvalid `prisma.user.deleteMany()` invocation in\n/var/task/src/functions/index.js:6:21\n\n\n Query engine binary for current platform \"rhel-openssl-1.0.x\" could not be found.\nThis probably happens, because you built Prisma Client on a different platform.\n(Prisma Client looked in \"/var/task/src/node_modules/@prisma/client/runtime/query-engine-rhel-openssl-1.0.x\")\n\nFiles in /var/task/src/node_modules/@prisma/client/runtime:\n\n index.d.ts\n index.js\n index.js.map\n\nYou already added the platform \"native\" to the \"generator\" block\nin the \"schema.prisma\" file as described in https://pris.ly/d/client-generator,\nbut something went wrong. That's suboptimal.\n\nPlease create an issue at https://github.com/prisma/prisma-client-js/issues/new","trace":["Error: ","Invalid `prisma.user.deleteMany()` invocation in","/var/task/src/functions/index.js:6:21","",""," Query engine binary for current platform \"rhel-openssl-1.0.x\" could not be found.","This probably happens, because you built Prisma Client on a different platform.","(Prisma Client looked in \"/var/task/src/node_modules/@prisma/client/runtime/query-engine-rhel-openssl-1.0.x\")","","Files in /var/task/src/node_modules/@prisma/client/runtime:",""," index.d.ts"," index.js"," index.js.map","","You already added the platform \"native\" to the \"generator\" block","in the \"schema.prisma\" file as described in https://pris.ly/d/client-generator,","but something went wrong. That's suboptimal.","","Please create an issue at https://github.com/prisma/prisma-client-js/issues/new"," at qw.request (/var/task/src/node_modules/@prisma/client/runtime/index.js:210:293)"]}
  1. Change the Prisma CLI/Client version to 2.7.0 and re-deploy
  2. It should work as expected

Expected behavior

  1. 2.8.0 should also download the required netlify binary if 2.7.0 does.
  2. The workaround of adding the specific binary works
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "rhel-openssl-1.0.x"]
}

created time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha b0ea8d9e93e1815edbb028d4c3fc5dea1f7bbe7a

chore: use 2.8.0

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 84f7f988f485a5de535effb484ecbf88d510f045

chore: use 2.7.0

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha d069ea59fb36b22b30663279d6d5334a1150df26

chore: use 2.8.0

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 96c76fbdc80ed603b0e6a8f0daa1c830a60fc0f7

chore: use 2.7.0

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha c3aaf93498bd602581be93f5818c0c62416b70a8

chore: use 2.8.0

view details

push time in 6 days

push eventdivyendu-test/redwood-tutorial-test

Divyendu Singh

commit sha d7fc2c6840753b7f3d38de6d765cc2d2f02b7042

chore: use rw 0.19.3

view details

push time in 6 days

push eventdivyendu-test/redwood-tutorial-test

David S Price

commit sha 4dcbfc17932b5f75519f42dc30021fd7900135ca

upgrade 0.19.5-canary.7 using prisma 2.9.0

view details

David S Price

commit sha ae0b104a051a5babc2205a18b3af20684633644d

upgrade 0.19.5-canary.22

view details

David S Price

commit sha 0d0eb5e6002d0b59cbfb489df88bc211cd692427

upgrade 0.19.5-canary.23; add binaryTarget rhel

view details

David S Price

commit sha 9987128c2e465ff6e36570bfef4b772b6e1dfdc0

code mode for Apollo v3 Scaffold change

view details

Divyendu Singh

commit sha dd90a9df075812afc979f3266ad0c6820752fa8a

chore: use only native

view details

Divyendu Singh

commit sha 7e01bad51ffea6483442cb84d12ff3ada929d7ea

feat: add meta cell to display Prisma version

view details

Divyendu Singh

commit sha 6c4c4f58338ba74e81ee31d435cc57c4c6c325d5

feat: add redwood version to meta cell

view details

Divyendu Singh

commit sha 48ee33966ff9d3541a49143982203141c8153240

Merge branch 'master' into v0.19.3

view details

push time in 6 days

push eventdivyendu-test/redwood-tutorial-test

Divyendu Singh

commit sha 6c4c4f58338ba74e81ee31d435cc57c4c6c325d5

feat: add redwood version to meta cell

view details

push time in 6 days

push eventdivyendu-test/redwood-tutorial-test

Divyendu Singh

commit sha 7e01bad51ffea6483442cb84d12ff3ada929d7ea

feat: add meta cell to display Prisma version

view details

push time in 6 days

issue openedredwoodjs/redwood

Add prismaVersion field to the redwood query

Feature request, this would help with debugging.

image

Prisma version can be fetched from

const { prismaVersion } = require('@prisma/client')
console.log(prismaVersion.client)

created time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha efead4fe136da2f3410d0cae52130d9e08cb4df8

trigger with 2.9.0

view details

push time in 6 days

push eventdivyendu-test/redwood-tutorial-test

Divyendu Singh

commit sha dd90a9df075812afc979f3266ad0c6820752fa8a

chore: use only native

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 1942e09ea56fff4d4c2904f4473f6281d946a7a8

trigger deploy

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 3b96f34890c68e5a85ed7033c5245b3c65e70a7c

trigger deploy

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 90d1759b94e3915d728bfdfabf532d71ab5d5a8c

trigger deploy

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 0c8b9ee87eb43876d1b5e1c6c54fcb7e7aedb457

deploy

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha 418d2c010761a670acd1f6f020203925c3080881

2.9.0

view details

push time in 6 days

push eventdivyendu-test/p2-netlify-ci

Divyendu Singh

commit sha b386abf64e984a76ffd84da1ebdf2b535ea45ff2

add binary targets

view details

push time in 6 days

more