WIP: Trimmed statistics functions have inconsistent API.

closes gh-2914

The TravisCI error seems to be a timeout related to coverage after passing the tests.

@argriffing Does that mean the error can be disregarded?

Does that mean the error can be disregarded?

Yes I think so.  This is related to https://github.com/scipy/scipy/issues/3913 - SciPy takes so long to build and test that it sporadically hits the TravisCI 50 minute time limit.  The error can be disregarded, or TravisCI could be restarted, or the problem could be patched by breaking up the tests or switching CI providers or probably by giving money to TravisCI.

These changes look good to me, signatures are correct. Too bad about ddof=1 (numpy uses 0) but that's necessary for backwards compat.

I included trim*because it seemed to make more sense than having a bunch of small related PR's instead of just one to keep track. I think the only things pending are masked array related, but I will get to that later on.

Makes sense to add trim* functions here. I've put some notes on those functions in gh-620.

I addressed the comments. Should I run the backwards incompatible change of trim1 and trimboth by the mailing list?

@aeklant yes, would be good to discuss those on the mailing list.

Since everyone who showed some interest seems to agree to the partial sorting I made that change. I also corrected the docstrings to reflect that change.
I had to make sure I sorted the output in the tests to avoid tests failing depending on whether they are run with numpy >= 1.8.0 or not. I could have also checked for the numpy version in each of the tests but this seemed easier to do and I didn't think there was a need to get technical since they're tests. Let me know what you think about that (e.g. Is the impact in time for TravisCI worth checking for the version instead of sorting?).

I wouldn't document the exact ordering of the result, as that is an implementational detail.
I'd just say the ordering of the trimmed content is undefined.
The tests should also not need to care about running in with partition or without, they only need to test that the results have been correctly trimmed, nothing else.
also trim_mean still sorts twice.

Yes, trim_mean should not call trimboth to avoid sorting the array twice.

Good, this only sorts once.

@aeklant I see one last thing that would be good to address: tmax and tmin return a masked array, while the other functions all return float or ndarray. This is inconsistent, and there is no reason for masked arrays to be returned anywhere in stats.py (it's an implementation detail leaking out). Could you change that and update the docstring examples to match?
Simple way would be to change last line to:
res = ma.maximum.reduce(am, axis).data
if res.ndim == 0:
    return res[()]

return res

Is there something else to review? Do you guys think it looks good for merging now?

Looks good to me now, merging. Thanks @aeklant, @jaimefrio

Thanks @rgommers. Can you close trim* issues: gh-618, gh-619, gh620 as they were handled in this PR too.

Sure, done.


Ripgrep always terminates with error code 2 on macOS

What did you expect to happen?
I am running counsel-projectile-rg on a project and I would expect to see files+lines where the entered string appears. Did used to work very well but broke recently (I didn't upgrade doom for a while, so I don't know where exactly this broke).
What actually happened?
I see the following error (error code 2):

Sadly I couldn't figure out how to debug this. I can't break on error (seems no elisp error is happening) and I can't figure out which command emacs is executing (I am not a elisp programmer - so my debugging capabilities are limited).
Additional details:
company-rg is working fine:

So I am not quite sure what the difference between these two commands are, but maybe this additional information helps?
Steps to reproduce:
This just happened after upgrading to the newest doom emacs.
System information:

((emacs
  (version . "26.3")
  (features . "JPEG RSVG IMAGEMAGICK GLIB NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS LCMS2")
  (build . "Nov 17, 2019")
  (buildopts "--disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs-plus/26.3/share/info/emacs --prefix=/usr/local/Cellar/emacs-plus/26.3 --with-xml2 --without-dbus --with-gnutls --with-imagemagick --with-modules --with-rsvg --with-ns --disable-ns-self-contained")
  (windowsys . batch)
  (daemonp . server-running))
 (doom
  (version . "2.0.9")
  (build . "HEAD -> develop f3bb23aa7 2020-07-21 16:19:08 -0400")
  (dir . "~/.home/doom/.doom.d/"))
 (system
  (type . darwin)
  (config . "x86_64-apple-darwin19.0.0")
  (shell . "/bin/zsh")
  (uname . "Darwin 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64")
  (path "~/bin" "/opt/local/bin" "/usr/local/bin" "/usr/local/sbin" "/opt/local/sbin" "~/.local/bin" "~/bin" "/usr/local/bin" "/usr/bin" "/bin" "/usr/sbin" "/sbin" "/Library/Apple/usr/bin" "~/Applications/SnowSQL.app/Contents/MacOS" "/usr/local/Cellar/llvm/9.0.0/bin" "~/.rvm/bin" "/usr/local/Cellar/emacs-plus/26.3/libexec/emacs/26.3/x86_64-apple-darwin19.0.0"))
 (config
  (envfile . envvar-file)
  (elc-files . 0)
  (modules :completion (company +childframe) (ivy +childframe) :ui doom doom-dashboard modeline doom-quit ophints hl-todo nav-flash (popup +all +defaults) vi-tilde-fringe window-select vc-gutter workspaces :editor format (evil +everywhere) snippets :emacs dired electric vc :tools eval editorconfig macos magit upload lookup lsp :checkers syntax :term eshell :lang (cc +lsp) csharp data emacs-lisp go markdown (org +capture +present) sh :config (default +bindings +snippets +evil-commands))
  (packages "n/a")
  (unpin "n/a")
  (elpa "n/a")))

This is a duplicate of #3038. See https://github.com/hlissner/doom-emacs/issues/3038#issuecomment-624165004 for workaround.
Run rg --with-filename --no-heading --line-number --color never TEXT by hand on your project to determine what error is causing it. Please move discussion there.

thanks -  #3038 didn't look like the same problem... I will comment there.


Cannot build ModelViewer with Release configure

Core project (Build_VS14\x64\Release\Output\Core\Core.lib) failed to build for ModelViewer in Release configuration using Visual Studio 2015 Update1 with the following error message (while Debug configuration is correct):
1>  FXAA.cpp
1>  GameInput.cpp
1>  GameCore.cpp
1>  GpuBuffer.cpp
1>  GpuTimeManager.cpp
1>  GraphicsCore.cpp
1>  Generating Code...
1>c:\program files (x86)\microsoft visual studio 14.0\vc\include\xmemory0(909): fatal error C1001: An internal error has occurred in the compiler.
1>  (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
1>   To work around this problem, try simplifying or changing the program near the locations listed above.
1>  Please choose the Technical Support command on the Visual C++
1>   Help menu, or open the Technical Support help file for more information
1>    CL!InvokeCompilerPass()+0x2d4bd
1>    CL!DllGetC2Telemetry()+0xae663
1>

And this is my visual studio version information:
Microsoft Visual Studio Professional 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01038

Installed Version: Professional

LightSwitch for Visual Studio 2015   00322-40000-00000-AA238
Microsoft LightSwitch for Visual Studio 2015

Visual Basic 2015   00322-40000-00000-AA238
Microsoft Visual Basic 2015

Visual C# 2015   00322-40000-00000-AA238
Microsoft Visual C# 2015

Visual C++ 2015   00322-40000-00000-AA238
Microsoft Visual C++ 2015

Visual F# 2015   00322-40000-00000-AA238
Microsoft Visual F# 2015

Windows Phone SDK 8.0 - ENU   00322-40000-00000-AA238
Windows Phone SDK 8.0 - ENU

AnalyzePackage   1.0
OpenCL Analyze package

Application Insights Tools for Visual Studio Package   1.0
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2015.1 (Beta8)   14.1.11106.0
ASP.NET and Web Tools 2015.1 (Beta8)

ASP.NET Web Frameworks and Tools 2012.2   4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET Web Frameworks and Tools 2013   5.2.30624.0
For additional information, visit http://www.asp.net/

Code Builder - API Debugger   <IP_ADDRESS>
Enables various API debugging facilities for OpenCL applications. These include (among other features): tracing, dumping buffers & images and visualizing the active OpenCL objects during debug session and afterwards.

CodeBuilderSessionManager   <IP_ADDRESS>
This package is in charge of managing all code builder sessions in the VS instance. A session is made of 1 or more cl files.

CodeBuilderTopMenu   1.0
This package is the top menu item in VS for Code Builder. This is the parent object for all other menu items in other packages.

Common Azure Tools   1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

GitHub.VisualStudio   1.0
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.

KofePackagePackage Extension   1.0
KofePackagePackage Visual Studio Extension Detailed Info

Microsoft Azure Mobile Services Tools   1.4
Microsoft Azure Mobile Services Tools

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

NuGet Package Manager   3.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

OCLDebugConfig   1.0
Information about my package

Office Developer Tools for Visual Studio 2015 ENU   14.0.23025
Microsoft Office Developer Tools for Visual Studio 2015 ENU

OpenCL Debug Engine   1
Intel(R) OpenCL Debug Engine

PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

Python Tools for Visual Studio   2.2.31105.00
Python Tools for Visual Studio provides IntelliSense, projects, templates, Interactive windows, and other support for Python developers.

Python Tools for Visual Studio - Django Integration   2.2.31105.00
Provides templates and integration for the Django web framework.

Python Tools for Visual Studio - Profiling Support   2.2.31105.00
Profiling support for Python projects.

SQL Server Data Tools   14.0.50616.0
Microsoft SQL Server Data Tools

Visual Assist
For more information about Visual Assist, see the Whole Tomato Software website at http://www.WholeTomato.com. Copyright (c) 1997-2015 Whole Tomato Software, Inc.

Visual C++ for Cross Platform Mobile Development   1.0
Visual C++ for Cross Platform Mobile Development

Visual C++ for Cross Platform Mobile Development   1.0
Visual C++ for Cross Platform Mobile Development

Visual Studio Tools for Universal Windows Apps   14.0.24720.00
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.

Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.

Xamarin   <IP_ADDRESS>7 (1390b70)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   <IP_ADDRESS> (d300845)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   <IP_ADDRESS> (ea30b32)
Visual Studio extension to enable development for Xamarin.iOS.

Please re-sync. I pushed a change to work around this bug last week. More details can be found in issue #68.

Oh, thank you! It works. Waiting for the compiler fix.

Duplicate issue. see #68


great code!  can you impl macd &  candlestick?

rt

hey! macd for sure at some point; i need to implement a histogram drawer, and once that's done it'll just mean tweaking the ema series to take a window size and macd should be doable.
candlestick will require a bit more thought as we'd need (4) data-points to power it, the open, close high and low, which i haven't figured out a way to codify in the model yet (we really only have y ranges as []float64).
in short, macd yes, candlestick will take a bit more work and will probably happen later

i have a first stab at macd series in the repo now; take a a peek. one thing i'm struggling with is how to verify that my implementation is producing the correct values (short of making an excel model and working backwards). i wouldn't use this yet until i get some better tests in there, but it should be good for at least running through a sanity check.

ok, i made an excel model and created test cases to verify, should be good to go on macd

good news

+1

Do you have an example of how this was intended to be implemented? MACDSeries, MACDLineSeries, and MACDSignalSeries all do not implement the Series interface, so they cannot be passed to a Chart's Series field like other charts may be implemented


Router middleware doesnt commit to store on SSR

I've created a middleware file called checkAuth.js:
export default function ({store, redirect, route}) {
  if (route.fullPath == '/login' && store.getters.isAuthenticated) {
    redirect('/');
  } else if (route.fullPath != '/login' && !store.getters.isAuthenticated) {
    redirect('/login');
    store.commit('SET_REDIRECTED_FROM', route.fullPath);
  }
}

and in nuxt.config.js I've set:
 router: {
    middleware: 'checkAuth'
}

relevant parts of store:
export const state = {
  user: null,
  redirectedFrom: null
};

export const mutations = {
  SET_USER (state, user) {
    state.user = user || null
  },
  SET_REDIRECTED_FROM (state, from) {
    state.redirectedFrom = from || null;
  }
};

The issue is that when line store.commit('SET_REDIRECTED_FROM', route.fullPath); is called in middleware, vuex store doesnt change the relevant state, even though I can see that the commit was actually called. Am I doing something wrong?

@Sarpedion if you are using routes with store you should use vuex-router-sync, and maybe commit to the store before do the redirect


setup automation for image build on release

setup automation for image build on release
Signed-off-by: Harshad Reddy Nalla<EMAIL_ADDRESS>Details:

This would set image build automatically on releases.
PR images can also be built.

Reference:
https://quay.io/repository/open-services-group/peribolos-as-service?tab=tags

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from harshad16 after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: tumido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [tumido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Implement response validation, add postResponseHandler

Closes #7

Renamed OpenAPIRequestValidator => OpenAPIValidator
Added validator.validateResponse
Added validator.getRequestValidatorsForOperation
Added validator.getResponseValidatorForOperation
validator.validateRequest & validator.validateResponse now accept
operationId as second parameter
OpenAPIBackend constructor opt validate can be a predicate function
to allow for fine control of whether to validate per request / operation

Thank you for the PR, hereafter is my review. Don't hesitate to let me know if what I say sounds like I'm totally off and didn't understand anything ^^.

this.validate seems to be only set to optsWithDefaults.validate in the constructor and never to anything else.

validateRequests and validateResponses seem to never be used.

In handleRequest the local variable validate seems to be decided upon the this.validate (either predicate or boolean) at request time and not re-evaluated later, meaning member context.responseValidator is populated based on decision taken at request time. I think that's why you planed the validateRequests and validateResponses ? I'm kind of confused about all that to be honest.

With validateRequests and validateResponses I can see scenarios where it is possible to validate requests and responses independently and freely. With a single point of predication, I'm not sure how this is going to happen. Maybe your PR is still in incomplete draft state, or I misunderstood something.

Just to suggest a bit of code rewrite, why not calling the routeHandler unconditionally, and then only applying the postResponseHandler if available ? This could allow centralized processing about the routeHandler, such as try/catching around or else. The tail call optimization that avoids await at the end of your code is probably negligible, and the whole function is already turned into a state machine anyway.

// handle route
let response = await (this.withContext
    ? routeHandler(context, ...handlerArgs)
    : routeHandler(...handlerArgs));

// post response handler
const postResponseHandler: Handler = this.handlers['postResponseHandler'];
if (postResponseHandler) {
    context.response = response
    // pass response to postResponseHandler
    response = await this.withContext ? postResponseHandler(context, ...handlerArgs) : postResponseHandler(...handlerArgs);
}

return response;

Thank you for the PR, hereafter is my review. Don't hesitate to let me know if what I say sounds like I'm totally off and didn't understand anything ^^.

this.validate seems to be only set to optsWithDefaults.validate in the constructor and never to anything else.

validateRequests and validateResponses seem to never be used.

In handleRequest the local variable validate seems to be decided upon the this.validate (either predicate or boolean) at request time and not re-evaluated later, meaning member context.responseValidator is populated based on decision taken at request time. I think that's why you planed the validateRequests and validateResponses ? I'm kind of confused about all that to be honest.

With validateRequests and validateResponses I can see scenarios where it is possible to validate requests and responses independently and freely. With a single point of predication, I'm not sure how this is going to happen. Maybe your PR is still in incomplete draft state, or I misunderstood something.

Just to suggest a bit of code rewrite, why not calling the routeHandler unconditionally, and then only applying the postResponseHandler if available ? This could allow centralized processing about the routeHandler, such as try/catching around or else. The tail call optimization that avoids await at the end of your code is probably negligible, and the whole function is already turned into a state machine anyway.

// handle route
let response = await (this.withContext
    ? routeHandler(context, ...handlerArgs)
    : routeHandler(...handlerArgs));

// post response handler
const postResponseHandler: Handler = this.handlers['postResponseHandler'];
if (postResponseHandler) {
    context.response = response
    // pass response to postResponseHandler
    response = await this.withContext ? postResponseHandler(context, ...handlerArgs) : postResponseHandler(...handlerArgs);
}

return response;

Hi! Thanks for taking the time to review! Super helpful having another pair of eyes on this stuff :)

You are correct. See the spread operator at the end of optsWithDefaults? We override any default values with the constructor's opts param there. https://github.com/anttiviljami/openapi-backend/blob/de72a09e2398969b94b8990ed3acb7565bcb8565/src/backend.ts#L90

Nice catch! I planned to use validateRequests and validateResponses but decided against it. Those are left over accidentally. Strange that my linter didn't catch that. 🤔

Yes, this is intentional. I thought it would be a good idea for the predicate function this.validate to receive the context object as well as the passed handler params for familiarity. You can now do things like:

const api = new OpenAPIBackend({
  ...,
  validate: (c) => {
    if (c.request.payload && c.request.headers['content-type'] === 'application/xml') {
      return false; // skip validation for xml payloads
    }
    return true;
  },
});

You're probably right here. Your suggestion makes the code more readable so I'll take your advice. Thanks!

With validateRequests and validateResponses I can see scenarios where it is possible to validate requests and responses independently and freely. With a single point of predication, I'm not sure how this is going to happen. Maybe your PR is still in incomplete draft state, or I misunderstood something.

Oh, and to answer this. Since api.handleRequest() never does any response validation, but instead leaves the validation task up to be done in the postResponseHandler I didn't see any point in having two separate opts for enabling request and response validation. You always do response validation yourself, whereas request validation can be enabled with opts.validate

Thank you.
Yeah about the ...opts shame on me for not seeing that ^^
Everything looks good then. Good job!


Improve leader node-left logging to indicate timeout/coordination state rejection

Signed-off-by: Poojita Raj<EMAIL_ADDRESS>Description
Production systems generally don't have debug logging enabled. The reasons for follower rejection are now logged at the default INFO logging level.
Issues Resolved
#992
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check

start gradle check


post-deploy hooks failing on windows since 1.20

Describe the bug
Post-deploy hooks are failing on windows since 1.20 - these were executing fine on 1.19.3.
For example using the following hook for prisma generate fails
hooks:
post-deploy:
- prisma generate
fails with:
post-deploy:
spawnSync prisma ENOENT
Running prisma generate ×
However changing 'prisma deploy' to 'prisma.cmd deploy' allows the command to be found and executed. This workaround was not required for 1.19.3. The same error and workaround also applies for other commands such as the graphql cli etc i.e. graphql get-schema fails but works when changed to graphql.cmd
To Reproduce
Steps to reproduce the behavior:

add a post deploy script for 'prisma generate' using 1.20.1 prisma cli on windows
run prisma deploy

Expected behavior
Prisma deploy should execute successfully
Versions (please complete the following information):

OS: Windiws 10
prisma CLI: 1.20.1
Prisma Server: 1.20.1

Regression is because a recent commit upgraded npm-run to latest version. Fix #2557 had purposely downgraded npm-run to 4.1.2 because of known issue on windows, timoxley/npm-run#19.

Pull request timoxley/npm-run#21 will hopefully fix this issue.

@yaacovCR : Thanks for the detailed insights, you are correct that this is a regression, I will patch this up soon.

Thanks and thank you for your work on Prisma!

I'm sorry I don't understand what the solution to this error is, someone can explain to me what to do, thank you

@difagume, workaround for now is as mentioned above by @pedwards1, to change the prisma command on windows within the post-deploy hook to prisma.cmd. It seems the eventual fix will be to move back to an older version of npm-run for now, but that has not been released yet.

Thanks @pedwards1 !
Same can be done if you're trying to execute graphql in your post-deploy then you can replace with graphql.cmd.


detect when used as a globally installed module; error on compile/clean verbs

fix and check can be used from a globally installed gts, but not check and clean.

Actually, use of check from a globally installed gts can be problematic. We do not depend upon typescript which means that unless the user has typescript also globally installed, we will not be able to instantiate tslint's API.
Perhaps the solution is for the global gts to try and locate the local gts and exec that, similar to how gulp does it.
Secondly, we should probably provide a better error message when check fails before typescript is missing.

Probably the only verb that makes sense from a non-local installed gts is init.
For all other verbs, we should exec the locally installed copy.

With the move to eslint I believe this actually works now!


Celebrations/sanctoral key division issues

We need to do the following:

move the following celebrations from celebrations (events) to sanctoral (even from sk.js, as I decided to keep them in sync with en.js for now; reasoning: even collective saint/blessed celebrations should be in the sanctoral):

allSaints;
christTheKing;
holyFamily;
josephHusbandOfMary;
maryMotherOfGod;
peterAndPaulApostles;

move the following celebrations from sanctoral to celebrations (events):

discoveryOfTheHiddenChristians;
guardianAngelOfPortugal;
immaculateConceptionOfTheBlessedVirginMaryPrincipalPatronessOfThePhilippines;
mostHolyNameOfJesusOrOurLadyOfBethlehem;
shipwreckOfSaintPaulApostle;
theFiveWoundsOfTheLord;
transferOfTheRelicsOfSaintStephen;
waitangiDay;

I need to do some investigations to see how this could be feasible, since in the romcal library theses current celebrations are deeply bound to the celebration sections in the locale files. What's the reason to move them?

reasoning: even collective saint/blessed celebrations should be in the sanctoral

Or another way to explain it: if we divide the celebrations (all of them) to celebrations (events) and sanctoral, we should be as punctual as possible.
The celebrations should contain any and all events-like celebrations and only those. Likewise, the sanctoral should contain any and all celebrations of saints and blesseds, be it humans or angels, celebrated individually or collectively. :smiley:

For the same reasons I've written here https://github.com/romcal/romcal/issues/210#issuecomment-937625932, I not sure this issue is still valid anymore.
Since romcal v3, the management of these LiturgicalDay object has been drastically refactored.


Replace RandomAccessFile in Env with io::RandomAccessFile

Do NOT merge this PR until #3066 is merged
What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[x] others

Problem Summary(Required) ：

Replace RandomAccessFile in Env with io::RandomAccessFile

@decster PTAL, especially those related to HDFSScanNode, e.g, hdfs_scan_node{.cpp, .h}, hdfs_canner{.cpp, .h}

I'll reopen this PR after manual tests passed.


window.print(); after content changed

Version
2.5.3
Reproduction link
https://jsfiddle.net/50wL7mdz/77812/
Steps to reproduce
Click the print link
What is expected?
i want to print "Print Me"
What is actually happening?
it will need to click second time only it change the content

change data don't update DOM immediately, you need execute window.print like this:
printNow(value){
  this.print = value;

  this.$nextTick(() => {
    window.print();
  });
}

What @anhulife said 🙂

change data don't update DOM immediately, you need execute window.print like this:
printNow(value){
  this.print = value;

  this.$nextTick(() => {
    window.print();
  });
}

It works!!!!!!!!


Stashed ops life cycle tests

Improve stashed ops tests coverage by using the pairwise generator to create different possible states in which a container could be at the moment of stashing and rehydrating.

This test suite will handle more scenarios once refresh happens more often. I will merge it as it is right now and add more cases as I finish the feature


added AUR to README

I have created an AUR package for all of us Arch users and added a link to it in the README

Thanks @Teddy-Kun
However, amdgpu_top uses crossterm-backend since v.0.1.2 , so it dose not depend on ncurses.
And amdgpu_top depends on libdrm-amdgpu .

Oh I did not know about the ncurses thing. I updated it.
As for the libdrm-amdgpu: Arch does not have a separate package for it, there are only libdrm and lib32-libdrm.

Apply, thanks.


Added cursor pointer

Added pr for #5

@AnshuPathak-88825 pull once

Didn't get it

@AnshuPathak-88825 Pull the recent changes to the website. I have merged some PRs just now. It's like updating your branch for this PR

so do I need to make again pr ? @Susmita-Dey

@AnshuPathak-88825 No.

@AnshuPathak-88825 Check this github guide.

I'm not getting it can you tell how can I do it ?

I'm not getting it can you tell how can I do it ? @Susmita-Dey

Check the above link github guide

@AnshuPathak-88825
Why did you commit package.json and package-lock.json
Those files shouldn't be staged to when you are committing


Remove ESURL from the log

Signed-off-by: linonymous<EMAIL_ADDRESS>

FYI: I did the same in github and gerrit @linonymous


Write a specification for a "FASM database" format

The fasm assembler uses;

Common logic which translate FASM feature names into bit positions
Custom logic to convert the bit position map into a bitstream by adding framing, headers, compression, etc.

WIP Document here


Request for more details

The article states that if we are not using Defender for Identity, then we can use powershell or event logs, but does not tell us how to do this. Please provide a link to instructions.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd5215da-c68b-eebf-6d81-ef109caa7f51
Version Independent ID: 8805daae-486b-7ea4-f4b4-ce9b0e04e51a
Content: Azure Active Directory security operations guide
Content Source: articles/active-directory/fundamentals/security-operations-introduction.md
Service: active-directory
Sub-service: fundamentals
GitHub Login: @BarbaraSelden
Microsoft Alias: baselden

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! I made a pull request to add references. https://github.com/MicrosoftDocs/azure-docs-pr/pull/167551


[SPARK-30946][SS] Serde entry with UnsafeRow on FileStream(Source/Sink)Log with LZ4 compression

What changes were proposed in this pull request?
This patch uses UnsafeRow to serialize/deserialize entry on FileStream(Source/Sink)Log, as well as applying LZ4 compression on serde.
The ground idea is that both FileEntry and SinkFileStatus haven't been changed for 3 years but we have been simply taking JSON serde to prepare with possible change and spending bunch of overhead on JSON format. CompactibleFileStreamLog has the metadata version information but it has been just version 1.
This patch introduces metadata version 2 of CompactibleFileStreamLog as leveraging UnsafeRow & LZ4 compression. While we introduce version 2 for CompactibleFileStreamLog, CompactibleFileStreamLog is still compatible with version 1 for both serialization and deserialization, so we can read from version 2 and write to version 2 in normal, and also we can read from version 1 and write to version 2 for smooth migration.
(Even we can stay with version 1 - read from version 1 and write to version 1 - whereas we won't do it actually.)
The approach how to load and store UnsafeRow with file is borrowed from HDFSBackedStateStoreProvider, as it has been running for 2.x version lines and no critical issue has been reported so far.
Why are the changes needed?
Multiple JIRA issues have been filed to report that huge metadata logs make their queries very slow. While this patch won't make their metadata log stop growing, this patch may heavily reduce down their metadata log and time to process compaction.

SPARK-24295
SPARK-29995

Please find the numbers in the section "How was this patch tested?".
As this also reduces the latency to read all files from file stream sink metadata, it also helps to speed up the query for both batch and streaming if the input path is pointing to the output of file stream sink.
Does this PR introduce any user-facing change?
No. It will read both v1 and v2 metadata log files, and writes v2 metadata log files. So once end users run their query long enough, cleanup would remove old metadata log files and eventually only v2 metadata log files will be left. (Say, smooth migration)
How was this patch tested?

Existing UTs (UTs for checking with 2.1.0 compatibility is basically the checking with V1 compatibility, as I don't find any change)
Manually done simple perf. test

Test environment

target metadata: FileStreamSinkLog
compact interval = 10
prepared 1 compact file and 8 normal files, try to write the next batch which is compact batch
the number of total entries (in compact batch): 1,707,950
memory usage of total entries (in compact batch): 606,97 MB

V1

total size of metadata log file (compact): 391.12 MB (410,116,683 bytes)
total elapsed time to compact (avg. of 10 times, excluding min and max): 26,199 ms
total elapsed time to load all entities to compact (avg. of 10 times, excluding min and max): 13,558 ms
total elapsed time to write all entities to compact batch file (avg. of 10 times, excluding min and max): 12,666 ms

V2

To run the test in same environment, I converted input metadata files to V2 before running tests. (1 compact file, 8 normal files)

total size of metadata log file (compact): 76.36 MB (80,073,732 bytes) (19.52%)
total elapsed time to compact(avg. of 10 times, excluding min and max): 2,948 ms (11.25%)
total elapsed time to load all entities to compact (avg. of 10 times, excluding min and max): 1,023 ms (7.54%)
total elapsed time to write all entities to compact batch file (avg. of 10 times, excluding min and max): 1,956 ms (15.44%)

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

Test build #118924 has started for PR 27694 at commit 55d238f.

Honestly I have been thinking about larger changes, like:

avoid rewriting all entities on compact operation
support retention (ideal to design with above item, as we won't be able to read all existing entities on compact operation)
use tree structure, or at least two kinds of entry "directory" and "file" to heavily reduce down path string on entries

but would like to have priorities on (less changes - bigger impact), and make changes incrementally.
This patch brings the least changes but great impact on performance. Above items are orthogonal to this improvement so they can be addressed on demand later.

Test build #118924 has finished for PR 27694 at commit 55d238f.

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

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

retest this, please

Test build #121228 has started for PR 27694 at commit 55d238f.

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

Test build #121228 has finished for PR 27694 at commit 55d238f.

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

Suppose there is a streaming job pipeline, and these streaming job comes from different end-users or department, if middle end-user upgrade their spark and use CompactibleFileStreamLog V2 (as you said in default, we can read from version 1 and write to version 2 for smooth migration.), then downstream jobs will fail. Is there something I misunderstand？So, It is better to keep the version of CompactibleFileStreamLog, or leave a config to upgrade version of CompactibleFileStreamLog with default false?

@uncleGen
Yes I haven't thought about the case where Spark versions are mixed up.
It seems to be a clear case that end users don't want to upgrade version smoothly (implicitly), but would it be some case where they start to write the output and want to make it be compatible with Spark 2.x?
If we want to have latter then it's worth to have an option which specifies "version" of the format. (The default value would be ideally same with the existing one in file, or highest known version.)
If we can just live with former then a flag option would be fine.

I've just picked this up but seems like it has a conflict + linter job failed. Could you resolve them?

Test build #122403 has started for PR 27694 at commit 74163d2.

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

Test build #122403 has finished for PR 27694 at commit 74163d2.

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

Test build #123150 has started for PR 27694 at commit 3231611.

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

Test build #123150 has finished for PR 27694 at commit 3231611.

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

retest this please.

Test build #123156 has started for PR 27694 at commit 3231611.

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

Test build #123156 has finished for PR 27694 at commit 3231611.

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

One lesson I learned from the past is UnsafeRow is not designed to be persisted across Spark versions. I'd avoid to introduce another place that persists data in the UnsafeRow format. Do you know what are the performance numbers if we just compress the text files?

One lesson I learned from the past is UnsafeRow is not designed to be persisted across Spark versions.

This sounds like a blocker for SS, as we leverage it to store state which should be used across Spark versions and shouldn't be corrupted/lost as it's time-consuming or sometimes simply not possible to replay from the scratch to construct the same due to retention policy. Do you have references on following the discussion/gotcha for that issue? I think we should really fix it for storing state - probably state must not be stored via UnsafeRow format then.

Do you know what are the performance numbers if we just compress the text files?

I haven't experimented but we can easily imagine the file size would be smaller whereas processing time may be affected both positively (less to read from remote storage) and negatively (still have to serialize/deserialize with JSON + compression).
Here the point of the PR is that we know the schema (and even versioning) of the file in prior, hence we don't (and shouldn't) pay huge cost to make the file be backward-compatible by itself. We don't do versioning for data structures being used by event log so we are paying huge cost to make it backward/forward compatible. If we are not sure about unsafe row format for storing then we may be able to just try with traditional approaches.

I've spent some time to experiment more approaches.
This is the experiment branch: https://github.com/HeartSaVioR/spark/tree/SPARK-30946-experiments

Version 3 is only applying compaction (LZ4) on existing format. See below commit:

https://github.com/HeartSaVioR/spark/commit/406670aa4910c4bec847a590ef37f2f0bd130902

Version 4 is serializing/deserializing entry via DataInputStream / DataOutputStream

https://github.com/HeartSaVioR/spark/commit/7c665163bdd1930fb8812d46a7f8cdd599b1cafb
I've also implemented simple apps to 1) prepare metadata (so that we can experiment on the specific batch) and 2) run simple test with various versions:
https://github.com/HeartSaVioR/spark-delegation-token-experiment/commit/bea7680e4c588f455f8c3181a96c9eff5002fa1a
The numbers are recorded below:
https://docs.google.com/spreadsheets/d/1D5P103F_sKOjkDpNr9PaCC8Ehk4Y4dRtH3oEdytM4_c/edit?usp=sharing

version
elapsed time
elapsed time (ratio of v1)
size
size (ratio of v1)

1
10628.75
100.00%
57265744
100.00%

2
939.25
8.84%
16655736
29.08%

3
10116
95.18%
17259852
30.14%

4
837
7.87%
15285626
26.69%

The number represents that applying compression on existing format doesn't help reducing the time, while the size is reduced similar with other alternatives. Other alternatives directly integrated to the data structure greatly reduce the time, say, 10 times faster. The size of compact files are similar across alternatives.

Hi all, are these numbers enough to persuade? Given we concern about "compatibility" I think the version 4 is ideal, which "Java" guarantees compatibility across architectures. I'll update the patch to use the version 4 as a new version (version 2, of course) as of now.

Test build #123555 has started for PR 27694 at commit 737cc60.

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

Test build #123559 has started for PR 27694 at commit 6cd9bfd.

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

Test build #123555 has finished for PR 27694 at commit 737cc60.

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

Also addressed the case on reading the metadata log from lower version of Spark.
@uncleGen Does the approach make sense?
@zsxwing Could we revisit the approach on performance & compatibility point of view?

Test build #123559 has finished for PR 27694 at commit 6cd9bfd.

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

Failed UTs are unrelated.

retest this, please

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

Test build #123564 has started for PR 27694 at commit 6cd9bfd.

Test build #123565 has started for PR 27694 at commit 3933018.

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

Test build #123565 has finished for PR 27694 at commit 3933018.

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

Test build #123564 has finished for PR 27694 at commit 6cd9bfd.

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

retest this, please

Test build #123582 has started for PR 27694 at commit 3933018.

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

Test build #123582 has finished for PR 27694 at commit 3933018.

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

retest this, please

Test build #123987 has started for PR 27694 at commit 3933018.

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

Test build #123987 has finished for PR 27694 at commit 3933018.

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

@HeartSaVioR Thanks for your efforts. The result (version 4) is very impressive. Overall, it makes sense to me. But we should resolve the concern about using UnsafeRow. I am not very familiar with the history of discussing about UnsafeRow. By the way, is there any value or plan to use this idea?

I’m sorry, but version 4 doesn’t leverage UnsafeRow. (version 2 was.) Please read the description thoughtfully.
As I commented earlier there’re still lots of possible improvements in metadata, but I don’t want to go through unless we promise dedicate efforts on reviewing.

Just to make sure I did go through the idea of @uncleGen proposed, I'll elaborate why I didn't go through actual implementation.
While there's effectively NO deletion of the entry on file stream source/sink, it's definitely needed to have "retention" on both, so consideration of deleting entries was required. Once we read previous file and make modification, then it defeats the good side of the idea (no read and no rewrite on previous compact batch).
There's a way to achieve both of the goods, via splitting compact batch file per timestamp (the unit would be day, hour, etc and the unit defines the granularity of retention) and delete compact batch file based on the retention. It's a bit complicated to implement, and size of the each compact batch file would be out of control.
The idea may be still valid but if we would like to make it work nicely it should have been designed thoughtfully.
Compared to that idea, this patch is no-brainer, inherits shortcoming of current compact behavior but can do the job pretty much faster (~10x). Based on end users' instinct about volume of the outputs per day and good value of retention, they can roughly control the size of the compact batch file.
(It still won't work if the volume is gigantic or they need to set pretty high retention, but that's the time we propose trying out alternatives. Currently it simply doesn't work or makes end users struggling with normal workload.)
Even with this patch & retention, memory issue may still exist, as this patch doesn't help reducing memory usage on compact. Current file stream source/sink requires to materialize all entries into memory during compact, maybe also during get. The problem is more specific to file stream sink, as the size of entry are much bigger, and even with retention a compact batch would have bunch of entries. Addressing issue on get is hard, but addressing issue on compact would be relatively easier, and helps file stream sink to avoid OOME during compact phase. Next item to do.

The numbers are pretty impressive. Thanks a lot for your work.
My high level comments regarding the PR:

The compression codec should not be hardcoded. It's better to allow the user to config the writer codec like other codec configs in Spark. The reader should be able to identify the codec and load files correctly. Otherwise, we would need to bump the version again when adding more codec support.
The cost of bumping file sink version is much higher than the checkpoint. The file sink metadata should be compatible with old versions if possible like other storage formats such as parquet, orc.

For example, in some company, the team who generates the output may not be able to convince the downstream to upgrade their Spark version.
The file sink metadata can be read by an external system. Bumping the version will need the ecosystem to build a new reader.
If a user hits a critical issue in new Spark version, they may want to rollback. Bumping the version will break this workflow.

It's better to make the default behavior like this:

Use v1 if an existing directory is using v1, so that we can still  support rollback. The user can set a flag to enable v2 explicitly.
Use v2 if it's a new directory.

I'm wondering if we can step back to think about whether it is possible solve the issue without bumping the version. IMO, the major issue is the number of files increases infinitely over time. This PR increase the upper bound but doesn't change the complexity. Maybe we should try to see how to reduce the number of files, such as supporting data compaction? You may notice that FileStreamSinkLog.DELETE_ACTION is never used. This is because it was added to support data compaction but we didn't implement it yet.
I totally understand that we may not be able to solve the metadata issue without bumping the file metadata version. Then it's better to design a better file sink log format to solve all of the following issues so that we don't need to bump the version again in future:

Data compaction support.
Open source format. It would be great that the new file sink log format can be read by Spark and other systems. An extra benefit is we can use Spark itself to process the metadata so that we don't have to put all metadata in the driver memory.
Better file stream source support. Since we always append files to the file sink, when reading a file sink using streaming queries, it would be great we can locate the new appended files quickly. For example, we can use log file name + line number as the streaming source offset instead, then we can jump to the log file directly.
Filter push down support when reading a file sink directory. For example, if a user queries only one partition, we don't need to load metadata of other partitions into the driver memory.
Decouple the file sink from the streaming query. Currently, one file sink output always maps to one streaming query. The user may want to use another streaming query or even batch query to write to the same file sink. But as we use the batch id as the file name, this is not supported.
Use relative path. Copying the file sink directory will break it today. It would be great that we remember the relative paths so that people can move or copy the directory.

@zsxwing
Thanks a lot for your detailed comment!
I think considering all of these would take me to redesign, which wasn't a goal actually. As I commented previously, building a holistic solution was not a goal, because I already indicated it should take considerable time, and someone might claim that it's reinventing the wheel.
That said, shall we do the following?

Review and merge other PRs which don't incur metadata version upgrade.

#28904
#28422
#28363
#27649
#27620

File an issue to address these requirement altogether, with one of PMC member being shepherd. (It would be amazing if you can volunteer.) Once someone volunteers and promises to make thing forward, I'll persuade my employer to allow me to take the work.

If it's not desired to go with 2, I'd ask to make the file source/sink metadata log class be pluggable at least (I'll craft a PR soon if that's the way to go), so that someone can move forward with restricting the use case.
WDYT?

(IMHO it might be still good to leverage this PR to be a chance to construct a good way for versioning properly - so that version 2 can be used as an interim with best practice on versioning, and we get version 3 with such major features included without headache on versioning.)

Probably we can go with supporting relative path “as well” in this metadata version which would heavily reduce the size even without compression. I’ll experiment this approach as well.

Probably we can go with supporting relative path “as well” in this metadata version which would heavily reduce the size even without compression. I’ll experiment this approach as well.

Never mind. I simply missed that the metadata log should be able to read from older Spark versions which might have no idea to handle relative path. This change also needs to bump up the version.

retest this, please

Test build #125726 has started for PR 27694 at commit 3933018.

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

Test build #125726 has finished for PR 27694 at commit 3933018.

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

retest this, please

Test build #125737 has started for PR 27694 at commit 3933018.

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

@zsxwing Would you mind if I ask your opinion on https://github.com/apache/spark/pull/27694#issuecomment-651479578 ?

Test build #125737 has finished for PR 27694 at commit 3933018.

This patch fails PySpark pip packaging 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/125737/
Test FAILed.

retest this, please

Test build #125748 has started for PR 27694 at commit 3933018.

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

Test build #125748 has finished for PR 27694 at commit 3933018.

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

Test build #125876 has started for PR 27694 at commit 86131af.

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

Test build #125876 has finished for PR 27694 at commit 86131af.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds no public classes.

retest this, please

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

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

Test build #125900 has started for PR 27694 at commit 86131af.

Test build #125900 has finished for PR 27694 at commit 86131af.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

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/125900/
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/SparkPullRequestBuilder-K8s/30544/
Test PASSed.

Test build #125934 has started for PR 27694 at commit 2559928.

Test build #125934 has finished for PR 27694 at commit 2559928.

This patch fails due to an unknown error code, -9.
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/125934/
Test FAILed.

retest this, please

Test build #125957 has started for PR 27694 at commit 2559928.

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

Test build #125957 has finished for PR 27694 at commit 2559928.

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

retest this, please

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

Test build #127534 has started for PR 27694 at commit 2559928.

Test build #127534 has finished for PR 27694 at commit 2559928.

This patch fails due to an unknown error code, -9.
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/127534/
Test FAILed.

retest this, please

Test build #127549 has started for PR 27694 at commit 2559928.

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

Test build #127549 has finished for PR 27694 at commit 2559928.

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

retest this, please

Test build #127573 has started for PR 27694 at commit 2559928.

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

Test build #127573 has finished for PR 27694 at commit 2559928.

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

Closing as I don't see any support on this and I'm now in favor of one of alternatives.


NoX11Error on OS X Yosemite

Hello,
I'm getting a NoX11Error when attempting to use dryscrape on X11. I'm using python 2.7 (with anaconda), and I have XQuartz installed and running. The installations all went fine (Qt, pip, webserver-kit, etc.).  Any help would be appreciated.
Johns-MacBook-Pro:dryscrape johngu$ echo $DISPLAY
/private/tmp/com.apple.launchd.57RQ2D0Hcg/org.macosforge.xquartz:0
/Users/john/anaconda/lib/python2.7/site-packages/webkit_server.pyc in get_default_server()
429   global default_server
430   if not default_server:
--> 431     default_server = Server()
432   return default_server
433
/Users/john/anaconda/lib/python2.7/site-packages/webkit_server.pyc in init(self, binary)
407       self._port = int(re.search("port: (\d+)", output).group(1))
408     except AttributeError:
--> 409       raise NoX11Error, "Cannot connect to X. You can try running with xvfb-run."
410
411     # on program termination, kill the server instance

Have you tried not using XQuartz at all, i.e. export DISPLAY=? I just installed it on my Mac without problems, and it seems to work as is, without an X server running

It might also be useful to see the full output of webkit-server. Can you try running /Library/Python/2.7/site-packages/webkit_server?

I'm running an install of Anaconda python (http://continuum.io/downloads),
so the location of my webkit_server is a bit different:
Johns-MacBook-Pro:site-packages johngu$ pwd
/Users/john/anaconda/lib/python2.7/site-packages
Johns-MacBook-Pro:site-packages johngu$ ./webkit_server
dyld: Library not loaded: libQtWebKit.4.dylib
Referenced from:
/Users/john/anaconda/lib/python2.7/site-packages/./webkit_server
Reason: image not found
Trace/BPT trap: 5
Johns-MacBook-Pro:~ johngu$ find . -name libQtWebKit.4.dylib
./anaconda/envs/python3/lib/libQtWebKit.4.dylib
./anaconda/lib/libQtWebKit.4.dylib
./anaconda/pkgs/qt-4.8.6-0/lib/libQtWebKit.4.dylib
I think did this: export
DYLD_FALLBACK_LIBRARY_PATH=/Users/johngu/anaconda/lib
After that I was able to operate the program fine.  I think it's just a
function of my using anaconda and the webkit_server not knowing where to
look for the libQt dylib's.
On Fri, Jul 24, 2015 at 1:41 AM, Niklas Baumstark<EMAIL_ADDRESS>wrote:

It might also be useful to see the full output of webkit-server. Can you
try running /Library/Python/2.7/site-packages/webkit_server?
—
Reply to this email directly or view it on GitHub
https://github.com/niklasb/dryscrape/issues/33#issuecomment-124177569.

thanks for letting me know. I should probably make the error message more specific, right now it just assumes that webkit_server failed to due a missing X connection if it doesn't run properly...


test: synchronizing json spec

What
APM agent specs automatic sync
Why
Changeset

https://github.com/elastic/apm/commit/10b6514 add application handler (https://github.com/elastic/apm/pull/503)

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-09-08T12:00:00.006+0000

Duration: 30 min 24 sec

Commit: c545e79b1488e5d7694cc2529ebb0f66e415d943

Test stats :test_tube:

Test
Results

Failed
0

Passed
9596

Skipped
8604

Total
18200

Trends :test_tube:

:green_heart: Flaky test report
Tests succeeded.

Expand to view the summary

Test stats :test_tube:

Test
Results

Failed
0

Passed
9596

Skipped
8604

Total
18200


Lab 07 - Storing Generated Documents in Azure Storage

SO WHERE is the sign-in button on the HOME page ?
End of Exercise 3 - Task 3 - step 26:
Click the Sign-in-Sheet button for any event.
So where is the button? Lab dies right here without the button.
Also, there is no blob container sign-in when using Cloud Explorer in next Exer 4 Task 1 step 7.

Thanks. I missed it.
Multi-project startup.
Should be a note that it comes up in the background underneath the Contoso.Events.Web home page. For the SLOW students and trainers.......
Thanks.

@denschork Does it come up in the background or as a new tab for you?

Separate browser window using IE 11. Its easy to miss.

Separate browser window.
From: Sidney Andrews<EMAIL_ADDRESS>Sent: Wednesday, November 09, 2016 7:49 PM
To: MicrosoftLearning/20532-DevelopingMicrosoftAzureSolutions<EMAIL_ADDRESS>Cc: denschork<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftLearning/20532-DevelopingMicrosoftAzureSolutions] Lab 07 - Storing Generated Documents in Azure Storage (#150)
@denschork https://github.com/denschork  Does it come up in the background or as a new tab for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftLearning/20532-DevelopingMicrosoftAzureSolutions/issues/150#issuecomment-259569936 , or mute the thread https://github.com/notifications/unsubscribe-auth/AKRK1SS6xXiKJGawcd4Fv_MzSpeo1qb9ks5q8mnhgaJpZM4KtL13 .  https://github.com/notifications/beacon/AKRK1URvZMdoSGCe-UpvKQyPKgYDXuQ2ks5q8mnhgaJpZM4KtL13.gif


_weakref.proxy raises an Exception when used on types with no rich comparison operators

The fix for this is defining the rich comparison methods on the object type.
See: https://github.com/IronLanguages/ironpython3/pull/710#issuecomment-568187567
The following code raises a SystemError:
import _weakref
class A: pass

a = A()
p = _weakref.proxy(a)
p.__lt__ # this line incorrectly raises a SystemError

Probably resolved by https://github.com/IronLanguages/ironpython3/pull/833


Use font-smoothing on Button component

Add -webkit-font-smoothing: antialiased to the Button component per discussion with @odmln
See https://developer.mozilla.org/en-US/docs/Web/CSS/font-smooth

Should we actually add that to the Base Component in the ThemeProvider?


Update solarviewdatareader to 1.0.8

Please update my adapter ioBroker.solarviewdatareader to version 1.0.8.
This pull request was created by https://www.iobroker.dev c0726ff.

1.0.8 created 18.01.2024
6 user


Slicer CLI UI

resovles #1
TODO:

[x] Review xmlParser code and see if I can convert it to typescript
[x] Start creating Vue panels for slicer CLI inputs/outputs

File Browser Functionality

[x] Collapsable system for folders vs items, where it will start with items collapsed
[x] Pagination system will allow offset for folders independent of items that way each can have it's own page listing
[x] Add in default limit of 500 or so (this is for the folders and items)
[x] Add in sorting system for folders/items which will redo the request.
[x] Make the top breadcrumb bar static and area below scrolling

Props:

[x] Props for saving a new item vs selection
[x] Props for determining selection type (file, folder, item)
[x] Props for multiple selection tools (being able to select multiple files or multiple folders)

Advanced FileBrowser Props:

[x] File validation callback functionality which will return metadata on selected file for validation
[ ] filter prop function to highlight files/folders that have a specific extension or metadata associated with it.

Other Tasks

[ ] create the proper API function for starting a dive-slicer-cli run task
[x] Create a Proper Parameter Component that can render the different types
[x] Create additional utilities for input/output parameters.  I.E. may need some file/folder browsers written in Bootstrap.

Next Up API Call
Need to convert a selected task back into a request to the back-end for running the Task.
This will require transferring values back into query parameters.
One thing to note is that files/folder are done in a paramname_path and paramname_folder. where _path is the GirderID of the item or the RegularExpression for selecting multiple and _folder is the parent folder.  I need to check if this is needed if it is only a direct girderItem.

Going to Merge this in and move newer issues to a new PR.  This is large enough already.


Dependency Shapely: Not installed in new env

The installation of Shapely doesn't work in a fresh environment.
How to reproduce:

pip install deutschland

Expected result:

python package should be installed

What I got instead:

Error message:

 ERROR: Cannot install deutschland==0.1.0, deutschland==0.1.1, deutschland==0.1.2, deutschland==0.1.3, deutschland==0.1.4, deutschland==0.1.5, deutschland==0.1.6 and deutschland==0.1.7 because these package versions have conflicting dependencies.

The conflict is caused by:
    deutschland 0.1.7 depends on Shapely<2.0.0 and >=1.7.1

Workaround:

first install Shapely manually by running pip install Shapely.

My environment:

Mac 11.5.2. Big Sur, Python 3.9.6, pip 21.2.4

I have so far not been able to reproduce your issue in a fresh environment.
Shapely is listed as a dependency, as shown in pip show deutschland and on PyPI (https://pypi.org/pypi/deutschland/0.1.7/json)
$ pip install deutschland==0.1.7
$ pip show deutschland

Name: deutschland
Version: 0.1.7
...
Location: /home/xxx/Dokumente/bundesapi/test_bundesapi/venv/lib/python3.8/site-packages
Requires: Pillow, dateparser, gql, tensorflow, boto3, Shapely, requests, slugify, beautifulsoup4, mapbox-vector-tile
Required-by:

My environment:

Ubuntu 20.04, venv with 3.8.10 and pip 20.0.2


Error StaticInjectorError[ViewContainerRef] when having *ngIf or *ngFor

Type of Issue
[x] Bug Report
[ ] Feature Request

Description
When I am using either *ngIf or *ngFor in my template I got this error message: StaticInjectorError[ViewContainerRef]. Any ideas why this happen?

How To Reproduce

Create a component footer.component.ts
Add *ngIf in footer.component.html
Run ng-packagr -p ng-package.json and npm publish
Install on new Angular 5 app (npm install)
Run my Angular 5 App ng serve

Here is my code:
footer.component.ts
import { Component, Input, OnInit } from '@angular/core';

@Component({
  selector: 'app-footer',
  templateUrl: './footer.component.html',
  styleUrls: ['./footer.component.scss']
})
export class FooterComponent implements OnInit {
  @Input() isTrue: boolean;

  constructor( ) { }

  ngOnInit() { }
}

footer.component.html
<footer>
    <h2 *ngIf="isTrue">Hello</h2>
</footer>

Expected Behaviour
Should not error
Version Information
ng-packagr: ^1.6.0
node: v7.6.0
@angular: v5.0.2
rxjs: v5.5.2
zone.js: v0.8.18

#299
Please, use the ng-packagr@next (2.0.0 release candidates) and typescript 2.4.x. Does it disappear?

Hi @doenikoe,
the error is reproducible in the integrationt ests of ng-packagr by running ng serve in the Angular CLI consumer app.
If you can figure out what is causing the Angular DI to throw the StaticInjectionError, it's going to help!

jvandemo/generator-angular2-library#240
angular/angular#20598

So, my team found a horrible fix for this issue:

Create a new project with the Angular CLI.
Copy over all of the dependencies from its package.json to your package.json
Delete your node_modules folder and your package-lock.json
npm install

As mentioned in https://github.com/dominique-mueller/angular-package-builder/issues/38, using the --aot or --preserve-symlinks flag on ng serve probably solves this issue (which occurs when installing the library via a local directory instead of remotely).

Yup same here even a simple *ngIf gives this error.

@doenikoe did you get this issue fixed?

Did anyone solve the issue ?? seems --preserve-symlinks also does not work

@SravanKumarNangunoori did you manage to make it? It doesn't seem to work still with latest version.

I have a similar issue when trying to use [ngClass] in a module that I import to another module. Using --preserve-symlinks doesn't solve it. When I use --aot I get an error message:
ERROR in ../sam-site/src/app/shared/shared.module.ts(5,2): Error during template compile of 'SharedModule'
  Function expressions are not supported in decorators in 'NgModule'
    'NgModule' contains the error at @angular/core/core.ts(194,31)
      Consider changing the function expression into an exported function.

I'm not familiar enough with Angular to know what this means or what to do with it, maybe someone has an idea where to look?

first check u have defined all the service in the  app.module.ts provider
like -    providers: [UserService, AuthService, Interceptor, TokenStorage],

Same error here StaticInjectorError(Platform: core)[NgClass -> IterableDiffers] and --preserve-symlinks seems not work. Any hint?

i dont whats it getting wrong but for me following solution works (i facing this in anguiar5)
add in angular-cli.json
"defaults": {
"styleExt": "css",
"component": {},
"build": {
"preserveSymlinks": true
}
}

delete node modules
npm install
ng serve
https://github.com/jvandemo/generator-angular2-library/issues/240 with the help oh this ,

this may help ........... :-)

UPDATE: I manage to solve the issue by updating both my lib and my app that uses the lib to Angular 5.2.8 (it works with 5.2.9 also) and angular cli to  1.7.3.
No preserveSymlinks or any other configuration is needed!

@vapits Could you link an example project with this working?  I'm currently still having issues using the Angular 5.2.8 and cli 1.7.3.   Maybe there is another package that needs to be a specific version or you have a specific angular/webpack config?  My main app will not dynamically load the lib with *ngIf, but loads fine without an *ngIf.

This happened for me as well.

I created an Angular library, a custom checkbox called my-checkbox.
I run yarn link in the my-checkbox dist folder.
I run yarn link my-checkbox inside my "real" app folder.
I add import { MyCheckbox } from my-checkbox`
I build the the app with ng build --watch

I get this warning from angular-cli
WARNING in<EMAIL_ADDRESS>4996:15-36 Critical dependency: the request of a dependency is an expression

I get this error runtime from browser:
ERROR Error: StaticInjectorError(AppModule)[NgClass -> KeyValueDiffers]:
  StaticInjectorError(Platform: core)[NgClass -> KeyValueDiffers]:
    NullInjectorError: No provider for KeyValueDiffers!
    at<EMAIL_ADDRESS>(core.js:1060)
    at resolveToken (core.js:1298)
    at tryResolveToken (core.js:1242)
    at<EMAIL_ADDRESS>(core.js:1139)
    at resolveToken (core.js:1298)
    at tryResolveToken (core.js:1242)
    at<EMAIL_ADDRESS>(core.js:1139)
    at resolveNgModuleDep (core.js:8377)
    at<EMAIL_ADDRESS>(core.js:9065)
    at resolveDep (core.js:9430)

Solved by running ng build --watch --preserve-symlink

sorry for commenting in closed issue but some of you guys going to love me for this and how trivial this is;
long story short - the module imports order is crucial;
please, refer to this article: https://blog.angularindepth.com/avoiding-common-confusions-with-modules-in-angular-ada070e6891f

I was working on this and I don't use the angular cli. The answer was very simple for me. Remember to remove your library's dependencies before installing into your main app.

#299
Please, use the ng-packagr@next (2.0.0 release candidates) and typescript 2.4.x. Does it disappear?

npm install ng-packagr
then npm install


feat(withLDProvider): adding mock support for withLDProvider

This package currently doesn't mock withLDProvider. This PR adds support for mocking the same.

This is now available in version 0.2.1. Thanks for the contribution!

Thank you @bwoskow-ld @yusinto for the quick turnaround. Appreciate it.


dogstatsd: remove stale UNIX socket on startup

dogstatsd removes stale UNIX socket when starting. This logic only applies to existing UNIX socket. If anything else (file, directory, etc...) exists for the same path, the NewUDSListener() function fails and returns an error.
Entrypoint scripts for the agent and dogstatsd standalone image have been updated.

@mfpierre Fixed! Should be good to go. Thanks!

@mfpierre waiting on your stamp of approval ;)


calling npm publish fails

Intention

I'm submitting a bug report
Environment

Operating System:
Windows 10

Node Version:
v6.2.2

NPM Version:
3.9.5

Description
Current behavior:
I've tried to add a new task which should run npm publish. It aborted with:
[20:54:00] -----STARTED-----
[20:54:00] spawn npm ENOENT
[20:54:00] -----FINISHED WITH ERROR-----
[20:54:00] spawn npm ENOENT

Expected/desired behavior:
Be able to run npm publish.
Logs

Logs are attached.
(btw. the issue template still mentions csv)
2016-010-04.txt

So the issue here is that on windows you need to spawn npm.cmd instead of npm. https://nodejs.org/dist/latest-v4.x/docs/api/child_process.html#child_process_spawning_bat_and_cmd_files_on_windows explains this a bit.

(btw. the issue template still mentions csv)

Will fix that 👍

Is this the first time that anyone tried to spawn npm? After all testing, this seems odd

We have only used npm start before (this command is used to start webpack skeletons). And we have a check that makes this work here. The problem is that this check is only used for the command npm start  and not for any npm command. So this should be easily fixed

Of course


error time tracking when added to an issue

Gitea version (or commit ref): 1.5.3
Git version: 2.11
Operating system: Linux Debian
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

2018/11/11 16:18:28 [I] [SQL] SELECT * FROM `user` INNER JOIN issue_assignees ON assignee_id = `user`.id WHERE (issue_assignees.issue_id = ?) []interface {}{1}
2018/11/11 16:18:28 [I] [SQL] SELECT COALESCE(sum(`time`),0) FROM `tracked_time` WHERE issue_id=? []interface {}{1}
2018/11/11 16:18:28 [I] [SQL] SELECT `id`, `type`, `issue_id`, `comment_id`, `user_id`, `created_unix` FROM `reaction` WHERE reaction.issue_id=? ORDER BY `reaction`.`issue_id` ASC, `reaction`.`comment_id` ASC, `reaction`.`created_unix` ASC, `reaction`.`id` ASC []interface {}{1}
2018/11/11 16:18:28 [I] [SQL] SELECT `id`, `assignee_id`, `issue_id` FROM `issue_assignees` WHERE `assignee_id`=? AND `issue_id`=? LIMIT 1 []interface {}{1, 1}
2018/11/11 16:18:28 [I] [SQL] SELECT `name` FROM `user` WHERE `id`=?  LIMIT 1 []interface {}{2}
2018/11/11 16:18:28 [I] [SQL] UPDATE `issue` SET `updated_unix` = ? WHERE `id`=? []interface {}{1541967508, 1}
2018/11/11 16:18:28 [I] [SQL] COMMIT
[Macaron] 2018-11-11 16:18:28: Completed POST /eeee/venenux-alone/issues/1/times/add 303 See Other in 642.204905ms

Description
after created a issue with default tags and a milestrone, try to added time tracking as 2 hours, got a Error 324 (net::ERR_EMPTY_RESPONSE): in the browser, using chrome
Screenshots

now after happened the bug the instalation cannot show any more at the browsers

i got it, after added the timetracking, the gitea tries to redirect to the configured domain url event the agnostc path.. so if we are outside with NAT will show localhost or whatever configured!

So you have to config your app.ini to set that with a outside NAT domain or IP.

noT, the app must make same as for rest of thigs, not use hard paths, due it's stupid if i inside the network (that are 100/1000 ) try to do with the external domain that are more slow!
when i touch the liabels, milestones etc, the gitea uses the current path url, not the hardcoded path.. specially if i foun it behing a reverse proxy

@lunny this are not a question, its a bug as same bug as in #5425 due many hardcoded path to a hijacked web root of the assumed web werver of the installations

this bug are causing issues in others due root url are kind of hardcoded from ROOT_URL as i described and today it 1.6.2 release and the bug is still happened!

stale bot marked in two weeks as closed! today 1.7.4 and no solution?


Doesn't compile with jdk 17+

it doesn't compile on jdk 17+, respectively, i can't use it on new versions of compose.
build log says:
Cannot inline bytecode built with JVM target 17 into bytecode that is being built with JVM target 1.8.

It was published with jvmTarget 17 by mistake. Technically it doesn't compile on target 16-.
You can workaround it now using
android {
    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_17
        targetCompatibility = JavaVersion.VERSION_17
    }

Next version will be published with target 11.

Please check 1.0.0-beta3


Getting more done in GitHub with ZenHub

Hola! @abhinav-mishra has created a ZenHub account for the floread-org organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

How do I use ZenHub?
To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.
What can ZenHub do?
ZenHub adds a series of enhancements directly inside the GitHub UI:

Real-time, customizable task boards for GitHub issues;
Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
Personal to-do lists and task prioritization;
Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub
Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @abhinav-mishra.

Guess everyone is on Zenhub so closing this.


@import should be hoisted to the top of the file

For example, the following LESS:
@font-face {
  font-family: "Epsilon";
  src: url('data:font/x-woff;base64,...')
}
@import url(//fonts.googleapis.com/css?family=PT+Sans+Narrow:400,700&subset=latin,cyrillic);

will be compiled by lessc as the following:
@import url(//fonts.googleapis.com/css?family=PT+Sans+Narrow:400,700&subset=latin,cyrillic);
@font-face {
  font-family: "Epsilon";
  src: url('data:font/x-woff;base64,...')
}

(it always put URL imports to top)
But dotless cannot do that and compiled CSS becomes invalid in many browsers. Example dotless output:
@font-face {
  font-family: "Epsilon";
  src: url('data:font/x-woff;base64,...')
}
@import url(//fonts.googleapis.com/css?family=PT+Sans+Narrow:400,700&subset=latin,cyrillic);

Thanks for reporting this. I will try to squeeze this into 1.5.

1.5.0-beta2 should be out within 15-30 minutes (depending on the AppVeyor build queue). The change should be included there.


What's new 1.16.0

PolygonID mainnet integration
PolygonID Twitter Attestations through Clique.Social
DeFi compliance SBT for BNB Chain


feat: add dropGroupByControl

🏆 Enhancements
POC of Explore drag and drop query panel. scope - Groupby control only.
link to: https://github.com/apache/superset/pull/13210

How about we name this dndColumnSelectControl? It's a control for selecting columns with drag and drop.

How about we name this dndColumnSelectControl? It's a control for selecting columns with drag and drop. We have deprecated groupby in QueryContext, so it's better to be consistent in control naming, too.

All right. I will rename it.


zsh completion lists variables along with recipes

Expected
When using ZSH, I expect just <tab> to list just the available recipes, just like it does when using Bash.
Actual
It lists all environment variables and just variables defined within the justfile. It does not list environment variables defined in a "dotenv" file.

Thank you for maintaining this over time. It's one thing to start a project; it's an entirely different thing to keep it up for 5½ years (a0d5b83a8008c4fec292fbacde61240141554fc3). I don't know how you do it.

Can you share a copy of your justfile, along with a screenshot of what you see when you type just <tab> in your terminal?

Thank you for maintaining this over time. It's one thing to start a project; it's an entirely different thing to keep it up for 5½ years (https://github.com/casey/just/commit/a0d5b83a8008c4fec292fbacde61240141554fc3). I don't know how you do it.

You bet! It's actually not so bad. I always fix bugs and respond to questions, and that isn't very hard. There are huge features that should be implemented, but I don't pressure myself to implement them, since I know doing that would burn me out pretty quickly.

Thanks for the details! Pinging @heyrict, who wrote the expanded zsh completion scripts.

It does not list environment variables defined in a "dotenv" file

Afaik this is the expected behavior. You may work around that by using other plugins

It lists all environment variables and just variables defined within the justfile

Not a bug. The completion style depends on your configuration. Try adding the following lines to your zshrc, which should group the completion by recipes and variables:
zstyle ':completion:*' group-name ''
zstyle ':completion:*:descriptions' format "%U%B%d%b%u"

@heyrict Thanks. How would I print only the commands?

@binyamin Try applying this patch to your _just completion script
--- /usr/share/zsh/site-functions/_just 2022-03-30 03:22:57.000000000 +0800
+++ _just   2022-04-06 17:07:03.102754922 +0800
@@ -114,9 +114,6 @@
 _just_commands() {
     [[ $PREFIX = -* ]] && return 1
     integer ret=1
-    local variables; variables=(
-        ${(s: :)$(_call_program commands just --variables)}
-    )
     local commands; commands=(
         ${${${(M)"${(f)$(_call_program commands just --list)}":#    *}/ ##/}/ ##/:Args: }
     )
@@ -126,7 +123,6 @@
             *) _message 'value' && ret=0 ;;
         esac
     else
-        _describe -t variables 'variables' variables -qS "=" && ret=0
         _describe -t commands 'just commands' commands "$@"
     fi

@heyrict perfect, thank you.
@casey Should I close this now? I still don't think this is expected behavior.

@binyamin  Please check this section in case you still think that is not expected. just os=plan9 test is a valid command to set variables, and the completion script won't know if you mean to type variables or recipes at the stage of just <Tab>.

@heyrict thank you, I must have missed that section


Update Go guidance for attributes

In service towards https://cloud-native.slack.com/archives/CJFCJHG4Q/p1706816394957449

While I have nothing against the changes I just want to point out that in my opinion the description is misleading

In service towards https://cloud-native.slack.com/archives/CJFCJHG4Q/p1706816394957449

See: https://github.com/open-telemetry/opentelemetry.io/pull/3927#pullrequestreview-1861131249

@cartermp @open-telemetry/go-approvers is this PR something we want to continue?

The content and title LGTM.
However, I do think that the description is true.
More: https://github.com/open-telemetry/opentelemetry.io/pull/3927#issuecomment-1952311697.
CC @MrAlias

However, I think that the description is not true. More: #3927 (comment).

@cartermp does this help you to finalize this PR?

gonna close this one out, it's been rather long


Create local database

Create a database and populate it with dummy data.
Instruction on how to access it are found in backend/README.md
The db structure is based on https://drive.google.com/open?id=1tZOHUczPERUcGlcnM7P4wwMiSAwdHCuH
HOWEVER I didn't know how to make a list of preferred dates in an SQL database, so I created a separate table for that.

Looks good to me.
Just one question to check I've understood correctly, were we able to get rid of the schema.sql script because the table structures are set up in the java classes?

Right, jpa construct the database automatically from the dto objects (@Entity annotation does this, I believe), so there is no reason for schema.sql anymore.


bug fix env.close()

Exception ignored in: <function Monitor.del at 0x10b1c8bf8>
Traceback (most recent call last):
File ".../lib/python3.7/site-packages/gym/wrappers/monitor.py", line 233, in del
File ".../lib/python3.7/site-packages/gym/wrappers/monitor.py", line 134, in close
File ".../lib/python3.7/site-packages/gym/core.py", line 248, in close
File ".../lib/python3.7/site-packages/gym/core.py", line 248, in close
File ".../lib/python3.7/site-packages/gym/envs/classic_control/cartpole.py", line 192, in close
File ".../lib/python3.7/site-packages/gym/envs/classic_control/rendering.py", line 62, in close
File ".../lib/python3.7/site-packages/pyglet/window/cocoa/init.py", line 281, in close
File ".../lib/python3.7/site-packages/pyglet/window/init.py", line 770, in close
TypeError: 'NoneType' object is not callable

Thank you!


Add NLP demo

Hopefully all the links are correct, can't really prove that until it's merged and I test it again from master.

Updated as per comments

Made suggested changes


Why ROME dose not support bf16 and fp16?

Flashattention is widely adopted, and it dose not support fp32. It is not convenient to train a model without bf16

In theory, ROME only involves modifications to the FFN layer and can support the usage of Flash Attention.
Thank you for your suggestions, we will support bf16 or fp16 as soon as possible.😊

Sorry for the late reply. I hope everything is going well with you recently.
Thanks for your sincere suggestion, the latest version of EasyEdit has supported editing the fp16 model through ROME, and the actual test has saved 10G of GPU memory on LlaMA-7B, welcome you to actively try. 😊

If this reply solves your problem, please help me close this issue. 😊


Add/Modify switches

This is great work Miguel.
Have you tested both the adding of new switches and the editing of existing ones?

This is great work Miguel.
Have you tested both the adding of new switches and the editing of existing ones?

yup, I can record a demo video if you'd like


Allow Creation of oauth2 User through the API

Feature Description
I think it would be amazing if you could support oauth2 user's creation from the api.
Let say i would like to create a "Google" Gitea User, so when the user will log in with google it would link his account to the gitea user i created.
It's already supported through the WebUI cf screenshot
For example i would like to automate the user's creation this way :
  response = requests.post(
      f"{https://gitea.io/api/v1/admin/users}",
      json={
          "authenticationSource": "Google", (to override the default value: local)
          "visibility": "Private",
          "authenticationSigninName": google_id,
          "username": username,
          "email": email,
          "sendNotification": True
      },
      headers=headers,
      verify=False
  )

Thanks in advance :pray:
Screenshots

Would be a really helpful feature! In my case I'm trying to connect keycloack for authentication. For automatic user creation via API it needs an auth sourceID (which is possible to extract only manually from the Gitea UI). If I could assign an authentication source using its name - all  problems solved. :)

This test seems to show a way to do it
https://github.com/go-gitea/gitea/blob/b2b49c9bde63b311f01d500ada9212c46b9602fe/tests/integration/admin_user_test.go#L52-L68


DECT 210: temperature stopped sending data

Describe the bug
Since December 20th the device stopped sending temperature data, or at least to record the data. The device itself has not been touched/modified. What really is strange is that the power switching does still work correctly, even via automation in the EVE app. Might be that this is an issue with the fakegato?
To Reproduce
Open the eve app and check the temperature history for the DECT 210. No new data is shown.
Expected behavior
It has been working before...so that is what I would hope to reach again.
Screenshots
n/a
Desktop (please complete the following information):
OS: Windows 10
Smartphone (please complete the following information):
iPhone with iOS15.2
Additional context
Since the beginning homebridge reports the following log lines during startup of the plugin:

3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatform WarnungDECT 210 Temperature: Multiple devices are configured with this name. Duplicate devices will be skipped.
3.1.2022, 17:46:37Fritz Platform BridgeBridge is running on port xxxxxx.
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformFritzBox Wifi guest: Configuring cached accessory...
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformDECT 210: Configuring cached accessory...
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformDECT 210 Temperature: Configuring cached accessory...
(...)
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformFritzBox Wifi guest: Setup accessory...
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformDECT 210: Setup accessory...
3.1.2022, 17:46:37Fritz Platform BridgeFritzPlatformDECT 210 Temperature: Setup accessory...
(...)

This warning has been there from the beginning, so I am not sure if that has something to do with the issue.
The relevant config.json-part is:

"smarthome": [
                {
                    "active": true,
                    "name": "DECT 210",
                    "ain": "11234 0123456",
                    "energy": true,
                    "temperature": true,
                    "accType": "switch"
                },
                {
                    "active": true,
                    "name": "DECT 210 Temperature",
                    "ain": "11234 0123456",
                    "accType": "temperature"
                }
            ]

To the above issue: cannot not cofirm, possibly influenced by other software.
BTW: is an readout of the powercomsumption (kWh) yet implemented?
I always wondered, if the "energy" option offers that possibility.
Cheers, keep the good work coiming...


Feature request: Provide Dockerfile for easier development and production deployment

It'd be really convenient to deploy CyberChef - either for development or in containerized environments like ECS/CapRover/GCP - using a Dockerfile.
Previous relevant issues and PRs are:

#474
#1215
#1140
#670
#675
#677
#178

Would also really like Docker support. Even if images aren't published to DockerHub or GHCR, an official Dockerfile would be nice (I could build the container myself with Compose).
It seems silly (and kind of a potential security issue) that I'm running code from GCHQ, but having to rely on random third-party images (or make my own).
Searching on DockerHub, there are a ton of images, but nothing official.
https://hub.docker.com/search?q=cyberchef

We now support dev containers and automatically build images to GCHR.