Skip to content

Use shields for IRC links#3

Merged
LukasReschke merged 1 commit into
nextcloud:masterfrom
MariusBluem:shields-for-irc
Jun 3, 2016
Merged

Use shields for IRC links#3
LukasReschke merged 1 commit into
nextcloud:masterfrom
MariusBluem:shields-for-irc

Conversation

@MariusBluem

Copy link
Copy Markdown
Member
@MariusBluem MariusBluem self-assigned this Jun 3, 2016
@LukasReschke

Copy link
Copy Markdown
Member

Great! 🚀

@LukasReschke
LukasReschke merged commit 62ef905 into nextcloud:master Jun 3, 2016
@MariusBluem
MariusBluem deleted the shields-for-irc branch June 3, 2016 18:32
@jancborchardt

Copy link
Copy Markdown
Member

Good stuff, thanks a lot! :)

@MorrisJobke MorrisJobke modified the milestone: Nextcloud 10 Jun 14, 2016
@g4jsg g4jsg mentioned this pull request Feb 22, 2017
@ghost ghost mentioned this pull request Jul 26, 2017
alpapan added a commit to alpapan/nextcloud-server that referenced this pull request Feb 7, 2024
fixes this error caused when system has usernames that are purely numeric.

An unhandled exception has been thrown:
Error: Object of class OCA\User_LDAP\User\User could not be converted to string in /var/www/nextcloud/apps/user_ldap/lib/User_LDAP.php:312
Stack trace:
#0 [internal function]: OCA\User_LDAP\User_LDAP->userExistsOnLDAP()
nextcloud#1 /var/www/nextcloud/apps/user_ldap/lib/User_Proxy.php(126): call_user_func_array()
nextcloud#2 /var/www/nextcloud/apps/user_ldap/lib/Proxy.php(140): OCA\User_LDAP\User_Proxy->walkBackends()
nextcloud#3 /var/www/nextcloud/apps/user_ldap/lib/User_Proxy.php(262): OCA\User_LDAP\Proxy->handleRequest()
nextcloud#4 /var/www/nextcloud/apps/user_ldap/lib/User_Proxy.php(239): OCA\User_LDAP\User_Proxy->userExistsOnLDAP()
nextcloud#5 /var/www/nextcloud/lib/private/User/Manager.php(168): OCA\User_LDAP\User_Proxy->userExists()
nextcloud#6 /var/www/nextcloud/apps/files_fulltextsearch/lib/Service/FilesService.php(399): OC\User\Manager->get()
nextcloud#7 /var/www/nextcloud/apps/files_fulltextsearch/lib/Service/FilesService.php(226): OCA\Files_FullTextSearch\Service\FilesService->initFileSystems()
nextcloud#8 /var/www/nextcloud/apps/files_fulltextsearch/lib/Provider/FilesProvider.php(246): OCA\Files_FullTextSearch\Service\FilesService->getChunksFromUser()
nextcloud#9 /var/www/nextcloud/apps/fulltextsearch/lib/Service/IndexService.php(174): OCA\Files_FullTextSearch\Provider\FilesProvider->generateChunks()
nextcloud#10 /var/www/nextcloud/apps/fulltextsearch/lib/Command/Index.php(403): OCA\FullTextSearch\Service\IndexService->indexProviderContentFromUser()
nextcloud#11 /var/www/nextcloud/apps/fulltextsearch/lib/Command/Index.php(280): OCA\FullTextSearch\Command\Index->indexProvider()
nextcloud#12 /var/www/nextcloud/3rdparty/symfony/console/Command/Command.php(298): OCA\FullTextSearch\Command\Index->execute()
nextcloud#13 /var/www/nextcloud/core/Command/Base.php(177): Symfony\Component\Console\Command\Command->run()
nextcloud#14 /var/www/nextcloud/3rdparty/symfony/console/Application.php(1040): OC\Core\Command\Base->run()
nextcloud#15 /var/www/nextcloud/3rdparty/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand()
nextcloud#16 /var/www/nextcloud/3rdparty/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun()
nextcloud#17 /var/www/nextcloud/lib/private/Console/Application.php(206): Symfony\Component\Console\Application->run()
nextcloud#18 /var/www/nextcloud/console.php(100): OC\Console\Application->run()
nextcloud#19 /var/www/nextcloud/occ(11): require_once('...')
nextcloud#20 {main}roopico /var/www/nextcloud/apps/user_ldap/lib/User/OfflineUser.phparch:index


Signed-off-by: Alexie Papanicolaou <alpapan@gmail.com>
miaulalala added a commit that referenced this pull request Dec 16, 2025
# This is the 1st commit message:

feat(snowflake): extend Entity class to support snowflakes

RFC: extending the Entity class to support snoflake IDs automagically

Good ides - yes / no?

Benefits:
- every entity that supports snowflake IDs can automagically handle them by implementing the `SnowflakeAwareEntity` instead of the regular `Entity`
- No adding IGenerator / IDecoder in every entity class
- centralised method support for `createdAt`, `setId`, and anything else we would like to offer separately
- get entire decoded snowflake id from the entity

Drawbacks:
- Will it work the way I think it should?

Signed-off-by: Anna Larch <anna@nextcloud.com>

# The commit message #2 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #3 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #4 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #5 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #6 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #7 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #8 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #9 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #10 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #11 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #12 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #13 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #14 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #15 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes

# The commit message #16 will be skipped:

# fixup! feat(snowflake): extend Entity class to support snowflakes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

4 participants