profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/xrmx/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Riccardo Magliocchetti xrmx menodizero.it Torino http://menodizero.it

unbit/uwsgi 3031

uWSGI application server container

unbit/uwsgi-docs 621

Official uWSGI docs, examples, tutorials, tips and tricks

abogushov/django-admin-json-editor 133

Adds json-editor for JSONField in Django Administration

welaika/sputnik 27

Crawling since 1957

italia/docs.italia.it 18

The source code that powers docs.italia.it

italia/docs-italia-theme 15

Tema per i documenti pubblicati su Docs Italia

20tab/uwsgiit_console 7

web application that use uwsgi.it api

coding-gym/snippets 7

Common code and patterns for practicing

OfficineArduinoTorino/LabAdmin 4

Manage user rights to access the lab and the machines

20tab/autoindexer 2

A python script to implement the auto indexing feature (mod_autoindex in Apache)

issue commentunbit/uwsgi

UWSGI alarms not executing on Docker Containers

Do you have libpcre in your container image?

jesseinit

comment created time in 6 days

push eventxrmx/cairocffi

Riccardo Magliocchetti

commit sha 65d6a45a98e533603366ba65ded16988af058f4f

docs: fix typo in overview

view details

push time in 7 days

PR opened Kozea/cairocffi

docs: fix typo in overview
+1 -1

0 comment

1 changed file

pr created time in 7 days

fork xrmx/cairocffi

CFFI-based cairo bindings for Python.

https://cairocffi.readthedocs.io

fork in 7 days

push eventxrmx/splunk-sdk-python

Matt Schwager

commit sha f7164a967786c045a9d12546633e933edfe7203b

Fix #309, avoid catastrophic backtracking in searchcommands.internals

view details

Shilpa Bijam

commit sha af998eefcf0b3f1c4b9b5831d1c11f265817751d

Updates to release 1.6.13

view details

Shilpa Bijam

commit sha 5f80fbd814a264bc73084cb397dd974137c215b6

updated changelog

view details

Amy Sutedja

commit sha 7ff830d458713e5c996b205cdff651bbe0006c65

Install sdk-app-collection via docker-compose

view details

Amy Sutedja

commit sha b8aefd6cac3d064a1d281539eba2fdc31bca8d72

Helpful instructions around docker usage

view details

Amy Sutedja

commit sha 3e0c6f105f1f3777e68973bfa8acb37f097f4ba5

Move env variable directive in README quickstart to after the command

view details

Ivan Jager

commit sha 6b51317fb174ea6cf0d717d6cbeeb11f242fd4c5

Fix extra chunks being sent for large chunks Previously, when an external command used the SCPv2 (chunked=true) protocol via splunklib and returned with 50,000 or more rows for one chunk, it would send two replies intead of one. This caused the external command to get out of sync, sending chunk replies before reading the corresponding request. Fixes #150

view details

Ivan Jager

commit sha 2beb3e34e19cd90ff9a94083a7ea0b94eca94960

Keep chunk requests and responses synchronized

view details

Ivan Jager

commit sha 5002dc61c35a9f3d24b4086dec88ab9a0a9cc572

Fix generating commands

view details

Ivan Jager

commit sha da3fc20fd8738a4614b45eb15d3f1b9cc0ad91f3

Clean up and match previous behavior more closely

view details

Ivan Jager

commit sha 9052c904a757220da1c73a283137986f039539b3

Fix test_internals_v2.py

view details

Ivan Jager

commit sha bb0d71b93b9e083ed8b31a99e904cd3beb9fb83a

search_command no longer sends a successful response on fatal errors

view details

Amy Sutedja

commit sha 390d32767643e7cdf39f9623a908bf9c5634de11

Rename and cleanup follow-up for chunk synchronization

view details

Amy Sutedja

commit sha 9e981b17e9608d7fd285a24226494224edfea90b

Release workflow via Github Actions

view details

Amy Sutedja

commit sha d1553e5fffb25d479d361730bf7adc80f7da4a7d

Change url assert in test_package

view details

Amy Sutedja

commit sha d60a22c087ee1dfb8ad8b1ed5dbe866c963c69b0

Merge branch 'master' of github.com:splunk/splunk-sdk-python into develop

view details

David Poncelow

commit sha 6a9c77b969d1a29f435837469c17b915f0c80065

a test to confirm errors in searchcommands with multibyte data

view details

Amy Sutedja

commit sha 0780fc1878e2de0effd0bbfaa45a963a2c73b4b6

Fix for multibyte inputs to custom search commands

view details

Amy Sutedja

commit sha 253784c6f7b918bbc8ef02d9a8358f0866756087

Multibyte test cleanup

view details

Amy Sutedja

commit sha 8dec1678e4e1643580c63bf4a961ad0abe41c686

Cleaner naming and semantics for custom search command input streams

view details

push time in 9 days

push eventxrmx/splunk-sdk-python

Matt Schwager

commit sha f7164a967786c045a9d12546633e933edfe7203b

Fix #309, avoid catastrophic backtracking in searchcommands.internals

view details

Shilpa Bijam

commit sha af998eefcf0b3f1c4b9b5831d1c11f265817751d

Updates to release 1.6.13

view details

Shilpa Bijam

commit sha 5f80fbd814a264bc73084cb397dd974137c215b6

updated changelog

view details

Amy Sutedja

commit sha 7ff830d458713e5c996b205cdff651bbe0006c65

Install sdk-app-collection via docker-compose

view details

Amy Sutedja

commit sha b8aefd6cac3d064a1d281539eba2fdc31bca8d72

Helpful instructions around docker usage

view details

Amy Sutedja

commit sha 3e0c6f105f1f3777e68973bfa8acb37f097f4ba5

Move env variable directive in README quickstart to after the command

view details

Ivan Jager

commit sha 6b51317fb174ea6cf0d717d6cbeeb11f242fd4c5

Fix extra chunks being sent for large chunks Previously, when an external command used the SCPv2 (chunked=true) protocol via splunklib and returned with 50,000 or more rows for one chunk, it would send two replies intead of one. This caused the external command to get out of sync, sending chunk replies before reading the corresponding request. Fixes #150

view details

Ivan Jager

commit sha 2beb3e34e19cd90ff9a94083a7ea0b94eca94960

Keep chunk requests and responses synchronized

view details

Ivan Jager

commit sha 5002dc61c35a9f3d24b4086dec88ab9a0a9cc572

Fix generating commands

view details

Ivan Jager

commit sha da3fc20fd8738a4614b45eb15d3f1b9cc0ad91f3

Clean up and match previous behavior more closely

view details

Ivan Jager

commit sha 9052c904a757220da1c73a283137986f039539b3

Fix test_internals_v2.py

view details

Ivan Jager

commit sha bb0d71b93b9e083ed8b31a99e904cd3beb9fb83a

search_command no longer sends a successful response on fatal errors

view details

Amy Sutedja

commit sha 390d32767643e7cdf39f9623a908bf9c5634de11

Rename and cleanup follow-up for chunk synchronization

view details

Amy Sutedja

commit sha 9e981b17e9608d7fd285a24226494224edfea90b

Release workflow via Github Actions

view details

Amy Sutedja

commit sha d1553e5fffb25d479d361730bf7adc80f7da4a7d

Change url assert in test_package

view details

Amy Sutedja

commit sha d60a22c087ee1dfb8ad8b1ed5dbe866c963c69b0

Merge branch 'master' of github.com:splunk/splunk-sdk-python into develop

view details

David Poncelow

commit sha 6a9c77b969d1a29f435837469c17b915f0c80065

a test to confirm errors in searchcommands with multibyte data

view details

Amy Sutedja

commit sha 0780fc1878e2de0effd0bbfaa45a963a2c73b4b6

Fix for multibyte inputs to custom search commands

view details

Amy Sutedja

commit sha 253784c6f7b918bbc8ef02d9a8358f0866756087

Multibyte test cleanup

view details

Amy Sutedja

commit sha 8dec1678e4e1643580c63bf4a961ad0abe41c686

Cleaner naming and semantics for custom search command input streams

view details

push time in 9 days

startednextapps-de/flexsearch

started time in 11 days

startedPaddlePaddle/PaddleOCR

started time in 14 days

startedflowingis/formazione

started time in 14 days

startedobsei/obsei

started time in 17 days

PR opened viebel/klipse

README: fix skulpt url
+1 -1

0 comment

1 changed file

pr created time in a month

push eventxrmx/klipse

Riccardo Magliocchetti

commit sha c611573e96167f5136bfe65137fcea97fa634c10

README: fix skulpt url

view details

push time in a month

fork xrmx/klipse

Klipse is a JavaScript plugin for embedding interactive code snippets in tech blogs.

http://blog.klipse.tech/

fork in a month

startedmarceloprates/prettymaps

started time in a month

issue commentxrmx/uwsgitop

Cannot get memory used report

Do you have any request? Otherwise numbers are not updated. If numbers are at 0 there's not much we can do from the uwsgitop side.

lucifer-wsp

comment created time in a month

issue commentxrmx/uwsgitop

Cannot get memory used report

Please follow instructions in this repository README

lucifer-wsp

comment created time in a month

create barnchxrmx/farmacie-tamponi-prezzi-calmierati

branch : main

created branch time in 2 months

created repositoryxrmx/farmacie-tamponi-prezzi-calmierati

created time in 2 months

pull request commentgit-l10n/git-po

l10n: it.po: fixup typo

@jiangxin PR has been sitting there since last may https://github.com/AlessandroMenti/git-po/pull/1

xrmx

comment created time in 2 months

PR opened git-l10n/git-po

l10n: it.po: fixup typo

Signed-off-by: Riccardo Magliocchetti riccardo.magliocchetti@gmail.com

+2 -2

0 comment

1 changed file

pr created time in 2 months

push eventxrmx/git-po

Derrick Stolee

commit sha 2782db3eed808c2a5097ccd5af813d3338c5f313

test-tool: don't force full index We will use 'test-tool read-cache --table' to check that a sparse index is written as part of init_repos. Since we will no longer always expand a sparse index into a full index, add an '--expand' parameter that adds a call to ensure_full_index() so we can compare a sparse index directly against a full index, or at least what the in-memory index looks like when expanded in this way. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 6863df355038dd2d30ac9899bdb304d8a57523af

unpack-trees: ensure full index The next change will translate full indexes into sparse indexes at write time. The existing logic provides a way for every sparse index to be expanded to a full index at read time. However, there are cases where an index is written and then continues to be used in-memory to perform further updates. unpack_trees() is frequently called after such a write. In particular, commands like 'git reset' do this double-update of the index. Ensure that we have a full index when entering unpack_trees(), but only when command_requires_full_index is true. This is always true at the moment, but we will later relax that after unpack_trees() is updated to handle sparse directory entries. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 836e25c51b20c1f1d122dc17a1c57dad15ff5854

sparse-checkout: hold pattern list in index As we modify the sparse-checkout definition, we perform index operations on a pattern_list that only exists in-memory. This allows easy backing out in case the index update fails. However, if the index write itself cares about the sparse-checkout pattern set, we need access to that in-memory copy. Place a pointer to a 'struct pattern_list' in the index so we can access this on-demand. This will be used in the next change which uses the sparse-checkout definition to filter out directories that are outside the sparse cone. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha cd42415fb4c9680f308ebf8f9f85ba90ae6014be

sparse-index: add 'sdir' index extension The index format does not currently allow for sparse directory entries. This violates some expectations that older versions of Git or third-party tools might not understand. We need an indicator inside the index file to warn these tools to not interact with a sparse index unless they are aware of sparse directory entries. Add a new _required_ index extension, 'sdir', that indicates that the index may contain sparse directory entries. This allows us to continue to use the differences in index formats 2, 3, and 4 before we create a new index version 5 in a later change. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 6e773527b6b03976cefbb0f9571bd40dd5995e6c

sparse-index: convert from full to sparse If we have a full index, then we can convert it to a sparse index by replacing directories outside of the sparse cone with sparse directory entries. The convert_to_sparse() method does this, when the situation is appropriate. For now, we avoid converting the index to a sparse index if: 1. the index is split. 2. the index is already sparse. 3. sparse-checkout is disabled. 4. sparse-checkout does not use cone mode. Finally, we currently limit the conversion to when the GIT_TEST_SPARSE_INDEX environment variable is enabled. A mode using Git config will be added in a later change. The trickiest thing about this conversion is that we might not be able to mark a directory as a sparse directory just because it is outside the sparse cone. There might be unmerged files within that directory, so we need to look for those. Also, if there is some strange reason why a file is not marked with CE_SKIP_WORKTREE, then we should give up on converting that directory. There is still hope that some of its subdirectories might be able to convert to sparse, so we keep looking deeper. The conversion process is assisted by the cache-tree extension. This is calculated from the full index if it does not already exist. We then abandon the cache-tree as it no longer applies to the newly-sparse index. Thus, this cache-tree will be recalculated in every sparse-full-sparse round-trip until we integrate the cache-tree extension with the sparse index. Some Git commands use the index after writing it. For example, 'git add' will update the index, then write it to disk, then read its entries to report information. To keep the in-memory index in a full state after writing, we re-expand it to a full one after the write. This is wasteful for commands that only write the index and do not read from it again, but that is only the case until we make those commands "sparse aware." We can compare the behavior of the sparse-index in t1092-sparse-checkout-compability.sh by using GIT_TEST_SPARSE_INDEX=1 when operating on the 'sparse-index' repo. We can also compare the two sparse repos directly, such as comparing their indexes (when expanded to full in the case of the 'sparse-index' repo). We also verify that the index is actually populated with sparse directory entries. The 'checkout and reset (mixed)' test is marked for failure when comparing a sparse repo to a full repo, but we can compare the two sparse-checkout cases directly to ensure that we are not changing the behavior when using a sparse index. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha f442313e2e7a2ebf592a5943d4d4392e88153484

submodule: sparse-index should not collapse links A submodule is stored as a "Git link" that actually points to a commit within a submodule. Submodules are populated or not depending on submodule configuration, not sparse-checkout. To ensure that the sparse-index feature integrates correctly with submodules, we should not collapse a directory if there is a Git link within its range. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 13e133124728736db605e8ad6d2a844c380cb735

unpack-trees: allow sparse directories The index_pos_by_traverse_info() currently throws a BUG() when a directory entry exists exactly in the index. We need to consider that it is possible to have a directory in a sparse index as long as that entry is itself marked with the skip-worktree bit. The 'pos' variable is assigned a negative value if an exact match is not found. Since a directory name can be an exact match, it is no longer an error to have a nonnegative 'pos' value. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 0938e6ff552510d4e6e495f062a9fab3e932178a

sparse-index: check index conversion happens Add a test case that uses test_region to ensure that we are truly expanding a sparse index to a full one, then converting back to sparse when writing the index. As we integrate more Git commands with the sparse index, we will convert these commands to check that we do _not_ convert the sparse index to a full index and instead stay sparse the entire time. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 58300f4743231724686d9ddf481aeefa4f90d2f7

sparse-index: add index.sparse config option When enabled, this config option signals that index writes should attempt to use sparse-directory entries. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 122ba1f7b52612e197db76aded1f9681b80f3085

sparse-checkout: toggle sparse index from builtin The sparse index extension is used to signal that index writes should be in sparse mode. This was only updated using GIT_TEST_SPARSE_INDEX=1. Add a '--[no-]sparse-index' option to 'git sparse-checkout init' that specifies if the sparse index should be used. It also updates the index to use the correct format, either way. Add a warning in the documentation that the use of a repository extension might reduce compatibility with third-party tools. 'git sparse-checkout init' already sets extension.worktreeConfig, which places most sparse-checkout users outside of the scope of most third-party tools. Update t1092-sparse-checkout-compatibility.sh to use this CLI instead of GIT_TEST_SPARSE_INDEX=1. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha dcc5fd5fd26b71d75f9e70abd0e09e553b5f40ca

sparse-checkout: disable sparse-index We use 'git sparse-checkout init --cone --sparse-index' to toggle the sparse-index feature. It makes sense to also disable it when running 'git sparse-checkout disable'. This is particularly important because it removes the extensions.sparseIndex config option, allowing other tools to use this Git repository again. This does mean that 'git sparse-checkout init' will not re-enable the sparse-index feature, even if it was previously enabled. While testing this feature, I noticed that the sparse-index was not being written on the first run, but by a second. This was caught by the call to 'test-tool read-cache --table'. This requires adjusting some assignments to core_apply_sparse_checkout and pl.use_cone_patterns in the sparse_checkout_init() logic. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 2de37c536d54a28a032491ad4ef97632ef6ab836

cache-tree: integrate with sparse directory entries The cache-tree extension was previously disabled with sparse indexes. However, the cache-tree is an important performance feature for commands like 'git status' and 'git add'. Integrate it with sparse directory entries. When writing a sparse index, completely clear and recalculate the cache tree. By starting from scratch, the only integration necessary is to check if we hit a sparse directory entry and create a leaf of the cache-tree that has an entry_count of one and no subtrees. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha 9ad2d5ea71d1470c2fd68b76c36b2ced3612cde3

sparse-index: loose integration with cache_tree_verify() The cache_tree_verify() method is run when GIT_TEST_CHECK_CACHE_TREE is enabled, which it is by default in the test suite. The logic must be adjusted for the presence of these directory entries. For now, leave the test as a simple check for whether the directory entry is sparse. Do not go any further until needed. This allows us to re-enable GIT_TEST_CHECK_CACHE_TREE in t1092-sparse-checkout-compatibility.sh. Further, p2000-sparse-operations.sh uses the test suite and hence this is enabled for all tests. We need to integrate with it before we run our performance tests with a sparse-index. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Derrick Stolee

commit sha c9e40ae8ec41c5566e5849a87c969fa81ef49fcd

p2000: add sparse-index repos p2000-sparse-operations.sh compares different Git commands in repositories with many files at HEAD but using sparse-checkout to focus on a small portion of those files. Add extra copies of the repository that use the sparse-index format so we can track how that affects the performance of different commands. At this point in time, the sparse-index is 100% overhead from the CPU front, and this is measurable in these tests: Test --------------------------------------------------------------- 2000.2: git status (full-index-v3) 0.59(0.51+0.12) 2000.3: git status (full-index-v4) 0.59(0.52+0.11) 2000.4: git status (sparse-index-v3) 1.40(1.32+0.12) 2000.5: git status (sparse-index-v4) 1.41(1.36+0.08) 2000.6: git add -A (full-index-v3) 2.32(1.97+0.19) 2000.7: git add -A (full-index-v4) 2.17(1.92+0.14) 2000.8: git add -A (sparse-index-v3) 2.31(2.21+0.15) 2000.9: git add -A (sparse-index-v4) 2.30(2.20+0.13) 2000.10: git add . (full-index-v3) 2.39(2.02+0.20) 2000.11: git add . (full-index-v4) 2.20(1.94+0.16) 2000.12: git add . (sparse-index-v3) 2.36(2.27+0.12) 2000.13: git add . (sparse-index-v4) 2.33(2.21+0.16) 2000.14: git commit -a -m A (full-index-v3) 2.47(2.12+0.20) 2000.15: git commit -a -m A (full-index-v4) 2.26(2.00+0.17) 2000.16: git commit -a -m A (sparse-index-v3) 3.01(2.92+0.16) 2000.17: git commit -a -m A (sparse-index-v4) 3.01(2.94+0.15) Note that there is very little difference between the v3 and v4 index formats when the sparse-index is enabled. This is primarily due to the fact that the relative file sizes are the same, and the command time is mostly taken up by parsing tree objects to expand the sparse index into a full one. With the current file layout, the index file sizes are given by this table: | full index | sparse index | +-------------+--------------+ v3 | 108 MiB | 1.6 MiB | v4 | 80 MiB | 1.2 MiB | Future updates will improve the performance of Git commands when the index is sparse. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

view details

Junio C Hamano

commit sha 9210c68d2af84d869f1635efe9a2092578653297

Merge branch 'mt/checkout-remove-nofollow' When "git checkout" removes a path that does not exist in the commit it is checking out, it wasn't careful enough not to follow symbolic links, which has been corrected. * mt/checkout-remove-nofollow: checkout: don't follow symlinks when removing entries symlinks: update comment on threaded_check_leading_path()

view details

Junio C Hamano

commit sha aab55b1d6e1541f70ff364ce7b2c98f6a8157084

Merge branch 'bs/asciidoctor-installation-hints' Doc update. * bs/asciidoctor-installation-hints: INSTALL: note on using Asciidoctor to build doc

view details

Junio C Hamano

commit sha ad16f748f22c82d096664f15f1a1c7fcc361cfe3

Merge branch 'ab/read-tree' Code simplification by removing support for a caller that is long gone. * ab/read-tree: tree.h API: simplify read_tree_recursive() signature tree.h API: expose read_tree_1() as read_tree_at() archive: stop passing "stage" through read_tree_recursive() ls-files: refactor away read_tree() ls-files: don't needlessly pass around stage variable tree.c API: move read_tree() into builtin/ls-files.c ls-files tests: add meaningful --with-tree tests show tests: add test for "git show <tree>"

view details

Junio C Hamano

commit sha b2309ad822500ba2c1088800b369851fad261e77

Merge branch 'ab/diff-no-index-tests' More test coverage over "diff --no-index". * ab/diff-no-index-tests: diff --no-index tests: test mode normalization diff --no-index tests: add test for --exit-code

view details

Junio C Hamano

commit sha 501380286295cac300dae86c3f0f6c10ff34b767

Merge branch 'cs/http-use-basic-after-failed-negotiate' When accessing a server with a URL like https://user:pass@site/, we did not to fall back to the basic authentication with the credential material embedded in the URL after the "Negotiate" authentication failed. Now we do. * cs/http-use-basic-after-failed-negotiate: remote-curl: fall back to basic auth if Negotiate fails

view details

Junio C Hamano

commit sha dc2a073036ccbd3d8aa707b98e996b6fb9bcd751

Merge branch 'ab/remove-rebase-usebuiltin' Remove the final hint that we used to have a scripted "git rebase". * ab/remove-rebase-usebuiltin: rebase: remove transitory rebase.useBuiltin setting & env

view details

push time in 2 months

issue closedxrmx/un-corso-django

2 errori riscontrati con dei comandi per il prompt.

Al capitolo 5.5 ho provato a utilizzare il comando touch su win10 ma esso non funziona, e sulla lista dei comandi non lo trovo quindi ho optato per creare il file a mano. Un altro errore che capita è provando a scrivere sul prompt corsi/tests ,questo perchè su win10 va usato \ invece di /. Sono piccolezze lo so ma lo dico per correttezza,

closed time in 2 months

ChristianMascolo

issue commentxrmx/un-corso-django

2 errori riscontrati con dei comandi per il prompt.

Dice bene @sanjioh, chiudo la issue. Grazie.

ChristianMascolo

comment created time in 2 months

startederikgrinaker/toydb

started time in 2 months

push eventunbit/uwsgi-docs

Riccardo Magliocchetti

commit sha 2337d88b526ac8a1c57e60a94a339d9325f5a040

Update Changelog for unreleased 2.0.20

view details

push time in 2 months

push eventunbit/uwsgi

ilrico

commit sha 4ab480695703ddaf27534dc5d5e20699b766db68

take into account new naming for LIBPL since python 3.6 related to issues 2270 and 2293

view details

Cyrille Pontvieux

commit sha 795337433fe79bfe97a903c19c1bed1b7e1a572d

Allow to compile on Python versions with more that two digits (Python 3.10)

view details

Luciano Rocha

commit sha 61ca0bffa5a1aed02b48865f9eab110049c8b662

allow 'iteration' option to uwsgi::add_rb_timer The caller can now specify a custom iteration value when setting an rb_timer. The default is still zero if no third parameter is passed, i.e.: uwsgi::add_rb_timer($signal, $interval); Is the same as: uwsgi::add_rb_timer($signal, $interval, 0);

view details

push time in 2 months

push eventxrmx/uwsgi

Riccardo Magliocchetti

commit sha 79b82b9bd277e4037ac432e1ed9bb52bf3e63ccc

ci: stop building python2.6 plugin Because it's not installable anymore. And it's 2021.

view details

Riccardo Magliocchetti

commit sha 73871abce61ba61c663a4636669edf9d28de8f22

Makefile: use python3 As it's a saner default in 2021.

view details

Riccardo Magliocchetti

commit sha f68ed41c55a46f3c369a551558b7a0905f8ecc34

Merge pull request #2274 from xrmx/drop-python26 Drop python26

view details

Krzysztof Warzecha

commit sha 5b9386374a5175e251b0375a5fb3bc69cc96defc

plugins/php/session.c: for php7 return failures only on failure

view details

Riccardo Magliocchetti

commit sha c87585769c8a024b09b3c2896ce33cb6bc3ccd1b

plugins/php: drop PHP < 7 code Not supported upstream since years.

view details

Riccardo Magliocchetti

commit sha 436e6bdd99b0b5de74aac3f78c2dfa405e553b16

plugins/php: remove TSRMLS_* macros They are gone in PHP 8 and were inert since PHP 7.

view details

Riccardo Magliocchetti

commit sha 4492b021958670745a59e5c92425c6ea7ac9d52e

plugins/php: fixup sapi_uwsgi_log_message signature for PHP 8

view details

Antonio Cuni

commit sha 6c82be6d855599f446e6a687a4ef89dcac61eb7c

fix segfaults when using --wsgi-env-behavior=holy. PyTuple_SetItem does NOT increment the item, so we need to do it explicitly. Without this, then env gets a negative refcnt during the deallocation of async_args, with all kinds of funny behaviors.

view details

Serge Bazanski

commit sha fde2100fc194ca0ec7384ba68e74ce7047c1d3e6

core, proto: replace uwsgi.h system includes This replaces all `#include <uwsgi.h>` in core/ and proto/ with `#include "uwsgi.h"`. This is to make it easier to build uWSGI with build systems that are more opinonated about local-vs-system include directories (eg. Bazel), and is without detriment to uWSGI itself (at least as far as I can tell).

view details

László Károlyi

commit sha ad65d86c116650df0c108ea1d72487219b0418b1

plugins/gevent: fix compilation with clang11 plugins/gevent/gevent.c[thread 11]: 392:21: error: cast to smaller integer type 'PyGILState_STATE' from 'void *' [-Werror,-Wvoid-pointer-to-enum-cast] PyGILState_Release((PyGILState_STATE) pthread_getspecific(up.upt_gil_key)); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fix #2238

view details

Riccardo Magliocchetti

commit sha 154307d7d8cd9c189cec29bde8aec7b13635bffb

plugins: use PyObject_CallObject() instead of PyEval_CallObject() Reference: https://bugs.python.org/issue29548

view details

Riccardo Magliocchetti

commit sha 3d6f200664ff5de8f820f996305b574d9fd5a745

plugins/python: don't call PyEval_InitThreads on python >= 3.7 As it's already called in Py_Initialize() there.

view details

Riccardo Magliocchetti

commit sha fe851f155f6c271fee18f0f83ac4e6bae9347b05

plugins/python: use Py_CompileString Instead of the deprecated PyParser_SimpleParseString, PyParser_SimpleParseFile and PyNode_Compile. While at it fixup a possible null pointer dereference when uwsgi_open_and_read returns an empty string. See https://bugs.python.org/issue40939

view details

Delena Malan

commit sha 88741d216fe15d69998bc5548db8c4e420070fdf

Log SIGINT/SIGTERM triggered kill_them_all

view details

Adrian

commit sha 66dd6c9734386db90860291b2a74d08420b9b533

Add trove classifier for Python 3.9

view details

Riccardo Magliocchetti

commit sha 181fe14c1be26fd74b37fdd888837f8ab0ddf19c

cron: log signal dispatching from registered cron handler

view details

Riccardo Magliocchetti

commit sha f8a1edc05415a39fb9f5612df2b6e334b722da80

core/cron: support 7 as weekday as an alias for sunday To match crontab behaviour.

view details

Étienne H

commit sha 11644f59393b5c698d93c83ecc4a08e19809dd4b

plugins/http: document http-timeout default of 60 seconds Refs #2264

view details

Unbit

commit sha c13190c633eaca51625f20abc8334f4c36d71ffe

Add options to override python sys.executable By passing as py-executable argument. Fix #670 Backported from b6308cae818dab78da5f51eae8c903b6e2122b7a

view details

ilrico

commit sha 4ab480695703ddaf27534dc5d5e20699b766db68

take into account new naming for LIBPL since python 3.6 related to issues 2270 and 2293

view details

push time in 2 months

startedzhenghaoz/gorse

started time in 2 months

startedfoniod/redbpf

started time in 2 months

issue commentunbit/uwsgi

Possible RCE when using persistent mode (--puwsgi-socket)

@tacbliw Possibly not the best way to report an RCE :sweat:

tacbliw

comment created time in 3 months