#41 table relative paths

Resolves #41 by adding basePath for remote datapackages and after that using url.resolve in Resources class to point to the relative resource.

@dumyan
One other thing - I suppose we need much more tests for path resolutions. Could you write a few additional tests (for datapackage and resource) with comprehensive list of combinations (basePath/path) to cover all edge cases?
it('source/type correctly works with base path', async () => {
  const paths = [
    {base: 'folder1', path: 'data/data.csv', source: 'folder1/data/data.csv', type: 'local'},
    // ... like 10 more)
  ]
  paths.forEach({base, path, source, type} => {
    const resource = new Resource({path}, base)
    assert(resource.source === source)
    assert(resource.type === type)
  })
})

The same technique could be used for other tests to ensure Resource.source/type works correctly on all possible input data.


Fix Subject queue not making sense

PR Overview

There are two issues with the Panoptes /queued request for Subjects. (See Issue #125)

One: logged in vs non-logged in get very different queues.
Two: when we set a new Subject Set id, the existing queue isn't cleared, so the new Subject Set isn't actually requested.

This PR fixes Issue TWO only, by resetting the internal queue whenever a new Subject ID is selected.

Testing is Madness
TL;DR this is difficult to test, but it looks like it works to me.
Anyway. Testing this will be odd given that ASM has about 5 Subject Queues with only 1 Subject each, and given Issue One above. This is the only way I can tell that it works, on localhost, while not logged in: (It always looks fine while logged in due to the combination of Issue 1 and the small Subject Sets.)

As a non-logged in user, I always see the same Subject when I choose a Subject Set, e.g. "1800-1839". (Expected: since non-logged in users always receive the same queue in the same order (see Issue One), this means I should always get the same first subject in the ever-resetting queue. Prior to this PR: selecting a new Subject Set (e.g. from "1800-1839") from the home page over and over again has the weird effect of processing through the same queue, resulting in a parade of exact Subjects going on over and over again.).
As a non-logged in user, if I click Transcribe in the navi, then home, then Transcribe, then home, etc, I see the "processing through the same queue" mentioned above, which is (mostly) expected in this context.
As a logged in user, I notice no changes. (Expected - logged-in users only ever get Subject queues with one Subject since each Subject Set has only one Subject. Therefore, their queue is always fresh.)

Status
Ready for review, @wgranger , but even if this is approved, it'll be worth monitoring this matter when we go into internal/beta testing and have larger Subject Sets to play with.

LGTM


Authors are written in lowercase in publications

I used the academic-admin tool to import publications automatically as written here.
Why did I get the authors' last names and initials in lowercase for all publications?

The generated markdown looks good
---
title: "Tunable Microwave Single-Photon Source Based on Transmon Qubit with High Efficiency"
date: 2020-03-01
publishDate: 2020-06-28T08:24:42.330115Z
authors: ["Yu Zhou", "Zhihui Peng", "Yuta Horiuchi", "O.V. Astafiev", "J.S. Tsai"]
publication_types: ["2"]
abstract: ""
featured: false
publication: "*Phys. Rev. Applied*"
url_pdf: "https://link.aps.org/doi/10.1103/PhysRevApplied.13.034007"
doi: "10.1103/PhysRevApplied.13.034007"
---

BibTex in the same folder
@article{PhysRevApplied.13.034007,
 author = {Zhou, Yu and Peng, Zhihui and Horiuchi, Yuta and Astafiev, O.V. and Tsai, J.S.},
 doi = {10.1103/PhysRevApplied.13.034007},
 issue = {3},
 journal = {Phys. Rev. Applied},
 month = {Mar},
 numpages = {11},
 pages = {034007},
 publisher = {American Physical Society},
 title = {Tunable Microwave Single-Photon Source Based on Transmon Qubit with High Efficiency},
 url = {https://link.aps.org/doi/10.1103/PhysRevApplied.13.034007},
 volume = {13},
 year = {2020}
}

How do I make all initial letters in names capital?

I had the same issue, updating Hugo solved it. See #1731

Thank you. Solved my problem

I had the same issue, updating Hugo solved it. See #1731


MSID: 87949 Version: 1 DOI: 2<IP_ADDRESS>3343

"msas": "Developmental Biology", "Physics of Living Systems"
"msid": "87949"
"preprintDoi": "10.1101/2<IP_ADDRESS>3343"
"Reviewed Preprint posted": "2023-08-09"
"Sent for peer review": "2023-05-10"
"Posted to bioRxiv": "2023-03-23" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>3343v1/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=87949)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/87949/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3343)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/87949/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/87949)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/87949

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/87949

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/87949/v1/87949-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/87949)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

All corresponding authors have same email address; extra image in bioRxiv (striking image); elocations missing from reference list; volume info missing from He et al., 2016 (conference ref so I assume this was just dropped)


upgrade(package): Bump dependencies

debug 2.6.1 -> 3.1.0
jsdoc-to-markdown 2.0.1 -> 3.0.0
mocha 3.2.0 -> 4.0.1

Change-Type: patch

@jversionbumper :'D
Someone's gotta do it while we don't have a greenkeeper


DataCentricFLClient memory leak

Description
Allocated memory is not released after .get() when using DataCentricFLClient.
How to Reproduce

Launch PyGrid Node ./run.sh --id bot001 --host <IP_ADDRESS> --port 8777 --start_local_db.
Run free -m -s 5 to monitor memory usage
Run the following code

import torch
import syft as sy
from syft.grid.clients.data_centric_fl_client import DataCentricFLClient

hook = sy.TorchHook(torch)
device = torch.device("cpu")
worker = DataCentricFLClient(hook, "ws://localhost:8777")

x = torch.zeros(1000, 1000).to(device)
while True:
	x_copy = x.copy()
	x_ptr = x_copy.send(worker)
	x_ptr.get()

The amount of free memory decreases continuously

Expected Behavior
Memory should be released after .get().
P.S. WebsocketClientWorker works fine (memory usage will keep at a certain level).
System Information

OS: Ubuntu
OS Version: 18.04.4 LTS
Language Version: Python 3.7.7
Package Manager Version: Conda 4.8.2
PySyft Version: 0.2.8

Additional Context
Example for WebsocketClientWorker
import torch
import syft as sy
from syft.workers.websocket_client import WebsocketClientWorker

hook = sy.TorchHook(torch)
device = torch.device("cpu")
worker = WebsocketClientWorker(hook=hook, id="bot001", host="localhost", port=8777)

x = torch.zeros(1000, 1000).to(device)
while True:
	x_copy = x.copy()
	x_ptr = x_copy.send(worker)
	x_ptr.get()

0.2.x is no longer supported.


echo: add Java package name and outer class name to be used in grpc java testing

Please provide a description of this PR:
We want to use the echo.proto in grpc java interop tests with Istio. The generated code should go into designated package and outer classname.

CC @costinm @stevenctl - this is for grpc-java's interop testing with Istio. Note that we import protos like this from their original source repo instead of making copies and modifying them locally. So to the extent possible we would like the original to reflect our requirements

Thanks @howardjohn for the approval. What else needs to happen to finish tests and then merge the PR?

/ok-to-test
forgot this

@sanjaypujare: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7615f460dc559681b443d8302887b4b99878792d
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest-required


Firebase fetchWithExpirationDuration completion handler not called

The callback isn't received from "fetchWithExpirationDuration" API. The completion handler isn't being called and hence, the remote config changes are not in effect.
    long expirationDuration = 3600;
    [self.remoteConfig fetchWithExpirationDuration:expirationDuration completionHandler:^(FIRRemoteConfigFetchStatus status, NSError *error) {
        if (status == FIRRemoteConfigFetchStatusSuccess) {
            NSLog(@"Config fetched!");
            [self.remoteConfig activateWithCompletionHandler:^(NSError * _Nullable error) {
               // [self.delegate configDownloadComplete];
            }];
        } else {
            NSLog(@"Config not fetched");
            NSLog(@"Error %@", error.localizedDescription);
        }
    }];

Hi there,
Is anything output to the console during this time, and are you connected to the network or are you in Airplane mode? You can set the logging level with [[FIRConfiguration shared] setLoggingLevel:FIRLoggingLevelMax];
Thanks, this information will help us debug the issue further.

Thanks, I will share the logs.
In my project, FIRConfiguration is added in WxWorks and in the project. I am getting duplicate warnings for the same.
Can this be the issue? If yes, please suggest the resolution.

Also, I do have network connectivity and the Firebase remote config is integrated via pods.

Thanks for the update. I'm not sure what you mean by WxWorks so I'm not sure if that affects it at all. Did you see any logs that you could share?

The WxWorks is a third party framework provided by WSI.
As requested, here are the logs:-
019-09-19 09:25:26.075716+0530  [2653:614558] 6.7.0 - [Firebase/Core][I-COR000001] Configuring the default app. 2019-09-19 09:25:26.076347+0530  [2653:614558] 6.7.0 - [Firebase/Core][I-COR000033] Data Collection flag is not set. 2019-09-19 09:25:26.076652+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: { 2019-09-19 09:25:26.077613+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query { 2019-09-19 09:25:26.078695+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query { 2019-09-19 09:25:26.115518+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query { 2019-09-19 09:25:26.116733+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: { 2019-09-19 09:25:26.117661+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][I-RCN000062] Loading database at path /var/mobile/Containers/Data/Application/394F7131-4E01-4155-8549-ED254A6E797A/Library/Application Support/Google/RemoteConfig/RemoteConfig.sqlite3 2019-09-19 09:25:26.124818+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][I-RCN000067] Successfully set configSettings. Developer Mode: false, Minimum Fetch Interval:0.000000, Fetch timeout:60.000000 2019-09-19 09:25:26.125060+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][I-RCN000039] Starting requesting token. 2019-09-19 09:25:26.125148+0530  [2653:614558] 6.7.0 - [Firebase/InstanceID][I-IID007006] Checkin parameters: { 2019-09-19 09:25:26.125308+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][2019-09-19 09:25:26.125390+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:26.125463+0530  [2653:614558] 6.7.0 - [Firebase/RemoteConfig][I-RCN0002019-09-19 09:25:26.144066+0530  [2653:614557]  - [Firebase/Analytics][I-ACS025028] AdMob and Firebase are in use in this app, but are not linked. For analytics data consistency and integrity, it is highly recommended that you link your AdMob app to the corresponding Firebase app and re-download the GoogleServices-Info.plist file. See https://support.google.com/admob/answer/6383165 for more information. 2019-09-19 09:25:26.155188+0530  [2653:614555]  - [Firebase/Analytics][I-ACS023007] Analytics v.50400000 started 2019-09-19 09:25:26.155542+0530  [2653:614555]  - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r) 2019-09-19 09:25:26.486110+0530  [2653:614567] 6.7.0 - [Firebase/InstanceID][I-IID007002] Invalid last checkin timestamp 2019-09-19 03:55:26 +0000 in future. 2019-09-19 09:25:26.486289+0530  [2653:614567] 6.7.0 - [Firebase/InstanceID][I-IID007003] Checkin successful with authId:<PHONE_NUMBER>841353695, digest: l1RCL4dda1HhjZlLfof2Bg==, lastCheckinTimestamp:<PHONE_NUMBER>000 53:614567] 6.7.0 - [Firebase/InstanceID][I-IID005004] Successfully got checkin credentials 2019-09-19 09:25:26.486591+0530  [2653:614567] 6.7.0 - [Firebase/InstanceID][I-IID008010] Checkin plist file is saved 614567] 6.7.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query { 2019-09-19 09:25:27.123032+0530  [2653:614555] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:27.130570+0530  [2653:614600]  - [Firebase/Analytics][I-ACS025026] Deferring to Firebase for event data collection 2019-09-19 09:25:27.651991+0530  [2653:614583] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:29.360997+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:29.361793+0530  [2653:614557] 6.7.0 - [Firebase/InstanceID][I-IID014000] Fetch new token for authorizedEntity:<PHONE_NUMBER>81, scope: * 2019-09-19 09:25:29.362125+0530  [2653:614557] 6.7.0 - [Firebase/InstanceID][I-IID020000] Register request to https://fcmtoken.googleapis.com/register content: X-osv=12.4.1&device=5738387946841353695&X-scope=*&plat=2&app=com.pnsdigital.weather. &app_ver=6.0&X-cliv=fiid-(null)&sender=863359794381&X-subtype=863359794381&appid=ep4rcr4OrlM&gmp_app_id=1:863359794381:ios:d53cac7918151276 2019-09-19 09:25:30.083700+0530  [2653:614557] 6.7.0 - [Firebase/InstanceID][I-IID023002] Couldn't delete item from Keychain OSStatus: -25300 with the keychain query { 2019-09-19 09:25:30.111219+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:30.366022+0530  [2653:614557] 6.7.0 - [Firebase/InstanceID][I-IID014001] Token fetch successful, token: ep4rcr4OrlM:APA91bG_7-mKQTZ6cch99Wc4CIiPSmirpMXdVv3czTPNPk8amKskYLJmyG22TxMCtbPFTaHVwpWaWRNFlXGOYFjvr1J1eEHDi15OV3-Y7mZF9SerNu4jbRCSwNlZZJgFO7umGpss7U1p, authorizedEntity:<PHONE_NUMBER>81, scope:* 2019-09-19 09:25:30.367083+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000022] Success to get iid : ep4rcr4OrlM. 2019-09-19 09:25:30.367880+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000024] Success to get device authentication ID:<PHONE_NUMBER>841353695, security token:<PHONE_NUMBER>45892552. 2019-09-19 09:25:30.367967+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000060] Fetch with user properties completed. 2019-09-19 09:25:31.733273+0530  [2653:614557] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:33.371823+0530  [2653:614600] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON. 2019-09-19 09:25:33.533786+0530  [2653:614601] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON.

Another set of detailed logs:-
[Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {     acct = "com.google.iid.checkin-account";     class = genp;     gena = "com.google.iid";     "m_Limit" = "m_LimitAll";     "r_Attributes" = 1;     "r_Data" = 1;     svce = "com.google.iid.checkin-service"; } 2019-09-19 09:34:15.798164+0530 [2687:618177] 6.7.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {     atag = <636f6d2e 676f6f67 6c652e69 69642d7c 4b7c>;     class = keys;     "r_Ref" = 1;     type = 42; } 2019-09-19 09:34:15.798261+0530 [2687:618177] 6.7.0 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: {     atag = <636f6d2e 676f6f67 6c652e69 69642d7c 507c>;     class = keys;     "r_Ref" = 1;     type = 42; } 2019-09-19 09:34:15.798341+0530 [2687:618177] 6.7.0 - [Firebase/InstanceID][I-IID009000] No keypair info is found with tag com.google.iid-|K| 2019-09-19 09:34:15.798415+0530 [2687:618177] 6.7.0 - [Firebase/InstanceID][I-IID009006] There's no legacy keypair so no need to do migration. 019-09-19 09:34:15.798505+0530 [2687:618177] 6.7.0 - [Firebase/RemoteConfig][I-RCN000062] Loading database at path /var/mobile/Containers/Data/Application/5B48DF6F-4D46-46BF-ABB7-9598E3D6A564/Library/Application Support/Google/RemoteConfig/RemoteConfig.sqlite3 2019-09-19 09:34:15.798670+0530 [2687:618177] 6.7.0 - [Firebase/RemoteConfig][I-RCN000067] Successfully set configSettings. Developer Mode: false, Minimum Fetch Interval:0.000000, Fetch timeout:60.000000 2019-09-19 09:34:15.798757+0530 [2687:618177] 6.7.0 - [Firebase/RemoteConfig][I-RCN000039] Starting requesting token. 2019-09-19 09:34:15.798832+0530 [2687:618177] 6.7.0 - [Firebase/RemoteConfig][I-RCN000065] Error parsing data as JSON.

@SachinAhujaGit Can you dial down the fetchTimeout to see if the handler is invoked? https://firebase.google.com/docs/reference/swift/firebaseremoteconfig/api/reference/Classes/RemoteConfigSettings#fetchtimeout
Also, am seeing "Error parsing data as JSON." in your logs. This is logged if a Remote Config key's value cannot be parsed as JSON. https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseRemoteConfig/Sources/FIRConfigValue.m#L71
Do you have some code that is incorrectly reading a key's value as JSONValue somewhere?

Thanks, @dmandar.
I reduced the fetchTimeOut to 30 seconds, but the handler isn't invoked. Then, I tried with 3 sec but still the same result.
There are keys in Remote Config with string value (without double quotes) like data URLs that is considered as invalid JSON. So, the error is coming for the same.
FYI..when I integrated it around 15 days back, the handler was getting invoked but from the last few days, the callback isn't received.  I haven't changed anything in the code but still it isn't working now. Please advise.

@SachinAhujaGit can you try deleting and reinstalling the app? Re: the error, yes, that makes sense. Please use JSONValue only while parsing a value stored as JSON in the firebase console. Also, what version of RC are you using?

@dmandar I have already tried deleting and reinstalling the app. It isn't working.
The Firebase remote config is integrated via pods.. so the latest FirebaseRemoteConfig version "4.3.0" is in effect.

Is this issue related to https://github.com/firebase/firebase-ios-sdk/issues/3818 ?

That sounds plausible. Do you have dynamic frameworks / the [FIRApp configure] not called warning (don't see it in the logs above)?

Also, can you try fixing/commenting out the invalid JSONValue parse error and get updated logs? The only last log of interest is [Firebase/RemoteConfig][I-RCN000039] Starting requesting token. with the error coming up right after (would have expected a read of config values only upon completion of the fetch request)

Yes, I do have dynamic frameworks. I debugged it further and found that the issue comes in RCNFetch.m (Line 277):
   [analytics getUserPropertiesWithCallback:completionHandler];
Here are the logs after commenting invalid JSONValue parse error:-
PodsDummy_FirebaseCore is implemented in both /private/var/containers/Bundle/Application/03210914-C073-4131-9697-7050D4A9AF5F/ .app/Frameworks/WxWorks.framework/WxWorks (0x10cd60980) and /var/containers/Bundle/Application/03210914-C073-4131-9697-7050D4A2019-09-20 12:20:54.879995+0530  [418:35354]  - <AppMeasurement>[I-ACS036002] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist 2019-09-20 12:20:54.905115+0530  [418:35358]  - <AppMeasurement>[I-ACS036002] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist 2019-09-20 12:21:00.492915+0530  [418:35361] 6.8.1 - [Firebase/Core][I-COR000001] Configuring the default app. 2019-09-20 12:21:00.493081+0530  [418:35361] 6.8.1 - [Firebase/Core][I-COR000033] Data Collection flag is not set. 2019-09-20 12:21:00.501429+0530  [418:35370]  - [Firebase/Analytics][I-ACS025028] AdMob and Firebase are in use in this app, but are not linked. For analytics data consistency and integrity, it is highly recommended that you link your AdMob app to the corresponding Firebase app and re-download the GoogleServices-Info.plist file. See https://support.google.com/admob/answer/6383165 for more information. 2019-09-20 12:21:00.504179+0530  [418:35361]  - [Firebase/Analytics][I-ACS023007] Analytics v.50400000 started 2019-09-20 12:21:00.504179+0530  [418:35370] 6.8.1 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: { 2019-09-20 12:21:00.504242+0530  [418:35361]  - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r) 2019-09-20 12:21:00.510116+0530  [418:35354] 6.8.1 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: { 2019-09-20 12:21:00.510749+0530  [418:35354] 6.8.1 - [Firebase/InstanceID][I-IID023000] Info is not found in Keychain. OSStatus: -25300. Keychain query: { 2019-09-20 12:21:00.511029+0530  [418:35354] 6.8.1 - [Firebase/InstanceID][I-IID009000] No keypair info is found with tag com.google.iid-|K| 2019-09-20 12:21:00.511067+0530  [418:35354] 6.8.1 - [Firebase/InstanceID][I-IID009006] There's no legacy keypair so no need to do migration. 2019-09-20 12:21:00.514420+0530  [418:35354] 6.8.1 - [Firebase/RemoteConfig][I-RCN000062] Loading database at path /var/mobile/Containers/Data/Application/A612D218-C4E8-4CCD-A42D-4FFEEE63AADB/Library/Application Support/Google/RemoteConfig/RemoteConfig.sqlite3 2019-09-20 12:21:09.043537+0530  [418:35399] 6.8.1 - [Firebase/RemoteConfig][I-RCN000067] Successfully set configSettings. Developer Mode: false, Minimum Fetch Interval:0.000000, Fetch timeout:60.000000 2019-09-20 12:21:09.045560+0530  [418:35399] 6.8.1 - [Firebase/RemoteConfig][I-RCN000039] Starting requesting token. 2019-09-20 12:21:09.301267+0530  [418:35370]  - [Firebase/Analytics][I-ACS025026] Deferring to Firebase for event data collection 2019-09-20 12:21:39.478753+0530  [418:35440] 6.8.1 - [Firebase/RemoteConfig][I-RCN000022] Success to get iid : dASsvCYOD3E. 2019-09-20 12:21:39.479036+0530  [418:35440] 6.8.1 - [Firebase/RemoteConfig][I-RCN000024] Success to get device authentication ID:<PHONE_NUMBER>959943453, security token:<PHONE_NUMBER>699179402. 2019-09-20 12:21:39.479132+0530  [418:35440] 6.8.1 - [Firebase/RemoteConfig][I-RCN000060] Fetch with user properties completed.

The project is using dynamic frameworks but that should not lead to fetchWithExpirationDuration
completion handler not being called.
Please advise as we need to go live ASAP.

PodsDummy_FirebaseCore is implemented in both /private/var/containers/Bundle/Application/03210914-C073-4131-9697-7050D4A9AF5F/ .app/Frameworks/WxWorks.framework/WxWorks (0x10cd60980) and /var/containers/Bundle/Application/03210914-C073-4131-9697-7050D4A2019-09-20 12:20:54.879995+0530 [418:35354]
is like a problem. Firebase is not designed to work from multiple copies in a single app. I suggest restructuring the app so that Firebase is only linked once.

Thanks, that worked.
I have removed Firebase.core from pods and is now able to fetch the config.


Make stub work for prototype methods

This is incredibly useful if you work with named constructors and
prototype methods.
All my classes look like this:
function MyClass() {}

MyClass.prototype.myFunc = function() {};

Without this patch sinon.stub(new MyClass) does not stub my prototype methods.
Let me know what you think!

+1 to that. We had this discussion over twitter:
https://twitter.com/#!/cjno/status/126676122242007040
https://twitter.com/#!/cjno/status/126676251661443072
https://twitter.com/#!/cjno/status/126676369903067136
While the argument "I don't want Sinon to help you successfully test an object that uses a collaborator in a way that fails in production" is totally valid, I still think there should be a way to stub objects with prototype methods too.
If not within the stub method then maybe in something like "stubWithPrototype" (bit verbose though).

If we're going to allow stubbing inherited properties, is there any point in restricting it to the first object on the prototype chain? I.e. do we need the isOwnProperty || isProtoProperty check? Wouldn't an unfiltered for-in be just as good?

If we're going to allow stubbing inherited properties, is there any point in restricting it to the first object on the prototype chain? I.e. do we need the isOwnProperty || isProtoProperty check? Wouldn't an unfiltered for-in be just as good?

That would work for me. Generally if I do sinon.stub(obj) I intend to stub all methods on that object, regardless of where they came from. If I want fine grained control, I will generally stub individual methods instead.
Let me know and I will modify the this patch.

I think I agree. I'm not entirely sure why the hasOwnProperty check is in there. What I don't want Sinon to do is to fake non-existing properties (i.e. sinon.stub(obj, "nonExistentProperty")). I don't actually mind faking inherited methods.
Pull out the filter, and I'll pull it!

Btw. I just figured out that another rather doable way is:
var stub = sinon.stub(Object.create(MyClass.prototype));

But generally I would probably still prefer what's discussed above as it feels more natural to do the stubbing that way.

That's definitely less easy on the eyes :) But I'll pull your change if you pick out the filter, so it just stubs whatever method the object has, regardless of prototype chain origin.

That's definitely less easy on the eyes :)

Turns out it wasn't actually working with an unpatched version of sinon either (npm was doing unexpected things, see https://github.com/isaacs/npm/issues/1727).
Anyway, I submitted the discussed simplification above, all tests passing!

Sorry for all the little commits, I can squash this into one if you'd like me to. But should be good now.

No, I like small commits :) Thanks again!

Sweet, thanks a lot!


Upgrade to Visual Studio 2019

This PR creates Visual Studio 2019 solution files and upgrades the appveyor build environment to use VS2019.

Forgot to mention in commit notes, this VS project settings ref's #136. I see a distinct change in build times on my local machine. All builds are currently queued on appveyor so waiting for it to do its thing.

I was just going to say, oh sweet, AppVeyor already supports VS2019, then saw your last commit about it being the Preview version. Still, should be good enough.

Seems there is a problem with the SDL2 redist NuGet Package:
C:\projects\nas2d-core\proj\vs2017\NAS2D.vcxproj(322,5): error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is packages\sdl2.nuget.redist.2.0.9\build\native\sdl2.nuget.redist.targets.

This is odd, because the package seems to have been installed:
nuget restore proj/vs2019
MSBuild auto-detection: using msbuild version '16.0.360.33175' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\bin'.
Restoring NuGet package sdl2.nuget.redist.2.0.9.
Restoring NuGet package sdl2.nuget.2.0.9.
  GET https://api.nuget.org/v3-flatcontainer/sdl2.nuget.redist/2.0.9/sdl2.nuget.redist.2.0.9.nupkg
  GET https://api.nuget.org/v3-flatcontainer/sdl2.nuget/2.0.9/sdl2.nuget.2.0.9.nupkg
  OK https://api.nuget.org/v3-flatcontainer/sdl2.nuget/2.0.9/sdl2.nuget.2.0.9.nupkg 18ms
Installing sdl2.nuget 2.0.9.
  OK https://api.nuget.org/v3-flatcontainer/sdl2.nuget.redist/2.0.9/sdl2.nuget.redist.2.0.9.nupkg 55ms
Installing sdl2.nuget.redist 2.0.9.
Adding package 'sdl2.nuget.redist.2.0.9' to folder 'C:\projects\nas2d-core\proj\vs2019\packages'
Added package 'sdl2.nuget.redist.2.0.9' to folder 'C:\projects\nas2d-core\proj\vs2019\packages'

I noticed in the original error message, it mentions build\native\sdl2.nuget.redist.targets, so perhaps the package is missing some native component.

To automatically close an issue when the PR is merged, the top post needs to reference the issue with close/fix/resolve (or conjugated forms of those). Any subsequent post will only create a reference to the Issue, not auto close it on merge:
https://help.github.com/en/articles/closing-issues-using-keywords
I'd recommend editing the first post to create a close reference for the Issue.

Great, suddenly TravisCI is failing again on Linux builds due to ancient SDL2 versions (using 2.0.5 instead of 2.0.9). It may be time to disable or remove TravisCI permanently.

For now I've turned off TravisCS. Merged changes from several of the PR's that Daniel pushed. Going to wait for these tests to complete and if they look good I'll move forward with this commit.
I will leave the VS2017 project in place for now, perhaps @cugone can get the nuget packages working again with the VS2019 project -- vcpkg is a lot easier and the libraries are much more up to date but it takes a lot longer for the builds to complete (has to build each library instead of downloading prebuilt binaries).

I was under the impression there was a desire to keep using VS2017 for now and wait for appveyor to upgrade to a non-preview builds of 2019.

Is there a way to only install the vcpkgs for the appropriate version being built? Right now both builds, x86 and x64, are installing both x86 and x64 vcpkgs. Only installing the x86 version for the x86 build and vice versa will considerably cut down on build time.

Is there a way to only install the vcpkgs for the appropriate version being built? Right now both builds, x86 and x64, are installing both x86 and x64 vcpkgs. Only installing the x86 version for the x86 build and vice versa will considerably cut down on build time.

It would, but it seems to be a moot point since you got it working properly via nuget. Will merge that version and close/delete this branch.
Thanks!

I was under the impression there was a desire to keep using VS2017 for now and wait for appveyor to upgrade to a non-preview builds of 2019.

Admittedly I feel a little foolish on this one. I didn't realize AppVeyor already had a VS 2019 preview version. I only saw the VS 2017 version option. Additionally I had just recently spent 2 days downloading and setting up a VS 2017 environment, and wasn't eager to go through that again so soon. Though Leeor did kind of sell me on it by saying the upgraded files should still work with VS 2017.
So yeah, maybe I still had a bit of a desire to stick with VS 2017, but ehh. Maybe I'm being a stick in the mud. Leeor is the one developing from Windows, and it is his project.
¯\_(ツ)_/¯


dcos-297 add HTTP 1.1 basic auth

This will prompt the use once per command for username/password if the server responds that it needs HTTPBasicAuth. It also allows the username/password (or just the username) to be stored in core.dcos_url instead of typing credentials in (http://username:password@dcos_url).

also note that we'd be sending passwords over non-https.  product is aware of this?

@jsancio updated

still missing tests

Holding off on tests to see if we can get a dcos-image with auth

updated, added a few mocks

@jsancio updated

LGTM. Just some minor comments.

thanks @jsancio, updated with latest comments


Moving all "alloca" instantiations to the entry basic block.

This is followup to PR #1003.
It updates all the "CreateAlloca" calls in the XLA code to ensure that "alloca"s are created in the entry basic block. See PR #1003 description for details on why
/cc @whchung @ekuznetsov139

Can one of the admins verify this patch?

the rocm-xla flakiness strikes me once more
Only one failure
//tensorflow/compiler/xrt/tests:raw_api_test_gpu_gpu                    TIMEOUT in 3 out of 3 in 915.0s

http://ml-ci.amd.com:21096/job/develop-upstream-unit-tests/job/tensorflow-upstream-unit-tests-rocm-xla/1392/console
kicking off rocm-xla again with fingers crossed

jenkins: retest rocm-xla please


fix: spacing issue with cvitems (#532)

Closes #532
This needs testing with previous LaTeX distributions, but I can confirm that the output from MiKTeX is identical to the PDF file that was generated before the bug emerged with the distribution update.

I can confirm it renders properly on an up to date MikTeX/MacTeX, however it does result in extra spacing on older texlive versions including with Overleaf set to texlive 2024.


fix(hapi.js): support latest hapi

:tada: This PR is included in version 1.13.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[tool_crash] FileSystemException: Exists failed, OS Error: The device is not ready., errno = 21

Command
flutter doctor

Steps to Reproduce

...
...
...

Logs
FileSystemException: Exists failed, OS Error: The device is not ready.
, errno = 21
#0      _Directory.existsSync (dart:io/directory_impl.dart:94:7)
#1      ForwardingFileSystemEntity.existsSync (package:file/src/forwarding/forwarding_file_system_entity.dart:43:33)
#2      ErrorHandlingDirectory.existsSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:497:22)
#3      _runSync (package:flutter_tools/src/base/error_handling_io.dart:597:14)
#4      ErrorHandlingDirectory.existsSync (package:flutter_tools/src/base/error_handling_io.dart:496:12)
#5      PubDependencies.isUpToDate (package:flutter_tools/src/flutter_cache.dart:102:57)
<asynchronous suspension>
#6      Cache.updateAll (package:flutter_tools/src/cache.dart:677:11)
<asynchronous suspension>
#7      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1271:7)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1161:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>

[✓] Flutter (Channel stable, 2.10.1, on Microsoft Windows [Version 10.0.19044.1503], locale en-US)
    • Flutter version 2.10.1 at F:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (8 days ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\humza\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\android-canary\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.1.0)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
    • Visual Studio Professional 2022 version 17.1.32210.238
    ✗ The current Visual Studio installation is incomplete. Please reinstall Visual Studio.

[✓] Android Studio (version 2021.2)
    • Android Studio at C:\android-canary\android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[✓] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.1503]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 98.0.4758.102
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 97.0.1072.62

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter Application Metadata
No pubspec in working directory.

Closing this as a duplicate of https://github.com/flutter/flutter/issues/81146


report: Use HTML instead of IFrame inside Google Colab.

Requires https://github.com/iterative/dvc-render/pull/118
Closes #460

Requires DVC release including the bump to dvc-render

@daavoo Is there an easy way to install to test in colab?

@daavoo Is there an easy way to install to test in colab?

!pip install git+https://github.com/iterative/dvclive@colab-notebook#egg

Codecov Report
Base: 95.68% // Head: 95.69% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (2cfbab3) compared to base (41d12d7).
Patch coverage: 69.23% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #461      +/-   ##
==========================================
+ Coverage   95.68%   95.69%   +0.01%
==========================================
  Files          37       37
  Lines        2315     2322       +7
  Branches      194      196       +2
==========================================
+ Hits         2215     2222       +7
+ Misses         62       61       -1
- Partials       38       39       +1

Impacted Files
Coverage Δ

src/dvclive/utils.py
83.69% <60.00%> (+2.79%)
:arrow_up:

src/dvclive/report.py
93.47% <75.00%> (-1.98%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

LGTM!
For my knowledge, what's the benefit of using IFrame otherwise?

HTML doesn't show the plots in my local Jupyter server but IFrame does 🤷


Pub: Upgrade Flutter to the latest stable version

Just out of curiosity, is there a concrete need for this, e.g. as it allows to scan more recent Flutter projects, or is this just maintenance?

Yes, we had an unmet requirement on the dart-sdk version.

Yes, we had an unmet requirement on the dart-sdk version.

Ok, good to know. This would be valuable information for the commit message, IMO.

Ok, good to know. This would be valuable information for the commit message, IMO.

I've updated the commit message.

I've updated the commit message.

Thank you!


disable RTTI for snappy compilation

Scope & Purpose
This restores the compilation of Snappy to how it was done before commit 573f7ebfdd0f5856970b2ea93555175d5ee9743b. That commit disabled the hack in Snappy that turns of RTTI in its CMakeLists.txt.
The reason for enabling RTTI for Snappy compilation in that previous commit was that we were deriving from two Snappy source files, which are supposed to be used as interfaces. However, g++ cannot link files which have base classes compiled without RTTI and derived classes that use RTTI. That's why RTTI was enabled for the Snappy files in that commit.
That required changes to the original Snappy CMakeLists.txt, and may have had an adverse impact on performance (still to be proven by our performance tests). Now, instead of turning RTTI on for Snappy, we turn it back off and in addition we turn off RTTI for the one file that derives from Snappy's interfaces. So we have to use some source-file specific compile hack in CMakeLists.txt to turn RTTI off for one of our own files.
This is hopefully less intrusive than turning RTTI off for Snappy and having to maintain a patch for Snappy's CMakeLists.txt long-term.
This doesn't need to be backported because the commit above was only in devel/3.9.
Testing if this works is basically done by compilers on all platforms. If this has a positive impact on performance we will see soon after merging by observing the trends in our performance tests.

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[x] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] The behavior in this PR was manually tested

Merging despite unrelated test failure on Windows (cluster).


Merged master into release 1.15

/LGTM
/approve

/assign @kbarnard10

/lgtm
/approve

/milestone 1.16


fix: remove extra pritunl yaml file

atlantis plan -d terraform/atlantis

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #9. To continue, delete the lock from #9 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

atlantis plan

Ran Plan for 0 projects:

atlantis plan -d terraform/atlantis

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14974395" -> "14974769"
            # (4 unchanged attributes hidden)
        }
    }
  # helm_release.pritunl has been changed
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ version                    = "0.1.0" -> "0.0.8"
        # (26 unchanged attributes hidden)
    }

Unless you have made equivalent changes to your configuration, or ignored the
relevant attributes using ignore_changes, the following plan may include
actions to undo or respond to these changes.

─────────────────────────────────────────────────────────────────────────────

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place

Terraform will perform the following actions:

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          + <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
        # (26 unchanged attributes hidden)
    }

  # kubernetes_secret.tls will be updated in-place
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls" -> null
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/ip-sans"          = "" -> null
              - "cert-manager.io/issuer-group"     = "cert-manager.io" -> null
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer" -> null
              - "cert-manager.io/issuer-name"      = "zerossl" -> null
              - "cert-manager.io/uri-sans"         = "" -> null
            }
            name             = "wayofthesys-com-pritunl-tls"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 2 to change, 0 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 0 to add, 2 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply -d terraform/atlantis

atlantis plan

Ran Plan for 0 projects:

atlantis plan -d terraform/atlantis

atlantis plan -d terraform/atlantis

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform plan -input=false -refresh -no-color -out \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis": exit status 1
random_id.encryption-key: Refreshing state... [id=GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns]
tls_private_key.ca: Refreshing state... [id=1de4512aa1ef3fcedb1bf04b728af0ccbc04ccb0]
tls_private_key.key: Refreshing state... [id=3ddd19aec0513c0b8cd92587a9ffa5664e20e9d8]
tls_self_signed_cert.ca: Refreshing state... [id=214559868745378656370816319241297031822]
tls_cert_request.request: Refreshing state... [id=bd65263b60fe87b500efff18a405fa1f641dcdc5]
tls_locally_signed_cert.cert: Refreshing state... [id=110921370611277964470799525342932874500]
helm_release.mongodb: Refreshing state... [id=pritunl-mongodb]
kubernetes_namespace.pritunl: Refreshing state... [id=pritunl]
kubernetes_namespace.mongodb: Refreshing state... [id=mongodb]
kubernetes_secret.docker_login_secret: Refreshing state... [id=pritunl/wayofthesys-com-docker-login]
kubernetes_secret.mongodb_root_password: Refreshing state... [id=pritunl/mongodb-root-password]
kubernetes_secret.tls: Refreshing state... [id=pritunl/wayofthesys-com-pritunl-tls]

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

Error: failed to render : <template_file>:7,18-37: Unknown variable; There is no variable named "DOMAIN_NAME_VERBOSE".

  with data.template_file.pritunl,
  on data.tf line 1, in data "template_file" "pritunl":
   1: data "template_file" "pritunl" {

atlantis apply -d terraform/atlantis

Ran Apply for dir: terraform/atlantis workspace: default
Apply Error
Show Output
running "/usr/local/bin/terraform apply -input=false -no-color \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis": exit status 1
kubernetes_secret.tls: Modifying... [id=pritunl/wayofthesys-com-pritunl-tls]
helm_release.pritunl: Modifying... [id=pritunl]
kubernetes_secret.tls: Modifications complete after 0s [id=pritunl/wayofthesys-com-pritunl-tls]

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Error: cannot load values.yaml: error converting YAML to JSON: yaml: line 28: did not find expected key

  with helm_release.pritunl,
  on pritunl.tf line 9, in resource "helm_release" "pritunl":
   9: resource "helm_release" "pritunl" {

atlantis plan -d terraform/atlantis

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform plan -input=false -refresh -no-color -out \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/10/default/terraform/atlantis": exit status 1
random_id.encryption-key: Refreshing state... [id=GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns]
tls_private_key.key: Refreshing state... [id=3ddd19aec0513c0b8cd92587a9ffa5664e20e9d8]
tls_private_key.ca: Refreshing state... [id=1de4512aa1ef3fcedb1bf04b728af0ccbc04ccb0]
tls_self_signed_cert.ca: Refreshing state... [id=214559868745378656370816319241297031822]
tls_cert_request.request: Refreshing state... [id=bd65263b60fe87b500efff18a405fa1f641dcdc5]
tls_locally_signed_cert.cert: Refreshing state... [id=110921370611277964470799525342932874500]
helm_release.mongodb: Refreshing state... [id=pritunl-mongodb]
kubernetes_namespace.pritunl: Refreshing state... [id=pritunl]
kubernetes_namespace.mongodb: Refreshing state... [id=mongodb]
kubernetes_secret.mongodb_root_password: Refreshing state... [id=pritunl/mongodb-root-password]
kubernetes_secret.docker_login_secret: Refreshing state... [id=pritunl/wayofthesys-com-docker-login]
kubernetes_secret.tls: Refreshing state... [id=pritunl/wayofthesys-com-pritunl-tls]

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

Error: failed to render : <template_file>:7,18-37: Unknown variable; There is no variable named "DOMAIN_NAME_VERBOSE".

  with data.template_file.pritunl,
  on data.tf line 1, in data "template_file" "pritunl":
   1: data "template_file" "pritunl" {

atlantis plan -d terraform/atlantis

atlantis plan -d terraform/atlantis


On-screen rendering and ganesh backend support

Do you plan to add hardware acceleration support? I have some native code for win/linux/ios/android that we use in Perspex for hw-accelerated drawing using Skia. For Windows it will add dependency on ANGLE, but performance improvements are worth of adding such dependency.

Since opengl-related calls are too platform-dependent and complex for a user it's better to keep Garesh backend initialization and surface-flipping in the native lib. I also can see that currently your bindings don't have built-in on-screen rendering support and you leave the task of blitting image to screen to the user.
In Perspex we have a concept of a render target that allows to create a rendering session which, when disposed, is flipped back to screen. It may be worth to do the same.
interface IRenderTarget
{
     IRenderingContext CreateContext();
}

interface IRenderingContext : IDisposable
{
      SkCanvas Canvas { get; }
}

To end user it will look like this:
var target = new OSWindowRenderTarget(hWnd/xid/nswindow);
...

using(var ctx = target.CreateContext())
{
     ctx.Canvas.DrawRectangle(...);
}

That render target will manage everything required to initialize ganesh-backend using ANGLE/EGL/GLX/AGLX/whatever or fall back to sw rendering.
Currently I have some code for that in Perspex
https://github.com/Perspex/libperspesk/blob/master/src/gl.cpp - EGL/ANGLE hw-accel (Win/Linux/Android)
https://github.com/Perspex/libperspesk/blob/master/src/win32.cpp - win32 window (SetDIBitsToDevice)
https://github.com/Perspex/libperspesk/blob/master/src/linux.cpp - X11 (XPutImage)
https://github.com/Perspex/libperspesk/blob/master/src/pview.mm - iOS using GLKView

@kekekeks I will be looking into this soon. I have got most of the GPU bits building for all platforms right now. The next step is to get ANGLE for Windows added, then wrap all the necessary types.
As the GPU bits are building already, initial wrapper can be created for OpenGL right now, except the UWP will have to wait for ANGLE. Win32 can have initial GL support until ANGLE arrives - giving it more options for devs.

@kekekeks Hardware support is here (-ish)
I have started with getting all the bits together and I think it is working quite well. Right now All the platforms should have OpenGL support (DirectX is coming in a few). This means all the platforms, except UWP, can draw with hardware acceleration.
The global issue for hardware / GPU is here: https://github.com/mono/SkiaSharp/issues/138
Please leave comments and suggestions so we can get the best product out.
There is also a preview NuGet: https://www.nuget.org/packages/SkiaSharp/1.53.2-gpu1
Please try that out and be sure to comment on how it went - if there are any features needed, just let us know!


DBCache doesn't work with custom cache table name on MSSQL/SqlServer

What steps will reproduce the problem?
Here I used basic template https://github.com/yiisoft/yii2-app-basic
According to https://www.yiiframework.com/doc/api/2.0/yii-caching-dbcache#$cacheTable-detail:

Create cache table

create table test_cache
(
    id     char(128) not null primary key,
    expire int,
    data   varbinary(max)
)

In db.php:

return [
    'class' => Connection::class,
    'dsn' => 'sqlsrv:Server=<server>;Database=<db>',
    'username' => '<user>',
    'password' => '<pass>',
    'charset' => 'utf8',
]

In web.php:

'cache' => [
    'class' => yii\caching\DbCache::class,
    'cacheTable' => 'test_cache'
],

In SiteController, in method actionAbout:

$cache = Yii::$app->cache;

return $cache->getOrSet('testKey', function () {
    return 122;
});

What is the expected result?
On page '122' and the cache table row with key 'testKey'
What do you get instead?
Error page with:
PHP Notice – yii\base\ErrorException
Trying to get property 'columns' of non-objectPHP Notice – yii\base\ErrorException
Trying to get property 'columns' of non-object

in C:\inetpub\wwwroot\aidan\web-test2\vendor\yiisoft\yii2\caching\DbCache.php
on line 308 at:
$this->db->getTableSchema('cache')->columns['data']->dbType === 'varbinary';

I think it should be:
$this->db->getTableSchema($this->cacheTable)->columns['data']->dbType === 'varbinary';

cause it uses default cache table name
Additional info

Q
A

Yii version
<IP_ADDRESS>?

PHP version
7.3.27 nts x64

Operating system
Windows Server 2016 (14393 )

Yes, this is exactly what you said. Would you mind preparing a PR with a fix?

done #18679


Skeleton: Add functionality to get bone global_pose without the override

The changes made to the skeleton class post-skin changed logic a bit for the global_pose, which caused the expected usage of get_bone_global_pose() to be different.
It is actually more correct now than it was before, but there was an expected usage by users that is now missing.
This PR adds the ability for users to obtain a bones global pose while ignoring the override pose of the bone they are requesting.
See: https://github.com/godotengine/godot/issues/33552

Love it! Thanks for investigation :-)
Will this also probably fix the issue that multiple SkeletonIKs won't work at the same time?

Love it! Thanks for investigation :-)
Will this also probably fix the issue that multiple SkeletonIKs won't work at the same time?

I am not sure, I don't have any knowledge on this, but I guess if two IK's were trying to apply a global_pose_override it makes sense.
The code would have to be updated for IK's though.

Love it! Thanks for investigation :-)
Will this also probably fix the issue that multiple SkeletonIKs won't work at the same time?

I am not sure, I don't have any knowledge on this, but I guess if two IK's were trying to apply a global_pose_override it makes sense.
The code would have to be updated for IK's though.

But one SkeletonIK does define a root and a tip bone and usually it should only affect bones in the defined chain.

Squashed and updated for master branch

closing because this is superseded by: https://github.com/godotengine/godot/pull/41322


[PPP-4490] We should not allow anonymous access to executeJob and exe…

…cuteTrans
PurRepositoryConnector changes are the result of reverting what was done under PDI-18081 (check pentaho-kettle#6595).
@pentaho/tatooine @pentaho-lmartins @jmcdaniel-5aho

:white_check_mark: Build finished in 36m 50s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine,plugins/pur/core

:ok_hand: All tests passed!
Tests run: 3654, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

It's not possible to add the dependency to 'pentaho-platform-core': on our build, it's built AFTER 'kettle-engine'!


[Vitest 3] "Intl.Collator is not a constructor" when using fake timers

Describe the bug
I am trying to upgrade to the latest Vitest 3 Beta. Our project does not use Vite for the build-pipeline (only a simple esbuild config, in fact), and we didn't need to do anything so far to get our tests running (we don't even have a vitest config).
However, after the upgrade, we suddenly see the following error in the console:
Intl.Collator is not a constructor

TypeError: Intl.Collator is not a constructor
 ❯ src/services/xxxxx.ts:96:24
     94| };
     95|
     96| const nameComparator = new Intl.Collator('en', {
       |                        ^
     97|   sensitivity: 'base',
     98|   numeric: true,

I thought it might have to do with the Vite 6 module resolution changes, but even tinkering with that one broke more than i liked. The project runs on Node v22, and Vitest v2 has worked without an issue so far.
The error also happens when I run vitest in isolation mode.
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-ptkpew1o?file=test%2Fbasic.test.ts
Once the async import gets resolved, Vitest doesn't know what Intl. is.
System Info
System:
  OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
  CPU: (16) x64 AMD Ryzen 9 7950X 16-Core Processor
  Memory: 25.82 GB / 35.24 GB
  Container: Yes
  Shell: 3.6.1 - /usr/bin/fish
Binaries:
  Node: 22.2.0 - /mnt/wslg/runtime-dir/fnm_multishells/40485_1735384937185/bin/node
  npm: 10.7.0 - /mnt/wslg/runtime-dir/fnm_multishells/40485_1735384937185/bin/npm
  pnpm: 8.15.5 - /mnt/wslg/runtime-dir/fnm_multishells/40485_1735384937185/bin/pnpm
  bun: 1.1.8 - ~/.bun/bin/bun
npmPackages:
  vitest: 3.0.0-beta.3 => 3.0.0-beta.3

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This looks like due to fake timers. Here is a simplified repro https://stackblitz.com/edit/vitest-dev-vitest-96ajsug5?file=test%2Fbasic.test.ts
In v3, we changed the behavior of toFake to fake everything globally available https://github.com/vitest-dev/vitest/pull/6288, which also includes Intl. There is a bug which breaks some Intl.xxx in @sinonjs/fake-timers and it's been fixed on upstream by https://github.com/sinonjs/fake-timers/pull/479, but we are still using fairly old version 11.1.0 (latest is 14.0.0), which is before the fix.
There's a PR https://github.com/vitest-dev/vitest/pull/7097 but probably we haven't reviewed yet.
In the mean time, you can explicitly set toFake to be same as v2 like
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    fakeTimers: {
      toFake: [
        'setTimeout',
        'clearTimeout',
        'setInterval',
        'clearInterval',
        'setImmediate',
        'clearImmediate',
        'Date',
      ],
    },
  },
});

Thanks! that did the trick. I updated the title for this issue accordingly.

@spaceemotion feel free to try it out pre-release of the PR https://github.com/vitest-dev/vitest/pull/7097#issuecomment-2565101092 I confirmed the repro is fixed with this https://stackblitz.com/edit/vitest-dev-vitest-52wgjnc6?file=package.json


Update static pages and add external links to main menu

Update About, FAQ, Data Management General Guidance pages w/ revised markdown files.
Add links to external resources (dmp Github wiki) and an arrow icon to the Learn main menu next to these items

For Administrators https://github.com/CDLUC3/dmp/wiki/Help-for-Administrators
For Developers https://github.com/CDLUC3/dmp/wiki/Help-for-Developers

using the font-awesome version of an external link icon

font awesome icon looks awesome! and thanks for adding to the footer links also.


Fixes #1438 - Make AppDeployIntegrationTest resilient to event reordering

Integration Tests are running fine.
Added some small comments, but overall LGTM.


Support move for ExprMakeTuple

[E]  LLVM JIT FAILED:
makeTuple: move is not supported. expr = ExprMakeTuple at %publicScripts/u2e/events.das:12:38
makeTuple: move is not supported. expr = ExprMakeTuple at %publicScripts/u2e/events.das:12:38
def AddListener(var event : IntEvent; var cb : lambda<(arg : int) : void>) : int
    event.listeners |> emplace([[auto cb, ++event.id]])
    return event.id

https://github.com/borisbat/dasLLVM/commit/34bfce27010f516ef8d6668b19a04824e930d0d3


Update requirements.txt

This should fix the requirements for the repo.

fix #268 #273

This is not needed. @Sticksman. setup.py handles all the dependencies. Only the test suite is needed.


Fix ownership of Newrelic ini

Needs to be readable by all users so that when running PHP FPM as non root the New Relic module can be used.

Fixed by #10


Self referencing many to many relationship

I want to create a many to many relationship in EF Core. My entity Product has many Product as childs. I have created a Lookup table with a ProductId and a ProductParentId and a reference to the Product Entity, but ProductParentId reference is null.
How can I also reference ProductParentId to a Product?
Product Entity
    public class Product
    {
        [Key]
        public int Id { get; set; }
        public string Naam { get; set; }
        public string Omschrijving { get; set; }
        public decimal ConsumentPrijs { get; set; }
        public decimal HorecaPrijs { get; set; }
        public bool OpWebsite { get; set; }
        public decimal? StukGewicht { get; set; }
        public string FotoPad { get; set; }
        public DateTime? DeletedOn { get; set; }
        public Eenheid StandaardEenheid { get; set; }
        public virtual Btw Btw { get; set; }
        public Product ProductParent { get; set; }

        public virtual List<ProductEenheid> ProductEenheden { get; set; }
        public virtual List<ProductGroepProduct> ProductGroepen { get; set; }
        public virtual List<ProductChild> ProductChilderen { get; set; }
    }

ProductChild Look up table
   public class ProductChild
    {
        public int ProductId { get; set; }
        public int ProductParentId { get; set; }

        public virtual Product Product { get; set; }
        public virtual Product ProductParent { get; set; }
    }

OnModelCreating
       protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity<ProductChild>()
                .HasKey(u => new { u.ProductId, u.ProductParentId });

            modelBuilder.Entity<Product>()
                .HasMany(u => u.ProductChilderen)
                .WithOne(f => f.Product)
                .HasForeignKey(f => f.ProductId);

            modelBuilder.Entity<Product>()
                .HasMany(u => u.ProductChilderen)
                .WithOne(f => f.ProductParent)
                .HasForeignKey(f => f.ProductParentId);
        }

I have essentially the exact same design in my application. However, when I save a ProductProduct entity it is assigning the ParentId to both the Parent and Child Id fields. I have no idea why this is happening. I'm looking at the reference in debugger before it's saved / updated and it looks correct, but after it updates it is incorrect in the database. Any ideas?

@selected-pixel-jameson Please file a new issue including a runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

@ajcvickers is this supported in 2.0.2 ?
In the example, "WithOne(f => f.ProductParent)"  doesn't provide the expression of the ProductProduct class.  The expression is expecting "Product".
modelBuilder.Entity<Product>()
    .HasMany(u => u.ProductChilderen)
    .WithOne(f => f.ProductParent)
    .HasForeignKey(f => f.ProductParentId);

@aaronhudon Yes, this is supported in 2.0.x. If you are encountering a problem, then please file a new issue with a runnable project/solution or complete code listing that demonstrates what you are seeing.

@ajcvickers Aren't the two modelBuilder.Entity<Product>() statement missing the .OnDelete(DeleteBehavior.Restrict) ? Otherwise I get an exception from EnsureCreated() regarding that this can cause cycles or multiple cascade paths. I tried to mimic this solution to my problem and still have the issue, and not entirely sure if the Restriction of DeleteBehavior is the correct solution here.
Thank you in advance!

@baloghlaszlo Not necessarily. First, this is a SQL Server limitation; other providers can handle this. Second, disabling cascade deletes entirely is often not the best way to handle this. Instead, it can be better to edit the migration to allow EF to continue doing cascade deletes while the database does not. Third, only one relationship needs to changed to prevent the cycle, and depending on how the domain model is used, this may be the best choice.

@ajcvickers   I think I have similar issue here.  I got error : System.InvalidOperationException: Unable to determine the relationship represented by navigation property 'AssociatedReservation.ParentReservation' of type 'Reservation'.
Either manually configure the relationship, or ignore this property using the '[NotMapped]' attribute or by using 'EntityTypeBuilder.Ignore' in 'OnModelCreating'.
[AuditParentType(typeof(Reservation))]
public class AssociatedReservation : DbEntity
{
public AssociatedReservation()
{
}
    public long ParentReservationId { get; set; }
    public long ChildReservationId { get; set; }

    public int TenantId { get; set; }

    public virtual Reservation ParentReservation { get; set; }

    public virtual Reservation ChildReservation { get; set; }

    public override IEnumerable GetIds()
    {
        yield return ParentReservationId;
        yield return ChildReservationId;
        yield return TenantId;
    }

    public static ModelBuilder Configure(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<AssociatedReservation>().ToTable("AssociatedReservations", schema: DbSchemas.Billing)
          .HasKey(x => new { x.ParentReservationId, x.ChildReservationId });

        //modelBuilder.Entity<AssociatedReservation>()
        //    .HasOne(o => o.ParentReservation)
        //    .WithMany(o => o.AssociatedReservations)
        //    .HasForeignKey(o => o.ParentReservationId)
        //    .HasPrincipalKey(o => o.Id);

        //modelBuilder.Entity<AssociatedReservation>()
        //   .HasOne(o => o.ChildReservation)
        //   .WithMany(o => o.ParentReservations)
        //   .HasForeignKey(o => o.ChildReservationId)
        //   .HasPrincipalKey(o => o.Id);

        //Need to configure the child -> associated reservation -> parent relationship
        //A Child Reservation will not have many Associated Reservations.
        //A Child Reservation will have one Parent Reservation
        //modelBuilder.Entity<AssociatedReservation>()
        //    .HasOne(o => o.ChildReservation)
        //    .WithMany()
        //    .HasForeignKey(o => o.ChildReservationId)
        //    .HasPrincipalKey(o => o.Id);

        modelBuilder.Entity<Reservation>()
           .HasMany(o => o.AssociatedReservations)
           .WithOne(o => o.ParentReservation)
           .HasForeignKey(o => o.ParentReservationId)
           .HasPrincipalKey(o => o.Id);

        modelBuilder.Entity<Reservation>()
           .HasMany(o => o.ParentReservations)
           .WithOne(o => o.ChildReservation)
           .HasForeignKey(o => o.ChildReservationId)
           .HasPrincipalKey(o => o.Id);

        return modelBuilder;

Reservation.cs has
public virtual List AssociatedReservations { get; set; }
public virtual List ParentReservations { get; set; }


Accessibility: Group label of radio button groups not announced by screen readers

Windows Terminal version (or Windows build number)
Windows Terminal Preview Version: 1.7.572.0
Other Software
Narrator, NVDA, JAWS
Steps to reproduce

Turn on Narrator.
Open Settings.
Tab to the Start Mode group of radio buttons.

Expected Behavior
The screen reader would say "Start mode", "Default radio button, 1 of 5" or similar.
Actual Behavior
Screen reader says "Default radio button, 1 of 5", but not what this is actually referring to. Same with other sets of radio buttons.
The prompts for these groups of radio buttons is mere static text that is not associated to the radio buttons in any way, and the radio buttons aren't grouped in a true groupbox, at least what accessibility is concerned.

This bug is also present in the XAML Toolkit Gallery app: https://github.com/microsoft/Xaml-Controls-Gallery/issues/657

This is because the WinUI RadioButtons control is actually not accessible: https://github.com/microsoft/microsoft-ui-xaml/issues/3183


⚠ ClamAV has degraded performance

In 226738b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 244 ms

Resolved: ClamAV performance has improved in 683a1c3 after 8 minutes.


ImportAttributeFlowRule key properties not unique

Using the DSC configuration generator I found that the IAF rules generated were not unique (failed when trying to create the MOF file).  The items have unique names (a GUID) but the key properties between two DSC resources are the same.
Probably need to change the IAF DSC resource schema to make items more unique.
It really boils down to an issue with DSC schema, captured nicely in this StackOverflow issue:
DSC Package resource have identical key properties
Here is the guide for authoring DSC resources:
Writing a custom DSC resource
The reason for not just using SrcAttribute as a Key property is that IAF rules will not always have a source attribute; for example:

DNPart IAF rules just use the DN so the sync config does not refer to a SrcAttribute
Constant IAF rules just use a ConstantValue so the sync config again does not refer to a SrcAttribute

Solution options

Introduce a Fake Identifier property as Key - ugly but workable
Create DSC resources for each IAF rule sub-type (Direct, Scripted, DN, DNPart, Constant) -
lots of extra resources and duplicate code
Overload SrcAttribute such that IAF rules that do not require it use it instead of 'DNPart' or 'ConstantValue' - breaks the clean link from the DSC resource schema to the sync XML, but results in a nice looking DSC resource without the fake identifier.
Unfortunately this hack won't work because an array property cannot be a key.

Repro
Configuration TestMimSyncConfig
{
    Import-DscResource -ModuleName MimSyncDsc

    Node (hostname)
    {
       ImportAttributeFlowRule af5ca310-1d8c-4669-95c2-1f7d0482cb8f
        {
            ManagementAgentName    = 'TinyHR'
            MVObjectType           = 'Contact'
            MVAttribute            = 'DisplayName'
            CDObjectType           = 'person'
            Type                   = 'direct-mapping'
            SrcAttribute           = 'LastName'
            Ensure                 = 'Present'
        }

        ImportAttributeFlowRule e1261aaa-de1a-4af0-8373-2c6c6fb76713
        {
            ManagementAgentName    = 'TinyHR'
            MVObjectType           = 'Contact'
            MVAttribute            = 'DisplayName'
            CDObjectType           = 'person'
            Type                   = 'direct-mapping'
            SrcAttribute           = 'FirstName'
            Ensure                 = 'Present'
        }
    }
}

TestMimSyncConfig -OutputPath "$env:TEMP\TestMimSyncConfig"
Start-DscConfiguration       -Path "$env:TEMP\TestMimSyncConfig" -Force -Wait -Verbose

Error
Test-ConflictingResources : A conflict was detected between resources '[ImportAttributeFlowRule]af5ca310-1d8c-4669-95c2-1f7d0482cb8f (::7::8::ImportAttributeFlowRule)' and '[ImportAttributeFlowRule]e1261aaa-de1a-4af0-8373-2c6c6fb76713
(::18::9::ImportAttributeFlowRule)' in node 'cmartbook'. Resources have identical key properties but there are differences in the following non-key properties: 'SrcAttribute'. Values 'LastName' don't match values 'FirstName'. Please update these
property values so that they are identical in both cases.
At line:289 char:9
+         Test-ConflictingResources $keywordName $canonicalizedValue $k ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], InvalidOperationException
    + FullyQualifiedErrorId : ConflictingDuplicateResource,Test-ConflictingResources
Compilation errors occurred while processing configuration 'TestMimSyncConfig'. Please review the errors reported in error stream and modify your configuration code appropriately.
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:3917 char:5
+     throw $ErrorRecord
+     ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (TestMimSyncConfig:String) [], InvalidOperationException
    + FullyQualifiedErrorId : FailToProcessConfiguration

Went with the fake identifier solution, not the most elegant option but gets the job done.


Minor Update to java README.md

i believe batching example intended to actually batch not send every transfer as a batch of 1

Oh dear, that's a good one, thanks! These docs are generated, let me fix this at the source!

ah seems i was skimming trough it too fast )


Staticfile buildpack doesn't build

Hi,
I just tried the buildpack https://github.com/cloudfoundry/staticfile-buildpack like this:

added a .buildpacks into the projects root with the address above
added an empty Staticfile
pushed to Flynn

But I got this result? Not sure what to do here.

Counting objects: 7, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (7/7), 1.14 KiB | 0 bytes/s, done.
Total 7 (delta 2), reused 0 (delta 0)
-----> Building swaggerui...
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/cloudfoundry/staticfile-buildpack
=====> Detected Framework: staticfile 1.3.16
remote: /tmp/buildpackLEEDO/bin/compile: line 14: /tmp/buildpackLEEDO/compile-extensions/bin/check_stack_support: No such file or directory
remote: ERROR: Build failed: exec: job exited with status 1
To https://git.flynn.....com/swaggerui.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.flynn.....com/swaggerui.git'

The multi buildpack (triggered by the .buildpacks file) doesn't support git submodules (see #3611), and the lack of a required submodule triggers this issue. You can delete the .buildpacks file and see if the correct buildpack kicks in, and if it doesn't, set BUILDPACK_URL.

That did it, thank you very much. :)
https://github.com/philiplb/swagger-ui-on-flynn


Gauze recipe in medfab

About the PR
Gauze can now be crafted in medical fabricators for 2 cloth.
Why / Balance
To speed up the production of gauze in the medical department, no more cutting up clothes and crafting bandages by hand.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: After realizing their employees have been forced to make medical supplies by hand, Centcomm has added a gauze option to their medical fabricators.

using the lathe to craft them should at least be more efficient than making them by hand

...wait for someone to say something here.

It should 100% be cheaper to fabricate gauze in the medfab rather than to make it by hand, speed alone will not make this sufficient as a better measure to craft gauze.

Actually speed by itself is good. Cheaper recipe would just be a bonus.


Added measure PID_RDR

Added an implementation for the measure PID_RDR, four small test cases, a short description in the documentation and a reference to the corresponding publication.

Thank you so much for adding this measure!  The paper is on the top of my reading list (I've skimmed, but need to read for more depth).


fix eviction-hard path

feature#compute-resources
Signed-off-by: Maximilian Meister<EMAIL_ADDRESS>part of
https://github.com/kubic-project/velum/pull/514

I was initially unsure about that, but I think it's a good idea. This is an attribute that is unrelated with the actual reservations.
I'll update the Velum PR to reflect this change.

@MaximilianMeister can you backport that to the 3.0 branch please?

can you backport that to the 3.0 branch please?

@flavio https://github.com/kubic-project/salt/pull/534


Master to main

Change master to main in templates. Do the docker images need to be updated for this change to be right?

It’s been a couple of months since we went over this, but isn’t the point of CI that the multiple versions of the code being worked on by different people be periodically tested and then merged into a single common location - i.e. being pushed to the git repository that everyone shares?

On Jun 23, 2020, at 7:00 AM, Paul Wilson<EMAIL_ADDRESS>wrote:

@gonuke requested changes on this pull request.
Requesting a change that is not really related to this PR... sorry. Pinging @psbritt
In cpp_config_template.yml:

@@ -21,7 +21,7 @@ jobs:
docker:
- image: cnerg/ubuntu-18.04_pyne-3:latest #any public docker container
steps:

                   -run: git push origin master

                   -run: git push origin main

I agree with this change, but I'm not sure I think it's wise to have a pushing job in this config file. It seems either dangerous or unnecessary, or both - especially for the beginners for whom these templates are intended.
Perhaps @psbritt can remind us why it's here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

The push is typically a manual step.  CI usually just ensures that tests pass, but manual code review is necessary before merging/pushing.

In that case, I’ll remove it.

On Jun 23, 2020, at 7:50 AM, Paul Wilson<EMAIL_ADDRESS>wrote:

The push is typically a manual step. CI usually just ensures that tests pass, but manual code review is necessary before merging/pushing.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ngranda - please rebase this with PR #11

@ngranda - please rebase this with PR #11

done!

Thanks @ngranda


Can't Install - Cannot Access File

So when I try to install XiVAlexander, I get this error message. It happens no matter which type of install I try to do.  Happens even when I run the launcher as administrator first.

This error message makes no sense. Can you extract the zip into a separate directory, confirm that there are 2 exe, 2 dll, multiple json files and folders in that extracted directory and then run Loader from that extracted directory?
ffmpeg.exe shouldn't even be there. Did you indeed download the file from Github Releases page?

Ah, I had those in there from the music upgrade. Ok, I completely deleted the files in there, and downloaded fresh, and now this happened.

If I do it from a totally different folder it does work, I'm guessing its because it wants to copy itself TO that folder.

Did you extract the files into %LOCALAPPDATA%\XivAlexander\? Then this definitely is what's going to happen. What made you extract files into that folder, though? Was there anything misreading on the wiki?

Yes, I had extracted the new files in there, but not the very first time I installer. The reason is when I had tried to update it while in game, via the check for updates menu, it failed for me, and just left an updates folder, while remaining in the prior version, so I figured I would just replace the files manually. And thus this issue, which now makes sense to me, as it's trying to copy files into that same folder....I would not have expected that behavior necessarily when using the install to game menu in the launcher though, since it makes me target the game folded, I assumed it would just move a file over there.

This is expected when trying to use updater when XivAlexander is running as installed mode, and updating when game is running while installed is simply impossible. I'll make Check for Updates open Github Release page instead.

help me aaa, i downloaded several times cuz idk, maybe corrupted files or something, reinstalled ffxiv and still the same error
:(


fix(generator-web): improve base URL logic

Currently, the site searches for dotted segments in the URL, signifying a version, to determine the base URL of the class search index.
The aim is to retain the configuration-agnostic nature of this logic.
This will break in a site build with snapshot or beta/alpha versions.

Relative links should also be used wherever possible to allow for deployment with a custom root path (e.g. /mappings in https://zlataovce.github.io/mappings).


Updating link to ARO docs instead of AKS

This documentation is for ARO with Azure Front Door, it shouldn't reference AKS documentation. This change points to the documentation on how to create a private ARO cluster instead.

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

#label:"aq-pr-triaged"

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

I don't think you need the ../openshift in front of the file name on line 21 because the file being referenced is in the same directory.

Fixed this, thanks @leebeasley-v

Michael, I'm sorry, but when I commented above I meant to leave only the filename, removing the "../openshift" portion, as shown below:
create a private Azure Red Hat OpenShift cluster
This is because you are referring to an article in the same directory.
Lee

Michael,
I'm sorry I may not have been clear enough when I commented. I meant for you to leave only the filename, removing the "../openshift" portion, as shown in the portion of the link below:
… cluster](howto-create-private-cluster-4x.md).
This is because you are referring to an article in the same directory.
Once you make the change, I’ll go ahead and run this one through the publishing process.
Lee
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Michael @.>
Sent: Wednesday, April 13, 2022 5:14 PM
To: @.>
Cc: Lee Beasley (COLLABERA @.>; @.>
Subject: Re: [MicrosoftDocs/azure-docs] Updating link to ARO docs instead of AKS (PR #90747)
I don't think you need the ../openshift in front of the file name on line 21 because the file being referenced is in the same directory.
Fixed this, thanks @leebeasley-vhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fleebeasley-v&data=05|01|v-leebeasley%40microsoft.com|b28b11ccf3a348eccdb908da1d9287b0|72f988bf86f141af91ab2d7cd011db47|1|0|637854812429866800|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=V5iUCCC2QTx0DK2bgK0jtYAxOQFvCuTsgQCWDykpYP0%3D&reserved=0
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F90747%23issuecomment-1098492793&data=05|01|v-leebeasley%40microsoft.com|b28b11ccf3a348eccdb908da1d9287b0|72f988bf86f141af91ab2d7cd011db47|1|0|637854812429866800|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=N24zeePdysuUI5XMVUX8ZMy4x0RNgRiuv9XpK03R4K4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW2VOBETNWEVPE75KTVARRLVE42JRANCNFSM5SCG6T5A&data=05|01|v-leebeasley%40microsoft.com|b28b11ccf3a348eccdb908da1d9287b0|72f988bf86f141af91ab2d7cd011db47|1|0|637854812429916775|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=DvdJcWGKJr1hQjicVEUO228Sc7gXOFm5hn35Sdx56xs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

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

Thanks @leebeasley-v, should be fixed now!

#sign-off I'm the technical writer on the OpenShift product and Rahul Mehta is the PM. This change is ready for publishing. Thank you. Lee Beasley

@leebeasley-v: I'm sorry - only the author of this article, @rahulm23, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


chore: disable kafka sink txn by design

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

no longer support write messages in txn mode.
related https://github.com/risingwavelabs/risingwave/pull/7500 & https://github.com/risingwavelabs/risingwave/issues/7499
Checklist For Contributors
- [ ] I have written necessary rustdoc comments
- [ ] I have added necessary unit tests and integration tests
- [ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
- [ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)

[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[x] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[ ] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Connector (sources & sinks)

Release note
deprecate use_transaction in kafka sink. Risingwave no longer support write messages in txn mode, since even if we do that, we still cannot guarantee exactly once.

Shall we also remove this option from the documentation?

Shall we also remove this option from the documentation?

Yes, added the label


Fix validation for getting profile by name

Summary
Fixes
Message: Error getting profile status
Details: Validation failed:
- Field 'name': value does not match regex pattern `^[A-Za-z][-[:word:]]*$`
Usage:
  minder profile status list [flags]

Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.747%. remained the same
when pulling ed6a69128469ae3b78f9b7d04b91bd75953a9ed1 on fix-profile
into 01c526c6a8cf16569335c423732c05a1a54c0460 on main.


dolphinscheduler-daemon.sh does not take effect

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

start worker-server on a node
on the same node ,run "sh dolphinscheduler-daemon.sh status api-server ", get the wrong result

What you expected to happen
when run "sh dolphinscheduler-daemon.sh status api-server ", the result should be "api-server is not running"
How to reproduce

start worker-server on a node
on the same node ,run "sh dolphinscheduler-daemon.sh status api-server ", get the wrong result

Anything else
I find the "CLASS" variable in dolphinscheduler-daemon.sh  is not assigned the corrent value when running then shell script. CLASS is always null
Version
3.0.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

This has been fixed in #11580. Will be released in the 3.0.1-release.