WIP: groupHistory: created components

closes #177 and #213

Codecov Report

Merging #333 into dev will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev     #333      +/-   ##
==========================================
+ Coverage   98.68%   98.71%   +0.02%
==========================================
  Files         152      160       +8
  Lines        2213     2254      +41
==========================================
+ Hits         2184     2225      +41
  Misses         29       29

Impacted Files
Coverage Δ

...nt/app/components/group/groupDetail/groupDetail.js
100% <ø> (ø)
:white_check_mark:

...ient/app/components/group/_history/history.spec.js
100% <100%> (ø)

...pp/components/group/_history/history.controller.js
100% <100%> (ø)

client/app/components/group/_history/history.js
100% <100%> (ø)

...nts/group/groupDetail/groupHistory/groupHistory.js
100% <100%> (ø)

...groupDetail/groupHistory/groupHistory.component.js
100% <100%> (ø)

...roup/groupDetail/groupHistory/groupHistory.spec.js
100% <100%> (ø)

...roupDetail/groupHistory/groupHistory.controller.js
100% <100%> (ø)

...app/components/group/_history/history.component.js
100% <100%> (ø)

... and 7 more

Continue to review full report at Codecov.

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

Can you separate the profile picture into a separate PR? I think it could take a while until we have the backend ready for it and I would like to have the history in production before that.

the current solution doesn't require the backend implementation, it only generates  default custom avatars without requesting one from the backend.
Without the avatar we would have to touch the history design twice, or with removing it: thrice.
But now it is already done ;)
so far everthing is done here, except:

[ ] review - maybe a better solution?

[ ] storeName in payload, to save the name permanently and avoiding a unnecessary complex frontend
(would require a controller for each history-typus to resolve the missing data)

[ ] adding all the missing typus strings

I will

add the missing strings
add some tests
add the store name to PICKUP_DONE payload


A warning during training

I faced a warning during training this code on coco2014.
train_vocab_w2v.py:367: UserWarning: Output "nms" missing from loss dictionary. We assume this was done on purpose, and we will not be expecting any data to be passed to "nms" during training.   optimizer=keras.optimizers.adam(lr=1e-5, clipnorm=0.001) 202 209
But this warning did not affect the running process. I want to know whether this warning will affect the performance of trained models. If so, how can I avoid this warning during my training process? I appreciate that if you can help me to solve this problem. Thank you for your attention.

You can ignore this warning. It should not affect performance.


v3: (proposal) install puppeteer dependencies with env variable PUPPETEER="true"

Proposal only
Changelog
Added condition to base docker image to optionally install chrome-stable linux/amd64 dependencies by supplying --build-arg="PUPPETEER=true" or process.env.PUPPETEER="true/core/...". Omitting the arg builds the image as previously.
Dockerfile:
# syntax=docker/dockerfile:labs

FROM node:18-slim AS base

# ENV DEBIAN_FRONTEND=noninteractive
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
ARG PUPPETEER_DEPS

# Install Google Chrome first to improve build time
RUN if [ "$PUPPETEER" = "true" ]; then \
      apt-get update && apt-get install -y wget gnupg \
      && wget --quiet --output-document=- https://dl-ssl.google.com/linux/linux_signing_key.pub | gpg --dearmor > /etc/apt/trusted.gpg.d/google-archive.gpg && \
      sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
      apt-get update && \
      apt-get install google-chrome-stable -y --no-install-recommends && \
      rm -rf /var/lib/apt/lists/* \
    # elif [ "$PUPPETEER" = "chrome-stable" ]; then \
    #     apt-get update && apt-get install -y puppeteer; && npx puppeteer browsers install chrome-stable \
    else \
        echo "Skipping puppeteer install"; \
    fi

RUN apt-get update \
  && apt-get install -y dumb-init

FROM base

WORKDIR /app

COPY --chown=node dist/index.mjs /app/

EXPOSE 8000

ENTRYPOINT [ "/usr/bin/dumb-init", "--", "/usr/local/bin/node", "/app/index.mjs" ]

🤔
Experimental Packages:
docker pull ghcr.io/turnout-labs/docker-provider:latest
docker pull ghcr.io/turnout-labs/docker-provider-chromium:latest
💯

The Containerfile used for building worker images is here:
https://github.com/triggerdotdev/trigger.dev/blob/main/packages/cli-v3/src/Containerfile.prod
I think we're going to expose an addOns option to trigger.config.ts that allows bundling extra dependencies to the worker Containerfile, something like this:
export const config: TriggerConfig = {
  addOns: ['puppeteer'],
};

I think we're going to expose an addOns option to trigger.config.ts

That's a good approach combined with something like the above build changes. But I don't think this will be enough to run properly in prod as the containers may require different permissions. Will have to test and investigate.


Large number of depreciation warnings

Information

Qiskit Terra version: master
Python version:
Operating system:

What is the current behavior?
Simply calling transpiled_circ = transpile(qc, backend) gives me:
/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:272: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

/opt/miniconda3/lib/python3.7/site-packages/qiskit_terra-0.14.0-py3.7-macosx-10.9-x86_64.egg/qiskit/transpiler/passes/routing/stochastic_swap.py:383: DeprecationWarning:

edge_map arg as a dictionary is deprecated. Use qubits and clbits args to specify a list of self edges to compose onto.

### Steps to reproduce the problem

### What is the expected behavior?

### Suggested solutions

Yeah, I've noticed this now too we should fix this prior to the 0.14.0 release. Either remove the deprecation or update the usage in terra to not use the deprecated input for compose() in any of the passes


Getting duplicate folders displayed when viewing SMB network share with "Continue where you left off" turned on

Describe the bug
I had turned on "Continue where you left off", close a window which was viewing a SMB network share the other day and when I opened it today, it was displaying a duplicate of each file and folder in there. When I refreshed the window, an additional duplicate of each was displayed as seen in the screenshot below.
To Reproduce
I simply opened the Files app and the duplicates were there.
Expected behavior
Simply show the current folders and files
Screenshots

Desktop (please complete the following information):

OS Version: Windows 10 Version 10.0.19041
App version: [v<IP_ADDRESS>]

Log file
Please upload the log file here so that we can understand your issue better. You can access it from Settings->About->Open log location. You can also find the log file manually by following this guide.
The only debug information present for today was the following:

debug_fulltrust.txt
2021-01-16 19:23:31.4212|INFO|.ctor|App launched|
2021-01-16 19:23:31.6197|WARN|.ctor|Can't get storage device name: Access is denied. (Exception from HRESULT: 0x80070005), skipping...|
2021-01-16 19:23:31.7387|INFO|.ctor|Drive added: C:\, Fixed|
2021-01-16 19:23:31.8612|INFO|.ctor|Drive added: E:\, Fixed|
2021-01-16 19:23:31.8952|INFO|.ctor|Drive added: H:\, Fixed|
2021-01-16 19:23:31.9767|INFO|.ctor|Drive added: X:\, Network|
2021-01-16 19:23:32.2607|WARN|.ctor|System.UnauthorizedAccessException: Attemting to add the device, SSK Storage, failed at the StorageFolder initialization step. This device will be ignored. Device ID: \\?\STORAGE#Volume#{d29020d8-e3e6-11ea-8cf5-b42e99a3f69c}#0000000000200000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}|

debug_fulltrust.txt
2021-01-16 19:23:32.5187|INFO|FilesFullTrust.QuickLook|QuickLook detected: False|
2021-01-16 19:23:33.1572|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.4457|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.4887|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.5397|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.5807|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.6237|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.6727|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.7157|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:33.7722|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.1677|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.2062|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.2467|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.2863|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.3278|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.3678|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:51.4103|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:53.1128|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:53.1540|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:53.1980|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:53.2395|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:53.2835|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.3602|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.4278|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.5272|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.5728|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.6237|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.6742|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.7257|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.7622|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.7992|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.8417|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.8812|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:23:55.9212|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:23.7479|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:23.7936|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:23.8377|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:23.8832|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:25.1348|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:25.5745|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:25.6205|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:25.6645|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:25.9880|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:26.0305|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:26.0720|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:26.1150|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|
2021-01-16 19:24:26.1605|INFO|FilesFullTrust.Program|Argument: GetIconOverlay|

@MostHated Thank you for opening this issue, it should be resolved with the latest update in the store. Please let us know if this is still an issue after updating to v1.1.

@MostHated Thank you for opening this issue, it should be resolved with the latest update in the store. Please let us know if this is still an issue after updating to v1.1.

My apologies, I didn't receive any sort of notification that an update was available for some reason. I did just do the update and reopened it. They were there again for a quick second, but then disappeared right away.

My apologies, I didn't receive any sort of notification that an update was available for some reason. I did just do the update and reopened it. They were there again for a quick second, but then disappeared right away.


删除任务bug

在删除任务的时候接口报错
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
接口报错："\n\n  \n    \n    \n    \n    \n    \n    \n  \n  \n
\n
NameError
\n
\n
NameError: name 'stop_task' is not defined
\n
\n
Traceback (most recent call last)
\n
\n
\n
\n
File "/usr/local/lib/python3.8/dist-packages/flask/app.py",\n      line 2095,\n      in call
\n
def call(self, environ: dict, start_response: t.Callable) -> t.Any:
\n
"""The WSGI server calls the Flask application object as the
\n
WSGI application. This calls :meth:wsgi_app, which can be
\n
wrapped to apply middleware.
\n
"""
\n
return self.wsgi_app(environ, start_response)
\n
\n\n
![image](https://github.com/Bron

自行构建和提供的镜像都试过，都会有这个报错

我也是，希望能解决一下


Are there limitations on the symbols which can be used?

I've compiled the code and try it out on some data I have. However, I get the error:
[ERROR]: Assertion failed in /tmp/psac/include/check_suffix_array.hpp:262

I don't get this error when using the random data supplied in this package. Are there some limitations regarding what symbols/encodings/characters can be used?

Can you share your input file so I can try to reproduce the problem? Thanks

Thanks, find the file attached below! IDK, maybe I did some mistake when compiling, looks pretty innocuous to me.
tiny.json

Maybe it's a matter of encodings. What encodings does the program expect? Thanks!

The default one expects ascii (one byte per character). There's some support for 2byte alphabets and integer alphabets, but I don't think I tested that very well.


add divider & section header distinguish between settings for current series vs. app-wide

The Reading mode dialog in Reader has mixed of settings for current series only & App-wide settings.
This PR add a divider and clarify the settings apply app-wide.

There are too many headers, tbh. Maybe make it capitalized?

A redesign is planned. This'll suffice for now.

A redesign is planned. This'll suffice for now.

should I close this then?


Boolean && should either always break or never break

First pass at implementing #89
This isn't ready to be merged yet, and I'm probably going to rewrite all of it, but I'm putting it up for discussion in case anyone has any insight on the problems I'm seeing.

Thanks for the PR! You dug into a hairier problem and got pretty far, good job. I think we can make this code clearer though, as well as improve performance. Some of the problems I see:

collectLogicalExpressions is recursive, and while I love recursion and functional programming, I'm very sensitive about perf in this project and it will easy degrade if we're not careful everywhere (death my a thousand cuts). We should do imperative iteration. Also the pairs machinery looks like a lot of work; I think we can simplify it.
I'm not sure why we need isStartOfLogicalExpressionChain? Can't you just check if chain.length > 1 ?
Do we not want this for binary expressions as well? Maybe not, but we need to solve similar problems for binary expressions... we could start with just logical though.

I had already started this work on another branch. Here's my complete implementation so far:
  case "BinaryExpression":
  case "LogicalExpression":
    const binaryExprs = []
    let curr = n;
    while(curr.type === "BinaryExpression") {
      binaryExprs.push({ right: curr.right, op: curr.operator });
      curr = curr.left;
    }
    binaryExprs.reverse();

    if(binaryExprs.length > 0) {
      return group(concat([
        // TODO: create correct paths
        print(FastPath.from(curr)),
        indent(options.tabWidth,
               concat(binaryExprs.map(expr => {
                 return concat([" ", expr.op, line, print(FastPath.from(expr.right))]);
               })))
      ]));
    }

    return group(concat([
        path.call(print, "left"),
        " ",
        n.operator,
        indent(options.tabWidth, concat([ line, path.call(print, "right") ]))
    ]));

While I need to fix a few things, and it applies it to binary expressions too, I believe this achieves similar results with a lot less code. Do you mind if I take this bug because there were a few things I wanted to look into while doing this?

Agreed on all points.
I have another version form this morning that gets rid of isStartOfLogicalExpressionChain and uses multilineGroup instead of conditionalGroup, and is way less code, but there are still some more issues with it that I haven't figured out yet. If you have something that's close I'm happy to let you take it :)

One thing I wanted to figure out was getting rid of those FastPath.from calls because that breaks a few things because the nodes don't have context anymore (i.e. a link back to the parent). We are using that in 1 or 2 other places. I think there was a couple other things I wanted to look at too.
Hope this doesn't discourage you, there are several other bugs that would be great to have fixed!

I can't wait to have this feature in!


NASA API website

I just looked at the NASA API website and there it asks me to register with an API key.
Maybe I am getting something wrong here, but if not I would love to fix this. I haven't really done much open source work, but I would love to change that.
Here is the link: https://api.nasa.gov/
Someone who wants to join and help can click it.

Signing up for an API key is free.

There are many APIs at NASA. Some asks for API Keys, Some don't.
For each API, there are the parameters, if there is apikey parameter, it will ask for it. Some really need it, and some just gives more options to use.
It's quite complicated. Some APIs offer a number of requests for free and then requires an authentication. Currently, we try to display the first accessible option.
NASA case is even more complicated since they offer a list of APIs with different authentication processes. So, from my POV, we should stick with the first accessible option which is authentication.

There are many APIs at NASA. Some asks for API Keys, Some don't.
For each API, there are the parameters, if there is apikey parameter, it will ask for it. Some really need it, and some just gives more options to use.
It's quite complicated. Some APIs offer a number of requests for free and then requires an authentication. Currently, we try to display the first accessible option.
NASA case is even more complicated since they offer a list of APIs with different authentication processes. So, from my POV, we should stick with the first accessible option which is authentication.

Thank u guys！


Free pascal?

Wondering if it would work with free pascal, lazarus...

应该是没问题的。有问题请反馈。

Yes, it should work. Lets improve the FPC/Lazarus compatibility?
With Lazarus 1.6.0 and FPC 3.0.0. Testing another day, after an auto conversion of the prjPackAndUnpack project to lazarus project by means of the built in conversion tool, the following messages occurred:
Compile Project, Target: prjPackAndUnPack: Exit code 256, Errors: 4
SimpleMsgPack.pas(93,7) Error: Incompatible types: got "AnsiString" expected "Int64"
SimpleMsgPack.pas(93,7) Error: Compile time expression: Wanted Boolean but got <erroneous type> at IF or ELSEIF
SimpleMsgPack.pas(97,7) Error: Incompatible types: got "AnsiString" expected "Int64"
SimpleMsgPack.pas(97,7) Error: Compile time expression: Wanted Boolean but got <erroneous type> at IF or ELSEIF

Same discussion here http://forum.lazarus.freepascal.org/index.php/topic,33762.msg219285.html#msg219285

Some suggestions, please let me know if it fits your requirements for a pull request.
program prjPackAndUnPack;

{$MODE Delphi}

uses
  Forms, Interfaces,
  ufrmMain in 'ufrmMain.pas' {Form2},
  SimpleMsgPack in '..\..\SimpleMsgPack.pas',
  uByteTools in 'uByteTools.pas',
  DMsgPackHelper in '..\..\DMsgPackHelper.pas';

{.$R *.res}

begin
  {$IFNDEF FPC}
  ReportMemoryLeaksOnShutdown := true;
  {$ENDIF}
  Application.Initialize;

  {$IFDEF WINDOWS}
  Application.MainFormOnTaskbar := True;
  {$ENDIF}

  Application.CreateForm(TForm2, Form2);
  Application.Run;
end.

For the other files, appending the following code right after the {$MODE DELPHI} directive allowed me to compile the project:
// use DELPHI 7 versions
// http://wiki.delphidabbler.com/index.php/Notes/VersionNumbers
{$IFDEF FPC}
  {$MACRO ON}
  {$define RTLVersion :=  15}
  {$define CompilerVersion := 15}
{$ENDIF}

Useful links for me:

http://www.freepascal.org/docs-html/prog/progse5.html#x138-1390002.2
http://www.freepascal.org/docs-html/prog/progsu48.html#x55-540001.2.48

Getting errors while pressing the test buttons with v. 15.
No errors using the following versions.
{$IFDEF FPC}
{$MACRO ON}
{$define RTLVersion :=  25}
{$define CompilerVersion := 18}
{$ENDIF}

你好,  最近几天没关注github。
由于我没有FPC环境，一些错误我无法调试。
我已经邀请你加入该项目，希望能和你一起完善该项目。希望你能加入。

Thank you, I hope to be a valuable contributor. I will work by Pull Request', anyway. Please, if you have any interest and when you find the time, take a look at the Lazarus 1.6. It is awesome.


how to export json source for Grafana

Json data sources that suitable grafana require manually supplying urls: /, /search, /query, /annotations. Optional urls: /tag-keys, /tag-values.
What methods should I use in appmetrics to provide access to url requests?
ref: https://github.com/grafana/simple-json-datasource

Not sure what is meant by "provide access to url requests?"
In terms of "how to export json source for Grafana" refer to Grafana's docs


Create list of pre-written commonly used named replacement patterns

I think #9 + #10 (docs examples) is more than enough.


[HOLD for payment 2023-12-12] [Theme Switching] Enable theme switching for status and scrollbar colors

We need to ensure that the status bar and scrollbar both change when the theme is changed cc @chrispader

comment for assigning :)

Sent offer here

Contributor+: @fedirjh paid $500 via Upwork.
Apologies @fedirjh


Do we still need helm-tiller plugin installed for Helm3?

In Dockerfile.helm3 we install helm-tiller plugin which is useless there.

Thanks, We should definitely remove it!


Remove NextJS' Incremental Static Regeneration

📚 Context
While we were working on a completely different thing (#623), @snehankekre noticed a performance issue on the API reference page (see comment).
Upon doing some research and testing, I noticed we were using NextJS' ISR in our pages, which is not compatible with static exports.
Removing that directive makes the static HTML export work again, making the site super fast, and (I believe) not causing any visualization issues nor errors.
🧠 Description of Changes

Removed revalidate: 60, from the return statement in getStaticProps;

💥 Impact

Size:

[x] Small
[ ] Not small

🌐 References

Unblocks #623

Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.

Thanks for the context, it helps! 😃

You can check the performance boost on the deploy preview generated by this PR

I'm likely doing something wrong, but I don't see a performance boost. It is identical to that of https://docs.streamlit.io (both API ref pages load almost instantly). Perhaps if these changes were in the components PR deploy preview we could see an improvement?

Even with the changes merged, the load time issue on /library/api-reference remains the same IMO. It's still taking around 6.5 seconds to render 🤔
Is it similar on your end?

Even with the changes merged, the load time issue on /library/api-reference remains the same IMO. It's still taking around 6.5 seconds to render in the components deploy preview.

Yeah, you're right. Let me circle back with @sfc-gh-tteixeira tomorrow and get back to you!

Should this PR be closed, given we fixed the performance issue in #623? Or are there merits to removing ISR? Namely, making static exports work again?

Should this PR be closed, given we fixed the performance issue in https://github.com/streamlit/docs/pull/623?

Yes, sorry! Closing now.

Or are there merits to removing ISR? Namely, making static exports work again?

There are merits to do that, but we're also doing it in #623, so no need for this PR anymore 👍


Display the version number somewhere on the production server. We need an "about" screen somewhere?

Transferred from MAVC. Still feels very relevant


Fix forms.py for Django >= 1.8

Django 1.8+ requires either exclude or fields meta in the ModelForm.

Hi, thanks for the request. There are more fixes required in order to make it works with Django 1.9. I'll try to fix it, but I haven't worked with Django for ages and so it may take time. If you need it running now, better use your fork until I update pip package.

Make sense, we already have a fork that we are using with Django 1.8[1] it's working fine.
Not sure, about django 1.9 though, maybe we have a release for Django 1.8 as it's LTS and the later add support for 1.9, thoughts?

Even if you just merge this one, we can use the latest master commit hash from this repo. I'll help out with Django 1.9 once we move on there.

Done, in master.


Job posting location test

We want to run a quick test on job aggregators' ability to read location data before our current job postings close early next week by adding a temporary hard-coded section to the job posting template
Additions

Temporary hard-coded list of cities associated with a job region

Testing

Check out branch
In admin, create (or update) a job posting in one of the 4 multi-state regions (West, Midwest, Southeast, Northeast)
Navigate to job posting page and verify in dev tools that a hidden "location" section appears after the region section at the top of the page

Screenshots

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewer tool :arrow_right:

Thanks, @chosak!


Add RuboCop project description to .pre-commit-hooks.yaml

This PR adds a description to  .pre-commit-hooks.yaml which enables this description to appear on the main list of pre-commit hooks (https://pre-commit.com/hooks.html).

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Popup shows unwanted completions when triggered manual

I'm currently using
let g:cm_auto_popup = 0
imap <C-Space> <Plug>(cm_force_refresh)

When I use this I notice that I get results in some of my completions that make no sense to me.

My expected result would be the same as with cm_auto_popup enabled

I've found a workaround for this issue.
When looking through your source code I found out that  changing cm_force_refresh fixed my issue.
func! cm#_force_refresh()
	" force=1
	call s:notify_core_channel('cm_refresh',g:_cm_sources,cm#context(),0)
	return ''
endfunc

What I did was change the 1 into 0.
I'm using nvim-cm-tern in my examples

Concluded that this is a terrible workaround... This only worked in JS for me. In Golang this will result in NCM not finding any completion; In my experience.

That's line completion.
Line completion is a non auto popup source, it's only triggered by <Plug>(cm_force_refresh)
It has lower priority so it's at the bottom of the menu.
You could disable it with g:cm_sources_override

I'm wondering:

Do you think we should add a mark to each item so that you know which source it's comming from? So that you know where to disable it.
Do you think manual completion should popup the same results as auto-popup?
How should manual completion behave while keeping the line completion source?

Here is a brief explanation of current behavior:
<Plug>(cm_force_refresh) activates all sources according to current file type. And it ignores the sources's cm_refresh_length. For example, with buffer keyword completion,
It auto pops up when you has typed four characters foob|, by default, But with manually completion, it's triggered for only one character. f|
Activates all souces could be annoying. But it seems it's needed in some use cases, for example, when you don't know what more to type to trigger the menu.

My proposal:

Add a mark into each completion item.

We could setup another config variable cm_manual_refresh_length, like
cm_refresh_length, but only used for manual completion.

As for the line completion source, it should only be triggered by manually,
and only when the cursor is at the beginning of a word, before typing a
character. It should be hidden when suggestions with higher priority is
available.

// cc @rafaeln

fixed in ncm2 <Plug>(ncm2_manual_trigger) has almost the same behavior of auto trigger


Inventory Valuation report do not support filtering on Bin level

In this section on this page:
**Filter totals by
Some lists that display calculated fields, such as amounts and quantities, will include the Filter totals by section where you can adjust various dimensions that influence calculations. To add a filter, choose the + Filter action. Then, type the name of the field that you want to filter the list by or pick a field from the drop-down list.**
In the older doc there is further clarification from a user perspective what this is about:
https://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2016/hh179511(v=nav.90)?redirectedfrom=MSDN
In support we get cases for why they can't use the "Filter Totals to" for 'Bin Codes' in the Inventory Valuation report.

Document Details
Report Limit totals to.docx
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 802c5ab2-6384-9f67-586f-8de66cd361cc
Version Independent ID: 12fb39ec-1f3c-e49b-de9c-7d9d09b29fc4
Content: Sorting, Searching, and Filtering Lists - Business Central
Content Source: business-central/ui-enter-criteria-filters.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Thank you for bringing this issue to our attention. Bin Filter information will be added and reflected in our documents during the next doc refresh. We hope that you find it useful.


PR Body: Handle case where the total rounds down to 0%

Let's rewrite to "Your file size has been reduced! " in the case of 0

Logic needs to be inserted here: https://github.com/dabutvin/ImgBot/blob/master/OpenPrFunction/PullRequestBody.cs#L59
Test needs updated here:
https://github.com/dabutvin/ImgBot/blob/master/Test/PullRequestBodyTests.cs#L33


Could not find a suitable constructor in com.netflix.titus.gateway.endpoint.v3.SupplementaryServiceLocationConfiguration

When running the current master branch, this error occurs in the gateway service:
Could not find a suitable constructor in com.netflix.titus.gateway.endpoint.v3.SupplementaryServiceLocationConfiguration. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
gateway_1       |   at com.netflix.titus.gateway.endpoint.v3.SupplementaryServiceLocationConfiguration.class(SupplementaryServiceLocationConfiguration.java:17)
gateway_1       |   while locating com.netflix.titus.gateway.endpoint.v3.SupplementaryServiceLocationConfiguration
gateway_1       |     for the 1st parameter of com.netflix.titus.gateway.endpoint.v3.ConfigurableReactorHttpClientFactory.<init>(ConfigurableReactorHttpClientFactory.java:18)
gateway_1       |   at com.netflix.titus.gateway.endpoint.GatewayEndpointModule.configure(GatewayEndpointModule.java:26) (via modules: com.google.inject.util.Modules$CombinedModule -> com.netflix.titus.gateway.startup.TitusGatewayModule -> com.netflix.titus.gateway.endpoint.GatewayEndpointModule)
gateway_1       |
gateway_1       | 1 error
gateway_1       | 	at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:470)
gateway_1       | 	at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
gateway_1       | 	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
gateway_1       | 	at com.google.inject.Guice.createInjector(Guice.java:99)
gateway_1       | 	at com.google.inject.Guice.createInjector(Guice.java:84)
gateway_1       | 	at com.netflix.governator.LifecycleInjectorCreator.createInjector(LifecycleInjectorCreator.java:100)
gateway_1       | 	at com.netflix.governator.LifecycleInjectorCreator.createInjector(LifecycleInjectorCreator.java:38)
gateway_1       | 	at com.netflix.governator.InjectorBuilder.createInjector(InjectorBuilder.java:209)
gateway_1       | 	at com.netflix.governator.InjectorBuilder.createInjector(InjectorBuilder.java:230)
gateway_1       | 	at com.netflix.titus.gateway.startup.TitusGateway.main(TitusGateway.java:60)

It is probably due to the inject of SupplementaryServiceLocationConfiguration in class ConfigurableReactorHttpClientFactory while SupplementaryServiceLocationConfiguration has a constructor with a Config parameter but without an inject
ConfigurableReactorHttpClientFactory >
https://github.com/Netflix/titus-control-plane/blob/670719bcd785758ce696ea1e877ee57d7b9d1242/titus-server-gateway/src/main/java/com/netflix/titus/gateway/endpoint/v3/ConfigurableReactorHttpClientFactory.java#L18
SupplementaryServiceLocationConfiguration.java >
https://github.com/Netflix/titus-control-plane/blob/0c74f92e953d6e2422f69e7f8a8d072deb4cd0c0/titus-server-gateway/src/main/java/com/netflix/titus/gateway/endpoint/v3/SupplementaryServiceLocationConfiguration.java#L17

@dan-at-teza Something like that is missing, but I am trying to run the latest master commit (https://github.com/Netflix/titus-control-plane/commit/25e125559b4165cc02e4a4e8772c79df3a13186f). I am trying to use the docker-compose way as described in the Readme. No files have been changed in my local environment. After running docker-compose up -d the gateway exits immediately with previously mentioned error message. So I am wondering if it is a local problem?


Unable to stop query / poor handling of long running queries

Version 1.4.5
Commit 887f4e8985023602e599cf86bdb44df48bb28569
Date 2019-02-12T06:20:08.633Z
VS Code 1.26.1
Shell 2.0.9
Renderer 61.0.3163.100
Node 8.9.3
V8: 6.1.534.41
Architecture x64
Unfortunately, I have come across many cases of long running queries (loops/cursors), especially when using WHILE, where once the query starts there is no way of stopping it and to recover proper ADS functioning other than application restart.
Sometimes you want to break due to unnoticed at error at run time, in others - just to optimize.
I had several scenarios to that, including:

The query starts, a procedure could be run in a loop, you try to push stop button many-many-times without any effect (the results keep coming in messages pane). When you push the DISCONNECT, the session gets disconnected, but cannot properly reconnect - the application cannot attain connection. Restart helps

In some cases if you push stop (which doesn't work) and leave the application running, you will get

This might have been caused by memory over-usage
I do not have reproduction steps that I could share

I have seen this problem also in situations where e.g. a WHILE would produce many result sets and keep producing them not allowing the user to stop the query. "While" (pun intended) not the prettiest example, you should get the point:
WHILE 1=1
BEGIN
[do some processing]
select * from #errors
IF @ROWCOUNT = 0 BREAK       -- wrong operator, there should be > , which makes it never break
END

I had this problem with a long running loop, example number 3.
Eventually the app crashed on me.


Hi, On Windows 2016 box, docker version 1.12.0. Trying to run multiple docker run commands in parallel randomly throws up errors.

----------------------docker version
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 23:54:00 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 23:54:00 2016
 OS/Arch:      windows/amd64

---------------docker info-------------
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.0
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: nat null overlay
Swarm: inactive
Security Options:
Kernel Version: 10.0 14300 (14300.1045.amd64fre.rs1_release_svc.160705-1059)
Operating System: Windows Server 2016 Datacenter Technical Preview 5
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 3.5 GiB
Name: vm-windkr-srv4
ID: SUCD:6AB7:XCW6:D643:2SLZ:XQGD:V6SB:VBGI:AQ2L:4PKK:27KP:QX6F
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Windows 2016 box in Azure - 2 core
Steps to reproduce the issue:
1. 1..10 | %{start-process docker 'run --rm microsoft/windowsservercore ping -n 10 <IP_ADDRESS>'}

Describe the results you received:
Few times it runs OK, but it starts giving errors randomly. Keep repeating the command then the system itself becomes un-usable and not able to run even one container.
stopped dockerd as service and Ran the dockerd in the command prompt to see the error o/p
Error got------------------
time="2016-08-11T04:56:34.493910700Z" level=error msg="container c68cfb33fc431024547dcf0fcf90572c22879e69e39cd828fb74db4e51f9142b encountered an error during CreateContainer failed in Win32: The system cannot find the file specified. (0x2) extra info: {\"SystemType\":\"Container\",\"Name\":\"c68cfb33fc431024547dcf0fcf90572c22879e69e39cd828fb74db4e51f9142b\",\"Owner\":\"docker\",\"IsDummy\":false,\"VolumePath\":\"\\\\\\\\?\\\\Volume{8290d4bb-5e00-11e6-8a17-92c690498fee}\",\"IgnoreFlushesDuringBoot\":true,\"LayerFolderPath\":\"C:\\\\ProgramData\\\\docker\\\\windowsfilter\\\\c68cfb33fc431024547dcf0fcf90572c22879e69e39cd828fb74db4e51f9142b\",\"Layers\":[{\"ID\":\"4d0401a1-8f93-562f-9e4b-97ec27537e28\",\"Path\":\"C:\\\\ProgramData\\\\docker\\\\windowsfilter\\\\6f3a515eeaa2f406e462d36b405089b938197d602496e5acb4d09997b325c289\"}],\"HostName\":\"c68cfb33fc43\",\"MappedDirectories\":[],\"SandboxPath\":\"\",\"HvPartition\":false,\"EndpointList\":[\"8e060088-1bb7-4271-a047-733252fb6e95\"],\"HvRuntime\":null,\"Servicing\":false}"

ping @jhowardmsft @jstarks ptal

Prob a TP5 bug. Have just run this 20 times (ie 200 containers, 20x10 parallel) without any failures on an RTM build, and a few runs with 20 containers in parallel.


On Handling the L2 Proxy Admin Owner

The goal is to remove all network specific configuration from the L2 genesis state so that there is a deterministic L2 genesis for all chains. This enables the authentication of a standard L2 chain by simply referencing the root hash. Each release of the L2 contracts would correspond to a hardfork. The network specific configuration would be pushed via deposit transactions to the L2 as the first transactions that the system processes via deposit transactions that are sent via SystemConfig.initialize. All of the getters for this configuration would be fetched from the L1Block contract. This follows the same design pattern for the L1 contracts where all immutables were removed in favor of storage so that the same contract implementations could be used by multiple chains.
There is an open question on how to handle the L2 ProxyAdmin owner. Right now, a standard stage 1 OP Stack chain should set the L2 ProxyAdmin owner to be the aliased account of the L1 security council/foundation multisig.
The following options explore the design spaces.
SystemConfig can set owner
This would follow the same pattern for all other network specific config, the SystemConfig would be able to deposit and set the owner in the L1Block contract. This would essentially mix roles in some cases unless we had more expressive RBAC in the SystemConfig as it would mix the security council and the chain operator in both having the ability to change the owner, since you can change the owner by calling transferOwner on the ProxyAdmin or have the owner of the SystemConfig initiate a deposit transaction that modifies the ownership. The way to solve this is only allow setting this value by the SystemConfig if the initial owner is address(0), and then only the existing owner would be able to modify the value in the L1Block contract.
Depositor Account is owner
Enshrine a new call path that emits a TransactionDeposited event in the OptimismPortal from the DEPOSITOR_ACCOUNT that calls the ProxyAdmin. The caller of this function could be fetched from the SuperchainConfig, allowing a single source of truth to be defined for which account can create an L2 ProxyAdmin action. This is a nice design because it enables both the protocol and the security council to take action on behalf of the L2 ProxyAdmin. Longer term we may want to remove this function as the OP Stack matures and only let the protocol act on behalf of the ProxyAdmin

Spoke with @tynes about this and we agreed that the "Depositor Account is owner" is our preferred approach. This lets us have a typical path of upgrading predeploys via hard fork, but also provides deposit transaction upgrade if needed (e.g. for incident response)


Integration test MVP

Kicks off #455 with a test for the quickstart example.
Todo

[ ] sort out CI wiring
[ ] sort out directory structure—maybe integration_tests instead of tests/integration for easier segmentation?

Bringing over convo w/ @kapilt from private slack (rethreaded for readability):

i'm a little concerned if a policy test runner is going to be a rabbit hole
its also hard to make generic and the value chain is a little unclear
even then, coming back up a step the intent was to make a cli tool for executing a test structure alongside a policy, not for cc itself, but for user defined policies. in terms of prioritization though its seems further out given other items on deck.

[this PR is] my attempt to avoid falling down the rabbit hole. :slightly_smiling_face:
Seemed to me that there’s value in testing policies in docs.
I believe [@scotwk] got bit by drift under http://www.capitalone.io/cloud-custodian/docs/usecases/.

agreed that would be good, though i would hope to see recorded tests for those as well.
there's definitely value in having some integration tests
would have saved at least one brown bag release
just concerned about hardcodes on infrastructure, its hard to make this stuff generic
you can pull the ubuntu ami from json

“generic” across clouds, you mean?

no.. across accounts
ie. how does someone else run this integration test

"recorded tests" Say more about that?

http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:aws.json

clicks

its all the public ubuntu amis, there's a sstream-query tool front end for it, but its relatively easily to parse adhoc

Gotcha, to make https://github.com/whit537/cloud-custodian/blob/9c14e9a7c46727c6510b9d08726f6dd17598547b/tests/integration/test_quickstart.py#L28 generic ya?

re usecases bitrot is there a pr for fixing it?

(etc. w/ @scotwk)

It’s a deep and probably interminable rabbit hole to try to test apodeictically.
I.e., testing negative assertions as well as positive.
Not just “this policy changed this state in this way” but also “this policy did not change state in any other way"

thats not possible without pulling cloudtrail

cloudtrail was one option I was considering, yes.

rabbit hole :wink:

Ya. :wink:
sec ...
Right, I was running up against the need to sandbox at the account level.
Account as building block. Doesn’t seem easy w/ AWS.
No cleanroom.
I think for integration testing to work we’d need to set up a dedicated account just for integration testing.
I don’t think we want to have CI hitting the same skunkworks account that we’re working in.

@kapilt Image id genericized in 80968e0df006c98094b7be0590d64b7d72d2dae7. Let me know if you'd rather fetch at runtime vs. storing 4 MB in Git.

I'm surprised that CI is passing. Sup with that?

the intent [on #455] was to make a cli tool for executing a test structure alongside a policy, not for cc itself, but for user defined policies.

Seems we'd use the same tooling for both. This PR is MVP, could evolve into a CLI.

in terms of prioritization though its seems further out given other items on deck.

Fair enough. Closing, then, I guess?


Question about dynamic data_dim

Thanks for this great library!
In my application of modeling molecule, each data is a molecule encoding in (SMILES) string.
Each molecule always having distinc number of atoms, and one library is able to extract the 3D coordinate of each atom which I want to cache.
Therefore, for each data, the data_dim shape is rather dynamic of (num_atoms, 3) where num_atoms is change for each molecule, is there a way to use stocaching for this data?
At first, I thought of using Naive dictionary caching, but as you mentioned in the blog, this naive approach will not work for multi-workers dataloader. Another way is to use num_workers=0 for the first epoch as mentioned here
https://discuss.pytorch.org/t/best-practice-to-cache-the-entire-dataset-during-first-epoch/19608/2

Thanks for getting in touch. Sorry for the slow reply, there have been a lot of conference deadlines recently!
Having a dynamic data_dim is an interesting problem and not one that I had originally considered. Personally, I would avoid solutions that require setting num_workers = 0 because, in my experience, it slows things down a lot. It should be possible to get some speedups using stocaching in this case, but it may depend on the distribution of the shapes (and how much engineering effort you are willing to put in). Here are my initial thoughts:

pad -> cache -> crop

Initialise the cache with data_dims = (K, 3), where K is the maximum number of atoms of any molecule in your dataset.

When caching molecules, you can simply pad with zeros to change from (num_atoms, 3) to (K,3). Then reverse this process by cropping off the padding when reading from the cache. This solution is probably the simplest to implement, but caching the padding will waste some space, especially if the distribution of num_atoms is long-tailed.

You could also reduce the average amount of wasted space by setting K to be less than the maximum num_atoms (e.g. to the 75%th percentile). This would preclude 25% of the dataset from being cached (you would have to add a line in your dataloader to check num_atoms and exclude molecules larger than K from the cache). However, the molecules that are cached would have less padding on average. You could find a good tradeoff for K heuristically, but I suspect it may be possible to derive a closed-form solution (or solve an optimisation problem) to find the best value :)

I hope this is helpful. I don't know too much about your field but I would be interested to know if it helps. If you derive a solution to the optimal K problem, let me know too!


Change dependencies for compatibility with Configuration cache

Based on https://docs.gradle.org/6.7/userguide/configuration_cache.html#config_cache:requirements
Need to move from project to projectLayout to comply with configuration cache requirements

Thank you for the pull request and bringing this to my attention.  I've added a few comments.

Would a test with gradle --configuration-cache help or something similar help to identify failures of this type?  If so, would it be useful to add such a test to the test corpus?

Would a test with gradle --configuration-cache help or something similar help to identify failures of this type? If so, would it be useful to add such a test to the test corpus?

This is a very fair question - I have asked the same question and haven't received a good answer yet.

Would a test with gradle --configuration-cache help or something similar help to identify failures of this type? If so, would it be useful to add such a test to the test corpus?

This is a very fair question - I have asked the same question and haven't received a good answer yet.

I'm fine with proceeding with the changes that we can identify as being needed based on our reading of the documentation, but if we can get some form of reliable detection of problems in place, we can prevent future regressions.

A good testing strategy for Gradle's configuration cache is to run the whole test suite with the configuration cache enabled. This requires testing the plugin with a supported Gradle version. If you support a range of Gradle versions you might already have, or want, to test with multiple Gradle versions. Then you can enable the configuration cache starting with the Gradle version that supports it.
If this can't be done right away, using tests that runs all tasks contributed by the plugin several times for e.g. asserting the UP_TO_DATE / FROM_CACHE behavior is also a good strategy.

A good testing strategy for Gradle's configuration cache is to run the whole test suite with the configuration cache enabled. This requires testing the plugin with a supported Gradle version. If you support a range of Gradle versions you might already have, or want, to test with multiple Gradle versions. Then you can enable the configuration cache starting with the Gradle version that supports it.
If this can't be done right away, using tests that runs all tasks contributed by the plugin several times for e.g. asserting the UP_TO_DATE / FROM_CACHE behavior is also a good strategy.

Thanks for the information, @eskatos .  This plugin does indeed support a range of Gradle versions, as well as testing for a range of versions.
@dcabasson Here's a proposal for how to accomplish it.  Enhance FunctionalSpec.  Add a method determineCommonGradleArguments() that assembles a List<String> of arguments that will be passed to Gradle.  It will include "--stacktrace" all the time, and "--configuration-cache" when gradleVersion is >= 6.6.  Update run and runAndFail to use determineCommonGradleArguments() rather than the hardcoded addition of "--stacktrace".

@dcabasson Thanks for bringing this up as something to address.  I think I've worked out the remaining issues, and it will be fully supported in the next release.
Thanks again for the testing tips, @eskatos .  I expect to release a version supporting the configuration cache tomorrow.


Remove JsonUtils dependency due to classpath issues

Codecov Report

Merging #11264 (f710cfd) into master (49fe4f2) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #11264      +/-   ##
==========================================
- Coverage    0.11%    0.11%   -0.01%
==========================================
  Files        2229     2229
  Lines      119959   119964       +5
  Branches    18173    18173
==========================================
  Hits          137      137
- Misses     119802   119807       +5
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
0.00% <0.00%> (ø)

integration1temurin17
?

integration1temurin20
?

integration2temurin11
?

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
?

unittests2temurin11
0.11% <0.00%> (ø)

unittests2temurin17
0.11% <0.00%> (ø)

unittests2temurin20
0.11% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...in/stream/kinesis/KinesisPartitionGroupOffset.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Adding more context on this PR:

We have seen that multiple versions of JsonUtils are pulled. (While having the same name space, the parameter's class namespace are different due to shading).
This is a short/mid term fix where we remove JsonUtils dependency from Kinesis library to resolve the dependency conflict.

@snleee @KKcorps JsonUtils is a pinot util class. How is it possible to pull multiple versions of it?

Does that mean we cannot use any class under pinot-spi?

@xiangfu0 I'm not very familiar with shading, but I don't think this is the correct fix because basically this means we cannot use any utils that pulls external dependencies. Can you also provide your opinion?

This is more for short term fix. We can revert this after we resolve the shading issue. Ideally, we should have a single definition of JsonUtils but it looks that it not easy to achieve. Let's discuss on this.

There are two different issues:

We have JsonUtils several times in the classpath with the same package. Luckily, the correct one is loaded first.
The plugins shade jackson using their package prefix. That means that when they call public spi that use jackson, they use their own package. For example, they call <apache pinot package>.JsonUtils.stringToObject(String, <their-package-prefix>.TypeReference), which does not exist.

That later problem is the one that affected us. The problem here is that by adding jackson arguments and results to our spi methods, we are indicating that jackson should not be shaded, when in fact jackson is one the main package we want to shade due to incompatibilities in the classpath.


Next filament release 2.0?

Hi, Could you tell me when you plan to release filament 2.0?
Thanks in advance,
Giorgio

I've seen a similar question before. https://github.com/google/filament/issues/3235

We have a release once a week and it will be 1.9.10. We're current holding releases until we solve something internally at Google but if shouldn't be long hopefully.


Save NN models

Hi, flaml has a implementation of doing (Multi-output regression).
What are the steps to save all the trained models generated by this code?

You can access the individual models via MultiOutputRegressor.estimators_ and then save them as usual using pickle, or if pickle doesn't work, then clouldpickle or dill


File is missing properties definition ! in lib.webworker.d.ts

Bug Report

🔎 Search Terms
File, type, lib.webworker.d.ts

🕗 Version & Regression Information
⏯ Playground Link

Playground link with relevant code
💻 Code

const test = (
    <>
        <input
        type={"file"}
            id={"file-upload"}
            name={"file-upload"}
            accept={"image/png, image/jpeg"}
            onChange={(e) => {
                const file = e.currentTarget?.files?.[0]; // Single file for this test
                if (file) {
                 /** @see {File} - Type File not have property path ? why ?  */
                    const path = file.path;
                    const pathForce = (file as unknown as { path: string }).path;
                }
            }}

        />
    </>
)

🙁 Actual behavior
type File is missing some property , like path where we can use inside nwjs or electron desktop app.
see https://github.com/microsoft/TypeScript/blob/main/lib/lib.webworker.d.ts
🙂 Expected behavior
We should able to see path , because is valide in js

The File type has no path property. That's an electron specific addition, it shouldn't be part of the webworker lib.

ho oups sorry for the mistake !


Add option to convert NaN and infinite values to strings when retrieving experiment properties

Issue
The "NaN" and "infinite" values are not part of the JSON standard. When we serialize entries with NaN or inf we are actually creating an invalid JSON document that is made possible by Python's default behavior for json (which is allow_nan=True). If allow_nan is set to False, then an exception would be raised.
Solution
We could add a flag such as stringify_nan which defaults to False that allows for converting NaN and infinite values to the string NaN/inf. This would allow services such as the Registry Backend to then serve valid JSON.
The issue could be fixed by adding in the line before the Dataframe is converted to dict (here: https://github.ibm.com/st4sd/st4sd-runtime-core/blob/master/python/experiment/service/db.py#L1137) a call to Pandas's fillna function, as such:
df.fillna('NaN', inplace=True)

For infinite values, instead, we will have to use the df.replace method
Done when

[x] We have a flag that allows stringifying NaN values

This closes #6


Implement alternative v2 backup

Use smth similar to this https://github.com/fanhattan/etcd-backup

Closing as we found a way to create and restore both v2 and v3 backups together.
See: https://github.com/giantswarm/etcd-backup/blob/master/Documentation/01-restore-etcd-from-backups.md


enabling net.bridge.bridge-nf-call-iptables not working on centos 7

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Environment:

Cloud provider or hardware configuration:
hardware configuration

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
Linux 3.10.0-514.16.1.el7.x86_64 x86_64
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Version of Ansible (ansible --version):
ansible <IP_ADDRESS>
ansible python module location = /usr/lib/python2.7/site-packages/ansible
python version = 2.7.5 (default, Aug  4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]

Kubespray version (commit) (git rev-parse --short HEAD):
ba0a03a
Network plugin used:
flannel_backend_type: host-gw
Copy of your inventory file:
Command used to invoke ansible:
Output of ansible run:

Anything else do we need to know:

The issue:
Task "name: Enable bridge-nf-call tables" in roles/kubernetes/node/tasks/main.yml doesn't execute on my "default" centos 7.4 install.
This breaks any bridge-based kubernetes networking with iptables kube-proxy, flannel in my case.
This can be fixed by replacing the conditions for task execution, modinfo_br_netfilter.rc == 1 in particular. Better fix might be: have a variable to enable sysctl or detect network backends that require it automatically.
I'd rather kubespray fail if it can't load br_netfilter or set net.bridge.bridge-nf-call-iptables vs current situation when kubespray succeeds but kubernetes network is broken.

We're seeing this exact same issue on our CentOS 7.3 implementation as well. The issue is with the line of code you mentioned located at:
https://github.com/kubernetes-incubator/kubespray/blob/a6975c18506f533ba9e67c7fb233e9898b77502b/roles/kubernetes/node/tasks/main.yml#L101
modinfo_br_netfilter.rc == 1 needs to be changed to modinfo_br_netfilter.rc == 0 to function correctly.
For us, this initially presented itself as cluster DNS issues since Pods were unable to perform lookups on kube-dns running on the same host. Since the bridge netfilter isn't being correctly enabled, it results in Pods being unable to communicate with other Pods on the same host.
This is a breaking bug for anyone using CentOS 7 and Flannel.

@paravz @nickkeyzer @Atoms Can you explain the resolution to this issue for me?
I'm having the issue on CentOS 7 where the windows pods can't connect to the kube-dns unless firewalld is stopped.
The recommended sudo sysctl net.bridge.bridge-nf-call-iptables=1 command fails with sysctl: cannot stat /proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory.
I tried editing /etc/sysctl.conf as per https://github.com/kubernetes/kubernetes/issues/33798#issuecomment-251661435 and rebooting but it's still not working. As soon as I sudo systemctl stop firewalld the resolution starts working. Adding DNS service and 53/tcp and 53/udp to the firewall zone had no effect either.

try to modprobe br_netfilter in your centos, then sysctl should work

try to modprobe br_netfilter in your centos, then sysctl should work

I did and the command indicates it succeeds but it doesn't seem to add the item to the /etc/sysctl.conf so I ended up modifying the file directly. It also didn't resolve my underlying issue either: my worker pods can't access kube-dns unless firewalld is disabled on the master.
Worth noting, not sure if required but, I created an /etc/modules-load.d/br_netfilter.conf to load the module at boot as well.
I'm not using kubespray, I used kubeadm, so this is out of topic. If you have any suggestions however, I'd appreciate it. I created an MS forum thread with more details.

Still experiencing this in CentOs 7.7 and kubespray v1.12.1, running ansible with the following command:
ansible-playbook test.yml -b -u centos -i <hostfile> --private-key=<key-file>

The issue we see is related the following ansible task:
https://github.com/kubernetes-sigs/kubespray/blob/v2.12.1/roles/kubernetes/node/tasks/main.yml#L73
# kube-proxy needs net.bridge.bridge-nf-call-iptables enabled when found if br_netfilter is not a module
    - name: Check if bridge-nf-call-iptables key exists
      command: "sysctl net.bridge.bridge-nf-call-iptables"
      failed_when: false
      changed_when: false
      register: sysctl_bridge_nf_call_iptables

Running this task returns the following (output for single host):
ok: [p3k8stestwk003] => {
    "msg": {
        "changed": false,
        "cmd": "sysctl net.bridge.bridge-nf-call-iptables",
        "failed": false,
        "failed_when_result": false,
        "msg": "[Errno 2] No such file or directory",
        "rc": 2
    }
}

Looking above, the rc key is 2, which then does not trigger the following task:
https://github.com/kubernetes-sigs/kubespray/blob/v2.12.1/roles/kubernetes/node/tasks/main.yml#L80
  sysctl:
    name: "{{ item }}"
    state: present
    sysctl_file: "{{ sysctl_file_path }}"
    value: "1"
    reload: yes
  when: sysctl_bridge_nf_call_iptables.rc == 0
  with_items:
    - net.bridge.bridge-nf-call-iptables
    - net.bridge.bridge-nf-call-arptables
    - net.bridge.bridge-nf-call-ip6tables

Was able to get a valid response by changing the command in the above from:
sysctl net.bridge.bridge-nf-call-iptables
to
/usr/sbin/sysctl net.bridge.bridge-nf-call-iptables
ok: [p3k8stestwk003] => {
    "msg": {
        "changed": false,
        "cmd": [
            "/usr/sbin/sysctl",
            "net.bridge.bridge-nf-call-iptables"
        ],
        "delta": "0:00:00.008156",
        "end": "2020-03-26 11:58:25.959879",
        "failed": false,
        "failed_when_result": false,
        "rc": 0,
        "start": "2020-03-26 11:58:25.951723",
        "stderr": "",
        "stderr_lines": [],
        "stdout": "net.bridge.bridge-nf-call-iptables = 0",
        "stdout_lines": [
            "net.bridge.bridge-nf-call-iptables = 0"
        ]
    }
}

Not a huge linux user, so not sure if the location /usr/sbin/sysctl is CentOS only, but happy to take a stab at a pull request if that would help.

Happens on centos 7.6;  okay on centOS 7.7 - Lesson - use an updated OS when installing kubernetes


Alter docs to reflect changes made to --queues_avoid

See related wr PR

Lint is failing, I cannot see why.


The types for custom routes are not being generated.

Hello,
I am using some custom routes. Like below:
 {
    path: '/apps/email/:filter',
    name: 'apps-email-filter',
    component: emailRouteComponent,
  },

  // Email label
  {
    path: '/apps/email/label/:label',
    name: 'apps-email-label',
    component: emailRouteComponent,
  },

So it gets below errors:

What should I do to resolve it?

This is normal for extendRoutes() as it's a runtime option. You can use build time options instead: https://github.com/posva/unplugin-vue-router/blob/main/src/options.ts#L111


Upgrade terraform-provider-azurerm to v3.40.0

Upgrade terraform-provider-azurerm to v3.40.0
Rebuild SDKs for v3.40.0

Looks like upstream just typo'd the 'blob' as 'blog' in the docs. Expect this will get fixed in the next release and we'll have to watch out for this during the next review and remove the override?

@danielrbradley I'm hoping our tooling will error if they rename the file, just like it did before I added the explicit "Docs" reference.


Opening a file URL with macOS open ignores query parameters

The standard way to open a URL in the default browser in macOS is the open command. Unfortunately, open actually understands URIs and ignores query parameters for the file:// protocol. This results in the html_views/goals/Coq.html file being loaded without the necessary hostname and port.
It seems the only real solution to this is to serve that file from a local webserver and open that server's address instead of a file.

I should mention that this is easy to workaround: the full URL is logged to the console; Help > Toggle Developer Tools will show it.

This issue also exists with Window's start command. But you can instead specify "firefox ${url}" or "chrome ${url}" via coq.externalViewUrlCommand, for example; these programs do preserve the query parameters or the file:/// Url.
I'll close this issue when I've implemented a webserver to host the pages.

It's awkward on macOS to refer to the binaries (they're not provided on the $PATH by default), but calling them directly does work. Specifically, I'm now using
"coq.externalViewUrlCommand": "'/Applications/Google Chrome.app/Contents/MacOS/Google Chrome' ${url}"
which correctly opens URLs with parameters, and re-uses the existing Chrome instance.
I think it's fair enough to document this for macOS and close this issue, and have a separate (low priority) task of serving the page with a webserver, especially if this is the only problem you're running into with a file:/// path.

@tchajed I've added some info on this in the wiki's "Tips", and the autocomplete for coq.externalViewUrlCommand in settings.json now suggests the chrome command for OSX (among some other options).
Also, I went ahead and implemented the webserver (pretty trivial in Node.js) because this is just going to confuse most users unless the default option "just works." The default for coq.externalViewUrlCommand is now "${url}", which will use OSX's "open", Window's "start", and Linux's "xdg-open".


sql: implement SHOW DEFAULT PRIVILEGES

PR: https://github.com/cockroachdb/cockroach/pull/67997
From release notes:

Added a crdb_internal.default_privileges table that is useful for getting a human-readable way of examining default privileges. [#67997][#67997] {% comment %}doc{% endcomment %}

Captured in included docs.


Team and Student Invites

Warning, massive pull request because I did some backend structural changes for some of the models - and decided to expand on it.
I will promisfy everything @hugomd later.

only missing a leave team endpoint and probably a lot of code cleanup sigh

@terencehuynh @hugomd I think this is all done now... monster pull 🙈


Open Data at Study Groups

Hey everyone,
Over the next little while, I'd love to get everyone's help designing some Study Group activities on the topic of open data. How can data sharing be introduced to your Study Group in a way your colleagues will find interesting and useful? Post ideas on this thread!
It'd be awesome if each of the Study Groups tried to throw an open data session this summer. Anything you want to try out is fair game - just be sure to document it and share back here!

@BillMills Has anyone done sessions on using Zenodo and GitHub together for DOIs?

:+1:  for that; i've tried it and loved it.

Nope, not that I know of - it's a good topic for a lesson though; super useful, not particularly difficult, but weird enough the first time through that a walkthrough would be helpful. Let me know how it goes!
Another thing to possibly add on to this lesson: when to mint releases / DOI's? At every single possible change? Only on major changes? For every project, or more for projects intended as reusable components? An actual librarian knows better than me how to do this in the most useful way possible, so I'd be curious to know! I would also mention DOI history management, too - the DOI will update itself every release if the zenodo hooks are still active, so I like to keep a record in the readme of past doi's for people (invariably) using old versions, see for example the top of this readme.

great ideas! this could be a great chance to work with @stephwright : ). I'll see what I can come up with for a lesson.

:+1: agree... great ideas!  We can talk about this when we chat next week, Tom!

Awesome thread, and sorry for my delayed response here. These are concepts we're evolving in the Open Data Training Series that @stephwright has authored. We're building on that curriculum over the next few months to get to match our Open Leadership Training Series.
Small plug for the Moz Open Leaders Mentorship Training which is taking participant applications through 1/20, ask @acabunoc for more details!


Share date/schedule util functions between swaps and bonds

Relates to https://github.com/digital-asset/daml-finance/issues/822

I am considering moving these to a new Claims/Util/Date module as well.

I am considering moving these to a new Claims/Util/Date module as well.

I think the extra dependency this would add is quite dangerous. It would force us to bump all claim instruments (including the generic instrument) for a change in Data. Not worth it in my opinion

I think the extra dependency this would add is quite dangerous. It would force us to bump all claim instruments (including the generic instrument) for a change in Data. Not worth it in my opinion

Do you see another shared package where these could live? Or better to keep duplicated, separate?

I think the extra dependency this would add is quite dangerous. It would force us to bump all claim instruments (including the generic instrument) for a change in Data. Not worth it in my opinion

Do you see another shared package where these could live? Or better to keep duplicated, separate?

What about Daml.Finance.Data?

What about Daml.Finance.Data?

I think that makes more sense. It solves the problem with dependencies as well. I have moved the functions to existing modules in that package now.


docs: forbid <IP_ADDRESS> passwd free login

Proposed changes
Issue Number: close #xxx
Problem summary
Handle description inconsistency in password-free login
PR #18816 omitted a necessary change.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[x] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

run buildall

run buildall

run buildall

please rebase your branch to master

run buildall

Used rebase (force push) to avoid merge commit.

run buildall

run p0


[BEAM-11160] Fix HadoopFormatIOIT

beam_PerformanceTests_HadoopFormat is failing since ElasticSearch update. The problem was that there was no dependency for apache commons-lang3 and NoSuchMethodError: StringUtils.isNoneEmpty was thrown.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java HadoopFormatIO Performance Test

Run Java PostCommit

Run Java PostCommit

Run Java_Examples_Dataflow PreCommit

Run Java_Examples_Dataflow_Java11 PreCommit

@aromanenko-dev Could I ask you to review this?


HW10.10.2016

https://github.com/SShopik/training_epam/tree/dev
branch dev
https://github.com/SShopik/training_epam/commit/9a23e707e56dad6c77a8a22d45e539df0d818e0a

ok


[Windows 10/11] Manual installation with pyenv doesn't seem to work properly

So, I uninstalled the UVR application in favor of trying out the manual installation instead of the executable to see if installing it manually via the archive and Command Prompt/Terminal would fix the bugs I've been dealing with in the Roformer models (to make a long story short, for some weird reason the Roformer models are just completely unusable for me now, and nothing I do fixes the problem), but the requirements.txt portion of the installation process gives me an error when it tries to build wheel for playsound.
Firstly, I'd like to mention that the recommended install code from the README did not work in my case, so I had to shorten it from python.exe -m pip install -r requirements.txt to pip install -r requirements.txt for it to even work. This is probably because I use Python via pyenv rather than straight installing Python, though.

The following images are the error I receive every time I try to manually install UVR. I should mention that I still get the error even after uninstalling what few dependencies were installed via pip uninstall -r requirements.txt to try and install the dependencies cleanly.

I'm honestly not sure what to do. I need the Roformer models for some of my projects, and until such a time as the bugs with them are resolved I cannot meaningfully move forward with those projects.

try to use python 3.8 version, the imp module is deprecated in the latest. hope this helps you


Migrate Lathe Material Ejection Code to MaterialStorage

About the PR
The lathe material ejection code acts as a do-nothing man-in-the-middle system that does work that would be reasonable for any MaterialStorage-using machine to use. This has been fixed by migrating the ejection code to MaterialStorage, allowing anything that uses the system to eject mats it is storing.
Why / Balance
It's not just lathes that store and might materially want to eject input materials.
Technical details
This is a lift-and-shift of the Lathe code over into MaterialStorage, both to solve #23184 (because EmoGarbage asked me to look at it) and to demonstrate comprehension of the ECS system used inside SS14.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
N/A, this is a non-functional code change.

Hey, this is a heavier PR than my first one, but is just a lift-and-shift designed to demonstrate I figured out how ECS works. My main concern here is that I'm unaware of the integration between the data fields as defined in Components and the physical objects manipulated by players - that's why I've kept the bool that checks if ejection is possible as defaulting to true.
I'd like to know what the process is if I set that bool to false by default. What would I need to change to ensure no regression within this PR?


fs/ioctl:add FIOC_XIPBASE to get file xip address

Summary
in tmpfs/romfs, we can get file real xip address to execute program
Impact
romfs & tmpfs
Testing
qemu with mps3 an547

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX Requirements.
Missing Information:

Purpose of the change:  The summary is too vague. Clearly state the reason for the change (e.g., bug fix, performance improvement, new feature).
Detailed description of the change:  Explain how you are enabling access to the file's XIP address. What code is modified?
Impact details:

Provide specifics for each "Yes" answer.  For example, which ROMFS/TMPFS functions are affected?
How does this impact users? What do they need to do differently?
Are there any security implications of exposing the XIP address?

Comprehensive testing:

List the specific operating systems, architectures, and boards used for testing.
Provide more detailed testing logs that demonstrate the functionality before and after the change.

Recommendations:

Expand the Summary:  Clearly articulate the problem being solved or the feature being added.
Detail the Implementation:  Explain the technical details of your changes.
Provide Specific Impact Information:  Give concrete examples and details about how this change affects the system and its users.
Improve Testing Documentation: Include more specific information about your testing environment and detailed logs that clearly show the change in behavior.


Remove libpython3.x.so dependency

Good to separate python part from original file.

looks good to me

looks good to me


Improved FancyZone's

Description of the new feature / enhancement
FancyZones addition:
My suggestion would be 'win' + 'mod' + 'arrow' would be to span adjacent zones
Scenario when this would be used?
For example sometimes I will be using 6-9 for 2 separate windows spanning [6,7] or [6,8].. etc..
currently my use case will have me 'win' + 'arrow' to the zone, then 'shift' and drag them between the 2 zones to have it span either the horizontal or vertical aligned span

Supporting information
No response

Are you asking to be able via keyboard to snap an app to 6+7?  Already supported
https://docs.microsoft.com/en-us/windows/powertoys/fancyzones#snapping-a-window-to-two-or-more-zones


pkg_resources deprecation warning

Currently, running test suite with pytest results in:
../../../../opt/anaconda3/envs/r5py/lib/python3.9/site-packages/pkg_resources/__init__.py:121
  /opt/anaconda3/envs/r5py/lib/python3.9/site-packages/pkg_resources/__init__.py:121: DeprecationWarning: pkg_resources is deprecated as an API
    warnings.warn("pkg_resources is deprecated as an API", DeprecationWarning)

../../../../opt/anaconda3/envs/r5py/lib/python3.9/site-packages/pkg_resources/__init__.py:2870
  /opt/anaconda3/envs/r5py/lib/python3.9/site-packages/pkg_resources/__init__.py:2870: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('mpl_toolkits')`.
  Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
    declare_namespace(pkg)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

Potential fix here
Upgrading pip from the version where the warning was introduced (23.1) to 23.1.1 / 23.1.2 did not resolve. Looks like this may be a warning propagating through pip via a dependency in setuptools. Seems to be the method used for detecting eggs in a package.

Can no longer reproduce. Will close the issue and re-open if needed.

Not closing as one day we may get to fix this. But currently a wontfix. Arising from this, see #165 regarding environment management.


Revamp GitHub workflows

Changed

Renamed Test workflow to Validate to better represent all the steps besides testing
All workflows to use checkout@v4 instead of v3
Validate workflow to use setup-node instead of Docker container
All setup-node steps to use .nvmrc to define node version
Validate workflow to run on push to main as well as pull request

Removed

"own all files" step from Validate workflow

I'll update the required CI stages once this merges.


econml 0.15.0 ❄

econml 0.15.0 ❄
Destination channel: Snowflake
Links

PKG-4217
Upstream repository
Upstream changelog/diff

Changes

recipe
upstream tests (a couple of patches to make them run): they are extremely slow

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_afaee3fcmb/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:58: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
clone/recipe/meta.yaml:58: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:58: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
clone/recipe/meta.yaml:58: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_07w05qfrwm/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:58: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:58: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
clone/recipe/meta.yaml:58: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
clone/recipe/meta.yaml:58: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f96b9h9wc9/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:60: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:60: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:60: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
clone/recipe/meta.yaml:60: missing_dev_url: The recipe is missing a dev_url
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_4bj2vrhxnf/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:59: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
clone/recipe/meta.yaml:59: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:59: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:59: missing_documentation: The recipe is missing a doc_url or doc_source_url
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_e2rk7xidbs/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:60: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:60: missing_license_family: The recipe is missing the about/license_family key.
clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
clone/recipe/meta.yaml:60: missing_dev_url: The recipe is missing a dev_url
clone/recipe/meta.yaml:60: missing_documentation: The recipe is missing a doc_url or doc_source_url
clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
===== Final Report: =====
5 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_0bn3fek8l8/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:62: missing_description: The recipe is missing a description
===== Final Report: =====
0 Errors and 1 Warning were found

Adding upstream tests would be nice if poss: https://github.com/py-why/EconML/tree/v0.15.0/econml/tests

@boldorider4 I'll take on this one as well and add upstream tests

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_afwldjg8s2/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:27: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_b0ek3pnr3u/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_6b8u6sexuo/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_f8ur74m_o6/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_2c6g6c1sxn/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:83: invalid_url: https://econml.azurewebsites.net/ : Not reachable: 403
===== Final Report: =====
1 Error and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_ac2b_2c07e/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:31: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_86v7qc8hf5/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_99kldo0d5i/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_0cxe3oysov/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_73_9t5s1tj/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_3c5ugpzq94/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_2034kn3mjc/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:32: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found


Intellisense shows wrong autocomplete if module names are the same as builtins

Environment data

VS Code version: 1.21.1
Extension version (available under the Extensions sidebar): 2018.2.1
OS and version: macOS Sierra 10.12.6
Python version: 3.6.4
Type of virtual environment used: venv

Steps to reproduce:

Create a file named the same as a builtin (or 3rd party library). Say json.py
Open a new file foo.py
Start typing import json.

Actual behavior
No intellisense autocomplete popup appears.
Expected  behavior
Intellisense autocomplete popup listing {} encoder, {} decoder, {} scanner, {} tests and {} tool should appear.
Logs
Output from Python output panel
None
Output from Console window (Help->Developer Tools menu)
None

This seems very similar to #178 , could they have the same cause?

Yep, this would be the same.


Remove builder dependency

Added in https://github.com/railsadminteam/rails_admin/commit/61a7e196e3fb8ffc3ae2db5136d8e9019c807134 / https://github.com/railsadminteam/rails_admin/commit/0188a8a09ce18dfb5f7993030049b48a7b9ab3fd, this appears to no longer be used.
Digging through the git history since when this was added.

Moved from app/helpers/rails_admin/main_helper.rb to lib/rails_admin/fields.rb
Moved from lib/rails_admin/fields.rb to lib/rails_admin/config/fields/types/boolean.rb
Removed from lib/rails_admin/config/fields/types/boolean.rb

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.6%) to 91.149%

Totals

Change from base Build<PHONE_NUMBER>:
-4.6%

Covered Lines:
3357

Relevant Lines:
3683

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.6%) to 91.149%

Totals

Change from base Build<PHONE_NUMBER>:
-4.6%

Covered Lines:
3357

Relevant Lines:
3683

💛  - Coveralls

😍

Changes unknown
when pulling 2b542ed49745deecc27895dd3eb061a4445db33e on remove-builder-dep
into ** on master**.


Remove ember-cli-frost-blueprints from dependencies

Since this is a breaking change, we may want to wait til LTS 2.0 for this, as a way to opt-out of frosty generators, consumers can choose not to install ember-cli-frost-blueprints and have the default generators if they prefer (mainly for folks who don't want to be fully frosty, those outside of Ciena).
This is related to: ciena-frost/ember-frost-core#272

Agreed, easier to swallow since we're close to LTS 2.0 as well


Refactor tags command

@liuchengxu because you're working on tags command, could you consider supporting custom/user ctags binary in proj_tags provider via settings or provider options? Clap proj_tags is using fixed ctags:
let s:support_json_format =
      \ len(filter(systemlist('ctags --list-features'), 'v:val =~# ''^json''')) > 0

Thanks.

@phongnh Not important for me as it's not hard to inject the binary into the PATH if you already have one, but I'm happy to accept PR.

@liuchengxu You're right. In my machine (Ubuntu), Universal Ctags is installed as ctags-universal instead of ctags, I'm not sure why (maybe conflicting with Exuberant Ctags). Maybe I just need to build and install Universal Ctags from source instead of package manager. Thanks.

@phongnh Or just create a symlink? Something like ln -s `which ctags-universal` /usr/local/bin/ctags

@phongnh Or just create a symlink? Something like ln -s `which ctags-universal` /usr/local/bin/ctags

Thank you @romgrk


Error in compiling Gaffer 0.4.0

When we try to compile Gaffer 0.4.0 with Maven we get the errors in the attached file:
maven errors.txt

Could you provide more details? Checking out tag gaffer2-0.4.0 and running mvn clean install doesn't produce that error for me. Which tag are you using? Which version of Java? Which version of maven?

we used Maven 3.3.9 and Java SE Development Kit 8u101. At first we used Windows 7 as OS, and we get the previous errors, then we switched to Gffer 0.4.1, and get the same error, so we tried with Debian 8, and we get the following other errors:
gaffer.graph.GraphTest.txt
So, @unclassified02 solved commenting the function shouldConstructGraphFromSchemaFolderPath in the file Gaffer-gaffer2-0.4.1\gaffer-core\graph\src\test\java\gaffer\graph\GraphTest.java
Now it seems to work properly (we are testing it with an Accumulo cluster and we are getting no errors nor warnings)

Looks like the error is caused by that test expecting the schema types to be iterated over in a particular order. However, the types are stored in a HashMap so the order will not be consistent.
We need to update the test and possibly others too to not rely on the ordering of the schema types. This basically means if we import and export a schema - the json types may not be in the same order.
Alternatively, it might be neater to just change the TypeDefinitions HashMap into something like a LinkedHashMap so order is preserved.

This has been fixed as part of gh-427. The change has been merged into the develop branch and will be released soon.