Add XLIFF log for translation managers

Motivation

At the moment, the translation managers have to manually keep track which XLIFFs they exported/imported and when.
Proposed Solution

Track these events in the CMS and show a list of the past XLIFF actions either below the page tree inside a spoiler (which is collapsed per default) or on an extra page.
Alternatives

Additional Context

We could actually make this part of a larger log functionality. We could, for example, show page edit events, removed pages, etc as well in this log. Do we want to have a log model or do we derive the log from our version keeping of pages? In this case we would probably need to keep track of exported XLIFFs in a new model.

We could actually make this part of a larger log functionality. We could, for example, show page edit events, removed pages, etc as well in this log. Do we want to have a log model or do we derive the log from our version keeping of pages? In this case we would probably need to keep track of exported XLIFFs in a new model.

We could actually make this part of a larger log functionality. We could, for example, show page edit events, removed pages, etc as well in this log. Do we want to have a log model or do we derive the log from our version keeping of pages? In this case we would probably need to keep track of exported XLIFFs in a new model.

Good idea! Moving and deleting pages are events which cannot be derived from our current models, so adding an additional log model with different categories could be reasonable.

We could actually make this part of a larger log functionality. We could, for example, show page edit events, removed pages, etc as well in this log. Do we want to have a log model or do we derive the log from our version keeping of pages? In this case we would probably need to keep track of exported XLIFFs in a new model.

Good idea! Moving and deleting pages are events which cannot be derived from our current models, so adding an additional log model with different categories could be reasonable.


Consider modifying usage of find_packages

Currently, find_packages is used as follows:
packages=find_packages(include=['{{ cookiecutter.project_slug }}']),

If the user creates a package foo and then creates a subpackage foo.bar (i.e. bar is a directory with an __init__.py), then the subpackage needs to be added explicitly to the packages list in setup.py.
I think that this can lead to unexpected consequences. For example, suppose the user forgets to add foo.bar to the package list. All tests will pass locally if they run tox or pytest from the project root directory because foo.bar is on the system path. All tests will pass on CI because the tests are executed from the project directory again. But if an end-user then pip installs the package, import foo.bar will result in an import error because the bar package will not have been installed to site-packages per setup.py. (This just happened to me, and it was impossible to debug until I finally lsed the site-packages directory of the environment I installed my own package to.)
I suggest to consider a slightly different paradigm which is used by Pandas for example.
packages=find_packages(include=['{{ cookiecutter.project_slug }}', '{{ cookiecutter.project_slug }}.*']),

The usual downside to this usage would be that a tests subpackage of foo would be installed, but that is not an issue in this pypackage organization.
Thoughts?

I have been bitten by this. The solution should definitely be merged imho

@bluesurfer thanks for the bump, just created a PR as well.


licence implicite

good morning
I not find what your distributed license games
missing the name of the open source license that you have chosen

It is licensed under the modified BSD 3-clause license:
https://github.com/Keripo/Beats2/blob/master/LICENSE
http://opensource.org/licenses/BSD-3-Clause
~Keripo

It is licensed under the modified BSD 3-clause license:
https://github.com/Keripo/Beats2/blob/master/LICENSE
http://opensource.org/licenses/BSD-3-Clause
~Keripo

tank you
you have to look on the side of f-droid to add your game there (I'll create an article on my blog (hence my question)


proguard-same name and class

Annotation-specified bean name 'i' for bean class [*.service.i] conflicts with existing, non-compatible bean definition of same name and class ;
proguard-maven-plugin: 2.5.3
proguard-core : 7.1.1

Please open an issue with proper information.


TypeScript issue with headless param in puppeteer-core = 22.2.0 and @sparticuz/chromium = 122.0.0

It looks like new puppeteer-core expects boolean or "shell" in the headless param but @sparticuz/chromium used old "chrome-headless-shell".
Is that correct to say that we can just use true instead of chromium.headless if we use Chromium 112+?

Thanks!

Ah, you are right. The PR that this is from is https://github.com/puppeteer/puppeteer/pull/11815. While the description of the PR states chrome-headless-shell, there is another commit that changes it to just shell.


Wording

Change apathy to empathy

My GitHub-fu fails me, this PR is superseded by https://github.com/SQLStreamStore/docs/pull/3


Basic datatypes

List of bugs / issues / popular questions we got during the tutorial:

[ ] Add import math in solution_circle_area() in basic_datatypes and explain that pi is defined there
[ ] #233 - is not clear that quadratic equation expects two results
[ ] solution_number_is_lower_than_0_or_greater_than_100 in the test we check for >=

in the def solution_number_is_even(number: float) -> bool: the input types do not match. It should be number:int

https://docs.python.org/3/library/decimal.html

In the exercise solution_return_first_and_last_element_from_list, the annotated return type is list[float] however the solution checks for a tuple[float, float]. We should make this consistent

popitem does not remove an arbitrary element but the last element inserted into a dict.

For the record: it takes roughly 3 hours to finish the basic datatypes section, so we might want to give students a bit more time for the next tutorial.

From #233: In the basic datatypes notebook, trying to convert a complex number to float raises a TypeError as expected. However, it doesn't print the error to the console unless it is surrounded by a try...except statement.


Example of Python Iteration over pages

This was very helpful if I would just see the example here instead of writing/inventing something, and finding in StackOverflow a better solution and re-write my solution :)
I hope this will be merged and help others who struggle with GitHub API automation.
Why:
just helpful information for the documentation that might help other developers use the API.
What's being changed:
Added  an example in the paging API documentation to help developers work with their code
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@blorby Thanks so much for opening a PR! I'll get this triaged for review ✨


cannot find package "github.com/jaxxstorm/hookpick/cmd"

Hey, just trying to build & test this neat looking tool! Following the README and got stuck at the build step:
cd $GOPATH/src
git clone https://github.com/jaxxstorm/hookpick.git
cd hookpick
curl https://glide.sh/get | sh
glide
go build -o hookpick main.go

    main.go:23:8: cannot find package "github.com/jaxxstorm/hookpick/cmd" in any of:
	[GOPATH]/src/hookpick/vendor/github.com/jaxxstorm/hookpick/cmd (vendor tree)
	[GOROOT]/src/github.com/jaxxstorm/hookpick/cmd (from $GOROOT)
	[GOPATH]/src/github.com/jaxxstorm/hookpick/cmd (from $GOPATH)

This is because main.go imports github.com/jaxxstorm/hookpick/cmd and not ./cmd, right? Should I be building with a different command?
Side note, make build fails too because I don't have goxc installed, this will be the next issue to solve.

It's because your git clone isn't right. Try this:
mkdir -p $GOPATH/src/github.com/jaxxstorm
cd $GOPATH/src/github.com/jaxxstorm
git clone https://github.com/jaxxstorm/hookpick.git

and go from there

I opened #21 to fix the goxc thing, bear with me

No sweat dude - thanks for the fast response!
Directory moving worked like a charm, thanks so much 🎉


Removes trailing whitespace from source files.

Some (pedantic) editors display trailing whitespace, which is distracting.

Very good change!
The trailing whitespace rule was disabled in .swiftlint.yml, I will merge and re-enable the rule.


iOS and Android handle form-uurlencoded requests differently

Describe the bug
iOS and Android handle form-uurlencoded requests differently. I believe the intent is to require the data property to be an object when making a the request, but that's not enforced on the JavaScript side. At the iOS layer, if the data property is a string, it's sent straight though; Android, on the other hand, expects it to be an object, and throws an exception if it's not.
To Reproduce
Make a call to Http.request() like so:
const response = await Http.request(
{
  "url":"https://foo.com",
  "method":"POST",
  "headers":{"Accept":"application/json","Content-Type":"application/x-www-form-urlencoded"},
  "data":"a=b&b=c&c=d"
}

Expected behavior
The behavior should be the same on both Android and iOS. If the intention is that form requests must have data specified as an object, then both platforms should throw an exception. Otherwise, both should expect a raw string.
Smartphone (please complete the following information):

Device: iPhone 11 Pro
OS:  iOS 15.5
Browser [Capacitor web view]
Simulator

Smartphone (please complete the following information):

Device: Android Pixel 4
OS:   API 30
Browser [Capacitor web view]
Simulator

Additional context
Relevant Swift code: https://github.com/capacitor-community/http/blob/3aca516560653349bd6f563b0d6c668e20827e03/ios/Plugin/CapacitorUrlRequest.swift#L100
Relevant Java code: https://github.com/capacitor-community/http/blob/3aca516560653349bd6f563b0d6c668e20827e03/android/src/main/java/com/getcapacitor/plugin/http/CapacitorHttpUrlConnection.java#L193
Clearly the workaround here is to just pass an object, but fixing this would save folks time!

Thank you so much for reporting this issue! I have been banging my head for the last couple of days on the issue why my oauth2 flow would not complete. It was because the code exchange fails on Android, which is a form-urlencoded POST request.
Fixing the data from a string to an object does the trick. Again, thank you!

@thomaux you're very welcome! I lost a lot of time with this one, too!


temporarily revert root build.gradle back to groovy

The publish task is not working and I'm not familiar enough with the Kotlin DSL to immediately debug.

Could you please paste the log here? @shashachu


Extend python get/set methods

To support reading/writing non-32bit fields:
-64 bit fields
-float fields
-object handle fields
-256bit fields
-list fields

Can you point me to some example how 32-bit fields are currently being read?

The python function for getting 32bit fields is here:
.text:100B2F60 PyObj_Obj_Get_Int proc near             ; DATA XREF: .data:102CF06Co
.text:100B2F60
.text:100B2F60 nFieldIdx       = dword ptr -4
.text:100B2F60 pCaller         = dword ptr  4
.text:100B2F60 pPyTupleIn      = dword ptr  8
Internally it uses the function
.text:1009E1D0 ; int __cdecl Obj_Get_Internal_Field_32bit_Int(ObjHndl, _nFieldIdx)
(that's a wrapper or something like that, no?)
There's a whole bunch of Obj_Get_XXXX functions that should be similarly exposed.

This is mostly done, though I'd like to add a generic variant for Set_IdxField_byValue to support vararg


Placed marker color and size input controls side by side

thank you. I could not figure out how to put those side-by-side.


Fixed script tag formatting in clones.md

Fixed script tag in clones.md to properly format and indent snippet.
Signed-off-by: Nicholas Huver<EMAIL_ADDRESS>

Signed-off-by: Nicholas Huber<EMAIL_ADDRESS>


Fix Gear Icon on Display

Describe the bug
The gear icon on the display always shows "neutral," even when we plug in forward to 5V.
To Reproduce
This occurred while testing on master with the full test rig set up.
Expected behavior
We expected the gear icon to switch to neutral.
Additional context
We weren't able to test while connected to BPS since BPS was faulting, so we don't know if that could affect things.

Fixed by bb76451 on production/M2 by fixing FSM logic in SendTritium. Not merged into master yet, but @IshDeshpa maybe we can still close this now?


setget is no longer working

Godot version:
3.1.2 >
OS/device including version:
Linux
Issue description:
setget command is no longer working, the value of var is correctly changing but the set function is not called.
Steps to reproduce:
var is_active : = false setget set_active, get_active

func _ready():
	is_active = true
	print(is_active)

func set_active(value : bool) -> void:
        print("test")
	is_active = value

func get_active() -> bool:
	return is_active

This is where self comes into play. From within the script, if you want the setter to be called when setting the property, use self.is_active = value, or set_active(value).

no sorry, this is my fault! This is also written in the documentation, I totally missed it!

no sorry, this is my fault! This is also written in the documentation, I totally missed it!


When Pill resizes the close icon should stick to the end

Package name(s)
Core (@salt-ds/core)
Package version(s)
Description
When Pill resizes the close icon should stick to the end, currently it's not.
Tasks

[ ] Figma (Salt 1) to provide example/guidance to achieve alternative resize behaviour
[ ] Code

Steps to reproduce

Go to https://saltdesignsystem-git-list-box-fed-team.vercel.app/salt/components/pill/examples#closable
Manually re-size the pill with CSS

Expected behavior
When Pill resizes the close icon should stick to the end

Operating system

[ ] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

looks like it is a documentation issue, it's missing justify in the closable examples.


Trouble with Music Details

Yo! I just got it up and running on my mac (i'm on M1), and it's showing me this:

any idea how i could fix this?

Yo! I just got it up and running on my mac (i'm on M1), and it's showing me this:

any idea how i could fix this?

i dunno if it's supposed to show like that, but i probably did something wrong. Can't see the music details

Hello! Can you tell me what song you were listening and, while playing this song, send me the result of the execution in Terminal of osascript -e "tell application \"Music\"" -e "get properties of current track" -e "end tell"

It was happening with all of the songs i was listening to at the time. I started playing my playlist and executed the command in terminal, and it shows 29:39: execution error: Music got an error: Can’t get properties of current track. (-1728)

Mmmh that's odd. Can you retry with a local track (not Apple Music) if it wasn't the case? If it was, it looks like the provided Apple Script interface that my script relies on is to be blamed here :/

tried it with a song on my computer, and it works just fine! I guess it cant get the info from songs on the actual streaming platform

Ok so I guess we run into the same limitation i described here https://github.com/NextFire/apple-music-discord-rpc/issues/1#issuecomment-748795840, I should update the README to acknowledge this limitation

See #4 for further possible developments

oh wait a sec
so I downloaded music from the Apple Music thing into my library, and now it's showing the song?
I guess it cant show stuff that isnt there

Oh well I'm not a Apple Music subscriber, I couldn't test myself haha
Anyway if it does not work well everywhere, it's still a bit broken...


2024-05-20

Meeting with Lewis Alcott from School of Earth Sciences, UoB.
Related issues:

#19

Lewis has offered to run the simulations in Matlab and provide the output data used to make the plots.


Add speedy deletion feature

What is the user problem or growth opportunity you want to see solved?
No response
How do you know that this problem exists today? Why is this important?
No response
Who will benefit from it?
No response
Anything else you would like to add?
No response

Note: Such a feature should be limited to experienced users.

**The evolution of the brain, the heart, the soul **
- [ ] - @nicolas-raoul ґ~~~~


C# Intellisense is not working

Issue Type: Bug
Intellisense is not working for C# version 'ms-vscode.csharp-1.19.0' and
it is working prefectlly with version 'ms-vscode.csharp-1.18.0'.
Extension version: 1.19.0
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3392)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.80GB (8.19GB free)

Process Argv
--folder-uri file:///c%3A/Users/ng79110/WorkSpace/AirBus/M-T/elec%20ART/WireAutomation

Screen Reader
no

VM
0%

Try installing 1.19.1 from here https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.19.1
The installation instructions are here https://github.com/OmniSharp/omnisharp-vscode/wiki/Installing-Beta-Releases

@filipw that solution did not solve the issue for me on Ubuntu 18.04 LTS

@ArunRaj6 Please share your omnisharp log.

@ArunRaj6 We havent heard from you in a while, so I will close this issue now. Please reopen whenever you have more time.

I have tried to upgrade the version to 1.19.1 but, its ask me to install another version of .NET also.
Now, I dont want to install an another version of .NET because of some other reason. SO, I downgraded the version to 1.18.0 now it is working fine.

@ArunRaj6 In order to support newer versions of .NET Core 3, 1.19.1 requires .NET Framework 4.7.2. If you want to use a later version of the C# extension at some point you'll need to install 4.7.2.

@rchande Sure, I will update it later.
@rchande  @akshita31 One open question,
Why C# extension tries to install the latest version every time when we re-launch the VSCode?

@ArunRaj6 By default, the extensions in vscode are set to auto-update, hence C# extension also updates to the latest version when it detects an older version.

You can disable that by changing the setting in VSCode.

@akshita31 - the intellisense  is doing me a hard time as well.
It works for some of the projects but don't work for others
I'm with omnisharp 1.19.1 and vscode 1.35
omnisharp log
    Target: e:\Workspaces\ShopLink\ShopLink

OmniSharp server started.
    Path: C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\OmniSharp.exe
    PID: 1892

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Windows 6.2.9200.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 15.0 - "C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild\Current\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to 'C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild\Current\Bin\MSBuild.exe'
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 15.0 - "C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild\Current\Bin"
            CscToolExe = csc.exe
            CscToolPath = C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild\Current\Bin\Roslyn
            MSBuildExtensionsPath = C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild
            MSBuildToolsPath = C:\Users\Dekel\.vscode\extensions\ms-vscode.csharp-1.19.1\.omnisharp\1.32.19\.msbuild\Current\Bin
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'e:\Workspaces\ShopLink\ShopLink'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in 'e:\Workspaces\ShopLink\ShopLink'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'e:\Workspaces\ShopLink\ShopLink\MallShopsInformation\MallShopsInformation.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'e:\Workspaces\ShopLink\ShopLink\ShopLink\ShopLink.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'e:\Workspaces\ShopLink\ShopLink'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: e:\Workspaces\ShopLink\ShopLink\MallShopsInformation\MallShopsInformation.csproj
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location 'e:\Workspaces\ShopLink\ShopLink' on host 16272.
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'e:\Workspaces\ShopLink\ShopLink\MallShopsInformation\MallShopsInformation.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project 'e:\Workspaces\ShopLink\ShopLink\MallShopsInformation\MallShopsInformation.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: e:\Workspaces\ShopLink\ShopLink\ShopLink\ShopLink.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'e:\Workspaces\ShopLink\ShopLink\ShopLink\ShopLink.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project 'e:\Workspaces\ShopLink\ShopLink\ShopLink\ShopLink.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project 'e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: MallShopsInformation
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: ShopLink
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: ShopsDataResourceAccess
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\obj\Debug\netstandard2.0\MallshopResourceAccess.AssemblyInfo.cs added to workspace
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\DbEntity\Revenues.cs added to workspace
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\Infrastructure\DesignTimeDbContextFactoryBase.cs added to workspace
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'e:\Workspaces\ShopLink\ShopLink\ShopsDataResourceAccess\ShopsDataResourceAccess.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: ShopsDataResourceAccess
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\DbEntity\MonthlyRevenues.cs added to workspace
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\Infrastructure\IMallshopDbContext.cs added to workspace
[info]: OmniSharp.OmniSharpWorkspace
        Miscellaneous file: e:\Workspaces\ShopLink\MallShopLink\MallshopResourceAccess\Infrastructure\MallshopDbContext.cs added to workspace


Switch to @segment/analytics-next

Hey Charles 👋
During npm install, there's this message:
<EMAIL_ADDRESS>Security updates will cease on August 31st, 2022. Please use @segment/analytics-next.
Do you think you could switch to the aforementioned module? Your module is great and we would love to use it long term.
Is there anything I can help you with regarding that?

I would probably solve the npm audit issues as well:

I'll have a look at if this is as simple as replacing one package with another, but given I am not on any projects that use Segment at the moment, I don't foresee this being high priority timeline-wise.
PRs are always welcome, but otherwise I'll try to make this change as time permits.

Releasing this now as a 2.0.0 major version bump.
Breaking changes:

Moved @segment/analytics-next from a dependency to a peerDependency, so you'll have to install it yourself alongside the react-segment-analytics module. This allows you to upgrade/patch the @segment/analytics-next module at will.
Removed eventPrefix. If you want event prefixes, I suggest using a custom hook:

import { useSegmentTrack } from 'react-segment-analytics';
function useTrack(eventName, ...args) {
  const track = useSegmentTrack();
  return track(`Prefix ${eventName}`, ...args);
}

I also added the Analytics browser settings and init options as props to the Segment component.


Flags enums generated from Swagger.json have incorrect values

My web-service exposes a [Flags] enum originally defined in C# as:
[Flags]
public enum AnnouncementDismissalTypes : Byte
{
	/// The announcement cannot be dismissed.
	None = 0,

	/// The announcement will only be shown to a user once and never again. Users may opt-in to receive the announcement again if <see cref="AllowReminder"/> is set.
	AllowAutomaticDismissal = 1,

	/// The user can permamently dismiss the announcement. The dismissal must be saved in the web-service.
	AllowManualDismissal = 2,

	/// The user can dismiss the announcement for 12 hours or until their next new session. The dismissal may be saved in the web-service but this is not necessary, e.g. if using the user's cookies.
	AllowReminder = 4,

	_All = AllowAutomaticDismissal | AllowManualDismissal | AllowReminder
}

The Swagger.json file generated by NSwag in the ASP.NET Core project describes the enum correctly:
"AnnouncementDismissalTypes": {
      "type": "integer",
      "description": "",
      "x-enumFlags": true,
      "x-enumNames": [
        "None",
        "AllowAutomaticDismissal",
        "AllowManualDismissal",
        "AllowReminder",
        "_All"
      ],
      "enum": [
        0,
        1,
        2,
        4,
        7
      ]
    },

However the NSwag Studio C# client code generator generated this incorrect enum definition:
[System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>)")]
[System.Flags]
public enum AnnouncementDismissalTypes
{
    None = 1,
    AllowAutomaticDismissal = 2,
    AllowManualDismissal = 4,
    AllowReminder = 8,
    _All = 16,
}

Observe how it has recomputed the values for the flags members and disregarded the original enum values from the Swagger file.
Also, I have XML-documentation Swagger help generation enabled, but it doesn't seem to be using the XML documentation for the original enum in Swagger. In fact the Swagger UI page doesn't describe the enum at all (it lists it only as AnnouncementDismissalTypes: integer with [ 0, 1 ] above it for some reason:

The problem is this here:
https://github.com/RicoSuter/NJsonSchema/blob/master/src/NJsonSchema.CodeGeneration.CSharp/Models/EnumTemplateModel.cs#L72
I think we need to check whether value is an integer and just use this otherwise keep the current logic.

I've got a fix, making a PR now.

Hi,
I'm using NSwag.MSBuild version 13.17.0 with NJsonSchema version <IP_ADDRESS> and I have the same problem as above
Example:
TestEnumDto:
type: integer
enum: [1, 2, 4, 5]
x-enumFlags: true
x-enumNames:
- One
- Two
- Four
- CombineOneAndFour
Once generated, CombineOneAndFour becomes 8 and should be 5 to follow enum array
Kr,
Philippe


Fix long time await in ThreadlessExecutor

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #12484 (f9e9bb6) into 3.2 (f951110) will increase coverage by 0.77%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##                3.2   #12484       +/-   ##
=============================================
+ Coverage     68.59%   69.37%    +0.77%
+ Complexity      341        2      -339
=============================================
  Files          3607     1625     -1982
  Lines        167542    67111   -100431
  Branches      27787     9834    -17953
=============================================
- Hits         114930    46560    -68370
+ Misses        42619    16053    -26566
+ Partials       9993     4498     -5495

see 2003 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Release 0.12.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b5acccf). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #149   +/-   ##
=========================================
  Coverage          ?   85.89%
=========================================
  Files             ?        8
  Lines             ?      156
  Branches          ?       24
=========================================
  Hits              ?      134
  Misses            ?       22
  Partials          ?        0

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 b5acccf...e705c52. Read the comment docs.


Full implementation ColorCategoriesStyle

I made several 'small' comments, but overall, the main idea LGTM. (explicit source instantiation with metadata +  source-dependant style functions).
Main points for discussion, with things I miss:

if we're gonna support stats for more than 1 field at the same time (so to allow several combined helpers, eg. color dependant one field and size for other field). I would vote yes.
If we extend the mechanism for the new 'style functions', that makes use of the Source, so they can allow a bigger object (Layer).

With probably a bit less of urgency / relevance now:

to give the source methods a bit more of cohesion (getFieldStats, getGeometryType, etc.) with the use inside of an intermediate Metadata class. The idea is, instead of having smaller 'pieces of state' in the source class, we have a big chunk (this._metadata), updated after instantiation, and the rest of them are functions, extracting pieces from it (eg urls) or calculating (eg from stats)

I agree with the three comments @VictorVelarde. Let's do it, they're not hard right now and they will be hard in the future.

What I don't agree is to adapt to CammelCase the fields of the API. I like the idea to keep them as they are at the API and it requires no extra effort 😄

Completed the implementation of the 2/3 points.

If we extend the mechanism for the new 'style functions', that makes use of the Source, so they can allow a bigger object (Layer).

I've not done this, because if we do that we created a circular dependency between Layer and Styles. Maybe we could add in the future a map parameter with the instance of the map instead of the layer. Thoughts?


Uploading PNG causes Willow TypeError

Issue Summary
After uploading a new image, the /admin/images page returns a TypeError: save_as_jpeg() got an unexpected keyword argument 'progressive'

Full traceback here
Steps to Reproduce

Log into the admin site
Go to images and click Add an image
Upload a new image and click back on the Images panel
The error will appear.

I would expect that it would show the list of all images like normal here. When debugging I ran across this:
   463
   464                    import ipdb; ipdb.set_trace
-->465                    return willow.save_as_jpeg(output, quality=quality, progressive=True, optimize=True)
   466                elif output_format == 'png':
ipdb> import pydoc
ipdb> print(pydoc.render_doc(willow.save_as_jpeg).splitlines()[2])
save_as_jpeg(f, quality=85) method of willow.plugins.pillow.PillowImage instance

It looks like the version of willow that is being called does not have the kwargs that this file expects even though I have 0.3.1 installed.
Technical details

Python version: 3.5.2
Django version: 1.10.2
Wagtail version: 1.7
Willow version: 0.3.1
Browser version: Chrome 53 on OS X 10.12

Hi @atelic,
You need to upgrade to Willow 0.4 - Wagtail 1.7 does not support earlier versions of Willow (see https://github.com/torchbox/wagtail/blob/master/setup.py#L33).

Thanks, @gasman I missed this. Sorry for the noise


fix(tracker): add the option to run tracking outside of angular zone

Fixes #60

Adds an option in configs to run the tracker outside of angular ngZone

Tests are broken though I have very little experience with those and the fix did not appeared to be obvious.

Thanks for the PR @Arrakis-Lux
You can add some tests like that:
Index: projects/tracker/src/lib/matomo-tracker.service.spec.ts
<+>UTF-8
===================================================================
diff --git a/projects/tracker/src/lib/matomo-tracker.service.spec.ts b/projects/tracker/src/lib/matomo-tracker.service.spec.ts
--- a/projects/tracker/src/lib/matomo-tracker.service.spec.ts	(revision 736dd3637ced5f88bd2451d648dee85ed3b18e45)
+++ b/projects/tracker/src/lib/matomo-tracker.service.spec.ts	(date<PHONE_NUMBER>568)
@@ -1,3 +1,4 @@
+import { NgZone } from '@angular/core';
 import { InternalMatomoConfiguration } from './configuration';
 import { MatomoHolder } from './holder';
 import {
@@ -15,8 +16,16 @@
 const PLATFORM_SERVER_ID = 'server';

 describe('MatomoTracker', () => {
-  function createTracker(disabled = false, platform: Object = PLATFORM_BROWSER_ID): MatomoTracker {
-    return createMatomoTracker({ disabled } as InternalMatomoConfiguration, platform);
+  function createMockZone(): jasmine.SpyObj<NgZone> {
+    return jasmine.createSpyObj<NgZone>(['runOutsideAngular']);
+  }
+
+  function createTracker(
+    config: Partial<InternalMatomoConfiguration> = { disabled: false },
+    platform: Object = PLATFORM_BROWSER_ID,
+    ngZone: NgZone = createMockZone()
+  ): MatomoTracker {
+    return createMatomoTracker(config as InternalMatomoConfiguration, platform, ngZone);
   }

   beforeEach(() => {
@@ -632,7 +641,7 @@

   it('should ignore calls when disabled', () => {
     // Given
-    const tracker = createTracker(true);
+    const tracker = createTracker({ disabled: true });
     (window as any)._paq = undefined;

     // Then
@@ -642,7 +651,7 @@

   it('should reject all promises when disabled', done => {
     // Given
-    const tracker = createTracker(true);
+    const tracker = createTracker({ disabled: true });

     // Then
     tracker
@@ -656,7 +665,7 @@

   it('should ignore calls when platform is not browser', () => {
     // Given
-    const tracker = createTracker(false, PLATFORM_SERVER_ID);
+    const tracker = createTracker({ disabled: false }, PLATFORM_SERVER_ID);
     (window as any)._paq = undefined;

     // Then
@@ -666,7 +675,7 @@

   it('should reject all promises when platform is not browser', done => {
     // Given
-    const tracker = createTracker(false, PLATFORM_SERVER_ID);
+    const tracker = createTracker({ disabled: false }, PLATFORM_SERVER_ID);

     // Then
     tracker
@@ -677,4 +686,23 @@
         done();
       });
   });
+
+  it('should run commands outside Angular Zone', () => {
+    // Given
+    const zone = createMockZone();
+    const tracker = createTracker({ runOutsideAngularZone: true }, PLATFORM_BROWSER_ID, zone);
+    let runOutside = false;
+
+    zone.runOutsideAngular.and.callFake(fn => {
+      runOutside = true;
+      return fn();
+    });
+
+    // When
+    tracker.ping();
+
+    // Then
+    expect(runOutside).toBeTrue();
+    expect(window._paq).toEqual([['ping']]);
+  });
 });

Hey there !
Hope you had a nice evening !
Just added the suggered tests (thanks for that :p I really need to work on this aspect ^-^)
Also updated the configuration documentation. I am not sure about the "Available in manual mode" part though.

@Arrakis-Lux Thank you, looks good to me!
Maybe we can do some optimization in the future, but we can keep it as-is for a first opt-in fix.
This fix might become a default in a future version of the lib. For that reason, please let us know any feedback in this PR or in a new issue!

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

v4.0.1
GitHub release

Your semantic-release bot :package::rocket:

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

v4.0.1
GitHub release

Your semantic-release bot :package::rocket:


Outline needed API test cases to increase dependabot confidence

Problem

We need to determine which test cases we need to increase our confidence of merging Dependabot PRs. Is our current coverage sufficient? What are we missing?

@dhruvkb this was previously something you volunteered to do; do you think it's still necessary, or have we had enough success with dependabot that we can merge this? The recent addition of the smoke test in #723 seems like a step in the right direction 😄

There is still significant scope for us to improve our tests. I'd recommend keeping the issue open and in the Backlog.


Docs for vagga installation on Arch Linux

Installation of vagga using AUR packages is documented

Nice. But do you always need to add user to subuid/subgid? I think for users that created with new "shadow" package, subuid and subgid are filled automatically, just like in ubuntu. Am I right?

Looks like you're right, will update doc

Merged. Thanks!


feat(alerting): Add AWS SES Alerting Provider

Summary

Added support for SES.
Checklist

[x] Tested and/or added tests to validate that the changes work as intended, if applicable.
[x] Updated documentation in README.md, if applicable.

@TwiN Updated.

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

Comparison is base (4dea597) 79.98% compared to head (6d651e8) 79.15%.
 Consider uploading reports for the commit d84932c to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #579      +/-   ##
==========================================
- Coverage   79.98%   79.15%   -0.84%
==========================================
  Files          56       57       +1
  Lines        4476     4576     +100
==========================================
+ Hits         3580     3622      +42
- Misses        715      773      +58
  Partials      181      181

Files
Coverage Δ

alerting/provider/provider.go
100.00% <ø> (ø)

config/config.go
75.10% <100.00%> (+0.10%)
:arrow_up:

alerting/provider/aws-ses/aws-ses.go
41.41% <41.41%> (ø)

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

@beschoenen Can you resolve the conflict? Once it's resolved, I'll merge.

@TwiN Should be all good now!

Thank you for the contribution!


Add spotify current track

Use the Spotify API to add current playing track

Can I take this issue ?

Assigned.


Mpr121 configAN3944 CDT register has invalid value

in  configAN3944 the CDT register is set to 0x04 which is an invalid value. Consequences are:

lock-in of the sensor to "touched" state when touched for long periods of time ( > 10 seconds)
lock-in sensor  to "touched" state when left alone for more than an hour

The CDT part of register 0x5D (Highest 3 bits) should at least be set to 001 as indicated in the Application Note AN3889 , as you can see from the below screenshot of the application note:

in the current configAN3944 the highest 3 bits of 0x5D are set to 000 which is invalid.

Thanks for pointing this out, we will change the default value to 0x24 to match the datasheet.
Have you tried to use the writeBytes() function to input a valid value for the configuration register? It would be nice to know that solves this issue.

Fixed by b257d91702045dce8b3364f3e2ed70e213f8eeae. Thanks!


Fix clicking january from december in materialcalendarview

If there is a MaterialCalendarView that has the setting setAllowClickDaysOutsideCurrentMonth(true) set, and the calendar shows December, if you click a date in January it goes back to November. I have coded up a fix but I do not have push permission to make a PR. This is on year boundaries, since the month 11 (december) is greater than the month 0 (january) it was going back a month instead of forward a month.
Cheers,
Brian

I would like to see this get checked in ASAP as well.
Thanks

This is issue #374 , I did a similar fix in pull request #376 several months ago. But no pull request is merged in this repository for several months.

Thank you for your solution, I refactored it a bit and will merge using this one #425.
Closing this one for now


41 android project

Closes ichi-go/ichi-go-project-tracker#41. Note that this does not connect to an emulator right now... I couldn't get it to build otherwise. I suspect that is because there is no code... So maybe when we get content into the project we can get things working.
Regardless, when code is added, we are going to add unit tests somehow...

All is well


[BEAM-3601] Switch to Java 8 futures

This ports the Beam codebase from Guava futures to Java 8 futures. This has been discussed at length on the Beam dev list.
The standards that I have held:

Consumers of futures use CompletionStage. They can do async chaining and can use MoreFutures.get(...) to get the result without passing through types they shouldn't be touching.
Producers of futures use CompletableFuture and return it as a CompletionStage.
When you need to handle exceptions in a reasonable way, use MoreFutures helpers that will complete things exceptionally based on the underlying function throwing.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.

[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

So many mocks ;_;

Requested reviews from just a couple folks in the right arenas rather than targeting the authors of every touched piece of code.

run java gradle precommit


Public and Private Access

Can an Azure Database for PostgreSQL server resource have both public and private access enabled simultaneously? We'd like to move to private endpoints but would like to minimize impact to clients so, only disable public access once all clients have been moved over to the private endpoint.
Thanks for any help!

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

ID: 9dfacd9d-6903-1cd0-2db7-110b70e14d3b
Version Independent ID: 4c3e1d9f-ba8e-5dfd-8dd9-f1695456775f
Content: Networking overview - Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/concepts-networking.md
Service: postgresql
GitHub Login: @niklarin
Microsoft Alias: nlarin

@jsoncoen Thank you for your feedback. We will investigate and update the thread further.

Hi @jsoncoen We don't allow public and private access at the same time in the Flexible server. So you need to prepare for switching to private access, i.e. be ready to change the connection string in your app, etc., and once ready do it.

We will proceed to close this issue now.
If there are further questions regarding this, please comment and we will gladly continue the discussion.


Optimisation: mycelial init --local re-downloads the binaries on 2.nd execution, this can (should?) be avoided

First of all: existed to try out the mycelial release!
I was aware of the project for over 1 year already, but just assumed, it has slowly died, like many other open source alternatives.
So: congratulations on this quite interesting approach, I think there is a lot of potential behind it. I'm also quite suprised that the HN crowd mostly ignored the release announcement, please ignore the silence and continue on iterating, you have something quite unique there. Especially when considering simplifying MQTT / event-driven architectures.
So, within 3 minutes into trying the new release I have notices, that on repeated  mycelial init --local the binaries are re-downloaded, I think this is not necessary.
Looking forward to play with mycelial more in my spare time.

Thank you so so much for the kind words, @mindreframer! Please do let us know your thoughts!!


Support for MySQL 5.7+ and PHP 7.0

I see Box Billing isn't available yet for PHP 7 and MySQL 5.7+ support. So, I would like to request the developers to have a look at it too.
Thanks !

Wish this project was brought back to life...

Maybe a Team should fork this

Hi,
you don't have to update much, I think. I have changes bb to use it with version 7.1.
If you found any error, please write back - I will fix it soon.
Just change : bb-load.php:
function handler_exception(Exception $e)

to
function handler_exception($e)

and: bb-libary/Box/Crypt.php:
<?php
/**
 * BoxBilling
 *
 * @copyright BoxBilling, Inc (http://www.boxbilling.com)
 * @license   Apache-2.0
 *
 * Copyright BoxBilling, Inc
 * This source file is subject to the Apache-2.0 License that is bundled
 * with this source code in the file LICENSE
 */

class Box_Crypt implements \Box\InjectionAwareInterface
{
    const CRYPT_MODE = 'AES-128-CBC';

    protected $di = NULL;

    public function __construct()
    {
        if (!extension_loaded('openssl')) {
            throw new Box_Exception('php openssl extension must be enabled on your server');
        }
    }

    /**
     * @param Box_Di $di
     */
    public function setDi($di)
    {
        $this->di = $di;
    }

    /**
     * @return Box_Di
     */
    public function getDi()
    {
        return $this->di;
    }

    /**
     * @param string $text
     * @param string|null $pass
     * @return string
     */
    public function encrypt(string $text, string $pass = null)
    {
        $key = $this->_getSalt($pass);

        $secretHash = md5($key);
        $iv = substr($secretHash, 0, 16);

        $output = openssl_decrypt(base64_decode($text), self::CRYPT_MODE, $key, 0, $iv);

        return $output;
    }

    /**
     * @param string $text
     * @param string|null $pass
     * @return bool|string
     */
    public function decrypt(string $text, string $pass = null)
    {
        if (is_null($text)){
            return false;
        }

        $key = $this->_getSalt($pass);

        $secretHash = md5($key);
        $iv = substr($secretHash, 0, 16);

        return base64_encode(openssl_encrypt($text, self::CRYPT_MODE, $key, 0, $iv));
    }

    /**
     * @param string $pass = null
     * @return string
     */
    private function _getSalt(string $pass = null)
    {
        if (null == $pass) {
            $pass = $this->di['config']['salt'];
        }
        return pack('H*', hash('md5', $pass));
    }
}

It seems that the install script cannot work with PHP7 because it uses the removed mysql_connect() function etc.

 Also. And I believe that one of the mechanisms/framework TWIG is the main responsible for this failure..
Its technology is good but at the same time very sensible


what is the usage of buffer = vr.get_batch(index).asnumpy() when using decord to read frames?

Dear all:
the buffer is really confusing. anyone would kindly illustrate it?

To get multiple frames at once, use get_batch this is the efficient way to obtain a long list of frames.  Perhaps with decord.bridge.set_bridge('torch') could be a more efficient data pre-process method.

To get multiple frames at once, use get_batch this is the efficient way to obtain a long list of frames. Perhaps with decord.bridge.set_bridge('torch') could be a more efficient data pre-process method.

hi, but my question is not get_batch to obtains several frames meanwhile. My question is: buffer = vr.get_batch(index).asnumpy() the buffer tensor is never used. why use buffer before images_group?

Sorry for just realizing that this was a duplicate block that wasn't removed during code cleanup. It has been corrected, and indeed, that data block wasn't utilized.
https://github.com/OpenGVLab/Ask-Anything/blob/d6ec28c157241867fcef80c44cdf4b732ca8b8ad/video_chat2/conversation.py#L96-L118

thanks for your responsible work.


fixed #13

Fails when trying to insert comments above attributes

[Route("{time}/{location}")]
[HttpGet]
public async Task<string> GetInfoForTime(string location, double time)

Coverage decreased (-4.5%) to 44.186% when pulling 691addec6e79b5f856c727067faeb799be7971b2 on fix/#13 into 56e5d64804426df344ce8679499e2f4e40ebc475 on master.

Coverage increased (+4.8%) to 53.488% when pulling 3a2f462926baffda77a62609610ce1e9619c6c41 on fix/#13 into 56e5d64804426df344ce8679499e2f4e40ebc475 on master.


Suggestion & Bug

I use it in our two project, some suggestions below:

Custom configuration: such as: color of task title, color of progress bar.

The different color can help us to distinguish different status of task.

Popup blocked by scrollbar.

Thank for your reply and update.

Really need these configurations in our project to make it more intuitive.

Send pr in #12 .

#14


Explicitly call out that the UI is installed with InfluxDB 2.x

The UI is part of the overall InfluxDB install.  Add wording that to access the UI you need:

influx daemon running  - start by typing influxd at the command line
go to http://localhost:8086/ in your browser to access the UI

add to the following docs:
https://docs.influxdata.com/influxdb/v2.4/visualize-data/
https://docs.influxdata.com/influxdb/v2.3/visualize-data/

Kelly already has an issue open:
https://github.com/influxdata/docs-v2/issues/4494
will close this out


Sticky JS does not work on Mobile

Sticky JS does not work on iOS 10.2. I tested on Chrome and Safari and the sticky header does not follow when I scroll. It works fine on desktop.
Any ideas?

I had disabled mine on mobile devices, It worked out better that way.
After fiddling with JS for an hour(because I suck at it), I got it to disable.
https://gist.github.com/sid-engel/996c1fd5d18e1c711dc7551d97982fb1
It properly enables/disables it, upon page resize, and load... Unlike any other solution I had found.


The LHS and RHS are swapped incorrectly when assign a subtype to a generic type

🔎 Search Terms
failed to assign a subtype to a base type
The LHS and RHS are swapped incorrectly
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
No response
💻 Code
// Your code here

import { createApi, fetchBaseQuery } from '@reduxjs/toolkit/query/react'
const mySlice = createApi({
reducerPath: 'myReducer',
baseQuery: fetchBaseQuery({
baseUrl: 'bbb',
}),
endpoints: (builder) => ({}),
})
const newSlice: ReturnType = mySlice
🙁 Actual behavior
test.ts:31:7 - error TS2322: Type 'Api<BaseQueryFn<string | FetchArgs, unknown, FetchBaseQueryError, {}, FetchBaseQueryMeta>, {}, "myReducer", never, unique symbol | unique symbol>' is not assignable to type 'Api<BaseQueryFn<any, unknown, unknown, {}, {}>, EndpointDefinitions, string, string, unique symbol | unique symbol>'.
  Type 'Api<BaseQueryFn<string | FetchArgs, unknown, FetchBaseQueryError, {}, FetchBaseQueryMeta>, {}, "myReducer", never, unique symbol | unique symbol>' is not assignable to type '{ reducerPath: string; internalActions: InternalActions; reducer: Reducer<CombinedState<EndpointDefinitions, string, string>, AnyAction>; middleware: Middleware<...>; util: { ...; }; endpoints: { ...; }; }'.
    Types of property 'reducer' are incompatible.
      Type 'Reducer<CombinedState<{}, never, "myReducer">, AnyAction>' is not assignable to type 'Reducer<CombinedState<EndpointDefinitions, string, string>, AnyAction>'.
        Types of parameters 'state' and 'state' are incompatible.
          Type 'CombinedState<EndpointDefinitions, string, string> | undefined' is not assignable to type 'CombinedState<{}, never, "myReducer"> | undefined'.
            Type 'CombinedState<EndpointDefinitions, string, string>' is not assignable to type 'CombinedState<{}, never, "myReducer">'.
              Types of property 'config' are incompatible.
                Type 'ConfigState<string>' is not assignable to type 'ConfigState<"myReducer">'.
                  Type 'ConfigState<string>' is not assignable to type '{ reducerPath: "myReducer"; online: boolean; focused: boolean; middlewareRegistered: boolean | "conflict"; }'.

31 const newSlice: ReturnType<typeof createApi> = mySlice
         ~~~~~~~~

Found 1 error.

This line shows that "myReducer" is not assignable to "string":
Type 'Reducer<CombinedState<{}, never, "myReducer">, AnyAction>' is not assignable to type 'Reducer<CombinedState<EndpointDefinitions, string, string>, AnyAction>'.
But the error inside swapped their positions which cause the problem:
Type 'ConfigState<string>' is not assignable to type 'ConfigState<"myReducer">'.
🙂 Expected behavior
Literal string type should be assignable to string type.
Additional information about the issue
No response

Caveat - I'm not a member of the TS team, just trying to help triage:
This isn't really a properly submitted bug report (no playground link, depends on external libraries, etc) so it's hard to know for sure, but I assume this is just contravariance of function parameters and therefore working as intended.  See the docs for --strictFunctionTypes and the definition of contravariance.  If you still think there's a bug, then please edit this report so it provides the information as requested.  Otherwise, it would be helpful for you to close the issue yourself so that the TS team doesn't need to spend their time on it.


Schemas: Support for arrays

Description
Adds ux for properties of type: 'array'. Uses the new PDraggableList component from prefect-design. Can add, re-order, and delete items from an array. Supports all features of schema properties.
Using this example flow
class User(BaseModel):
    name: str
    age: int
    birthday: date

@flow
def schema_testing(list: List[User], names: List[str]):

Produces this UI

Currently the user is only given a json input (same flow)

@znicholasbrown

Can delete buttons use the small button type instead of regular? they're huge atm

I agree. Though that will turn into a menu so I'll play with the layout/sizing once the ux is more final

Would like to see a better UX around empty lists besides just the add item button, it's a little confusing as-is. When a list is empty can we have some placeholder subdued (maybe even italicized?) text that says something like "{{property.title}} is empty"

@brandonreid I'd love to see some exploration around this. I thought about putting an empty item in the list but we've had some reports of schemas with circular references and automatically putting things in lists is one way that happens. But maybe won't be an issue?


[cleanup][broker] remove unused method getTotalServiceUnitsLoaded

Motivation
remove unused method getTotalServiceUnitsLoaded.


Use a transparent color when setting fill/stroke colors in a pattern context but with no colorspace

/botio test

/botio test

/botio test

There is a regression in issue6707.pdf.
It's due to the fact we've a previous valid colorspace which is not replaced by the default gray one.
On master, I just applied this diff:
diff --git a/src/core/colorspace.js b/src/core/colorspace.js
index 74b43a1c4..ee2e8493c 100644
--- a/src/core/colorspace.js
+++ b/src/core/colorspace.js
@@ -396,7 +396,8 @@ class ColorSpace {
               }
             }
           }
-          throw new FormatError(`Unrecognized ColorSpace: ${cs.name}`);
+          return this.singletons.gray;
+          //throw new FormatError(`Unrecognized ColorSpace: ${cs.name}`);
       }
     }
     if (Array.isArray(cs)) {

and interestingly the above pdf shows stuff which was invisible before.
I know this pdf is a bit corrupted, but I do wonder if instead of throwing in ColorSpace::_parse when we've a wrong cs we could fallback on DeviceGray.
In the last months, we removed few throw ... to just fallback on something (or sometimes just to do nothing), maybe we could do the same here.
@Snuffleupagus wdyt ?

I know this pdf is a bit corrupted, but I do wonder if instead of throwing in ColorSpace::_parse when we've a wrong cs we could fallback on DeviceGray.

Without testing I really don't know what the general effect would be if we change all the relevant cases in that method to just "swallow" errors, since it might "fix" some things and break others.
Maybe we should just update this patch to address the referenced issue, without regressing anything, and then we could look into those ideas in a follow-up instead to reduce the number of "moving parts" in this PR?

/botio test

/botio makeref


TypeScript Strict Mode: set noImplicitAny to true

This will improve the quality of our source code a lot.

All done.


Do not encode pubsub message for gRPC requests.

Protobuf encodes pubsub messages, and google-cloud-python did as well which resulted in a double encoding of the message when protobuf was in use.
Fixes: #2577

If there's a better way to pass _USE_GAX on to Topic let me know. I'm not sure I like this path.

I believe this also needs a complementary change on the pull/b64decode side

I believe this also needs a complementary change on the pull/b64decode side

@ericbuehl Yep, you are correct.  @daspecster, you can verify by running the pubsub system tests:  the "end-to-end" test will fail if @ericbuehl is correct.

Bingo!
Also referenced here.

@daspecster: High level question, why were so many new tests needed?

They're mostly to cover the branch for if 'data' in.... and with/without gax. There's only three though, and if you think I can get rid of one LMK.

@daspecster If you make a helper, you only have to cover the branch in your helper.

@dhermes I commented about the helper. Maybe you know a better way to do it?

Gahhh...this didn't auto refresh....I see your comment not. I follow.

@dhermes, I think I covered what you mentioned. LMK if I missed understood anything.
@tseaver LMK if you have anything else.

@daspecster Other than that tiny nit I don't have any other requested changes.
I do however still feel very unsure if we are correctly handling users passing bytes / unicode in this method.

@daspecster OK I have it figured out now. Before:

_PublisherAPI.topic_publish did nothing (data = {'messages': messages}). Since json.dumps() fails with bytes (in Python 3), this essentially assumes the data passed in was unicode.
Batch.publish and Topic.publish went to base64 and to unicode (base64.b64encode(message).decode('ascii')). This also effectively required message to be bytes (see below the behavior)
Subscription.pull (via Message.from_api_repr) converts the message data from base64 to bytes

Now:

Topic.publish does nothing to the message (message_data = {'data': message, 'attributes': attrs}) but Batch.publish makes sure it is unicode (_bytes_to_unicode(message))
_PublisherAPI.topic_publish manually encodes each message to base64 (for HTTP), which still is an effective check for bytes but transform(message['data']) is missed the cast to unicode (the GAX case also checks bytes since it goes into a BytesField)
_PublisherAPI.subscription_pull (for HTTP) manually converts from base64 back to bytes (the GAX version does something similar), note here that transform() does the right thing, i.e. bytes
Subscription.pull not updated in this PR (but should be)

$ python -c 'import json; print(json.dumps(b"a")); print(json.dumps(u"D"))'
"a"
"D"
$ python3 -c 'import json; print(json.dumps(b"a")); print(json.dumps(u"D"))'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.5/json/__init__.py", line 230, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python3.5/json/encoder.py", line 198, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.5/json/encoder.py", line 179, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: b'a' is not JSON serializable

$ python -c 'import base64; print(base64.b64encode(b"X")); print(base64.b64encode(u"Y"))'
WA==
WQ==
$ python3 -c 'import base64; print(base64.b64encode(b"X")); print(base64.b64encode(u"Y"))'
b'WA=='
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.5/base64.py", line 59, in b64encode
    encoded = binascii.b2a_base64(s)[:-1]
TypeError: a bytes-like object is required, not 'str'

I should be able to just handle the the bytes conversion in the transform() function right?

I should be able to just handle the the bytes conversion in the transform() function right?

You're better off making a custom transform helper so you don't need to have another branch to deal with in your transform helper.
def _base64_unicode(value):
    """Foo docstring."""
    as_bytes = base64.b64encode(value)
    # _Sadly helpers.bytes_to_unicode() doesn't take encoding as an
    # argument, so don't worry about updating it in this PR
    return as_bytes.decode('ascii')

Subscription.pull is a transport-agnostic method, so it's up to the transports to encode/decode the data. The GAX transport does this according to the proto definition, so we don't have to do anything. The HTTP transport is the only place you need to worry about encoding / decoding.

So what needs to be updated with that?

Rip out all decoding from Message.from_api_repr, it'll be handled fine by the transform() you've already done to the received messages.

Just bytes handling?

Yeah, should all be clear from above

@dhermes LMKWYT.
Subscription.pull should have been covered here right?

LGTM

Thanks @dhermes!
@tseaver is there anything else you had for this?


I cant start my Headless drupal via vagrant up command

Issue Type

Bug Report / Support Request

Your Environment

Vagrant version : Vagrant 2.0.3
Virtual box version: Version 5.2.8 r121009 (Qt5.6.2)

Your OS

Windows (10)

Full console output

D:\drupal_react\decoupledkit-drupal>vagrant up
Bringing machine 'decoupledkit' up with 'virtualbox' provider...
==> decoupledkit: Checking if box 'geerlingguy/ubuntu1604' is up to date...
==> decoupledkit: Clearing any previously set forwarded ports...
==> decoupledkit: Clearing any previously set network interfaces...
==> decoupledkit: Preparing network interfaces based on configuration...
    decoupledkit: Adapter 1: nat
    decoupledkit: Adapter 2: hostonly
==> decoupledkit: Forwarding ports...
    decoupledkit: 22 (guest) => 2222 (host) (adapter 1)
==> decoupledkit: Running 'pre-boot' VM customizations...
==> decoupledkit: Booting VM...
==> decoupledkit: Waiting for machine to boot. This may take a few minutes...
    decoupledkit: SSH address: <IP_ADDRESS>:2222
    decoupledkit: SSH username: vagrant
    decoupledkit: SSH auth method: private key
==> decoupledkit: Machine booted and ready!
[decoupledkit] GuestAdditions versions on your host (5.2.8) and guest (5.2.4) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (<IP_ADDRESS>-2ubuntu11.5).
linux-headers-4.4.0-87-generic is already the newest version (4.4.0-87.110).
The following packages were automatically installed and are no longer required:
  libyaml-0-2 python-cffi-backend python-crypto python-cryptography
  python-ecdsa python-enum34 python-httplib2 python-idna python-ipaddress
  python-jinja2 python-markupsafe python-paramiko python-pkg-resources
  python-pyasn1 python-setuptools python-six python-yaml sshpass
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 102 not upgraded.
Copy iso file C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 5.2.8 - guest version is 5.2.4
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.8 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.4 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
An error occurred during installation of VirtualBox Guest Additions 5.2.8. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> decoupledkit: Checking for guest additions in VM...
==> decoupledkit: [vagrant-hostsupdater] Checking for host entries
==> decoupledkit: [vagrant-hostsupdater] Writing the following entries to (C:/WINDOWS/system32/drivers/etc/hosts)
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  www.local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  adminer.local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  xhprof.local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  pimpmylog.local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater]   <IP_ADDRESS>  dashboard.local.decoupledkit.com  # VAGRANT: b3caf5c85a48b44d807df28819de3ee2 (decoupledkit) / 5d7d4c2b-daac-4933-b7ff-b635084ead81
==> decoupledkit: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-hostsupdater-<IP_ADDRESS>/lib/vagrant-hostsupdater/HostsUpdater.rb:98:in `initialize': Permission denied @ rb_sysopen - C:/WINDOWS/system32/drivers/etc/hosts (Errno::EACCES)
        from C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-hostsupdater-<IP_ADDRESS>/lib/vagrant-hostsupdater/HostsUpdater.rb:98:in `open'
        from C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-hostsupdater-<IP_ADDRESS>/lib/vagrant-hostsupdater/HostsUpdater.rb:98:in `addToHosts'
        from C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-hostsupdater-<IP_ADDRESS>/lib/vagrant-hostsupdater/HostsUpdater.rb:47:in `addHostEntries'
        from C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-hostsupdater-<IP_ADDRESS>/lib/vagrant-hostsupdater/Action/UpdateHosts.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/check_guest_additions.rb:49:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/siddhant.chopra/.vagrant.d/gems/2.4.3/gems/vagrant-vbguest-0.15.1/lib/vagrant-vbguest/middleware.rb:31:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/wait_for_communicator.rb:71:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/boot.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/sane_defaults.rb:38:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/forward_ports.rb:31:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/network_fix_ipv6.rb:41:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/network.rb:123:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:49:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/env_set.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/provision.rb:80:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/call.rb:53:in `call'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/call.rb:53:in `call'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/call.rb:53:in `call'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/box_check_outdated.rb:79:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/call.rb:53:in `call'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builtin/call.rb:53:in `call'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/warden.rb:34:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/action/runner.rb:66:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/machine.rb:227:in `action_raw'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/machine.rb:202:in `block in action'        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:592:in `lock'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/machine.rb:188:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/machine.rb:188:in `action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

Summary

I am learning to work on headless drupal in react. Using vagrant and virtual box but it seems its not opening and i'm stuck. please help

Thank you - "sudo vagrant up" worked on my Mac terminal where I got the following error message:
Line number: 0
Message: Errno::EACCES: Permission denied @ rb_sysopen - /Users/.vagrant.d/gems/2.4.3/cache/vagrant-hostsupdater-<IP_ADDRESS>.gem

@dimitridarras - So is this working if you use sudo to run vagrant commands? Can you see if you're an Administrator on your Mac? See: https://ttlc.intuit.com/questions/1899267-administrator-rights-mac


chore: Switch to Yarn instead of npm

Most of the repos are using Yarn (and most likely we'll switch all of them over time)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create yelling.py

WILL RESPOND TO ANYONE TALKING TOO QUIETLY IN THE #yelling CHANNEL.

retest this please

retest this please

retest this please


When using 'module' to install selinux-module the selinux-mode is set to disabled.

When using 'module' to install selinux module mode is set to disabled. (Probably because ::selinux-class is implicitly loaded by type module.)
Expected was that just installing a module would leave the selinux-mode as-is.
See comment on: https://github.com/jfryman/puppet-selinux/commit/86e9599a7ac25a8f8bd0f8dc2d9665ef3b697bff

I will attempt to fix this problem later this week.

:+1: this confused me greatly and is poor behavior IMO, not to mention undocumented.

This should be changed now :)

this should be fixed already. please re-open if you still see this problem


Improve tests and docs for migrate API

Summary of changes:

Fix some typos from migrate API docs (someone else was faster)
Add a mention about disableTransactions config option
Add descriptions for each config option
Remove mention of config option database (couldn't find out where that would be used, hope I got this right?)
Add basic tape tests for the migrator

Proof-reading the config option descriptions is probably a good idea.
The changes to actual code are sort-of cosmetic, just thought to make it easier to find the config default values. Was thinking of asserting for valid values in setConfig(), but didn't want to start breaking apps which are potentially feeding in invalid/old config values.

Thanks for the PR and I'm really sorry that this hasn't got any attention before (I just stumbled here while cleaning up old stuff).
Code / documentation did look fine to me, would you like to fix conflicts here?

Hi @elhigu,
Whoops, forgot myself that this wasn't merged yet, could've taken an action myself earlier, too. But anyway, I'll take a fresh look at this, I assume most of the changes are valid still (haven't been following changes lately too actively but this is now a good reason to catch up).

@elhigu, PR fixed and good to go as far as I can see, thanks for taking this forward.

Thanks!


RT4265: Fix s_server.c when SRTP is disabled

The srtp_profiles varible is not #ifdef'd out when SRTP is disabled.

is this a dup of #447 ?

Not a dup, but similar. This is an issue in s_server.c. That issue was in bn_srp.c, I believe.

This fix is in master in commit d631602533d2e06f9a7a7645ee66638190e0db54.


Add close method for TopKOperator

Description
No close method may cause memory leak.

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

Comparison is base (2a1fad8) 49.03% compared to head (78735ec) 49.03%.

Files
Patch %
Lines

...ngine/execution/operator/process/TopKOperator.java
87.50%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##             master   #11649   +/-   ##
=========================================
  Coverage     49.03%   49.03%
- Complexity    24913    24917    +4
=========================================
  Files          2815     2815
  Lines        176137   176145    +8
  Branches      21132    21133    +1
=========================================
+ Hits          86360    86381   +21
+ Misses        89777    89764   -13

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


[SPARK-7593][ML] Python Api for ml.feature.Bucketizer

Added ml.feature.Bucketizer to PySpark.
cc @mengxr

Merged build triggered.

Merged build started.

Test build #32629 has started for   PR 6124 at commit 05285be.

Test build #32629 has finished for   PR 6124 at commit 05285be.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DoubleArrayParam(parent: Params, name: String, doc: String, isValid: Array[Double] => Boolean)
class Bucketizer(JavaTransformer, HasInputCol, HasOutputCol):

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

Merged build finished. Test PASSed.

LGTM. Merged into master and branch-1.4. Thanks!


jsagent8 is broken

jsagent8 is the jsagent in jumpscale8.
It still relies on j.dirs.hrdDir which does not exist anymore.
j.application.config behaves in another way then before.

his is pushed on 8.1.1 if we are moving this issue to 8.2.0, then 8.1.1 not 8.1.0
branch has to be rebased/merged  onto 8.2.0

verified on 8.1.1

From controller of any env (which uses js7) try to run jumpscript (ex:echo_async) on jsagent8 (which uses js8)
cmd to run: jsac exec -o jumpscale -n echo_async -nid 7
-o : is the organization


Any chance of adding delete function

Awesome workflow. But sometimes I wanna delete a safari (or chrome) bookmark using alfred. Any possibility?

Nope, no chance I'm afraid. Safari's bookmarks, reading list and history are strictly read-only.
AFAIK, there is no (external) API for editing Safari's bookmarks.

Is there no way you can ammend the read-only bookmarks? Safari can delete the bookmarks from its GUI bookmark manager, perhaps it deletes them by their uid if they have one. Maybe Safari 12.0 changed something.

Is there no way you can ammend the read-only bookmarks?

No. There is no bookmarks API.

Maybe Safari 12.0 changed something.

Why don't you try to find out yourself before asking me?

Why don't you try to find out yourself before asking me?

It was just a note. I can't upgrade to Mojawe yet but will do soon and will certainly try. Deleting bookmarks quickly is still an annoying issue.

Deleting bookmarks quickly is still an annoying issue.

Yes, it is. And as explained when I closed the issue, this workflow does not (and never will) alter Safari's private data.
I suggest you look into Safari Extensions, which do have the ability to manipulate Safari's bookmarks.


[SPARK-27918][SQL][TEST][FOLLOW-UP] Open comment about boolean test.

What changes were proposed in this pull request?
This PR is related to https://github.com/apache/spark/pull/25074 and follow up https://github.com/apache/spark/pull/24767.
How was this patch tested?
N/A

@dongjoon-hyun Could you take a look at this PR?

Can one of the admins verify this patch?

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/testing-k8s-prb-make-spark-distribution-unified/13787/
Test PASSed.

Test build #108702 has started for PR 25366 at commit 9654246.

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/testing-k8s-prb-make-spark-distribution-unified/13788/
Test PASSed.

Test build #108703 has started for PR 25366 at commit 05a14c5.

Test build #108705 has started for PR 25366 at commit 5090742.

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/testing-k8s-prb-make-spark-distribution-unified/13790/
Test PASSed.

Test build #108702 has finished for PR 25366 at commit 9654246.

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/108702/
Test FAILed.

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/testing-k8s-prb-make-spark-distribution-unified/13797/
Test PASSed.

Test build #108712 has started for PR 25366 at commit 7278128.

Test build #108703 has finished for PR 25366 at commit 05a14c5.

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/108703/
Test PASSed.

Test build #108705 has finished for PR 25366 at commit 5090742.

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/108705/
Test PASSed.

Test build #108712 has finished for PR 25366 at commit 7278128.

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/108712/
Test FAILed.

Sure, @beliefer . I'll take a look.  Thank you for pinging me.

@beliefer . Please regenerate the result. That will recover the UT failures.

BTW, @beliefer . This had better be a followup of yours ([SPARK-27924][SQL] Support ANSI SQL Boolean-Predicate syntax). I updated the PR title. Also, I changed How was this patch tested? section. Since you updated the test cases which are verified by Jenkins. It should not be 'N/A'.

I made a PR to you, @beliefer . Please review and merge.

https://github.com/beliefer/spark/pull/2

Does https://github.com/apache/spark/pull/25357 afffects the output in this pr? If so, I think we'd be better to merge that pr first to make code changes less.

BTW, @beliefer . This had better be a followup of yours ([SPARK-27924][SQL] Support ANSI SQL Boolean-Predicate syntax). I updated the PR title. Also, I changed How was this patch tested? section. Since you updated the test cases which are verified by Jenkins. It should not be 'N/A'.

Thank you very much!

I made a PR to you, @beliefer . Please review and merge.

beliefer#2

Thanks for your help! It's my mistake. I forget something.

Test build #108741 has started for PR 25366 at commit 30ed8d3.

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/testing-k8s-prb-make-spark-distribution-unified/13822/
Test PASSed.

Test build #108741 has finished for PR 25366 at commit 30ed8d3.

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/108741/
Test PASSed.

@maropu . IMO, we need more review on #25357 ~ I'll comment on that PR.

@dongjoon-hyun  Thanks for your help, review and work!


Have #DigtialNepal as hashtag on the website

amit - can we reactivate the section where we can show the #DigitalNepal as hashtag. The hashtag can be linked to this? https://twitter.com/search?q=%23digitalnepal&src=typd

@ravinepal Actually, we had deactivated the section because it no longer works. This was discussed the last time. Our theme based on zeppelin used their own server to fetch the tweets. I'll do some research and see if there is any alternative.