text:
git: blame current file - ignore uncommitted changes

One scenario that I frequently end up in, is that I start to edit some code, then realize that I need to understand the origin of the code better, so I do a git blame to find out who was there before me, and what issue they were working on.
At this point, though, git blame will include my local changes, and therefore tell me that I was the one touching the code last.
Is it possible to get an option to ignore uncommitted changes when doing the blame?
Would it even be possible to have a 'history walker' so that we could blame the same file, but the previous version of it?
Another option would be to have 'blame' as an option when selecting a version from the log.
git: log current file -> [select a version] -> blame

Totalt irrelevant.
Hei hei nordman :)

authors: stoivo vegar

repo: divmain/GitSavvy


text:
importers: filter out empty attrsets

Allows you to have arbitrary folders that only get picked up if .nix files are in there. This could be useful for a folder dedicated to contains patches. And generally improves safety of the now fully recursive importers.
I decided to put this in rakeLeaves, since it makes no sense to rake pointless folders and the change propagates to all importers.

bors try

Do I see correctly this would prevent:
./a/b.foo

from getting picked up?

Yes those would have ended up as:
a = { };

or
a = { b = { }; }

Which I think actively hurts more than helps. Will add test cases now.

bors try

bors r+
Nice catch!

source: gharchive/pull-request

repo: divnix/digga

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 ArtChart is down

In 91e78da, ArtChart (https://artchart.net/en) was down:

HTTP code: 504
Response time: 15965 ms

Resolved: ArtChart is back up in 5953d12 after 4 minutes.

source: gharchive/issue

repo: divtiply/artupptime


text:
🛑 Polswiss Art is down

In 19e6272, Polswiss Art (https://www.polswissart.pl/pl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Polswiss Art is back up in 5180bdb after 12 minutes.


text:
Handle sPoNgEbOb case

The pathological case of someone arbitrarily capitalising chunks of words should be handled properly.

Added in most recent commit.

repo: divvun/divvunspell


text:
Emby doesnt play a single file

So moved a few files into teldrive, so far so good, emby cant play them, all im getting are the errors below:
r0gu3@server3:/etc/systemd/system$ sudo systemctl status teldrive_vfs.service
● teldrive_vfs.service - Rclone VFS Mount
Loaded: loaded (/etc/systemd/system/teldrive_vfs.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2023-12-03 21:54:09 CET; 43s ago
Process: 12080 ExecStop=/bin/fusermount -uz /mnt/teldrive (code=exited, status=0/SUCCESS)
Process: 12082 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
Main PID: 12154 (rclone)
Status: "[21:54] vfs cache: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)"
Tasks: 12 (limit: 4915)
CGroup: /system.slice/teldrive_vfs.service
└─12154 /usr/bin/rclone mount --user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.70 --config=/home/r0gu3/.config/rclone/rclone.conf --all
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: too many errors 11/10: last error: vfs reader: failed to write to cache file: HTTP error 416 (
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: failed to kick waiters: vfs reader: failed to write to cache file: HTTP error 416 (416 Request
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: failed to _ensure cache vfs reader: failed to write to cache file: HTTP error 416 (416 Request
Dec 03 21:54:53 server3 rclone[12154]: IO error: vfs reader: failed to write to cache file: HTTP error 416 (416 Requested Range Not Satisfiable) returned body: "invalid range: failed to overlap\n"
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: downloader: error count now 12: vfs reader: failed to write to cache file: HTTP error 416 (416
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: failed to download: vfs reader: failed to write to cache file: HTTP error 416 (416 Requested R
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: too many errors 12/10: last error: vfs reader: failed to write to cache file: HTTP error 416 (
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: failed to kick waiters: vfs reader: failed to write to cache file: HTTP error 416 (416 Request
Dec 03 21:54:53 server3 rclone[12154]: Media/Filme.Romanesti/Queen.Marie.of.Romania.2019.1080p.AMZN.WEB-DL.DDP.5.1.H.264-SPWEB.mkv: vfs cache: failed to _ensure cache vfs reader: failed to write to cache file: HTTP error 416 (416 Request
Dec 03 21:54:53 server3 rclone[12154]: IO error: vfs reader: failed to write to cache file: HTTP error 416 (416 Requested Range Not Satisfiable) returned body: "invalid range: failed to overlap\n"
I am on the latest teldrive and did the database update on neon

Facing the same issue myself, all videos play fine in teldrive web ui but nothing plays in emby. I am gonna test with jellyfin too just in case to confirm before concluding that its a streaming issue with rclone mount only

Facing the same issue myself, all videos play fine in teldrive web ui but nothing plays in emby. I am gonna test with jellyfin too just in case to confirm before concluding that its a streaming issue with rclone mount only

You are lucky, i just uploaded files that play just fine locally with emby, they dont play at all in teldrive ui; I have never made it work to stream from teldrive into emby; im not sure if this is something to do with teldrive or how i made the configs to be honest.

Oh ? What flags are required if you dont mind ?

rclone mount teldrive: /mnt/rclone --vfs-cache-mode=full  -vfs-cache-max-age=72h --vfs-cache-max-size=200G
This should be fine

Thank you very much, i will test that right away.

@xd003 i cant get it to work can u help me?


text:
Enhance home page and add review page

please assign this to me under hacktoberfest

@Sahoobarsharani sure

@Sahoobarsharani any updates ? Because we are getting many PRs and old issues and stale PRs are being closed

yes I'm in the middle of it.

okay

authors: Sahoobarsharani divyanshudhruv

repo: divyanshudhruv/Minifolio


text:
Fix glyphicon display for generic-lookup

Fixes issue #214.

Closing, and going to recreate not based on my master branch.

license_source: bigquery


text:
Remove debug print

Description
Port changes in #6791 as aggreed on the issue
Related resources

#6791

Checklist

[x] I have opened this pull request against develop
[ ] I have updated the CHANGELOG.rst
[ ] I have added or modified the tests when changing logic

Coverage remained the same at 78.215% when pulling dd7bda3b19d43c6f40cbe1a02eef10714f064870 on yakky:merge/6791 into 4d75b926fda163e476d3af3a7a534276429d66d6 on divio:develop.

@FinalAngel @Aiky30 could you restart the failed travis task? failure seem more random than related to this, and apparentyl I can't restart tasks on travis (probably due to the org change)

@yakky @FinalAngel I don't have the access to rerun this test I'm afraid. I don't think I was ever able to in Travis, I could in Circle CI.

@yakky @Aiky30 you may need to re-trigger the build. They should no go through the django-cms organisation (which should allow you to restart the builds)

@FinalAngel forced a push to retrigger the build. I confirm that I can now cancel / retry builds on travis

Needs bringing up to date and then it's ready to come in.

@Aiky30 sorry I missed your comment
Changelog entry added

@Aiky30 conflict fixed

authors: Aiky30 FinalAngel coveralls yakky

repo: django-cms/django-cms


text:
Don't queue objects that don't have a SearchIndex

This just needlessly bloats up the queue and spams with errors messages like "index not found".. no need for all this.
Cleaned branch from https://github.com/django-haystack/queued_search/pull/11
Apologies about the previous mess.

boo, this was a really simple and easy fix..


text:
Probes don't pick up 500 error (caused by psycopg2)

On a Django 2.2 project there was an update of psycopg2, which caused a known error. This resulted in 500-errors when accessing the website. The project has amongst others two django deployments, that use django-hurricane with following command:
python manage.py serve
                     --static
                     --port 8155
                     --check-migrations
                     --command 'migrate'
                     --command 'collectstatic --no-input'

The probes didn't realize the error and the pods became alive and ready.

I'll investigate some more as to what is actually causing this issue. It seems like no real database connection is made during the probes.

Is this still a thing with hurricane 1.0.0?

I keep in mind to test that when I have the opportunity.

In the meantime, did you have this "opportunity"? 💯

No...

authors: Schille tschale

repo: django-hurricane/django-hurricane


text:
Unable to run django oscar through docker

Found a bug? Please fill out the sections below.
Issue Summary
I am trying to run official django oscar docker image but not getting any clue. Please help me out.
A summary of the issue.

Hi there. We use Github only for managing bugs and feature requests, and not for support. We recommend that you ask for help on Stack Overflow using the django-oscar tag, or joining our slack workspace and asking a question there. Thanks.

@solarissmoke Hope you are doing well. As you have suggested to me I have tried several times to ask the question on StackOverflow but not even got any attention. I have also tried to join your given slack channel but that gives me 504 error. Can you suggest any better option, please? Thank you.

repo: django-oscar/django-oscar


text:
Custom error reporter

Would you be open to adding the ability to pass in the custom error reporting class directly instead of having to use the entry_points / extras approach? I'm not suggesting replacing it, just adding direct reference of a simple class as well. It would make internal error reporting systems much easier to implement.

Seconded.
If we could define something like this, passing a dotted path to a reporting class, it might simplify adding local reporting classes.
Q_CLUSTER = {
    ...
    "error_reporting": {
        "myapp.tasks.CustomReporter": {
            # kwargs
        }
    }
}

Passing dotted paths to classes seems to align with how you can define classes for other Django settings like cache and database backends.
Hopefully that could co-exist with the existing entrypoints-based options.

I am not against this, but I am really backed up with work and I won't be able to get to this any time soon. If someone wants to make a PR, then I am happy to review.

Thanks for being open to the idea. I'm also a little swamped at the moment, but when time permits I'll give it a go.

@GDay So basically just something like this?
https://github.com/django-q2/django-q2/compare/master...oliverhaas:django-q2:feat/error-reporter-by-module-path
If the basic approach looks fine to you, I will add something to the docs, a simple test, and maybe better error handling for the import. Sometime until the end of the year is my plan, anyway.

authors: GDay ebaumgartner kevinob11 oliverhaas


text:
Add German translation

Including new date formats like dd.mm.YYYY and 23. for 23th etc.
Changes:

Adding translation strings in recurrence.js (day of month & date format for "until ...")
Creating new po/mo files (Dutch/French translations from @bheesink and @ollb were quite helpful as basis for translation)

Further contributions and improvements are always welcome. Keep up the nice work!

Hope the project is not dead, I would really appreciate some feedback.

Definitely not dead, sorry for the slow reply. I'll aim to take a look at
this today.
On 3 Dec 2016 9:03 p.m., "Denis Anuschewski" notifications@github.com
wrote:

Hope the project is not dead, I would really appreciate some feedback.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/django-recurrence/django-recurrence/pull/77#issuecomment-264665372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_7XSJWilggXaN1yDLwgHLkE6-gh96pks5rEdkigaJpZM4K45Jk
.

Glad to hear that!

Thanks @denisiko! The change looks good, so I've merged it. I'll wait a bit to see if any other pull requests come in over the next few weeks - if not, I'll get a release merged with it.

Nice! Hope someone can use it.

I checked, and we have a few things in 1.4.1 already, so hopefully @emperorcezar can push a release fairly soon (Adam - if it's easier feel free to just grant me access to PyPI so I can do it).

authors: denisiko dominicrodger

repo: django-recurrence/django-recurrence


text:
Suggestion: Add topics to this repo to make it more discoverable

I did a survey of feature flipper libraries recently, and django-waffle was not easy to come by. I'd suggest adding the "feature-flags" topic to this repo, so that others have an easier time finding it.

Done.

authors: brianpeiris clintonb

repo: django-waffle/django-waffle


text:
Refs #28814 -- Backport Python 3.7 compatibility to Django 1.11.x LTS

As requested in 931c60c5216bd71bc11f489e00e063331cf21f40 .

Looks good. MySQL GIS test failures aren't related.

buildbot, test on oracle.

authors: timgraham zyv

repo: django/django


text:
Fixed #30509 -- Various FileResponse fixes and changes

ticket 30509
Copying the ticket's description as well as my knowledge of GitHub's formatting allows me... :P
As I've mentioned in PR #11011 (of ticket 30196) I noticed a couple of issues with the way FileResponse is created (and other minor things), and in this ticket I'll try to list and fix them.
For initial clarity, this PR consists of 2 commits. The first is a set of tests, most of which show invalid behavior in some quite specific cases based on current code. The second contains my initial proposed fixes.

tests:

a. test_file_from_buffer_absolute_name:
test ends in an error, because set_headers() attempts to read the 'name' property if the filename (which can be overwritten by the custom filename) is recognized as an absolute path by os.path.
b. test_file_from_buffer_explicit_type1, test_file_from_buffer_explicit_type2:
of these 2, first test shows the way to explicitly set Content-Type header of the response, while the second shows that in a case that the set value matches the beginning of the default value ('text/html; charset=%s' % self.charset), it will consider that value as unset and proceed to read the content type from the file.
c. test_file_from_named_buffer1, test_file_from_named_buffer2:
tests show how you can easily 'fool' FileResponse into thinking it's dealing with an actual file, resulting in incorrect header values if such file exists (1) or an error if it doesn't (2).
d. test_file_from_disk_custom_name, test_file_from_disk_as_attachment_custom_name:
these are just 2 missing tests to check whether giving a file a custom name even works.

fixes:

a. ignored custom filename before setting Content-Length and changed the following condition a bit to fix 1.a. and the error case of 1.c.
b. added a self._default_content_type flag to HttpResponseBase.__init__() to mark that there was no content_type explicitly set, so it should be figured out from the file, if possible, to fix 1.b.
c.

added a way to tell the filelike object's size if it's neither a file nor has a getbuffer attribute, using .seek() and .tell() if they're available, and otherwise .read()
moved os.path.getsize path to be the worst-case-scenario, to avoid reading the same file from disk again when possible
that fixes the remaining problem found in 1.c..

d. moved encoding_map to initialize only when it's necessary.
e. changed set_headers() to _set_headers() to mark it as an internal function.
f. simplified the - IMO - unnecessarily detailed docs of FileResponse to just tell the user what do the parameters cause, instead of (almost) explaining what each line of code does - if the user wants to know which headers get what kind of values under which conditions they can just check the code, Python is nearly pseudocode anyway.

One thing i'm not sure about is if FileResponse should support reading filelikes from a different position than the beginning. If so, getting Content-Length would require a tiny change to accomodate a non-zero starting point, while otherwise it could use a filelike.seek(0) somewhere to be sure we're reading it from the very beginning.

Oh, from the failed checks i see that the Unix's named pipes have a seek attribute, but don't allow to actually use it... I'm writing it on Windows, so that one failing test case was being skipped, so i couldn't notice an issue with it.

What happens currently with regard to Content Length if we pass a non-seekable buffer? That should be an error right? Whilst we're here is it worth adding a suitable exception?

If that buffer has a getbuffer method, then it is being used. Otherwise, it seems to be the same case as these unseekable named pipes, and they simply end up not setting Content-Length at all - that's how it was since before i started playing with it. Can we even do anything about it?

Looking into these unseekable named pipes i noticed that they (like all IOBase-derived classes) have a seekable method, so i managed to simplify handling such cases.
Also while combining test_file_from_buffer_explicit_typeX and test_file_from_named_bufferX, i took the liberty of combining all test_file_from_disk_X and test_file_from_buffer_X into 2 large cases.
Because of the complexity of possible Content-Disposition values the new test_file_from_buffer_response contains a 3-way if-else, but i hope it's not a problem.

Conflict is due to #11676, which doesn't conflict only in code (doc, actually) but also in the idea.
In this PR i changed Content-Length calculation to end up with .seek(0) for seekable filelikes without getbuffer method, which partially contradicts with what was added in #11676 (that you have to .seek() yourself).
If i should instead seek back to the initial position of the cursor then it's not a problem, but if we agree that all buffers and files should be automatically seeked to 0, then #11676 would become completely incorrect and should be reverted (preferably before this gets pulled to avoid resolving conflicts).
With buffers currently the problem is that .getbuffer().nbytes returns the entire size of the buffer even if the cursor is anywhere else, so the size of read data may differ from Content-Length, so i think we should seek(0) them too. Or, instead, just use the tell/read&seek method there too.

Before i get on it, what should i do with objects that have the getbuffer method? As i wrote before, the behavior would be more accurate if i used tell-seek method on them too. Should that be the first checked option?

So the use case is, for example tailing a log file, or sending an audio from a point. The answer I want is the content length sent, not what else might be available, no?

So the use case is, for example tailing a log file, or sending an audio from a point. The answer I want is the content length sent, not what else might be available, no?

I agree, and seek-tell/read is the only way to do that AFAIK.
Now that i think about it, maybe with getbuffer we could do self['Content-Length'] = filelike.getbuffer().nbytes - filelike.tell(), but if tell isn't available then we're returning possibly incorrect values again.
Also suggestions how to shorten these lines in test cases so flake8 passes? Break lines? (where?) Shorten variables' names?

Try to isolate the exact case(s) we can't handle. Deal with the rest, then we can always acknowledge a know limitation in the remaining cases — maybe raise a warning so folks can do something different. (But I suspect no-one is using it that way...)
Break after the and

Raising a warning is done through checks.Warning()?
I asked about the lines in test_fileresponse.py, there's no and there (besides one comment).

Not sure if that's the best way, but it's a way.
Also i had to flip these levels of if statements before to save some lines, especially if i'm gonna add these warnings soon.

Yeah, i'm still up for that.

Can I get you to rebase and squash, and split the initial "we're just testing the existing behaviour" into separate commits first?

Do i understand you correctly that you want me to squash all of my test_fileresponse.py changes into a single commit, and all remaining changes into a second one? Kinda like i did with my first 2 commits in this PR (except there was no squashing required, obviously)?

there's a lot going on (maybe too much) in test_file_from_buffer_response

I am aware of that, but my idea was to easily check all (or, well, a couple of) possible combinations of used parameters, to prevent some specific combination of values from causing wrong results - for example using a filelike without name, while setting a custom name, could affect calculating Content-Length, despite there being no clear connection between the two.

Hi @ShingenPizza

Yeah, i'm still up for that.

Super.

Do i understand you correctly that you want me to squash all of my ...

No, sorry, I wasn't clear. What I mean is that we should add and merge all the "increasing coverage" tests first — i.e. the ones that would pass on master. (So for example the test_file_from_disk_response cases.)

...my idea was ...

Sure. But it's (practically) impossible to read the tests and work out which bit of logic is being tested where. The tests then don't really document the functionality, nor is it clear which behaviour is under test — they're approaching higher level integration tests, if that makes sense. Nothing wrong with that, except that it's really hard to see what's going on — hence this sitting unreviewed for so long.
I think to divide by header might be a good split. So tests for Content-Type, say. How does that sound to you? The goal here is coverage, but also clear, readable tests: it would be nice to open the test file and easily see what's going on: as it is, that's not currently the case. (As ever, there's no single right answer, but that's the goal — as long as we hit that, happy to follow your lead.)
Make sense?

Okay, sorry for the wait, but i was kinda overwhelmed with the idea of having to rework all those tests to check one header each.
So i did it eventually, and i hope i didn't accidentally forget any cases that i wanted to check.
So is it fine now?

Okay, so this is what was throwing errors before.
Couldn't see it before because the logs were gone.
Also i noticed that with this whole separating tests by header we're not really testing the actual response content much.

everything is green! may be ready for check in?

authors: ShingenPizza auvipy carltongibson


text:
Increased test coverage of django.utils.inspect.

The function is not used in django's code base.

@atombrella Thanks :+1: I added tests for inspect.func_accepts_kwargs().

authors: atombrella felixxm


text:
Refs #32381 -- Include number of rows matched in bulk_update() return value

Ticket #32381 -- Include number of rows matched in bulk_update() return value

[x] Implement the simplest approach (return the sum of its updates)
[x] Add documentation (bulk_update)
[x] Add documentation (changelogs)
[x] Discuss/resolve Tim McCurrach's duplicates problem
[x] Discuss/resolve Chris Jerdonek's future-proofing proposal

Oops! I might need help with this failing JavaScript test. Right now I have no clue what went wrong :(

Oops! I might need help with this failing JavaScript check. Right now I have no clue what went wrong :(

Don't worry, it's unrelated.

@diego-lima Do you have time to keep working on this?

@felixxm I've been on a tight schedule for the past month. I'll be able to return to this in two weeks.

Thanks, sounds good :+1:

Closing due to inactivity. Feel-free to open a new PR.

Superseded by #14559.

authors: diego-lima felixxm pope1ni


text:
Doc'd a precise exception type in Paginator.page() docs.

InvalidPage => EmptyPage

@sih4sing5hong5 Thanks :+1:


text:
Fixed #35273 -- Fixed rendering AdminFileWidget's attributes.

Trac ticket number

ticket-35273
Branch description
Provide a concise overview of the issue or rationale behind the proposed changes.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[x] For UI changes, I have attached screenshots in both light and dark modes.

@codingjoe Do you have time to keep working on this? If not, I can reorganize commits.

@codingjoe Thanks :+1:

@codingjoe Thanks :+1:

Thanks @felixxm I appreciate the help <3

authors: codingjoe felixxm


text:
Fixed #24072 -- Added FileResponse

https://code.djangoproject.com/ticket/24072

Nice patch!

Ok, I just pushed a new commit which should address all of the current comments.

merged in 3d2cae0896ee8026d1c2c5d31e4c4c8f74f2fef4, thanks.

authors: claudep collinanderson timgraham


text:
fix ipv6 validator: check address for valid symbols first

I've got an issue when user posted an IPv6 address with spaces right after a colon (like this: fe80::2000:f8ff: fe21:67cf) and Django passed that value to database and user got DataError exception. This fix prevents the issue.

Thanks for the patch. A Trac ticket and a regression test is is also required.

Closing due to lack of follow up.

authors: name-no timgraham


text:
Refs #25588 -- Fixed GDAL dependency in spatial lookups.

I moved the attempt to convert to raster into a separate method that is only called if GDAL is installed.
Is there a way to create a regression test for this? I don't know how to mock a system that does not have gdal installed.

I don't think any tests are needed. This works besides the test failure reported by Jenkins and a few other issues, at least some of which don't appear to be related to this ticket:
======================================================================
ERROR: test_srid_option (gis_tests.geoapp.test_serializers.GeoJSONSerializerTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/media/sf_django/tests/gis_tests/geoapp/test_serializers.py", line 85, in test_srid_option
    geojson = serializers.serialize('geojson', City.objects.all().order_by('name'), srid=2847)
  File "/media/sf_django/django/core/serializers/__init__.py", line 129, in serialize
    s.serialize(queryset, **options)
  File "/media/sf_django/django/core/serializers/base.py", line 96, in serialize
    self.end_object(obj)
  File "/media/sf_django/django/core/serializers/json.py", line 61, in end_object
    json.dump(self.get_dump_object(obj), self.stream,
  File "/media/sf_django/django/contrib/gis/serializers/geojson.py", line 58, in get_dump_object
    'Unable to convert geometry to SRID %s when GDAL is not installed.' % self.srid
django.core.serializers.base.SerializationError: Unable to convert geometry to SRID 2847 when GDAL is not installed.

======================================================================
ERROR: test06_f_expressions (gis_tests.relatedapp.tests.RelatedGeoModelTest)
Testing F() expressions on GeometryFields.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/media/sf_django/tests/gis_tests/relatedapp/tests.py", line 155, in test06_f_expressions
    c2 = c1.transform(2276, clone=True)
  File "/media/sf_django/django/contrib/gis/geos/geometry.py", line 524, in transform
    raise GEOSException("GDAL library is not available to transform() geometry.")
django.contrib.gis.geos.error.GEOSException: GDAL library is not available to transform() geometry.

======================================================================
FAIL: test_add_raster_field_on_db_without_raster_support (gis_tests.gis_migrations.test_operations.OperationTests)
----------------------------------------------------------------------
django.core.exceptions.ImproperlyConfigured: RasterField requires GDAL.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/media/sf_django/django/test/testcases.py", line 1092, in skip_wrapper
    return test_func(*args, **kwargs)
  File "/media/sf_django/tests/gis_tests/gis_migrations/test_operations.py", line 134, in test_add_raster_field_on_db_without_raster_support
    False, fields.RasterField
  File "/usr/lib/python3.5/contextlib.py", line 77, in __exit__
    self.gen.throw(type, value, traceback)
  File "/media/sf_django/django/test/testcases.py", line 604, in _assert_raises_message_cm
    self.assertIn(expected_message, str(cm.exception))
AssertionError: 'Raster fields require backends with raster support.' not found in 'RasterField requires GDAL.'

======================================================================
FAIL: test_create_raster_model_on_db_without_raster_support (gis_tests.gis_migrations.test_operations.OperationTests)
----------------------------------------------------------------------
django.core.exceptions.ImproperlyConfigured: RasterField requires GDAL.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/media/sf_django/django/test/testcases.py", line 1092, in skip_wrapper
    return test_func(*args, **kwargs)
  File "/media/sf_django/tests/gis_tests/gis_migrations/test_operations.py", line 123, in test_create_raster_model_on_db_without_raster_support
    self.set_up_test_model(True)
  File "/usr/lib/python3.5/contextlib.py", line 77, in __exit__
    self.gen.throw(type, value, traceback)
  File "/media/sf_django/django/test/testcases.py", line 604, in _assert_raises_message_cm
    self.assertIn(expected_message, str(cm.exception))
AssertionError: 'Raster fields require backends with raster support.' not found in 'RasterField requires GDAL.'

I fixed the test failures from Jenkins, and added @skipUnless(HAS_GDAL) decorators to the two raster support db tests. I suspect these would have failed on a system with PostGIS and without GDAL even before adding the lookups.
The other two tests do not seem to be related to the ticket.

authors: timgraham yellowcap


text:
Refs #25854 -- Completed a RequestContext docs example.

https://code.djangoproject.com/ticket/25854

Might be worth storing the Template instance in a more meaningful variable name while you're at it. Otherwise LGTM.

authors: charettes timgraham


text:
feat: Make django logo clickable. onClick redirect to homepage

Closes #240
Changes
Make top django logo clickable.
Type of change

[x ] Feature update

Author Checklist

[ x] Code has been commented, particularly in hard-to-understand areas
[ x] Changes generate no new warnings
[ x] Vital changes have been captured in unit and/or integration tests
[ x] New and existing unit tests pass locally with my changes
[x ] Documentation has been extended, if necessary
[x ] Merging to main from fork:Suraj1089/djangoindia.org

LGTM ! Thanks @Suraj1089 @Saurabhsharma884  👍


text:
Feature request: Standalone/Server mode

Hello,
Thanks a lot, portal is a great addition to the Clojure ecosystem.
I wonder if that was possible to create a standalone server mode, and clients could connect to it by sending request to the server.  In my mind , you could start a server portal with babashka in a a given port (say 1664), then any client (clj/CLJS) could send edn data to the server through http request. Optimally, a tap register function would be provided so that user just have to provide the port of the server.
This would disentangle portal from the client process and ease the integration with other tools (such as emacs) and shadow-CLJS/hot reloading) and ithe workflow would then resemble to the nrepl/socket repl.
An example of such implementation is the shadow-CLJS inspect server.
Best regards,
David

Hi @davidpham87, thanks for the kind words!
Portal could provide a client API but it would provide less functionality since it wouldn't have access to runtime objects. I added https://github.com/djblue/portal/commit/0d39d476ef4203292871b6b0ab89c57a6112e6a2 as an example of what could be done currently with portal. Is this kind of what you were thinking?

Hi @djblue,
Thanks a lot for the swift answer! Yes, this is what I have been thinking about!
As for your comment, I might be using clojure in the wrong way, but I try to code as much as possible with data, and if I need to introspect an object, I try to convert it to a hash-map before I tap it.
In terms of ergonomics, I wish we could have a flag to portal.main such that we could invoke portal standalone this way:
bb -cp `clojure -Spath -M:portal/cli` -m portal.main --standalone --port 1664

(or have the usual shortcut -s and -p).
As for the client, it would be great if this is included directly inside the portal api, so that we could have it on both Clojure and ClojureScript. But as it is now, I can already use it!
I am going to try to incorporate portal with my clomacs configuration :-)
Best regards,
David

@djblue thanks for this, portal keeps surprising me with how easy it is to set up in different environments! This time tap>-ing from Cloudflare workers :)

@martinklepsch Thanks a lot for the code snippet, we should totally find a way to merge this into the library. @djblue Would you welcome a pull request?

@martinklepsch thanks for the ClojureScript client example!
@davidpham87 I would definitely welcome a pull request! Since you've opened this issues, I've been thinking a lot about how a remote API would enable a bunch of useful workflows. https://github.com/djblue/portal/tree/client-api is what I have done so far but it could use more work.
I'm thinking the clients could live under portal.client.<platform>, for example:

portal.client.jvm
portal.client.web
portal.client.node
portal.client.clr
portal.client.erlang

I recently added https://github.com/djblue/portal/commit/b7cf00b9ca7ea8ffaeff8ed30fa644fcd373c63b. So I'm hoping in the future, you will be able to pipe all tap>s to a single portal and quickly determine which runtime they came from 👌

@davidpham87 the changes have been merged to master and will be part of the next release. I made the following updates:
Rename client fns from send! to submit

Use submit to more closely match portal.api/submit
Default to edn for transport as it provides the highest level of serialization fidelity.
Include metadata when printing edn
Default to tagged literals when reading edn

Thanks again for this awesome contribution!

authors: davidpham87 djblue martinklepsch

repo: djblue/portal


text:
Client and Server examples don't work

When I run the server and client with
cargo run --example server ./ --listen 127.0.0.1:4433
and
cargo run --example client https://localhost:4433/cargo.toml
I just get a bunch of retransmits and eventually the client times out.
I get the same retransmit messages when I run the benchmark.
Am I doing something wrong or is this a bug?

At a guess, your OS may not support dual-stack sockets. The client example binds to IPv6, so try binding the server to [::1]:4433 and using that in place of localhost to be sure.

Yeah running the server on ipv6 works, although I do have to use localhost as it tries to do a dns lookup. Thanks!

repo: djc/quinn


text:
🛑 Writeguard is down

In f89779c, Writeguard (https://www.writeguard.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Writeguard is back up in 2b0cc7f.


text:
switch to setup-java action (to replace setup-scala which is no longer maintained)

I initially raised thise because Eclipse Temurium has taken over Adoptium - https://adoptium.net/
I then discovered that setup-scala doesn't support Temurin and is no longer being maintained - https://github.com/olafurpg/setup-scala/issues/49

Agreed. This is a yak I need to shave sooner rather than later.

authors: djspiewak pjfanning

repo: djspiewak/sbt-github-actions


text:
Change Log?

More of a feature request I guess.
What is the best way to tell what new apps have been added?  Is there a change log?
I like to check this repository on a regular basis, say once a week. What is the best way to figure out what has been added since the last time I checked other than diff'ing the repository?
Thanks in advance.

Our Twitter feed may be of some interest to you:
https://twitter.com/opensourceios

#360

authors: dkhamsing scribblemaniac wm-j-ray

repo: dkhamsing/open-source-ios-apps


text:
Recursive template expansion with HashMap

When the value of one hashmap is a struct or a class that contains another hashmap an error occurs.
Code:
import containers;

HashMap!(const(int), A) hm;

class A
{
    protected HashMap!(int, bool) innerHm;
}

void main()
{
}

Output:
source/app.d(7,15): Error: struct containers.hashmap.HashMap(K, V, Allocator = Mallocator, alias hashFunction = generateHash!K, bool supportGC = shouldAddGCRange!K || shouldAddGCRange!V, bool storeHash = true) recursive template expansion source/app.d(7,15):        while looking for match for HashMap!(int, bool) [snip]/ldc2-1.19.0-osx-x86_64/bin/../import/std/traits.d(3360,63): Error: template instance std.traits.isDynamicArray!(A) error instantiating ../../.dub/packages/emsi_containers-master/emsi_containers/src/containers/internal/node.d(63,26):        instantiated from here: hasIndirections!(A) ../../.dub/packages/emsi_containers-master/emsi_containers/src/containers/hashmap.d(26,41):        instantiated from here: shouldAddGCRange!(A) source/app.d(3,1):        instantiated from here: HashMap!(const(int), A) source/app.d(3,1):        while looking for match for HashMap!(const(int), A) [snip]/ldc2-1.19.0-osx-x86_64/bin/ldc2 failed with exit code 1.

It might be a compiler bug since changing the order of the declarations seems to solve the problem

repo: dlang-community/containers


text:
Move generated docs{,-prerelease}.json to $GENERATED

It just felt wrong to put generated files not into the $(GENERATED) folder.
As on the DMD Makefile I used $G to avoid the visual noise.
CC @CyberShadow @s-ludwig

Second PR that's a duplicate of my PRs in past month: https://github.com/dlang/dlang.org/pull/1657
We could use more dlang.org reviewers...

Second PR that's a duplicate of my PRs in past month: #1657

Sorry :S

We could use more dlang.org reviewers...

Yes, please :)

authors: CyberShadow wilzbach


text:
Remove 'State of D' survey banner

To be merged on Wednesday, 14.3

As it turns out, we already have a new item for the highlighted news area - the Amazon Smile promotion.
I already added this to this PR to avoid merge conflicts:

I'm not really sure about this. The turquoise really sticks out from the rest of the page.
Can we put this on the donate page or redesign it to be less obtrusive?
What do you think @CyberShadow?

redesign it to be less obtrusive?

How about something like the existing banner?

or:

I think the banner is OK, considering it's temporary.

@JackStouffer the plan is to swap this tonight, so if you have a better idea, please let me know.

If it's temporary I'm ok with it.

authors: CyberShadow JackStouffer wilzbach


text:
Error for implicit string concatenation

PR to accompany https://github.com/dlang/dmd/pull/8220
See https://dlang.org/deprecate.html#Implicit string concatenation
This PR moves a deprecation forward, further narrowing the gap between specification and implementation.

(rebased)

authors: JinShil wilzbach


text:
Heisenbug: deferred crash when writing to stdout on Windows without console.

verylonglogin.reg reported this on 2011-11-02T06:42:48Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=6880
CC List

andy
dlang-bugzilla

Description
A possible Release-only bug: deferred crash when writing to stdout on Windows without console.

To reproduce:
1. Write a program using `writeln` for debugging output.
2. Prefix every `writeln` with a `debug` except one which was missed.
3. Create a release build with SUBSYSTEM:WINDOWS which has no console and test it a bit to see it launches and works.
4. Take tons of user feedbacks like: "It works about a minute (10 minues, an hour) and than it crashes."

Fitst two Steps will be solved as soon as
Suggestion #1. some debug tracing will be added to Phobos (std.log, e.g.) and
Suggestion #2. `writeln` with friends will be marked by a big red text "NOT FOR DEBUG OUTPUT, USE ... INSTEAD".

But it still can be a situation like when you need an optional non-debug console output for some reason, e.g. program can optionally work in a console mode and than you have missed one `if(consoleMode)` prefix.

Suggestion #3. Throw an exception as soon as `writeln` is called and standard output stream is invalid, like .NET Framework's System.IO.Console.WriteLine()...
Strange, but I can't reproduce such exception in .NET Framework any more, now WriteLine() just silently doing nothing, maybe I mixed something in memory, it was a long time ago... Anyway, this silence looks not good.

And
Suggestion #4. Remove writing debug info to a console in release from Phobos (e.g. std.typecons.Unique) and disallow such code in Phobos forever.

But all this is just IMO, what do you think?

andy commented on 2015-01-25T18:06:20Z
I test this, on windows, with DMD v2.066.1:

dmd -L/SUBSYSTEM:WINDOWS test.d

import std.stdio;

void main()
{
writ

dlang-bugzilla commented on 2011-11-02T14:40:04Z
It would help if you provided a stack trace. You can write a WinMain which displays uncaught exceptions in a message box:
http://www.digitalmars.com/d/2.0/windows.html

You may find this helpful:

if (!GetConsoleWindow()) {
    stdout.open("stdout.log", "w");
    stderr.open("stderr.log", "w");
}

verylonglogin.reg commented on 2015-01-25T18:28:43Z
(In reply to AndyC from comment #3)
> I test this, on windows, with DMD v2.066.1:
>
> ---- file test.d:
> import std.stdio;
>
> void main()
> {
>    writeln("hello world");
> }
>
>
> comile:
> dmd -L/SUBSYSTEM:WINDOWS test.d
>
> ran it by dbl-clicking and from cmd.exe.  No exception, no error.
>
> I checked std/typecons.d and found no write's without debug.
>
> Closing.
>
> Please re-open if its still a problem, and please provide more specific
> steps to reproduce.  "take tons of user feedback" doesn't help me fix the
> problem.

As I had written in the issue description it's a deffered failure (i.e. some buffer overflows). One can use any testcase which prints enough data to overflow the buffer, e.g.:
---
import std.stdio;

void main()
{
    foreach(const i; 0 .. 100_000)
        write("12345678"); // for me fails at i = 2048
}
---

andy commented on 2015-01-25T18:10:51Z
I test this, on windows, with DMD v2.066.1:

---- file test.d:
import std.stdio;

void main()
{
   writeln("hello world");
}

comile:
dmd -L/SUBSYSTEM:WINDOWS test.d

ran it by dbl-clicking and from cmd.exe.  No exception, no error.

I checked std/typecons.d and found no write's without debug.

Closing.

Please re-open if its still a problem, and please provide more specific steps to reproduce.  "take tons of user feedback" doesn't help me fix the problem.

verylonglogin.reg commented on 2015-01-25T19:22:25Z
(In reply to AndyC from comment #5)
> Confirmed.  Breaks for me to.
>
> Do you know if there is a way to detect if a console exists?

This information alone doesn't give you much as e.g. a stream can be redirected.
Also I have already written all information I know about the issue here.

andy commented on 2015-01-25T19:14:23Z
Confirmed.  Breaks for me to.

Do you know if there is a way to detect if a console exists?

dlang-bugzilla commented on 2017-06-27T18:10:27Z
As I understand, what happens here is:

1. The program starts, and writes data to stdout / stderr
2. The data goes into the C FILE* buffer
3. When the buffer fills up, the C runtime attempts to flush it
4. Upon flushing, it discovers that the output handle in non-writable

Perhaps the runtime could detect an unwritable stdout/stderr and close (or otherwise make invalid) the respective std.stdio handles.

Though, even if writeln was changed to check if the output handle is writable on first or every write, the steps to reproduce would still apply - a forgotten writeln inside some rarely-executed code, such as an error handler, can still go through initial testing and end up crashing the application on the end-user's site.

dlang-bugzilla commented on 2015-01-25T19:23:16Z
You can detect if your program is running in a console with:

GetConsoleWindow() != NULL

However, this is probably not what you want - instead you want to check if standard output is writable (you can probably create a GUI program and redirect its output somewhere, and the program will work fine). I'm not sure how to do that off the top of my head, though.

repo: dlang/phobos


text:
Fix Issue 16264(+11599) - BigInt multiplication crashes on 64-bit

https://gist.github.com/yosupo06/03bc48477049c8ac094a242bee511d0d#file-a-d : Stress test code

Thanks for your fix and thorough testing.
A small explanation of what you fixed (in the commit message) would be really helpful to review this.

thx

This pull request introduced a regression:
https://issues.dlang.org/show_bug.cgi?id=19740

authors: CyberShadow MartinNowak yosupo06


text:
remove upload_heatlist button from comp_detail view

Solution is for the admin login to upload file-based heatlists

fixed with pull request #77


text:
Example with koa-router doesn't work

"koa-router": "^7.3.0"
this is version, app.use can work, but router not work!!!

I got the same problem.
...
app.use(KoaBodyParser())
router.all('/api/file', KoaBody(), async ctx => {
  ctx.body = {
    api: true,
    type: ctx.method,
    query: ctx.query,
    body: ctx.request.body,
    files: ctx.request.body.files
  }
})

"koa":"2.5.1"
"koa-router": "7.4.0"
"koa-body":"2.6.0"

Can one of you provide a single file that reproduces the exact issue? Is there an error?

@MarkHerhold
My problem is that when the Content-type  is application/x-www-form-urlencoded it does not respond to the.
code:
app.use(KoaBodyParser())

router.all('/api/file', KoaBody(), async ctx => {
  ctx.body = {
    api: true,
    type: ctx.method,
    query: ctx.query,
    body: ctx.request.body,
    files: ctx.request.body.files
  }
})

When the code is app.use(KoaBodyParser())  othor router it dose not work !

@MarkHerhold
const router = new Router() router.use('/upload', KoaBody({ multipart: true }), async ctx => {   console.log(ctx.request.body); })
or use router.post and etc, it not work, but use app.use, encountered the same problem @damianb, other routers await to loading.
use koa-router, maybe router.use parameters is error, and not run next() other middleware

the same with me ,the result of  console.log(ctx.request.body.files)  is undefined , i have already to upload a picture.

how to resolve this problem ??

@Chen-WeiZhen files was moved to ctx.request.files in the latest version.

Whet I try to use koa-body in router, I get this exception:
error:  message=next is not a function, stack=TypeError: next is not a function
at /srv/.../node_modules/koa-body/index.js:110:14
at process._tickCallback (internal/process/next_tick.js:68:7)

in app level it works fine. My params:
koaBody({
    json: false,
    text: false,
})

@kaimiyang I'm still not exactly sure what the issue you are facing is. My speculation is that you aren't correctly initializing your router before trying to use it.
This minimal example works for me:
var log       = console.log,
    Koa       = require('koa'),
    app       = new Koa(),
    router    = require('koa-router'),
    koaBody   = require('../index'),
    port      = process.env.PORT || 4291
    host      = process.env.HOST || 'http://localhost';

/*!
 * Accepts only urlencoded and json bodies.
 */
router.post('/upload', koaBody(), async (ctx) => {
    console.log(ctx.request.body);
  }
);

app.use(router.routes());
app.listen(port);

log('Test with executing this commands:');
log('curl -i %s:%s/post/users -d "user=admin"', host, port);
log('Press CTRL+C to stop...');

@gugu please open a separate issue and include your version of both koa-body and koa-router.
Both of you, please see the koa-router example here.

authors: Chen-WeiZhen MarkHerhold gugu kaimiyang mengdu scragg0x

repo: dlau/koa-body

license: mit


text:
Issue with KakaduNativeProcessor

Description
When running this image with KDU 8.2.1 we are running into frequent crashes. The image seems more stable locally when running on a single core (via docker-compose)
deploy:
  resources:
    limits:
      cpus: '1'
      memory: 4096M

However, when deploying to AWS ECS, either as a Fargate or EC2 service this is still unstable. Using different combination of S3Source/FileSystemSource, StreamStrategy/CacheStrategy/DownloadStrategy and enabling/disabling chunking makes no difference.
This is not happening with all images, we are encountering this in Wellcome's environment, mostly with images that originated from proquest. E.g.

b17523722_hin-wel-all-00000343_0049.jp2
b12948093_hin-wel-all-00009067_0001.jp2
b12948093_hin-wel-all-00009067_0065.jp2
b10004816_hin-wel-all-00012196_0003.jp2
b10004816_hin-wel-all-00012196_0004.jp2

Note that the above are larger than most other Wellcome JP2s but are by no means large (~8MB). Tile requests seem fine but it could be due to the size.
Errors/Behavour
Cantaloupe logs will often output something similar to:
[qtp283318938-12] INFO  e.i.l.c.r.i.v.ImageResource - Handling GET /iiif/2/5%2Fb12946308_hin-wel-all-00001677_0040.jp2%2Fb12946308_hin-wel-all-00001677_0040.jp2.jp2/full/max/0/default.jpg
[qtp283318938-12] DEBUG e.i.l.c.r.i.v.ImageResource - Request headers: X-Forwarded-Proto: http; X-Forwarded-For: 62.254.125.28; Host: kduspecial.dlcs.io; X-Forwarded-Port: 80; X-Amzn-Trace-Id: Root=1-646cbff7-70123d20199f2b423a0d24bd
[qtp283318938-12] DEBUG e.i.l.c.i.MetaIdentifier - [Raw path component: 5%2Fb12946308_hin-wel-all-00001677_0040.jp2%2Fb12946308_hin-wel-all-00001677_0040.jp2.jp2] -> [decoded: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2] -> [slashes substituted: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2]
[qtp283318938-12] DEBUG e.i.l.c.i.Identifier - [Raw path component: 5%2Fb12946308_hin-wel-all-00001677_0040.jp2%2Fb12946308_hin-wel-all-00001677_0040.jp2.jp2] -> [decoded: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2] -> [slashes substituted: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2]
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache - getInfo(): not found: /var/cache/cantaloupe/info/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b.json
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache - getSourceImageFile(): /var/cache/cantaloupe/source/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b
[qtp283318938-12] DEBUG e.i.l.c.s.FilesystemSource - Resolved 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2 to /home/cantaloupe/images/5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2
[qtp283318938-12] DEBUG e.i.l.c.p.ProcessorFactory - KakaduNativeProcessor selected for format JPEG2000 (AutomaticSelectionStrategy offered KakaduNativeProcessor, OpenJpegProcessor, GrokProcessor)
[qtp283318938-12] DEBUG e.i.l.c.p.ProcessorConnector - File -> FileProcessor connection between FilesystemSource and KakaduNativeProcessor
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache - getInfo(): not found: /var/cache/cantaloupe/info/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b.json
[qtp283318938-12] DEBUG e.i.l.c.c.InfoService - readInfo(): read 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2 from KakaduNativeProcessor in 9 msec
[work-nm-2516274] DEBUG e.i.l.c.c.InfoService - putInObjectCache(): adding info: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2 (new size: 1)
[work-nm-2516274] DEBUG e.i.l.c.c.InfoCache - putInObjectCache(): adding info: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2 (new size: 1)
[work-nm-2516274] DEBUG e.i.l.c.c.FilesystemCache - put(): writing 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2 to /var/cache/cantaloupe/info/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b.json_work-nm-2516274.tmp
[work-nm-2516274] DEBUG e.i.l.c.c.FilesystemCache - put(): moving /var/cache/cantaloupe/info/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b.json_work-nm-2516274.tmp to /var/cache/cantaloupe/info/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b.json
[qtp283318938-12] DEBUG e.i.l.c.r.i.v.ImageResource - Base URI assembled from X-Forwarded headers: http://kduspecial.dlcs.io
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache - newDerivativeImageInputStream(): /var/cache/cantaloupe/image/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b_56782f8b936d89dd34b4839ae243ef0a.jpg
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache - newOutputStream(): miss; caching 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2_1:1_scalebypixels:!2612,3827,bicubic_encode:jpg_JPEG_80_interlace_#FFFFFF_8_e95198c48292fa4c8fc0617e850c1f6d
[qtp283318938-12] DEBUG e.i.l.c.r.ImageRepresentation - Writing to the response & derivative cache simultaneously
[qtp283318938-12] DEBUG e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Rendered region 0,0/2612x3826; source 0,0/2612x3826; 0x reduction factor; differential scale 8071693/10000000; PPI 600.0x600.0
[Thread-10] ERROR e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Kakadu Core Error:
System is entering deadlock. This may be a false alarm if you are expecting a
call to `kdu_thread_entity::signal_condition' from a foreign thread, but then
`kdu_thread_entity::wait_for_condition' should have supplied
`expect_foreign_wakeup'=false to avoid the false alarm.
Deadlock detected by thread 2
* Working-waiters state 0x2000000000000004
* Non-waiting workers state 0x0000000000000081; (A,T,I)=(1,0,2)
* Thread 0: <idle>; <Status=--A>; <WWID=0>, conditions...
Waiting for "get_new_synthesized_stripe" (S,F)=(...,Local)
* Thread 1: <idle>; <Status=--A>; <No-WWID>
* Thread 2: <active>; <Status=--A>; <No-WWID>
* Thread 3: <idle>; <Status=--A>; <No-WWID>
Kakadu Core Error:
System is entering deadlock. This may be a false alarm if you are expecting a
call to `kdu_thread_entity::signal_condition' from a foreign thread, but then
`kdu_thread_entity::wait_for_condition' should have supplied
`expect_foreign_wakeup'=false to avoid the false alarm.
Deadlock detected by thread 2
* Working-waiters state 0x2000000000000004
* Non-waiting workers state 0x0000000000000081; (A,T,I)=(1,0,2)
* Thread 0: <idle>; <Status=--A>; <WWID=0>, conditions...
Waiting for "get_new_synthesized_stripe" (S,F)=(...,Local)
* Thread 1: <idle>; <Status=--A>; <No-WWID>
* Thread 2: <active>; <Status=--A>; <No-WWID>
* Thread 3: <idle>; <Status=--A>; <No-WWID>
[qtp283318938-12] ERROR e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Fatal error in the codestream management machinery.
[qtp283318938-12] DEBUG e.i.l.c.p.c.ImageWriterFacade - Writing with edu.illinois.library.cantaloupe.processor.codec.jpeg.TurboJPEGImageWriter
[qtp283318938-12] DEBUG e.i.l.c.r.ImageRepresentation - KakaduNativeProcessor processed in 383 msec: 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2_1:1_scalebypixels:!2612,3827,bicubic_encode:jpg_JPEG_80_interlace_#FFFFFF_8_e95198c48292fa4c8fc0617e850c1f6d
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache$ConcurrentFileOutputStream - close(): closing stream for 5/b12946308_hin-wel-all-00001677_0040.jp2/b12946308_hin-wel-all-00001677_0040.jp2.jp2_1:1_scalebypixels:!2612,3827,bicubic_encode:jpg_JPEG_80_interlace_#FFFFFF_8_e95198c48292fa4c8fc0617e850c1f6d
[qtp283318938-12] DEBUG e.i.l.c.c.FilesystemCache$ConcurrentFileOutputStream - close(): moving /var/cache/cantaloupe/image/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b_56782f8b936d89dd34b4839ae243ef0a.jpg_qtp283318938-12.tmp to /var/cache/cantaloupe/image/bd/41/77/bd41775f8f5f909ca8c04c76ac24772b_56782f8b936d89dd34b4839ae243ef0a.jpg
[qtp283318938-12] DEBUG e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Kakadu Core Warning:
Destroying the memory allocator used to manage core precinct resources without
first releasing all the relevant allocated memory.

which doesn't necessarily happen just before a crash and seemingly doesn't happen on every occasion. The actual error is:
[qtp283318938-17] DEBUG e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Rendered region 0,0/2630x3801; source 0,0/2630x3801; 0x reduction factor; differential scale 7872825/10000000; PPI 600.0x600.0
[qtp283318938-17] DEBUG e.i.l.c.p.c.j.JPEG2000KakaduImageReader - Rendered region 0,0/2630x3801; source 0,0/2630x3801; 0x reduction factor; differential scale 7872825/10000000; PPI 600.0x600.0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f9ed7742a77, pid=23, tid=80
#
# JRE version: OpenJDK Runtime Environment (11.0.18+10) (build 11.0.18+10-post-Ubuntu-0ubuntu122.04)
# Java VM: OpenJDK 64-Bit Server VM (11.0.18+10-post-Ubuntu-0ubuntu122.04, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libkdu_jni.so+0x347a77] kd_core_local::kd_resolution::advance_bkgnd_parsed_precinct_rows(kdu_core::kdu_thread_env*, bool)+0x1c7
#
# Core dump will be written. Default location: /opt/kakadu/core.23
#
# An error report file with more information is saved as:
# /opt/kakadu/hs_err_pid23.log
#
# If you would like to submit a bug report, please visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-lts
#
/opt/app/s3-config.sh: line 11: 23 Aborted (core dumped) java -Dcantaloupe.config=/cantaloupe/cantaloupe.properties -Xmx$MAXHEAP -Xms$INITHEAP -jar /cantaloupe/cantaloupe-$CANTALOUPE_VERSION.jar

# Problematic frame:
# C [libkdu_jni.so+0x347a77] kd_core_local::kd_resolution::advance_bkgnd_parsed_precinct_rows(kdu_core::kdu_thread_env*, bool)+0x1c7

Next Steps
We need to identify:

Is this an issue with Kakadu?

8.2.1 only? Do older/newer versions work?
Can we get support if so?

Or Cantaloupes use of Kakadu?

How do we fix if so?

Resolved by upgrading to 8.4.1

repo: dlcs/image-server-node-cantaloupe


text:
Undocumented global CSS handling

Hey, thank you for the beautiful solution and unblocking my Next13 experiments.
So far I've noticed only one "big" problem (the other one is something about linaria vs webpack cache) related to global css and the expectations for css modules - aka "pure selectors"
Long story short - you have undocumented file pattern enabling non-pure selectors and the pattern is not really "sound" - I can imagine a file named css-reset.global.ts, but not css-reset.linaria.global.ts
Wondering if pattern can be changed a little bit and the solution documented.

Hey @thearnica, I'm glad to hear that it helps your experiments. Unfotuantially I'm not quite sure if I got the issue, could you elaborate a bit more? I tried to document the rule here. Is there anything that could have been documented better?

🙃 yep, everything is clearly documented. Now I am drinking the second cup of a coffee and thinking how did I miss that
Look like my issue was resolved 🤗, thank you

authors: dlehmhus thearnica

repo: dlehmhus/next-with-linaria


text:
W10 node-sass@4.9.3 error

$ npm -v
6.9.0

$ node -v
v12.5.0

$ node -p process.versions
{
  node: '12.5.0',
  v8: '7.5.288.22-node.14',
  uv: '1.29.1',
  zlib: '1.2.11',
  brotli: '1.0.7',
  ares: '1.15.0',
  modules: '72',
  nghttp2: '1.38.0',
  napi: '4',
  llhttp: '1.1.4',
  http_parser: '2.8.0',
  openssl: '1.1.1c',
  cldr: '35.1',
  icu: '64.2',
  tz: '2019a',
  unicode: '12.1'
}

$ node -p process.platform
win32

$ node -p process.arch
x64

Hello,
I have an error for a while when I try to install gulp-sass. The download directory of node-sass on windows is no longer the right one :

The link of download is a 404 : https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-72_binding.node
Thanks in advance

Fixed by do a npm i gulp-sass (and deleting the node_modules) that updating the composer-lock.json. Then the repo url was good

repo: dlmanning/gulp-sass


text:
Service Request by [Jessica ] on county data view

[ ] Qualtrics Service Request Form was received from User
[ ] e-mail acknowledging that User's Qualtrics Service Request Form was sent
[ ] Problem NOT RESOLVED
[ ] Problem PARTIALLY RESOLVED
[ ] Problem FULLY RESOLVED and Issue is Closed
[ ] Qualtrics Post-Service Request Survey was sent to User

Use comments feature (below) to document:

A clear and concise description of the solution.

A clear and concise description of any alternative solutions or features you've considered.

Any additional context, such as screenshots about the problem.

Hi Donrie:
Is this for Putnam only?
DL

Hi Jeff
If possible can you please allow for the monitoring measures data to be downloaded and sorted according to the most recent date.

No, all counties profe'

Hi Donrie: Monitoring would need to be sorted by IPA/Strategy, then by Measure, then by date for each point entered for a measure. At least that is what I would suggest.
Is this getting at the matter?
Downloaded data can be sorted in any way via Excel, of course.

You don't understand, hold let me send the image

Hi Jeff
Can you sort this data as Jessica request for all the counties please. She wants the most recent data at the top.

authors: dlounsbu donriepurcell

repo: dlounsbu/NYHEALing-IPAtracker-support


text:
Don't use unset($this)

I have an error PHP Fatal error:  Cannot unset $this in php7.1 with the XMLGenerator because it has a method like:
public function __destruct() {
      unset($this);
}

From the php documentation of unset you can read:

Note:

It is not possible to unset $this inside an object method since PHP 5.

Before php7 it doesn't hurt but now it complains about it. I think it could be removed without problems as $this variable is removed automatically when you go out of context.

I did an update for that

authors: PhoneixS dmitrirussu

repo: dmitrirussu/php-sepa-xml-generator


text:
Added tesnorizeation for avx2 based gemm.

Summary:
Similar to other avx512 tensorization that reduces data:1x4 and kernel:16x4 to output:1x16, this PR introduces similar reduction using avx2 tensorization. It keeps the same API as avx512 so as to not have to introduce a new memory layout for weights.
Test Plan:
on avx2 machine:
python tests/python/contrib/test_gemm_avx2_acc32.py
Reviewers:
Subscribers:
Tasks:
Tags:
Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers.

Depends on this PR: https://github.com/dmlc/tvm/pull/3981

@anijain2305, thats a good question. I havent checked the performance of this agains fp32 model we are interested in. I will report the numbers soon. But we do get a lot of speed up on skylake with avx512 and assuming we dont get anything from AVX2 instructions itself due to latency issues you mention, there should still be some perf left from the memory bw persepctive.

@anijain2305, thats a good question. I havent checked the performance of this agains fp32 model we are interested in. I will report the numbers soon. But we do get a lot of speed up on skylake with avx512 and assuming we dont get anything from AVX2 instructions itself due to latency issues you mention, there should still be some perf left from the memory bw persepctive.

Ok. This might be useful to do some paper calculations to see if we can get performance theoretically - https://www.agner.org/optimize/instruction_tables.pdf

@anijain2305, do you mind if I land this? I would like to use it for some of the stuff we are working on.

@anijain2305, do you mind if I land this? I would like to use it for some of the stuff we are working on.

Yes, please go ahead. The changes LGTM. Would appreciate if later you could update with the performance comparison.

Thanks @anijain2305, will do so.

Just as FYI. CI is failing on the test I added as it is dependent on this PR: https://github.com/dmlc/tvm/pull/3981/. I need to land that.

@anijain2305, would mind merging this please? I dont think I can, plus it seems that my lint changes and addressing your comments might have voided your approval.

I don't have merge permissions :)
@tqchen can you please take a look?

Thanks @kimishpatel @anijain2305

authors: anijain2305 kimishpatel tqchen

repo: dmlc/tvm


text:
How to use  momentum in the learning rate

When I adjust the learning rate parameter, the learning rate remains constant during the training process，so，l would like to know how to get an adaptive learning rate，for example,using  momentum or sth?
@kashif @mattn @darxriggs @smly @omo @JiaxiangBU

There's call back function.

repo: dmlc/xgboost


text:
Support building with cmake with unity build (build speedup)

Hi there,
With cmake > 3.16 there is a nice (optional) feature called unity build which help speedup building large or complex C++ projects. Here is a write up on how this works. Speed ups can be pretty large.
However tweaks are sometimes required to get it to work. Typically if you have 2 constants with the same value in 2 .cpp file, a problem happens. Variables with similar name needs to only be declared once.
Here is how I tried to build xgboost but I got those errors which I have a hard time decipher.
$ mkdir build ; cd build
build$ cmake -DCMAKE_UNITY_BUILD=ON -DUSE_OPENMP=OFF -DBUILD_STATIC_LIB=ON ..
build$
build$ make
Scanning dependencies of target dmlc
[  7%] Building CXX object dmlc-core/CMakeFiles/dmlc.dir/Unity/unity_1_cxx.cxx.o
[ 15%] Building CXX object dmlc-core/CMakeFiles/dmlc.dir/Unity/unity_0_cxx.cxx.o
[ 23%] Linking CXX static library libdmlc.a
[ 23%] Built target dmlc
Scanning dependencies of target objxgboost
[ 30%] Building CXX object src/CMakeFiles/objxgboost.dir/Unity/unity_6_cxx.cxx.o
[ 38%] Building CXX object src/CMakeFiles/objxgboost.dir/Unity/unity_5_cxx.cxx.o
In file included from /Users/bsergeant/src/foss/github/xgboost/build/src/CMakeFiles/objxgboost.dir/Unity/unity_5_cxx.cxx:4:
/Users/bsergeant/src/foss/github/xgboost/src/predictor/predictor.cc:12:1: error: explicit specialization of 'Get' after instantiation
DMLC_REGISTRY_ENABLE(::xgboost::PredictorReg);
^
/Users/bsergeant/src/foss/github/xgboost/dmlc-core/include/dmlc/registry.h:236:47: note: expanded from macro 'DMLC_REGISTRY_ENABLE'
  Registry<EntryType > *Registry<EntryType >::Get() {                   \
                                              ^
/Users/bsergeant/src/foss/github/xgboost/src/predictor/cpu_predictor.cc:507:1: note: implicit instantiation first required here
XGBOOST_REGISTER_PREDICTOR(CPUPredictor, "cpu_predictor")
^
/Users/bsergeant/src/foss/github/xgboost/include/xgboost/predictor.h:240:54: note: expanded from macro 'XGBOOST_REGISTER_PREDICTOR'
          ::dmlc::Registry<::xgboost::PredictorReg>::Get()->__REGISTER__(Name)
                                                     ^
1 error generated.
make[2]: *** [src/CMakeFiles/objxgboost.dir/Unity/unity_5_cxx.cxx.o] Error 1
make[1]: *** [src/CMakeFiles/objxgboost.dir/all] Error 2
make: *** [all] Error 2

If anyone is interested or can give us clues on how to fix that it would be appreciated. Thanks !

To fix it the factory registry in dmlc core needs to be changed.

Or setup SKIP_UNITY_BUILD_INCLUSION for needed source files.

Managed to get it working and tried it out.  There's some speedup but in general quite similar as XGBoost is not difficult to compile, and CMake unity build doesn't support CUDA.

Thanks for trying !
On my Linux box xgboost takes quite a bit of time to compile which is why I asked. For one codebase we saw improvements from 6 to 10x.
I know that cmake cuda support seems to improve with time, the latest release 3.19 mention improved cuda support so hopefully one day they will support unity builds.

On Oct 27, 2020, at 1:35 AM, Jiaming Yuan notifications@github.com wrote:
Managed to get it working and tried it out. There's some speedup but in general quite similar as XGBoost is not difficult to compile, and CMake unity build doesn't support CUDA.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/dmlc/xgboost/issues/6293#issuecomment-717078051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2O6UPMJA2CNL4XNAFH6XLSM2A37ANCNFSM4TADZQMA.

@bsergean Thank you for bringing it up, it actually helps up on Windows CI build time. :-)

Well I'm very glad it's helping.
If you end up making a new release which has it I'll be more than happy to test it, or I can just use a commit to test it actually.

On Oct 27, 2020, at 11:06 PM, Jiaming Yuan notifications@github.com wrote:
@bsergean https://github.com/bsergean Thank you for bringing it up, it actually helps up on Windows CI build time. :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dmlc/xgboost/issues/6293#issuecomment-717720421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2O6UMN2CE4ZWSMNTPORKDSM6YHFANCNFSM4TADZQMA.

We are preparing 1.3 release.  But will also keep you posted on merging the PR.

Merged.  Feel free to try it out on master.

authors: bsergean trivialfis


text:
[R] native routines registration

CRAN check now nags:
File ‘xgboost/libs/xgboost.so’:
  Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’

It is good practice to register native routines and to disable symbol
search.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.

... as if there were not enough hoops already to jump through in order to use native code from R.
Anyway, the manual provides good explanations and instructions for that practice. I went with the simpler option: generating the registration code with tools::package_native_routine_registration_skeleton('.', con = 'src/init.c', character_only = F).
Another slightly more complex option might be to use tools::package_native_routine_registration_skeleton('.', con = 'src/init.cc', include_declarations = F, character_only = F), and then edit src/init.cc to add the #include "./xgboost_R.h" line and prepend XGB_DLL in front of void R_init_xgboost. But I don't see any reason to prefer this approach.

@hetong007 @tqchen could one of you please review this? Many R packages are adding such registrations lately.
As there would be need to modify the auto-generated init.c file to conform to our code requirements, it would make sense to edit it by hand in future. Thus, an option with init.cc would not be much different, and might even be preferable as it wouldn't require repeating the declarations. What's your opinion?

LGTM

Seems either way's fine. If we could pass the code through a function similar to formatR::tidy_source(), then lint is happy.
I looked into formatR, seems not able to do it though.

authors: hetong007 khotilov tqchen


text:
Double arrows on the merge button?

I know we've talked about this before, but I was just looking at the merge button thinking that it might be nice to have arrows on both sides of it... Thoughts?

What we discussed before is that the arrow to the working directory doesn't necessarily happen. If there is a merge conflict (as there often are), then only changes are made to the working directory. Also it can be unclear where changes are coming from and going to with arrows.
Changes come from the repository (and possibly working directory, but not in most cases), which results in changes in the working directory, and either a fast forward (no new commit) or a new commit, which you might have to commit changes for.
If you think arrows on the merge button come closer to informing users that this is what Git is doing, add them, or something that does 😃

The way I see it, with or without arrows the merge button is lying about what it's doing compared to the other buttons. I don't know which is the better lie!

repo: dmusican/Elegit


text:
Update prod to use 33_6_1_cms2

Allow numeric literals in data-tier names
https://github.com/dmwm/CMSRucio/issues/744

Did you test this on integration?

This is on integration now.
I have notified WM to test. And once they are satisfied we can merge this.

authors: dynamic-entropy ericvaandering

repo: dmwm/rucio-flux


text:
Add task :build to compose resources

Please add a task to build compose resources used in dobi.yaml.
Docker compose itself never rebuilds its images so if you develop images you have to manually rebuild them which involves:

specifying proper Docker Compose file with -f
specifying proper project name which is used in dobi.yaml

i.e.
$ docker-compose -f docker-compose.service-name.yml -p project-name build

Needless to say that if you mistype something or forget to provide project name you have pretty good chances to run into real problems with images versioning.
And all that could be replaced by just:
$ dobi service-name:build

ALSO
Using this task we could write special aliases in dobi.yaml for building all the images as a preparation step before running jobs, e.g;
job=build:
  tasks: [job1-image, job2-image, compose1:build, compose2:build]

This is especially important as images fetching/building takes a lot of time (tens of minutes or more) during which you basically sit and wait. So it's reasonable to separate steps of building and running.

Image should be built as dobi image resources, not from the compose file. I do not want to support building with docker-compose.

Image should be built as dobi image resources, not from the compose file. I do not want to support building with docker-compose.

What do you mean "support with docker-compose"? Is it in some way difficult to do it or what? You already run docker-compose up, do you? So what's wrong with adding more such things? Or do you mean that you don't want to make Dobi better?

What do you mean "support with docker-compose"?

There is already a way to build images, it is the dobi image resource. There's no reason to build using docker-compose build.
I don't want to make it worse. Having two different ways to do the same thing makes it worse.
The better way to build images is to make dobi image resources.

@OnkelTem , @dnephin  is right.
Before you used dobi, you were most likely using docker-compose to facilitate at least two things:

build your images
run your stack in a way that closely simulates production.

Long ago, I stopped using docker-compose to build my images because it provide enough control over how the built images are named.
So, now that you're using dobi, you don't need to use docker-compose build directive. simply specify image instead, and make dobi build the images to match.

authors: OnkelTem airtonix dnephin

repo: dnephin/dobi


text:
linkleri dışarıya nasıl gönderebiliriz.

yani istanbul a tıkladığında istanbul için yapılmış sayfaya nasıl gönderebiliriz.
bilgilendirir misiniz

jquery ile id degerini alıp sehiri belirleyin redirect ypabilirsiniz

@ismailix çok geç olmuş ama svg-turkiye-haritasi.js içerisinde 'click' eventi zaten mevcut, oradan hangi ile tıklandıysa onu yakalıyoruz. Yakaladığımız il hangisi ise onun sitesine istediğiniz gibi yeni sekmede açma yaptırabilirsiniz. Yeni sekmede açmak için de javascipt içerisinde yer alan yöntemleri rahatlıkla kullanabilirsiniz.

authors: Sami-donmez SarperMUTLUBAY ismailix

repo: dnomak/svg-turkiye-haritasi


text:
Layer weights change despite trainable flag set to false

I have a network where some of the network layers have the trainable flag set to false.  I check the weight values before and after calling "fit" and the weight values change.  Even when regularization is set to false,  they change.  Could this be a bug or am I missing something?  Thanks
Jeff
for layerName in ae.layers_:
    if isinstance(ae.layers_[layerName],Conv2DLayerFast):
        ae.layers_[layerName].W = ae.layers_[layerName].add_param(ae.layers_[layerName].W,ae.layers_[layerName].W.container.data.shape, trainable=False)
        ae.layers_[layerName].b = ae.layers_[layerName].add_param(ae.layers_[layerName].b,ae.layers_[layerName].b.container.data.shape, trainable=False)
        #ae.layers_[layerName].params.items()[0][1].remove('trainable')
        #ae.layers_[layerName].params.items()[1][1].remove('trainable')

print get_all_param_values(ae.layers_['conv2d1'])

ae.fit(X, X_out)
print get_all_param_values(ae.layers_['conv2d1'])

Also, the message that is displayed when when training the network
"Neural Network with 458656 learnable parameters"
Displays the total number of learnable parameters, not the number of parameters that are being learning (prints the same number if trainable=False on some layers)
This is the fix, not sure if intended or bug:
@staticmethod
def _get_greeting(nn):
    shapes = [param.get_value().shape for param in
              nn.get_all_params(**trainable=True**) if param]
    nparams = reduce(operator.add, [reduce(operator.mul, shape) for
                                    shape in shapes])
    message = ("# Neural Network with {} learnable parameters"
               "\n".format(nparams))
    return message

About your first problem, I don't know why the weights change. nolearn should not interfere with that. Have you tried what happens if you use the same layers but train without nolearn?
Regarding the second problem, I guess it depends on your definition of "learnable". I believe the main distinction is "learnable" vs hyper-parameters such as the learning rate. Maybe there should be a second sentence with the number of trainable parameters, as you suggested? You could try to make a pull request and see what @dnouri thinks about it.

I updated the 'greeting' in the way that @caleytown suggested.  I think it's what people expect.

@caleytown If you've initialized your network before, e.g. you've trained it with fit already before your loop, then make sure that you initialize the network again (and thus pass the updated list of parameters this time).
Something like this should do:
# after some training, set some params to be not trainable:
mylayer = ae.layers_['mylayer']
mylayer.params[mylayer.W].remove('trainable')
mylayer.params[mylayer.b].remove('trainable')

# now call intialize to recompile optimizer, then fit:
ae._initialized = False
ae.initialize()

ae.fit(X, X_out)

authors: BenjaminBossan caleytown dnouri

repo: dnouri/nolearn


text:
w* tests fail with xiwi

Some platform combinations require xiwi to run graphical applications.  When those combinations are hit, the w* tests fail since the system is waiting for the extension (which isn't installed).
w* tests should not require the extension be installed to test (i.e., plumb that it's a test and avoid trying to connect to the extension/failing on no connect)

This now only impacts wheezy/kali (non-rolling).  Probably not worth fixing.

repo: dnschneid/crouton


text:
Pruning /mnt/stateful_partition/crouton/chroots/wheezy mounts...

Hello ,
i am trying to install debian wheezy on my Acer C720.
some days ago it worked well ... then i deleted the chroot for some reason.
today again i tried to install wheezy
chronos@localhost / $ sudo sh ~/Downloads/crouton -r wheezy -t kde
...after downloading files
it says
I: Base system installed successfully.
Pruning /mnt/stateful_partition/crouton/chroots/wheezy mounts...
but keeps on hanging after that. what did i do wrong this time?

try deleting the chroot again, and if that doesn't work u could try the other versions of debian, if u haven't already

now it worked k, but i get no sound . thats a pity.

with squeeze i also have problems
Installing target audio...
Fetching CRAS (branch 5c1b8df3853498e30e416b6289c12dab41a5988a)...
--2015-11-05 19:55:51--  https://chromium.googlesource.com/chromiumos/third_party/adhd/+archive/5c1b8df3853498e30e416b6289c12dab41a5988a.tar.gz
Resolving chromium.googlesource.com... 64.233.166.82, 2a00:1450:400c:c0b::52
Connecting to chromium.googlesource.com|64.233.166.82|:443... connected.
ERROR: certificate common name *.googlecode.com' doesn't match requested host name chromium.googlesource.com'.
To connect to chromium.googlesource.com insecurely, use `--no-check-certificate'.
Error fetching CRAS
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/squeeze...


text:
🛑 Site SCAE RGA is down

In 37842cd, Site SCAE RGA (https://www.sca-rga.interieur.gouv.fr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site SCAE RGA is back up in a48e995.

repo: dnum-mi/stats-sites-api


text:
Problem with karma peerDependencies

It looks like there's a problem retrieving all the dependencies when doing an npm install.  There is an issue open https://github.com/karma-runner/karma/issues/873, but it's not clear if anyone on the karma team is going to do anything about the dependency mess created.
Is there a workaround for this?  Thank you,
 ws@0.4.32 install /Users/jem/Dev/formbuilder/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
npm ERR! peerinvalid The package karma does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer grunt-karma@0.6.2 wants karma@~0.10.0
npm ERR! peerinvalid Peer karma-mocha@0.1.8 wants karma@>=0.12.8
npm ERR! peerinvalid Peer karma-safari-launcher@0.1.1 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-chrome-launcher@0.1.4 wants karma@>=0.9.3
npm ERR! peerinvalid Peer karma-firefox-launcher@0.1.3 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-phantomjs-launcher@0.1.4 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-coffee-preprocessor@0.1.3 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-html2js-preprocessor@0.1.0 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-jasmine@0.1.5 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-requirejs@0.2.2 wants karma@>=0.9
npm ERR! peerinvalid Peer karma-script-launcher@0.1.0 wants karma@>=0.9

npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/jem/Dev/formbuilder
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/jem/Dev/formbuilder/npm-debug.log
npm ERR! not ok code 0

Hello guys,
I am trying to use karma for an angular project unit tests but i get the same issue, does someone find a working fix for it ?
Thanks

authors: JMuhire jamesmortensen

repo: dobtco/formbuilder


text:
Fix new zstd support for alpine images

In e8ebf74e50128123a8d0220b85e357ef2d73a7ec zstd was installed as build dependency and thus does not end up in the final image which in turn renders docker-entrypoint.sh broken when using *.sql.zst files.

Thanks!

authors: tianon zappolowski

repo: docker-library/postgres


text:
Fixing releaseableLayer handling of layer streams and mounts.

Original PR message:
releaseableLayer includes automatic handling for creating a read/write layer and mounting it on a call to Mount(), but then does not correspondingly unmount the layer before trying to delete it, which will fail for some graphdrivers. Commit on a releaseable layer also leaks the tarstream for the layer. To fix this, the stream close is deferred in Commit and releaseRWLayer now correctly handles unmounting the layer before trying to delete it.  In addition, the changes include better error handling in Release() to make sure that errors are returned to the caller for failures on read/write layers instead of being ignored.# Please enter the commit message for your changes. Lines starting
Cherry-Pick note:
This version of the change was edited to merge with docker-ce 17.06, which did not include the releasableLayer.Commit code, requiring that part of the merge to be removed.
(cherry picked from commit 1d457999c4540aacda68f834bdb3c6f220ce3fd5)
Signed-off-by: Stefan Wernli swernli@ntdev.microsoft.com
Please do not send pull requests to this docker/docker-ce repository.
We do, however, take contributions gladly.
See https://github.com/docker/docker-ce/blob/master/CONTRIBUTING.md
Thanks!

ping @tonistiigi @andrewhsu PTAL - see the discussion on https://github.com/docker/docker-ce/pull/153; the fix for 17.07 did not apply on 17.06, so this is a modified version of the patch for 17.06
thanks @swernli !

if someone with write-access to this repo can prefix the title with [17.06] (for easier recognition) 👍

authors: swernli thaJeztah

repo: docker/docker-ce


text:
Superfluous "s" in sentence

File: engine/admin/systemd.md
"storage-drivers": "overlay"
There is a "s" to many, should be:
"storage-driver": "overlay"

I'll fix this!


text:
Release note strategy for Docker CE and EE

Problem description
We need to decide where release notes live now, who writes them, who hosts them, etc. We need to try to keep this as low maintenance as possible. A possible approach is a "highlights reel" curated by product management, coupled with a Github query showing the full list of PRs that went into a release, per affected repo.
Writing full, proper release notes is very time-consuming, and if the Docs team is going to take this on, we need more resources. This is not my first release notes rodeo.
cc/ @thaJeztah @friism @dmp42 @johndmulhausen

coupled with a Github query showing the full list of PRs that went into a release, per affected repo.

This is gonna be more tricky with the new release procedure, because pull requests will no longer be tied to a milestone, so even if we set impact/changelog on pull requests, there's no easy way to get a lost  of all of those that went into the release.
Possibly with some git magic; finding the commits, and relating that to pull requests

This was already fixed. :) 🎉 🌮

authors: mstanleyjones thaJeztah


text:
Add Dockerize and ASP.NET Core doc

Proposed changes
Add "Dockerize an ASP.NET Core app" documentation to the Docker engine examples section.
This doc takes the user through adding a Dockerfile and .dockerignore file to a simple ASP.NET Core application. It includes both Linux and Windows Container options for writing the Dockerfile. It then instructs the user on how to build and run the Docker container and view it in the browser.

This doesn't look good to me. I'm copy-pasting a critique I've offered to assorted others previously.

The basic problem is that the tutorial assumes users build the .NET app outside of Docker. This means the tutorial requires installing a bunch of random software on the machine for the project to build (in this case VS, .NET Core and Bower and Gulp - in addition to Docker). This nullifies one of the main reasons that developers love Docker, namely that Docker eliminates "It worked on my machine!?" problems. As currently written, to build a .NET app using this method, a developer onboarding to a project still has read through a long'ish setup readme, familiarize themselves with npm, install it, install .NET framework, etc. And woe betide you if you have the wrong version of any of that software installed, or it's misconfigured. An ops-guy will have the same headaches trying to set up and maintain a CI system.

Note that I'm not opposed to the pattern where you build a slim container for deployment. Here's a PR sent to some of Steve's code showing how this can be combined: https://github.com/SteveLasker/BuildASPDotNetInAContainer/pull/1/files
cc @glennc

Thank you @friism. That makes a lot of sense. I'll rework the doc based on your feedback.

@kendrahavens awesome, let me know if I can help.
It's a little contrived, but here's one way you could do the flow:

docker run -v ${PWD}:/app --workdir /app microsoft/dotnet:1.1.0-sdk-msbuild-rc4 dotnet new mvc
Add Dockerfile similar to this
Show that it builds and runs
Show how to add the .deploy Dockerfile
Do the scripting to copy build output from builder to deploy container as done here.

Any movement on this? We'd love to get it in!

@mstanleyjones Right now we are rewriting this sample to build the app in an sdk container and then run in a runtime container.  This way the user avoids needing .NET Core installed on their local machine. We are considering the work on multi-stage builds that looks right for this scenario. So our Dockerfile would look somewhat like:
FROM microsoft/dotnet:1.1-sdk-msbuild
AS build
WORKDIR /app

# copy csproj and restore as distinct layers
COPY dotnetapp.csproj .
RUN dotnet restore

# copy and build everything else
COPY . .
RUN dotnet publish -c Release -o out
ENTRYPOINT ["dotnet", "out/dotnetapp.dll"]

FROM microsoft/dotnet:1.0-runtime
WORKDIR /app
COPY --context=build out .
ENTRYPOINT ["dotnet", "dotnetapp.dll"]

Should I close this and open a new PR when the new sample is ready?

It is up to you. What is the COPY . . about? I've never seen that syntax before.

Cool! COPY is just like Add, but preferred because it is more transparent. It copies files from a source to a destination. The . is the current directory.

We are considering the work on multi-stage builds that looks right for this scenario

😍

What is the overlap between this and the recently-published https://docs.docker.com/compose/aspnet-mssql-compose/ ?

We'd like to have an ASP.NET core example that demonstrates how to build with the onbuild image and deploy with the much-smaller dotnet runtime image. The doc you mentioned covers a compose scenario while there is the simpler "Dockerize an app" scenario that could be a good addition to the Docker engine examples section of the documentation.

Multi arch will also change this, along with mutli-stage build.

Any news?

Any news?

Sorry for not responding sooner! We've been holding off on merging any multi-stage build samples into our samples and guidance repos until it is part of the stable Docker for Windows channel. This shouldn't hold up adding a .NET sample to your docs though! I simply hadn't gotten to it.

Please remove the stalled label when you are ready for us to review this one again.

I can't track the place where @thaJeztah told you to use e.g. but I think it is better to say for example, in the text flow, or just leave that off. Popping into Latin that nobody remembers what it stands for can be problematic for people whose first language is not English, and the amount of benefit you get from it is very small.

@mstanleyjones Could you remove the stalled tag? I believe I've addressed all the requested changes.

@mstanleyjones @thaJeztah Hey folks, are there any more changes I can make? I see the deploy/netlify preview failed. Is there anything I can fix to get it passing?

I removed the stalled label. You can make Netlify start again by amending and force-pushing the commit. Let me checkout this PR and verify that it builds locally, though.

FYI there are some mistakes in the YAML of the file. You can't word-wrap in the YAML without changing the syntax of it. I'll push a commit that fixes that after I finish testing locally.

I found a few more problems, still working on this. I'll push all the commits I've added when I get this into a better state.

@mstanleyjones Thank you so much for your help on this!

@johndmulhausen I tested this locally and it works fine. Netlify is busted thinking it's against the vnext-engine branch. Can you please squash and merge this, and make sure to clean up the commit message when squashing? Thanks!

Thanks for the review @mstanleyjones !

authors: friism glennc johndmulhausen kendrahavens mstanleyjones


text:
Current compose is 1.14.0

On https://github.com/docker/compose/releases, the latest version is 1.14.0.
Thanks !

@shin- PTAL and push anything relevant into vnext-compose, and ping me when you want to merge into master.

authors: guillaumerose mstanleyjones


text:
Remove typo return preventing Markdown link from working as intended

Proposed changes
Edited text to make it actually work as a link as intended.

Deploy preview for docsdocker ready!
Built with commit 910414eda33caff0da2c9f7cbbe905817086252e
https://deploy-preview-8216--docsdocker.netlify.com

authors: GordonTheTurtle ntravis


text:
Volume source on host garbled when mounted into container by docker-1.5.0

I start my container with (not using the new --read-only flag):
docker run […] --env PULSE_SERVER=unix:/tmp/pulse-unix --volume /run/user/10000/pulse/native:/tmp/pulse-unix devurandom/firefox

/run/user/10000/pulse normally looks like this:
$ ls -ln /run/user/10000/pulse/
total 4
srwxrwxrwx 1 10000 10000 0 Feb 17 11:01 native
-rw------- 1 10000 10000 5 Feb 17 11:01 pid

After executing above docker command with docker-1.5.0, the directories look like this:
$ ll /run/user/
total 0
drwxr-xr-x  4 root    root      80 Feb 17 10:40 ./
drwxr-xr-x 35 root    root    1220 Feb 17 10:40 ../
drwxr-xr-x  3 root    root      60 Feb 17 10:39 10000/
drwx------  2 dirmngr dirmngr   40 Feb 17 10:39 121/
$ ll /run/user/10000/
total 0
drwxr-xr-x 3 root root 60 Feb 17 10:39 ./
drwxr-xr-x 4 root root 80 Feb 17 10:40 ../
drwxr-xr-x 3 root root 60 Feb 17 10:39 pulse/
$ ll /run/user/10000/pulse/
total 0
drwxr-xr-x 3 root root 60 Feb 17 10:39 ./
drwxr-xr-x 3 root root 60 Feb 17 10:39 ../
drwxr-xr-x 2 root root 40 Feb 17 10:39 native/
$ ll /run/user/10000/pulse/native/
total 0
drwxr-xr-x 2 root root 40 Feb 17 10:39 ./
drwxr-xr-x 3 root root 60 Feb 17 10:39 ../

Note that the whole user directory is suddenly owned by root, and that the former socket native now became a directory.
Everything works as expected with docker-1.4.1. I am using versions from the Docker PPA on Ubuntu 14.04.

Can you show your full command? Your ellipsized example doesn't even show --read-only being used.
I can't duplicate:
# docker run --read-only -v /run/user/$(id -u)/pulse/native:/tmp/pulse-unix -tid busybox sh
ae18de6cfe4c17b6f933b8fb89ec1c0749490c7894397343e738b7c1fa318c37

# ls -la /run/user/$(id -u)/pulse/
total 4
drwx------ 2 phemmer adm  80 2015/02/11-19:30:02 ./
drwx------ 5 phemmer adm 100 2015/02/11-19:30:02 ../
srwxrwxrwx 1 phemmer adm   0 2015/02/11-19:30:02 native=
-rw------- 1 phemmer adm   4 2015/02/11-19:30:02 pid

Full startup script:
#!/bin/bash

container_exists() {
        local container_name="$1"
        docker ps -a | awk '$NF=="'"${container_name}"'"{found=1} END{if(!found){exit 1}}'
}

xhost +local: || exit 1

if ! container_exists home ; then
        docker run --name home devurandom/home || exit 1
fi

if ! container_exists firefox ; then
        exec docker run --name firefox --volumes-from home --env DISPLAY=$DISPLAY --volume /tmp/.X11-unix:/tmp/.X11-unix --env PULSE_SERVER=unix:/tmp/pulse-unix --volume /run/user/10000/pulse/native:/tmp/pulse-unix devurandom/firefox
fi

exec docker start firefox

The container is usually still running from the last time, so the last exec should be the one being executed.

@devurandom Any progress on this?
Also, I'm a little confused about how your script works, even on 1.4.1, without --net=host. My understanding and experience has been that a mounted X11 socket gets overriden by the new network stack created by default.

@devurandom It has been detected that this issue has not received any activity in over 1 year. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?
Thank you!

authors: GordonTheTurtle devurandom phemmer ryneeverett

repo: docker/docker


text:
how get docker registry2.0 source code?

how get docker registry2.0 source code?

@blackfader just look here https://github.com/docker/distribution

Correct, the registry 2.0 source code is in the https://github.com/docker/distribution repository.

thinks

and registry2.0 now support proxy or cache model？

authors: DieterReuter blackfader thaJeztah


text:
Incorrect document storage-opt

The document in
./daemon/graphdriver/devmapper/README.md|273 col 34| docker -d --storage-opt dm.use_deferred_device_removal=true
But the code use dm.use_deferred_removal
1779         case "dm.use_deferred_removal":
1780             EnableDeferredRemoval, err = strconv.ParseBool(val)
1781             if err != nil {
1782                 return nil, err
1783             }

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

@rickyzhang82  Thanks for reporting, next time when you find an incorrect document, you can open
an PR to correct it. :)


text:
update and run vendor script

so there was weird whitespacing that got messed up the last time this was run, this fixes that and cleans up vendor helpers as well :)
ping @tianon @calavera @LK4D4

Bizarre :+1:
LGTM

LGTM

authors: LK4D4 jfrazelle tianon


text:
add -f to plugin inspect

depends on https://github.com/docker/engine-api/pull/376
ping @anusha-ragunathan @tiborvass

Design LTGM :angel:

@vieux : Please update this test while you are here. https://github.com/docker/docker/blob/master/integration-cli/docker_cli_plugins_test.go#L40

depends on https://github.com/docker/docker/pull/25424

@anusha-ragunathan I think I addressed all your comments.

LGTM

LGTM

docs LGTM :cat:

authors: anusha-ragunathan icecrime vdemeester vieux


text:
Build sockets/unix_socket.go for Solaris

Docker uses the methods from the github.com/docker/go-connections/sockets package to connect to unix sockets.
This PR enables this on Solaris. This has been tested and works on Solaris
This is a part of a larger effort for a native port of Docker on Solaris.
Signed-off-by: Amit Krishnan krish.amit@gmail.com

LGTM

LGTM

authors: amitkris calavera cpuguy83

repo: docker/go-connections