API v3 branch updates/fixes

Hi @tomlandia
UPDATE: 2/6/2017
-profiles now displaying (you need to check the online or photos box and uncheck to get them to show)
profiles = _.reject(response.profiles, function(profile) {
changed to
profiles = _.reject(response.data.profiles, function(profile) {
I'll attach files here, and I've got it to kind of authenticate on the Fuckr side but  I don't think it's correct still.  Also, don't edit your profile, or instant ban. Use at your own risk
It will show 100 profiles right now.  The only data that shows currently is the age, and if the profile has it, the distance, but do to settings that is currently only in km.  If you click on the settings, it gives you can error, but this is a step in the right direction.
https://drive.google.com/file/d/0BxSmknffFGTnaFpKdmY4NEMtUmM/view?usp=sharing
The above link is just the main files, without executables.  This next link has the Windows 64 bit whole package.
https://drive.google.com/file/d/0BxSmknffFGTnMkNHcU5zX29WSW8/view?usp=sharing
So yes, the old API (v2) is down.
I'm working with the new one (v3), and have fixed some things.  I typically work with the fuckr.js as I'm on Windows 7, 64-bit.  But have checked some of the coffee files too.
SIGNUP: YOU COULD LOGIN, BUT NOT SIGNUP/CREATE PROFILE
The program would sit and spin, but never contacted the server.  The issue here was that a function was not being processed as a function, and would stall out.  Also, there is already a / in the API_URL, so having /users would give a 404 (not found)
fuckr.js Line 137:
return getGCMToken.then(function(token) {
change to:
return getGCMToken().then(function(token) {
fuckr.js Line 138:
return $http.post(API_URL + '/users', {
change to:
return $http.post(API_URL + 'users', {
This will then contact the server and create the account with a 201 (created) and get all the data and log you in.  I verified this by using the test account I created and logging in on my tablet, and it works.
Also /services/authentication.coffee lines 40 and 41 contain these.
CONSTANT 404
After logging in, or signing up, there was a constant 404, if you press the online now, or photo only, (I edited the template to show these again), you get a 404.
fuckr.js Line 452:
$http.get(API_URL + "locations/" + geohash + "/profiles/online=true").then(function(response) {
change to:
$http.get(API_URL + "locations/" + geohash + "/profiles").then(function(response) {
That will take care of that error.  It appears that the filtering needs to be worked on.
/services/profiles.coffee Line 14 has the /online=true also
Other issues
-The app does not seem to realize when it is logged in, and the chat and settings icons do not show up.  I have not had a chance to dig into that yet and cannot troubleshoot those areas.
-The profiles themselves do not show up when you log in or create your account, but the profile json data is in the app, just not displayed.  I don't know if that is a databinding issue or what the cause is.  Before the v2 API shut down, I replaced the profiles = area where the profiles were pulled from https://primus.grindr.com/2.0/nearbyProfiles , and the profiles would display.  I wondered if it's a template issue as the template uses ng-repeat="profile in nearbyProfiles"
-The managed fields do not get loaded from the server and I'm not sure if that's why the profiles are not loading.
-The app does not actually log out, as there is no logoutAndRestart() function.
That's all I've got figured out for now.

I believe that under the profilesController section, the grindrParams has been removed, yet it is referenced in other areas.  This is throwing errors for me on line 715
filter = $scope.$storage.grindrParams.filter;
which references the grindrParams, and also line 744
return $scope.refresh();
as that is references the $scope.refresh() at line 713 and processes to 715 and the grindrParams.
I have a feeling the reason the profiles worked the other day was that I copied that whole profiles controller area from v2 api, and copied it to v3.  Now that v2 API is down, that no longer works.  This is another area to work on as the code for the locations has been updated.

hi @RobbieTechie thanks for all the discovery you have been doing on this.  Maybe I can help some as well, do you want to create a fork with your changes so I can test locally as well?

@kusaa
I just forked it, now I'm going to do some editing.  I'm also going to change where it saves the data for now, so when this gets finished, hopefully people won't lose their chats, this will be a fresh start for now.

@RobbieTechie I just cloned your fork, thx!

Will there maybe be an updated dmg? I'm not sure how to fix mine..

An updated dmg would be great! I went in and tried manually replacing the files from your fork, @RobbieTechie, but I think I may be missing something cause it isn't working quite just yet...

I love you guys and would love an updated dmg...  I went in and tried manually replacing the files from your fork, @RobbieTechie, but I think I may be missing something cause it isn't working quite just yet...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ljkappas I'm not on mac, and really not sure how to work with the files there.  I have been meaning to make a Hackintosh, but when we get this fixed, or if tomlandia updates it, it will get taken care of.
@northstar77 I don't think you are missing anything.  I pulled what is basically a work in progress for the v3 API and fixed some bugs, but it's not near complete.  It orignally gave a 404 error every time you ran it, and I fixed that, then I fixed not being able to make profiles, so if you fill that out, it will create one, and I got it to pull down the data for the profiles, but it still won't display them, that's what I'm working on figuring out now.  I've got some ideas but it's somewhat trial and error too as some things have changed quite a bit.
As for working with the dmg files, I know that @victorgrego had mentioned some things about that in this link: https://github.com/tomlandia/fuckr/issues/89 there are a lot of posts so you'll have to read through, but for now bugs and basic functionality are still being worked out.  When I make progress I'll put it here, and if @tomlandia  gets time, he is more than welcome to take any info I put here and put in in the official app.

@RobbieTechie Oh, ok! I thought you had gotten it working and I was just missing something.
@ljkappas Sadly, I don't have the skill or knowledge to make a the dmg once these guys fix this, but I can at least walk you through updating the files.  Last time Fuckr had issues I got the app working by adding/replacing with updated files (thanks @RobbieTechie !). If such new files are created and makes the app work on Windows, I can whether I can find the right spot for them in the Mac app directories. If success, I'll make an easy step-by-step guide to use until the next official release.

Hey guys!   Any updates on progress so far?

I'm making some bit by bit, haven't had a whole lot of time to work with it.  I am making some progress though.

logged in just to cheer you on @RobbieTechie

Another mac guy here.   Tried the old fix of moving files, etc.  No luck @Kaube . @RobbieTechie , any luck with your hackintosh?  @Tomlandia, do you think you be updating and packaging a dmg anytime soon?

@dcminicoder The project is completely at a standstill right now. Version 3 of the code is forced on all users of Grindr. This shuts down any prior work that was done so you were able to use any version of Fuckr. @RobbieTechie  is graciously working on his free time, this isn't even his project and trying to get any work around going on Version 3. It would be like if someone changed the locked and the way the door opened and you had to figure out how to get inside (everything changed). @tomlandia has been graciously made this software in his spare time as a hobby. We must all be patient because this was Grindr who changed all the locks and the doors on the building. I am sure if you are a programmer they could use some help, otherwise lets just cheer them on for success.

i'd like to  help if i can. I was a programmer in an earlier life -- but that really was years ago, so it may prove too difficult for me to  do anything useful. At least it will be a pleasant distraction from camming naked in zoom conference rooms lol.    I'm perfectly happy to be directed by you and/or Tomlandia btw about the best way to use the extra pair of eyes and hands that I can bring to the party.

So, I am able, and interested, to help, but we need to organize this. If we get to know in what point we are right now we can start coding and making progress. First we need to list what is working right now and what is not, so we can each one pick one task (or all, haha) and start coding.

Here's what I can tell you as of right now.  I created a new folder, put in the latest version of node webkit and put the apiv3 branch in there.  Then I started the troubleshooting what I noted above.  Based on what's been done so far, you can create an account or log in to an account.  If you login, it will log into the grindr side of things, which I have verified using the actual app on my tablet. The profile does show up when I change the location to my area, even though the Fuckr app acts like it's not logged in.  There is a line in the code missing that sets that the app is authenticated = true;  I added that in, but it appears to execute at the wrong time, or improperly.
What's working:
-Create account
-Log into grindr
-Reads the blocking
-Pulls profile data (but does not display profiles)
What's not working:

Does not pull managed fields
-Filters
-Undelivered chat messages
-Logging in/out on Fuckr side of things.

What's unknown:
-Chat portion
-Settings/update profile.  side note: I did force this and test, and it did switch US and Metric when api2 worked
When the v2 api still worked, I copied the section of code for the nearbyProfiles, that it pulled from ht*ps://primus.grindr.com/2.0/nearbyProfiles and the profiles would show up, and the filters worked.  The section of the code that sets up  the grindrparams was removed in the update, and I believe that is causing some issues right now.  I am also not sure if the template needs to be updated and it had a section of code that with ng-repeat for "profile in nearbyProfiles" and I'm not sure if that was based on the url or settings.
I will update this comment and attach when I get the chance.

Hi @RobbieTechie

I'm not sure if the nearbyProfiles part was based on the url or the code.

It shouldn't be since nearbyProfiles is a variable.

In the profilesController, that section set up the filters before and had a section of code
filter = $scope.$storage.grindrParams.filter;
The grindrParams are not setup in the APIv3 and I believe the code hangs at this point, but I've not verified this yet. The grindrParams are referenced quite often, so I have a feeling this is a sticking point.

Try replacing the references like this:
$scope.$storage.grindrParams.filter --> $scope.$storage.filter
$scope.$storage.grindrParams.lat --> $scope.$storage.location.lat
$scope.$storage.grindrParams.lon --> $scope.$storage.location.lon
$scope.$storage.location --> $scope.$storage.location.name
I was trying to do the changes myself, but I am on Windows 10 and for some reason I cannot build Fuckr from the source. Are you using Windows?

SO I'm entirely new to node, in fact to github, and of course to fuckr. But
I usually learn fast.  If it comes to that, if we get some progress made it might be
useful to you even if all i do is free up your time by updating/answering
issues as they arise. Last meta-comment: as luck would have it, my main 2TB
disk failed on Friday, and i spent the entire weekend coaxing about 1.5TB
of data off the disk (a full 500GB of which was NOT porn :)). Finally got
that sorted and a restored a working machine Sunday evening (London Uk
time), and took my first steps tonight:
So I started with Robbie Techie's repo, and I am on a Win 10 machine right
now. I can build that code, sort of:

l get three warnings from

npm install --save-dev
one is about node-uuid being deprecated and two about minimatch beinug

deprecated

2.Then just before that command returns, I get a quick series, perhaps 5-10
instances in a row of the following errors:
$ InterfaceRegistry(service_manager:connector):
bash: syntax error near unexpected token `service_manager:connector'
InterfaceRegistry(service_manager:connector):
Owned by:
ssbbp@DESKTOP-IUIHLNO  ~/Documents/GitHub/fuckr (master)
$ Owned by:
bash: Owned: command not found

nw run build

produces four releases without incident (win 32 win64 osx and linux64)

but then running

nw fuckr
returns a  long error output which i find impossible to understand. That
error is what's in the attachement to this mail. Perhaps oddly, if i just
run the stand-alone .exe in win 10, i don't get that output at all -- it
looks as if the release win64 client boots flawlessly. EXCEPT within a
minute or so, both versions of the client (i.e. standalone .exe and nw
fuckr) start to bring up the fuckr web page and immediately throw an Http
400 error.
Note that these two errors are obviously in Fact the same -- they concern
this line arounnd "InterfaceRegistry(service_manager:connector):"
So I believe that job #1 is to make this error go away.
That being said, I do manage to builld the clients -- and the fuckr.exe
standalone throws  no error. Although  it isn't successful at sending a
web query.
I'm on win 10, and could voice/video/share my screen with you any time, if
that' would be useful.
scott (ssbbpp)
On Sun, Feb 5, 2017 at 3:57 PM, NoahX1<EMAIL_ADDRESS>wrote:

Hi @RobbieTechie https://github.com/RobbieTechie
I'm not sure if the nearbyProfiles part was based on the url or the code.
It shouldn't be since nearbyProfiles is a variable.
In the profilesController, that section set up the filters before and had
a section of code
filter = $scope.$storage.grindrParams.filter;
The grindrParams are not setup in the APIv3 and I believe the code hangs
at this point, but I've not verified this yet. The grindrParams are
referenced quite often, so I have a feeling this is a sticking point.
Try replacing the references like this:
$scope.$storage.grindrParams.filter --> $scope.$storage.filter
$scope.$storage.grindrParams.lat --> $scope.$storage.location.lat
$scope.$storage.grindrParams.lon --> $scope.$storage.location.lon
$scope.$storage.location --> $scope.$storage.location.name
I was trying to do the changes myself, but I am on Windows 10 and for some
reason I cannot build Fuckr from the source. Are you using Windows?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-277528573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVCJBAZveJ0DDAc1HpZLWDFh4oOMbuGFks5rZfFTgaJpZM4LuWfw
.

$ nw fuckr
[9036:5292:0205/232713.550:ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: rappor::mojom::RapporRecorder requested by: content_renderer exposed by: content_browser via InterfaceProviderSpec "service_manager:connector".

@NoahX1
Yes I'm on Windows, using Windows 7 64 bit.  As for building the source, I'm not entirely sure I'm grasping what you're saying.  In windows you don't need to build anything unless you're running it using node, in that case go to a command prompt and type npm install -g nw to globally install node webkit, then nw fuckr to run it.  As of right now, you won't see anything though, this is basically in alpha status and not complete at all.
@ssbbpp to use a non depricated version, you can at the at latest.  such as npm install -g minimatch@latest  Just to be clear, I am not the author of this program, that would be @tomlandia so as far as closing down issues when they come up, that's up to him.
I'm trying to logically approach this, and as this is basically a new version, and code has been changed, and some removed, I'm trying ot approach this from a step by step process.
-If someone were new, they would either need to create an account on grindr or login after creating an account.  That originally was not working in this APIv3 build, but I fixed that.
-Next thing, would be logging in, which it does on grindr's side, but the fuckr app itself does not appear to know that it's authenticated.  I did fix that somewhat by adding a $rootscope.authenticated = true; in the login section and the signup section.  I'm not sure that is the correct spot, as it seems redundant to have to do that twice, but it functions for now.
The next issue is getting profiles to show up.  When the v2 API and v3 were both working, i could get the profiles to show up by pulling data from the v2 api, since the code has changed in Fuckr for v3 that is where I'm working on figuring things out now.

@victorgrego @kusaa @NoahX1 @ssbbpp
Ok guys, I've got profiles showing up, only 100 right now.  I've attached a link at the top with the main files.  I'll probably attach a full package with the executable files too.  This is still a work in progress but it's progress.

@RobbieTechie I was struggling to get the profiles showing, I was always getting errors in the calls I will just get your update and try to work over it I guess.

@victorgrego I was too, and I was about ready to give up last night.  I've been going over the code from version 1.8.1 and the v3 API figuring out changes.  I put a reference to the small change that got that working in the very first post.  It was on line 466 where the .data was missing.  Adding it back and bingo!
profiles = _.reject(response.data.profiles, function(profile) {
Right now it will show 100 profiles, yet I could not get it to show more.  I tried playing with the quantity argument, but no dice there.  I also tried messing with "profileQuantityPerCascadePage": 100, that the bootstrap use to call.  The other thought was maybe load more pages, but I didn't get that far.  I did notice on the developer console, if you switch to map view, it seems to pull down more profiles.  Unfortunately the map is not pinpointing yet.
I've also played with filtering a bit, on the loading url as I have not got the filters in the app themselves working.
$http.get(API_URL + "locations/" + geohash + "/profiles?photoOnly=true").then(function(response) {
That will load profiles that only have profiles.  Originally the program had /profiles/online=true with a back slash instead of a question mark, which I didn't realize at the time could be changed so I just removed it.  You can put different filters there though such as ageMinimum or ageMaximum
`$http.get(API_URL + "locations/" + geohash + "/profiles?photoOnly=true&ageMinimum=18&ageMaximum=99") just as an example.

Oh btw, I spotted why you could not make the chat to work. You are creating multiple instances to jacasr. What I did was just to emit the authenticate and set to true in the rootscope inside of the use credentials function. Now chat is working :o
Here's the link to the shared folder with everything: https://drive.google.com/open?id=0B0A27xuGfUWrUFQtQkFOaVFleDA

That's awesome, were going to get this working yet.  I'm currently working on getting the filters to function again.  I'm updating the template a little and going through getting the parameters to function in the url.

Hi RobbieTechie could you Skype me @ ljkappas? I have a question..

Hi,
I am using the Mac version and it used to function, but now the download from the site always brings up an Error 400 message, and replacing all the files in the Package Contents with the folder that was shared doesn't fix it. Any idea what to do?

Updated:  Added the option back to switch from Metric to US for distance (I don't think I updated this in coffee scripts), also fixed sending location in chats.  Distance does not seem to be accurate at all, and as far as I can tell it does not update location.  I added the feature back, but it gave errors so I removed it again.
Also, profile data seems to be missing  except the same data I can see in my rooted tablet in the profile table.  The table contains age, displayName, distance, isFavorite, lastUpdated (in epoch time), profileId, profileImageMediaHash, seen (this is the last time they were last active), showAge, showDistance, _id, state.
https://drive.google.com/file/d/0BxSmknffFGTnVlZxMmdlZE13Zlk/view?usp=sharing

Okay, I've updated the chat issue, and it seems to be working well right now. Since just fuckr.js was updated I've posted to pastebin: http://pastebin.com/rgSgM3nL
Basic functionality is now all good. We can chat with neighbors and see them. I would say our next step should be:
1- Filtering Profiles
2- Showing profile data
3- Retrieving and showing own profile
As soon as we are done with this we should push it into github so Tom can update the website.
After we have this priority issues does we can work on minor things:
4- Updating the profile
5- Pinpointing
6- There's a minor bug where you get the messages, it gets stored, you hear the notification, but you just see it if you click the person profile on chat panel.

 Thank you for your time and effort to make this work again!

So, @victorgrego, @RobbieTechie, with previous fixes that have been made for fuckr, since I'm on a Mac, I've normally just gone in and replaced the files. However, if you guys say you seem to have gotten it up and running, then it doesn't seem to be working for me this time around :( Any way of helping with that?

@northstar77 Well sry, not a mac user here. Maybe you are just setting things wrong. just substitute the fuckr.js file and it should work.

@nutritiousreject Do you know if Mac uses the coffee files and then builds those into javascript, or if it directly uses the javascript.  There are some settings inside the javascript that refer to Mac, but it looks like those are for using an older version of node-webkit and the way it handles the gui.  What are you specifically having problems with?  Does it load or not load, does it not log in, not create an account, nothing show up?  I'm not on Mac and didn't do the Hackintosh but I can still check some of this out.
@victorgrego I've been attempting to get the managed fields back in.  On the old version, I could just update the link to pull the new fields that added positions, that were not in the v2 managed fields.  The old version of the app will still pull those down without being logged in if you click the profiles table at the top.
I'm thinking those need  to be added back into the controller, just like I did with switching the Metric and US.  I've added managedFields to the end of the profiles controller:
profilesController = function($scope, $interval, $localStorage, $routeParams, $window, $injector, profiles, pinpoint, managedFields) {
I've also added the url back in, as that was taken out. and added it to the filters section, but I'm wonering if I'm missing some small detail.
As for showing your own profile, maybe using ng-show, set it to use the same pure-1-5 grid so it's 1/5th and pull the url for your profile, and set that up before the ng-repeat for the rest of the profiles.
As for filters, I know you can add the tribes and all that, I've been messing with that in the links.  I'll have to see about getting the paramaters to the end of the url.  The old version had it set as https://primus.grindr.com/2.0/nearbyProfiles', paramsand the params were cloned from local storage. in the getNearbyProfiles function.

I just got the managed fields filters to show back up, but I still have to implement them into the actual filtering.

fixed an issue with blocking too

@victorgrego No, I'm putting everything right where it should be :-/
I can't even get it to log in, it still sits and spins and I even went into the js file to make sure the edits @RobbieTechie had made were in there. I'm also getting an "Unexpected error (HTTP 401)" But I'm guessing that's just because it won't let me actually log in?

@northstar77 Does the login page even come up, it looks like this now....

@RobbieTechie Thank you so much for the update. Nothing shows up on Mac. Is there any Mac user has the same issue?

@CDLVY @northstar77
There is the problem, line 88 of fuckr.js, which says
return chrome.instanceID.getToken({
This uses chrome to get the messaging token. so the next question is, does a Mac process this differently.  Node Webkit is using Chromium, you may try to update that from https://nwjs.io/

Here is the update, with the chat fixes that Victor did and the managed fields implemented.  I still don't have the actual filtering implemented, but this is a start for that issue.
https://drive.google.com/file/d/0BxSmknffFGTnY3U2RkczRGoxak0/view?usp=sharing

@RobbieTechie Yes I am able to get that new login page. Just that when I enter my login info it still sits and spins. I'll try that suggestion you made shortly and let you know the results.

@northstar77 I'm hoping that works, I know that's tied to the instanceID and that was added in Chrome version 46 I believe, so it's not super long ago cross your fingers

Oh... o_o ...this is getting hardcore programming XD, i guess we mortals should check in once u nice people work out the fix on a full ammm.... easy-to-get file?

@RobbieTechie So I downloaded NWSJ from the site you provided and I was hoping I could somehow get lucky and figure this out on my own, but I have no knowledge of any of this and I'm over my head at the moment haha. Do you have Skype by any chance?

@RobbieTechie I got all the filters working and the managedFields back I need to get the profiles showing.

Ok, what I found so far... Seems like the paid filters do not work. If you try to filter by tribe, hiv or position grindr does not filter. I also added a correction that does not allow grindr to do calls when the age is <18 or >99 or minage > maxage or when invalid. Because those calls return errors.
Another issue that need to be fixed is the distance calculation. It always show me like 200km+ from my neighbors lol (I wish).

I just added back the updatLocation coding, and have it push the geohash to https;//grindr.mobi/v3/me/location.  I was messing with the filters and location data earlier.  I may be wrong but I believe the profile data won't show up if you don't have a location set.  What I mean by this, the app defaults to San Francisco, and if I move it to Michigan where I'm from, it will say that the profiles are a long ways away.
When you use to have the app load with no gps on, it would throw you in the middle of nowhere, and that almost seems like that's what happens here, even with the locaiton being pushed.  I'll post that here.  I also had some profiles showing up in San Francisco, but they appeared to only read the longitude, the were in a straight line north and south.  I'll attach what I've got.
There is also a section in the old Fuckr app I messed with that seemed to get pinpointing somewhat working, but I didn't figure that out exactly so I deleted it, but the code was
getNearbyProfiles = function(locations) {
    var promises;
    promises = locations.map(function(location) {
      var params;
      params = _.clone($localStorage.grindrParams);
      params.lat = $localStorage.location.lat;
      params.lon = $localStorage.location.lon;
      return profiles.nearby(params);
    });
    return $q.all(promises);
  };

https://drive.google.com/file/d/0BxSmknffFGTnNzhYWmNLX3ZWTW8/view?usp=sharing

The tribes were filtered by the numbers in the managed fields, I had those working earlier, and in fact I believe you can filter with multiple fields at one time.  Let me get an example then I will edit this.  Also, I 've seen many profiles that have an age of 0, not sure why they do that now, since the app puts your age in by deault.

(API_URL + "locations/" + geohash + "/profiles?photoOnly=true&lookingForIds=2
that would give you photos only and looking for Chat
API_URL + "locations/" + geohash + "/profiles?photoOnly=true&lookingForIds=2,3 would give you chat and dates.  There was a section in Fuckr 1.8.1 that sorted out Ids.
$scope.changeFilter = function(filterName) {
    var filterValue;
    filterValue = $scope.$storage.filter[filterName];
    if (filterValue) {
      $scope.$storage.grindrParams.filter[filterName + "Ids"] = [filterValue];
    } else {
      delete $scope.$storage.grindrParams.filter[filterName + "Ids"];
    }
    return $scope.refresh();
  };

For hiv, you can't filter by that, I tried that before with the old Fuckr app, but the official app doesn't even use that as a filter.  I thought they would add it but it's still not in the official app.  The positions were only in the v3 api managed fields https://grinbr.mobi/v3/managed-fields.  Check the link set in the app, it might be primus.grindr.com/2.0/managedFields, that's the old one.  That should be around linek 765 give or take a little bit.
You need to have a legit user agent set when using chrome to view managed fields, or it will say the client is deprecated.  You can use chrome, and on the network tab, set the user agent to
Chrome - Android Mobile and it will show the fields.

I suggest that the app should ask which location to use by default by showing the gps coordinate selector window on first login for each new profile. It's not a good idea to show up in San Francisco, and then change the continent within a second. That gets you banned pretty quickly.
So it's going to be working soon!! Fantastic!

So apparently the filtering is not working right now, and I did notice earlier that their servers seem to be having issues.
@mattitutti If you want to customize you're version, you can go right ahead and do that yourself, nobody has ever been banned for showing up in San Francisco, otherwise the loads of people there would all get banned.

Ok I don't think their servers are having issues, I apparently messed something up with my last release, I just switched back to when you updated the chats, and the filters are working.  I'm about to get some sleep though.  I'll get back at this in a while.

Obviously it does not get anyone blocked if you want to keep your profile in San Francisco. For me it used to be an issue with the previous versions of the app. Profile was constantly getting banned after changed from the default San Francisco to ... Europe, but oh well, it was cured by creating the profile from the original app itself and then using fuckr didn't get me banned. So there is some kind of filtering involved there... they can find ur profile and block it if the behaviour is suspicious.

Well, whenever I did any updates before, all you did was constantly bitch about how it was a short term solution, or there was always something that was not good enough, even though nobody else at that time worked on it.  So I guess the only thing I can tell you is, if it's not good enough for you then just don't use it.

first of all can i just say what an AWESOME job @RobbieTechie and @victorgrego and the rest have done. I check this forum every single day (yup) waiting for fuckr to work so imagine how happy i am to see what you guys have done.
and to avoid speeding around the globe at warp speed, just make sure you're logged out, set your location and log in again. you should be at the location you last set when you were logged out.
just a question @RobbieTechie i haven't set any filter (like you said they don't work) but i can't see any profile with no picture. just me or the current version's limitation?

@bootyliciousgeek  If it's the first time that you're loading the app, or if you cleared out your AppData folder, then simply click the online box, then uncheck it.  I'm not sure what the deal is there, but it's probably some simple thing we're overlooking.  Some of this issues might be the updates to Chromium in the node webkit, not sure though.  I know for mac users, it won't process the gcmToken properly.  Give that a try and see if it works.  I'm taking a break for a while though, it's been a  26 hour day for me.

Hey guys, i just registered because i am also a mac user (i also have windows). I only have limited webdeveloper skills so I guess i wont be of any help otherwise. Let me know if there is anything I can do to help maybe in terms of testing.
@mattitutti has a point on the location thing but I suppose you can circumvent that by just registering on the official app before moving to fuckr.

@RobbieTechie did that but from the start it showed only profile with photos (unless there was no photo-less profile around SF when i started the app). Oh well I'll manage :)

I downloaded the apiv3 files from GIT, then overwrote view files and fuckr.js from the latest zip provided by @RobbieTechie.  Did i get it wrong? Should i download @RobbieTechie 's version only from the first message?  I do seem to get profiles showing up, i can sign in, send/ receive messages.  Probably the profile part doesn't work no?
Don't get me wrong @RobbieTechie , i do appreciate your contributions. And why i haven't done anything is the fact that you and few others are already dealing with it.

@bootyliciousgeek Right now that's normal, we are working with the filtering but have not totally put the functionality into the app yet.

So, I updated my branch of fuckr (https://github.com/victorgrego/fuckr). It has the filters and chat working.
@RobbieTechie i will look into implementing that fix.
The priority list is as follows:
1- Showing profile data
2- Retrieving and showing own profile
3- Updating the profile
4- Pinpointing
5- There's a minor bug where you get the messages, it gets stored, you hear the notification, but you just see it if you click the person profile on chat panel.

Awesome, you're a rockstar @victorgrego , I'm digging through code right now to do some more testing and see what else I can figure out.  I noticed last night I had profile markers show up, now I believe I messed that up.   In some of the lat and lon settings, Google uses .lng instead of .lon and I changed that, which might be why the profiles were not pinpointed properly.
I did test some of the profile updating before we made this much progress, and I would say be careful.  If it does not process properly that can lead to an instant ban.  I changed the displayname and about me without issues.  Also  a side note, v3 of Grindr does not use the headline any longer, but it would get thrown into the about me section of your profile.  I'm not sure if that causes any bans but did not appear as such.

Here is what I mean by the pinpointing.  I started with a fresh copy of api3 today and have been going through.  I did not put the updateLocation back in this yet, but this is what the app did yesterday with the getNearbyProfiles under the pinpointing. being put back in.  It's as if it only reads the latitude or longitude.  I was wondering if this is because of the name and lat and lon being set in the profiles controller in one section and if it's not worked out properly in other areas of code.  Yet sending the location from the chat works and appears to be accurate.

@victorgrego I've got the app pulling data for the profile you're logged in with, which it didn't do before, and perhaps this can lead to getting data for the other profiles.
Under the get function, it was missing data again, I changed
return deferred.resolve(response.profiles[0]);
to
return deferred.resolve(response.data.profiles[0]);
which was the same thing that prevented any profiles from showing up on the grid originally when we first started working with this. the .data was missing.  This will also contribute to editing your own profile, as it would not show any data before but now it will.

As of right now I have the profile able to pull data when you're on the settings page, so if you've filled anything out, it shows up, and if you have a pic that shows too.  The only major issue there currently, if you attempt to edit the height, it will instantly ban the profile.  I've also added back the option to display or hide your age.
As for profile data, I'm still not getting anything other than the age, yet, on the settings page, it will pull down all your profile data.  I have not yet put in the filters on this version, and I also don't have the updateLocation function in here either.

I've been reworking the filters, and now I've also got the profile data showing up.  I don't have the filters fully implemented but I'm getting there.

It would be helpful if you indicated clearly the name of the functions. Because for example, when you say that you found data missing I do not know where you are referring to, i went through all the code but could not find what you are talking abt.

What I meant was the dot data .data but because I typed it out, it removed it.
get: function(id) {
var deferred;
if (profileCache[id]) {
return $q.when(profileCache[id]);
} else {
deferred = $q.defer();
$http.post(API_URL + 'profiles', {
targetProfileIds: [id]
}).then(function(response) {
return deferred.resolve(response.data.profiles[0]);
});
return deferred.promise;
}
},

@victorgrego I can get a profile to show details, such as the about me, height and weight, but it's only if it's clicked from within the chat, as I cannot get the grid to load after doing this.  This is also without the filters in there, since the grid won't load.  Perhaps this will give some clue to getting the data to show up.  This also allows you to edit your own profile data, except for the height, if you mess with that, the account will instantly ban.  And yes it will allow you to upload a profile picture, but after you select it, you have to click off that field, it acts a bit funny.
I'm attaching this, and it will load your chats and allow you to click profiles in chat and show the profile info, but it will pop up errors because the geolocation is not properly being implemented here.
This almost appears that it reads the profile data from a cache, as the pinpointing section clones the localstorage.
https://drive.google.com/file/d/0BxSmknffFGTnbGlBWC1aYXBBdEk/view?usp=sharing

So I started with a fresh version of fuckr.js from the APIv3 and fixed some of the original issues, and then when opening the chats that I've already had with profile data, it still loads.  This tells me that the profiles you view in the grid are not being cached to disk or being removed, unless there would be some other reason?

So doing some testing, right now the only way profile data will show up, is if someone chats with you, then for some reason the profile data is visible.  If you chat with someone and they don't respond then the data still doesn't show up.

@victorgrego
I think I understand why the profile data isn't showing up, but I'm having issues trying to get it working.
under the profiles.get function
get: function(id) {
      var deferred;
      if (profileCache[id]) {
        return $q.when(profileCache[id]);
      } else {
        deferred = $q.defer();
        $http.post(API_URL + 'profiles', {
          targetProfileIds: [id]
        }).then(function(response) {
          return deferred.resolve(response.profiles[0]);
        });
        return deferred.promise;
      }
    },

On the line that says
return deferred.resolve(response.profiles[0]);
this is where I was talk ing about adding the word data
return deferred.resolve(response.data.profiles[0]);
Doing that will allow you to edit your profile under the settings page, except for height, that will ban your profile instantly.  But the issue for the individual profile data lies in this function too.....
when it sends to the server
targetProfileIds:[id]
This is explained here https://github.com/tomlandia/fuckr/blob/master/unofficial-grindr-apiv3-documentation.md#get-the-profile-of-specific-users
I can pull up a full profile with details if it's sent to chat.  Looking at the chat section, specifially at the code that says:
return profiles.get(id).then(function(profile) {
     return $localStorage.conversations[id].thumbnail = profile.profileImageMediaHash;
   });

That processes the link properly and people in chat being clicked on gives full profile.  I'm attaching the javascript I'm using, which is basically a rework from earlier, without the filters.  Also I saved a .har file when I got a full blown profile, and the section that shows the link being sent is this:
"headersSize": 975,
          "bodySize": 31,
          "postData": {
            "mimeType": "application/json;charset=UTF-8",
            "text": "{\"targetProfileIds\":[82659130]}"
          }
        },

I'm having trouble getting this to send to the server properly.  As I'm nowhere near professional at programming, perhaps with the details here, something can be figured out. I don't know if you need it, but I will attach the current fuckr.js that I'm working with.  I tried clicking the chat profiles with the version where you fixed the filters and it would not bring the profiles up but this verson will.  This also allows you to edit your profile.
https://drive.google.com/file/d/0BxSmknffFGTnSmR6bGxzZWttTGc/view?usp=sharing

Hello @RobbieTechie
As you already know, javascript handles json as objects. Sending them to the server is another thing, the json object needs to be "stringified". like this var myJSON = JSON.stringify(myObj);
Also you never need to worry about quotes and escaping them, as it is done automagically if you stringify(), parse() them like in the examples found from the url below.
I have not checked what library is used for JSON in nodejs or in this app, so basically you can avoid all the problems by creating those as objects, then stringify() for storing or sending and parse() for reading the json data from the server or from storage..
See this for usage examples
http://www.w3schools.com/js/js_json_intro.asp

I've got the profile data showing up!!  The get:  function I posted above was not the problem.  The problem lies in that two different urls are used to pull the profile data.  The first one gets the profiles by geohash and the other without it.  The program was caching the profiles from the first and using that data in the 2nd and the data in the first is limited.  I commented out the caching and bingo!!  The filtering may need to be figured out on implementing again though, as the version with t he filters would not  work if you pull your won data for your own profiles,  I will attach the version from the original v3 API with as much funcionality as I can get in.  That will be attached here momentarily.

I left the cache for the profile grid inself, then removed it from the get: function.  This way it will still cache a location and only pull the data for an individual profile instead of not caching any of it and having to fetch it all every time you move.
get: function(id) {
      var deferred;
      //if (profileCache[id]) {
      //  return $q.when(profileCache[id]);
      //} else {
       { deferred = $q.defer();
        $http.post(API_URL + 'profiles', {
          targetProfileIds: [id]
        }).then(function(response) {
          return deferred.resolve(response.data.profiles[0]);
        });
        return deferred.promise;
      }
    },

That last one I posted is from a fresh start, and did not have the filters.  This one is the version victor did with filters working and shows the profile details.  You may need to clear your AppData folder if anyone tests this.
https://drive.google.com/file/d/0BxSmknffFGTnaGZZUU0xeHBuUEU/view?usp=sharing

I seem to be missing something - cant get it to run. Assume the contents
just over write the same files in fuckr-master.  Do you have a link to
download the master that works?  is a dsifferent nwjs needed?
Thx - Dennis
On Mon, Feb 13, 2017 at 3:17 PM, RobbieTechie<EMAIL_ADDRESS>wrote:

That last one I posted is from a fresh start, and did not have the
filters. This one is the version victor did with filters working and shows
the profile details. You may need to clear your AppData folder if anyone
tests this.
https://drive.google.com/file/d/0BxSmknffFGTnaGZZUU0xeHBuUEU/
view?usp=sharing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-279555396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AObrISiJCIhPXasXLq9BBis-XdRCrpEgks5rcOR-gaJpZM4LuWfw
.

What I just shared there is the basic changes and i just shared it through google drive.  Right now we've only got it working with Windows.  I can load a full package here but it's just for Windows as we have not got a mac version working.  The people that posted details about that showed that Chrome on Mac was not able to fetch a certain token properly and would prevent the program from working.  I'll put together a 64 bit windows version and upload it and link it here shortly and update this comment with the fix.  This is still beta so it's not going to work with your old version with old chats, we have it put the data in a new directory right now.

Hmm maybe I need to flush a cache somewhere or something but I get error 403 when I try to log in and 404 when I try to create a new account..

Found the issue with profiles being banned when editing the height (which I disabled).  There use to be a bunch of short bots, 2'3" or 68.58 cm,  The height can be re-enabled for editing by setting a minimum value of 4'0" max of 8'0" or min="121.92" max="243.84"

I missed fixing that when I ran through this version, I'll upload a fixed fuckr.js and you can copy that to allow you to make a new profile.   There was a forward slash  / left in, and I also need to fix the block function, forgot to update that too.  I'll post a fixed fuckr.js you can copy in there.
You can also clear your appdata by copying and pasting c:\Users\%username%\AppData\Local into your start menu search, or in the navigation of "My Computer" then find a folder named "Fuckrtestbed" and delete it, that will clear all settings for different versions of the app.

From what I did earlier, I missed a few things, here the height editing is fixed, blocking is fixed, online filter is fixed, and now if you have favorites, they show up with the check of a box.
https://drive.google.com/file/d/0BxSmknffFGTnNi1ySHd1aWFrTGc/view?usp=sharing

@RobbieTechie in previous version you can send location, but this new one you can't

Nice! Works fine for now haha. No way to add favorites from the Fuckr end?

Right now the priorities list is
x1- Showing profile data
2- Retrieving and showing own profile
x3- Updating the profile
4- Pinpointing
5- There's a minor bug where you get the messages, it gets stored, you hear the notification, but you just see it if you click the person profile on chat panel.
2 I think it will be easy, as it s done in edit
3 needs some updates as there is a minor issue when editing, or a bug.
4 I have an idea, we need to switch from lat/lon to  geohash
5  I believe is fixed with a $scope.apply() in the controller
I think we will be able to add the ability to favorite, but it won't override what Grindr has set, meaning the 10 per day limit unless you're an exta subscriber.   I believe that now they have that checked on their server side

hey there. been following along and wow, such collaboration. I wonder about a problem i have even after the last version for windows and clearing the local app directory.
-before i could just 'click' on the grid  (pic 1)

and the program would fire up and allow me to see profiles without even logging in. when i do this now i get the 401 error (2nd pic).

Is this intended or MUST i log in now to see local profiles? ..wunderin'

The old app ran on Grindr's old api, which would allow you to click on the profiles grid and see profiles without being logged int.  Now you must be logged in or you get that 401 which means unauthorized.

Got it. Was not sure of that functionality change. Thanks for answering RT!

@victorgrego  So I've made an interesting discovery, thanks in part to a friend joking with me about moving decimal places, and it involves the distance.  Grindr is using higher precision.  If you take the profile distance and divide by 1000, it becomes accurate again.  I'm not sure if that will mess up the pinpointing or not, but it fixes profile distance.

where in the code should the change go?
On Tue, Feb 14, 2017 at 8:33 PM, RobbieTechie<EMAIL_ADDRESS>wrote:

@victorgrego https://github.com/victorgrego So I've made an interesting
discovery, thanks in part to a friend joking with me about moving decimal
places, and it involves the distance. Grindr is using higher precision. If
you take the profile distance and divide by 1000, it becomes accurate
again. I'm not sure if that will mess up the pinpointing or not, but it
fixes profile distance.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-279914712,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AObrIRXyYo0sM2AYsroGnbAhr-EZdxHXks5rcoA1gaJpZM4LuWfw
.

If you are using US for distance and not metric, for now you can go to the kmToLocalUnit function and change it to.  I just added 3 decimal places.  That code is around line 821 give or take some lines.
I'm trying to figure out if there is a spot that controls the decimal places of the distance overall,  but right now I'm exhausted so I'm probably about to get some rest.
For km, you could also change the km to
return (km/1000) + ' km';
But that will give a bunch of decimal places.  That could be controlled with piping in the template though.  I use to switch from km to miles and use {{0.621371*profile.distance | number:3}}  so you could use {{profile.distance | number:3}} to limit the decimal places in km.
kmToLocalUnit = function($localStorage) {
  return function(km) {
    if (!km) {
      return '';
    } else if ($localStorage.localUnits === 'US') {
      return (km * 0.000621371).toPrecision(3) + ' miles';
    } else {
      return km.toPrecision(3) + ' km';
    }
  };
};

putting the 3 decimal places will

ATTN Mac Users:

Download latest version of Fuckr.
Download and unzip this file: https://drive.google.com/file/d/0BxSmknffFGTnNi1ySHd1aWFrTGc/view
Open the unzipped folder, select everything in it and copy it.
In Finder go to where you have Fucker located, right-click it, and select "Show Package Contents"
Contents > Resources > app.nw and paste the files in this folder. Just replace all when asked.
Go to https://nwjs.io/ and download this app/file. I downloaded the SDK version, but not sure if it makes a difference.
Once it's downloaded and installed, go back to the finder and drag it into that same app.nw folder.
Open Terminal (Can used the Spotlight search to find it), copy and paste the following command: open -n -a nwjs --args "/home/path/to/app"
Enjoy Fuckr in its most updated form.

Awesome work @northstar77

Grindr just did an update today, not sure if that's bad or not but thought I'd give everyone a head's up haha

So @RobbieTechie, now that I'm finally on the same page as everyone else, I just want to make sure that the following are not yet working: seeing someone's locations via clicking the globe on their profile, and also the map view. Is that right?

The pinpointing from a profile is not working and the map view won't show people either as of right now.  I believe that this may have to do with the fact Grindr is now official using meters and not kilometers to measure distance.  someone right now 12 miles from me looks like 19714.149889821052 for distance.  I don't know for sure if there are too many decimal places causing problems, but we will get it figured out.

@RobbieTechie that is meters - you probably just need to divide the distance by 1000 before passing it into trilaterate() as part of the beacon object

@genevera Yeah I know it's meters.  I'm just trying to figure out if there's one or two spots to fix it overall for the entire program.  For the distance right now I'm fixing it in the kmToLocalUnits function, and that's for the distance on the profiles.  I'll definitely look into that though, thank you.

I've got the profile pinpointing working for a local area now, just gotta check some things and tie up some things later today and I'll post it.

Awesome!
On Feb 16, 2017 12:39, "RobbieTechie"<EMAIL_ADDRESS>wrote:
I've got the profile pinpointing working for a local area now, just gotta
check some things and tie up some things later today and I'll post it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-280402762, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMJK0ewSlo438-_dPWQ1zMu_eLCgsDMdks5rdInRgaJpZM4LuWfw
.

@northstar77 Thanks for your instructions for Mac users! The method works well for me except for uploading pics and other minor issues that have been mentioned before. Can you upload pics successfully  without having an unexpected error HTTP: 400?

Ok guys, right now this thing is working.  It's showing full profiles, it chats, and it now again pinpoints people.  The distance, whether set to US or Metric, gives 3 decimal places.  That I did because of densely populated areas,
There is a bug when updating your profile, it seems to either take the height or weight but not both, and yes I'm aware of that.  I fixed the drop down filters, a couple things needed updates in the template.  I also have a checkbox to show favorites if you have them.  I don't have the ability to favorite people in the app though.  Currently it only shows 100 profiles, unless you have an extra account.
I've added the main updated files to my github, you could just download the master from there, which might be what the Mac users will want to do .  For the Windows 64 bit users
https://drive.google.com/file/d/0BxSmknffFGTnMzdUTDI2alF4TDg/view?usp=sharing

@CDLVY You're welcome! Glad it's working for you! And what do you mean by uploading pics? You mean like sending in chat or uploading to your profile? Cause I haven't attempted to upload a new profile pic, but sending pics through chat worked fine for me.

Hi guys, thanks for all your work, i was just testing the app and i am not able to upload pictures, is that normal? or maybe i need delete all previous files and try again? thanks again for your work!!!

If you mean the profile pic, you have to select it from your computer, then after it puts the file name in the space, you have to click a different section of the page, such at the about me section, that should trigger it to say it's uploaded and "Image up for review by some Grindr™ monkey"  As for chat images, after you select one, it doesn't show up right away under the chat section.  Typically you have to click off that page, say go back to the profile grid, then come back, and it should show up then.  I have not yet really looked into those issues.  I did notice there is no doctype in the tenplates so perhaps that is causing some issues.

i am talking about thechat images, i'll try to look into it, right now i am getting unexpected error HTTP: 400 when i try to upload one. Thanks for your job, man!

@northstar77 Every time I try to send a new pic, I could not upload it from my Mac. Is there a way to fix that? Same here. @dvinan

@dvinan @CDLVY I really don't know what to tell you, guys. I unfortunately don't have the skills for this type of thing. I just happened to get lucky messing around and thankfully got it to work. :( I'm sorry, guys.

So another issue I've found is that when you start using the app again, any undelivered messages from when you ere offline, get pulled from the server, but do not get written into the chat and currently they may just build up.  You still get messages while online though.

Maybe it is only me,
using @RobbieTechie  's version for windows 64.
Cant seem to send or recieve any messeges, either offline or online.
They just stack up in the chat windows, but nothing is getting through.

Regarding the profile pic, I followed the advice you gave above, uploaded a pic (one I've used before on previous versions), once the file name appeared, clicked on 'about me' but get error 413

keep getting error 403 too. creating a new profile, even when settings left untouched, will result in error when the app is opened again

@guywpg the 413 would mean too large, so I'm guessing the pic you are trying to upload is to many bytes.  As for the 403, is it a window popping up, or in the console, you will get 403's from people without pics.

Hi, I downloaded the RobbieTechie google file, im 64 Windows user, and when opening the App I get a 403 error, perhaps my account got Banned? I had my account signed up b4 the update issue thing......so... i got banned or is something else?

@RobbieTechie same problem like @Alastor1
i can create a new profile, edit my settings, upload pictures but can't send any message (no textbox appeared under the received message). previously i just closed then reopened the app. now i'd get the 403 error

I had this prob the first time but clicked on the "sign out", restarted and
then it was ok.
On Fri, Feb 17, 2017 at 1:28 PM, Alastor1<EMAIL_ADDRESS>wrote:

Hi, I downloaded the RobbieTechie google file, im 64 Windows user, and
when opening the App I get a 403 error, perhaps my account got Banned? I
had my account signed up b4 the update issue thing......so... i got banned
or is something else?
[image: image]
https://cloud.githubusercontent.com/assets/22179454/23083909/9dfb13c8-f525-11e6-94c8-316c29fd9fb8.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-280771343,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AObrIW6N6s7eK2XQ-05KKYhZjj1ghtg_ks5rdhEBgaJpZM4LuWfw
.

In earlier versions I was able to use more than one profile - in the start
screen I could change the email and login. Messages from both profiles
would appear in the chat window. Did this for primarily testing.  This no
longer works. I have two recent versions of fuckr; one where distance works
and the earlier one where it doesnt. Each will only start with the first
profile I used after downloading. Using a different email gives a 403
error.
Also the app doesnt appear to sign out. There are two "sign out" icons, the
leftmost being functional and gives the appearance of signing out but when
the app is restarted (after signing out) it immediately starts to run - no
login screen.
Thx for the great work on this.

One of the main issues in the beginning was that when this would sign in, it would not sign back out.  There is a function that would remove some stored data and restart the app.  While we've been testing, this basically has been bypassed, and I have not yet put it back in.  Those are not two sign out icons, one is to sign out and one is to sign in.
The reason you could use multiple profiles is that the chat history is not cleared when you logged out.  I will see what I can do with the logging in and out when I get a chance.
Basically when Grindr forced the upgrade, the code was gutted, and Victor and I have been working on putting things back together piece by piece, or section by section.  Grindr has also switched up quite a few things, some of which is not at all documented, so it may take a little time to get all the bugs worked out.
That 403 has happened to me too, @Alastor1 I just realized I did not update the main index file, which was modified, so I will update that, and perhaps that will help.

@bootyliciousgeek Would you happen to be using Windows 10 by chance.  I don't usually use it, but I messed around with it tonight, and there is a spot in the code that uses Chrome too get a token, and it does not like doing under Windows 10.

ohh I see, hopefullly that will help and will erase the possibility of being banned...also I am using W10 ._.  . Welp anyhow I'll wait and thank you for helping us :D .

@RobbieTechie Awesome work man! I think you just just clean the code and do a commit so @tomlandia can update the main github and website. Just tested and everything seems to be working just fine.
I am impressed by how fast you got acquainted with the language and the framework!
Sorry for not being active last days, was pretty busy with school.

@RobbieTechie Strange because I didn't have to resize this same pic before but sure enough, it now works! Thanks again 😄

@RobbieTechie yup windows 10

@bootyliciousgeek I don't usually use Windows 10, but I tried that last night and got the same result.  I have an idea of getting the code with just javascript and not calling the InstanceID, which seems to be the issues.
@guynwpg You're welcome
@victorgrego  There is still an issue with undelivered chats from being offline.  They do not get written into the chat on the disk.  They also seem to not get acknowledged, as every time the app gets restarted the chat data is still shown if you look at the link in the console in the response section.
As for school and being busy, that's totally understandabale, it's all good man.

@RobbieTechie Was just curious if there was any way you guys would be able to implement being able to save a profile as a favorite through Fuckr? If it's even possible, that is.

welp, i borrowed a friend Android device and was able to log in in Grindr with the same account i created on Fuckr....but on Fuckr i cant log in with it, keeps saying error 403 as soon as i open the app and also when tryining to relog.... so if not banned, I guess is the Windows 10 thingy?

Yes @Alastor1 , it appears to be because of Windows 10 and the way Chrome and Windows 10 get along.  I thought there was a way to use just javascript to get the token it needs, but that uses a Chrome InstanceId, which is where the problem lies.  I'm searching for a solution, perhaps something involving permissions.
@northstar77 The favorites question was asked before,  yes that will be able to be added, but I'm working on a few other things first.  Also, this won't bypass the limits, just like blocking.  If you try to block more than 10 you'll get an error.

@RobbieTechie Oh ok, cool! And sorry, didn't mean to ask again, just must've missed when it originally was, my bad. :)

Oh, I see, thank you. I do not know a thing about programming....sorry cant help, but cheer 4 ye man, Ill wait for any possible fix.

As far as i know. Most updated fuckr right know is designed to work in wins 64 bit user. Is there any update for 32 bit user ?

Yes @BloodyCrown it will work with 32 bit, you could head to nwjs.io and download the 32 bit version, then extract those files into the fuckr directory and overwrite the 64 bit ones.  I could also download that and do the whole package and attach it here in a bit.

I saw that @tomlandia has done an update to the api3 branch, so I am going to work with that now, so we don't keep making different versions.
@victorgrego I fixed the undelivered chats.  On tomlandia's branch, on line 248 of fuckr.js
_(response.data).sortBy(function(message) {
is now
_(response.data.messages).sortBy(function(message) {
This was the reason we were getting an undefined message over and over every time the app loaded. there was an empty object being returned.

So Windows 10 just had a rather large update, and those of you using it should now be able to use Fuckr without the 403 from the gcm token not working.  Even the emojis look pretty cool =D
@Alastor1 @bootyliciousgeek

is this downloadable from fuckr.me?
On Wed, Feb 22, 2017 at 12:23 AM, RobbieTechie<EMAIL_ADDRESS>wrote:

So Windows 10 just had a rather large update, and those of you using it
should now be able to use Fuckr without the 403 from the gcm token not
working. Even the emojis look pretty cool =D
@Alastor1 https://github.com/Alastor1 @bootyliciousgeek
https://github.com/bootyliciousgeek
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tomlandia/fuckr/issues/107#issuecomment-281600864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AObrIVTpCn1b8_veZX2TiASFtnLywQP_ks5re_CHgaJpZM4LuWfw
.

@RobbieTechie i've no idea how to do the emojis but you're right! no more 403

@RobbieTechie
Could you please upload the updated package with the executable and everything?
Thanks.

Thanks a lot @RobbieTechie and sorry guys about leaving this aside that long! Gonna release a v2.

Thank you :D

Thanks a lot to everybody for your effort!
I am on MAC.  I have done all the steps suggested by northstar77 but nothing at all.
Any suggestion? It gives error repeatedly

is there any full "pack" ou there i can download that works  (win 10 here)?


Scrolling with ScrollView component

Hi,
I am not sure whose issue is this but this example is my starting point so I am asking here. The problem is that scroll within ScrollView component doesn't work when using NavigationCardStack or NavigationTransitioner.
Anyone else using this or has any ideas?

Code snippet?
Also, make sure that you have flex: 1 set on your ScrollView component and all parent components up the chain from it. Missing one causes ScrollViews to not know their height and stop working.

@jlyman For testing purposes I am using your code so just try using ScrollView instead of View in one of your screens for example FirstScreen.js.

Hmm, can't seem to replicate this issue. Here's some scrolling that works just fine on Android for me:
import React, {PropTypes} from 'react'
import {ScrollView, Text, StyleSheet} from 'react-native'

import NavButton from './NavButton'

const FirstScreen = (props) => {
	return (
		<ScrollView style={styles.container} contentContainerStyle={styles.scrollContainer}>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>
			<Text style={styles.title}>First Screen</Text>

			<NavButton destLabel="Second" buttonHandler={props.onButtonPress} />
		</ScrollView>
	)
}

FirstScreen.propTypes = {
	onButtonPress: PropTypes.func.isRequired
}

const styles = StyleSheet.create({
	container: {
		flex: 1,
		backgroundColor: '#2F9CB2'
	},
	scrollContainer: {
		justifyContent: 'center',
		alignItems: 'center'
	},
	title: {
		fontSize: 24,
		fontWeight: '500',
		color: '#ffffff',
		marginBottom: 30
	}
})

export default FirstScreen

Note you'll want to add some margin on the top to make sure things don't get hidden behind the nav bar, but I didn't do that in this app because it isn't meant to be a skeleton or boilerplate that covers all bases, just a simple example of how to combine Redux and NavExp.
Is there any more particular issue than the above that you are seeing?


chore: adding .github/CODEOWNERS to comply policy bot alert

Fixes #8021 .
This commit followed the sample https://github.com/GoogleCloudPlatform/sample-repo-template/blob/main/.github/CODEOWNERS
and https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file.

The CODEOWNERS file is valid


Simplify requirements

This PR simplify the requirements, and introduces extras_require to support:

when running pip install imjoy or pip install imjoy[worker] only requirements for the workers will be installed
when running pip install imjoy[engine] it will add extra requirements for running the engine
when running imjoy or python -m imjoy, it will upgrade the engine with pip install imjoy[engine]

It also reduces the occurrence of required packages into only once (in setup.py), the default plugin requirements becomes only imjoy[engine].
When running imjoy --dev, for each plugin process, the imjoy package folder will be added to PYTHONPATH and use python -m workers.python_worker, otherwise, the pip version will be used by running python -m imjoy.workers.python_worker.
Replace pathlib in setup.py to be compatible with python2 such that pip install imjoy can run in python2.
We should close #70 , in favor of this one.

This is a great improvement for maintainability. Nice!


Enable setting values in IDSMapping

This PR enables data to be set on the IDSMapping directly. We need this functionality so that we can overwrite empty arrays, i.e. *_error_upper in #156. I did this by deconstructing the key, and finding the corresponding array using getattr/setattr. This means the .fields key can no longer be used (we didn't use it anyway in the code).
It also means we don't have to rely on updating the numpy arrays in-place, like we do in the create step (profile[:] = np.array([...]) or using the out argument).

@v1kko Could you have a look at this and let me know if you see any issues?


Cleanup

These are purely non-functional changes.
The purpose of this branch is to bring the project in line with PSR-1/2 standards, as well as correct any minor instances of code smell and inconsistencies.

definitely should be merged; clean code - better readability!

Thanks for resubmitting 👍


Support external shuffle service

Add external shuffle service for yarn.
Add external shuffle manager for spark.

@gleon99
Please help to take a review when you're free.
Customer is using external service of sparkucx of my branch currently.
We'd like to merge the code from my branch into official.


collection.someData IS reactive, but collection.data.someData ISN'T

This is a known bug, although it is not urgent because you do not need to use the subgroup "data" is it only mirrors the data properties on the root of the collection object.
As it stands it's useful to know what is data and what isn't. To differentiate between groups, filters and routes, but the values will always remain the defaults for now.
mapData uses the root anyway, so this does not affect how the component sees your data, just how you choose to interact with it directly. to mutate data use collection.someData = newValue

Update: this means that using data or filters in the context object of an action, filter or watcher will not work. They'll have the initial state, but nothing after that. Will look into the cause and fix asap.

op, I just fixed it. https://github.com/jamiepine/pulse/commit/eb766f97bc575bef28dc8c67506f1f2704efc10e


Fixed players being unable to drop cards on canvas.

Contribution by @SalieriC . Fix for #16 .

@SalieriC I rebased your changes on the latest version and applied some minor adjustments. I also removed the "GM must view scene" restriction by passing the scene ID as you suggested.
GitHub doesn't seem to keep track of contributors if I rebase and squash commits, which is a bit dumb if you ask me. I'll add you to the list of contributors in the README.

Thank you very much. =)


Add RNG Peripheral

Adds support for the true random number generator (RNG) peripheral inside the ESP32.

Thanks!


DataTable 2 inside ScrollView (ListView, SingleSchildScrollView)

When we have a large enough list and it does not fit on the screen, internal scrolling of the list is triggered, but when we reach the end of the list, the overall scrolling of the screen does not work.

My widget 'DataTable 2' has static height and is inside the column. The column itself is inside ListView. @maxim-saplin

Hello, @maxim-saplin Please see an example of my problem and one of the solutions taken from the overflow stack. Perhaps you have other ideas about this.


read_dimensions non-ascii categoryids

categoryids that contain non-ASCII characters are being incorrectly altered by .lower(). This means the categoryid is not being found, which results in a failure.
For example "persÃ¶nlich_addressierte_Werbung_per_Post" should be lowered to "persÃ¶nlich_addressierte_werbung_per_post" and not "persã¶nlich_addressierte_werbung_per_post".

Resolved by #768.


server-side sorting/filtering using binding to amp-list[src]

I could see this in:

AMP for ecommerce page
amp-list example
other ideas?

Agreed — I think it's a perfect fit for the product category/browse/search-result page for the e-comm sample. For now amp-carousel doesn't support amp-list, so it might help if the items were shown more as a list or grid, rather than a set of carousels. WDYT?
Here's an example in the wild of what server-side sorting/filtering w/out page reload can look like for a product category/browse/search-result page.
Would also be nice to call out the general functionality in the amp-bind and amp-list pages (though depending on the amount of effort, you could either include an example inline, or just link to another example)
The general feature would also be useful for a blog or news publication category/search-results page, so it might be worth making an example for that as well at some point

@choumx I am working on a "sorting menu" like this: Once you click on a sort choice from the sorting list, that choice goes on top of the list.
I was trying to realize it in here by using amp-bind to change the value for each option using a temp value to do the swap. It doesn't seem to work, could you take a look? If you click on the menu choice (the one with the border) it shows the other option.
hight to low, low to high -> low to high, high to low
low to high, high to low -> hight to low, high to low  both are "high to low"
Do you think there could be an easiest way to achieve this?

@choumx Apology, amp-selector would be a better fit here, please ignore my previous comment.

The example works great!
To follow up on my request above: Is it possible to present the sort items in a list view, instead of in the carousel? I think it's great to show that changing the sort order is possible in the context of the carousel, but I think that presenting items in as a list, the format that users are used to seeing (and a format that merchants are used to using), will increase the likelihood that they will understand how this will be useful to them. What do you think?

Sounds great, I was confused as there is no carousel at the moment but it's just the display. Will move it into a list layout.

@ericlindley-g I deployed a new version, is this better?

Yes—it looks great! (and the search capability is awesome, too!)
Thanks for getting this in, and sorry I was unclear w/r/t the "carousel" when there wasn't actually one :P
It might be worth thinking a bit about how to make it work on desktop to fill up the space on the right, but at least for now the mobile view gives great examples to use in the blog post about amp-bind!

Ok, thanks

This is now deployed here.


Adding support for per-request headers

This PR adds support for the concept of per-request headers. These are introduced by adding a RequestHeaders structure which is similar to the existing CacheHeaders structure. These are configured on ApolloQueryCalls and provided to a new interceptor which adds the specified headers to the call when executed.
This PR also fixes an issue with the integration tests - SHA hashes can be different on different file systems based on encoding. On my local machine, at least, these hashes were different than the hard-coded values. So replacing the integration test SHAs with constants worked better. (Note - the tests don't seem to fully pass for me with ./gradlew check, with some lint errors in files I didn't touch)
This should help to address https://github.com/apollographql/apollo-android/issues/1183.

Looks great, question should ApolloMutationCall has the same API?

@sav007 - great callout. I can't see any good reason why this shouldn't work for mutations too, so I've added that API.


Use rules_python free-threading config settings

Eliminates the need for custom settings, and another flag to set for consuming builds.
This requires a bump to rules_python v0.39.0, which introduced free-threading support.

Note to self: I should probably add an "oldest supported Bazel" setup job to ensure that the minimum supported Bazel doesn't bump unexpectedly.


Add a submit button : Does not advance to next challenge

I get message that the challenge is passed, but the page does not advance to the next challenge
Challenge Add a Submit Button to a Form has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
<link href="http://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

<form action="/submit-cat-photo">
  <input type="text" placeholder="cat photo URL">
  <button type="submit">Submit</button>
</form>

Submit

Submit

Submit// Submit(S not s)


Adding script for multiband paper experiments

This PR adds a script, multiband_exps.sh, which runs experiments which are used to generate the ablation and classification detection figures from Bliss for multiband images.
NOTE: Have not yet tested if script runs end-to-end (i.e. first training three models and then running experiments), but it should work with minor modifications to multiband_exp.ipynb notebook.
Current issues:

Plots for galaxy classification figure look off w.r.t. axes ticks and cosmetic things.

@sawanp813 Is this ready to merge?

@sawanp813 Is this ready to merge?

I haven't run the script recently following the recent changes. I can verify everything checks out in the coming days, though if I remember correctly there were some issues with metrics that seemed off.


integrations/golang: Use full package paths when building.

Carefully tracking the path to the built package within the Go module allows us to refer to binaries in a build plan across modules.
Previously given the following specification in example.com/foo/xxx/binary.cue
build_plan: [{binary: "example.com/bar/yyy"}]

we would try to build a package with the desired local name (yyy), but within the "calling" module (example.com/foo/yyy).

I've tried build a few binaries in various locations including in workspace submodules and it seems that all works. 🤞


Retrieve and host DCP1 project matrix files and host them

The matrix service is being retired as part of the retirement of DCP1 at the end of the year.
The original plan was to serve the static matrix if you asked for a matrix for a project, and if you asked for a combined matrix across multiple projects, to return a sensible error as part of DCP2. There is now a significant risk of this not being delivered and SCEA and others rely on this.
We need to get a copy of all project matrices from DCP1 and transfer them to an FTP site where they can be publicly accessed.
FTP site setup instructions: https://tsc.ebi.ac.uk/article/ftp-request-new-ftp-site
We then need to work with SCEA to adapt their tool to pull the matrix files from the FTP site instead of the DCP1 matrix service.
https://github.com/ebi-gene-expression-group/hca-matrix-downloader

Recording some questions here while they are in my head:

What level of granularity will the projects need to be? i.e. will they need to be split by:

technology SS2/10x etc
species
tissue type i.e. primary vs cell line vs organoid
organ
developmental stage
other?

will we be expected to maintain this in the future? i.e. when there is an MVP where matrices can be downloaded from will we need to continue to add them to this ftp site? Will we need to replace these with the new matrices as they are generated under the 'phased' plan?

will we be expected to edit the code again if there is a new matrix service/alternative way of getting matrices programmatically?

https://humancellatlas.usegalaxy.eu/root?tool_id=toolshed.g2.bx.psu.edu%2Frepos%2Febi-gxa%2Fhca_matrix_downloader%2Fhca_matrix_downloader%2Fv0.0.3%2Bgalaxy0

Pablo's email comments:
1.- re-write the underpinnings of:
https://github.com/ebi-gene-expression-group/hca-matrix-downloader
so that it would retrieve results from, say, an ftp directory or an object store, after an initial search against something (a json file metadata->data path?) holding the exactly searchable metadata (Project title, Project label or ID) as explained on that repo.
If that is done without any changes to the interface, after some testing:
2.- we could simply bump the version of that repo and make a release of that
3.- bump the version of the bioconda package (https://bioconda.github.io/recipes/hca-matrix-downloader/README.html)
4.- update the Galaxy wrapper (https://github.com/ebi-gene-expression-group/container-galaxy-sc-tertiary/blob/develop/tools/tertiary-analysis/data-hca/matrix-service.xml) to look at the newer version of the bioconda package. I would still add that the data is currently being retrieved from EBI with some wording explaining why this is not coming from the HCA.
While the CLI does allow a more complex Matrix API query in json, we are not exposing this AFAIK in the Galaxy tool, so we can get away with not serving that part (with proper explanation on the CLI).
2, 3 and 4 are relatively straightforward if interfaces (how you use the CLI) are kept without changes in point 1.

currently working on trying to set up the ftp, we first need to set up a virtual user who will be able to write to the ftp, I have asked @tburdett to follow this up as needs to be requested by the GTL

i forked the repo and setup a branch to begin work on refactoring
https://github.com/ebi-ait/hca-matrix-downloader/tree/hca-dcp-ftp

Changes to the code are on a branch with a PR here: https://github.com/ebi-ait/hca-matrix-downloader/pull/1
We think the code should work but we are waiting for the ftp folder to be set up and the files to move there before we can test it properly.
@ESapenaVentura downloaded the matrix files to the cluster so they are ready to be moved to the ftp folder when it is created.
After we are confident the code changes work, I think the next step would be to contact Pablo to see if he is happy with the changes and to get his help with releasing the code to bioconda and testing it works in their galaxy instance.

The FTP site is ready and with all the matrix files available
I have tested the code:

Got UUID with all 3 types of search (UUID, project_shortname, project_title)
Tested what happens when it doesn't exist (prints and exits)
Downloaded a mtx file with project name
Downloaded a loom file with project name

And it works fine. Currently talking with Pablo about what are the best next steps

Since the next steps are on their end (even if we end up helping) should we move this ticket to done @clairerye ?

Pablo said that this is ok and that they will test on their end and put the package in BioConda.
We are done on our side so moving to done

thanks @mshadbolt and @ESapenaVentura for getting this done so efficiently!


Save automatically the conversation on blob storage for future analysis

Describe the solution you'd like
It would very useful have in a settings form, the chance to enable auto save conversation of the bot in a blob storage, in order to analyze the answers of the bot for future improving.
thanks.

Thanks @JonathanFingold for the suggestion. We don't have plans to add this functionality natively in Composer any time soon, but achieving this will be possible while utilizing Composer extensions and custom runtime functionality. We're working on these items right now and will have documentation for users to reference in the coming months. I'll close this for now, thanks!


Vs2015 support

Support planned?

Yes.  I'm going to spend some time this weekend and release this and a few other extensions for VS 2015

:+1:


fix: fix deploy tx RLP decoding

The transaction RLP decoding logic assumes to is present but it's actually not true for contract deployment transactions. The library fails to decode such transactions as a result.
This PR fixes it.

Fixed formatting. Didn't realize I should use nightly tool chain for that lol.


Fixed SCT-2780, SCT-2781 and SCT-2782.

This PR adds new sorting options, real names from users and data type statistics in narrative previews. It also adds a cache to reduce the number of HTTP requests a client makes when using the dashboard.
Lexicographical sorting is added to the possible NarrativeList sorts as well as caching to avoid repeating the same HTTP requests. Narrative previews are also cached. This caching is only done in memory and will be lost if the client navigates away from the page. Even so, this caching is designed so that future versions may use string based key-value stores such as localStorage.
Bare usernames are replaced with real names, and in the narrative detail these names are links to the user's profile. These links have the username as their title attribute so that it may be seen on hover. While this is not visible in mobile views, the username is listed on the user profile. These usernames are also cached to prevent extraneous HTTP requests. The summary also identifies the most common data types within a narrative. Further, for shared narratives only the first few users are to show up by default but there is an option to see the rest.

I'm going to merge this.  If there is anything critical that was raised we can deal with it in the next PR.


MySQL - Atlas fails to inpect schema when a column is specified as an unsigned float

It seems that when you create a column in mysql with an unsigned float, Atlas cannot parse its precision in sql/mysql/convert.go and throws a lovely error message like below:
Error: mysql: parse precision "unsigned"

hey @megalan247 ,
thanks for reporting this!
note that MySQL docs state:

As of MySQL 8.0.17, the UNSIGNED attribute is deprecated for columns of type FLOAT, DOUBLE, and DECIMAL (and any synonyms); you should expect support for it to be removed in a future version of MySQL. Consider using a simple CHECK constraint instead for such columns.

However, Atlas should definitely support this for the versions that do. We will work on a fix and update here.

Hey @megalan247, I just merged a PR to fix this. Please try again with the latest master.
Don't hesitate to reach out to us, if you have any more questions.


Catch exceptions when errors rendering template

This will raise a Home Assistant specific error when an error occurs when rendering a template. When it is processing a value, it will log the error but return the original value instead.
CC: @philipbl

@philipbl I've updated the return value to be user defined. That way the caller can decide what to do with the value in case of an error. If people want more power they should use the render method directly.


Added Enhanced Ecommerce Purchase

Hoping this can be of use for more people, on the Enhanced Ecommerce there is no use of currency. I only coded and tested this funcitonality in the range of Enhanced Ecommerce. Thank you.

@patrys Can you merge this?

Thank you


Update grape-entity

https://groups.google.com/forum/m/#!topic/ruby-grape/H7O3fX8TA24
There's a security vulnerability in versions before 0.6.0.

Are you working on a PR for this?
The CHANGELOG for 0.6.0 doesn't mention any breaking changes.


Proposal: add option to disable axes independently

Creating something like this would be possible if the Y axis was disabled.

https://github.com/ksassnowski/vueclid/assets/6376814/0be1316b-55b4-4d4d-a809-6c33850e5f76
I was thinking, If the elements had data attributes it could also be easy to address them with css.


Heston volatility should be placed as a parameter of Heston class

Currently, Heston class has variance but doesn't have volatility as a buffer.
However, in terms of calculating delta or others, volatility should be registered.

Codecov Report

Merging #201 (3662f90) into develop (1904018) will decrease coverage by 0.24%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           develop     #201      +/-   ##
===========================================
- Coverage   100.00%   99.75%   -0.25%
===========================================
  Files           41       41
  Lines         1203     1233      +30
===========================================
+ Hits          1203     1230      +27
- Misses           0        3       +3

Impacted Files
Coverage Δ

pfhedge/features/functional.py
89.28% <40.00%> (-10.72%)
:arrow_down:

pfhedge/instruments/primary/heston.py
100.00% <100.00%> (ø)

pfhedge/nn/modules/ww.py
100.00% <0.00%> (ø)

pfhedge/stochastic/cir.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/loss.py
100.00% <0.00%> (ø)

pfhedge/features/_getter.py
100.00% <0.00%> (ø)

pfhedge/instruments/base.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/clamp.py
100.00% <0.00%> (ø)

pfhedge/features/features.py
100.00% <0.00%> (ø)

pfhedge/nn/modules/hedger.py
100.00% <0.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1904018...3662f90. Read the comment docs.

Thank you for the suggestion! It is nice to make volatility accessible as an attribute.
It seems better to make it property from the viewpoint of memory efficiency. What do you think?

I apologize I don't know much about memory efficiency.
Thus, I'll leave it to you.

Although totally different from this, I think the default value of sigma in Heston class, Heston prossess generation, cir process generation.
Why did you set the sigma to 2.0?
from pfhedge.stochastic.cir import generate_cir
generate_cir(10,100, sigma=2.0)
generate_cir(10,100, sigma=0.2)

sigma=2.0 seems too big and makes many 0 as a result.
This means no volatility.
I think sigma=0.2 seems better.
https://doi.org/10.1007/978-3-319-05221-2_3
p.75 Fig. 3.1 seems a good reference for it.

Why did you set the sigma to 2.0?

I chose the default parameters as that in the experimental setup of Deep Hedging (eq. (5.2)). But I am also skeptical that it is a sensible value because it actually breaks the Feller condition and results in vanishing variances. I appreciate it if you could create a separate issue on that so we can make a further discussion.

I think I didn't make it clear enough.
We might want to avoid registering equivalent buffers because a buffer, which typically is of size (10000, 20), can be MB-sized.
Could you take a look at https://github.com/masanorihirano/pfhedge/pull/1 and merge it if looks fine?

I have understood basically.
Now, I reviewed your excellent code and accepted the modification.


Java (Gradle) ignoring maven central

Package ecosystem
java
Package manager version
gradle 7.0.2
Language version
java 11 & 16
Manifest location and content prior to update

build.gradle
luna-main/build.gradle
luna-cacti/build.gradle
luna-weather/build.gradle
luna-dvb/build.gradle

dependabot.yml content
https://github.com/MarcelCoding/luna/blob/main/.github/dependabot.yaml
Updated dependency
org.springdoc:springdoc-openapi-webflux-ui 1.5.6
What you expected to see, versus what you actually saw
As you see maven central is not checked:
updater | INFO <job_161072655> Checking if org.springdoc:springdoc-openapi-webflux-ui 1.5.6 needs updating
  proxy | 2021/06/14 07:35:00 [048] GET https://raw.githubusercontent.com:443/getnova/maven/main/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [048] 404 https://raw.githubusercontent.com:443/getnova/maven/main/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [050] GET https://repo.spring.io:443/release/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [050] 404 https://repo.spring.io:443/release/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [052] GET https://repo.spring.io:443/milestone/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [052] 404 https://repo.spring.io:443/milestone/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [054] GET https://repo.spring.io:443/snapshot/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
  proxy | 2021/06/14 07:35:00 [054] 404 https://repo.spring.io:443/snapshot/org/springdoc/springdoc-openapi-webflux-ui/maven-metadata.xml
updater | INFO <job_161072655> Latest version is
updater | INFO <job_161072655> Requirements to unlock update_not_possible
updater | INFO <job_161072655> Requirements update strategy
updater | INFO <job_161072655> No update possible for org.springdoc:springdoc-openapi-webflux-ui 1.5.6

But Maven Central is configured: https://github.com/MarcelCoding/luna/blob/main/build.gradle#L35-L51
Native package manager behavior
Gradle is capable to locate packages in maven central.
Images of the diff or a link to the PR, issue or logs
Logs

🕹 Bonus points: Smallest manifest that reproduces the issue

Our project is suffering from the same issue I think: https://github.com/vector-im/element-android/issues/5961.
@MarcelCoding did you find a way to workaround the problem?

Unfortunately not, I could try not using mavenCentral() but like the actual URL maven { url 'https://repo1.maven.org/maven2/' }. Idk why I didn't tried it yet...
... it actually worked. I am so stupid.
@bmarty

Ideally we'd parse this out as a special case and translate it to the known maven central URL, but I looked at the commit where you fixed this (https://github.com/MarcelCoding/luna/commit/7e2053bd7872a7ddf964ba676de1649dfde8c749) and it looks like mavenCentral() allows specifying URL excludes, so it gets tricky fast:
https://github.com/MarcelCoding/luna/commit/7e2053bd7872a7ddf964ba676de1649dfde8c749#diff-49a96e7eea8a94af862798a45174e6ac43eb4f8b4bd40759b5da63ba31ec3ef7L39-L41
Our current parser for Maven is completely ruby based, and a bit primitive... long term we'd like to move to a native Java-based helper which would allow directly processing code when fetching the packages, but we're unlikely to get to that for a while.
Thankfully the workaround is trivial.