VCRUNTIME140.APP.dll missing in UWP release build?

Building for the first time the Release of a C++/winrt UWP app I find that the .exe will not launch independently due to these errors:
VSRUNTIME140.APP.dll was not found
MSVCP140_APP.dll was not found
This is VS 2019 Preview 2.1 - the debug build works fine inside VS, but I wonder what might be done to get the Release to run outside the VS environment. The only advice I found suggested making sure that VS included the VisualC++ runtime for UWP component but it does include that.

Hi @jevansAN -- I'm sorry you're experiencing this issue. Unfortunately this issue list is specifically for documentation problems. I'd recommend that you post this in the forums or on Stack Overflow, linked on our support page: https://developer.microsoft.com/en-us/windows/support. Thank you!

HI @jevansAN -- please let us know if you have any doc-specific feedback. Thank you!


Update text on "how to cite" that is included at top of every downloaded csv file

Research that uses data from D-PLACE should cite both the original source(s) of  the data and the paper by Kirby et al. in which D-PLACE was first presented  (e.g., research using cultural data from the Binford Hunter-Gatherer dataset: "Binford (2001);  Binford and Johnson (2006); Kirby et al. 2016)." The reference list should include the date data were  accessed and URL for D-PLACE (https://d-place.org), in addition to the full references for Binford (2001),  Binford and Johnson (2006), and Kirby et al. 2016.
[changed from "Kirby et al. Submitted" to "Kirby et al. 2016." Open to other adjustments.

Think this is an issue with the website


Testing Update: Testing Guidelines

Develop a simple and easy to follow guidelines for methods and expectations when testing React components and unit testing of functions,.

Depends on #2758


Continuous synchronisation is hanging despite pending changes.

Description
During the continuous synchronisation we're observing that synchronisation of actual documents gets stucked. Even if number of pending changes grows, actual documents are not transferred. It can be hanged for couple of minutes or several (if not dozens) hours until data is synchronised for a given database.
Here is an example of such active task:
curl localinstance.url:5984/_active_tasks | jq .

[...]
{
    "node": "nonode@nohost",
    "pid": "<0.29234.1394>",
    "changes_pending": 1355,
    "checkpoint_interval": 30000,
    "checkpointed_source_seq": "3165235-g1AAAAI7eJyV0EsOgjAQBuBGlIdGN8a1HqFA0bKSmygjNIQgXeher-AJ9BLuTPQmeg1XWFrCQmMCm5nkz-TLzGQIITPRIjTMec6jOMh5wnf7TMSdEMG0KIo00QDp-ngrMoOyDaNAvuf_CDATFZY10jtJxF_gue3HTZGgRFY1Yl4lEtluTCluiqxL5FAjg4lEXOI4lHkNkbwrKjqKJpyzgvqGhDDF4DCnFXRR0F1Bo7eEgLIwxmEr6KGgZ7WRpTaCiGCgraCXgqofWTcJeeD5BH5OSz9XAqs7",
    "continuous": true,
    "database": "shards/20000000-3fffffff/_replicator.1559734367",
    "doc_id": "events_central_to_remote",
    "doc_write_failures": 0,
    "docs_read": 9319,
    "docs_written": 9319,
    "missing_revisions_found": 9319,
    "replication_id": "d37b2ffbfd3c618125e5d8a5d44a6999+continuous",
    "revisions_checked": 3011221,
    "source": "http://centralinstance.url:80/cdb/events/",
    "source_seq": "3165235-g1AAAAI7eJyV0EsOgjAQBuBGlIdGN8a1HqFA0bKSmygjNIQgXeher-AJ9BLuTPQmeg1XWFrCQmMCm5nkz-TLzGQIITPRIjTMec6jOMh5wnf7TMSdEMG0KIo00QDp-ngrMoOyDaNAvuf_CDATFZY10jtJxF_gue3HTZGgRFY1Yl4lEtluTCluiqxL5FAjg4lEXOI4lHkNkbwrKjqKJpyzgvqGhDDF4DCnFXRR0F1Bo7eEgLIwxmEr6KGgZ7WRpTaCiGCgraCXgqofWTcJeeD5BH5OSz9XAqs7",
    "started_on":<PHONE_NUMBER>,
    "target": "http://localinstance.url:5984/events/",
    "through_seq": "3165235-g1AAAAI7eJyV0EsOgjAQBuBGlIdGN8a1HqFA0bKSmygjNIQgXeher-AJ9BLuTPQmeg1XWFrCQmMCm5nkz-TLzGQIITPRIjTMec6jOMh5wnf7TMSdEMG0KIo00QDp-ngrMoOyDaNAvuf_CDATFZY10jtJxF_gue3HTZGgRFY1Yl4lEtluTCluiqxL5FAjg4lEXOI4lHkNkbwrKjqKJpyzgvqGhDDF4DCnFXRR0F1Bo7eEgLIwxmEr6KGgZ7WRpTaCiGCgraCXgqofWTcJeeD5BH5OSz9XAqs7",
    "type": "replication",
    "updated_on":<PHONE_NUMBER>,
    "user": null
  },
[...]

some active tasks returns null (but in such cases we know that there are no changes) like:
"changes_pending": null,
There are no errors or warnings in CouchDB logs.
Steps to Reproduce
Not sure if it can be reproduced as it does not occur on test or staging instances (central instance + 2-3 remote ones).
Expected Behaviour
Replicator should synchronise data when there are pending changes and should not hang.
Your Environment
We're running one central instance and 14 remote instances. Each of remote instances is running continous replication for 13 databases (which creates a 26 replicators per instance).
CouchDB is run as a Docker container based on apache/couchdb:2.3.1 image.
Here is an output of http://centralinstance:5984:
{"couchdb":"Welcome","version":"2.3.1","git_sha":"c298091a4","uuid":"dab47a850777bb5df191177447125088","features":["pluggable-storage-engines","scheduler"],"vendor":{"name":"The Apache Software Foundation"}}
Remote instances uses satellite connection to access internet - sometimes it can be slow and sometimes instances are offline. However case described above is for situations when internet is available and there are plenty of server resources (RAM, cpu, IO, net etc.).
We're using this configuration file (on every instance):
[httpd]
server_options = [{buffer, 16384}]

[replicator]
retries_per_request = 20
worker_processes = 10
worker_batch_size = 200

CouchDB Version used: 2.3.1
Operating System and version: RHEL 7

Additional context
We have no attachments in our databases, only JSON documents.

Thank you for your report.
Do you see any errors in the log related to broken connections, timeouts, retries, or failing replication jobs?
A few other notes:
retries_per_request = 20 could be lowered probably. The retries have a doubling exponential backoff starting at 0.25 sec and a max wait time of 5 minutes. The default value of 5 would be '0.25 * 2^5 = 8sec.6would be16` sec, etc. This was probably more useful before the replicator had a scheduler, but it with a scheduler it might be better to lower retries for individual requests, let the job crash and retry later again as whole.
Another setting that could probably be adjusted is replicator's checkpoint_interval. By default it is 30000 (msec), that is 30 sec, but if you do notice that your replications job are crashing because of network connection failures, then maybe lower that to 5 or 10 seconds.
Also noticed you set [httpd] server_options buffer size. I wonder if you do it because of this issue: https://github.com/mochi/mochiweb/commit/f86693f06e05f2f6cf17433134a6891bd6634a53 and also if you really want to set on [httpd] ... instead of [chttpd] .... [httpd] ... section mostly (but not always) affects just the backdoor / local listening (port 5986). The regular db server_options setting would be under the [chttpd] section.


Party Requirement Items being Consumed Instantly

Adding items to my inventory like hardwood or tools are consumed almost instantly and not at the rate that the party wages area shows. I cannot complete quests for tools or bring tools for projects to my castle because a stack of 50 tools will be consumed all at once. Another example, I bought around 1200 hardwood and in just 2 in game days all but 102 were consumed when the daily rate is only 2.5.
Also tried lowering the consumption rate in MCM to 1% and removed everyone from my party and still all tools disappeared from my inventory.
If there is a fix for this I'd be glad to know. Thank you.

Seeing the same issue. Stacks of supplies (hardwood, alcohol, textiles, etc.) all consumed in 1 day outside settlement. Haven't carried anything more than 100 or so of any supplies to see how much is being consumed.
My mod list, incase we can find a pattern:
Harmony v.<IP_ADDRESS>
ButterLib v<IP_ADDRESS>
UIExtenderEx v<IP_ADDRESS>
MCM v<IP_ADDRESS>
Bannerlord <IP_ADDRESS>56
Birth and Death Options
BannerKings v<IP_ADDRESS>
Improved Garrisons v<IP_ADDRESS>
Historical Banner Icons v1.0
Immersive Battlefield v<IP_ADDRESS>
Open Source Armory v1.15
POC v1.1.5
BannerColorPersistence w/ Bannerpaste v1.4.5
Magic Holsters v1.2
No Big Smiles v1.0
Improved Horse Caparisons e1.5.2


Reading from binary not does report correctly

It does look at all records, but because it only reports on every fifth one, it does appear to have completed. Simple update the screen after leaving the reading loop.

Done


AndroidManifest and oppwa 4.12.0

Hello,
I have the oppwa version and trying to use the plugin but I get this error:

Attribute activity#com.oppwa.mobile.connect.checkout.dialog.CheckoutActivity@windowSoftInputMode value=(adjustResize) from [oppwa.mobile-4.12.0-release.aar] AndroidManifest.xml:27:13-55
	is also present at [:hyperpay_plugin] AndroidManifest.xml:37:13-52 value=(adjustPan).
	Suggestion: add 'tools:replace="android:windowSoftInputMode"' to <activity> element at AndroidManifest.xml:23:9-27:58 to override.

my manifest is the same as the example.

Hello bro
We still using this version 4.9 .0
implementation(name: "oppwa.mobile-4.9.0-release", ext: 'aar')
Next release we will upgrade sdk version to 4.12.0
Now try using this version 4.9

@aalhadhoud
Hi bro
I hope you are doing well
We released last version 2.0.0 with upgrade hyperpay sdk version 4.12.0


Support temporal types in Kafka JSON encoder

Update decoder to use parameterized timestamp semantics
Support temporal types in Kafka JSON encoder

still working on incorporating changes to TIME WITH TIME ZONE and the removal of precision <= 3

The record decoder was returning the value for TIME WITH TIME ZONE types in the UTC time zone, so I added code to account for the offset. This is ready for another round of review

@charlesjmorgan please let us know when this one is ready. Also please rebase, there is conflict in TestKafkaIntegrationSmokeTest

@losipiuk This PR should be ready to merge, unless you or anyone else wants to take another look

Merged, thanks @charlesjmorgan !


Now able to download refrence data at Google storage

Dear Team,
I am not able to download datasets from google storage space.
This is one of the example where tried to download data but it didnt work.
/gpfs/projects/bioinfo/najeeb/tools/google-cloud-sdk/bin/gsutil cp gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/ .
While I can see data are available at this location.
/gpfs/projects/bioinfo/najeeb/tools/google-cloud-sdk/bin/gsutil ls gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/_SUCCESS
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/metadata.json.gz
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/cols/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/entries/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/globals/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/references/
gs://seqr-reference-data/GRCh37/TopMed/bravo-dbsnp-all.removed_chr_prefix.liftunder_GRCh37.mt/rows/
Could you please help with this?
Thanks
Najeeb

Hi Najeeb,
What error are you seeing when attempting to copy the files?
The gsutil cp command above won't work unless you add the -r option because the *.mt paths are directories.
Also, although you're free to download them, you shouldn't need to download these files to run the seqr annotation pipeline locally or on dataproc. The cloud storage connector for spark allows the pipeline to access this data directly from gs://seqr-reference-data/ while the pipeline is running.

Dear BW,
I have used this command as well.
/gpfs/projects/bioinfo/najeeb/tools/google-cloud-sdk/bin/gsutil cp -r gs://seqr-reference-data/GRCh37/eigen/EIGEN_coding_noncoding.grch37.ht/ .
But I am not able to copy the file. My command is not giving any error as it's just quitting silently.  Although I am able to copy CADD finally using the same type of command but not other files.
Thanks,
Najeeb

Hi @snashraf,
Try running gsutil cp without a trailing slash on the source URL.
gsutil cp -r gs://seqr-reference-data/GRCh37/eigen/EIGEN_coding_noncoding.grch37.ht .

instead of
gsutil cp -r gs://seqr-reference-data/GRCh37/eigen/EIGEN_coding_noncoding.grch37.ht/ .

Thanks !!
Removing trailing slash works for me.
Regards,
Najeeb
On Sat, Jul 6, 2019 at 1:22 AM Nick Watts<EMAIL_ADDRESS>wrote:

Hi @snashraf https://github.com/snashraf,
Try running gsutil cp without a trailing slash on the source URL.
gsutil cp -r gs://seqr-reference-data/GRCh37/eigen/EIGEN_coding_noncoding.grch37.ht .
instead of
gsutil cp -r gs://seqr-reference-data/GRCh37/eigen/EIGEN_coding_noncoding.grch37.ht/ .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/macarthur-lab/hail-elasticsearch-pipelines/issues/146?email_source=notifications&email_token=ABBFINZ2AGDX763JQOPLM33P57CSFA5CNFSM4H54BHXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKMQBA#issuecomment-508872708,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBFINZCTFJVM5UWTDLWYDTP57CSFANCNFSM4H54BHXA
.

--
Syed Najeeb Ashraf

Can you please point me to some script at seqr where you have used Hail for annotation from various data sources like Gnomad, 1KG, Cadd, Clinvar, etc, etc? I have already downloaded data from seqr.
Thanks
Najeeb


DevTest Labs browser connect and VNet peering doesn't work (anymore?)

Tried to activate Browser access in a VNet peered to a Hub with a Bastion Host.
Browser connect doesn't change to 'yes' as it would do if you have a Bastion host in the same VNet as DTL.
According to this side (and my experience some monthes ago) this should work.
Accessing DTL VMs from Hub and and ouside via RDP does work.
No firewalling, no NSG etc.
Anything else which I might miss?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e03fe8f3-cb91-cb10-8e72-5e6c6270f644
Version Independent ID: c11d8e02-48e2-9250-fa59-3f00114c765c
Content: VNet peering and Azure Bastion architecture
Content Source: articles/bastion/vnet-peering.md
Service: bastion
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@MaxiPalle -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

@MaxiPalle, looks like you have raised a support with Azure on this and working with backend team. Meanwhile, I have assigned the respective content author here for more insights.

I am running into the same issue. A hub (with bastion) and spoke (with DTL) does not work. If I put the bastion in the same vnet with DTL, it works.

#reassign: @AbdullahBell

Have the same issue. Setup vnet peering and Azure Bastion. Shareable link works. But the "Browser Connect" button is not shown on the DevTest lab vm.

Any updates?

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close

Any update on this issue/limitation from Microsoft?


Add isArrayOfTrytes method in ValidatorUtil class

As title, add the isArrayOfTrytes method to validate the array of trytes.
It's also related to issue #64.

@Techworker, please review this PR. Thanks.

Hi @Techworker, thank you for your reply.
I refer this line and I found that this should check the trytes is 2673.
Is this unnecessary? Thanks.

I think its unnecessary

Hi @Techworker, thank you for your reply. Do you mean I remove this 2673, and using the default value?
It makes sense I think. I will try that.


Updated ~Hindi

Added another translation for Hindi
Adding a language

[✓] The code displays "Hello World"
[ ] I have updated the readme to include the new language
[ ] I have incremented the language count in the readme

Only one form of "Hello World" should be used. Which one is the "best"?

Only one form of "Hello World" should be used. Which one is the "best"?

The reason I added the 2nd translation is because the 1st one is a literal conversion of the expression 'Hello World'. The one I added is the converted form of it (Hello translates to 'namaste' and World is called 'duniya' in Hindi)


Build of demos fails

Step 20/22 : RUN /bin/bash -c "source $MINICONDA/bin/activate ogre; ./build_sdl.sh"
 ---> Running in a89997dd18b1
No Anaconda environment is active.
The command '/bin/sh -c /bin/bash -c "source $MINICONDA/bin/activate ogre; ./build_sdl.sh"' returned a non-zero code: 1

This particular problem is now fixed. However, the demos will still not compile because pkg-config cannot find the Ogre specific options anymore. Even if it did find them, Ogre would still not compile because the API has changed since I wrote the examples. I will not fix this because I do not use Ogre anymore - sorry.


PowerToys "Run" still hijacks the standard Windows shortcut "Alt+Space"

Microsoft PowerToys version
0.37.2
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

Install PowerToys.
Attempt to use the standard, well-documented, Windows shortcut: Alt+Space in an "active window". Where "active window" means: any currently running (standard) Windows application with a GUI.
Powertoys hijacks Alt+Space and displays its "Run" feature (if activated, which is the default).
The standard Windows feature to "Open the shortcut menu for the active window." fails to function.

✔ Expected Behavior
Alt+Space should not launch Powertoys Run.
Alt+Space should continue to function as it always has, as documented by Microsoft, and experienced (and needed) by many users of Windows going back to version 3.x (or possibly earlier):

Alt+Space = "Open the shortcut menu for the active window."

Screenshot shows the feature functioning properly in Notepad.
The same menu will appear in any standard Windows application with a GUI.

❌ Actual Behavior
PowerToys hijacks the standard, documented, Windows shortcut Alt+Space and uses it to launch the Powertoys "Run" feature instead.
Recommendation:
Select another OS-level shortcut key combination that does not conflict with (all) other applications.
Optionally allow users to select Alt+Space if they wish, but I would also recommend against allowing this or other standard
shortcuts (without first warning the user making the settings choice).
See additional comments here:
https://github.com/microsoft/PowerToys/issues/12601#issuecomment-902926221
In short:

breaking standard Windows feature is not a good idea
hijacking this shortcut can cause confusion
it interferes with anyone that uses or requires the "shortcut menu for the active window", and specifically people that must primarily work with Windows using the keyboard

Other Software
Affects all applications with a standard GUI running on Windows 3.1, 95, 98, NT, 2000, Vista, XP, 8.0, 8.1, 10, 11 as well as many dialogs or windows displayed by the operating system itself.
Documentation for this this shortcut is listed here and I include a screenshot as well.
https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec

Hi, this is the expected behavior of PowerToys run. If you wish to use the Alt+SpcarBar as "Open the shortcut menu for the active window", please reset the shortcut here:

To customize your shortcut. Thanks!

Also, It seems like you are using an outdated version of PowerToys. Please update to the latest release to get new features and patches!

@DerekRead Honestly, almost every key combination is used as a shortcut. We have to pick one shortcut for the PowerToys run. Please just set your own shortcut if you need to use Alt+Space for "Open the shortcut menu for the active window". Please just set a shortcut yourself.

I filed this issue to help your team though, not me. I wouldn't have bothered if that wasn't the case
Perhaps PowerToys will never become a core part of Windows (I have no idea what the plans are), or if some portion of these tools will be, but if it does this issue will come up again. It might be worth thinking about this long term.
If this really is of no concern to your team then I'm happy with that. Just trying to help out.

@DerekRead Thanks for your advice and we really appreciate it. I could understand your concerns and think about future integration with Windows may cause shortcut conflict.
I would say there is no plan for PowerToys to merge into the core part of Windows, but it'll keep working like how a third-party system utility.
Thanks again for your suggestion and if there is a plan for PowerToys to merge to the core part in Windows, we'll definitely add this to our concerns. Thank you and be safe!

I always suggest to use Win+Q for PT Run, because it's identical to Win+S and when PowerToys is active, it opens "PT Run", and when it's not active, it defaults to standard Windows Search. 😃

Hi @DerekRead / @BillR5GitHub
We understand your pain but with OOBE, we really do try and make this clearer what the default is as well the fact you can change it.  PowerToys is by nature an incubation for ideas and it becomes very hard to have "natural" key shortcuts that don't clash.
Background on why alt-space was the default. We wanted something easy and powerful to quickly trigger. We had a very diverse dev team create it and had tested a few permutations. When in development, we had Win+Space was the actual default but it was quickly pointed out when we had Win+Space we broke international keyboard swapping however. Shifting to alt-space, we got zero comments and didn't seem to conflict with anything. I believe Scott Hanselman, months later, to point alt-space to us and how he uses it.  Ctrl-Space is a power keystroke in apps like Visual Studio.
This is a shockingly hard problem to solve for default key interactions, more so for something you want quickly interacted with. Different languages have may not have all the same keys, and keys move depending on language. Is the keystroke accessible for someone with a single hand?  For something like this, space bar and modifier keys stay constant.
Improving OOBE/SCOOBE to make it clearer what the default key hooks are so you clearly know what triggers something i think is bigger bang for the buck. Anything we shift to that is easy to execute will upset a set of users.

@crutkas I always recommend Win+Q because of the similar/dual function for standard Windows Search. What do you think about changing our default hotkey to this? Users always will have Win+S as alternative.

Thinking in terms of motion for your hand, win+q is hard to hit as a power keystroke. Big motion to have to move back to typing.

Assuming the default shortcut won't be altered (sounds like that battle is lost, though I really think that's a mistake)...
I think your main concern should be mitigating confusion about Alt+Space doing something unexpected as people are unable to immediately make the connection to PowerToys. If you search a little bit you will see various posts (Reddit, etc) where people can't put 2+2 together and figure out it is PowerToys that is using the shortcut.
Part of the issue is that the dialog that pops up for PowerToys Run doesn't identify itself. I doesn't have a titlebar or icon or anything else. People that see "start typing..." can easily assume it is just part of the OS because it appears to perform the same function as Windows Search (Win+S). If someone installs PowerToys to use a feature other than Run, (FancyZones seems to be very popular) they are unlikely to make the connection.
Not only do they need to make the connection that the feature is part of PowerToys, they also need to figure out that it is "PowerToys Run", then make the assumption that they can alter the behaviour in settings.
A few people I've talked to assumed it came as part of a Windows update (even though they personally installed PowerToys) and they went down the wrong path looking for information on why "Windows Search" is now popping up with Alt+Space.
I haven't found a real need for Run yet myself, so I simply disable it completely. This isn't about me. It's about reducing user confusion (or reducing support calls -- if this was a product with support).

This needs to be reopened. I just wasted quite some time to find out that a MS program breaks one of the (important) standard shortcut! Use ctrl-win-alt-r or something else, but not a standard windows shortcut, which -- as Derek pointed out already -- is well documented!

Assuming the default shortcut won't be altered (sounds like that battle is lost, though I really think that's a mistake)...
…
I think your main concern should be mitigating confusion about Alt+Space doing something unexpected
…
This isn't about me. It's about reducing user confusion

I logged in to thank @DerekRead for caring, and @Jay-o-Way for the tip about Win+Q. Thank you! 👍


mb 4409 donald update cac

Description
New CAC obtained. PR will update the sha256_digest and subject column values for cac access with new card.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make run_prod_migrations

Code Review Verification Steps

Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 58f07f61bc31138dc8082d566614f62b14c7b7c2

Tested on experimental. Was able to successfully fetch mtos via prime api client.


Revert comparison change in intellisense

There was a recent change that updated the comparison for Intellisense suggestions. While the change looks good, it broke a test in Power Apps, so we're reverting it to unblock the integration, and later we can decide whether to reapply this change and update the test.

Will keep the change


I want a primitive string validation

As an AaC user, I want a primitive validation for string, so that I can guarantee that string values are actually strings.
There is a question of how do we validate strings; the goal for this validator is to ensure that fields of type 'string' are represented as strings in the python environment. This will help us to avoid issues where plugin developers are expecting to be able to perform python string operations on a field that is designated as a string with the confidence that the value won't be a non-string object.
References:
Example integer primitive validator: https://github.com/jondavid-black/AaC/blob/ebe8651472afa136a37994cdf728c2af53e9c34a/python/src/aac/plugins/first_party/primitive_type_check/validators/int_validator.py#L1-L49
AC:

[ ] There is a new primitive type validation for strings
[ ] The string primitive validation ensures that string are instances of python string objects.
[ ] If a user puts a non-valid value in a string field, their validation fails with an appropriate error message.

[ ] The message must include a note about surrounding the offending value with quotations to turn it into a string value.

For simplicity, I'll work this in PR #542.


Add New FeatureGate UnauthenticatedHTTP2DOSMitigation

fixes: https://github.com/kubernetes/website/issues/44122
see https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/features/kube_features.go#L182-L198

I will sync with @enj to see if this message is correct.
see https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/features/kube_features.go#L182-L198

Hi @pegasas, Please sign EasyCLA, it will allow reviewers to review, approve and add LGTM label to your PR.

/easycla

Hi @pegasas, Please sign EasyCLA, it will allow reviewers to review, approve and add LGTM label to your PR.

Thanks @utkarsh-singh1 .
I have done easycla.
thank you for your quick review!


Update intro-windows-in-kubernetes.md - minor grammatical correction

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Please delete this note before submitting the pull request.
For 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For Chinese localization, base branch to release-1.12
For Korean Localization: set Base Branch to dev-1.13-ko.
Help editing and submitting pull requests:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
Help choosing which branch to use:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/assign

@BusiPlay Thank you for your contribution. Please sign the CLA so we can accept your PR for review.

/check-cla

@BusiPlay Thanks for your PR. Please sign the CLA https://github.com/kubernetes/community/blob/master/CLA.md

/approve

I have signed CLA
On Mon, May 6, 2019 at 8:22 AM Kubernetes Prow Robot <
<EMAIL_ADDRESS>wrote:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: michmike
https://github.com/kubernetes/website/pull/13750#issuecomment-489601119
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: bradtopol
If they are not already assigned, you can assign the PR to them by writing /assign
@bradtopol in a comment when ready.
The full list of commands accepted by this bot can be found here
https://go.k8s.io/bot-commands?repo=kubernetes%2Fwebsite.
The pull request process is described here
https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process
Needs approval from an approver in each of these files:

content/en/OWNERS
https://github.com/kubernetes/website/blob/master/content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/13750#issuecomment-489601184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6TCVQZR4TPNUXVC5U3T6LPUAPJNANCNFSM4HFAYTGQ
.

checked : https://deploy-preview-13750--kubernetes-io-master-staging.netlify.com/docs/setup/windows/intro-windows-in-kubernetes/
/lgtm
/approve


rocmPackages.half: 6.0.2 -> 6.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.half is: C++ library for half precision floating point arithmetics
meta.homepage for rocmPackages.half is: https://github.com/ROCm/half
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.1.0 in filename of file in /nix/store/hm7khi82py69ba6gzq54iyq571fck7jc-half-6.1.0

Rebuild report (if merged into master) (click to expand)

23 total rebuild path(s)

23 package rebuild(s)

First fifty rebuilds by attrpath
rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.miopen-hip
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
rocmPackages_6.half
rocmPackages_6.migraphx
rocmPackages_6.miopen
rocmPackages_6.miopen-hip
rocmPackages_6.mivisionx
rocmPackages_6.mivisionx-cpu
rocmPackages_6.mivisionx-hip
rocmPackages_6.rpp
rocmPackages_6.rpp-cpu
rocmPackages_6.rpp-hip
rocmPackages_6.rpp-opencl
zluda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hm7khi82py69ba6gzq54iyq571fck7jc-half-6.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.half https://github.com/r-ryantm/nixpkgs/archive/46f8bc195726766d601fa923add5a6e70dd702f7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/46f8bc195726766d601fa923add5a6e70dd702f7#rocmPackages.half

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hm7khi82py69ba6gzq54iyq571fck7jc-half-6.1.0
ls -la /nix/store/hm7khi82py69ba6gzq54iyq571fck7jc-half-6.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

11 packages marked as broken and skipped:

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
zluda

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.half is: C++ library for half precision floating point arithmetics
meta.homepage for rocmPackages.half is: https://github.com/ROCm/half
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.2.0 in filename of file in /nix/store/wsk93fkn5bfqvfvs3j75jyaqrcpb6cmy-half-6.2.0

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.miopen-hip
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
rocmPackages_6.half
rocmPackages_6.migraphx
rocmPackages_6.miopen
rocmPackages_6.miopen-hip
rocmPackages_6.mivisionx
rocmPackages_6.mivisionx-cpu
rocmPackages_6.mivisionx-hip
rocmPackages_6.rpp
rocmPackages_6.rpp-cpu
rocmPackages_6.rpp-hip
rocmPackages_6.rpp-opencl
zluda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wsk93fkn5bfqvfvs3j75jyaqrcpb6cmy-half-6.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.half https://github.com/r-ryantm/nixpkgs/archive/15b4a93edb5af0c7651e14df64c6bedac3a265a3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/15b4a93edb5af0c7651e14df64c6bedac3a265a3#rocmPackages.half

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wsk93fkn5bfqvfvs3j75jyaqrcpb6cmy-half-6.2.0
ls -la /nix/store/wsk93fkn5bfqvfvs3j75jyaqrcpb6cmy-half-6.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

11 packages marked as broken and skipped:

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
zluda

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.half is: C++ library for half precision floating point arithmetics
meta.homepage for rocmPackages.half is: https://github.com/ROCm/half
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.2.1 in filename of file in /nix/store/vgxsd9mbrr18chh0jxkcxxzai3zx4sqz-half-6.2.1

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.miopen-hip
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
rocmPackages_6.half
rocmPackages_6.migraphx
rocmPackages_6.miopen
rocmPackages_6.miopen-hip
rocmPackages_6.mivisionx
rocmPackages_6.mivisionx-cpu
rocmPackages_6.mivisionx-hip
rocmPackages_6.rpp
rocmPackages_6.rpp-cpu
rocmPackages_6.rpp-hip
rocmPackages_6.rpp-opencl
zluda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vgxsd9mbrr18chh0jxkcxxzai3zx4sqz-half-6.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.half https://github.com/r-ryantm/nixpkgs/archive/e9a332d723d4075a0eb25db39aede4364ac2af10.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e9a332d723d4075a0eb25db39aede4364ac2af10#rocmPackages.half

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vgxsd9mbrr18chh0jxkcxxzai3zx4sqz-half-6.2.1
ls -la /nix/store/vgxsd9mbrr18chh0jxkcxxzai3zx4sqz-half-6.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

11 packages marked as broken and skipped:

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
zluda

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.half is: C++ library for half precision floating point arithmetics
meta.homepage for rocmPackages.half is: https://github.com/ROCm/half
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.2.2 in filename of file in /nix/store/pgwhq8vghkqdjqja22savarvrsydakg1-half-6.2.2

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.miopen-hip
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
rocmPackages_6.half
rocmPackages_6.migraphx
rocmPackages_6.miopen
rocmPackages_6.miopen-hip
rocmPackages_6.mivisionx
rocmPackages_6.mivisionx-cpu
rocmPackages_6.mivisionx-hip
rocmPackages_6.rpp
rocmPackages_6.rpp-cpu
rocmPackages_6.rpp-hip
rocmPackages_6.rpp-opencl
zluda

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pgwhq8vghkqdjqja22savarvrsydakg1-half-6.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.half https://github.com/r-ryantm/nixpkgs/archive/a6c334b403d6dd4a96d6e82f67334f4785391999.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a6c334b403d6dd4a96d6e82f67334f4785391999#rocmPackages.half

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pgwhq8vghkqdjqja22savarvrsydakg1-half-6.2.2
ls -la /nix/store/pgwhq8vghkqdjqja22savarvrsydakg1-half-6.2.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

11 packages marked as broken and skipped:

rocmPackages.half
rocmPackages.migraphx
rocmPackages.miopen
rocmPackages.mivisionx
rocmPackages.mivisionx-cpu
rocmPackages.mivisionx-hip
rocmPackages.rpp
rocmPackages.rpp-cpu
rocmPackages.rpp-hip
rocmPackages.rpp-opencl
zluda

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Modernize Docker workflow

🗣 Description
This PR updates the workflows to use more recent methods:

It uses the suite of Docker GitHub Actions (from CrazyMax).
It builds Docker images for more than one platform.
It handles making builds for branches, and tags them correctly.
It detects a release by the name of the git tag.
Nightly builds.

💭 Motivation and Context
I've been building this workflow based on some of the best-practices of the docker actions repos.
See here: https://github.com/docker/build-push-action#complete-workflow
Basically: If you change something in the repo, an image is going to pop out.  This is a good thing.  It makes testing branches a piece of cake.

🧪 Testing

Tested for a few months in my personal project.
CI.
Note: I plan on squash merging this PR since there were a few fix commits to tease out problems in the workflow.
📷 Screenshots (if appropriate)
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

WRT commits 905799f, 3e7033b, and c506a21...I think GitHub gives you the option to combine multiple suggestions into a single commit.  I haven't had a chance to confirm that yet, but this would have been an excellent place to use that feature (assuming it exists).
Also, we should strive to use a better commit comment than the default offered by GitHub.  "Update .github/workflows/build.yml" is not very informative.
Not criticizing, just pointing out how we can better use our tools.

:notes: Workin' on my night builds :notes:

WRT commits 905799f, 3e7033b, and c506a21...I think GitHub gives you the option to combine multiple suggestions into a single commit. I haven't had a chance to confirm that yet, but this would have been an excellent place to use that feature (assuming it exists).
Also, we should strive to use a better commit comment than the default offered by GitHub. "Update .github/workflows/build.yml" is not very informative.
Not criticizing, just pointing out how we can better use our tools.

I saw the "add to batch" button after I got through a couple of the suggestions.  I agree, those defaults suxors.
Also see my comment in the description that I plan on squash-merging this PR since the commits are too exploratory (for my liking) due to the need to debug the workflow github-side.   I put that in there as I am open to preserving the individual commits if the team things there is value there.

WRT commits 905799f, 3e7033b, and c506a21...I think GitHub gives you the option to combine multiple suggestions into a single commit. I haven't had a chance to confirm that yet, but this would have been an excellent place to use that feature (assuming it exists).
Also, we should strive to use a better commit comment than the default offered by GitHub. "Update .github/workflows/build.yml" is not very informative.
Not criticizing, just pointing out how we can better use our tools.

I saw the "add to batch" button after I got through a couple of the suggestions. I agree, those defaults suxors.
Also see my comment in the description that I plan on squash-merging this PR since the commits are too exploratory (for my liking) due to the need to debug the workflow github-side. I put that in there as I am open to preserving the individual commits if the team things there is value there.

Maybe do a rebase and mark the fluff as fixup to roll those into useful commits? That way we can avoid squashing the whole thing down, but also trim the fat so to speak.

Maybe do a rebase, mark the fluff as fixup, and force push to keep useful commits? That way we can avoid squashing the whole thing down, but also trim the fat so to speak.

100% agree with @mcdonnnj here.

In addition to that, and given that this is a skeleton repo that external folks may want to study before using, I think it might make sense to add more comments in .github/workflows/build.yml. The intent is less to detail what is being done by the code and more to guide the eye and help break up the giant workflow into digestible chunks (or "functions") that each perform a particular function. That file is a little overwhelming at first glance, and it's difficult to find one's place again if one looks away at an email and comes back to it.

This is a good suggestion.  I'll add some detailed documentation about what is going on.   Mainly for future-me.  Because I'm sure this will run for six months then fail, and I'll come back all Gandalf-in-Moria when it breaks.

Maybe do a rebase, mark the fluff as fixup, and force push to keep useful commits? That way we can avoid squashing the whole thing down, but also trim the fat so to speak.

You like it when GitHub goes down?!   Cause this is how GitHub goes down.   😉
I'll attempt this!  Keep an eye on: https://www.githubstatus.com/

You like it when GitHub goes down?! Cause this is how GitHub goes down.
I'll attempt this! Keep an eye on: https://www.githubstatus.com/

I do this sort of thang tous les temps.  C'est une chose quotidienne pour moi.  You and GitHub will be OK! :fr:

Interactive rebase == Great Success!!

Jesus H. Christ we're still here!
https://www.youtube.com/watch?v=ir5bTic17k4


Support non-Basic-Multilingual-Plane (BMP) characters

Description
A new pull request after changing the code per the comments in #331.
Replaced charCodeAt() to codePointAt()  in encoding.js and modified font.js to handle surrogate pairs, for supporting non-Basic-Multilingual-Plane characters (i.e. U+10000 to U+10FFFF).
Motivation and Context

It addresses #168 and #327, and the issue mentioned by @schuylr in #297.
How Has This Been Tested?

npm run test
npm run dist and npm run start to check the usages of opentype.js via http://localhost:8080
Run the rendering test from https://github.com/unicode-org/text-rendering-tests. After the fix, it passed CFF-1 and CFF-2 test cases. Results in GVAR-4, GVAR-5 and GVAR-6
Tested in Internet Explorer 11 for the polyfill of String.prototype.codePointAt

are still incorrect, but the icon is shown instead of 2 dots. See the screenshots below.
Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I did npm run test and all tests passed green (including code styling checks).
[ ] I have added tests to cover my changes.
[ ] My change requires a change to the documentation.
[ ] I have updated the README accordingly.
[x] I have read the CONTRIBUTING document.

In stringToGlyphs, there is a trick to iterate simply over characters without checking surrogate pairs :
const chars = [...s];
const indexes = [];
for (let i = 0; i < chars.length; i += 1) {
        const c = s[i];
        indexes.push(this.charToGlyphIndex(c));
}

Thank you @fpirsch. I have tried to change the code as above but it seems to be broken after rollup, as rollup-plugin-buble converted the code as follow:
var this$1 = this;

var chars = [].concat( s );
var indexes = [];
for (var i = 0; i < chars.length; i += 1) {
    var c = chars[i];
    indexes.push(this$1.charToGlyphIndex(c));
}

s becomes the only element in the chars array and therefore chars.length always equal to 1...

Thanks @antonytse for trying :-)
I should have thought about bublé. If new syntax doesn't transpile, we can use the new method with good old syntax Array.from and "ponyfill" it (just discovered the word).
// Array.from implementation for strings thanks to Mathias Bynens ( https://github.com/mathiasbynens/Array.from )
var arrayFromString = Array.from || (s => s.match(/[\uD800-\uDBFF][\uDC00-\uDFFF]?|[^\uD800-\uDFFF]|./g) || []);

arrayFromString('a💩b');       // ['a','💩','b']

Thanks. I have added a commit for this. 😃

The arrayFromString will be created over and over again if it is declared inside the stringToGlyphsmethod. It should be placed in the top-level scope, after the imports.
Sorry @antonytse, it should be perfect after that :-)


VS Code Buffering Issue when Printing Outputs in Jupyter Notebooks

Does this issue occur when all extensions are disabled?: Not sure (need extensions to use Jupyter)

VS Code Version: 1.78.2
OS Version: Windows 11 Enterprise 22H2
Using Jupyter Notebooks in VS Code
Launching VS Code from WSL2 Ubuntu 18.04 terminal
Connecting Jupyter Notebook with conda environment (although issue seems to repro without conda)
Jupyter extension v2023.4.10112418018

Steps to Reproduce:

Open VS code from WSL2 with code . (where conda environments are already initialized)
Create a new Jupyter Notebook in VS Code
Connect the Jupyter Notebook to a conda environment as the python kernel (select Kernel >> Python Environments >> conda environment)
Populate the first python cell of the jupyter notebook with the following code:# Prompt the user 10 times (0-9 times) and ask them to enter the answer number
# this will then print the question number and answer number together
for question_num in range(0, 10):
    answer_num = input("Enter the Answer Number:")
    print(f"Question Num = #{question_num}; Answer Num = #{answer_num}")

Execute the cell and enter your answers as 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 (one at a time). Note that the answer numbers always remain in sync with the question numbers, but the bug shows up when the question-answer pairs aren't always being displayed to the console after providing the answer number. For example:

Here I'm about to enter 3 as an answer after having entered "0", "1", and "2"; Only "0" and "1" have flushed:

Here I just entered 3 and am about to enter 4 and all 4 previous response ("0", "1", "2", "3") have flushed:

Note that this issue doesn't occur on IDEs such as JupyterLab and Jupyter Notebooks, only on VS Code Jupyter Notebooks.
Solution/Workaround:
The solution/workaround was to add a sys.stdout.flush() before prompting the next time around, as shown below:

It would be good however for VS Code to not do this buffering, especially since JupyterLab and Jupyter Notebook don't run into this issue.

Had no issues up until today with printing... was this a recently introduced change?

Having the same issue here. I am using rusts pyo3 crate to generate python bindings. Works flawless in the command line without any notebook.

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/13039


Need to provide a hook to prevent tests from timing out when debugging

When debugging flutter tests with IntelliJ or another IDE, test timeouts still trigger which makes it frustrating to setbreakpoint within tests. As soon as you resume the debugger after hitting a breakpoint, the test you were trying to debug times out ending your debug session.
The recently added --pause-after-load in package:test handles this case ignoring timeouts when the flag is set. For consistency it would be nice if the same flag also worked with flutter test causing timeouts to be ignored. Currently the workaround is to delete the body of the _checkTimeout method in flutter_test/lib/src/binding.dart
See
https://github.com/dart-lang/test/pull/876
for the change to package:test to implement --pause-after-load
@grouma who implemented the feature for package:test

Note that flutter run already supports a --start-paused option which is used by IDEs. It would be nice if that option caused flutter_test to not timeout the test.
Separately it would be nice to normalize the names --pause-after-load  and --start-paused.


Error 500 when trying to login user in production (docker setup)

Hi,
Thanks a lot for this nice project.
When I try to login using my superuser credentials on production user docker setup, it fails with 500 error..
And then, when I check the docker logs, I don't really see anything except lines like:
DEBUG 2017-04-03 20:13:56,294 base 15<PHONE_NUMBER>59360 Configuring Raven for host: <raven.conf.remote.RemoteConfig object at 0x7fe10da72f28>
INFO 2017-04-03 20:13:56,297 base 15<PHONE_NUMBER>59360 Raven is not configured (logging is disabled). Please see the documentation for more information.
Is it not possible to see logs the usual way in production?
Sorry if noob questions..
Thanks

Marking this as closed, please reopen if still an issue.

For people that might be stuck at the same point, I managed to resolve this issue by using sentry.
I first created a Sentry account, and then provided the SENTRY_DSN in the .env file.
This allowed me to obtain a useful trace in the Sentry App.
Basically, the 500 error was due to a failure in the Mail backend, as I didn't provide a Mail backend configuration in the .env file (e.g. Mailgun), so I proceeded to add the Mailgun API and the Mailgun domain in the .env file and this solved my issue.

@jduraj mind adding that to the docs?

@jayfk https://github.com/pydanny/cookiecutter-django/pull/1134