[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #93: Fix wrong step number caused by #75
SignorMercurio opened a new pull request, #93: URL: https://github.com/apache/pulsar-site/pull/93 In #75, `display: list-item` and `counter-reset` are used to add line number in code blocks, which impacts the index of normal `` elements. This PR uses `display: inline-block` and a number of styles instead and should fix apache/pulsar#15662. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace merged pull request #93: Fix wrong step number caused by #75
urfreespace merged PR #93: URL: https://github.com/apache/pulsar-site/pull/93 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #94: Prettify line number in code blocks
SignorMercurio opened a new pull request, #94: URL: https://github.com/apache/pulsar-site/pull/94 1. Reduce the padding between line number and code. 2. Remove `position: sticky` to eliminate strange scrolling behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace merged pull request #94: Prettify line number in code blocks
urfreespace merged PR #94: URL: https://github.com/apache/pulsar-site/pull/94 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] zrsaber opened a new pull request, #95: fix error about star
zrsaber opened a new pull request, #95: URL: https://github.com/apache/pulsar-site/pull/95 Fix the star error, complete the following issues https://github.com/apache/pulsar-site/issues/83 four in https://github.com/apache/pulsar/issues/15550 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (PULSAR-20) Exception for "Topic not exist" should name the topic and server
[ https://issues.apache.org/jira/browse/PULSAR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541477#comment-17541477 ] Jason Kania commented on PULSAR-20: --- Thanks for the response and the PR. The issue was due to auto-creation not being enabled but made difficult due to the error message. Not creating the topics seems to be the default configuration that comes with the bundle. > Exception for "Topic not exist" should name the topic and server > > > Key: PULSAR-20 > URL: https://issues.apache.org/jira/browse/PULSAR-20 > Project: Pulsar > Issue Type: Improvement >Reporter: Jason Kania >Priority: Major > > I am getting the following exception while using Flink with Pulsar where I > believe the topic does not exist but I cannot determine which topic it is > because the job is complicated. I get the following error: > org.apache.pulsar.client.admin.PulsarAdminException$NotFoundException: Topic > not exist > at > org.apache.pulsar.client.admin.internal.BaseResource.getApiException(BaseResource.java:230) > at > org.apache.pulsar.client.admin.internal.TopicsImpl$7.failed(TopicsImpl.java:529) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.JerseyInvocation$1.failed(JerseyInvocation.java:882) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.JerseyInvocation$1.completed(JerseyInvocation.java:863) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:229) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime.access$200(ClientRuntime.java:62) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime$2.lambda$response$0(ClientRuntime.java:173) > at > org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors$1.call(Errors.java:248) > at > org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors$1.call(Errors.java:244) > at > org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:292) > at > org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:274) > at > org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:244) > at > org.apache.pulsar.shade.org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288) > at > org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime$2.response(ClientRuntime.java:173) > at > org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$apply$1(AsyncHttpConnector.java:228) > at > java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859) > at > java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837) > at > java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) > at > java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073) > at > org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$retryOperation$4(AsyncHttpConnector.java:270) > at > java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859) > at > java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837) > at > java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) > at > java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.NettyResponseFuture.loadContent(NettyResponseFuture.java:222) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:257) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.handler.AsyncHttpClientHandler.finishUpdate(AsyncHttpClientHandler.java:241) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.handler.HttpHandler.handleChunk(HttpHandler.java:114) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.handler.HttpHandler.handleRead(HttpHandler.java:143) > at > org.apache.pulsar.shade.org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78) > at > org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) > at > org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) > at > org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) > at > org.apache.pulsar.shade.io.netty.handler.codec.MessageToMessageDecod
[GitHub] [pulsar-site] visortelle opened a new issue, #96: Algolia search doesn't work
visortelle opened a new issue, #96: URL: https://github.com/apache/pulsar-site/issues/96 https://user-images.githubusercontent.com/9302460/170059683-887cb086-5836-4d00-8e65-def534fdfbea.mov Checked with Chrome and Firefox. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #97: Sync language tab choices
SignorMercurio opened a new pull request, #97: URL: https://github.com/apache/pulsar-site/pull/97 Fix apache/pulsar#10282. Please see the original issue for more details. Note that some pages use options like `pulsar-admin`, `REST API` and `Java`, while others use `Admin CLI`, `REST API` and `Java Admin API`. Not sure if we should make these options consistent, but I've ensured that the options on the same page is consistent so that the tab choices are synced on the same page. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Apache Pulsar 2.10.1 release
There are some PRs that are coming in that must be included. Thanks, Dave > On May 23, 2022, at 9:59 PM, Yunze Xu wrote: > > +1 > > Thanks, > Yunze > > > > >> 2022年5月23日 11:34，Hang Chen 写道： >> >> +1 >> >> There are a lot of transaction fixes. >> >> Thanks, >> Hang >> >> PengHui Li 于2022年5月21日周六 13:06写道： >>> >>> Hello, Pulsar community: >>> >>> I'd like to propose to release Apache Pulsar 2.10.1 >>> >>> Currently, we have 190 commits [0] and there are many transaction >>> fixes, security fixes. >>> >>> And there are 22 open PRs [1], I will follow them to make sure that >>> the important fixes could be contained in 2.10.1 >>> >>> If you have any important fixes or any questions, >>> please reply to this email, we will evaluate whether to >>> include it in 2.10.1 >>> >>> [0] >>> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.1+ >>> [1] >>> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.10.1+ >>> >>> Best Regards >>> Penghui >
Re: [DISCUSS] Apache Pulsar 2.9.3 release
There are some PRs that are coming in that must be included. Thanks, Dave > On May 23, 2022, at 4:29 AM, PengHui Li wrote: > > +1 > > Thanks > Penghui > > On Mon, May 23, 2022 at 3:31 PM mattison chao > wrote: > >> Hello, Pulsar community: >> >> I'd like to propose to release Apache Pulsar 2.9.3 >> >> Currently, we have 192 commits [0] and there are many transaction >> fixes, security fixes. >> >> And there are 22 open PRs [1], I will follow them to make sure that >> the important fixes could be contained in 2.9.3 >> >> If you have any important fixes or any questions, >> please reply to this email, we will evaluate whether to >> include it in 2.9.3 >> >> [0] >> >> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+ >> [1] >> >> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.9.3+ >> >> Best Regards >> Mattison >>
Re: [DISCUSS] Apache Pulsar 2.9.3 release
+1 Thanks, Hang Dave Fisher 于2022年5月25日周三 04:18写道： > > There are some PRs that are coming in that must be included. > > Thanks, > Dave > > > > On May 23, 2022, at 4:29 AM, PengHui Li wrote: > > > > +1 > > > > Thanks > > Penghui > > > > On Mon, May 23, 2022 at 3:31 PM mattison chao > > wrote: > > > >> Hello, Pulsar community: > >> > >> I'd like to propose to release Apache Pulsar 2.9.3 > >> > >> Currently, we have 192 commits [0] and there are many transaction > >> fixes, security fixes. > >> > >> And there are 22 open PRs [1], I will follow them to make sure that > >> the important fixes could be contained in 2.9.3 > >> > >> If you have any important fixes or any questions, > >> please reply to this email, we will evaluate whether to > >> include it in 2.9.3 > >> > >> [0] > >> > >> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.3+ > >> [1] > >> > >> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.9.3+ > >> > >> Best Regards > >> Mattison > >> >
[GitHub] [pulsar-helm-chart] michaeljmarshall commented on pull request #266: Add bk, zk securityContext to support upgrade to non-root docker image
michaeljmarshall commented on PR #266: URL: https://github.com/apache/pulsar-helm-chart/pull/266#issuecomment-1136704025 @maxsxu - thanks for testing out my theory. I realize now that the `fsGroup` does not technically need to be `0` or `root` in this configuration. A user deploying to OpenShift can choose any user that is acceptable. The docker image will work correctly, because the `.conf` files are writable by the `root` group, and the configured `fsGroup` will own the PVCs. Essentially, OpenShift users will just need to select an `fsGroup` that passes the security context requirements. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-manager] Hongten opened a new issue, #463: Pulsar manager supports normal users to access
Hongten opened a new issue, #463: URL: https://github.com/apache/pulsar-manager/issues/463 Currently, the pulsar admin can access the pulsar manager to manage the Pulsar clusters. However, normal users can not access it. I think the pulsar manager should support it. For example. The users have below operations on the pulsar manager. 1. Users request to create a tenant, namespace, and topic(Need admin to approve) 2. Users request the permission for the namespace( e.g produce, consume)(Need admin to approve) 3. Users request the quota for the namespace(Need admin to approve) 4. Users request to view the topic that users user have permission to access 5. Users request to view the real-time traffic and historical traffic for topics -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-manager] urfreespace merged pull request #458: feat:upgrade version to 0.3.0
urfreespace merged PR #458: URL: https://github.com/apache/pulsar-manager/pull/458 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
