Split nested snippet into inner/outer

What do you think?  I pulled out the "parameters" from the template for outer-scoped, added "parameters" (as values) for inner-scoped, and added comments to make clear what they are.  Should help steer users to inner-scoped when needed.
inner-scoped

    "resources": [
        {
            "name": "nestedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-06-01",
            "properties": {
                "expressionEvaluationOptions": {
                    "scope": "inner"
                },
                "mode": "Incremental",
                "parameters": {
                },
                "template": {
                    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
                    "contentVersion": "<IP_ADDRESS>",
                    "parameters": {},
                    "variables": {},
                    "resources": [],
                    "outputs": {}
                }
            }
        }
   ],

outer-scoped

    "resources": [
        {
            "name": "nestedDeployment1",
            "type": "Microsoft.Resources/deployments",
            "apiVersion": "2020-06-01",
            "properties": {
                "expressionEvaluationOptions": {
                    "scope": "outer"
                },
                "mode": "Incremental",
                "template": {
                    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
                    "contentVersion": "<IP_ADDRESS>",
                    "variables": {},
                    "resources": [],
                    "outputs": {}
                }
            }
        }
    ],

I could also remove the "expressionEvaluationOptions" from the outer-scoped since it's the default (and used to not exist).

I could also remove the "expressionEvaluationOptions" from the outer-scoped since it's the default (and used to not exist).

Yes, I'd say leave out all properties that are the default in snippets.


Add --path option to wit add command.

This PR adds a --path option to the wit add command, similar to how PR #113 added the option to cargo component add.
It also fixes the formatting such that dependencies that need an inline table are written with an inline table.

Ignore the CI failures for now, once wasm-tools and wit-bindgen are released, I'll update deps and rebase the outstanding PRs.


fix(events): fixed filtering on events

Proposed changes
added back the default event filter
Issue number: closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] CHANGELOG.md has been updated. Guide
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] The fixtures have been updated if needed (for migrations)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

La inn en liten fiks på gavekort-utsender også slik at den nå er good. Testet at den funker også

La inn en liten fiks på gavekort-utsender også slik at den nå er good. Testet at den funker også


[Event Request] codeunit 7017 "Price List Management" - OnCheckIfPriceListLineMarkingIsNeededOnBeforeFindLines

Describe the request
local procedure CheckIfPriceListLineMarkingIsNeeded(var PriceListLine: Record "Price List Line"; PriceAssetList: Codeunit "Price Asset List"): Boolean;
....
                PriceListLine.SetRange("Variant Code");
            OnCheckIfPriceListLineMarkingIsNeededOnBeforeFindLines(PriceListLine, PriceAsset);
            if not PriceListLine.IsEmpty() then begin
....
end;

[IntegrationEvent(false, false)]
local procedure OnCheckIfPriceListLineMarkingIsNeededOnBeforeFindLines(var PriceListLine: Record "Price List Line"; var PriceAsset: Record "Price Asset")
begin
end;

Additional context
We have a new price asset Attribute and we are not able to show them from the Item Card with action "Sales Prices". We are not able to set enough filters to enable MarkingIsUsed := true and rec.MarkedOnly(true);
Internal work item: AB#540597

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 21720.


Fix YamlDecoder and NaN tag

https://yaml.org/spec/1.2.2/#1032-tag-resolution
https://scastie.scala-lang.org/9DqmGdYWQwWA9OUmjqjbCg
Relates to

https://github.com/VirtusLab/scala-yaml/issues/314
https://github.com/VirtusLab/scala-yaml/pull/322

/cc @lbialy @OndrejSpanel

Haha, my first draft for NaN/Inf parsing used regex too and after Tomek's nitpick I decided to simplify at the cost of precision with endsWith. It's also a bit faster than regex I think. Is this a problem you have encountered in a real scenario (the -XXXInf) or are you just fixing the possible edge case? I mean, I thought about it for a minute and decided it's rather improbable that user would expect the field to be a Float/Double and it would contain a string ending with Inf by chance.
Proper perf-optimized impl would not use regex so it's a question whether we want to even take perf into consideration.

If you attempt to parse a string "Reinf" as Float and succeed, than that's just a bug. There's no way around it.
I don't mind if you optimize it further. I'm sure people, me included, would welcome that. (Generally speaking, optimizations should go hand in hand with benchmark, to show that they actually are optimizations.)
But first it needs to be correct.

Is this a problem you have encountered in a real scenario (the -XXXInf) or are you just fixing the possible edge case?

Fortunately I didn't stumble upon this bug in production. I was just reading the code and it figuratively jumped at me.

@tgodzik we're back to regex matching, but this impl is cleaner than mine, I like it

Btw this Any parsing is correct but very very slow.

Btw this Any parsing is correct but very very slow.

Do you have some numbers or any hint what actually is the bottleneck? Is it really the regex matching? That is something which won't be too difficult to fix. Maybe I could have a look at it myself if/when I have some time...

I'd be happy to ditch the regexes and do "manual" comparisons, if it helps the PR to get merged.
(I just don't have any benchmarks that could show how much it improves performance.)

No need, it's fine, like I said, I went the same way on the original PR before review. Performance would have to be considered separately with a serious amount of pondering whether it's actually relevant in a yaml library. Does anyone actually parse or print yaml at scale?


[Feature Request] Add HackerPack

Overview
A HackPortal user should be able to view all information about the hackathon regarding workshop materials, events, food, etc.
Proposal

Sidebar

General
Workshop Type(sponsor, tech, comm)

name of workshops

Hacker name and welcome at the bottom

Dashboard

Hack Center
Scan-in
HackerPack
Project submission

Main Content

Document links
Header and info

HackerPack must include the following:
Sidebar, dashboard, navigation bar
This application will exist at the route /dashboard/hackerpack and exist as a dynamic page. A hacker must be able to view and go to each subsection of the page via the sidebar menu. A sponsor should be able to view the workshop materials that are required for their own workshop. The dashboard should be accessible at all times to access other sections of the dashboard.

Hackerpack is finished. Next step is to add ability to fetch main content from outside documents to display in the hacker pack section, instead of directly writing out content into code.


[Feat]: add a python program for sharing file between computers.

Is your feature request related to a problem? Please describe.
add a python program for sharing file between computers.
Describe the solution you'd like.
can share file ussing two computers.
Describe alternatives you've considered.
python
Show us the magic with screenshots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

@Zedoman shall i work on this?


zuki-themes: 3.36-4 -> 3.38-1

Motivation for this change
Update to version 3.38-1
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123676 at 76bf46af run on x86_64-linux 1

2 packages built successfully:

tests.trivial
zuki-themes


Update spack package

Spack Package for Elephant
This PR contains a spack package for elephant. This package is required to integrate elephant as a component to  EBRAINS Phase 3.
Links:

spack: https://spack.readthedocs.io/en/latest/
spack pipelines for ebrains: https://drive.ebrains.eu/library/c11f95c0-59fd-428f-b02e-2238566c8499/Technical Coordination/Documentation/spack-pipelines-documentation/latest

Hello @Moritz-Alexander-Kern! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file .ebrains/spack/elephant/package.py:

Line 20:80: E501 line too long (96 > 79 characters)
Line 21:80: E501 line too long (96 > 79 characters)
Line 22:80: E501 line too long (96 > 79 characters)
Line 23:80: E501 line too long (95 > 79 characters)
Line 24:80: E501 line too long (95 > 79 characters)
Line 25:80: E501 line too long (95 > 79 characters)
Line 26:80: E501 line too long (95 > 79 characters)
Line 27:80: E501 line too long (95 > 79 characters)
Line 28:80: E501 line too long (95 > 79 characters)
Line 29:80: E501 line too long (95 > 79 characters)
Line 30:80: E501 line too long (95 > 79 characters)
Line 31:80: E501 line too long (95 > 79 characters)
Line 32:80: E501 line too long (95 > 79 characters)
Line 33:80: E501 line too long (95 > 79 characters)
Line 34:80: E501 line too long (95 > 79 characters)
Line 35:80: E501 line too long (95 > 79 characters)
Line 40:5: E303 too many blank lines (4)
Line 41:80: E501 line too long (90 > 79 characters)
Line 42:80: E501 line too long (100 > 79 characters)
Line 46:80: E501 line too long (100 > 79 characters)
Line 47:80: E501 line too long (87 > 79 characters)
Line 48:80: E501 line too long (87 > 79 characters)
Line 49:80: E501 line too long (87 > 79 characters)
Line 50:80: E501 line too long (82 > 79 characters)
Line 53:80: E501 line too long (82 > 79 characters)
Line 54:80: E501 line too long (82 > 79 characters)
Line 55:80: E501 line too long (82 > 79 characters)
Line 56:80: E501 line too long (82 > 79 characters)
Line 57:80: E501 line too long (83 > 79 characters)
Line 58:80: E501 line too long (88 > 79 characters)
Line 59:80: E501 line too long (87 > 79 characters)
Line 60:80: E501 line too long (82 > 79 characters)
Line 61:80: E501 line too long (82 > 79 characters)
Line 62:80: E501 line too long (82 > 79 characters)
Line 63:80: E501 line too long (82 > 79 characters)
Line 64:80: E501 line too long (82 > 79 characters)
Line 70:5: E303 too many blank lines (5)

The spack package has been added to the TC collab. It has also been added to the spack upstream, see: https://github.com/spack/spack/pull/30613 .
At this point it does not seem sensible to keep the spack package in NeuralEnsemble/elephant repo,
This PR can be reopened if we would like to add the spack package to this repo.


Prevent going trought closing function

When you first load your template, the dropdown is not dropped (isDropped and isOpened are both false).
you then go throught the following fonctions:
linkList();
LxDropdownService.close($scope);

which are useless to call at this point.

We've just released LumX v1.0.0rc1. This new version fixes the issue, so I'm closing your PR. Thank you!


To rebuild the hardware design

Hello , I am trying to rebuild the hardware design by the params I trained from resized 128x128 images with command ./make-hw.sh cnvW1A1 Z1-Z2 a, and I get the error:
/BNN-PYNQ-master/bnn/src/library/finn-hlslib/mvau.hpp:154:27: error: no matching function for call to object of type 'Recast'
auto const  act = TSrcI()(inElem, mmv);
and BNN-PYNQ-master/bnn/src/library/finn-hlslib/bnn-library.h:62:
/home/carol/桌面/BNN-PYNQ-master/bnn/src/library/finn-hlslib/fclayer.h:107:3: error: no matching function for call to 'Matrix_Vector_Activate_Batch'.
I have no idea how can I fixed the error, where should I fix it while I want to have a larger size input, and is the config.h file effect? I guess the problem is about activation but I am not sure, and a recipe for target 'obj/top.o' failed. If config.h effect can you tell me what is variable PE, SIMD, WMEM, TMEM means? I am confused about this, thank you

Hello , I am trying to rebuild the hardware design by the params I trained from resized 128x128 images with command ./make-hw.sh cnvW1A1 Z1-Z2 a, and I get the warning In file included from ../../../../../../../library/host/rawhls-offload.cpp:44:
In file included from /home/carol/BNN-PYNQ/bnn/src/library/host/foldedmv-offload.h:136:
/home/carol/BNN-PYNQ/bnn/src/library/finn-hlslib/bnn-library.h:47:9: warning: 'AP_INT_MAX_W' macro redefined [-Wmacro-redefined]
#define AP_INT_MAX_W 4096
^
/opt/Xilinx/Vivado/2017.4/include/etc/ap_private.h:96:9: note: previous definition is here
#define AP_INT_MAX_W 1024
And
WARNING: Hls::stream 'DoCompute.inter8' is read while empty, which may result in RTL simulation hanging.
WARNING: Hls::stream 'DoCompute.inter0_2' contains leftover data, which may result in RTL simulation hanging.
I have no idea how can I fixe it, Does any other file need to change if I want to have a larger size input instead of 32x32? And is the config.h file in folder hw effect? If config.h effect can you tell me what is variable PE, SIMD, WMEM, TMEM means? I am confused about this, thank you

Hi Changyiyu, do you still have both of these problems (no matching fxn call to Recast and hls::stream warnings), or just the latter one?

Hi, just the latter one. Thank you!

As already explained in the other thread #124 (btw, please close either one or the other) you need to change the dimensions of the feature maps in the script generating the config.h file. Additionally, you will need to change in the top.cpp file the value of the input bits in lines 163, 168 and 169.

Hi, thank you for the explanation. Then I have one more question is the file of w1a1 that I got after training, there have bin files of weight and the config.h in hw file, but does not generat the top.cpp. ls the top.cpp  a original file in /network/W1A1/hw? Actually I just need copy all of the bin files and config.h to /network/W1A1 from /training/binpara-cnvW1A1-pynq, Is it right?

The top.cpp file is not yet automatically generated. That file have to be hand written and reflect the network topology you have trained. Have you changed the number or type of layers?

No, I just change the pixel size of the input image. Should I change the number of layers in the model for the bigger pixel?


newSize = -1 when make settler in city with size 1

I haven't write access to repo, so I cannot merge :(

@Kright You should have write access to the repo now and be able to merge your own PRs!  Congratulations on being the first new contributor since we came up with a process for how to add people to the team!


Changed CONTRIBUTING.md

I added some informations for newbies.

It showed error in maths/rsa.py , when I restarted build, the error was gone. https://travis-ci.org/keon/algorithms/builds/366117956


BL-967-fe-navbar-could-stay-fixed-when-scrolling

Description
Ticket BL-967-fe-navbar-could-stay-fixed-when-scrolling
The user story for the ticket was to make the header sticky so that when the user scrolls down he has access to it all the time. specially on smaller screens when the user has to do a lot of scrolling.
we achieved the objective by doing the following:

Target the correct class for the entire element we want to make sticky.
Apply the position property: sticky to it.
we noticed that when scrolling some of the items show up above the header. so we modified the Z-index property to fix this issue.

Video Link
Loom Video
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Love to see that we got this fixed this makes a huge difference great work


Can't save resource when Statamic search is enabled

Discussed in https://github.com/duncanmcclean/runway/discussions/344

Originally posted by martink635 September 23, 2023
I need some help with setting this up. I am following the docs, and everything mostly works fine, but on saving I get this error:
[2023-09-23 12:54:34] local.ERROR: DoubleThreeDigital\Runway\Data\AugmentedModel::supplement(): Argument #1 ($data) must be of type array, null given, called in /statamic/vendor/doublethreedigital/runway/src/Search/Searchable.php on line 81 {"userId":"8d82ac72-df9a-485b-900a-6fd41bd61545","exception":"[object] (TypeError(code: 0): DoubleThreeDigital\\Runway\\Data\\AugmentedModel::supplement(): Argument #1 ($data) must be of type array, null given, called in /statamic/vendor/doublethreedigital/runway/src/Search/Searchable.php on line 81 at /statamic/vendor/doublethreedigital/runway/src/Data/AugmentedModel.php:26)

The model gets saved normally, but it throws this. Not sure what is the cause. I've tried and I can replicate it with a blueprint of just 1 title field and nothing else.
I think I missed a step somewhere, but can't find it.
Using the latest Statamic and Runway. I do have the Meilisearch addon, but the model in question is not being indexed.

@martink635 Can you share your search.php config file? I can't reproduce this.

Of course. I am sorry if this was not clear enough, this I think only happens if you use the Meilisearch addon for Statamic. It might be an issue on their end as well.
https://statamic.com/addons/elvenstar/statamic-meilisearch
    'indexes' => [

        'default' => [
            'driver' => 'local',
            'searchables' => 'all',
            'fields' => ['title'],
        ],

        'recipes' => [
            'driver' => 'meilisearch',
            'searchables' => ['collection:recipes'],
            'fields' => ['title', 'description', 'locale', 'status'],
            'sites' => "all",
            'settings' => [
                'filterableAttributes' => ['locale', 'status'],
                'stopWords' => [],
            ],
        ],

    ],

If I remove the recipes index, everything works fine. I've pasted the full stack error log in the discussion reply as well.

I had a look a few days ago and I think there's something that needs to be changed in the Mellisearch driver.
I think $document->reference() on this line needs to be changed to $document->getSearchReference() which is used in the same place in the built-in Algolia driver.
Would you be able to let me know if making that change fixes the issue?

I've opened a PR on the Mellisearch driver: https://github.com/elvenstar/statamic-meilisearch/pull/18
Since this issue isn't a bug with Runway itself, I'm going to close this issue now.

Thanks for this!
Sorry for the late reply, but the proposed change fixes this. 👍


release for arm eventhub

Can you please link the associated PR in the rest-api-specs repo that shows the change in swagger that drove the changes here?

This PR is not required, it's just for Python.


Remove Typo Error In Azure CLI

$ is used in variable declaration and remove Typo Error In Azure CLI

@msmbaldwin
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Improve blockwise_meta exception handling

Current blockwise_meta/blockwise implementation defaults to dtype construction of Dask.Array when an non-trivial exception is raised when computing _meta. This is suboptimal for two reasons:

It's difficult to trace that the defaulting happened within blockwise for somewhat complex user code;
Exceptions that come from the array compute task (with NumPy, CuPy, etc.) are not raised to the user during graph construction.

Ideally, we would handle all possible exceptions, with all remaining ones assumed to be user's mistake, such as passing casting to cupy.einsum (which isn't supported), as discussed in https://github.com/dask/dask/pull/4914.
Given that _meta now exists, Dask has become a universal scheduler, which probably means we can't handle every single possible exception, but we should at least allow developers to know about such cases, as well as letting users know they possibly made a mistake. We should therefore let most exceptions pass back to the user in blockwise.
This is loosely related to #4951, where we wish to allow users/developers be alerted of conditions that Dask can't handle and should probably be better handled by the library which Dask is using as a backend through __array_function__.

Just checking in, is this resolved by the xref'd PRs above @pentschev or is there still more to do here?

I'd say that #4954 improved this dramatically, but I don't consider it resolved, as per my comment https://github.com/dask/dask/pull/4954#issuecomment-502717153. In particular https://github.com/dask/dask/pull/4954/files#diff-3598e11c3b3a16881fecff61abdf1f4cR118 would still prevent other exceptions from a backend library's code to be raised. We don't yet have a general solution for that, so I would prefer to leave this open for now.


Ignore spuriously failing Windows test

I really have no clue why this test is failing on Windows, and after months of
being unable to diagnose I'm tired of retrying PRs due to this failure. Let's
just ignore it on Windows.
Closes #3466

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 3b4987c has been approved by brson

:hourglass: Testing commit 3b4987c with merge e7e6110...

:sunny: Test successful - status-appveyor, status-travis
Approved by: brson
Pushing e7e6110ac383d5cf4621e458f7b6b295fbe8e1fe to master...


Integrate AppVeyor CI #192

Fixes #192
Work in progress, will ping when it is ready.

Here's the badge for this PR:

Some points to discuss (if we agree to integrate AppVeyor):

We have the option of testing with 32-bit or 64-bit Java, or both. This should only matter if the project starts using native libraries, but which option should we go with?

Given that Travis already runs checkstyle for us, should we get Appveyor to run checkstyle as well? I'm inclined to say yes, because checkstyle does not add a significant cost to build times anyway.

cc @damithc @m133225

This PR currently explicitly switches on core.autocrlf. I think I will solve #191 first so we can keep the appveyor.yml configuration as simple as possible.

Nice work @pyokagan 👍
Any comments @m133225 ?

To answer the questions,

The more common one which I guess is 64-bit?
I'm fine to running checkstyle on both CIs

@damithc

The more common one which I guess is 64-bit?

Yeah I guess we should just go with one. Testing both 32-bit and 64-bit would double the build times, and I don't think we will have any architecture-specific bugs since we don't use any native libs.
If we ever start using native libs then we should switch to testing both architectures.

I'm fine to running checkstyle on both CIs

OK. I also just realised that running checkstyle on Windows would help us find issues like #191.

Not ready for review yet, #194 should be merged first :-P

Seems @m133225 gave the 👍
So you can go ahead and merge whenever you are ready @pyokagan

@damithc Thanks. This PR still needs a bit of cleanup though, I'll ping again when it's really ready.

Superseded by #218


WSGIRef package does not work with Python 3.5

WSGIRef package uses print statement, not print function, so it breaks under python 3

Thanks! I just cleaned the requirements file in 9a274e4.


Unified difficulty formula

Sorry, I'm not following, what's the purpose of this change?

It compartmentalizes Homestead/Byzantium formula changes to a single if clause, and makes the whole difficulty calculation straightforward. It also separates difficulty bomb from the main formula, and sets foundation to potentially bringing it under an if clause or removing altogether.


[OneDrive] list children return 404 rather than 401 after access_token expired

Hi folks,
There are many ways to list data form server.
But it seems return different code after access token expired
retuen 404:
https://api.onedrive.com/v1.0/drive/items/CB0BF412D51BBD9F!25418/children

{
  "error": {
    "code": "itemNotFound",
    "message": "Item does not exist"
  }
}

retuen 401:
https://api.onedrive.com/v1.0/drive/root/children

{
  "error": {
    "code": "unauthenticated",
    "message": "Must be authenticated to use '/drive' syntax"
  }
}

what is going wrong ヽ(o’Дo)ノヽ(o’Дo)ノヽ(o’Дo)ノヽ(o’Дo)ノヽ(o’Д`o)ノ.....

FWIW, there could be security implications to returning a 401 instead of a 404 for a specific item. If I'm an attacker trying to brute force random items with a made-up token, you shouldn't tell me when I hit a valid one. Even if I'm not allowed to get it.

Hi,
I am also facing issues with this wrong error code. The only way to handle expired tokens is for now to remove  access_token and get a new one each time my application gets a 404, which in most cases does not come from any auth issues.
I am pretty sure a lot of consuming apps implementations could easily lead to infinite loops if not handled with care.
Mike has a point about security, but if the service returned a 401 for any invalid or missing token, regardless of asked resource, then the attacker couldn't know if the item exists. This is the way a lot of APIs work.
Thank you

Good point. And FWIW, my implementation would also suffer from this issue, I just haven't had it pop up yet.

When you retrieve your access token there is an expires_in field, that should be how you determine that your token is viable or needs to be refreshed.
I would not recommend detecting 401 and making the assumption that your application does not have a valid access token anymore as there are many scenarios when interacting with a OneDrive you do not own that would send 401 Unauthorized and a new access token would not resolve them (The current accounts permissions were revoked by the owner)

Thank you,
Do you think the expires_in field is reliable? In other terms, is there any reason that would cause an access_token to become invalid sooner?
That would be a shame for my app to NOT ask for a new token because it thinks that current one is valid although it is not. But if this cannot happen, then I will definitely rely on expires_in rather than blindly refreshing the token at each 404.

I own and maintain the MSA OAuth client for Android, and the OneDrive SDK for Android.  I have a lot of faith in the value in the expires_in field, as it prevents unneeded round tripping when an authentication token has expired.

Shouldn't an expired or invalid access token always get a 401?
Why would you even check for the existence of a resource before checking the validity of the supplied token?

Hi everyone,
I know it's been a bit, but this has been fixed. It should 401 in the case of an invalid token now.
Thanks!


pod update在Installing Realm (3.1.0)卡住

Your questions.
-报错信息：
[!] Error installing Realm
[!] /usr/local/bin/git -C /var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6 submodule update --init --recursive
Submodule path 'Realm/ObjectStore': checked out '8517ee7f4378fe0f54945b3e4973766ff65e455d'
Submodule 'Realm/ObjectStore' (https://github.com/realm/realm-object-store.git) registered for path 'Realm/ObjectStore'
Cloning into '/private/var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6/Realm/ObjectStore'...
Submodule 'external/catch' (https://github.com/philsquared/Catch) registered for path 'Realm/ObjectStore/external/catch'
Cloning into '/private/var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6/Realm/ObjectStore/external/catch'...
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/philsquared/Catch' into submodule path '/private/var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6/Realm/ObjectStore/external/catch' failed
Failed to clone 'external/catch'. Retry scheduled
Cloning into '/private/var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6/Realm/ObjectStore/external/catch'...
error: RPC failed; curl 56 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/philsquared/Catch' into submodule path '/private/var/folders/_y/gfbrplk934313lprck24l6r00000gn/T/d20180929-38864-kqskm6/Realm/ObjectStore/external/catch' failed
Failed to clone 'external/catch' a second time, aborting
Failed to recurse into submodule path 'Realm/ObjectStore'
Environment.

Mobile model: iphoneX
Mobile system: iOS 8
Dev platform: darwin/windows/linux
Node: v10.11.0
Npm: 6.4.1

What do you think may be caused by the analysis of the problem.

我已经安装好了所有的环境，根据官网步骤走到这步就卡住了，不知道为什么。

Reappearance of the problem (It's best to have a screenshot).

可能是我昨晚电脑休眠了没吓到 我现在重新update一下


make certs valid for k8s dns names

[x] Installs cleanly on a fresh build of most recent master branch
[?] Upgrades cleanly from the most recent release
[x] Updates documentation relevant to the changes

fixes #1810

all green but manual validation is blocked by #1819


271 vite updates

sorry, need more time to fix  error -
does not provide an export named 'Buffer'

My overall feedback is that we need to find a better solution in general to this problem. Moving to a reliance upon globals in our production app in order to run our tests is not a good approach.

but we do as global when use extension -
 new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
    }),

But doesn't our npm package dependency "buffer": "^6.0.3" remove the requirement of relying on a global?

Realizing that our import should look like this:
import { Buffer } from 'buffer/';

This indicates that it's not the global buffer module, but the npm package that should be imported. Think this will help us get around these global issues?

this library works - https://www.npmjs.com/package/vite-plugin-node-stdlib-browser! but it's not  safe types, I'll try their implementation! strangely, other similar libraries don't work

can there be a problem that the library exposes the value as exports.Buffer and because of this I get the error The requested module 'web/node_modules/.pnpm/registry.npmmirror.com+buffer@6.0.3/node_modules/buffer/index.js?v=aed3b625' does not provide an export named 'Buffer'?


Provide a clear error message when the terraform binary doesn't exist.

Describe the solution you'd like
It would be nice if terragrunt could provide a clean error message when the terraform binary does not exist.
Describe alternatives you've considered
I've considered adding a before_hook calling a custom script to ensure the terraform binary exists. The downside of this approach is that it would entail a fair amount of boilerplate.
Additional context
n/a

Hi,
can be shared logs on how Terraform is failing?
In my tests, if Terraform is not available, the message below is printed:
$ terragrunt apply
ERRO[0000] exec: "terraform": executable file not found in $PATH
ERRO[0000] Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Maybe it is OS-specific, I tested on Ubuntu.

Ah, sorry. We have a custom terraform wrapper to do some stuff before invoking terraform. When using terraform directly (not our wrapper), I'm able to see the above output. I think we can chalk this up to something on our end. If I can find a workaround that's worth sharing, I'll post here.

Ah, sorry. We have a custom terraform wrapper to do some stuff before invoking terraform. When using terraform directly (not our wrapper), I'm able to see the above output. I think we can chalk this up to something on our end. If I can find a workaround that's worth sharing, I'll post here.


How to use any playback technology (YouTube, Wistia, Etc...) for Video.js using your package?

How to use https://github.com/videojs/videojs-youtube plugin with your package? please write me steps here.
Looking for exact steps from scratch to end.

Hi @surmon-china, would you consider add a wistia example in the future?


updated main photo to 2015 car and recolored logo

I think this combo of logo and photo looks good

I dont know, it's really hard for me to read the white. I don't like it that much. Also, that photo seems kind of low res or blurry. Like it was made blurry but not enough. Idk it just looks weird

I can blur the photo further and see how that looks. With no blur it's unreadable regardless of color. I tried orange, black and white and white seemed the best. We could do a black and white photo again I suppose but that was pretty universally not that well recieved

Bump, I can blur this more if you want but at least this change would have a current car photo instead of a 3 year old b&w photo

Let's finalize the design before we worry about changing it


Structure

Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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 not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

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

@leananepari Hey, was looking for a description of what this PR does. Could you maybe update the description section with a few sentences of link me to a Trello card? Thanks! 😸

Also, no reason to keep branches around after they've been merged! Deleting unused branches keeps your repo clean 😁


Put the delegate automatically

If I have something like this:
///
extension Something : SomeClassDelegate {
When I hit that space, instead of leaving me a field to fill out on the MARK that's created, can you have it notice that there's a protocol already declared and just use that as the default value?  So I'd want to get
// MARK: - SomeClassDelegate
there automatically.

It is a possible improvement and I will implement it later.

Added in #161


1.8 id/meta -> 1.9 blockstate NBT mappings and 1.12 id/meta -> 1.13 blockstate NBT mappings

Currently, it's not possible to upgrade a world from 1.12 or earlier to any version lower than 1.18.10, because the id/meta mappings we have produce blockstates for 1.18.10.
1.8 id/meta -> 1.9 blockstate mappings are needed for upgrading saved items from <= 1.8 to 1.9 or later, as 1.9 started using blockstate NBT for stored blockitems.
1.12 id/meta -> 1.13 blockstate mappings are needed for upgrading blocks from <= 1.12 to 1.13 or later, as 1.13 started using blockstate NBT for blocks.

Fixed by https://github.com/pmmp/BedrockBlockUpgradeSchema/commit/8b72c47109e174ac7f17c3ac546748f8e49a5fdf.


refactor: simplify test suites

refactor: allow unittest to discover suites
chore: format

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

This fixes the deprecation warning @ShaunSHamilton pointed out here: https://github.com/freeCodeCamp/curriculum-helpers/pull/122#pullrequestreview-1841481226


style: public profile | Icon bug fixed

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

Code of Conduct

[ ] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Thecyberworld.
Join the Thecyberworld GitHub Organisation by raising an issue (you will be sent an invitation).

Fixes issue #688

Take a look @ArkadiK94

@kabir0x23 what do you think?

@Riyazul555 In my opinion, the number should stay in the middle and please put the icon in left to the number ( the other side)

@Riyazul555 hi, do you work on it?

@kabir0x23 He didn't response to me, so I did it. what do you think?

@kabir0x23 could you review it?

looking good


remove regexp from danger file

Going to go ahead and merge this because my comment doesn't really affect anything here.


Scrolling List's bottom sheet is probably modal, should dim rest of screen

Open Gallery, go into components, lists. Tap the menu icon in the upper right to open the bottom sheet.
I think the bottom sheet is modal. If so, the spec says "When a modal bottom sheet slides into the screen, the rest of the screen dims, giving focus to the bottom sheet."

The list configuration bottom sheet is currently a "persistent bottom sheet" which is not supposed to be modal.
https://www.google.com/design/spec/components/bottom-sheets.html#bottom-sheets-persistent-bottom-sheets
There may be a better way to present the options for this demo.  The idea was to let the user see the effect of reconfiguring the list in situ.

Ah, OK. Thanks for the clarification!


don't rebuild the sysroot if profile.*.lto changed in Cargo.toml

cc #79

@homunkulus r+

:pushpin: Commit 66fc18c has been approved by japaric

:hourglass: Testing commit 66fc18c with merge 66fc18c...

:broken_heart: Test failed - status-appveyor


tests for DTCWT

Additional tests for dtcwt are required.

what would you like to test specifically?

we now have tests for Parseval since #55
shall we close this?


Use shell to redirect a few big files

Yep, it fails. I'll do another round tomorrow.
On Mon, Feb 13, 2017, 8:04 PM apolcyn<EMAIL_ADDRESS>wrote:

@apolcyn commented on this pull request.
In tools/run_tests/run_microbenchmark.py
https://github.com/grpc/grpc/pull/9699#pullrequestreview-21673462:

@@ -133,11 +133,9 @@ def collect_perf(bm_name, args):
'bins/mutrace/%s' % bm_name,
'--benchmark_filter=^%s$' % line,
'--benchmark_min_time=20'])

with open('bm.perf', 'w') as f:

 f.write(subprocess.check_output(['sudo', 'perf', 'script', '-i', 'perf.data']))

with open('bm.folded', 'w') as f:

 f.write(subprocess.check_output([

     '%s/stackcollapse-perf.pl

' % flamegraph_dir, 'bm.perf']))

subprocess.check_call(['sudo', 'perf', 'script', '-i', 'perf.data', '>', 'bm.perf'], shell=True)
subprocess.check_call([

   '%s/stackcollapse-perf.pl' % flamegraph_dir, 'bm.perf', '>', 'bm.folded'], shell=True)

Actually AFAIK I don't think the python.sub_process recognizes this?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/9699#pullrequestreview-21673462, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpudVBy6559vQXvMF9l-f1sSMtEetdzks5rcSfagaJpZM4MABMH
.


Get Plotly to update heatmap when clicked more than once

Solved but not ideally.  Talk to Al on Monday to see if there's a quick way of doing it better.

Obsolete with move to highcharts.


Script Error.

i have been using advdupe2 for a long time now and never had any issues besides the easily fixable EOF errors, but in the last few days i have been unable to save new versions of a dupe i have which worked and saved fine a few weeks ago, it saves it with success but whenever i click the file to load in the dupe again, it creates an instant script error and does not ghost, attempting to spawn it will make it spawn about halfway before disappearing and giving a "PhysicsObjects" related error.
all other saved dupes save and load in perfectly fine, there seems to be no logical reason for this one to get corrupted every time, even if i try saving an older version of it, it seems to corrupt now.

here is a copy of the file that cannot save itself
this is before trying to save the file
m32t100 luch_194.txt
this is after trying to save the file
m32t100 luch_195.txt

The lua errors indicate corrupt dupe. I can try saving and seeing if I can reproduce the corruption.

then i dont know why it works before saving, but reloading the file breaks it instantly.

The lua errors indicate corrupt dupe. I can try saving later and seeing if I can reproduce the corruption.

i have found the issue, it turned out to be a faulty holo e2 i had hidden away inside the tank, sorry to have potentially wasted your time grb93.

That shouldn't cause corruption unless your advdupe2 is out of date. I'd like to still investigate if that isn't the case.

No its the reason why i came here, ive used the workshop upload of advdupe2, and some friends had suggested to get rid of that one to download the github one, which didnt solve it.

I can reproduce it so I'll see whats causing it soon.


Feature Request: Bouncing Icon for a more non-intrusive notification

Hello Nudge Team, it is possible to have an option for the nudge icon to bounce up and down on the down in the dock for a slightly less intensive "hey you have an update" notification instead of the static window. Some of my end users respond to motion more positively than to a static window.

Sorry no plans to do this.


Bug after cancelling Requests

I open the request view with a button. When I cancel the request by using the default feature by tapping the background and then press the button again it looks the following:

Same as #14, I'll have a look later if nick hasn't by then.

Cool, thanks :)

This was resolved in #14. I'll make note of how to pull the newest stuff with cocoapods in the readme.

Alright, thanks for the support :)


Add node version check

Fixes #89

The error message could include some suggested actions which I've added in #101


[FEATURE REQUEST] :bookmark_tabs: Create CONTRIBUTING.md

Is your feature request related to a problem? Please describe.
People don't really know how to contribute.
Describe the solution you'd like
Create CONTRIBUTING.md (example) as a how-to guide
Add in README.md the link and info that we are open to new contributors.
Additional context
Consider creating CODE_OF_CONDUCT.md as well

template generator: https://bttger.github.io/contributing-gen-web/
may be useful: https://mozillascience.github.io/working-open-workshop/contributing/

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

We already have this documentation in place.


Add Mekanism (and Co.) to Curse

Hi there,
It would be nice to add Mekanism to Curse so it can be used in the Curse Voice minecraft launcher.

Nice to ask. Thought I'm not sure Aidan will agree as he never intended to put it on Curse and remove the last version uploaded on it (but the guy didn't asked and published it as a (fake) fork).
Don't hope too much

Asking is all we can do, installing isnt to hard but it would be a nice addition that could increase userbase ;). and of course Uploading a File/Mod/program which is not yours should not be condoned.
let's see what aidan says :D;)

In #2380  he said he was thinking about it.  That was sometime last year.
I'm quite curious what Aidan's thoughts on Curse are at the moment.

I'd rather he put it on CurseForge actually. Curse lags the Nether out of my browser and I don't know why.

Ah. Sorry, I assumed they meant Curse. Why do they even have mods on both Curse and CurseForge anyway?

This is being considered, I promise :)

unable to safely/securely transit through completion of downloading mekanism since last two releases. AdFly pages get hijacked WAY too easily. please take this into consideration for hosting project on curse.com aka cursefoge

Yeah, AdFly is broke as all heck lately... comes up blank, then when you wait out the timer and click the link it brings you to multiple very spammy and hacky looking and just totally untrustworthy sites with no actual downloading of Mekanism possible. I finally gave up and searched out an unauthorized mirror because it was impossible to get through AdFly's spam wall.

i eventually found it by downloading some random modpack (Random meaning i
forgot which one lol)
On Mon, Aug 29, 2016 at 4:26 AM, Daniel Bentley<EMAIL_ADDRESS>wrote:

Yeah, AdFly is broke as all heck lately... comes up blank, then when you
wait out the timer and click the link it brings you to multiple very spammy
and hacky looking and just totally untrustworthy sites with no actual
downloading of Mekanism possible. I finally gave up and searched out an
unauthorized mirror because it was impossible to get through AdFly's spam
wall.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aidancbrady/Mekanism/issues/3125#issuecomment-243076948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ9bYTx_fMIFW4hsyivg8uP7_lkrrDNWks5qkqXjgaJpZM4HsoE6
.


xrate not good enough

prometheus-2.39.1+0.0.3.linux-amd64
Some improvements, but this still needs to be fixed:

Scrape interval is 5s

It is not entirely clear what you mean. Are you referring to the jittery ramp-up? The few small jitters later on? The fact that there exists a ramp-up at all?

Hi. Yes, the ramp-up.
I would prefer (in most situations, especially for graphing) to just use less points, than interpreting rate 5m as average over 5 minutes, and no data meaning 0, but rather, to mean smooth in 5m windows, but ignore non-existing points.
I know that with such a definition, variance at the start of timeseries might be higher, so maybe have a minimum threshold (1/4 of time range), or something.
It is a bit weird imho with current semantic.

Consider that increase() is essentially implemented as rate() * interval. With your proposed approach, a metric that appears then disappears after a few minutes and increments by 1 per second would produce a total increase of 86400 over 1d,
Similarly, if you compute the rate over multiple hours of short-lived metrics, it would look as if they were increasing at their peak rate for the whole duration (e.g. a metric that appears and disappears after 5 minutes would result in a 65 minute line if you used rate(metric[1h]) on it). Another way or looking at it is that one would expect the area under a chart to be proportional to the increase of the counter(the rate is the derivative of the counter; the counter is the integral of the rate). The 65 minute constant rate for a 5-minute counter hugely overestimates the counter increase.
Plus, there's the potentially huge variance when the metric appears/disappears.


Fix "Return list of packages that support AllNamespaces install mode and do not use webhooks" catalog query in the docs

Need to fix "Return list of packages that support AllNamespaces install mode and do not use webhooks" query here and here.
Currently the query returns nothing.

@grokspawn did a bit of investigation and here are the important bits:

The issue appears to be that the catalog has shifted from bundle-level metadata stashed in olm.bundle.object to olm.csv.metadata.

Here's a flawed replacement for jq when olm.csv.metadata is present in the catalog:
jq -cs '.[]|select(.schema == "olm.bundle") | {"package":.package, "version": .properties[] | select(.type == "olm.package").value.version, "compatibleInstallMode": .properties[] | select(.type == "olm.csv.metadata").value | select((.installModes[] | select(.type == "AllNamespaces" and .supported == true))).labels[]}'

Flawed because it seems to report each matching entry three times.

Fixed in https://github.com/operator-framework/operator-controller/pull/1464


Fixed build_visual_display_page producing a crash

Description of Work
Fixes #22
Inside build_visual_display_page, a workspace was repeatedly created which apparently produces a crash. The workspace was not used anywhere so simply deleting that line solved the issue.
Testing Instructions

In example_runScript.py make sure that run_data = "neutron".
Run example_runScript.py in the mantidpython console.
It should run smoothly now. Additionally, tables are created which link to the visual display pages.

Note: Visual display pages are broken. This is a known issue #

please fix conflict

thanks for this fix


Icon request: MSI

URL for the brand / site / app
https://www.msi.com/
Logo resources for the icon
No response
Anything else?
No response

Based of my research, MSI doesn't have any service that uses 2FA.


Chrome not open anything

What are you trying to achieve? (Expected behavior)
Opening a website
What do you get instead? (Actual behavior)
Chrome opens and shows "data:," in the location bar and nothing happens until PHP times out
How could the issue be reproduced? (Steps to reproduce)
https://github.com/facebook/php-webdriver/blob/community/example.php
Details

Php-webdriver version: latest from this repo from yesterday
PHP version: 7.2.8
Selenium server version: 3.9.1
Operating system: OSX latest
Browser used + version: ChromeDriver 2.44.609545

Console output from selenium driver
❯ java -jar ~/Downloads/selenium-server-standalone-3.9.1.jar
14:59:45.738 INFO - Selenium build info: version: '3.9.1', revision: '63f7b50'
14:59:45.739 INFO - Launching a standalone Selenium Server on port 4444
2018-11-22 14:59:45.876:INFO::main: Logging initialized @411ms to org.seleniumhq.jetty9.util.log.StdErrLog
2018-11-22 14:59:45.982:INFO:osjs.Server:main: jetty-9.4.7.v20170914, build timestamp: 2017-11-21T22:27:37+01:00, git hash: 82b8fb23f757335bb3329d540ce37a2a2615f0a8
2018-11-22 14:59:46.002:WARN:osjs.SecurityHandler:main: ServletContext@o.s.j.s.ServletContextHandler@48f278eb{/,null,STARTING} has uncovered http methods for path: /
2018-11-22 14:59:46.006:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@48f278eb{/,null,AVAILABLE}
2018-11-22 14:59:46.031:INFO:osjs.AbstractConnector:main: Started ServerConnector@4145bad8{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:4444}
2018-11-22 14:59:46.032:INFO:osjs.Server:main: Started @567ms
14:59:46.032 INFO - Selenium Server is up and running on port 4444
2018-11-22 15:00:12.586:INFO:osjshC.ROOT:qtp112797691-15: org.openqa.selenium.remote.server.WebDriverServlet-152aa092: Initialising WebDriverServlet
15:00:12.641 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession@7711f9c1
15:00:12.644 INFO - /session: Executing POST on /session (handler: BeginSession)
15:00:12.706 INFO - Capabilities are: Capabilities {browserName: chrome}
15:00:12.707 INFO - Capabilities {browserName: chrome} matched class org.openqa.selenium.remote.server.ServicedSession$Factory (provider: org.openqa.selenium.chrome.ChromeDriverService)
Starting ChromeDriver 2.44.609545 (c2f88692e98ce7233d2df7c724465ecacfe74df5) on port 1085
Only local connections are allowed.

Console output from php
❯ php index.php

Fatal error: Uncaught Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY"}}

Operation timed out after 30000 milliseconds with 0 bytes received in /Users/user/test/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:292
Stack trace:
#0 /Users/user/test/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php(126): Facebook\WebDriver\Remote\HttpCommandExecutor->execute(Object(Facebook\WebDriver\Remote\WebDriverCommand))
#1 /Users/user/test/index.php(18): Facebook\WebDriver\Remote\RemoteWebDriver::create('http://localhos...', Object(Facebook\WebDriver\Remote\DesiredCapabilities), 5000)
#2 {main}
  thrown in /Users/user/test/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php on line 292

Nevermind - updating chrome itself fixed it instantly...
FOR PEOPLE IN THE FUTURE FINDING THIS WITH THE SAME ISSUE:
UPDATE CHROME ON YOUR SYSTEM! ;)
as in literally start chrome or the window it opens and hit update!


Unable to find dependencies for InTheHand.BluetoothLE.dll

When my Visual C# setup project is doing its pre-build validation I am getting these warnings:
WARNING: Unable to find dependency 'SYSTEM.RUNTIME.WINDOWSRUNTIME' (Signature='B77A5C561934E089' Version='<IP_ADDRESS>') of assembly 'InTheHand.BluetoothLE.dll'
WARNING: Unable to find dependency 'WINDOWS.FOUNDATION.FOUNDATIONCONTRACT' (Signature='(null)' Version='<IP_ADDRESS>') of assembly 'InTheHand.BluetoothLE.dll'
WARNING: Unable to find dependency 'WINDOWS.FOUNDATION.UNIVERSALAPICONTRACT' (Signature='(null)' Version='<IP_ADDRESS>') of assembly 'InTheHand.BluetoothLE.dll'
I see that I have these packages installed along with many others:
InTheHand.BluetoothLE v4.0.25
System.Runtime.WindowsRuntime v4.6.0
Does anyone know the significance of these warnings? I haven't seen any runtime problems with the InTheHand.BluetoothLE.dll on the Windows PCs where I have installed my application.

What .NET platform does your project target? e.g. .NET Framework 4.x, .NET 5.0x etc This will determine which .dll is used and the dependencies are different because there are changes in the way interop with the Windows/UWP APIs works.

currently .NET Framework 4.7.2

Here's my packages.config:

When I install InTheHand.BluetoothLE.4.0.25 with NuGet I see this:
Attempting to gather dependency information for package 'InTheHand.BluetoothLE.4.0.25' with respect to project 'DriScope', targeting '.NETFramework,Version=v4.7.2'
Gathering dependency information took 97 ms
Attempting to resolve dependencies for package 'InTheHand.BluetoothLE.4.0.25' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'InTheHand.BluetoothLE.4.0.25'
Resolved actions to install package 'InTheHand.BluetoothLE.4.0.25'
Adding package 'Microsoft.Windows.SDK.Contracts.10.0.22621.2' to folder 'C:\SVN\SDAC2\APP\trunk\packages'
Added package 'Microsoft.Windows.SDK.Contracts.10.0.22621.2' to folder 'C:\SVN\SDAC2\APP\trunk\packages'
Added package 'Microsoft.Windows.SDK.Contracts.10.0.22621.2' to 'packages.config'
Successfully installed 'Microsoft.Windows.SDK.Contracts 10.0.22621.2' to DriScope
Adding package 'InTheHand.BluetoothLE.4.0.25' to folder 'C:\SVN\SDAC2\APP\trunk\packages'
Added package 'InTheHand.BluetoothLE.4.0.25' to folder 'C:\SVN\SDAC2\APP\trunk\packages'
Added package 'InTheHand.BluetoothLE.4.0.25' to 'packages.config'
Successfully installed 'InTheHand.BluetoothLE 4.0.25' to DriScope
Executing nuget actions took 2.23 sec
Time Elapsed: 00:00:02.7741800
========== Finished ==========

I'm hoping this warning won't actually mean there is a problem. The only thing I can see is that the net461 version of the dll (which net472 will use) specifies the target platform version as 10.0.19041.0 but references the interop library Microsoft.Windows.SDK.Contracts 10.0.22621.2 and it should probably be updated so that these match. Either way the minimum supported version is 10.0.17763, if your project targets an older version of Windows that might cause a warning and the code would fail.

I haven't seen any problems but I just wanted to make sure there won't be issues when my software is used on some user's Windows PCs.
I see you have bumped Microsoft.Windows.SDK.Contracts from 10.0.22621.2 to 10.0.22621.755 which is the latest version. Will you be releasing a new InTheHand.BluetoothLE soon? I have pulled your latest code but I'm not sure how to build it myself.

I performed these updates today using NuGet:
InTheHand.BluetoothLE.4.0.25 -> InTheHand.BluetoothLE.4.0.26
Microsoft.Windows.SDK.Contracts.10.0.22621.2 -> Microsoft.Windows.SDK.Contracts.10.0.22621.755
After doing this I get this error:
1>C:\SVN\SDAC2\APP\trunk\packages\Microsoft.Windows.SDK.Contracts.10.0.22621.755\build\Microsoft.Windows.SDK.Contracts.targets(4,5): error : Must use PackageReference
Do I need to right-click on my packages.config and select "Migrate packages.config to PackageReference..."? After I do that I have a slew of other errors that appear.
https://learn.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference
Is Microsoft forcing me to migrate from packages.config to PackageReference or is there a way around this?

Microsoft solved my issue:
In general, setup projects don’t understand WinMDs.  This package is a bit of a special case in that it’s used by .NET Framework projects and contains WinMD files, which is not common (though I know it’s supported, as described here).  You can likely get the behavior you’re looking for by excluding all these winmds from the setup project.  Expand “Dependencies”, multi-select all the WinMDs, then right click and Exclude.  This will of course exclude them from your installer, which is fine since they’re just metadata files used at build time.
I am still having this exception issue but it's separate to I will close this issue.


MoltenVK 1.1.3 #feb8d41

Patches MoltenVK to commit hash #feb8d41
Contains some fixes for problems we ran into with rust-gpu.

Also patched CI to macos-11


[Bug]: Theme app extensions preview not working

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App, Extension
Expected behavior
Allows preview of theme app extensions

┏━━ Pushing theme files to App Ext. Host (xxxxx-xxxxx) (#xxxxxxxxx) on xxxxxxx-dev.myshopify.com
┃                                                                      100%
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (24.69s) ━━
┏━━ Viewing extension… ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃ Enable your theme app extension:
┃ https://partners.shopify.com/xxxxxx/apps/xxxxxxxx/extensions/theme_app_extension/xxxxxxxxx
┃
┃ Setup your theme app extension in the host theme:
┃ https://xxxxxxxx.myshopify.com/admin/themes/xxxxxxxx/editor
┃
┃ Preview your theme app extension:
┃ http://<IP_ADDRESS>:9292
┃
┃ (Use Ctrl-C to stop)
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (0.0s) ━━
15:16:46 Pushed » 'xxxxxxxxx-extension' to a draft

Actual behavior
but not working...

╭─ error ─────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  command extension:serve:/Users/xxxxx/Projects/xxxxxxx/xxxxxxxx/xxxxxxxx-shopify-app/extensions/x │
│  xxxxx-extension not found                                                                           │
│                                                                                │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Stack trace
No response
Reproduction steps

yarn create @shopify/app --template=ruby
cd app-template-ruby
cd web
bundle install
bin/rails app:template LOCATION=./template.rb
cd ..
yarn dev

Up to this point, it starts without problems.
But, when the next step is executed, it will not start on error.

yarn shopify app generate extension
yarn dev

Operating System
macOS Monterey 12.3.1
Shopify CLI version (check your project's package.json if you're not sure)
3.23.0
Shell
iTerm2
Node version (run node -v if you're not sure)
v14.18.1
What language and version are you using in your application?
ruby 3.1.2

I have solved this problem myself.
Here is what I did to solve it.

Remove the globally installed shopify-cli, such as the Homebrew version.
Make sure the project Ruby version and the globally Ruby version are the same.
Install the shopify-cli gem in the global
Remove all node_modules
Run the setup again from yarn install

I don't understand why you need to install the shopify-cli gem globally.
I would be very happy to be able to use it without installing it.

Same issue here 🧐

https://github.com/Shopify/cli/issues/724 has seemed to fix it for me, I needed to set my global rbenv version, which doesnt seem ideal.


Conditional compilation added

Restrict to only Windows compilation for saw

Pull Request Test Coverage Report for Build 303102837

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 39.724%

Totals

Change from base Build 302983733:
0.0%

Covered Lines:
20168

Relevant Lines:
46563

💛  - Coveralls


Improve unit test coverage [65%]

What does this PR do
Improve unit tests coverage
How can it be tested
Run VariantsCoreTests target on Xcode
Task
helps to resolve #82 (where #X is the number of an issue)
Checklist:

[ ] I ran make validation locally with success [this is causing troubles see #99]
[x] I have not introduced new bugs
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new errors

Fails

:no_entry_sign:
Copyright header is missing in files: Tests/VariantsCoreTests/ProjectFactoryTests.swift, Tests/VariantsCoreTests/String+WriteTests.swift

  Generated by :no_entry_sign: Danger Swift against 38744ff127a70b3f68bddf29325617819d97229d


With ipykernel<6, breakpoints in cells are ignored if "jupyter.stopOnFirstLineWhileDebugging" is false

Environment data
Version: 1.60.1 (user setup)
Commit: 83bd43bc519d15e50c4272c6cf5c1479df196a4d
Date: 2021-09-10T17:07:10.714Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
Jupyter Extension: 2021.8.2041215044
ipykernel: 5.5.5
Expected behaviour
# %%
print(3)
print(5) # <-- set breakpoint here

If I I hit the "debug cell" code lens button, it should stop at print(5)
Actual behaviour
It does not stop and will simply run the whole cell in the debugger. It will stop if:

You were to put a breakpoint in the print function somewhere.
You have the "jupyter.stopOnFirstLineWhileDebugging" setting set to True; this will start the debugger paused on the first line of the cell, and continuing from there will stop at the breakpoint.

Thanks for the bug. Easy to repro too. I'm guessing we're not sending the breakpoints early enough when there's no initial breakpoint, or we send them but the source isn't matching.

Note for anybody investigating. Set these to see what messages are getting sent to debugpy:
PYDEVD_DEBUG=True
DEBUGPY_LOG_DIR=<dir that already exists>
PYDEVD_DEBUG_FILE=<dir that exists, but new file allowed>

Going to close this as it works fine with ipykernel 6, with the old debugging mode


[Lead space] shorter variation

Task
A lot of efforts has been done to identify the height and usage for different lead spaces, so far only the tallest was built. Our goal this round would be to design and spec 1-2 more variants that might be shorter, more practical, and allow more content to show above the fold.

[x] Design explorations & synthesis of past work #5197
[x] Review with core team + design leads of AEM & HC
[x] Spec
[ ] Update documentation (website) FYI @JennySanchez
[ ] Build

Additional Information

box folder
Original size standards
Solutions page template
Services page template
Support landing page
Products landing page

Resources

Current one in our library: https://ibmdotcom-web-components.mybluemix.net/?path=/story/components-leadspace--default-with-no-image

Different use cases are captured in Ideation repo issue: https://app.zenhub.com/workspaces/carbon-for-ibmcom-5d449f3642eb1962336cbe52/issues/carbon-design-system/digital-design-ideation/126

Research and explorations from Lara:

Here is the lead space research work I shared today during Reboot design review. Feel free to dig around and challenge anything in the Sketch file or report. I added questions and potential directions to move forward with but all of this will need further review and probing by design and content strategy! Let me know if you have questions.
Sketch file with competitor audits and internal audit/journey proposals:
https://ibm.box.com/s/jyhzoysxeca8lenhz37gf8hfreoturjm
Research report:
https://ibm.box.com/s/2fywsn7qwhev2ay4ia3jknhh17ugx5vj
Draft content for lead spaces pattern (to publish on IBM.com Library)
Boxnote:
https://ibm.box.com/s/00ayfghsn26ge4g19lcn59buylav2xix

Hybrid Cloud library: https://pages.github.ibm.com/MSC-Cloud/hc_fractal/components/detail/2a--white.html

AEM proposal: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/5094

Some examples of Events and Think Lead space modifications.  https://www.ibm.com/events/  and https://www.ibm.com/events/think/
Rafeal to provide more details about the sizes to Jenny and document here.

Consider AEM's recommendation:
https://app.zenhub.com/workspaces/carbon-for-ibmcom-5d449f3642eb1962336cbe52/issues/carbon-design-system/carbon-for-ibm-dotcom/5094

Documented slack discussion:
Lead space variants

super
tall (default)
medium
short

Alignment options
left
center
Type options (this one requires more discussion)
semibold
light


how can I navigation one page to another

can't navigation to one page to another, when I use SideMenuItemDataTile ontap Function full screen are change how can I change only body part

can't navigation to one page to another, when I use SideMenuItemDataTile ontap Function full screen are change how can I change only body part

The project now includes simple and go router examples. Please take a look at them.
simple
go_router


in search results, registrations of the same project cannot be distinguished from one another

from the community repo: https://github.com/CenterForOpenScience/community/issues/276
Steps

Search the OSF for a project that has been registered multiple times (try searching "local versus global")

Outcome

Registrations of the same project are listed as separate results
The registrations are indistinguishable from one another
They do not necessarily appear next to each other or in recent to oldest order.

Suggested Behavior

Registrations should be distinguishable from one another.
They do not have to be listed as separate results. One suggestion is to collapse registrations of the same project that are returned in search results into one result, with the option to expand that result. On expansion, the different registrations and their dates could be shown and linked to. If this model is followed, I would suggest making the link visible when unexpanded (the title of the registration int he image below) link to the project's registrations page, so that the user is brought to a place where they can see each registration listed.

Of course, this could almost certainly be improved visually, but the basic idea is there.

@lbanner I like the suggested idea can I start working on it?

I'll assign you @Johnetordoff -- But want @jlcohoon thoughts here also on this solution. @jlcohoon? Thanks.

Just so you know, I'm expecting this might be a little complicated. Right now, we are just asking Elastic for results and displaying them. Elastic doesn't really understand about registrations being a part of another project, in the way that it doesn't understand that components belong to projects as such. Trying to find a way to handle this after Elastic is done with it won't work well, because Elastic handles sorting and pagination. This implies that we need to make changes to the Elastic search to make it work better.  Because we are using the Lucene search syntax, we may be somewhat limited in our methods of interaction. I don't know if we can combine aggregations with Lucene, for example, which would almost certainly be necessary.
The short of it is that we will probably want to have a proposal done for the change, and probably someone will need to have a conversation with @fabianvf about what's likely to be feasible and what isn't.

I suggested it, so I'm a pretty big fan of the plan. I'm happy to write/assign someone to write a proposal for it if need be.

If we're doing something fancy, it might be cool to aggregate all of the components that match a project as well. So, for example, if you searched for Reproducibility Psychology, then RPP would show up at the in the list, and all of the components would be accessible from the search page, rather than necessarily being each individually listed as a component. This should, in turn, cause RPP to be waaaay high up in the search results (which is a separate issue).
This might be different enough not to do all in one go. It might make sense to try it out with registrations and do components as a separate thing or not at all, but having it in the back of the head during design is not a bad thing.

Might a less fancy solution be simply changing the way we name Registrations? Say, for instance, adding a date in the name/title?

I'd think that that's a good solution for now. More fanciful work could be saved for the future. @lbanner how might we preserve the other suggestions for future work? I do think @brianjgeiger's suggestion would be a good enhancement.

How do you think the date should be formatted, to the minute or just to the day? I don't think it's out of the question you'd have two registration on the same day, but having a lot of extra digits in such small font makes it difficult to read. Is there any style guide rules about dates?

Not sure, probably not though.  You can check here: https://centerforopenscience.github.io/osf-style/
I'd say that for registrations, down to the minute is most helpful.

I would agree with @jlcohoon that to the minute would be ideal ... there may be a reason that you registered twice in a day (forgot to add a component prior to registration) and would want to make sure you know which is the most recent

+1

@caneruguz and I are working on amending the Style Guide to include rules on displaying date/time. Any input is appreciated.

@sloria any input on this?

re: Displaying date times--we currently display datetimes in localized iso8601 format, with a tooltip for UTC time. I think we go with that for now.

I think ISO 8601 is ideal for storage of dates, as it is easily machine readable, but I'm not sure it is the most human friendly representation. I think something like February 2nd, 2015 at 8:00PM is much friendlier to display.

:+1: for Fabian,
There was an extensive discussion on this earlier: https://github.com/CenterForOpenScience/osf.io/issues/668

I"m moving ahead with the dating individual entries option, if nobody has any more input. Also here's my purposed style guide guidelines for dates. It just tries to keep everything consistent with the log's datetime display:
Using Datestime
All dates are to be displayed in UTC and should be precise down to minute. Ideally dates should be bolded and appear with a explainatory tooltip. You may also want to include information about the timezone if many datetimes are listed.Example2015-01-23 1:42 PM

:+1: as long as @jlcohoon is on board!

I think there is no obstacle to go ahead with the date time to fix this specific issue.
However in terms of adding the concept to the style guide I would pause there. Since the goal of the guide is to have a conversation about the standards we have we should discuss it there:
https://github.com/CenterForOpenScience/osf-style/issues/65
After that issue is resolved we can go ahead and quote it for future date related style questions.

I support that thought/plan, but who currently has eyes on the StyleGuide? --- need a way to raise visibility on that when discussion/decision needed. In this case, I will raise it. Thanks.

@Johnetordoff Based on discussion and direction here: https://github.com/CenterForOpenScience/osf-style/issues/65 We are good to go on your approach. Thanks.

I think ISO 8601 is ideal for storage of date(time)s, as it is easily machine readable, but I'm not sure it is the most human friendly representation. I think something like February 2nd, 2015 at 8:00PM is much friendlier to display.

I disagree. ISO 8601 is an effective way to display dates in a human-friendly, non-locale-specific way (keep in mind that we don't localize dates at the moment). Datetimes should be displayed as they are on the site now--YYYY-MM-DD hh:mm A, using the FormattableDate helper.

@sloria XKCD does not count as human friendly, sneaky move there though, adding it as a supporting link!
But seriously I don't think you can find good support for ISO 8601 being user friendly method to display dates; which is okay. We have very good reasons to use that style. We support a community of science from all over the world; standardization, ability to render dates in many different computing systems and fairness is very important.

@caneruguz makes a fair point, though I think this discussion is outside the scope of this issue. As you pointed out, we had already come to a decision after discussion in https://github.com/CenterForOpenScience/osf.io/issues/668 . A suggest further discussion on displaying dates happen in the osf-style tracker.


Support generating pages in draft mode

Is your feature request related to a problem? Please describe.
I am able to generate all the pages from, the schema, but during development I'd still like to commit these files and have them in the repository, but in draft mode.
Perhaps I did not do this right, but I tried adding draft: true in the plugin without success.
{
  loaders: {
    GraphQLFileLoader: "@graphql-tools/graphql-file-loader",
    }
 draft: true
}

Describe the solution you'd like
A way to tell the plugin that the pages should be generated in draft mode.

Hi @stefan-mysten
What do you mean by draft mode? Can you give an example on it would differ from normal generated pages?

Thanks for the quick reply @edno
I would like to generate the pages where in their headers I have already set draft: true. Maybe this is a docusaurus related config option and not related to this plugin, but I couldn't find much info in their repo either.
Here's my generated boolean file for the graphql schema I have.
boolean.mdx file
---
id: boolean
title: Boolean
hide_table_of_contents: false
---

What I am looking for is:
---
id: boolean
title: Boolean
hide_table_of_contents: false
draft: true
---

Gotcha! I found the info in the page plugin-content-docs.
This is not currently supported, but this should be pretty straight forward as a new property for docOptions and consumed by printHeader method.

That makes sense, thanks for looking into it @edno!

@stefan-mysten
You can now pass draft: true setting using the new option docOptions.frontMatter released in 1.22.0
Example
plugins: [
    [
      "@graphql-markdown/docusaurus",
       {
        schema: "./schema/swapi.graphql",
        docOptions: {
          frontMatter: {
            draft: true, // set draft for generated pages
          },
        },
      },
    ],
  ],

@edno Appreciate you taking the time to add this feature!


Feature - add support for inline  blocks in Markdown

New feature to add support for inline <code> blocks. In Markdown, enclosing text in a single backtick causes the text to HTML to get rendered as <code>...text...</code>.

Fixed in commits

added support for inline code for Markdown
Updated code and readme for Markdown inline code support

Final merge in

Merge branch 'issue-11' into main


Add Operator-SDK changes

Following Upgrade Operator SKD [page](Upgrade SDK Version) I have created the following commits.

Upgrade changes to v1.14 and K8s to 1.22
Upgrade changes to v1.16
Upgrade changes to v1.18 + K8s 1.23 (v1.17 and v1.18)

At last Update Makefile target version & Operator-sdk 1.20 and run make bundle.

I have updated to Go 1.17, K8s 1.23 and related packages (to the relevant Go 1.17 version) since the latest Operator-SKD is still using K8s 1.23 and Go 1.17.

commit #4 (Switch go-get to go-install can be discarded after merging #12.

I am closing this PR since appending the two commits form #34 to #35 helped passing the Github test.
Originally the idea was to create small disconnected PRs, but I didn't apply to this PR (#34) and #35.
This PR failed with Github test error which looks like it is related to Go version (in Operator sdk version v1.21.0 they use Go 1.17 and in this PR I still have Go 1.16) while in #35 this test fails again with go mod tidy: go.mod file indicates go 1.18, but maximum supported version is 1.17 error.
Therefore, I have suspected that they both fail because for using the newest version for the Makefile tools (in #34 ) I need Go 1.18 and for Go 1.18 (#35) I need the newest version of the Makefile tools....


feat: multierror support

for now if one handler will return error slog-multi won't pass record to other handlers, so we SHOULD use multierr

Thanks for this first contrib ;)


Disable blocks depending on the page

My brother wanted to bother you again, and I have a question.
Is it possible to disable certain blocks when I select a page?

Suppose I want to disable certain blocks when the user selects the checkout page, because there are blocks that cannot be used unless they are on a specific page.

I was thinking of running a command where I get the BlockManager but I haven't found any functionality within the API that allows me to disable the blocks

I don't think you can disable blocks, maybe you can filter out the blocks?

It can also be an option, I will give an example to understand what I want to achieve.
There are some blocks that are responsible for building the payment form at the time of completing a purchase for having added products to the cart.
In theory, the blocks that are part of the payment process should only exist when selecting the checkout page.
So we could:
a. Hide blocks visually
b. Disable blocks when changing a page using the BlockManager
c. Change the list of blocks every time a page is changed.

I don't think you can disable the blocks from the API, the only option I can think of would be to filter out those blocks each time you switch to such a page so that they don't appear in the block manager.

If that seems to be the easiest option, I was looking at the api and indeed there is no method to do it.
I will take a look to make the filter and I will tell you if I could solve it through the filters


use else if to check for additional key codes

No need to use a second if statement when we're just checking for additional keys.

If you want, I can include this as part of the fix for #7. Just let me know either way.


Code modernizing proposal: using format instead of %

Python's replaced % with format some time ago and % is now deprecated, so I think switching to format could be appropriate.
Some examples:
in nltk.util:
raise UnicodeError(
        'Unable to decode input data.  Tried the following encodings: %s.'
        % ', '.join([repr(enc) for enc in encodings if enc]))

will be changed to:
raise UnicodeError(
        'Unable to decode input data.  Tried the following encodings: {}.'.format(
        ', '.join([repr(enc) for enc in encodings if enc])))

another one:
'%s.%s' % (selfname, name)

will be changed to
'{}.{}'.format(selfname, name)

Should this have been closed by #1512?

There are still quite a lot that can be cleaned up for this issue.
Moving from the C-style %s , %d, %f the new print_function from PEP 3105 would be a good thing.
E.g.
~/git/nltk$ grep '%s' nltk/*
...
Binary file nltk/treeprettyprinter.pyc matches
nltk/treetransforms.py:                parentString = "%s<%s>" % (parentChar, "-".join(parent))
nltk/treetransforms.py:                        newHead = "%s%s<%s>%s" % (originalNode, childChar, "-".join(childNodes[i:min([i+horzMarkov,numChildren])]),parentString) # create new head
nltk/treetransforms.py:                        newHead = "%s%s<%s>%s" % (originalNode, childChar, "-".join(childNodes[max([numChildren-i-horzMarkov,0]):-i]),parentString)
Binary file nltk/treetransforms.pyc matches
grep: nltk/twitter: Is a directory
nltk/util.py:    print('%s supports the following operations:' % obj.__name__)
nltk/util.py:            name = '%s.%s' % (selfname, name)
nltk/util.py:        print(textwrap.fill('%s%s' % (name, argspec),
nltk/util.py:        'Unable to decode input data.  Tried the following encodings: %s.'

Using "f-strings" might be an alternative too https://www.python.org/dev/peps/pep-0498/ =)

Using "f-strings" might be an alternative too https://www.python.org/dev/peps/pep-0498/ =)

I fully support this if/when 2.7 support is dropped. Moving to format() for now will ease the transition to f-strings.

Hi, I would like to work on this issue. Is it still open ?

Hello i am looking to contribute to this issue. This would be my first open source contribution. Can anyone explain what needs to be done regarding this issue?

@abid1998 if you would like to take up this issue, it's simple but tedious. Basically go to every file listed that contains %s and format the strings into f-strings or modern strings:
~/git/nltk$ grep '%s' nltk/**/* | cut -f1 -d":" | uniq

P/S: There'll be tricky cases but most of it should be simple.
Please take a look at https://github.com/nltk/nltk/blob/develop/CONTRIBUTING.md and create a pull-request whenever you're ready, we'll do a review to check through before finalizing a merge.

@alvations keep in mind though that f-strings can only be used if NLTK drops support for Python < 3.7. Also, if Python 2.7 is supported, you can't mechanically replace % formatting with .format, because they are not the same when unicode and str types are mixed (see https://github.com/nltk/nltk/issues/518#issuecomment-27180470).

I think it can be much easier to solve once Python 2.7 support is dropped; otherwise, there is a high risk of introducing Python 2 specific bugs.

@stevenbird are there any plans to make this issue active ?


[PoC] Sample Data Ingestion Feature

Overview

Write script to generate sample data (similar to below):
def generateCommerceData():
    f = Faker()

    sampleDate = f.iso8601()
    sampleOrder = f.pyint(0, 20)
    sampleFailure = f.pyint(0, 2)
    sampleRevenue = f.pricetag()

    return {'date': sampleDate, 'count': sampleOrder, 'failure': sampleFailure, 'revenue': sampleRevenue}

To make the process applicable to any existing or future plugin, the script should take in mappings for an argument. Additionally, the process for actually creating sample data will have to be consulted with the ML team.

Alternatives considered:

Use AD plugin team's Cypress tests to use their sample data.

Write script to ingest sample data into index (similar to below):
for i in range(5):
    body = generateCommerceData()
    body['orderID'] = i + 1
    response = client.index(
        index = index_name,
        body = body,
        id = i + 1,
        refresh = True
    )
    print('\nAdding document:')
    print(response)

The amount of data ingested will be enough to last for several weeks, when a scheduled job can delete both the index and detector/monitor/plugin tool.

Additionally, there is an option to ingest existing JSON data, if it is provided.

orderId = 1
with open("ecommerce.json", 'r') as f:
    for line in f:
        response = client.index(
            index = index_name,
            body = line,
            id = orderId,
            refresh = True
        )
        print('\nAdding document:')
        print(response)
        orderId += 1

Start the detector or other plugin tool with custom configurations using existing API calls (note that Observability plugin does not have an API reference page).

Schedule job using Kubernetes cronjobs to remove the index and detector and restart both. This may require creating an image.
# Delete the index
response = client.indices.delete(
    index = index_name
)

print('\nDeleting index:')
print(response)

# Re-create the index
index_body = {
    'settings': {
        'index': {
            'number_of_shards': 1
        }
    }
}

response = client.indices.create(index_name, body=index_body)
print('\nCreating index:')
print(response)

Alternatives considered:

Use a rollup job to roll up older data into a new index

Not needed for the use case as sample data is meant as a demo. The customer does not need rollups for old sample data. Rollup costs can be expensive as well.

Diagram

Couple comments here:

what's your final proposal here? I saw there are options and alternatives considered, please list your final proposal

this should cover mains functionality below, please let me know what's your thought

can generate random data, like as sample
can generate data based on customer provided json file
can accept for sample data files, like tar file contains all the required the data.
can call the API to configure sample data for plugins
can run remotely with secure login

@ohltyler @ylwu-amzn would you help to review

Couple comments here:
* what's your final proposal here? I saw there are options and alternatives considered, please list your final proposal

"Alternatives considered" are choices that came up during my design, but I omitted. Everything else in this PoC is my current plan.

* this should cover mains functionality below, please let me know what's your thought

  * can generate random data, like as [sample](https://github.com/elastic/makelogs)

I plan to use the Faker library to generate various fields that might be applicable. However, I will need to consult with the ML team to discuss several aspects of how to generate good random data.

  * can generate data based on customer provided json file

I just finished that feature in my script. The sample data generator can accept mappings (provided as a JSON string), a JSON string in the form {<field>: <value>}, or a NDJSON file (zipped or raw) as arguments. The user just has to specify the field type, either as a type listed here or a Faker attribute.

  * can accept for sample data files, like tar file contains all the required the data.

I plan to add a feature to the ingestion tool to allow users to just ingest data they provide as a NDJSON file.

  * can call the API to configure sample data for plugins

That is planned for my data ingestion script and should be straightforward as the OpenSearch documents provide various API references. However, I will sync up with the Observability plugin team to determine how to pre-configure the ingested data as there is no API section on the documentation.

  * can run remotely with secure login

I do not believe I have to worry about this feature if my script runs as a Kubernetes Cronjob. The process for this is to create a Dockerfile using my scripts, push it to a repo (I'm planning on DockerHub), and adding a Cronjob container to my cluster. As to configuring the Dockerfile and allowing container communication, I might need help on this part as I am still unfamiliar on containers.

push it to a repo (I'm planning on DockerHub)
have you been try to elastic container registry? in order to avoid the billing, I suggest you to take a look ECR

@huyaboo I'm late to take a look, but have a few comments you can think about

How often and when will the scheduled cleanup job run? You will want to make sure it isn't too disruptive to customers, and may want to communicate that this data and corresponding plugin tools are refreshed on a regular basis.
Regarding the data generation itself, you may want to keep in mind how it will perform with anomaly detectors. The ideal data to showcase good model performance includes a few main ideas:

data is dense enough such that there is >=1 data point per detector interval
there is sufficient historical data such that the real-time detector can begin to fully run after one interval (currently this requires 128 data points - e.g., a detector with interval 10 mins would start running if there is 10x128=1280 mins = 21.33 hrs of historical data when the detector is first started)
the configured features have some trend and aren't purely random noise, such that finding anomalies is a reasonable use case
there is a large amount of historical data to showcase and run historical detection

Rather than deleting the plugin resources (like anomaly detectors) every time, have you considered having a separate scheduled job to just ingest more data to the already-existing indices? This would obviously depend on the available space on the cluster, but it would be a less-expensive and less-disruptive way to have refreshed data without re-creating all of the plugin resources


Fixing timezone issues

Fixes #42

Merged per https://github.com/spring-cloud/spring-cloud-dataflow-metrics-collector/commit/d006c6ea6d2268d67e062ba00e45606fc831c58e


Apply gds changes onto upstream master

This PR shows the changes made to errbit by GDS. The commit history has been simplified by squashing the 60 or so commits from our current fork down to a smaller number of larger, feature-focused commits.
The intention behind this is that it will it easier to maintain our branch by rebasing against upstream.

@alext I've removed the cache headers for serving static files


Set publish mode to editor

Let's not push straight to master.

Tested via https://github.com/gil--/gatsby-starter-shopifypwa/pull/47
😃 Woo!