:erlang.system_time vs :os.system_time (Time.now)

I think the :erlang version is preferred over the :os version in erlang 18, because :erlang supports time warp and is a monotonically increasing time (:os is not).

That's probably a good change to make, I also need to update the measure/elapsed functions to use monotonic_time instead of the current diffing method. I'll add that to my TODO for the next release.

After looking into some past issues, i saw the reason why you changed it to :os was because:
https://github.com/bitwalker/timex/issues/112

Ah, sure enough, I knew I had chosen it for a reason, but going back and reviewing the documentation for this issue didn't jog my memory. I still need to make changes for measure/elapsed, so I'll keep this open as a reminder, but after reviewing that issue, I think I'll keep the current usage of :os.system_time, unless there is an alternate solution for #112 that allows us to both resolve the sleep issue while getting to use :erlang.system_time

perhaps by using some kind of configuration, allow you to set it differently in :dev and :prod

That is an option - the default config could use :os.system_time, and it could be overridden to allow the use of :erlang.system_time, something like:
config :timex,
  system_time_source: :os # or :erlang

ah! thanks

I've added this (though not yet committed to master), so it will show up in a future release. I'll close this for now, but I'll update this thread when a release is pushed and we can reopen it if there are issues.


How to add a blogroll?

This theme is really coooool, but I didn't find how to add a blogroll in the demo. Did I miss it?

There is no blog roll. Feel free to add one and submit a PR.
Thanks


How do you calculate the "offset" and "scales" on cityflow?

Can you describe step by step on cityflow_s01 and cityflow_s02? Thank you :)

Hi @SasinPhimsiri,
Those cameras have overlaps, so I took one reference camera (which will be scale 1), and I picked a vehicle in the beginning of the video and one at the end, and checked the elapsed time in seconds. Now if we do the same on other cameras, and:

the time elapsed on the reference camera is $t_1$
same event took $t_2$ on the second camera
then the scale of camera 2 is $t_2 / t_1$

I calculated the offsets similarly, by picking the appearance of the same vehicle in the beginning of the video (say $t_1$ on the reference. and at $t_2$ on the other camera), then the offset is $t_1 - t_2$.
If the cameras don't have overlaps, it's more difficult I guess. Probably one can do it by picking a few vehicles and checking the differences in their transition times. (which is needed anyway for configuring the transition windows)


MOTR-252 DMAQC phenotypic data release

Key Changes:

Added metadata for the DMAQC phenotype data release.
Extracted the data release descriptions JSX rendering code from the release page component to new external components.
Pinned react-particles-js to v2.7.1 to remove unit test warnings.
Added @storybook/preset-create-react-app dependency to comply with Storybook warnings.

Merged MOTR-252


sync

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

944 of 1093 (86.37%)  changed or added relevant lines in 29 files are covered.
56 unchanged lines in 5 files lost coverage.
Overall coverage increased (+2.9%) to 58.694%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

skrf/io/csv.py
1
2
50.0%

skrf/mathFunctions.py
33
34
97.06%

skrf/vi/vna_old.py
0
1
0.0%

skrf/calibration/calibration.py
1
3
33.33%

skrf/media/rectangularWaveguide.py
3
5
60.0%

skrf/vi/vna/keysight_pna.py
0
2
0.0%

skrf/notebook/bokeh_.py
0
3
0.0%

skrf/plotting.py
1
4
25.0%

skrf/frequency.py
57
61
93.44%

skrf/io/general.py
16
20
80.0%

Files with Coverage Reduction
New Missed Lines
%

skrf/io/touchstone.py
1
83.09%

skrf/vectorFitting.py
2
79.81%

skrf/networkSet.py
4
75.41%

skrf/tests/test_network.py
20
94.92%

skrf/time.py
29
41.49%

Totals

Change from base Build 581764539:
2.9%

Covered Lines:
8240

Relevant Lines:
14039

💛  - Coveralls


[11.x] Fixes Illuminate\Http\Response to output empty string if $content is set to null

Symfony set the content to null for response()->noContent() https://github.com/symfony/http-foundation/blob/e88a66c3997859532bc2ddd6dd8f35aba2711744/Response.php#L246-L249
This cause issue with PSR-7 HTTP Stream in Octane

fixed laravel/octane#972

Also, for the same hash you linked the $this->setContent(null);, setContent() actually uses the null-coalescing operator to convert null to an empty string:
https://github.com/symfony/http-foundation/blob/e88a66c3997859532bc2ddd6dd8f35aba2711744/Response.php#L418-L423
Maybe the problem is something else?

Does octane calls Illuminate\Http\ResponseTrait@getOriginalContent(), the Response::$original property is stored unchanged, that might be the issue.

I'm a little hesitant to follow Symfony style since their phpdoc indicate string|null while ours is mixed
Also with mixed we could potentially introduce breaking changes for application that expected that they can directly return null (maybe 🤔)

I agree, but our override at the end defers to theirs
From our current code null should end up being handled by parent::setContent($content); which already coalesces null to an empty string


[V1] Button refactor

[ ] split-menu rename to split-button

[ ] specificity max 0.3.0

[ ] have single class versus modifiers (i.e. iui-button-high-visibility))

[ ] Icon button component. Should be square

[ ] Button group sub components

[ ] Borderless active button needs active stripe

Something we might want to think about is how to make our mixins smaller, as we reuse them in several other components.
In #568, @FlyersPh9 added a iui-button-active mixin but it only has some of the active button styles, with the rest of them being located in iui-button-borderless and iui-button-default under the &.iui-active modifier.

How do we feel about this:
<button class="iui-button" data-button-type="cta">
Instead of this:
<button class="iui-button iui-button-cta">
Or this:
<button class="iui-button-cta">

have single class versus modifiers (i.e. iui-button-high-visibility))

This will result in a lot of duplicate CSS in the output.

How do we feel about this: <button class="iui-button" data-button-type="cta">

I like the data attribute but it should probably be prefixed with -iui-. Also might want to avoid the word "type" because its overused especially in JS. So something like data-iui-button-variant or even just data-iui-variant.
But one of the goals with this refactor should be to make it easier and less problematic to reuse the button styles in other components, so lets make sure this data attribute doesn't get in the way.

I have this within borderless.scss to achieve 1 / 1 aspect ratio for borderless buttons with only an icon:
.iui-button-icon:only-child {
  margin-left: 2px;
  margin-right: 2px;
}

&[data-iui-button-size='small'] .iui-button-icon:only-child {
  margin-left: 2.5px;
  margin-right: 2.5px;
}

&[data-iui-button-size='large'] .iui-button-icon:only-child {
  margin-left: 3.5px;
  margin-right: 3.5px;
}

The values are not good, but the values I think might be better once we change $iui-baseline to 12px.
I was also trying this out as a solution for further in the future when :has is better supported but unfortunately no luck:
@supports selector(:has(.iui-button-icon:only-child)) {
  :has(.iui-button-icon:only-child) {
    aspect-ratio: 1 / 1;
  }
}

If I implement the current solution we end up with 170 test image changes, 1 of which is broken because #680 hasn't been merged into the v1.0 branch yet.  Should I commit this change or hold off until later?

@FlyersPh9 can you verify the initial task list and if all is done, close this issue?

@veekeys, specificity is at 0,3,1 because of notification marker mixin which needs to be re-worked anyways #411.  The borderless icon button is not 1:1 yet, I'll submit a PR to change baseline to 12px which should make the 1:1 ratio easier to achieve.


Creating 2 entries of BLOB types with statically created map invalidates the output

If I do the following:
uint8_t out[1000]
binn obj[1];
binn_create(obj, BINN_MAP, 1000, out);
binn_map_set_blob(obj, 1, "data1", 5);
binn_map_set_blob(obj, 2, "data1", 5); // << from this point its impossible to load out[]

EDIT:
It works when using binn_map() instead of binn_create()

The same as #6

Verified and works! Thanks.


CAMEL-20381: camel-core - EIP model should include which exchange pro…

…perties they set when using the EIP.
Description

Target

[ ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ ] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

@jono-morris here is what I am working on.
If you want to help then we need to markup more EIPs on the Exchange, like what is done for split and loop. The descriptions can likely be found in the doc files, eg loop-eip.adoc etc. And make sure to set its java type etc.
We should also find out afterwards how we can take the options from the generated json file in the model, and automatic have that in the EIP docs (like its done for the EIP options itself). But this requires some changes in camel-website.

The website docs does this
// eip options: START
include::partial$eip-options.adoc[]
// eip options: END
We need something ala
// eip options: START
include::partial$eip-exchangeProperties.adoc[]
// eip options: END

Thanks, let me start by marking up some more of the EIPs

I think this PR has all the EIPs - there are only a few that uses exchange properties

Yeah there didn't seem that many of them. SagaProcessor used SAGA_LONG_RUNNING_ACTION and a number of them used Exchange properties via ExchangePropertyKey, e.g. Enricher, InterceptSendToEndpointProcessor etc. not sure if you wanted to include those.

Not all of them as some of for internal use. Enricher uses dynamic processor (toD) that sets some but I may have forgotten to add it to the label


Make --watch work with ko://

Fixes https://github.com/google/ko/issues/249
The dep-notify package doesn't know anything about ko, so we need to
trim the strict prefix before sending import paths over to it.

These non-linux/amd64 platforms really like sitting in a queue on travis.


removed unnecessary module

Removing the no longer used repository module.

This is good initiative to remove unused modules 👍 ... Along with this 'repository' module, we also should remove 'cassandra' module.
Background: Like 'repository' module 'cassandra' module is also became orphan during datastax-driver-migration project.

Oh good to know - I removed it aswell :) Thanks for the input!

Looks good and let's make sure that the functional and unit tests are passing.

@AndreaSuckro That was quick 👍
:shipit: Provided functional tests are passing on wasabi & wasabi-intuit...

Functional & unit tests verified for wasabi-os, will check later for wasabi-intuit.

All tests passing.


DSC not compiling when using windows

Describe the bug
When i try to compile the DSC in windows with the mvn clean package command it makes all the build process but it doesn't output the build complete mesage.
To Reproduce
Steps to reproduce the behavior:

Download de Dataspace connector on a windows machine
Navigate inside the folder and run mvn clean package
Wait until the build is finished
See error

Expected behavior
The build outputs build failure with the log:
2021-06-10T11:40:55,787 [main] INFO - Starting ViewAssemblerHelperTest using Java 16.0.1 on SQS-LAPTOP-37 with PID 12936 (started by jmartinez in C:\Users\jmartinez\Desktop\DataspaceConnector)
2021-06-10T11:40:55,789 [main] INFO - No active profile set, falling back to default profiles: default
2021-06-10T11:40:55,837 [main] INFO - Started ViewAssemblerHelperTest in 0.201 seconds (JVM running for 262.321)
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.259 s - in io.dataspaceconnector.view.ViewAssemblerHelperTest
[INFO] Running io.dataspaceconnector.view.ViewEqualsTests
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.55 s - in io.dataspaceconnector.view.ViewEqualsTests
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ConfigurationControllerTest.updateConfiguration_unauthorized_return500:219 » IllegalAccess
[INFO]
[ERROR] Tests run: 1031, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  05:49 min
[INFO] Finished at: 2021-06-10T11:41:15+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project dataspaceconnector: There are test failures.
[ERROR]
[ERROR] Please refer to C:\Users\jmartinez\Desktop\DataspaceConnector\target\surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Desktop :

OS: Windows 10

Hi,
I cannot reproduce the test failure (branch: main, OS: Ubuntu).
please pull the main branch again and run a mvn clean. This should have been addressed by #325.

I can compile the connector no problem on ubuntu in a VM i have in my computer. But when i try to compile it in my native windows OS i get this message.
The version i have is fresh and just donwnloaded from the github repo.

There has been an update to the test suite just this morning.
The log message you posted shows 1031 unit test, but with the change this morning there should be only 1001 unit tests when running mvn test. When running mvn verify there should be additional 34 integration test in a seperat test phase.
(Also all test have passed the github actions for windows github actions for windows).
I will check again on windows, maybe there are some flaky tests.

Ran mvn verify on Windows, branch main. Cannot reproduce test failure.

with mvn verify it still gives the error
2021-06-10T14:18:04,983 [main] INFO - Starting ViewAssemblerHelperTest using Java 16.0.1 on SQS-LAPTOP-37 with PID 8804 (started by jmartinez in C:\Users\jmartinez\Desktop\DataspaceConnector)
2021-06-10T14:18:04,985 [main] INFO - No active profile set, falling back to default profiles: default
2021-06-10T14:18:05,017 [main] INFO - Started ViewAssemblerHelperTest in 0.239 seconds (JVM running for 184.302)
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.277 s - in io.dataspaceconnector.view.ViewAssemblerHelperTest
[INFO] Running io.dataspaceconnector.view.ViewEqualsTests
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.541 s - in io.dataspaceconnector.view.ViewEqualsTests
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   ConfigurationControllerTest.updateConfiguration_unauthorized_return500:219 » IllegalAccess
[INFO]
[ERROR] Tests run: 1031, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:06 min
[INFO] Finished at: 2021-06-10T14:18:10+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project dataspaceconnector: There are test failures.
[ERROR]
[ERROR] Please refer to C:\Users\jmartinez\Desktop\DataspaceConnector\target\surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Your repository seems to be still out of date. I base this on the facts that:

There are only 1001 Unit Tests not 1031.
The ConfigurationControllerTest has been renamed to ConfigurationControllerIT.

Has this problem been solved @jmartinezsqs?

Yeah, with the last update of the code, it builds correctly on my windows machine. Thanks for the help


Month wrog grouping

Version
latest
Development Environment
Firefox dev-edition on debian 10
Current Behavior

I generate simple calendar with month view:
  var calendar = new tui.Calendar('#calendar', {
    isReadOnly: true,
    defaultView: 'month',
    taskView: true,
    week: {
      daynames: ['Domenica','Lunedi', 'Martedi', 'Mercoledi', 'Giovedi', 'Venerdi', 'Sabato'],
    },
  });

and create event from json data, loaded with createSchedules() func:
{"id":14,"category":"allday","calendarId":"1","isReadOnly":true,"start":"2019-07-06T00:00:00+00:00","color":"#fff","title":"FE143HV","body":"Scadenza"},{"id":16,"category":"allday","calendarId":"1","isReadOnly":true,"start":"2020-01-09T00:00:00+00:00","color":"#fff","title":"FE182XC","body":"Scadenza"}

why do you group events? how can I view events individually as examples:

The schedule data you created is the same as calendarId: "1".
https://nhn.github.io/tui.calendar/latest/Schedule
Can you assign values to the color, bgColor, BgColor and border Color properties when creating a schedule?


invalid interval key for script:///... stanzas

Not sure if you want a new Issue created for this, but, in addition to the default key, I'm getting:

Invalid key in stanza [script://./bin/lsof.sh] in inputs.conf, line 2: interval = 600.
With this config:

[script://./bin/lsof.sh]
interval = 600
sourcetype = lsof
source = lsof
index = os
disabled = 0

Originally posted by @mccarthyp-snet in https://github.com/splunk/vscode-extension-splunk/issues/18#issuecomment-644404577

Resolved in version 0.2.4


Mark the package as typed

See also: https://mypy.readthedocs.io/en/latest/installed_packages.html#creating-pep-561-compatible-packages
See also: https://github.com/camptocamp/c2cwsgiutils/pull/969

Error on backporting to branch 0.9, see Docker Hub actions for more information.


Implement awaitResult to synchronously wait for API results

This is an attempt to move blocking calls out of AppStoreConnectAPIService and into a Publisher function called awaitResult.
It collects up all values and returns a .success with all the published values or it returns a .failure with the Error that completed the stream
📝 Summary of Changes
Changes proposed in this pull request:

Rename ResultRenderable to Renderable
Rename previous ResultRenderer to DefaultRenderer
Adds a new ResultRenderer that renders Result types
Removes Publisher extensions to render results
Adds awaitResult Publisher extension to synchronously wait for a result of all output values or the error in the stream
Changes all Commands to use the new await call and result renderer

⚠ Items of Note
Since the Commands currently return an AnyPublisher we can't know how many elements will be returned. As such awaitResult wraps the output values in an Array meaning all JSON / YAML output is surrounded in an array.
We should discuss ways to get around this. E.g. returning something like a Future from the AppStoreConnectAPIService for commands that only emit once.
Or maybe the AppStoreConnectAPIService functions should be blocking calls that return a result.
Alternatively we await for a singular result and assert that we don't get more than one
🧐🗒 Reviewer Notes
🔨 How To Test
All existing commands should still work as expected except for the aforementioned Array wrapping

Closed in preference of merging #106


add meme_psp_gen

requested by @mmiladi

Thanks much @bgruening ! :pray:

I guess there the integration is not effective yet. meme_psp_gen is not available in fr-galaxy.
Thanks much,


Add support for passing class to custom File btn/input

This patch adds support for a button-class and input-class option in the file() method on the Form helper.
This was to allow the passing of custom classes to those elements to help with more complex styling or tweaking, or just simply (in my actual use case) passing the btn-sm class to make the button smaller.
As I needed to set up some defaults for the new array keys I altered the way in which defaults options are handled so there won't be a chain of if(isset) operations for each key.

I think this is a good idea to add ways to customize the button / input of the custom file input but using input-class, button-class, etc. options is leading to lots of extra codes. The best way to handle this will be to add to extra options, called _input and _button, which are themselves options array used for the input and the button, such as:
$this->Form->input ('myfile', [
    '_button' => [
        'class' => 'btn-sm'
    ],
    '_input' => [
        'class' => 'input-sm'
    ]
]) ;

This would allow to a real customization of the button and the input without adding extra code for each option.
I cannot do the update right now, but if you want to give it a try, feel free.

Yeah, I think I see what you mean.  I've had a crack at it, hope this is more in line with what you were thinking.  I also backed out the array merge on the default options and went for the _extractOption to be more consistent.


Create an optional instrumental track

Not persé an issue to create txt files from song files.. but i see loads of "complete" songs do not come with an instrumental version. This is sad as many people would like to sing without backing vocals (if they're brave enough)
Would it be possible to include spleeter to create an instrumental version of the song preferably through an option checkmark: "Create instrumental version"

@Baklap4  what do you mean? UltraSinger already creates an * [Karaoke].txt with instrumentals. UltraSinger uses DemucsV4 instead of spleeter, because it has slightly less noise.

Oh wow my bad i completely missed this hahah. Closing the issue 👍


Not possible to pass args or options

I am trying to pass a extension to the application but neither the proper args for pyppeteer or the options for selenium dont work
args: [
'--disable-extensions-except=/path/to/extension/',
'--load-extension=/path/to/extension/',
]
options.add_extension('./exampleOfExtensionDownloadedToFolder.crx')

Extensions in Dolphin Any are added differently, the update will have

Fixed


chore(deps): update nx workspace

:tada: This PR is included in version 9.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to handle activity where parameters is empty?

Case:
class Car < ApplicationRecord
   include PublicActivity
   enum status: { online: 1, offline: 0 }
end

c = Car.create status: :online

c.activities.count # => 1

c.update status: :online # ActiveRecord will actually update it and trigger after_update

c.activities.count # => 2

c.activities.last.parameters.empty? # => true

How would you handle this?
IMHO if possible, we should have this:
c.activities.last.parameters # => [{ status: ['online', 'online'] }]

Or
I think it is also ok to not create a new activity when ActiveRecord can't determine the changes.

This isn't meant to be paper_trail. You decide when to create records and what the params end up in the activity.


MINOR: Format AdminUtils::assignReplicasToBrokers java documentation

The assignReplicasToBrokers method has helpful but a large unformatted
javadoc comment that results in a big blob in generated html. This
change formats the comment so that generated javadoc is nice.
Here are javadoc images before and after.

retest this please.

retest this please.


Page.setExtraHTTPHeaders has no effect

page.setExtraHTTPHeaders(headers) does not have any effect in version 0.10.2. Works as expected in 0.10.1.

The headers arg changed from being an Map to an Object in 0.10.2. Check that you're using the updated signature.
https://github.com/GoogleChrome/puppeteer/blob/v0.10.2/docs/api.md#pagesetextrahttpheadersheaders

Hi Eric,
Thanks for that -- I didn't think to double check the signature. Confirmed working with 0.10.2 now after adjusting on my end. Sorry for the noise.
-M


You can upgrade exchanger and it should be fixed.
composer update florianv/exchanger


Set available actions according to level

Given that we know at what level each action becomes available, it should be possible to automatically enable and disable actions as the level changes, including cross-class actions.
However, we still need to be able to retain the ability to disable actions that we don't want to use and enable actions we always want to use, regardless of level.
Implementation notes:

Base set of available actions can be determined from the set of class levels
Two more sets of actions are persisted:

Enabled -- actions that must always be available
Disabled -- actions that must never be available

Need a button to reset the Enabled and Disabled lists -- "Reset to level X"?

This has been implemented with a button in the crafter stats view that enables all actions available at the levels defined for all the classes. Actions can still be individually disabled/enabled as desired.


version key in the manifest file

Hi! I ave this error, but le addon can run manually, ...
2022-06-02 09:15:31 ERROR (SyncWorker_4) [homeassistant.loader] The custom integration 'airthings' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details

I have delete  https://github.com/custom-components/sensor.airthings_wave folder and no more error,
sorry for inconvenience

No problem, and thanks for closing this issue.


nixos-unstable: switch failed at the unused i18n.inputMethod.fcitx5.enableRimeData

Describe the bug
Failing to switch a nixosConfiguration in a flake that follows nixos-unstable.
Getting a seemingly irrelevant message: "error: fcitx-engines is deprecated, please use fcitx5 instead".
This is despite:
❯ nix eval .#nixosConfigurations.cs-338.config.i18n.inputMethod.enabled
null
❯ nix eval .#nixosConfigurations.cs-338.config.i18n.inputMethod.package
null

Steps To Reproduce
Steps to reproduce the behavior:

I assume, you just build a nixosSystem from the current nixos-unstable channel's nixpgks. I haven't checked yet

Expected behavior
Successful build and switch
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.19, NixOS, 23.05 (Stoat), 23.05.20230314.7067edc`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - channels(ss): `"nixgl"`
 - channels(root): `"nixgl, nixos-21.05.2132.733682c3292"`
 - nixpkgs: `/etc/nixpkgs/channels/nixpkgs`
❯ nix flake metadata
...
Last modified: 2023-04-11 21:49:14
Inputs:
...
├───nixpkgs: github:NixOS/nixpkgs/3fb8eedc450286d5092e4953118212fa21091b3b
...

I had the same problem, and in my case, Home Manager turned out to be the cause by some reason (even with empty config). HM flake was pointing to the release-22.11 branch; switching to the master branch fixed the error.

Encountered same problem, fixed by updating home-manager flake.

@SomeoneSerge could you bump hm and confirm whether the issue still exists?


TS-4957: Make the use of madvise() with MADV_DONTDUMP configurable.

(cherry picked from commit 514d3fd7de5841b8a74cd32bed001db9b479764f)
Backport PR to 6.2.x

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1143/ for details.

This PR is for backport to 6.2.1

EventSystem.o
../../../iocore/eventsystem/EventSystem.cc:38:7: error: unused variable 'iobuffer_advice' [-Werror,-Wunused-variable]
int iobuffer_advice          = 0;
^

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1036/ for details.

oops
From: Leif Hedstrom<EMAIL_ADDRESS>Reply-To: apache/trafficserver<EMAIL_ADDRESS>Date: Wednesday, November 2, 2016 at 12:01 PM
To: apache/trafficserver<EMAIL_ADDRESS>Cc: John Rushford<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [apache/trafficserver] TS-4957: Make the use of madvise() with MADV_DONTDUMP configurable. (#1171)
EventSystem.o
../../../iocore/eventsystem/EventSystem.cc:38:7: error: unused variable 'iobuffer_advice' [-Werror,-Wunused-variable]
int iobuffer_advice = 0;
^
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[approve ci]

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1039/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1146/ for details.

removed unused variable in Eventsystem.cc and squashed commits.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1042/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1149/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1150/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1043/ for details.


Making Cards more Attractive

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Adding more styling to the card section like adding some shadow at the back making it more pretty and also adding some hover effect to make it look good
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Ohk , go ahead !

Ohk , go ahead !

Thanks @amanjaiman1

Ohk , go ahead !

Please make it label under ggsoc

First complete it

First complete it

Ok.

@amanjaiman1 please assign this to me , its been 1 week still no response from other contributor

@Abhinavcode13 create a new issue if you want to enhance the current card because I'm going to close this issue.


forking issues

well im by no mean a git expert but forking the project from an updated repository gives me an outdated version of it (on my local repository) and i dont seem to figure out how to fix that.
anyone here who have been through the same issue can fix ?

Once you have forked a repo, you should keep it up to date: https://help.github.com/en/articles/syncing-a-fork

Closing because it looks to be resolved. Please open again if that is not the case.


Auto-Compile and Auto-Reload of Electron/

Hello,
Thank you so much for putting this template together. I am new to Electron and this has been super helpful in getting up to speed.
I noticed that auto-reload is very easy on the Renderer process, but I have to restart "yarn dev" everytime I make changes to code in the electron/ folder (index.ts and preload.ts). Is there any way to have these files auto-compile into JS and auto-reload every time I save the files? If this is not possible, what command can I run in a separate terminal while having to "CTRL+C and yarn dev"? Can I use nodemon to handle this?
Thanks in advance

This repo just has a very simple project setup and I agree the hot reload for the electron code is missing. But because of it missing I am referencing to more advanced repositories in the Readme.
There are templates having HMR.Link


Display inconsistency fix

@WillFP
Finally found source of display bug that causes enchants to not appear and armor tiers to display as %tier%. Usually the PacketWindowItems onSend is called once per event, but sometimes it's called an additional 3 times with the windowId set to 0. This infrequent case caused the display to break because player.lastDisplayFrame was not set to empty during those additional calls. I also fixed a packet type that I think you intended to use in PacketHeldWindowItems.
I've tested this on 1.19.2 with displayframes set to true, and it works without any issues that I can see. Small bug XD
This should resolve Auxilor/EcoEnchants#299 and resolve Auxilor/EcoEnchants#303
Let me know if you want me to get any more debug info

Just fyi. I just saw a console error for the HeldItemSlot packet. I'm about to goto bed so I'll look at it tomorrow. I didn't run into any in game issues, but error not good. You prob know how to fix anyways. This packet was sent on player join
com.comphenix.protocol.reflect.FieldAccessException: Field index 0 is out of bounds for length 0
        at com.comphenix.protocol.reflect.FieldAccessException.fromFormat(FieldAccessException.java:49) ~[ProtocolLib.jar:?]
        at com.comphenix.protocol.reflect.StructureModifier.read(StructureModifier.java:218) ~[ProtocolLib.jar:?]
        at com.comphenix.protocol.reflect.StructureModifier.modify(StructureModifier.java:320) ~[ProtocolLib.jar:?]
        at com.willfp.eco.internal.spigot.display.PacketHeldWindowItems.onSend(PacketHeldWindowItems.kt:19) ~[eco-6.41.1-all.jar:?]
        at com.willfp.eco.core.AbstractPacketAdapter.onPacketSending(AbstractPacketAdapter.java:119) ~[eco-6.41.1-all.jar:?]
        at com.comphenix.protocol.injector.SortedPacketListenerList.invokeSendingListener(SortedPacketListenerList.java:195) ~[ProtocolLib.jar:?]
        at com.comphenix.protocol.injector.SortedPacketListenerList.invokePacketSending(SortedPacketListenerList.java:149) ~[ProtocolLib.jar:?]
        at com.comphenix.protocol.injector.PacketFilterManager.postPacketToListeners(PacketFilterManager.java:547) ~[ProtocolLib.jar:?]```


Do we know the value type here? Maybe we should add a // TODO?

Do we know the value type here? Maybe we should add a // TODO?
Originally posted by @ChristopheCVB in https://github.com/obs-websocket-community-projects/obs-websocket-java/pull/118#discussion_r703311475

It's a string https://github.com/obsproject/obs-websocket/blob/master/docs/generated/protocol.md#getstreamservicesettings


PQMT:[Teams admin center] The custom app UI displayed is different between the actual UI and the Learn page

[URL]
https://learn.microsoft.com/en-us/microsoftteams/manage-apps#manage-org-wide-app-settings
[Description]
"Custom apps" toggle switch description in "Org-wide ap settings" differs between the actual UI and the document site.
[Actual]
"Custom apps" toggle switch description in "Org-wide ap settings" differs between the actual UI and the document site.
[Expected]
I'd like to match the description of the "Custom apps" toggle switch in the "Org-wide ap settings" between the actual UI and the document site.
[Repro]
1.Please refer to this URL: https://learn.microsoft.com/en-us/microsoftteams/manage-apps#manage-org-wide-app-settings
Actual operating procedure:
1.Access to Teams admin center.
2.Navigate to "Teams apps" > "Manage apps" > "Org-wide app settings".
[Source]
Japan Internal Feedback
[Copied from]
https://microsoftapc.sharepoint.com/:li:/t/NTO-Japan/E2an9yHlhQJNvY3aw4pdyC8B6yClVRauKcSEEsc2k_t6rA?e=yDicRF

Thanks @v-suomori . We are updating this via the linked pull request.


removes root logger configuration

Removes root logger configuration to avoid unexpected logging behavior.  For example, before importing pwnedpasswords the application was set to log at WARN and above.  After importing, it is now set to DEBUG.
IPython 7.5.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import logging

In [2]: logging.getLogger().level
Out[2]: 30

In [3]: import pwnedpasswords

In [4]: logging.getLogger().level
Out[4]: 10

I think the tests are failing on master too maybe because it is reaching out to the API and the response has changed from when the test was written.  I'd be happy to help fix the tests.  Should I mock out the API request? Or update the expected values so it passes?

@mjhoffman65 Thanks for the PR! I think it's a good thing it touches the API, so a test update would be great. Thanks so much for your help!

@dlo Thanks for the feedback!  I updated the number of results and got two of the tests passing.
I might be missing something, but it looks like the search functionality doesn't exist on the API anymore?  I don't see any mention of the pwdpassword endpoint in the docs and calling it manually returns a 404 with an Invalid API query response.  This 404 is causing the 3rd test to fail.

@mjhoffman65 Thank you!

it looks like the search functionality doesn't exist on the API anymore

This seems to be the case. Because it's gone from the documentation now, I think it's ok to nix it from the test suite.

Thanks again @mjhoffman65!

No problem!  Any idea when this will be released to PyPI?

Hey @mjhoffman65, I realize this is super belated (I somehow missed this), but version 2.0.0 should be available on PyPi in case you were still waiting :)


imagenet-11k-place365-ch

Where can I find the label names of imagenet-11k-place365-ch  models?
http://data.mxnet.io/models/imagenet-11k-place365-ch/
Thank you very much

Please ask your questions on https://discuss.mxnet.io/, We use GitHub Issues for bugs and Feature Requests.

This might be the one, but I am not sure..please do ask on discuss.mxnet.io
http://data.mxnet.io/models/imagenet-11k/synset.txt

@nswamy No, this is not the corresponding one.
The desired classes num is 11586, while the imagenet-11k/synset.txt has 11221 classes


Too many network turns

Description:
Consider the below program,
import ballerina/http;
import ballerina/io;

public function main() returns error? {
    final http:Client clientEndpoint = check new ("http://localhost:9090", { httpVersion: "2.0", http2Settings: {http2PriorKnowledge:true}, compression: http:COMPRESSION_ALWAYS});
    foreach int i in 0 ..< 10 {
        string resp = check clientEndpoint->get(string `/greeting/${i}`);
        io:println(resp);
    }
}

For this program client has sent 11 packets.

Now consider the below program,
#!/bin/bash

URLS=""
for i in {1..10}
do
    URLS+="http://localhost:9090/greeting/${i} "
done

nghttp -y --no-dep $URLS

For this program client has only sent 3 packets.

The backend,
import ballerina/http;

service / on new http:Listener(9090, config = {httpVersion: "2.0"}) {
    resource function get greeting/[string count]() returns string {
        return "Hello, World! " + count;
    }
}

Actually I made a mistake in the previous test. Ballerina program needs to run in parallel. Hence, updated the program,
import ballerina/http;
import ballerina/io;

public function main() returns error? {
    final http:Client clientEndpoint = check new ("http://localhost:9090", { httpVersion: "2.0", compression: http:COMPRESSION_ALWAYS});
    foreach int i in 0 ..< 10 {
        _ = start getAsync(clientEndpoint, i);
    }
}

function getAsync(http:Client c, int i) returns error? {
    string resp = check c->get(string `/greeting/${i}`);
    io:println(resp);
}

Yet there is a problem. Now it creates many connections when in fact we only need one.


Method renames: Disallow attr methods, constructors

This change disallows attr_* method renames, as well as constructors. We can't rename attr_ methods because we don't yet rename fields. We only block prepare_rename when invoked at the definition, to keep it fast it succeeds for sends. The rename task fails when invoked from anywhere.
Motivation
Correctness, it doesn't make sense to rename attr methods but not the field, and we don't do field renames yet.
Test plan

See included automated tests.

Updated, ptal @jvilk-stripe? We now get the "Attribute renames are unsupported" error while renaming attr_ methods from anywhere.

👍  removed the iteration and improved the error message with your suggestion.
ptal @jvilk-stripe


Load Shedding

Summary

RFCs: $\emptyset$.
Categories: any of protocol-units

Objective
Implement load shedding for transaction flow.
Transaction Load Milestones

In the current implement only v1, pardon the uninspiring naming, is considered. I think ideally, we would transform this such that we have an enum TransactionLoadMilestone, that we increment and decrement on relevant structs.
On the full-node, implement v1 is fairly trivial, as we can report status directly to the client via the MempoolRequest API. I believe you may also be able to use the commit_transaction and reject_transaction API in a similar manner. But I have not yet confirmed.
Changelog

Testing

Outstanding issues

@mzabaluev It would be good to move these parameters out into the SuzukaConfig before going too much further.

@mzabaluev Is the above any better?


wl_display@1: error 1: invalid arguments for<EMAIL_ADDRESS>

I found a possible bug in uwac-input.c in the function set_cursor_image(...).
The problem is that this function is called twice before the on_buffer_release(...) is called. I tested it with a boolean which I set after wl_surface_commit(...) and reset after wl_buffer_destroy(...).
This can happen with particularly fast touch movements on different surfaces.
Error output:
proxy 0x8129fc0 already has listener
wl_display@1: error 1: invalid arguments for<EMAIL_ADDRESS>I'm a little unsure how to fix this. I don't know, if there is a smarter way than to set a boolean as reminder if the buffer is already destroyed.

When I check if a listerner is already registered and make no wl_surface_attach anymore, this fix the situation for me.
Commit: 249dce954e896aa3ff135b7882c56ff35a3384b6
The problem always comes if the seat->pointer_type is 0. Because this buffer will be not destroyed.

@chakuzo would be nice if you could create a pr, github is a bit messy with showing which fork the commit is from.


User is not authorized to perform: lex:RecognizeText on resource

Describe the bug
When I attempt to send an input into the generated Lex bot via the aws-lex-web-ui iframe, I receive an error of Message: "User: arn:aws:sts::[ACCOUNT]:assumed-role/lex-web-ui-CognitoIdentityPool-Z-CognitoAuthRoleV1-[ID]/CognitoIdentityCredentials is not authorized to perform: lex:RecognizeText on resource: arn:aws:lex:[REGION]:[ACCOUNT]:bot-alias/[ID]/[ID] because no identity-based policy allows the lex:RecognizeText action"
To Reproduce
Bring up the CloudFormation stack and send a message to the Lex bot.
Expected behavior
The bot should be able to handle the input message and return with a message
Please complete the following information about the solution:

[x] Version: v5.0.0
[x] Region: us-east-1
[x] Was the solution modified from the version published on this repository? No.
[x] If the answer to the previous question was yes, are the changes available on GitHub? N/A
[x] Have you checked your service quotas for the sevices this solution uses? N/A
[x] Were there any errors in the CloudWatch Logs? Not that I could find

Screenshots
N/A
Additional context
CloudFormation parameters:

DefaultKendraIndexId
-

ElasticSearchNodeCount
4

Email
<EMAIL_ADDRESS>

Encryption
ENCRYPTED

FulfillmentConcurrency
0

KibanaDashboardRetentionMinutes
43200

LexBotVersion
LexV1 and LexV2

LexV2BotLocaleIds
en_US,es_US,fr_CA

PublicOrPrivate
PRIVATE

Username
Admin

XraySetting
FALSE

I was able to resolve this issue by manually attaching the QnABot-LexBotPolicy-[ID] policy to the lex-web-ui-CognitoIdentityPool-Z-CognitoAuthRoleV1-[ID] and  lex-web-ui-CognitoIdentityPool-CognitoUnauthRoleV1-[ID] roles, so it looks like this is related specifically to the v1 roles missing a couple actions.
Note anything between brackets is my doing for obfuscation or simplicity.

Hi @ChaseIngebritson the action lex:RecognizeText is LexV2 specific so it shouldn't interfere with V1 roles.
Thanks for bringing this up. I'm looking into recreating this and will update this thread further.

Thanks! Hopefully this isn't related to the AWS Lex Web UI, but I can move the issue if so. It's a bit difficult to discern which of the two projects is causing the issue.

This error is from lex-web-ui and is related to that project instead of qnabot. That said, RecognizeText is an api on Lex V2. The V1 role by definition would not contain the permissions to invoke RecognizeText. The similar "V2" role also created by LexWebUi would provide a policy to allow RecognizeText.
I suspect you initially deployed LexWebUi using a V1 based bot name and then switched it over to a V2 based bot id by updating CF template parameters. Switching a deployed LexWebUi between V1 and V2 by changing bot relevant template parameters is not supported and will not work correctly.
You would need to deploy a new LexWebUi and specify the V2 parameters only: BotId, BotAliasId, and LocaleId. This LexWebUi will use the "V2" based role using policies that support LexV2.
Can you try a new deployment filling in just V2 parameters? That is, leave BotName empty.

Thank you for the quick response and apologies for the delay on testing this, I got sucked into a couple other projects. I'll update with findings once I'm able to get a chance to test the reboot.


I would like to able to download, extract and run Ollama on an Intel GPU

In order to use Ollama easily on Intel discrete GPU, I would like to able to download the ollama binary that is built with Intel OneAPI SYCL runtime directly.
Example:
curl -L https://ollama.com/download/ollama-linux-amd64-sycl.tgz -o ollama-linux-amd64-sycl.tgz
sudo tar -C /usr -xzf ollama-linux-amd64-sycl.tgz

I am willing to contribute this feature if needed.

Intel discrete GPUs is being tracked via #1590


Use CommonJS build as NPM main module

with installation instructions in README

:+1:
We never published 2.7.1?

Yeah, 2.7.1 got skipped on NPM. 2.7.2 will include those changes.


Support ssh remotes

Fix https://github.com/Microsoft/vscode-pull-request-github/issues/273 . The logic in this PR is using the same scheme as the origin one (or where the PR is targeting) for the newly created remotes. For example, if the origin remote is using ssh and we try to create a new remote for a pr on the origin remote, we should use ssh instead of https.

Happily :)

Added test cases for

type checking. At this moment, we will see both SSH or SCP like Uris as SSH protocol (which means we don't really have git:// scheme detection) but it should be fine.
update method for Protocol. It's mutable so the name is more accurate than with as @queerviolet pointed out.

LGTM :)


Updated CRDs to include  field

For each of the following check the box when you have verified either:

the changes have been made for each applicable version
no changes are required for the item

Affected versions:

[x] Latest
[ ] 1.1
[ ] 1.0

The CSV is responsible in OLM installs for

[ ] Operator permissions
[ ] Operator deployment
[ ] Operand permissions
[x] CRDs

The operator.yml is responsible in non-OLM installs for

[ ] Operator permissions
[ ] Operator deployment

The ansible role is responsible in non-OLM installs for:

[ ] Operand permissions
[x] CRDs

The ansible role is always responsible for:

[ ] Operand deployment

If this PR updates a release or replaces channel

[ ] I created a new z release directory in deploy/olm-catalog/konveyor-operator
[ ] I updated channels in the konveyor-operator.package.yaml
[ ] I created a new release directory in deploy/non-olm
[ ] I created or updated the major.minor link in deploy/non-olm
[ ] Updated the .github/pull_request_template.md Affected versions list

Part of https://github.com/konveyor/mig-controller/pull/452, should be merged simultaneously

"For each of the following check the box when you have verified either:
the changes have been made for each applicable version
no changes are required for the item

"


Pseudo commit

https://github.com/SAP/abap-file-formats-tools/pull/158 will fix the unit test

closes #163


Revisited descriptions.

Updated the descriptions for all the products with the difference
between versioned and unversioned release. Also added a specific
description for Ubuntu Preview.
Co-authored-by: Didier Roche<EMAIL_ADDRESS>

Yeah, this is some duplication but I think this is the best path forward. We may add other keywords or something else, so let’s use this mecanism rather than attempting doing something too generic.


Added contact us page

Description
Added the contact us page
Please include a summary of the change and which issue is fixed.
Fixes #51
List any dependencies that are required for this change
NA
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
On my local host
UI /UX changes
Attach gif or screenshot for changes.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

please remove conflicts then i will merge this pr @harshb02

please remove conflicts then i will merge this pr @harshb02

On it

remove the contact us section on the main page and change the navbar link to this page.

Done with the changes you have requested and have resolved the conflicts also @ravikr126

Resolved the changes @harikesh409

remove the contact us section on the main page and change the navbar link to this page.

This is not done.

remove the contact us section on the main page and change the navbar link to this page.

This is not done.

now it is done @harikesh409


rel branch, generate and generate_stream not working

when using generate endpoint it is giving
{'error': 'generate expects model to produce exactly 1 response, use generate stream for model that generates various number of responses'}
when using generate_stream endpoint it is returning empty response

Please share end to end steps to reproduce your issue.

i might just got the solution that is to recompile the model using tensorRT-LLM branch
but for Clearity i will just explain all the steps
i have used tensorRT LLM - 0.5.0 to compile my LLama-70B model and yi-34b llamafied model into int4 awq quantized model.
then i use tensorrt llm backend - 0.5.0 with triton inference server to deploy my model and it is working fine for generate, generate_stream and also grpc inflight streaming as well.
but Stop words is not working in any of these 3 in 0.5.0 and i got to know that it updated in later version so i switch to rel branch and main branch for tensorRT llm backend and use my previous compiled 0.5.0 version model on the version and the above issue occurred.
inflight grpc is working fine in rel branch and main branch but ensemble is not working and stop words is still not working

Thank you for the update. Do you still have question? It looks you still have issue on stop words and ensemble. Could you describe more?

Yes, so after the previous message. i just recompile the model using the main branch for tensorRT LLM and tensorrt llm backend.
as i was going to use awq-4bit model i first use 0.5.0 branch to create .pt model of awq as .npz model from latest branch is not giving good responses. so after compiling the model i use tensorrt llm backend to deploy the model and now generate and generate_stream is working and sometime stop word is working fine to. But its like not all the time or not all the words are capable of stop word.
Example - Prompt
"This the conversation between two pirated Luffy and Zoro and they are good friends
Luffy: Hey Zoro, how are you? My name is Luffy.
Zoro:"
this is my prompt and stop word is "Luffy:" so that it should stop after generate Zoro: message but it didn't stop at stop word. and when i replace stop word with "Zoro" it works but yes not worked with "Zoro:". I just want to understand is there any criteria of detemining what should be our stop word like Symbol should present or not "Zoro" worked but "Zoro:" not worked
any other guideline or any help that would help me to solve this problem.

You could check the stop_words_id in model.py of preprocessing and the output_ids in model.py of postprocessing. Sometimes, the mapping of stop_words -> stop_words_ids is not unique and the output_ids does not contains the stop_words_ids.

@byshiue yes that is the actual problem as token that is passing in stop words id is never generated as they have different token ids


Set the adapter title to the widget's name

The adapter's title is always set to "OWF7 Adapter".  Set the title to the following:

The "name" from the system API for that widget.
The widget's host and path, followed by " -- OWF Widget"  (e.g. "example.com/widget/myWidget.html -- OWF Widget"

The "name" from the system API for that widget.

The name is only obtainable if the GUID of the widget is known. Widget param's are passed to the iframe initialization through the hash of the adapter, should the course of action be to gather the GUID from the hash else fall back to option 2?
A bulk get of the system.api /application resource list could match a URL -> launchUrl -> GUID. but has the side-effect of potentially longer load time if the user has a large amounts of applications. Also I believe launchUrl's arent managed as strictly unique so there can be issues of multiple application listings able to claim as a match.

Is the title needed at time of widget instantiation?
The title is not included in the iframe's window.name config in owf7, thus gathering the data from system.api asynchronously while the iframe is loaded seems to be a viable option.
generateIframeName:function (url, objectId, widget, paneType, launchData, isLocked) {
                var iframeNameObj = {
                    id:objectId,

                    containerVersion:Ozone.version.owfversion,
                    webContextPath:Ozone.config.webContextPath,
                    preferenceLocation:Ozone.config.prefsLocation,

                    relayUrl:this.getContainerRelay(),
                    lang:Ozone.lang.getLanguage(),
                    currentTheme:Ozone.config.currentTheme,
                    owf:true,
                    layout:paneType || "",
                    url:url,
                    guid:widget.widgetGuid,
                    version:widget.version || 1,
                    locked: isLocked || false
                };

                if (launchData) {
                    iframeNameObj.data = launchData;
                }

                //return this json object as formatted string which is appropriate for being put in the name attribute of the
                //iframe tag.
                return iframeNameObj;

            }

handled in #16


Try to fix security exception

Description
Fixes #1413 I hope.
I added permission check on location manager registration phase, to solve the problem permissions are getting on runtime after Android 6.0
Tests performed
I couldn't tested it, since I couldn't reproduce the bug. But it didn't break anything as far as I can say. Help of @97balakrishnan wanted to test.

I am getting this error now.
04-06 17:23:09.376 7076-7076/fr.free.nrw.commons.debug E/AndroidRuntime: FATAL EXCEPTION: main
    Process: fr.free.nrw.commons.debug, PID: 7076
    java.lang.RuntimeException: Unable to start activity ComponentInfo{fr.free.nrw.commons.debug/fr.free.nrw.commons.nearby.NearbyActivity}: java.lang.ClassCastException: fr.free.nrw.commons.CommonsApplication cannot be cast to android.app.Activity
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2426)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2490)
        at android.app.ActivityThread.-wrap11(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1354)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5443)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
     Caused by: java.lang.ClassCastException: fr.free.nrw.commons.CommonsApplication cannot be cast to android.app.Activity
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onStart(NearbyActivity.java:264)
        at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1260)
        at android.app.Activity.performStart(Activity.java:6276)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2389)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2490)
        at android.app.ActivityThread.-wrap11(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1354)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5443)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)

This should fix the issue @97balakrishnan , can you please test?

Now Iam getting this eror log.
I think the permission request is called multiple times
I'll upload screencast in some time.

04-06 20:32:09.311 5939-5939/fr.free.nrw.commons.debug E/AndroidRuntime: FATAL EXCEPTION: main
    Process: fr.free.nrw.commons.debug, PID: 5939
    java.lang.StackOverflowError: stack size 8MB
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
        at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:394)
        at fr.free.nrw.commons.location.LocationServiceManager.requestPermissions(LocationServiceManager.java:71)
        at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:97)
        at fr.free.nrw.commons.nearby.NearbyActivity.onRequestPermissionsResult(NearbyActivity.java:161)
        at android.app.Activity.requestPermissions(Activity.java:3827)
    	at android.support.v4.app.ActivityCompat.reques
04-06 20:32:09.409 5939-5939/fr.free.nrw.commons.debug E/JavaBinder: !!! FAILED BINDER TRANSACTION !!!  (parcel size = 1523252)
04-06 20:32:09.410 5939-5939/fr.free.nrw.commons.debug E/AndroidRuntime: Error reporting crash
    android.os.TransactionTooLargeException: data parcel size 1523252 bytes
        at android.os.BinderProxy.transactNative(Native Method)
        at android.os.BinderProxy.transact(Binder.java:503)
        at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:4453)
        at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:90)
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
        at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)

We are having progress, thanks for your cooperation I can be working again after 4 hours. It would be great if you could be online too, is it possible according to your time zone @97balakrishnan

Sorry @neslihanturan it'll be 1am here

I added these few lines to requestLocationPermission() and it seems to be working fine.
@neslihanturan  Can you please try this when you start coding and check if there's no problem.
private boolean PERMISSION_UNDEFINED=true;
private void requestLocationPermissions() {
        if (!isFinishing()&&PERMISSION_UNDEFINED) {
            PERMISSION_UNDEFINED=false;
            locationManager.requestPermissions(this);
        }
    }

But in this case requesting permission is enough to set our Boolean, what if user doesn't give permission? I think instead of a Boolean we should check if permission is granted. Then it should be solved.

Well, in that case what you are suggesting is , if the user doesn't grant permission we repeatedly show permission request to the user until he grants. That gould not be done right?

Sorry it was a typing mistake. *Could
Not Gould :)

@97balakrishnan ready to test again:)

@misaochan this also requires testing for someone who can't reproduce the bug. Becasue there is possibility that it can break something.

Hi @neslihanturan , I tested this on an API 25 emulator by following the steps:

Log into the app
Open nearby places
Grant permission for location access

I don't get the crash mentioned, however Nearby places do not load in this case even with coordinates being sent to the emulator multiple times. The progress bar runs forever. Do they load for you? However, once I go to another activity and then return to Nearby, they load perfectly fine.
Logs:
04-10 18:37:59.890: D/NearbyActivity(4029): Skipping update of nearby places as location is unavailable
04-10 18:37:59.892: D/LocationServiceManager(4029): Provider network disabled
04-10 18:37:59.893: D/NearbyActivity(4029): GPS is enabled
04-10 18:37:59.894: D/NearbyActivity(4029): Skipping update of nearby places as location is unavailable
04-10 18:37:59.906: D/LocationServiceManager(4029): Provider network disabled
04-10 18:37:59.908: D/NearbyActivity(4029): Skipping update of nearby places as location is unavailable
04-10 18:37:59.922: D/LocationServiceManager(4029): Provider network disabled
04-10 18:38:06.928: D/LocationServiceManager(4029): gps's status changed to 1
04-10 18:38:30.252: D/LocationServiceManager(4029): gps's status changed to 1
04-10 18:38:42.256: D/LocationServiceManager(4029): gps's status changed to 1
04-10 18:38:55.757: D/LocationServiceManager(4029): gps's status changed to 1

Oh:( This PR has a damnation I think. My tests on 25 were fine. Let me look at it.

Yeah, I agree. Honestly, if the user refuses permission, I think it is OK for them to just be sent back to Home with a Toast or Dialog saying "Nearby places cannot be loaded without location permissions".  If they navigate to Nearby again, they would be asked for permissions again. That might make the permission logic more straightforward.

I believe this time the problem is solved @misaochan . I have tested it on API 25 and 19

Hmmm... okay. I tested this on API 25 emulator as usual.
The good news is: The new permission logic is simplified and works quite well. I tried denying permissions the first time around and it does what it is supposed to do, display a message and sends me back to Contributions.
The bad news is: Granting permissions still doesn't work. I thought it might have been because I only turned on GPS (sent coords to emulator) AFTER the loading started, so I tried again with coords sent earlier. Still runs forever.
Might be worth inserting a log to check if onRequestPermissionsResult in NearbyActivity is actually being called?
Logs:
04-12 01:06:25.172: D/NearbyActivity(7268): Skipping update of nearby places as location is unavailable
04-12 01:06:25.172: D/LocationServiceManager(7268): Provider network disabled
04-12 01:06:25.173: D/NearbyActivity(7268): GPS is enabled
04-12 01:06:25.174: D/NearbyActivity(7268): Skipping update of nearby places as location is unavailable
04-12 01:06:25.193: D/NearbyActivity(7268): Skipping update of nearby places as location is unavailable
04-12 01:06:25.224: D/LocationServiceManager(7268): gps's status changed to 1
04-12 01:06:37.177: D/LocationServiceManager(7268): gps's status changed to 1

On a side note, when I tried to go back to Contributions while Nearby was loading forever, I got this crash. However, I think it might not be related to these changes.
04-12 01:00:08.187: E/MessageQueue-JNI(6777): java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.Reference.get()' on a null object reference
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.support.design.widget.BottomSheetBehavior.onInterceptTouchEvent(BottomSheetBehavior.java:299)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.support.design.widget.CoordinatorLayout.performIntercept(CoordinatorLayout.java:460)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.support.design.widget.CoordinatorLayout.onInterceptTouchEvent(CoordinatorLayout.java:499)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2175)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:413)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1808)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.app.Activity.dispatchTouchEvent(Activity.java:3061)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:375)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.View.dispatchPointerEvent(View.java:10243)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4438)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4306)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3906)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3872)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3999)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3880)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4056)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3906)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3872)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3880)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:6246)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:6220)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:6181)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:6349)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:185)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.os.MessageQueue.nativePollOnce(Native Method)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.os.MessageQueue.next(MessageQueue.java:323)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.os.Looper.loop(Looper.java:136)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at java.lang.reflect.Method.invoke(Native Method)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-12 01:00:08.187: E/MessageQueue-JNI(6777): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
04-12 01:00:08.187: D/AndroidRuntime(6777): Shutting down VM
04-12 01:00:08.187: D/AndroidRuntime(6777): --------- beginning of crash
04-12 01:00:08.187: E/AndroidRuntime(6777): FATAL EXCEPTION: main
04-12 01:00:08.187: E/AndroidRuntime(6777): Process: fr.free.nrw.commons.debug, PID: 6777
04-12 01:00:08.187: E/AndroidRuntime(6777): java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.Reference.get()' on a null object reference
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.support.design.widget.BottomSheetBehavior.onInterceptTouchEvent(BottomSheetBehavior.java:299)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.support.design.widget.CoordinatorLayout.performIntercept(CoordinatorLayout.java:460)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.support.design.widget.CoordinatorLayout.onInterceptTouchEvent(CoordinatorLayout.java:499)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2175)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2632)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2264)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:413)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1808)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.app.Activity.dispatchTouchEvent(Activity.java:3061)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:375)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.View.dispatchPointerEvent(View.java:10243)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4438)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4306)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3906)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3872)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3999)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3880)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4056)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3906)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3872)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3880)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3853)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:6246)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:6220)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:6181)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:6349)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:185)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.os.MessageQueue.nativePollOnce(Native Method)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.os.MessageQueue.next(MessageQueue.java:323)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.os.Looper.loop(Looper.java:136)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at java.lang.reflect.Method.invoke(Native Method)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-12 01:00:08.187: E/AndroidRuntime(6777): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Interesting. So I inserted the log, and it seems that indeed onRequestPermissionsResult is called. I am not sure why place updates are still skipped. I'm sure the emulator isn't the problem, since when permissions aren't involved (e.g. the second time I use Nearby onwards), the places display fine.
04-12 01:13:34.172: D/NearbyActivity(8293): Nearby activity's onRequestPermissionsResult called
04-12 01:13:34.172: D/NearbyActivity(8293): Nearby activity's onRequestPermissionsResult called and if clause satisfied
04-12 01:13:34.206: D/NearbyActivity(8293): Skipping update of nearby places as location is unavailable
04-12 01:13:34.208: D/NearbyActivity(8293): GPS is enabled
04-12 01:13:34.208: D/NearbyActivity(8293): Skipping update of nearby places as location is unavailable
04-12 01:13:34.210: D/LocationServiceManager(8293): Provider network disabled
04-12 01:13:34.212: D/NearbyActivity(8293): Skipping update of nearby places as location is unavailable

Hmm maybe I miss this issue since I also check onRequestPermissionResult and everything seems nomal to me. Continuing to work on this haha:D

@misaochan I suspect you should see Illegal argument exception (it should be caught) in your error logs, when nearby loads forever. Am I right?

My latest changes are tested on 19 and 23 emulators and 16 real device, works with no problem. Please inform me if you encounter some.

Just tested this on API 25. I did not get an exception previously, but I do get the Illegal Argument Exception now, but not the same one as you got in #1435 . Mine is:
04-13 01:24:17.498: E/LocationServiceManager(4078): Illegal argument exception
04-13 01:24:17.498: E/LocationServiceManager(4078): java.lang.IllegalArgumentException: invalid provider: null
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.location.LocationManager.checkProvider(LocationManager.java:2248)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:466)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:102)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.onStart(NearbyActivity.java:275)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1248)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.Activity.performStart(Activity.java:6696)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2628)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.ActivityThread.-wrap12(ActivityThread.java)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.os.Handler.dispatchMessage(Handler.java:102)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-13 01:24:17.498: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
04-13 01:24:17.499: E/LocationServiceManager(4078): Security exception
04-13 01:24:17.499: E/LocationServiceManager(4078): java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.os.Parcel.readException(Parcel.java:1684)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.os.Parcel.readException(Parcel.java:1637)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:614)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:887)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:471)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:105)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.onStart(NearbyActivity.java:275)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1248)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.Activity.performStart(Activity.java:6696)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2628)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.ActivityThread.-wrap12(ActivityThread.java)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.os.Handler.dispatchMessage(Handler.java:102)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-13 01:24:17.499: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
04-13 01:24:17.500: D/NearbyActivity(4078): GPS is enabled
04-13 01:24:17.523: D/NearbyActivity(4078): GPS is enabled
04-13 01:24:17.590: E/LocationServiceManager(4078): Illegal argument exception
04-13 01:24:17.590: E/LocationServiceManager(4078): java.lang.IllegalArgumentException: invalid provider: null
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.location.LocationManager.checkProvider(LocationManager.java:2248)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:466)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:102)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.refreshView(NearbyActivity.java:353)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.access$000(NearbyActivity.java:53)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity$2.onReceive(NearbyActivity.java:326)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1122)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Handler.handleCallback(Handler.java:751)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Handler.dispatchMessage(Handler.java:95)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
04-13 01:24:17.590: E/LocationServiceManager(4078): Security exception
04-13 01:24:17.590: E/LocationServiceManager(4078): java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Parcel.readException(Parcel.java:1684)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Parcel.readException(Parcel.java:1637)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:614)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:887)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:471)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:105)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.refreshView(NearbyActivity.java:353)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity.access$000(NearbyActivity.java:53)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at fr.free.nrw.commons.nearby.NearbyActivity$2.onReceive(NearbyActivity.java:326)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1122)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Handler.handleCallback(Handler.java:751)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Handler.dispatchMessage(Handler.java:95)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at android.app.ActivityThread.main(ActivityThread.java:6119)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
04-13 01:24:17.590: E/LocationServiceManager(4078): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Sorry. :/ I will test on my real device after this, but it is more difficult to get logs from there since it hits the buffer limit quickly.

Tried this with real device, API 24. This time there is no progress bar, but a blank screen after I enable permissions. If we haven't found a fix by Saturday, I'll try and take a look at the code too and see if we can find an easier way to fix this. Don't stress out too much about it. :)
04-13 01:32:51.646: E/LocationServiceManager(9261): Illegal argument exception
04-13 01:32:51.646: E/LocationServiceManager(9261): java.lang.IllegalArgumentException: invalid provider: null
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.location.LocationManager.checkProvider(LocationManager.java:2248)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:466)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:102)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.nearby.NearbyActivity.onStart(NearbyActivity.java:275)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.Activity.performStart(Activity.java:6929)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2887)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2985)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.ActivityThread.-wrap14(ActivityThread.java)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.os.Handler.dispatchMessage(Handler.java:102)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at android.app.ActivityThread.main(ActivityThread.java:6692)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
04-13 01:32:51.646: E/LocationServiceManager(9261): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)
04-13 01:32:51.674: E/LocationServiceManager(9261): Security exception
04-13 01:32:51.674: E/LocationServiceManager(9261): java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.os.Parcel.readException(Parcel.java:1693)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.os.Parcel.readException(Parcel.java:1646)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:681)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:887)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.location.LocationManager.requestLocationUpdates(LocationManager.java:471)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.location.LocationServiceManager.requestLocationUpdatesFromProvider(LocationServiceManager.java:131)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.location.LocationServiceManager.registerLocationManager(LocationServiceManager.java:105)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at fr.free.nrw.commons.nearby.NearbyActivity.onStart(NearbyActivity.java:275)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.Activity.performStart(Activity.java:6929)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2887)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2985)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.ActivityThread.-wrap14(ActivityThread.java)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1635)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.os.Handler.dispatchMessage(Handler.java:102)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.os.Looper.loop(Looper.java:154)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at android.app.ActivityThread.main(ActivityThread.java:6692)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at java.lang.reflect.Method.invoke(Native Method)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468)
04-13 01:32:51.674: E/LocationServiceManager(9261): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)
04-13 01:32:51.679: D/NearbyActivity(9261): GPS is enabled
04-13 01:32:51.743: D/NearbyActivity(9261): GPS is enabled