az resource delete --resource-type "Microsoft.Logic/workflows" doen't work when we try to delete a logic app.

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az resource delete --resource-group   --name  --subscription  --resource-type "Microsoft.Logic/workflows"
Describe the bug
When we ran commented command, the logic app is never deleted. There is not response after run the command.
To Reproduce
run this command az resource delete --resource-group   --name  --subscription  --resource-type "Microsoft.Logic/workflows"
Expected behavior
Logic app expected to be deleted.
Environment summary
N/A
Additional context
We also tested with powershell command getting the same result. We use AZ CLI command mainly.

@zhoxing-ms for awareness


History component requires internet access

Home Assistant release with the issue:

0.88.2
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):

Raspbian Stretch Lite
Home Assistant installed with the "python virtual environment"-method
Home Assistant automatically starts with the systemd setup given in documentation.
Component/platform:

https://www.home-assistant.io/components/recorder/
Description of problem:
If the Pi boots and connects first with a wifi network without internet connection the history component does not show anything but "No state history found.". If I switch to a wifi station with internet access the history components start working and show me some nice graphs of collected temperature data. If I switch back to the hotspot without internet connection then the history still works, it also shows new incoming data. On second boot everything works normally even without internet access, but a day later there is the same problem. So I believe the problem could be a process which blocks until it can reach a service in the internet before continuing, if the last connection was too long ago.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
just default recorder config, no changes

Traceback (if applicable):

Additional information:
The problem was found by setting up a demo project on a tablet's hotspot, which has no simcard and therefore no access to the internet.

History graphs rely on google charts https://developers.google.com/chart/


Pipe: fix losing points when enable batch mode (WIP)

Description
As title, the specific reason are not yet clear...

This PR has:

[ ] been self-reviewed.

[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[x] been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

LGTM. The reason is that one connector may transfer events from multiple dataregions, and events from different dataregions may have the same commit id. So we should use equals() instead of comparing commit ids.


refactor gc log parser

Codecov Report
Attention: 320 lines in your changes are missing coverage. Please review.

Comparison is base (e156c5a) 74.54% compared to head (c5d9cab) 9.86%.

Files
Patch %
Lines

...metheus/exporter/jgc/collector/parser/Metrics.java
0.00%
139 Missing :warning:

...us/exporter/jgc/collector/parser/GCAggregator.java
0.00%
109 Missing :warning:

...prometheus/exporter/jgc/collector/GCCollector.java
0.00%
23 Missing :warning:

...exporter/jgc/collector/LocalCollectorRegistry.java
0.00%
21 Missing :warning:

...etheus/exporter/jgc/collector/SystemCollector.java
0.00%
16 Missing :warning:

...c/main/java/prometheus/exporter/jgc/Bootstrap.java
0.00%
11 Missing :warning:

.../prometheus/exporter/jgc/tailer/TailerManager.java
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #54       +/-   ##
============================================
- Coverage     74.54%   9.86%   -64.69%
+ Complexity       77      34       -43
============================================
  Files            13      10        -3
  Lines          1603    1561       -42
  Branches        126     131        +5
============================================
- Hits           1195     154     -1041
- Misses          337    1390     +1053
+ Partials         71      17       -54

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Volume Manifest Builder to use local file system

v-m-b gets its images for processing from S3. We would like to use the local file system for two reasons:

we can generate manifest.jsons during the sync process, instead of a post-processing step
we eliminate the cost of calling S3's GetObject for each image.
Should be faster

@eroux @xristy I'd like to extend this issue a little by proposing we not look for and save graphics errors any more.  rationales:

Modular - this code should only build the volume manifest. Error checking is an add-on
audit-tool is the definitive source of format errors, it has better user control. This code uses magic constants which no longer apply.
The original code created a csv error file on each invocation, even if no errors were found. Let's not do that anymore.

If you want an informal notification of errors, I could leave the error checking code in place, but have the output added to the json, if it would not interfere with iiif. I could add an array:
{
"filename" : "IMG12345.jpg",
"dimensions" : { height: 42 , width: 42 },
graphics_errors : [
"imgTooBig",
"notTif4",
"notgreyscale"]
}
But mostly I think there's no market for this output.
Thoughts? Add it to json, or just drop it?

Well, I agree with the principle yes... the tool already writes a "size" property in the json when the image is too big, which is the main thing I need for iiif. The csv is only about gathering some info about non-conforming images, if it's deemed useless it can go.

No it doesn't.

I understand, thanks. I'll dump the errors, but will add the resolution in another change.

Assuming the Audit tool is run prior to generating the dimensions.json then the error checking in v-m-b shouldn't find any but if it does then it would be useful to know about it. Not checking is won't make errors go away. FInding an error early can reduce debug effort later


added js code to project

looks like you copied the js script from the bootcamp study guide. Are you going to modify for this project?

Don't forget to give credit to where you got the js code in your readme doc

if you are going to use code from the bootcamp study guide, be sure to credit that in your readme.


Menu Key does not cause a context-menu to pop up

The Menu Key should cause a right-click context menu to pop up when pressed, as it does across the entire OS and most applications.
Useful not only for broken computer mice (which I'm suffering from right now), but also for accessibility and consistency with what a user might expect.

Is this considered fully implemented by #29895, or are there still places where it should be implemented? See also https://github.com/godotengine/godot-proposals/issues/143.

My patch is only for the text editors.

Isn't this fixed by https://github.com/godotengine/godot/pull/38556?

Isn't this fixed by #38556?

I don't think so, it only makes the key recognized by the engine, but one still has to implement functionality to trigger an action when it's pressed in relevant editor controls.
But this is superseded by godotengine/godot-proposals#143.


Test failure: HelloWorld

This test fails occasionally with the following error:
System.TimeoutException : IIS failed to stop site Default Web Site.
   at Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer.WaitUntilSiteStopped()
   at Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer.StopAndDeleteAppPool() in /_/src/Microsoft.AspNetCore.Server.IntegrationTesting.IIS/IISDeployer.cs:line 240
   at Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer.Dispose() in /_/src/Microsoft.AspNetCore.Server.IntegrationTesting.IIS/IISDeployer.cs:line 55
   at Microsoft.AspNetCore.Server.IntegrationTesting.FunctionalTestsBase.StopServer() in /_/test/Common.FunctionalTests/Utilities/FunctionalTestsBase.cs:line 58
   at ReflectionAbstractionExtensions.DisposeTestClass(ITest test, Object testClass, IMessageBus messageBus, ExecutionTimer timer, CancellationTokenSource cancellationTokenSource) in C:\Dev\xunit\xunit\src\xunit.execution\Extensions\ReflectionAbstractionExtensions.cs:line 76
------- Stdout: -------
| [0.001s] TestLifetime Information: Starting test HelloWorld-Server: IIS, TFM: net461, Type: Standalone, Arch: x64, ANCM: V1, Host: OutOfProcess at 2018-08-10T20:46:57
| [0.010s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Information: Deploying [Variation] :: ServerType=IIS, Runtime=CoreClr, Arch=x64, BaseUrlHint=, Publish=False
| [0.012s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\unix\lib\netcoreapp2.0
| [0.012s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying System.Security.Principal.Windows.dll
| [0.013s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\unix\lib
| [0.013s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\unix
| [0.014s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\win\lib\netcoreapp2.0
| [0.014s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying System.Security.Principal.Windows.dll
| [0.016s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\win\lib\netcoreapp2.1
| [0.016s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying System.Security.Cryptography.Cng.dll
| [0.016s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\win\lib
| [0.018s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes\win
| [0.019s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\runtimes
| [0.019s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4\wwwroot
| [0.019s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying static.txt
| [0.020s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\2070abc0d7774fcdb2a398a3f72d61f4
| [0.020s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Authentication.Abstractions.dll
| [0.021s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Authentication.Core.dll
| [0.025s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Connections.Abstractions.dll
| [0.026s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.Abstractions.dll
| [0.027s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.dll
| [0.029s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.dll
| [0.030s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Http.Abstractions.dll
| [0.031s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Http.dll
| [0.033s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Http.Extensions.dll
| [0.034s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Http.Features.dll
| [0.035s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.HttpOverrides.dll
| [0.036s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.IISIntegration.dll
| [0.038s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.IISIntegration.pdb
| [0.039s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.IISIntegration.xml
| [0.045s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.Kestrel.Core.dll
| [0.047s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.Kestrel.dll
| [0.048s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.Kestrel.Https.dll
| [0.049s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISDeployer Debug:   Copying Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions.dll
| [0.050s]
...

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC @muratg
This issue was made automatically. If there is a problem contact ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

Is there any logging or extra information that we could add to make this more diagnosable when it happens again?

Yes?

[ ] Add the logging (TODO: Link to PR/commit)

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact ryanbrandenburg.

Should be fixed by https://github.com/aspnet/IISIntegration/commit/a8be2bf25b8ff748eba2660107ff9e2fb1945dcc.


[SPARK-18373][SS][Kafka]Make failOnDataLoss=false work with Spark jobs

What changes were proposed in this pull request?
This PR adds CachedKafkaConsumer.getAndIgnoreLostData to handle corner cases of failOnDataLoss=false. I listed all kinds of cases we should support in the code comment.
How was this patch tested?
Because I cannot find any way to manually control the Kafka server to clean up logs, it's impossible to write unit tests for each corner case. Therefore, I just created test("stress test for failOnDataLoss=false") which should cover most of corner cases.
I also modified some existing tests to test for both failOnDataLoss=false and failOnDataLoss=true to make sure it doesn't break existing logic.

Test build #68380 has started for PR 15820 at commit e8eff9f.

Use https://github.com/apache/spark/pull/15820/files?w=1 to review PR to ignore space changes.

cc @tdas @marmbrus @koeninger

Test build #68380 has finished for PR 15820 at commit e8eff9f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68380/
Test PASSed.

Merged build finished. Test PASSed.

Wow, looks like the new github comment interface did all kinds of weird things, apologies about that.

@koeninger Thanks for reviewing. Refactored the codes to avoid using early returns and addressed your comments.

Test build #68421 has started for PR 15820 at commit 7afac17.

Test build #68421 has finished for PR 15820 at commit 7afac17.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68421/
Test PASSed.

Test build #68508 has started for PR 15820 at commit 3aa9d7e.

Test build #68508 has finished for PR 15820 at commit 3aa9d7e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68508/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68731 has started for PR 15820 at commit 52ea0d6.

Test build #68733 has started for PR 15820 at commit 5475c59.

Test build #68735 has started for PR 15820 at commit 3b51e1e.

Test build #68731 has finished for PR 15820 at commit 52ea0d6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68731/
Test PASSed.

Test build #68733 has finished for PR 15820 at commit 5475c59.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68733/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68735 has finished for PR 15820 at commit 3b51e1e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68735/
Test PASSed.

Test build #68811 has started for PR 15820 at commit 6eb1cb9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68811/
Test PASSed.

Test build #68878 has started for PR 15820 at commit 2fc98cd.

Test build #68878 has finished for PR 15820 at commit 2fc98cd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68878/
Test PASSed.

Because the comment made by me and +1'ed by marmbrus is hidden at this point, I just want to re-iterate that this patch should not skip the rest of the partition in the case that a timeout happens.

Test build #68948 has started for PR 15820 at commit d0bcba0.

Test build #68948 has finished for PR 15820 at commit d0bcba0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68948/
Test FAILed.

Test build #68949 has started for PR 15820 at commit dcf6126.

Test build #68949 has finished for PR 15820 at commit dcf6126.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68949/
Test FAILed.

Test build #68952 has started for PR 15820 at commit 35f9b1a.

Test build #68952 has finished for PR 15820 at commit 35f9b1a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68952/
Test PASSed.

Test build #68969 has started for PR 15820 at commit 8558139.

Test build #68969 has finished for PR 15820 at commit 8558139.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68969/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68978 has started for PR 15820 at commit 1b8d56e.

@tdas I did some changes to make the stress test stable and ran it for 20 minutes without errors. I also confirmed the warning logs did appear in the unit test logs.

Test build #68978 has finished for PR 15820 at commit 1b8d56e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68978/
Test FAILed.

Test build #3431 has started for PR 15820 at commit 1b8d56e.

@zsxwing should the title include SPARK-18529 per your comment on the JIRA?

@zsxwing should the title include SPARK-18529 per your comment on the JIRA?

Thanks for pointing out. Updated.

Test build #3432 has started for PR 15820 at commit 1b8d56e.

Test build #3432 has finished for PR 15820 at commit 1b8d56e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM. Merging this in master and 2.1


Personal Blog - a new Gatsby.js theme

Maybe someone of you already know. Last week I released my first Gatsby.js theme
Themes is a great new, still experimental, feature of Gatsby.js. I decided to transform to themes all of my starters, just now.
So, it's time for Personal Blog, although in this  case the transformation will not be limited to implementing theme functionality. I decided to rewrite the whole codebase.
These are goals of the transformation:

upgrade to Gatsby v.2

for CSS, emotion instead of jss

for buttons and form elements, custom components instead of material-ui

for dropdown menus: @reach/menu-button

for form validation: formik

for UI state management: React Context instead of redux

as a cherry on top: we will rewrite  Class components to functional ones with hooks

I will start this weekend. If there is anybody who would like to help, write a comment below. Especially, I'm looking for someone who will help me rewrite styles from jss to emotion.

Cool! What’s your estimate for completing the rewrite?
Wishlist:

multiple tags
netlify-cms
discus comments (or something else, just not facebook)

@greglobinski Great news Greg! thanks for your work.
After reading this, i told my self that my hunch is right that you are going to replace jss with something else, i think it is a good choice that you chose emotion, because AFAIK gatsby works nice with emotion.
But before i, we or anybody decide to contribute to rewrite jss to emotion, i think at first you need to work on replacement from redux to react context, imho.
Once again, thanks greg, it is great to know that you will continue to support this great gatsby starter.

damn, i just realize what you mean about Theme is Gatsby.js Theme feature https://www.gatsbyjs.org/blog/2018-11-11-introducing-gatsby-themes/, to be honest, i find out about this just now.
Hmm... i need to check this out this weekend

Cool! What’s your estimate for completing the rewrite?

I can't say, I personally can work on this project only on weekends, so for sure it will not be one weekend.  :)

multiple tags, netlify-cms (gatsby plugin) ,discus comments (or something else, just not facebook)

all these can be done, but it's  not in the scope of this iteration

But before i, we or anybody decide to contribute to rewrite jss to emotion, i think at first you need to work on replacement from redux to react context, imho.

I will not try to replace redux with contex trying to maintain existing code working. I will start from zero level building the site step by step.

Update:
We will use emotion in a styled component way

Ok so I guess if one wants to start a new blog now, it will be easy to switch over the new version (once the theme is done) by just copying over the content directory right?

@maxscience Generally yes, but I can't promise that it will be possible without any 'moving' procedure, like for example, renaming content files.

If anybody would be interested in the progress of work, go to the issue board of my gatsby-themes repo

Current state of dev

current state of dev

current state of dev

That's all for this weekend, I would not (probably) be able to move forward till the next weekend. But I did a good progress till now, so stay tuned.

current state of dev

current state of dev; slowly but steadily :)

another step forward

Greg,
Love the look of what's happening with Gatsby and your starter/theme. I am curious. Would it be possible to integrate the gravatarMD5 feature from hero-blog? This is a really cool feature which gives a new level of functionality.

@polishedwp Sure, maybe not in the first iteration, but later why not :)

current state of development

although it was not planned, the theme will work with *.mdx files as a source of content.   https://twitter.com/greglobinski/status/1104710231605628928

@greglobinski looking forward to the new theme, checking new commits every weekend :)
question/request: the original blog theme misses tags per post and a screen to filter tags, any chance you plan to add these to your plan?
Estimates for the next release of the blog theme?

@alexpov

the original blog theme misses tags per post and a screen to filter by tags, any chance you plan to add these to your plan?
Yup, tags will be added

Estimates for the next release of the blog theme?
Not 100% sure, but I think I need two more weekends to release the theme in its first shape.

current state of dev
.

HI @greglobinski Any updates on the theme update?

@wzard Work is in progress. Not many visual changes though.

Hi @greglobinski, any updates ?

Hey @greglobinski, any things?

Hi all, I'm a Gatbsy newbie, been trying to run this starter straight out of the box but am getting numerous errors, is there something obvious I've missed or are there known issues with it at the moment?
Would really love to get this working as its looks fantastic!
The initial errors are these...
 info sharp Using cached /Users/xxx/.npm/_libvips/libvips-8.7.0-darwin-x64.tar.gz prebuild-install WARN install No prebuilt binaries found (target=12.1.0 runtime=node arch=x64 libc= platform=darwin)   TOUCH Release/obj.target/libvips-cpp.stamp   CXX(target) Release/obj.target/sharp/src/common.o In file included from ../src/common.cc:27: ../src/common.h:78:20: error: no member named 'Handle' in namespace 'v8'   bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);                ~~~~^ ../src/common.h:78:37: error: expected '(' for function-style cast or type construction   bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);                           ~~~~~~~~~~^ ../src/common.h:78:39: error: use of undeclared identifier 'obj'   bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
Appreciate any help!

Try clearing public, .cache folder and using node 11

I was going to post that there are issues with sharp and Node v.12 so looks like you are on the right track.
Also, has this starter been upgraded to Gatsby v.2 yet?

The starter is still on v1

Hi, thanks for the replies guys!
Yes I did already try clearing the cache but I’ll try the Node 12 and see if that works.
Regarding the V2, I thought I saw a check in last year which upgraded it to V2, could have been another branch though.
Thanks again!

Tried installing Node 11 and then got error stating Sharp model was missing so I installed it and then getting error telling me to remove the module...
Might be best to wait for Greg's V2 update.
`Something went wrong installing the "sharp" module
dlopen(/Users/xxx/Desktop/life-blog2/node_modules/sharp/build/Release/sharp.node, 1): Library not loaded: @rpath/libvips.42.dylib
Referenced from: /Users/xxx/Desktop/life-blog2/node_modules/sharp/vendor/lib/libvips-cpp.42.dylib
Reason: Incompatible library version: libvips-cpp.dylib requires version 52.0.0 or later, but libvips.42.dylib provides version 51.0.0

Remove the "node_modules/sharp" directory, run "npm install" and look for errors
Consult the installation documentation at https://sharp.pixelplumbing.com/en/stable/install/
Search for this error at https://github.com/lovell/sharp/issues
`

@Raf1001 I'm sorry, but this thread is reserved to inform others about progress in theme development, so I had to remove your comments, but feel free to open a separate issue.

Sorry guy, sorry for the delay but be sure that I did not abandon the project.

@greglobinski It been so long seen your last commit!

How is it going @greglobinski. awesome theme, hope to see the new version soon. good luck. :)


"allOf" tag does not work when used to extend existing schema.

Probably related to https://github.com/dschnelldavis/angular2-json-schema-form/issues/112
"allOf" tag does not work as per this sample code, which is the standard pattern for extending one schema with another:
{
  "schema":{
    "definitions": {
      "base":
      {
        "required": ["name"],
        "properties":
        {
          "name":{"type":"string", "default":"hello world!"}
        }
      }
    },
    "allOf":[
      {"$ref":"#/definitions/base"},
      {
        "properties":
        {
          "foo":{"type":"boolean", "default":false}
        }
      }
    ]
  }
}

Actually, this pattern should work.
OneOf and anyOf will need their own special widget, but allOf is already supported, and as long as the properties of the schemas being merged don't conflict, it should render correctly.
However, it appears you've found a bug in the algorithm that merges allOf schemas.
Thanks for posting the example. I'll look into it.

Never mind. The allOf merging algorithm is working fine. The problem is that your schema doesn't have a "type" property.
(In some cases, angular2-json-schema-form will add "type": "object" to a schema, but only if it sees a "properties" key at the root level of the schema, which this schema doesn't have.)
To make this schema render correctly, just add "type": "object", like so:
{
  "schema": {
    "type":"object",
    "definitions": {
      "base": {
        "properties": {
          "name": { "type":"string", "default":"hello world!" }
        }
        "required": ["name"],
      }
    },
    "allOf": [
      { "$ref": "#/definitions/base" },
      {
        "properties": {
          "foo": { "type":"boolean", "default":false }
        }
      }
    ]
  }
}


1 acorn vulnerability found in yarn.lock yesterday

Probably in the Snyk console already, but just incase:
From Dependabot:

1 acorn vulnerability found in yarn.lock yesterday
Remediation
Upgrade acorn to version 7.1.1 or later. For example:
<EMAIL_ADDRESS>version "7.1.1"
Always verify the validity and compatibility of suggestions with your codebase.
Details
GHSA-7fhm-mqm4-2wp7
moderate severity
Vulnerable versions: >= 7.0.0, < 7.1.1
Patched version: 7.1.1
There are high severity security vulnerabilities in two of ESLints dependencies:

acorn
minimist

The releases 1.8.3 and lower of svjsl (JSLib-npm) are vulnerable, but only if installed in a developer environment. A patch has been released (v1.8.4) which fixes these vulnerabilities.
Identifiers:
CVE-2020-7598
SNYK-JS-ACORN-559469 (doesn't have a CVE identifier)

Resolved.


Encapsulate does not support return Values

Type Error (TypeError: 'NoneType' object has no attribute 'getitem') when attempting to use the return value from an encapsulated job.

@benedictpaten will probably want the full stack trace if you still have it.

Where do I post it? It's an easily reproducible error.
On Wed, Sep 30, 2015 at 6:59 PM, Hannes Schmidt<EMAIL_ADDRESS>wrote:

@benedictpaten https://github.com/benedictpaten will probably want the
full stack trace if you still have it.
—
Reply to this email directly or view it on GitHub
https://github.com/BD2KGenomics/toil/issues/444#issuecomment-144593654.

--
Arjun Arkal Rao
PhD Student,
Haussler Lab,
UC Santa Cruz,
USA
<EMAIL_ADDRESS>

Here in the GH issue. Use triple backticks.
https://guides.github.com/features/mastering-markdown/#examples

Adding the full error trace
eduroam-169-233-202-80:Desktop arjun$ python untitled.py /tmp/temp
No handlers could be found for logger "toil.resource"
INFO:toil.lib.bioio:Logging set at level: INFO
INFO:toil.common:Using the single machine batch system
INFO:toil.jobStores.fileJobStore:Jobstore directory is: /tmp/temp
WARNING:toil.batchSystems.singleMachine:Limiting maxCores to CPU count of system (4).
INFO:toil.batchSystems.singleMachine:Setting up the thread pool with 40 workers, given a minimum CPU fraction of 0.100000 and a maximum CPU value of 4.
INFO:toil.common:Written the environment for the jobs to the environment file
WARNING:toil.resource:Can't globalize module ModuleDescriptor(dirPath='/Library/Python/2.7/site-packages', name='toil.job', extension='.pyc').
WARNING:toil.resource:Can't globalize module ModuleDescriptor(dirPath='/Library/Python/2.7/site-packages', name='toil.job', extension='.pyc').
WARNING:toil.resource:Can't globalize module ModuleDescriptor(dirPath='/Library/Python/2.7/site-packages', name='toil.job', extension='.pyc').
WARNING:toil.resource:Can't globalize module ModuleDescriptor(dirPath='/Library/Python/2.7/site-packages', name='toil.job', extension='.pyc').
INFO:toil.leader:Checked batch system has no running jobs and no updated jobs
INFO:toil.leader:Found 1 jobs to start and 0 jobs with successors to run
INFO:toil.leader:Starting the main loop
INFO:toil.batchSystems.singleMachine:Executing command: '/usr/bin/python -E /Library/Python/2.7/site-packages/toil/worker.py /tmp/temp L/g/jobmxyp84'.
WARNING:toil.leader:The job seems to have left a log file, indicating failure: L/g/jobmxyp84
WARNING:toil.leader:Reporting file: L/g/jobmxyp84
WARNING:toil.leader:L/g/jobmxyp84:	---TOIL WORKER OUTPUT LOG---
WARNING:toil.leader:L/g/jobmxyp84:	WARNING:toil.resource:Can't find resource for leader path '/Users/arjun/Desktop/untitled.py'
WARNING:toil.leader:L/g/jobmxyp84:	WARNING:toil.resource:Can't localize module ModuleDescriptor(dirPath='/Users/arjun/Desktop', name='untitled', extension='.py')
WARNING:toil.leader:L/g/jobmxyp84:	Traceback (most recent call last):
WARNING:toil.leader:L/g/jobmxyp84:	  File "/Library/Python/2.7/site-packages/toil/worker.py", line 241, in main
WARNING:toil.leader:L/g/jobmxyp84:	    jobStore=jobStore)
WARNING:toil.leader:L/g/jobmxyp84:	  File "/Library/Python/2.7/site-packages/toil/job.py", line 892, in _execute
WARNING:toil.leader:L/g/jobmxyp84:	    self._serialiseJobGraph(jobWrapper, jobStore, returnValues, False)
WARNING:toil.leader:L/g/jobmxyp84:	  File "/Library/Python/2.7/site-packages/toil/job.py", line 847, in _serialiseJobGraph
WARNING:toil.leader:L/g/jobmxyp84:	    self._setReturnValuesForPromises(returnValues, jobStore)
WARNING:toil.leader:L/g/jobmxyp84:	  File "/Library/Python/2.7/site-packages/toil/job.py", line 595, in _setReturnValuesForPromises
WARNING:toil.leader:L/g/jobmxyp84:	    argToStore = returnValues[i]
WARNING:toil.leader:L/g/jobmxyp84:	TypeError: 'NoneType' object has no attribute '__getitem__'
WARNING:toil.leader:L/g/jobmxyp84:	Exiting the worker because of a failed job on host Arjuns-MacBook-Pro.local
WARNING:toil.leader:L/g/jobmxyp84:	ERROR:__main__:Exiting the worker because of a failed job on host Arjuns-MacBook-Pro.local
WARNING:toil.leader:L/g/jobmxyp84:	WARNING:toil.jobWrapper:Due to failure we are reducing the remaining retry count of job L/g/jobmxyp84 to 0
WARNING:toil.leader:Job: L/g/jobmxyp84 is completely failed
INFO:toil.leader:Only failed jobs and their dependents (1 total) are remaining, so exiting.
INFO:toil.leader:Finished the main loop
INFO:toil.leader:Waiting for stats and logging collator process to finish
INFO:toil.leader:Stats/logging finished collating in 0.336077928543 seconds
Traceback (most recent call last):
  File "untitled.py", line 94, in <module>
    test_2() # TypeError: 'NoneType' object has no attribute '__getitem__'
  File "untitled.py", line 89, in test_2
    Job.Runner.startToil(F, params)
  File "/Library/Python/2.7/site-packages/toil/job.py", line 361, in startToil
    return mainLoop(config, batchSystem, jobStore, rootJob)
  File "/Library/Python/2.7/site-packages/toil/leader.py", line 505, in mainLoop
    raise FailedJobsException( config.jobStore, totalFailedJobs )
toil.leader.FailedJobsException: The job store '/tmp/temp' contains 1 failed jobs


Tell me what you think

If we are using multiple prefix's on both new and old models we should probably figure out what items can be shared and what items need to be separate. So far I  have one setup with the following but would like to know what you guys think.
Shared

models
repositories
functions.php / helpers.php

Not Shared

controllers
requests
fields_file
{prefixed}public/assets
{prefixed}/layouts/*

I  am starting to think It might help if we have 3 or 4 prefix options instead of 2 but i am still trying to work it out and have not been able to yet.
1- RoutePrefix
2- PathPrefix
3- ViewsPrefix
maybe even a forth for
4- PublicPrefix
This way even if all of the prefixes are not used they can default to the main prefix:
***prefix = admin would be all 4 unless otherwise specified. ***
then you could seperate all of the part into assignable options.
example: for public you could have themes  and can switch from one to another using this convention.
Or maybe have the layouts assigned in the controller so the route pulls the right views when directed.
example blog with layouts selected in controller:

public function index(Request $request)
  {
    $tag = $request->get('tag');
    $data = $this->dispatch(new BlogIndexData($tag));
    $layout = $tag ? Tag::layout($tag) : 'blog.layouts.index';

    return view($layout, $data);
  }

  public function showPost($slug, Request $request)
  {
    $post = Post::with('tags')->whereSlug($slug)->firstOrFail();
    $tag = $request->get('tag');
    if ($tag) {
        $tag = Tag::whereTag($tag)->firstOrFail();
    }

    return view($post->layout, compact('post', 'tag'));
  }

As of right know that Is all I have been working on but by all means lets collaborate.

Prefix Concept
Ok i did some testing today trying to find out the most effective way to use prefixes for both backwards compatibility and new generation.
My proposal is this:

RoutePrefix
PathPrefix
ViewsPrefix
PublicPrefix

Not only will these be very precise when building or converting exiting apps but it will also make it really hard for a hacker to get the hang of so will keep the app more secure. Not only that but it will also make it hard for someone with no laravel experience to mess up.
Now let me explain why.
lets say we have a basic blog and the normal routes would be something along the lines of
BLOG
    |- App
        |- Console
        |- Events
        |- Exceptions
        |- Helpers
        |- Http
            |- Controllers
                |- ADMIN:controllers
                OR
                |- BACKEND:controllers
            |- Middleware
            |- Requests
                |- ADMIN:Requests
                OR
                |- BACKEND:Requests
        |- Jobs
        |- Listeners
        |- Models
            |- ADMIN:models
            OR
            |- BACKEND:
        |- Policy
        |- Providers
        |- Repositories
        |- Services
    |- config
    |- database
    |- public
        |- ADMIN:ASSETS
            |- css
            |- js
            |- images
        OR
        |- BACKEND:
            |- css
            |- js
            |- images
        |- css
        |- js
        |- images
    |- resources
        |- lang
        |- assets
        |- views
            |- admin = ADMIN AREA
                    |- users
                    |- posts
                    OR
            |- backend = ADMIN AREA
                    |- users
                    |- posts
            |- users
            |- posts
    |- Storage

If you are familiar with laravel or any other framework they all have the same tree structures. This makes it very easy to learn and take advantage of.  As you can see the main pathways, routes and everything else are essentially the same as the other. This makes it very easy to get into each one without much trouble just my knowing one you pretty much know them all.
This also means if you already have an app and its admin section let say is backend for files but not for the routes then you would have to redo all of the files in that directory, and not be able to use the generator.

But

With laravel you can have the same thing but with names of everything not alike and very hard to determine without having access to the filesystem itself. Here is what I  propose.
Awesome Blog

{ RoutePrefix = ADMIN }
{ PathPrefix = BACKEND }
{ ViewsPrefix = SECURE }
{ PublicPrefix = ADMINLTE }

This would work out something like this:

Routes.php

Route::get('admin/users' [ 'as' => 'secure.users', 'uses' => 'Backend\UsersController@getIndex']);

App\Http\Controllers\Backend\UsersController.php

public function getIndex()
{
    $users = User::orderBy('created_at', 'DESC')->paginate(10);

    return view('secure.users.index', compact('users'))->with('active', 'user');
}

public/adminlte/layouts/app.blade.php

{!! asset('/adminlte/assets/css') !!}
{!! asset('/adminlte/assets/is') !!}
{!! asset('/adminlte/assets/images') !!}

SHARED ASSETS
App\MODELS\User.php
App\REPOSITORIES\UserRepository.php

As you can see it would be very hard to get to say the controller from the path in the assets or the route provided in the actions from the forms.
But like I  said the best part is this leaves the backwards compatability to work in a already build app with the directories that are within it.

And

Say you didnt want to do all this and you are building new then all of them default back to the first prefix supplied or none at all.

QUICK EXAMPLE OF POSSIBILITIES

AWESOME APP
    |- App
        |- Console
        |- Events
        |- Exceptions
        |- Helpers
        |- Http
            |- Controllers
                |- UsersController
                    |- {PathPrefix = BACKEND }: index, show, edit, create, update, delete // using {PublicPrefix = ADMINLTE }:ASSETS
                    |- {PathPrefix = FRONTEND }: index, show // using {PublicPrefix = liveSite }:ASSETS
            |- Middleware
            |- Requests
                |- {PathPrefix = BACKEND }: index, show, edit, create, update, delete  // using {PublicPrefix = ADMINLTE }:ASSETS
                |- {PathPrefix = FRONTEND }: index, show // using {PublicPrefix = liveSite }:ASSETS
        |- Jobs
        |- Listeners
        |- Models
            |- uSER:Shared
        |- Policy
        |- Providers
        |- Repositories
            |- uSER:Shared
        |- Services
    |- config
    |- database
    |- public
        |- {PublicPrefix = ADMINLTE }:ASSETS
            |- css
            |- js
            |- images
        |- {PublicPrefix = LIVESITE }:ASSETS
            |- css
            |- js
            |- images
    |- resources
        |- lang
        |- assets
        |- views
            |- {ViewsPrefix = SECURE } = ADMIN AREA
                    |- users  // using {PublicPrefix = ADMINLTE }:ASSETS
                    |- posts  // using {PublicPrefix = ADMINLTE }:ASSETS
            |- users // using {PublicPrefix = liveSite }:ASSETS
            |- posts// using {PublicPrefix = liveSite }:ASSETS
    |- Storage

@phillipmadsen I like the idea and will start working on it. But as of now, we are not using public prefix anywhere because we are directly referencing CDN in adminlte and bootstrap templates. But in next 2 weeks, I am going to push some more templates of some popular themes like metronic, flatlab, chandra and as these are paid themes. so a user who purchased it needs to put it at the right place and configure it to work. so then we will implement public prefix.

I have done one commit for initial support of 4 prefix options as mentioned above.
Also, I have added a support for multiple/nested prefix support like.
--prefix=backend,admin. so it will generate something like following,
Namespace: App\Http\Controllers\Backend\Admin
Path: app/Http/Controllers/Backend/Admin
views: resources/views/backend/admin
routes: backend.admin

Great ides, i love it.
I just started playing with your dev branch and am getting some errors ill list them just in case you might be working on it.

ran php artisan infyom:api_scaffold Product --fieldsFile='resources/model_schemas/Product.json'
returned

  [ErrorException]
  Undefined index: ns

@phillipmadsen I have pushed a fix for it. Check again.


Crossplane monitoring

What: Define relevant metrics
Why: Enable platform team to verify crossplane setup is working and get alerts on crossplane workloads issues
examples:

Orphaned resources (platform)
Reconciliation failures: sync errors (platform)
Dashboard for the user (what resources, count resource, sync status, MTTR): need to automate (User)
Adoption rate: how many manifests are crossplane (platform)

https://github.com/dfds/backstage/issues/514 and https://github.com/dfds/backstage/issues/515 spawned for the different types of monitoring setup


Create Uninvented Technology

This is a little bit of a sarcastic issue.
Recently discovered, a similar program already exists. So many startups in the world, so many ideas being created and realized at each moment.
Every idea I have ever had already exists. Never before have I created a brainchild that was not born a different mind. I find myself wondering if there is an idea that doesn't exist. Is there something truly and completely individual?
The answer, I fear, is no. As I look deeper into ideas, I challenge exemplary ideas.  Where would humans be without François Isaac de Rivaz's genius brainchild. Was that idea his own?
The answer here, is also no. François Isaac de Rivaz's idea was, in part, a product of his individual brain, however it was not solely his own. Without the discoveries of Thomas Edison, there would be no electricity. Without electricity, the automobile would have had no ignition for its hydrogen fuel.
If we examine the work of Thomas Edison, we find evidence that some of his ideas were not his own. Instead, another inventor was robbed for credit; Nikola Tesla.
Is any idea a unique invention? Perhaps, but most ideas are simply improvements on the past. A brain picks up on a historical creation, and crafts it into something new. This new invention, is an improvement or a more integrated utilization.
With these new principles, how do we exact this towards software? Can we create a revolutionary product, that changes the world? The answer is yes, it is possible. We can create something, however we must also acknowledge that others will come to similar ideas, and that these ideas are not truly and completely original.
The question now, is how do we make link dump revolutionary? How do we create something better? How do we take the ideas of others, and create something magnificent from them?

I think the question we need to ask is, does technology have to be revolutionary. I had this same debate about all the android apps I've made. I mean I made a system monitor, music player, and a calculator as example. none of them are unique technologies, and there's nothing wrong with that.
I think the reason we as tech companies and developers feel this way. As that is what technology does, it revolutionizes the world. But One thing I'd like to say, that's only what we hear about in the news and things. We never hear oh hey, microsoft made cortana, so revolutionary! But I heard about siri every where when it first came out right?
Another thing is, technology is so new. Computers were barely runnin kilobytes of memory in the 80s. a little more 30 years later it can hold thousands times that. What I'm getting at here, we feel technology is so revolutionary is because it grows so fast, so almost everything feels like a revolution. But once something grows it begins to improve itself.
Let's take music for example. Something that's been around forever, and much more than just 30 years old. You think Lil Wayne's new song is gonna be revolutionary? No, it's just gonna be another hip hop track. I'll even say J dilla isnt revolutionary. What he did, djs had been doing for years before him. But just because he isnt revolutionary in music and created some brand new never seen hip hop or genre, doesnt mean he's a legend, and an amazing artist.
Just because something like linkDrops exists, doesnt mean it can't be a great and respected piece of software.

HAHAHAHA I just found out raindrop.io isnt a website, its a plugin fror chrome too btw :')

I feel like this philisophical issue can be closed now :)


ByteArray as base64 string

Provide a serializer that encodes/decodes a ByteArray as a base64 encoded String
See

https://github.com/Kotlin/kotlinx.serialization/pull/1676
https://github.com/Kotlin/kotlinx.serialization/issues/1633
https://stackoverflow.com/questions/74049511/parse-a-byte-array-into-a-bytearray

Considerations:

ByteArray is multiplatform, so the implementation will either need to be pure Kotlin, or have platform specific implementations. Perhaps use https://square.github.io/okio/?
Should we also provide other encodings, like base16, base32, base64, base85?

Should we also provide other encodings, like base16, base32, base85?

I think we can hold off on that until someone makes a compelling argument for adding them.

ByteArray is multiplatform, so the implementation will either need to be pure Kotlin, or have platform specific implementations. Perhaps use https://square.github.io/okio/?

I think we can use the implementation from https://github.com/square/okio/blob/master/okio/src/commonMain/kotlin/okio/-Base64.kt, as long as we keep attribution to the original author, right? I would prefer not to pull the entire okio lib in just for base64 encoding at the moment.


[HOTFIX] Replace sqlContext and sparkSession with spark.

What changes were proposed in this pull request?
This replaces sparkSession with spark in CatalogSuite.scala.
How was this patch tested?
Pass the Jenkins tests.

Hi, @andrewor14   @techaddict
Typo errors seem to break builds.

Oh, there are more. I'll add more commits.

Test build #58254 has started for PR 13030 at commit 90031f0.

@dongjoon-hyun Thanks for doing this, merging should have caused problems since it was a very big patch. 👍

@andrewor14 . I've saw you fixed the first one. Please fix the second one, too.

I rebased.
Right, it was a huge work. Great, @techaddict !

Test build #58257 has started for PR 13030 at commit db0b416.

LGTM merging into master 2.0

Thank you. I think that's all. This passed the following, locally.
build/mvn -T 4 -q -DskipTests -Pyarn -Phadoop-2.3 -Pkinesis-asl -Phive -Phive-thriftserver install

Thanks for catching this @dongjoon-hyun. I'm surprised Jenkins didn't catch it.

Test build #58254 has finished for PR 13030 at commit 90031f0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58254/
Test FAILed.

Merged build finished. Test FAILed.

Test build #58257 has finished for PR 13030 at commit db0b416.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58257/
Test PASSed.

Merged build finished. Test PASSed.


Tutorial for basic usage of DynPy's reporting module

The essential information about reporting module for DynPy are to describe. The guide has to contain basic information on how to create a simple text document using the basic classes, i.e. reporting modules such as ReportText, Markdown or Picture.
Similar report can be found in #44

Update comment

Done, can be closed.


Add ChannelManifest.Builder

Adding Builder for ChannelManifest to make it easier to create them especially in tests.
Adding missing builder options for Channel and missing equals/toHash methods in Builder and ChannelManifest

Added a few more missing options for the builder.
@jmesnil could you merge this if you're OK with the change? I'd like to use it for #268

@spyrkob thanks!


Add descriptions to commands (namely, snippets)

This adds a "description" property to actions. Notably, the shell completion protocol (#3121) will now also populate that.
The suggestions UI can then use those descriptions to display an additional tooltip with that information.
TeachingTip was kinda an abject disaster last time I tried this, so this isn't a TeachingTip. It's literally a text block.
xlinks:

#13000
#15845
#14939 - the last abandoned attempt at this

Gifs:
Top-down, suggestion menu

bottom-up suggestion palette


[WIP] [Syntax] Refactor Tuple Type Syntax

This patch:

Refactors TypeArgumentListSyntax and
TypeArgumentListSyntaxData to use the SyntaxCollection and
SyntaxCollectionData APIs.
Refactors TupleTypeElementSyntax to own its trailing comma and
updates the tests accordingly.
Provides an infrastructure for promoting types to use
the SyntaxCollection APIs
Reworks TypeArgumentList as TupleTypeElementList

Still needs to be done:

Update LegacyASTTransformer and ensure those round-trip tests work.

Resolves SR-4307.

@swift-ci please smoke test

Are you planning to look at LegacyASTTransformer visitor methods for TupleTypeRepr?

Yep! I'm going to address that after addressing these comments.

@swift-ci please smoke test

@swift-ci please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 9a72a3ee8d5d86feeadccac0a816185bdd2480e9
Test requested by - @harlanhaskins

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 9a72a3ee8d5d86feeadccac0a816185bdd2480e9
Test requested by - @harlanhaskins

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Just amazing. Thanks!


Using Direct meter

Hello,
I found a tutorial for using meter in https://github.com/haoyuz/p4-tutorials/blob/master/examples/meter/.
In this tutorial, they use "meter_array_set_rates" to set the data rate for the flow. Now, I want to set the data rates by using p4runtime. Do P4runtime-shell supports to do this? Thanks you very much

Yes.
For an indirect meter, try:
P4Runtime sh >>> me = meter_entry["<name of meter object>"]

P4Runtime sh >>> me?

You should be getting a help message about how to set rates.

Hello,
I did me.cir =  to set the value. But I have another question about the unit. Do the rates in the P4runtime is units/microseconds?
Thanks in advance.

Units per second: https://github.com/p4lang/p4runtime/blob/v1.2.0/proto/p4/v1/p4runtime.proto#L346


Incremental tags per chapter?

First of all, I just want to say that I am very impressed with the book, and am very satisfied. I'm consistently impressed (and challenged) by the quality of the code Objc.io has produced over the years.
As I'm working through the book, however, it is difficult to come to this project and maintain a context for what is currently being developed. Would it be possible to see the project not in a final state, but as it is built up and refactored?
I understand that this is no small request. I think the learning potential of such an undertaking would be relatively huge, though.

@oflannabhra That's one of the things on our list. We didn't do it for the first iteration, because things were changing too much. We'll definitely consider this going forward. Thanks for the feedback!

:+1: man, you guys are awesome! Thanks for being so open and accessible!


Tuneup Changes zoom of Current Workspace

On the first run of a graph, tuneup "jitters" the screen by changing the zoom area. Is there any way to fix this?

Hi @johnpierson - you cannot reproduce this behavior without tuneup installed?

Hi @johnpierson - you cannot reproduce this behavior without tuneup installed?

I noticed it right after installing tuneup. Let me uninstall and give it a few runs as well. :)

I noticed it right after installing tuneup. Let me uninstall and give it a few runs as well. :)

With Tuneup Installed:

Without:

and the log from with tuneup:
Documentation Browser (id: 68B45FC0-0BD1-435C-BF28-B97CB03C71C8) view extension is added
DynamoManipulationExtension (id: 58B0496A-E3F8-43D9-86D2-94823D1D0F98) view extension is added
LibraryUI (id: 85941358-5525-4FF4-8D61-6CA831F122AB) view extension is added
Notifications (id: ef6cd025-514f-44cd-b6b1-69d9f5cce004) view extension is added
Monocle View Extension (id: 5A256B35-BD09-423C-82A1-372957143927) view extension is added
TuneUp (id: b318f80b-b1d0-4935-b80e-7ab1be7742b4) view extension is added
PackageManagerViewExtension (id: 100f5ec3-fde7-4205-80a7-c968b3a5a27b) view extension is added
Python Migration (id: 1f8146d0-58b1-4b3c-82b7-34a3fab5ac5d) view extension is added
Workspace References (id: A6706BF5-11C2-458F-B7C8-B745A77EF7FD) view extension is added
Welcome to Dynamo!
00:00:00.4976685 elapsed for loading Dynamo main window.
Preparing to load the library resources.
ViewExtensionCommandExecutive ( UniqueId: b318f80b-b1d0-4935-b80e-7ab1be7742b4, Name: TuneUp, commandTypeName: SelectModelCommand )
ViewExtensionCommandExecutive ( UniqueId: b318f80b-b1d0-4935-b80e-7ab1be7742b4, Name: TuneUp, commandTypeName: SelectModelCommand )

With Tuneup Installed:

Without:

and the log from with tuneup:
Documentation Browser (id: 68B45FC0-0BD1-435C-BF28-B97CB03C71C8) view extension is added
DynamoManipulationExtension (id: 58B0496A-E3F8-43D9-86D2-94823D1D0F98) view extension is added
LibraryUI (id: 85941358-5525-4FF4-8D61-6CA831F122AB) view extension is added
Notifications (id: ef6cd025-514f-44cd-b6b1-69d9f5cce004) view extension is added
Monocle View Extension (id: 5A256B35-BD09-423C-82A1-372957143927) view extension is added
TuneUp (id: b318f80b-b1d0-4935-b80e-7ab1be7742b4) view extension is added
PackageManagerViewExtension (id: 100f5ec3-fde7-4205-80a7-c968b3a5a27b) view extension is added
Python Migration (id: 1f8146d0-58b1-4b3c-82b7-34a3fab5ac5d) view extension is added
Workspace References (id: A6706BF5-11C2-458F-B7C8-B745A77EF7FD) view extension is added
Welcome to Dynamo!
00:00:00.4976685 elapsed for loading Dynamo main window.
Preparing to load the library resources.
ViewExtensionCommandExecutive ( UniqueId: b318f80b-b1d0-4935-b80e-7ab1be7742b4, Name: TuneUp, commandTypeName: SelectModelCommand )
ViewExtensionCommandExecutive ( UniqueId: b318f80b-b1d0-4935-b80e-7ab1be7742b4, Name: TuneUp, commandTypeName: SelectModelCommand )


localized version of Riot

Hi,
I found that strings.xml is localized only in english language.
I can translate in spanish and Italian if the programmers want integrate the localized files on the main sources.

It would be nice.

l10n+1. I think using Zanata/Transifex would be nice.

You are rigth.... closing


EMF support?

Thank you for making your library available.
The December 23, 2016 commit started down the path of adding EMF support.  Are there plans to resume that effort?

@tbluemel, I'm very glad to hear you've started digging into improving EMF support.  Does supporting EMF look to be substantially harder than WMF?  Are you able to reuse your WMF conversion approach in general or maybe even some of the code?
Thank you for starting on improving EMF support.

It's essentially the same concepts as WMF, just a different "API" or "records" if you will.    I made enough changes for some images to display something, but it still needs work before images start looking as intended.  I haven't had time to look at it further, but feel free to dig into it as well.  I currently don't have any work done that I haven't pushed.


Errors on api.Streams.Delete

Deletion of Stream from StreamSchedule throws 404 Error for GET request https://v2-dev.media.kukoon.de/api/v1/stream/STREAMID

okay, it makes a unessasary request in background - good finding

looks for me like solved


Feature/client/e3 create expense form

Describe your changes

Create create-expense-form
Modify create/update-expense api

Issue
#98
URL
http://localhost:3000/expenses/create
Screenshot (if you made the UI)
https://github.com/HAK2024/fairy-share/assets/132407687/e8e75440-612b-4a87-90fe-9df47a60e00f
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings and no errors

Could you delete client/app/expenses/type/index.ts as it's an empty file?

Fixed
https://github.com/HAK2024/fairy-share/pull/107/commits/f73d7f5a66cb0141bc9d85267c403f4aa4096ba4


parallel construction in the left nav bar across products

At a minimum, it seems like we should make the Intro sections congruent across products, possibly replicating "Concepts" and "Guides" across the other products, too:

Fixed by https://github.com/influxdata/docs.influxdata.com/pull/416 and https://github.com/influxdata/docs.influxdata.com/pull/426


interpolate env vars, tests

Description

Related Issue

Motivation and Context

How Has This Been Tested?

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 have signed the Adobe Open Source CLA.
[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.

lgtm, but qq do we support this also in the regular deployment, and if not why have it there?

This is also performed deep in runtimelib, although with a different regex, and it does not cover all the cases covered here.  ${key} {key} and $key but NOT literals like '${key}'
At some point this should be refactored ( into config loader I think )
I think it was also an error to put this logic in rtlib, it should not be looking at process.env


Running an experiment on a https:// site will insert http:// analytics tags

Hi, I'm running an experiment on a https site, however the analytics tags inserted by the experiment plugin are inserted only using http://
To be precise: ga.src = 'http://www.google-analytics.com/ga.js';
I had a look at the documentation, but couldn't find any solution there.
I must note, my site is behind a SSL terminator / proxy. The rewriting of images is creating absolute https URL's from relative urls (no http/https in front) just fine.

@Joostvanderlaan If your SSL terminator is (capable of) forwarding a X-Forwarded-Proto header to your webserver, you might want to take a look at https://developers.google.com/speed/pagespeed/module/https_support#RespectXForwardedProto


Intellisense API could support a transient input string on top of document

To provide Intellisense in a text box (e.g. for a watch expression or breakpoint condition), we use the provideCompletionItems method at the current cursor location in the underlying text document.
This works fine for the first completion (which does not need any input from the text box) but it fails as soon as new input is typed in the text box. In this case provideCompletionItems is not aware of the new text and returns bogus items.
To fix this, we could add the text entered in the textbox to the underlying text document so that the provideCompletionItems always sees the "full picture" and returns correct completions. The problem is that this would modify the underlying text document which would get saved and trigger other mechanisms e.g. error markers etc.
A better and simpler approach would be if provideCompletionItems could take an optional "overlay" string which is appended at the given location in a transient way before the completions are determined.

Unsure about that... For VS Code the truth is in the documents and adding another truth on the side a slightly confusing.


feat: support ChatModels Qianfan QianfanChatEndpoint function_call

Description:

feature for QianfanChatEndpoint function_call ability, add integration_test for it
add model, endpoint supported in calling params
add raw response in ChatModel Message

Issue:

#10867
#11105
#10215

Dependencies: no
Tag maintainer: @baskaryan
Twitter handle: no

CI actions seems good, PTAL. @baskaryan

No reply after long days. Tell me If I could do anything to promote this PR. Looking forward to your comments.  @baskaryan @eyurtsev

lgtm, thank you @NuODaniel!


added column with first looks

@angelinetsui I think this should work. Let me know what you think. :)

You're right, we don't want this. Will fix this.

wait!! I have a question. Aoi only has three levels: target, distractor and others. But we don't really want other as the Aoi....
For example,  other, other, other, other, target, target, we want target only
But I am unsure how we fix target, other, target, target.

It looks like rle() will cleverly not treat NA NA NA as a streak. So if you
turn "other" into NA, I think it will dtrt
On Wed, Apr 1, 2020 at 4:51 PM angelinetsui<EMAIL_ADDRESS>wrote:

wait!! I have a question. Aoi only has three levels: target, distractor
and others. But we don't really want other as the Aoi....
For example, other, other, other, other, target, target, we want target
only
But I am unsure how we fix target, other, target, target.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/manybabies/mb2-analysis/pull/45#issuecomment-607544922,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGNTIRL44EKR46HHSYL7W3RKPHOTANCNFSM4LZS6FMA
.

such a cool function!!!

Fixed this now, had to create dummy variables in order to exploit this rle behavior with NaN's (as I can't have a column with both strings and NaN's)


MQTTRetainedMessageManager improvement proposal

Currently the MQTTRetainedMessageManager invokes an event to let listeners (i.e. a backing store) know when retained messages have changed. However, events raised in the UpdateMessage method do not convey what type of update has been performed, and the backing store would need to implement the same logic as present in the UpdateMessage method to replicate the same update action (i.e., check if the application message's payload is empty).
What I'd like to propose is to change the RetainedMessageChangedEvent event signature slightly to indicate whether a message has been added, removed or replaced. The StoredRetainedMessages member can then be removed from event arguments (breaking change). Relying on the full list of stored retained messages in these events may prevent further improvements in this area.
The included Server_Invokes_Retained_Message_Events unit test demonstrates the use of the modified event.
In the future, the GetMessages method and associated logic would probably need another look as it demands that all retained messages are made available in memory. Once that is resolved then the need for a separate implementation (i.e. via IMqttRetainedMessagesManager as in #1663 or otherwise) may become less relevant.
Any thoughts?

I have looked a bit further into GetMessages / GetMessage and the steps required to avoid holding all retained messages in memory by using "Intercept" event handlers. Multiple event handlers would be required to make that efficient, i.e. for "Fetch" to intercept loading, or getting one or more messages; for "AddOrUpdate", for "Remove", for "Clear", and for "Filter". All of the event handlers should be present at the same time to make things work. Of course, there could be a "super" event that accumulates all event parameters into one, but that is ugly. This leads back to the IMqttRetainedMessageManager interface approach, which seems to be the cleaner option and is likely more efficient.
Here is my trial (I haven't tried with an actual database behind): https://github.com/logicaloud/MQTTnet/tree/improve-mqttretainedmessagemanager-with-intercept-events
It now becomes questionable whether it is worthwhile introducing a breaking change with this proposal, since it wouldn't prepare some path forward. So, I'd be happy to close. I'll leave this up for a few days in case there is some feedback, or feel free to close now.

Please see my comment here: https://github.com/dotnet/MQTTnet/discussions/1764#discussioncomment-6188068

I close this one now; any improvements can flow into what comes out of discussion #1764.

Closing.


feat: Initial commit

Description
PowerVS instance creation with storage configuration.
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[x] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

@ocofaigh please trigger the pipeline :)

/run pipeline

/run pipeline

@ocofaigh please run it again :)

@ocofaigh done.

@ocofaigh thank you for those comments. All fixed :)

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline


get_byte_buffer equivalent in bincode 2?

Hi. I am interested in bincode 2 and am trying migrating from v1. A difficult point is that I do not find an equivalent of BincodeRead::get_byte_buffer() in v2. I use it for zero-copy deserialization.
You might think, anyway, we need to first allocate a Vec<u8> then read data into it when using get_byte_buffer, hence there will be no difference compared to Reader::read() in v2, which fills data into a provided &[u8]. However, this is not the case when we are memory mapping a file and using a custom global allocator which can 1) ignore deallactions in that heap regions and latter free them in batch, or 2) can do partial deallocation. In my use case, I directly construct Vec<u8> (unsafely) from slices within the ignored heap regions and pass its ownership to deserializer in get_byte_buffer. The Vec<u8> is then passed to serve_bytes::ByteBuf or String in my data structures. There is zero copy in this deserializing process.
My use case may be tricky. However, as the allocator API is getting stabilized, we will be able to do it in a safer way.
I am wondering whether it would be better to provide a similar API in v2.

We're thinking of switching to the read_buf API (tracking issue, RFC) for this, once that is stabilized. Does that cover your use-case?

We're thinking of switching to the read_buf API (tracking issue, RFC) for this, once that is stabilized. Does that cover your use-case?

Unfortunately, no. read_buf is to avoid initialization. Maybe I did not describe it clearly. I'd like to provide some code samples.
For example, I have a struct:
#[derive(Serialize, Deserialize)]
struct MyData {
    // Serde will treat Vec<u8> as an array.
    // So, we need `serde_bytes` here.
    // Or, we can use String as an example.
    #[serde(with = "serde_bytes")]
    bytes: Vec<u8>,
    // ..other fields
}

I memory-map a file into memory:
let mmap = memmap2::MmapMut::map_mut(&file)?;
let ptr = mmap.as_mut_ptr();
let len = mmap.len();
let reader = MyReader { ptr, len };
std::mem::forget(mmap);

Then I implement a custom BincodeReader:
struct MyReader {
    ptr: *mut u8,
    len: usize,
}

impl<'a> BincodeRead<'a> for MyReader {
    fn get_byte_buffer(&mut self, length: usize) -> bincode::Result<Vec<u8>> {
        if self.len < length {
            // ...error handling stuff
        }
        // construct the Vec just on the mapped memory
        let vec = unsafe { Vec::from_raw_parts(self.ptr, length, length) };
        self.ptr = unsafe { self.ptr.add(amt) };
        self.len -= amt;
        Ok(vec)
    }

    // ...other methods
}

Finally,
let data: MyData = bincode::deserialize_from_custom(reader);

This will work if we are using a custom global allocator that ignores deallocations in mapped heap region (otherwise it will corrupt). You can see that data.bytes will right point to the mapped memory: it is completely copy-free, and the copying from kernel file buffer to userspace is also eliminated.

I think I understand what you want for your use case.
Unfortunately the bincode trait can't return Vec directly any more because we want to make embedded systems a first class citizen for bincode. I don't see an easy way to add a specialized function that returns a Vec only if alloc is enabled, this sounds like it'd break horribly if bincode is somewhere in a complex dependency tree.
It would be nice if we could do something like
trait CustomAllocator {
    fn allocate_vec_in_place(...);
}

impl<T, A> bincode::Decode for Vec<T, A>
    where T: bincode::Decode,
    A: CustomAllocator
{
     // ...
}

impl<T> bincode::Decode for Vec<T, Global>
    where T: bincode::Decode
{
     // ...
}

But that

sounds like it needs implementation specialization
sounds very specific to your use case and not something we can implement globally.

For now I think the best solution would be to have your own Vec wrapper:
struct CustomAllocVec<T>(Vec<T, YourAllocator>);

impl<T: Decode> Decode for CustomAllocVec<T> {
    // you can do your custom logic here
}

But that would require having control over all vecs in your dependency tree

But that

sounds like it needs implementation specialization
sounds very specific to your use case and not something we can implement globally.

Yes, you're right. Maybe we could do it with something that is similar to #[serde(with="...")]. It would be nice if we could achieve proxying using bincode's encode and decode, e.g.:
#[derive(Encode, Decode)]
struct MyData {
    #[bincode(decode_with="zero_copy_decode_vec")]
    bytes: Vec<u8>,
}

It is somewhat out of current topic, though. And we can still do it by implementing custom decode for the whole struct or with bincode::serde.


Add warning that Azure AD API will be decommissioned by the end of 2022

Microsoft is going to turn off the Azure AD API, which means users who are authenticated through it will no longer be able to log in to Rancher.
There is an email being sent to customers about this, but I think we should also put a banner in the UI warning people that service will be disrupted if the Rancher app is not added to the new API in the Azure portal.

@mantis-toboggan-md Do we now have this with the work you did for 2.6.7?

Yes: This is covered by #5739 and #5671 in 2.6 and #6316 in 2.5


Expose a way to compile mdast to html

As far as I can tell, there's no way to compile mdast once you have parsed a string to it.
This would be useful because I want to modify a mdast tree and then compile it to HTML

Welcome @maplant! 👋
This is duplicate of https://github.com/wooorm/markdown-rs/issues/101 and https://github.com/wooorm/markdown-rs/issues/32
Please check the issue tracker before logging a new ticket, thanks!


Feature/cleanup config

What? and Why?
These 3 items don't change between environments so removing them will reduce
the configuration burden.
Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   82.75%   82.75%
=======================================
  Files          14       14
  Lines        1061     1061
=======================================
  Hits          878      878
  Misses        183      183

Impacted Files
Coverage Δ

transform/settings.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Updated readme

Don't merge until log location in prod has been changed!


Set Elixir Path/Erlang bin, Atom breaks.

Hi there!
So I checked out one of the (closed) bugs but I'm still getting a problem similar to the one described.
I'm using Elixir 1.1.1, installed via Homebrew.
It's not an error I'm actually receiving, it's the fact that my whole Atom install becomes unresponsive until I manually delete the folder containing autocomplete-elixir. Am I just setting the elixir path wrong?
where does homebrew usually install Elixir, and where can I find my Erlang Bin directory?

I also have this issue.

I just wanted to add that if you uninstall the package with the Atom cli tool using the command apm delete autocomplete-elixir, the config.cson in your ~/.atom directory will still have the autocomplete-elixir configuration settings.
If you try reinstalling the package the client will continue to break again, so make sure you clean the config.cson of the autocomplete-elixir options before trying again.
You also want to double check that the path is set correctly. In the command line you can type which iex and if it was setup correctly you should see the path to it.

I've added Troubleshooting to the README.md file
Please check out if anything works for you from there

Seems to be a duplicate of #47


Add localization comments

Hopefully this will help the translators.

{Locked="{invariantBroken, details}"} needs to be like  {Locked="{invariantBroken}, {details}"}",

or just remove the commenting for locking {}, since our default rule should prevent translating {} already.


Feature request: Add Debug derives for types in windows-metadata

Motivation
Currently debugging and figuring out how to use the windows-metadata crate is cumbersome, since very few of the types it returns implement Debug. This was most frustrating for the structs and enums in https://github.com/microsoft/windows-rs/blob/master/crates/libs/metadata/src/reader/mod.rs and Type in https://github.com/microsoft/windows-rs/blob/master/crates/libs/metadata/src/reader/type.rs, but it seems that many of the types in this crate are missing Debug without a good reason.
As the std::fmt docs say:

fmt::Debug implementations should be implemented for all public types. Output will typically represent the internal state as faithfully as possible. The purpose of the Debug trait is to facilitate debugging Rust code. In most cases, using #[derive(Debug)] is sufficient and recommended.

Drawbacks
This could add some compilation slowdown, but that's mostly a worry for auto-generated code with thousands of types. This issue is about manually adding a couple of #[derive(Debug)] annotations on <50 types.
Rationale and alternatives
No response
Additional context
No response

If this would be accepted I can submit a PR for this.

The main challenge is that the reader types are really just indexes into metadata tables and those indexes by themselves only carry offsets so a formatter could not provide much visualization without an explicit reader.

The ones in the Tables macro are not that useful, but seeing their indices would still be a bit useful for debugging and especially when comparing them to when they are printed as part of the compound types.
But many of them are immediately useful: Type can print the full type most of the time, and similarly Interface and its field types, Signature and its field types, Value, ... can all print a lot of useful details, all with the derived Debug implementation and without the need to use the reader to get more info.

Sure, as long as that's understood I have a branch with some refactoring that includes this. Coming soon.


Remove conmon cgroup before pod cgroup for cgroupfs

For pods using cgroupfs, we were seeing some error messages in CI from an inability to remove the pod CGroup, which was traced down to the conmon cgroup still being present as a child. Try to
remove these error messages and ensure successful CGroup deletion by removing the conmon CGroup first, then the pod cgroup.

/approve

@mheon tests aren't too hip.  Other than @rhatdan's comment, LGTM.

Rebased, let's see if CI is fixed

@rhatdan @baude @TomSweeneyRedHat @umohnani8 Anyone mind dropping an LGTM?

LGTM

/lgtm

/retest


Remove version: qBittorrent.qBittorrent version 4.6.7

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-4.6.7/qbittorrent_4.6.7_x64_setup.exe/download
Status Code: 200
(Automated message - build 896)

Close with reason: Package still available.;


infisical: 0.3.7 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/infisical/versions.
meta.description for infisical is: The official Infisical CLI
meta.homepage for infisical is: https://infisical.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.1 with grep in /nix/store/vxg77c7nhdf6gjwmi35yi1pv08s3nrzc-infisical-0.4.1
found 0.4.1 in filename of file in /nix/store/vxg77c7nhdf6gjwmi35yi1pv08s3nrzc-infisical-0.4.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
infisical

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vxg77c7nhdf6gjwmi35yi1pv08s3nrzc-infisical-0.4.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 infisical https://github.com/r-ryantm/nixpkgs/archive/05426c8c4b271b2b9b01b21baa9ab53147198bcd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vxg77c7nhdf6gjwmi35yi1pv08s3nrzc-infisical-0.4.1
ls -la /nix/store/vxg77c7nhdf6gjwmi35yi1pv08s3nrzc-infisical-0.4.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

1 package built:

infisical

Maintainer pings
cc @ivanmoreau for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/infisical/versions.
meta.description for infisical is: The official Infisical CLI
meta.homepage for infisical is: https://infisical.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.2 with grep in /nix/store/pswkl5pzmhy02d8dwgfj80q3ldq6m1w8-infisical-0.4.2
found 0.4.2 in filename of file in /nix/store/pswkl5pzmhy02d8dwgfj80q3ldq6m1w8-infisical-0.4.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
infisical

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pswkl5pzmhy02d8dwgfj80q3ldq6m1w8-infisical-0.4.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 infisical https://github.com/r-ryantm/nixpkgs/archive/44cd14f9a79d6c006692eeab06d0cd0cad392431.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pswkl5pzmhy02d8dwgfj80q3ldq6m1w8-infisical-0.4.2
ls -la /nix/store/pswkl5pzmhy02d8dwgfj80q3ldq6m1w8-infisical-0.4.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

1 package built:

infisical

Maintainer pings
cc @ivanmoreau for testing.

Would it be possible to bump it to the last version 0.14.2?


V6 update for MacOS: Intro to RP

@wadepickett  please wrap up what you're doing ASAP. This is your top priority.  ~You won't be able to PR this until #23112 merges, but you can go through it on the Mac before that.~

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

ID: a25bf940-8977-fec4-461b-542a9f550fc8
Version Independent ID: 5492c641-af15-64b8-beaa-ddf511be73e6
Content: Tutorial: Get started with Razor Pages in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/razor-pages-start.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Will start on this as soon as the public preview of VS 2022 for Mac becomes available. Understood it is a top priority,  thanks Rick.

Public preview became available last night.  On this now...


How to remove Chathead from activity?

Thanks for Library. Its great.
I want to remove/disapprear chathead from activity on the TAP of Button. Is it Possible?
What changes i will have to make in code to perform this functionality?
Please reply ASAP. I am in the middle of it.
Thanks in advance.

stopService(new Intent(MyActivity.this, ChatHeadService.class));

Thanks for the reply. I managed it later.
But now I have another issue , if I remove chathead by dragging it into the
removeview which is at bottom, how should I notify my activity that chat
head has been removed explicitly??
Please help me out with this.
Thanks.
On 10-Mar-2017 9:48 PM, "Henry Chuang"<EMAIL_ADDRESS>wrote:

stopService(new Intent(MyActivity.this, ChatHeadService.class));
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/henrychuangtw/Android-ChatHead/issues/13#issuecomment-285712320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYv9ZFe6FPh737QkwQJF0XF_ZGvzoUxHks5rkXfHgaJpZM4MZEgH
.

Good question, write a callback listener when stopping chathead


Starting Points of Animations

Is it possible to have starting points for the animations?  for example, if I'm using the "jelly" preset, the animated elements animation starts at coordinates center center.  Can I change them to start top left for example. x:0 and y:0?

You can always set the transform-origin (https://developer.mozilla.org/en-US/docs/Web/CSS/transform-origin) on your element to change this.

yup, that works, thanks

:+1:


option htmlroot missing?

The option htmlroot supported by gulp-uncss seems to be missing.
It is required for proper processing of relative links to javascript code within the html files.

AFAIK, it's supported, just not documented.

Thank you for the fast reply @RyanZim! I could not get htmlroot it working in my enviroment. Could you provide a minimal example for gulp?


Support multiple content types

Currently only application/json is provided for, we should come up with a design that makes content types pluggable and implement provision of multiple content types in order of specified preference.

It's pretty strait forward to add content negotiation to the controller. The problem is to bring custom defined body parsers into the scope.
So basically, the issue is as following:

Content negotiation is something which should happen behind scenes, therefore it should be done in controller_base, not the controller itself
The controller_base completely regenerated each time specification is changed. There is no hand-written code in the controller_base
For content negotiation to work we might need to have custom (de)serialisers in scope
We cannot place them into the package object because it's already used to place PathBinders, QueryBinders and HeaderBinders and also completely generated
So basically it seems like our only option is to have a naming convention for the programmer to place serialisers into some package/object/class/trait/whatever
We then need to analyse which custom serialisers present and generate dynamic imports in the controller_base accordingly, which gives us following questions to answer:

where to place sources for custom serialisers
which infrastructure provide for the programmer to write them
which kind of structure they should be placed into
how to check which serialisers to include where and avoid naming clashes

Would like to discuss this more deeply

Released in 0.1.6


chore(master): release 2.5.1

:robot: I have created a release beep boop
2.5.1 (2024-04-10)
Bug Fixes

add gnupg support for phive (#38) (b7b4218)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/docker-php-dev/releases/tag/v2.5.1 :sunflower:


Ensure correct IE focus when the user clicks outside the focused control. #406

Clicking on another input element when selectize has focus causes it to focus on the body in IE. By calling focus on the target after blurring, the focus event is fired as expected on IE.

@brianreavis Looks like you merged this, then later reverted in 6f409616623b940d41dfdc8576ccd8d7b8346cc5? Can you explain? Related to #406.


Recap of PackageCompiler.jl push

Writing down some info and thoughts that might useful to other Dash component developers that want to support Julia

Release v1.3.1 is the first release which made DashTextareaAutocomplete functional in PackageCompiler compiled apps.
We did so by adding a Artifact.toml to this project (more info on Julia Artifacts here). Julia artifacts only support publicly-available URLs of tarballs as targets, so we tar'ed the min.js and min.js.map files in deps/ in an extra build sub-command. After npm publish, this tarball is then available on unpkg.com e.g. at<EMAIL_ADDRESS>In  postbuild_fixups.sh, we:

include the Pkg.Artifacts module in src/DashTextareaAutocomplete.jl and  addPkg in the Project.toml deps
use the artifact"" string macro to include the tarball content in src/DashTextareaAutocomplete.jl upon initialisation (see https://github.com/etpinard/dash-textarea-autocomplete/pull/21)
update the Artifact.toml specifications accordingly

(along with patching for https://github.com/etpinard/dash-textarea-autocomplete/issues/11)
PR https://github.com/etpinard/dash-textarea-autocomplete/pull/25 may eventually streamline this process a little bit more and perhaps make it more robust as well.
Drawbacks

We can't install DashTextareaAutocomplete before we npm publish (as Pkg.add requires the unpkg.com URL to download the artifact). That is, we can't install a dev version of DashTextareaAutocomplete from e.g. a github URL.
Using RelocatableFolders.jl as demonstrated in https://github.com/etpinard/dash-textarea-autocomplete/pull/20 would fix this problem, but this would perhaps uncover new problems such as adding a 0.x  dependency to DashTextareaAutocomplete and potentially leading to slower performing apps.

Some of the operations in postbuild_fixups.sh are non trivial.
The modifications of src/DashTextareaAutocomplete.jl by the postbuild_fixups.sh script could eventually make their way to dash's dash-generate-components julia component logic. Creating a tarball with min.js and min.js.map files from python wouldn't be too hard either.
But trying to replicate the "update Artifact.toml specifications" step in python might be tricky (can we replicate the behaviour of Tar.tree_hash and sha256 identically in python?) and a bit of a moving target (what if Julia artifacts undergo a breaking change in a future release?). So, I think it would be safer to use a Julia script, but then maybe asking for all Dash component devs to have julia installed to build their components is too much?

Hi, @etpinard , @Felix-Gauthier !
I have been working on a new system for generating/publishing component packages for Julia from Python packages for quite some time. Unfortunately, the work is not going very fast - because my main job takes up a lot of time and working on the current issues of Dash.jl also distracts from this task.
If you have the time and desire - could you check how your package will be generated and whether it will work with PackageCompiler out of the box?
The development version of components generator is here: https://github.com/waralex/DashComponentsBuilder.jl
For more operational communication, you can write to Julia's slack in the #dash channel, or directly to me there (my nickname is waralex)