I have a problem that phabricator doesnt map user to svn commit in Diffusion, if the commits are commited before the user is created in phabricator. So the user will not receipt any notification related to that commit. Is there a way to map those commits to the user too. Thanks.
You can request a reparse of the commits from the command line.
bin/repository reparse --all REPO --message
The reparsing will happen in background, so don't expect instant results after the command is run.
Related
I made a page where users can update their names and status just like WhatsApp & Telegram.
These changes are published using LAZY mode since I don't want to update every user using the app right away. I just want to fetch it manually when necessary (for example when the user open the chat view with that user). (https://mesibo.com/documentation/api/real-time-api/profiles/#profile-publishing-mode)
The problem is: how can I fetch the updated profile of other users?
Whenever I get the profiles with Mesibo.getProfile("address") the data is still not updated.
since I don't want to update every user using the app right away.
Even if you use real-time mode, updates don't go to every user but only those users who have subscribed to it.
https://mesibo.com/documentation/api/real-time-api/profiles/#subscribing-to-a-profile
In lazy mode, it may be updated along with other profiles or when the message is received from the users. Before that, getProfile may not return the latest profile.
If you are starting with mesibo, recommend using real-time mode and optimizing later using the lazy mode
How to monitor each and every command executed by user, even in sudo level.
I have configured audit rules and they are appearing in audit.logs, but I want to view each command timely from server to Kibana/wazuh manager.
enter image description here
Auditd share complete commands and users UID too with wazuh if configured properly.
So I just added those columns from list in Kibana and now data is apearing fine.
here is the repo: https://github.com/webostin/sf-case-study/tree/master/movie-invalidator
Short App description
Platform Symfony. We have Movie Entity. We have complex caching system for cache movies pagination and movies itself. We have frontend panel and backend panel.
We have User Entity attached to Movie. We have also Admin Entity.
Problem
We need to soft delete Movie and at the same time reset cache and send email. We have to make it in three (or in future more) contexts:
Frontend User deletes Movie attached to him. Action: soft remove, reset cache, send email to admin;
Admin deletes Movie. Action: soft remove, cache restart, send email to User.
Cron while checking Movie data disables the movie. Action: soft remove, reset cache, send emails to Admin and User
Question
What is the best practise in this specific example. I found 3 solutions: implement everying separetly (not good), write an event subscriber and trigger an event whenever I want to disable Movie, write a service and use Service to disable Movie. It's question for best readable and proper solution. Please provide your solutions if you have any
Mark to delete the movie in the first step. In this case you do not need to unload the cache (you will see a warning message in the interface). In the second step, the administrator confirms the deletion and is added to the queue for cron. the third step is to delete the cron, send e-mail and clear the cache. In this way the entire load rides on the cron.
Why do i get this error message when i try to launch conversation service tool:
Unable to retrieve the list of workspaces. Error: Insufficient privileges
You need delete cookies of your browser. I faced with the same problem but after to delete cookies I could see my workspaces.
I'm one of the developers of the Watson Conversation service and you seem to have uncovered a small bug in the way that the tooling currently operates. We've been able to successfully reproduce this.
In short, when you open up the tooling to train an instance of the Watson Conversation service a call is made to Bluemix for all instances of the Watson Conversation service that you can see. However, due to the way that Bluemix space permissions work, you may be able to see instances that you don't have permission to edit. You should be able to find your service in the dropdown in the upper right corner of the screen.
In order to have permission to edit and make changes to an instance of the Watson Conversation service, you'll need to have dev permissions in the space that contains the instance of the Watson Conversation service. If you'd like to work on that service instance, you'll need to ask the person who owns the service instance to grant you dev permissions in the space. You can find out more about how to do this in the managing team members and roles section of the IBM Bluemix documentation.
I met the same issue
"Unable to retrieve the list of workspaces. Error: Insufficient privileges".
I double checked my permissions and validated that I have the admin access to all services in my space.
Then, I switched to a different browser and was able to navigate to the watson tool login page.So for my case, it looks more like a cookie issue. Thanks #Richard L. 's comment.
I have been trying Phabricator platform for 2 days in that to use it in our team. Everything seem fairly great except one I don't know how to make it.
We want to add Code Review process to our work flow forcefully. So I config Differential. Then as a developer I can use Arcanist command line to send a diff to the web UI requiring someone else to review. Someone can also accept or deny it after reviewing. That is OK.
But me who should be waiting other's review acceptance before pushing my changes to the hosted repo, can do that with git push (not arc land or arc amend) without the acceptance. How can I prevent this?
In the upstream we have Herald check for the presence of a Differential Commit, which you can send an embarrassing email, trigger an Audit, or whatever. Because we're a small team, we trigger an Audit (presuming those instances are generally emergencies and can be reviewed later). If the repository is also hosted by Phabricator, you can set a Policy on the repository to who has access to push to it. We use this to gate contributors. Frequent contributors can land reviewed code freely. New contributors have to have code landed by the upstream manually.
As far as I know, you can't. A user either has push rights or he has none. One way would be to trust the committer not to push his things until the review was accepted. On the other hand you could drop the right to push and let the reviewer or an administrator land the patch.
One different (maybe little complicated) way might be to create some herald rules to prevent the push. But I am not sure if herald is flexible and powerful enough for that kind of job.