Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST APIのテスト #23

Closed
syuilo opened this issue Jan 4, 2017 · 0 comments
Closed

REST APIのテスト #23

syuilo opened this issue Jan 4, 2017 · 0 comments

Comments

@syuilo
Copy link
Member

syuilo commented Jan 4, 2017

REST APIをテストするには、まずTravis上にMongoDBなどを構築する必要があります
参考: https://docs.travis-ci.com/user/database-setup

syuilo added a commit that referenced this issue Jan 4, 2017
Add services to .travis.yml
@syuilo syuilo closed this as completed Jan 19, 2017
@syuilo syuilo added the test label Jan 19, 2017
acid-chicken pushed a commit that referenced this issue Apr 23, 2019
Steve-0628 referenced this issue in Steve-0628/misskey Feb 20, 2023
* feat: github actionsでdockerイメージをビルドする

* fix: change workflow name and install ca

* fix: apt-getで運が悪いとコケる対策

* feat: Docker composeでのビルド時にghcr.ioからキャッシュを取ってくるようにした

* remove: `misskey-dev/misskey`既存のworkflowを削除
anatawa12 referenced this issue in anatawa12/misskey May 9, 2024
shiosyakeyakini-info pushed a commit to shiosyakeyakini-info/misskey that referenced this issue Aug 31, 2024
* add: Importing of Posts

- Supports Instagram, Mastodon/Pleroma/Akkoma, Twitter and *key

* upd: update limit

* upd: pass full thinuser

* fix: cleanup not available on development env

* upd: remove unused function, fix logger message

* fix: broken unicode in strings on IG imports

* fix: use a proper function

* any→string

Co-Authored-By: Marie <[email protected]>

* fix: prevent *key renotes/boosts from being imported

Stop renotes/boosts from *key from being imported due to missing functionality of getting the related posts

* upd: import replies to own posts on *key

* fix: type

* upd: import own replies to own tweets

* chore: remove type in DbNoteImportToDbJobData

* merge: improve recreateChain

Resolves misskey-dev#159

* upd: remove event stream calls on import

* upd: lower max uses per hour on `import notes`

* upd: add `Facebook` to note importing

* fix: attachments not working on FB import

* upd: create Folders for imported media

* prepare to import more notes

`recreateChain` converts a list of notes into a forest of notes, using
notes that are not replies as roots, and replies as child nodes,
recursively.

Previously, notes that are replies to notes not included in the
export, and their children, were never put in the forest, and
therefore wheren't imported.

This can be fine when importing from Twitter, since we can't really
link a note to a tweet.

And, for the moment, it's acceptable when importing from *key, because
the export doesn't contain the instance URL, so we can't resolve ids
to remote notes.

It's less fine when importing from Mastodon / Pleroma / Akkoma,
because in those cases we _can_ link to the remote note that the user
was replying to.

This commit makes `recreateChain` optionally return "orphaned" note
trees, so in the (near) future we can use it to properly thread
imported notes from those services.

* properly thread Mastodon imports

* fix chaining for Mastodon notes

the id / replyId are not at the top level, so now `recreateChain`
takes a list of keys to walk, not just a single key

* thread Pleroma imports as well

I have _not_ tested this, but it should work fine, those exports are
the same shape as Mastodon's

* Use hashed filename for exists check

* upd: prevent vanilla mastodon imports from importing DMs

Also adds the visibility function to mastodon imports

* fix: correct followers visibility on import

* fix: if condition

* upd: add home as a visibility for mastodon imports

* Use hex digest

* Use base64url digest

* Simplify hash steps

* fix: visibility check on masto import

Originally from PR misskey-dev#288

* link twitter names to twitter, not nitter misskey-dev#382

nitter seems very dead

* Fixed code injection from twitter import

* simpler json-isation

thanks Alina for the suggestion

* simpler mapping

thanks Alina

* make almost all fs ops async

there's no `fs.promises.exists`

* simpler logic

thanks Alina

* decode entity references from tweets

apparently *some* tweets have those ☹

* lint

* import fs/promises the right way

thanks Marie

* fix: keep alt text of file if present

* allow setting separate timeout / max size for imports - fixes misskey-dev#479

* Update index.d.ts

* lint

* os.api→misskeyApi

* Update QueueProcessorService.ts

Co-Authored-By: Marie <[email protected]>

* Chore: remove sharkey specific elements

* Add check for prohibited words when importing notes

Co-Authored-By: Marie <[email protected]>

* Update ImportNotesProcessorService.ts

Co-Authored-By: Marie <[email protected]>

* Fix: DragonflyDB error during note import

Production環境はこれをPushしても治らないので注意

* Fix: チャートにダイレクト投稿が反映されないように

* isSensitive→isKeyWordIncluded

* Enhance: pushしないTLを指定できるように

* Chore: Prevent FTT issues from invalid note time

* Chore: Add note import info and disclaimer

* Refactor: NoteCreateService

* Feat: isInHanaModeというユーザー概念を追加

* Enhance: Featuredで連合先のノートも扱うように、規模に合わせてすべてのノートを考慮

* Feat: はなみタイムライン

* Feat(backend):はなモード中にするノートはローカルタイムラインに流れないように

* autogen

* autogen

* Update misskey-js.api.md

* Fix: test

* fix: e2e test

* add csp

* fix csp

* add icon font

* enhance: 設定画面を独立させる

* fix tl behavior

* remove unused locale string

* add english translation

* fix

* lint

* PostFormまわりの公開範囲の表示をはなモードで切り分ける

* lint

* tweak design

* lint

* add missing property

* specify hanamode preference when invoking notes/create

* add hanamode visibility icon to note header

* Revert "specify hanamode preference when invoking notes/create"

This reverts commit d253d62.

* (backend) dont explicitly specify that the note is in hanamode

* Chore: Follow API changes in commit 6e10704

* add missing schema

* remove official support for some platform

* lint

* Fix: Type Error

* refactor

* lint

Co-authored-by: かっこかり <[email protected]>

---------

Co-authored-by: Mar0xy <[email protected]>
Co-authored-by: Gianni Ceccarelli <[email protected]>
Co-authored-by: dakkar <[email protected]>
Co-authored-by: smitten <[email protected]>
Co-authored-by: KevinWh0 <[email protected]>
Co-authored-by: kakkokari-gtyih <[email protected]>
lqvp referenced this issue in lqvp/misskey Nov 11, 2024
feat: リアクションした人一覧がブロック・ミュートを考慮するようにする設定
lqvp referenced this issue in lqvp/misskey Nov 28, 2024
* add: Importing of Posts

- Supports Instagram, Mastodon/Pleroma/Akkoma, Twitter and *key

* upd: update limit

* upd: pass full thinuser

* fix: cleanup not available on development env

* upd: remove unused function, fix logger message

* fix: broken unicode in strings on IG imports

* fix: use a proper function

* any→string

Co-Authored-By: Marie <[email protected]>

* fix: prevent *key renotes/boosts from being imported

Stop renotes/boosts from *key from being imported due to missing functionality of getting the related posts

* upd: import replies to own posts on *key

* fix: type

* upd: import own replies to own tweets

* chore: remove type in DbNoteImportToDbJobData

* merge: improve recreateChain

Resolves misskey-dev#159

* upd: remove event stream calls on import

* upd: lower max uses per hour on `import notes`

* upd: add `Facebook` to note importing

* fix: attachments not working on FB import

* upd: create Folders for imported media

* prepare to import more notes

`recreateChain` converts a list of notes into a forest of notes, using
notes that are not replies as roots, and replies as child nodes,
recursively.

Previously, notes that are replies to notes not included in the
export, and their children, were never put in the forest, and
therefore wheren't imported.

This can be fine when importing from Twitter, since we can't really
link a note to a tweet.

And, for the moment, it's acceptable when importing from *key, because
the export doesn't contain the instance URL, so we can't resolve ids
to remote notes.

It's less fine when importing from Mastodon / Pleroma / Akkoma,
because in those cases we _can_ link to the remote note that the user
was replying to.

This commit makes `recreateChain` optionally return "orphaned" note
trees, so in the (near) future we can use it to properly thread
imported notes from those services.

* properly thread Mastodon imports

* fix chaining for Mastodon notes

the id / replyId are not at the top level, so now `recreateChain`
takes a list of keys to walk, not just a single key

* thread Pleroma imports as well

I have _not_ tested this, but it should work fine, those exports are
the same shape as Mastodon's

* Use hashed filename for exists check

* upd: prevent vanilla mastodon imports from importing DMs

Also adds the visibility function to mastodon imports

* fix: correct followers visibility on import

* fix: if condition

* upd: add home as a visibility for mastodon imports

* Use hex digest

* Use base64url digest

* Simplify hash steps

* fix: visibility check on masto import

Originally from PR misskey-dev#288

* link twitter names to twitter, not nitter misskey-dev#382

nitter seems very dead

* Fixed code injection from twitter import

* simpler json-isation

thanks Alina for the suggestion

* simpler mapping

thanks Alina

* make almost all fs ops async

there's no `fs.promises.exists`

* simpler logic

thanks Alina

* decode entity references from tweets

apparently *some* tweets have those ☹

* lint

* import fs/promises the right way

thanks Marie

* fix: keep alt text of file if present

* allow setting separate timeout / max size for imports - fixes misskey-dev#479

* Update index.d.ts

* lint

* os.api→misskeyApi

* Update QueueProcessorService.ts

Co-Authored-By: Marie <[email protected]>

* Chore: remove sharkey specific elements

* Add check for prohibited words when importing notes

Co-Authored-By: Marie <[email protected]>

* Update ImportNotesProcessorService.ts

Co-Authored-By: Marie <[email protected]>

* Fix: DragonflyDB error during note import

Production環境はこれをPushしても治らないので注意

* Fix: チャートにダイレクト投稿が反映されないように

* isSensitive→isKeyWordIncluded

* Enhance: pushしないTLを指定できるように

* Chore: Prevent FTT issues from invalid note time

* Chore: Add note import info and disclaimer

* Refactor: NoteCreateService

* Feat: isInHanaModeというユーザー概念を追加

* Enhance: Featuredで連合先のノートも扱うように、規模に合わせてすべてのノートを考慮

* Feat: はなみタイムライン

* Feat(backend):はなモード中にするノートはローカルタイムラインに流れないように

* autogen

* autogen

* Update misskey-js.api.md

* Fix: test

* fix: e2e test

* add csp

* fix csp

* add icon font

* enhance: 設定画面を独立させる

* fix tl behavior

* remove unused locale string

* add english translation

* fix

* lint

* PostFormまわりの公開範囲の表示をはなモードで切り分ける

* lint

* tweak design

* lint

* add missing property

* specify hanamode preference when invoking notes/create

* add hanamode visibility icon to note header

* Revert "specify hanamode preference when invoking notes/create"

This reverts commit d253d62.

* (backend) dont explicitly specify that the note is in hanamode

* Chore: Follow API changes in commit 6e10704

* add missing schema

* remove official support for some platform

* lint

* Fix: Type Error

* refactor

* lint

Co-authored-by: かっこかり <[email protected]>

---------

Co-authored-by: Mar0xy <[email protected]>
Co-authored-by: Gianni Ceccarelli <[email protected]>
Co-authored-by: dakkar <[email protected]>
Co-authored-by: smitten <[email protected]>
Co-authored-by: KevinWh0 <[email protected]>
Co-authored-by: kakkokari-gtyih <[email protected]>
u1-liquid pushed a commit to u1-liquid/misskey that referenced this issue Jan 16, 2025
…k-timeout

fix(stripe/webhook): Customer IDに該当するユーザーが存在しない場合タイムアウトが発生する問題を修正
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant