enki | Renders API Blueprint docs and uploads them to Confluence | REST library

Your code produced the correct results for the data you fed it!

The breakpoint list [30, 44, 66, 75, 85] bisects the letter string "FEDCBA" as follows:

1. Check tables name
2. You need to Give a space before where

I mean...

"Select username, password " + "Where username =....."

Or

"Select username, password" + " Where username =....."

Here is one method that uses a correlated subquery:

This is rather vague text there, but I guess it is just that if the descriptor is closed elsewhere, it is silently removed from the set. From Linux manpages, epoll(7):

Q6 Will closing a file descriptor cause it to be removed from all epoll sets automatically?

A6 Yes, but be aware of the following point. A file descriptor is a reference to an open file description (see open(2)). Whenever a descriptor is duplicated via dup(2), dup2(2), fcntl(2) F_DUPFD, or fork(2), a new file descriptor refer‐ ring to the same open file description is cre‐ ated. An open file description continues to exist until all file descriptors referring to it have been closed. A file descriptor is removed from an epoll set only after all the file descriptors referring to the underlying open file description have been closed (or before if the descriptor is explicitly removed using epoll_ctl(2) EPOLL_CTL_DEL). This means that even after a file descriptor that is part of an epoll set has been closed, events may be reported for that file descriptor if other file descrip‐ tors referring to the same underlying file description remain open.

So you have a socket with fd 42. It gets closed, and subsequently removed from the epoll object. But the kernel doesn't notify the libev about this through epoll_wait. Now the epoll_modify is called again with fd = 42. epoll_modify doesn't know whether this file descriptor 42 the same that already was in the epoll object or some other file description with the file descriptor number 42 reused.

One could also argue that the comments are just ranting and the design of the libev API is at fault here.

When you're not using IniRealm, you don't directly map Roles -> Permissions. You have to tell Shiro what permissions a User has with SimpleAuthorizationInfo's addStringPermissions or addObjectPermissions and if you're using roles to assign groups of permissions manually retrieve those.

There are multiple ways to do this depending on your app. Without knowing how complex your application is, it's difficult to recommend an approach. For maximum flexibility, you can create 3 database tables: USER_PERMISSIONS, ROLE_PERMISSIONS, and USER_ROLES.

If you're only doing permission checks, I'd recommend doGetAuthorizationInfo only retrieve the permissions assigned to a user. Roles would only be used on the front-end to assist in assigning groups of permissions to certain users. This is the Explicit Role recommended by Shiro in Roles.