fix(package): update monk to version 5.0.1 #479
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
korewaChino
pushed a commit
to FyraLabs/nyaakey
that referenced
this pull request
Jun 17, 2024
kanarikanaru
pushed a commit
to HanaMisskey/misskey
that referenced
this pull request
Aug 13, 2024
kanarikanaru
added a commit
to HanaMisskey/misskey
that referenced
this pull request
Aug 16, 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]>
nakkaa
pushed a commit
to nakkaa/kakurega.app
that referenced
this pull request
Sep 5, 2024
nanasina8
pushed a commit
to nanasina8/misskey
that referenced
this pull request
Sep 6, 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 taiyme#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 taiyme#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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #477