{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":341058855,"defaultBranch":"master","name":"pulsar","ownerLogin":"yangl","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-02-22T02:37:52.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/231353?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1677849281.585016","currentOid":""},"activityList":{"items":[{"before":"a9037334a399af905fae94d2aefa5db339cbd5b1","after":"5d5ec947249df50bf35a78b6a2a0d3b00d97ca66","ref":"refs/heads/master","pushedAt":"2023-05-15T03:04:38.015Z","pushType":"push","commitsCount":170,"pusher":{"login":"yangl","name":"YANGLiiN","path":"/yangl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/231353?s=80&v=4"},"commit":{"message":"[fix][broker] Allow Access to System Topic Metadata for Reader Creation Post-Namespace Deletion (#20304)\n\n## Motivation\r\nAfter initiating the snapshot segment function, deletion of topics necessitates the activation of readers. Furthermore, these readers should be opened and deleted as they are used, which implies that we should not pre-store readers. However, after initiating the deletion of namespaces currently, it is not allowed to obtain the metadata of partition topics or lookup, making it impossible to create readers. This results in the inability to delete namespaces.\r\n\r\n## Modification\r\nAllow the acquisition of system topic metadata after initiating namespace deletion, thus creating readers to clean up topic data.","shortMessageHtmlLink":"[fix][broker] Allow Access to System Topic Metadata for Reader Creati…"}},{"before":"e973388eb77f226e0546f88c87821f8c7ee26281","after":"a9037334a399af905fae94d2aefa5db339cbd5b1","ref":"refs/heads/master","pushedAt":"2023-03-22T11:08:47.135Z","pushType":"push","commitsCount":53,"pusher":{"login":"yangl","name":"YANGLiiN","path":"/yangl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/231353?s=80&v=4"},"commit":{"message":"[fix] [admin] Make response code to 400 instead of 500 when delete topic fails due to enabled geo-replication (#19879)\n\nMotivation: As expected, If geo-replication is enabled, a topic cannot be deleted. However deleting that topic returns a 500, and no further info.\r\nModifications: Make response code to 400 instead of 500 when delete topic fails due to enabled geo-replication","shortMessageHtmlLink":"[fix] [admin] Make response code to 400 instead of 500 when delete to…"}},{"before":"d17bdf85d184c37cfcc16cfcb8df6f2e198e6fec","after":"e973388eb77f226e0546f88c87821f8c7ee26281","ref":"refs/heads/master","pushedAt":"2023-03-08T10:23:53.034Z","pushType":"push","commitsCount":8,"pusher":{"login":"yangl","name":"YANGLiiN","path":"/yangl","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/231353?s=80&v=4"},"commit":{"message":"[fix][broker] Fixed history load not releasing (#19726)","shortMessageHtmlLink":"[fix][broker] Fixed history load not releasing (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1611271807\" data-permission-text=\"Title is private\" data-url=\"https://github.com/apache/pulsar/issues/19726\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/apache/pulsar/pull/19726/hovercard\" href=\"https://github.com/apache/pulsar/pull/19726\">apache#19726</a>)"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADLJQuOgA","startCursor":null,"endCursor":null}},"title":"Activity · yangl/pulsar"}