Can't copy long output text

Environment

Elixir & Erlang/OTP versions (elixir --version): Elixir 1.12.1 (compiled with Erlang/OTP 24)
Operating system: macOS 11.4
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): livebook CLI (livebook server)
Livebook version (use git show if running with mix): v0.2.0
Browsers that reproduce this bug (the more the merrier): Firefox 91.0a (Nightly), Safari 14.1.1
Include what is logged in the browser console: -
Include what is logged to the server console: -

Current behavior
When I try to copy a long output text from livebook, only the visible lines are copied.
I suspect that some Javascript is removing the non-visible lines during scrolling.
Therefore the non-visible lines aren't copied.
I tried to work around that issue, by selecting the text from the bottom, because when at the top of the cell,
every <div> with the cells content is in the DOM, but that doesn't work either.
Reproduce:

Add this to a Elixir cell in Livebook:

Range.new(1, 1000)
|> Enum.to_list()
|> IO.inspect(limit: :infinity)

Try to copy the output

Expected behavior
Output should be copyable.
Maybe add a Copy to clipboard button to the cell?

@jonatanklosko
Thanks for the fast implementation. Helps a lot.
But one thing still bothers me:
When copying the lower fields output, it copies the truncated output.
It would be nice, when the Copy to clipboard button always copies the whole output.
Currently this looks quite difficult to achieve, because the LiveView only gets the formatted output.
I am not sure if it is suitable to save the whole output with the LiveView or if that will make it to slow.
Is this behaviour somehow achievable?

That’s Elixir’s regular inspection limits. You can inspect it yourself but perhaps we could configure the default inspection options in Kino? Similar to how it works on IEx?

@josevalim
I think the output can stay as it is.
But maybe add the raw evaluation response of the Elixir section to the metadata and fetch it from there (with inspect(limit: :infinity)), when the Copy to clipboard button is pressed?

I think it would be confusing if what you copy is not what is being shown?

Hmm, sounds reasonable.
But most of the time I don't want to copy the truncated data. I want to have the "real result" of the cell. But maybe using inspect is the way to go.

I agree with @josevalim that we should copy whatever can be seen on the screen. Also the inspected result may be really huge, and it's even likely with Nx tensors, so I'd leave IO.inspect(whatever, limit: :infinity) explicitly to the user when they really want the whole result. Also keeping the full inspect around would have significant impact on the memory used, while objectively it's a rather specific use case.
@josevalim making the inspect options configurable in Kino is a way, but at this point I only see someone using it to set limit: :infinity and that doesn't sound like a reasonable option to set globally :thinking:

Also keeping the full inspect around would have significant impact on the memory used, while objectively it's a rather specific use case.

Yeah, thats what I thought.
Thanks for the fast feedback! ❤
I think this Issue can get closed then.

I can see people finding the limit of 50 too low and they may want to increase it a bit. We can always document making it infinity isn’t a good idea. I am sure it will come up other times.


Reduce maven transient dependecie

The dependency list of the pact-jvm-provider and consumer for junit, are a bit big. And can cause a lot of conflicts (think about the sl4j dependence thats cross project from pact-jvm-model to pact-jvm-matcher etc).
We should analyse and reduce the needed packages (and if possible reduce the amount of nested dependencies (but this could be a scala thin).

I researched topic of CDC today and, to be honest, I am not sure if I should use pact-jvm because of all of these dependencies. scala, kotlin, groovy, aws sdk, gson, kotson, jackson, jsonpath, netty, etc.
I had to exclude some libs in build.gradle dependencies of pact-jvm because they clashed with project ones.

Do you plan to eradicate kotlin, scala and groovy from dependencies?
Did you thought about distributing pact-jvm as shadow jars (aka fat jars)

list of dependencies for consumer test
list of dependencies for provider test


Slow import

Because intake automatically import all plugins it finds, importing intake is pretty slow and getting slower. Suggest we consider some method to take note of the plugin names that are importable, but only import them upon the use of an open_* function, or while loading a catalogue referencing given plugin.

Yeah, we could replace these with thunks that defer the import until the first usage.

Actually, thinking about this further, the name of the plugin is a currently an attribute of the Plugin subclass, so we do have to import the plugins in order to even populate the open_* functions and the plugin registry.

There could be a convention that the __init__ modules define the plugin, and import intake to do it, but source and all functionality is always in another module which is only imported when the plugin is used.

To close this issue, I suggest that documentation should appear in the make-a-plugin page, describing the pattern.

Example for intake-avro https://github.com/ContinuumIO/intake-avro/pull/4/commits/9e6f10e76c21cad8b0f43a2da050bfb2e6f43a1e


Is it possible to access inner contents of element as it was written in md?

I'm building a documentation site for a pattern library and would like to write code examples in markdown and then render it with a live code editor like react-live.
## Start now button

Launch your service with a Start now button.

<Example>
  <Button kind="start">Start now</Button>
</Example>

And have it render out something like this:

The missing piece is having the "children" of <Example> passed through as a string so that react-live can handle rendering.
Is it possible to access the inner contents of <Example> as it is written in the markdown?

Oh definitely! Make an override function for “Example” and then handle the
children as desired.
On Fri, Aug 3, 2018 at 11:45 AM Jon Earley<EMAIL_ADDRESS>wrote:

I'm building a documentation site for a pattern library and would like to
write code examples in markdown and then render it with a live code editor
like react-live https://react-live.kitten.sh/.
Start now button
Launch your service with a Start now button.

Start now

And have it render out something like this:
[image: screen shot 2018-08-03 at 12 29 43 pm]
https://user-images.githubusercontent.com/1678665/43654445-3b0c19fa-9719-11e8-9661-22b4e77d0d8d.png
The missing piece is having the "children" of  passed through as
a string so that react-live can handle rendering.
Is it possible to access the inner contents of  as it is written
in the markdown?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/probablyup/markdown-to-jsx/issues/201, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAiy1gzL_OH7iWq2qRLHCEQOU5ezC32jks5uNH4pgaJpZM4VuTNV
.

Thanks for the response!
The code below generates the screenshot above. My issue with this override is that I don't know how to get the inner contents of  as it was written in the markdown. The children are already React elements at this point.
const ExampleOverride = ({ children, ...props }) => {
  return (
    <Example code={`<Button kind="start">Start now</Button>`} />
  )
}

The example expects a code prop of valid JSX.

Oh I see. Hmm yeah it’s not currently possible to grab that, but it could
be added as it’s available during the “react” step of each rule.
On Fri, Aug 3, 2018 at 12:00 PM Jon Earley<EMAIL_ADDRESS>wrote:

Thanks for the response!
The code below generates the screenshot above. My issue with this override
is that I don't know how to get the inner contents of as it was written in
the markdown. The children are already React elements at this point.
const ExampleOverride = ({ children, ...props }) => {
return (
<Example code={<Button kind="start">Start now</Button>} />
)
}
The example expects a code prop of valid JSX.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/probablyup/markdown-to-jsx/issues/201#issuecomment-410315144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1sMGmBefWUJNA7GiRhZVdGUMcbJDks5uNIG2gaJpZM4VuTNV
.

If it could be added that would make amazing! I'll look to publish a companion library for live code examples in markdown.
Curious -- Have you come across other approaches to including live code examples in markdown?

I think react-styleguidist does it?
On Fri, Aug 3, 2018 at 12:10 PM Jon Earley<EMAIL_ADDRESS>wrote:

If it could be added that would make amazing! I'll look to publish a
companion library for live code examples in markdown.
Curious -- Have you come across other approaches to including live code
examples in markdown?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/probablyup/markdown-to-jsx/issues/201#issuecomment-410317773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1uy-0ad9xWoi7JYu6NC8PfziX7M4ks5uNIP9gaJpZM4VuTNV
.

export default function Markdown({ children, options, ...props }) {
    return React.cloneElement(compiler(children, options), props, children);
}

Would something like this be the right idea? Thinking of forking.
https://github.com/probablyup/markdown-to-jsx/blob/master/index.js#L1584

Well that would clone the whole tree for you. Are you looking to obtain the entire markdown block source or just whatever is inside a specific rendered HTML element/component?

Gotcha. For this just interested in whatever is inside the specific rendered HTML element/component.

This is the kind of doc experience I'm aiming for: https://github.com/emotion-js/emotion/blob/master/docs/css.md.
Looks like I'll be trying out Gatsby next.


[experiment] In ZipOutputStream, optionally transform the names of added entries with a simple fixed transform function.

Alternate spin off of #497 with an inline transform function instead of a swappable NameTransform.
Keeps all the code local to ZipOutputStream rather than changing anything else, scope there for sharing the utility code.
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

refs #495

I am closing this in favor of #497


Draftable should only control Save button

if i does not misunderstand, Draftable should only control Save button. and we  should always have publish  button.
i will do a PR for 1.9.3

Semantics ... one could argue you Publish a draft. If everything is published, there is no Publish verb per se. We'll see what others have to say.

You also publish a new version. It would more consistent and less confusing to have "publish" that always results in the contents of the editor going online, and a "save as draft" button.

Having a "Save as draft" and "Publish" button seems the most straight forward option. If a content type is not draftable, then perhaps only the "Publish" button should be displayed, since the content item would be published immediately.

I agree with @sfmskywalker
if need , i can do more commit

Action:

Change "Save" to "Save as draft"
Show Publish all the time.

Example:
For a draftable content type, we'll have "Save as draft" and "Publish"
For a non-draftable CT we'll have "Publish"

added new commit for
Action:
Change "Save" to "Save Draft"
Show Publish all the time.


test: add unit test

Codecov Report
Attention: Patch coverage is 84.61538% with 2 lines in your changes missing coverage. Please review.

Project coverage is 69.25%. Comparing base (ef072e6) to head (eb88166).

Files with missing lines
Patch %
Lines

controller/ws/ws/handler.go
84.61%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              3.0     #358      +/-   ##
==========================================
+ Coverage   69.01%   69.25%   +0.23%
==========================================
  Files          98       98
  Lines       13230    13219      -11
==========================================
+ Hits         9131     9155      +24
+ Misses       3350     3316      -34
+ Partials      749      748       -1

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


Java projects generated with gradle init should use toolchains

When generating a Java project using gradle init the resulting build scripts do not contain any configuration related to the Java toolchains. If the user is new to Gradle this would mean they are likely to overlook this and not notice that the compilation results or language features may depend on the version of the JVM running Gradle or somehow selected by the IDE. Even if the user is experienced, having the toolchain block readily available to be edited in the build script makes for a better UX when starting out with the project configuration.
Gradle init already pins many versions of libraries and tech-stack related things like Kotlin version. Therefore, adding Java version as well wouldn't be a significant change. Of course, this begs a question which Java version to choose. However, I believe using the latest available LTS should suffice. More specifically, Gradle 8.0 could include Java 17 toolchain configuration in the templates.
java {
    toolchain {
        languageVersion = JavaLanguageVersion.of(17)
    }
}

If for some cases Gradle generated build-logic containing precompiled script plugins, then the toolchain should be defined there, such that it can be shared between a library and an application sub-projects.

Most likely, applying the toolchains for all generated Kotlin project makes sense too, however, it could be more involved than just providing a top-level java-extension configuration.

We could ask the user and default to whatever the current JVM is.

If you are interested in contributing to Gradle, this issue is actionable and ready for contribution but might be challenging for first time contributors. See CONTRIBUTING.md for more information.
Asking for a Java version should be an additional question and default to the Java version that's running the script.

I've just tried this feature with the latest edge version (gradle-8.1-20230314080845+0000): It seems to work for non-multi-projects only. For a multi-module project, I'd have expected the configuration in <project>.java-common-conventions.gradle[.kts], but there is none.

@chkpnt, could you create a separate issue for your request if it is still relevant?


snapshot: replace "readonly" with View snapshot type

What started out as a simple PR to remove the "Readonly" column became an
adventure to add a proper type for a "View" snapshot. The short story here is
that we now get the following output:
$ sudo ctr snapshot ls
ID 									 PARENT 								 KIND
sha256:08c2295a7fa5c220b0f60c994362d290429ad92f6e0235509db91582809442f3 								  	 Committed
testing4								 sha256:08c2295a7fa5c220b0f60c994362d290429ad92f6e0235509db91582809442f3 Active

In pursuing this output, it was found that the idea of having "readonly" as an
attribute on all snapshots was redundant. For committed, they are always
readonly, as they are not accessible without an active snapshot. For active
snapshots that were views, we'd have to check the type before interpreting
"readonly". With this PR, this is baked fully into the kind of snapshot. When
Snapshotter.View is  called, the kind of snapshot is KindView, and the
storage system reflects this end to end.
Unfortunately, this will break existing users. There is no migration, so they
will have to wipe /var/lib/containerd and recreate everything. However, this
is deemed worthwhile at this point, as we won't have to judge validity of the
"Readonly" field when new snapshot types are added.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>WIP because I still need to update the snapshotter units tests. Even with that, the PR should be fully functional, so feel free to give it a try if you are brave.

Codecov Report

Merging #1236 into master will increase coverage by 0.11%.
The diff coverage is 84.12%.

@@            Coverage Diff             @@
##           master    #1236      +/-   ##
==========================================
+ Coverage   27.91%   28.03%   +0.11%
==========================================
  Files          28       28
  Lines        2826     2829       +3
==========================================
+ Hits          789      793       +4
  Misses       1888     1888
+ Partials      149      148       -1

Impacted Files
Coverage Δ

snapshot/naive/naive.go
45.58% <83.33%> (ø)
:arrow_up:

snapshot/btrfs/btrfs.go
49.35% <83.33%> (+1.09%)
:arrow_up:

snapshot/overlay/overlay.go
47.05% <85.71%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM

I like using the enum for this

LGTM
Feel free to merge now and we can update the test comment later


Add scitokens tests (SOFTWARE-4221)

And other miscellaneous HTCondor-CE test cleanups

@matyasselmeci this is ready (TM) now! There are still failures (https://osg-sw-submit.chtc.wisc.edu/tests/20210301-1454/results.html) but most importantly test_04_trace passes now. The other failures, I think are bugs in the actual software stack, for which my current theories are:

PBS/Slurm job submission fails due to our battle-axed blahp that #if 0s out the Globus bits
condor_ce_run doesn't pass along the _condor_SCITOKENS_FILE environment necessary for job submission so it doesn't actually use the generated credential

I've squashed a few of the commits but left a few that are useful (D_SECURITY:2 is incredibly verbose and fills up the 10M VMU output dirs, no trailing slashes in issuer mapfiles, token scopes must be space-separated)


PUMA-Clone created

Description 📜
This is a Puma-India Clone created using Bootstrap framework
Fixes #740

Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[X] Add a new project
[] Modified or enhanced the existing projects
[] Improve the readme of any project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[] Project using only HTML & CSS
[X] Project using HTML, CSS & JS
[] Project using ReactJs

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[X] I have performed a self-review of my own code or work.
[X] I have commented on my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸

@khushi-purwar Please review this PR

@gurjeetsinghvirdee I have removed .DS_Store


Popups in panels tab showing in wrong position

Godot version
4.0.beta10
System information
Mac OS 12.6 M1 Max
Issue description
When using the bottom panel tabs, the popups and popovers are showing in wrong positions. I noticed this problem in Tileset panel, SpriteFrames panel and Debugger panel. This problem solves itself when Godot is restarted but after some time, it happens again. I don't know if this help, but I'm using two external displays.
Debugger
https://user-images.githubusercontent.com/3025661/211197903-4231c7fc-535e-4b97-93dc-a65e505c5172.mov
SpriteFrames
https://user-images.githubusercontent.com/3025661/211197901-35268396-fbda-4879-b45c-a21d76ae56fe.mov
Tileset
https://user-images.githubusercontent.com/3025661/211197891-282dc557-c74c-4f01-9760-b3d1e536f5d3.mov
There is problem with popup in script editor too when right clicking on file name, but I could not record the video.
Steps to reproduce
I don't know how to reproduce this problem, it happens when I'm using the godot after some time.
Minimal reproduction project
N/A

I'm using Godot 4.0.beta11 since the release and this bug didn't occur.


View Menu Items are disabled inappropriately

VSCode Version: 1.8-Insiders
OS Version: macOS

Steps to Reproduce:

Open a new Window
Click View menu

I expect to be able to open the command palatte.
Instead it and all other menu items are grayed out.

@waderyan is that reproducible?

Happened to me too.

@bpasero
Can you try repro this way:

Open VSCode
Cmd+Shift+N to create empty workspace
Close every window other than the empty workspace
Quit VSCode
Reopen VSCode


https://link.short2url.in/akqQm

Domain
link.short2url.in
Link
https://link.short2url.in/akqQm
Version
0.0.0
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
(Optional) Anything else?
No response

.


Instructions on adding pull secret is wrong in documentation

The documentation (https://developer.ibm.com/tutorials/create-appsody-stack/) describes adding a secret as follows:
apiVersion: appsody.dev/v1beta1
kind: AppsodyApplication
metadata:
name: myapp
spec:
version: 1.0.0
applicationImage: myapp
stack: mystack
service:
type: NodePort
port: 8080
imagePullSecrets:
- name: mysecret
However, if you look at the CRD, is defined as
pullSecret: string
so, the addition in the yaml should be:
apiVersion: appsody.dev/v1beta1
kind: AppsodyApplication
metadata:
name: myapp
spec:
version: 1.0.0
applicationImage: myapp
stack: mystack
service:
type: NodePort
port: 8080
pullSecrets: mysecret
instead.

@henrynash please could you look into this?

will push new PR today for this

I have already created and merged a PR that corrected the code snippet, but had missed the surrounding text. This PR fixes that as well: https://github.ibm.com/IBMCode/Code-Tutorials/pull/2410
@airazabal Do you agree that the actual attribute should be pullSecret not pullSecrets (as you initially indicated), since this seems to be what the Appsody Operator supports?

Yes. That'll do it.

@airazabal the PR has now been merged and the fixes look good to me. Please can you close this issue if you're happy with the changes?

yes please close


Add 'create cluster' command

Initially  support AKS (and probably ACS until AKS is GA), but design to make it easy for other contributors to add GKE, EKS, etc.  Prompt for location and configuration parameters and kick it off.  Option to automatically configure VS Code extension to use the new cluster if that works with the spin-up time.

Great to see this get started!  Please feel free to @ me into any PRs...
--brendan

From: itowlson<EMAIL_ADDRESS>Sent: Friday, December 8, 2017 10:59 AM
To: Azure/vscode-kubernetes-tools
Cc: Subscribed
Subject: [Azure/vscode-kubernetes-tools] Add 'create cluster' command (#2)
Initially support AKS (and probably ACS until AKS is GA), but design to make it easy for other contributors to add GKE, EKS, etc. Prompt for location and configuration parameters and kick it off. Option to automatically configure VS Code extension to use the new cluster if that works with the spin-up time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fvscode-kubernetes-tools%2Fissues%2F2&data=04|01|bburns%40microsoft.com|17891a3ffed847cee88908d53e6dc4d4|72f988bf86f141af91ab2d7cd011db47|1|0|636483563528078759|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=6ycytsQGpL%2FVYlJ0XyyKklBx8vrZMiOC9rsWPH2XtRM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFfDggxGtLepZyq8ov8kADJ1JLEL2-Gcks5s-Yb-gaJpZM4Q7gbX&data=04|01|bburns%40microsoft.com|17891a3ffed847cee88908d53e6dc4d4|72f988bf86f141af91ab2d7cd011db47|1|0|636483563528078759|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=uSFeB6vcJS39cEPoD0YkRF7u4VaTveosO8wz0Tm2hRg%3D&reserved=0.


Added support for 'reflectable'

As you can see I also added two more tests plus a browser sample.

Thanks for the PR, using reflectable will definitely make this library better suited for use in the browser.
I spent some time experimenting with the code. One concern is I think the behaviour has changed compared to the old mirrors based version. Ideally this change will be backwards compatible so that we don't break people's existing code.
I've written some extra tests, these pass on the mirrors version, but fail when run with the reflectable version.
9e2308f531a348c852693e791080b04e0d5692dc


Target API 28

To support material components later

Done https://github.com/CherryPerry/Amiami-android-app/commit/6d501898d6fffab0c01470c07c6ab8c2c7800856


nixos/update-users-groups: read access to /etc/shadow for group shadow

Motivation for this change
#98676 set /etc/shadow group to shadow. However, the group wasn't given read-access to the file thus defeating the purpose of the PR. This PR now adds read-access to /etc/shadow for group shadow. This fix was accepted in the following comment: https://github.com/NixOS/nixpkgs/pull/98676#issuecomment-801233318
cc: @cole-h
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

I tried to reply via email, but apparently it didn't work..
I was just thinking if the permissions should be 0440 instead of 0640. Or is there a reason to have the shadow file writable on NixOS?
Also, do you know how to properly set up nginx so that it has access to /etc/shadow file? It works if I set users.extraUsers.nginx.extraGroups = [ "shadow" ] but I understood that no user should be put to that group (I don't know why) and instead setgid should be used. I tried the following but it didn't work:
security.wrappers.nginx = {
  source = "${config.services.nginx.package}/bin/nginx";
  group = "shadow";
};

Nginx service didn't seem to have access to the shadow file with this config. (I suppose the wrapper is just added to /run/wrappers/bin/nginx and the nginx service doesn't use that. Do you know how it should be set?

I'd modify the nginx service and add systemd.services.nginx.serviceConfig.SupplementaryGroups = [ "shadow" ]; -- that's how I do it for services that need my keys group.
FWIW, my Pihole installation has /etc/shadow as 0640 as well. (A fresh Arch ISO has 0400, but the file is owned by root:root.)
I don't think it really matters, since it's owned by root... root can do whatever it wants with that file even if it's r/o.

Thanks!

If you can find some reasoning on why 0440 is more desirable over 0640, feel free to open a PR with that justification. But, at the moment, I think it's fine to leave it as 0640 (considering it's owned by root:shadow).

Thanks! I now tried:
systemd.services.nginx.serviceConfig.SupplementaryGroups = [ "shadow" ];

instead of
users.extraUsers.nginx.extraGroups = [ "shadow" ];

but with SupplementaryGroups config, nginx isn't able to read /etc/shadow whereas with extraGroups config it is. I can see the following line in the generated systemd service file for nginx:
...
SupplementaryGroups=shadow
...

I wonder why it doesn't work.. Any ideas?

And you restarted the nginx unit afterwards? I've seen services need to be manually restarted despite the service definition changing underneath it.
Also try plain old serviceConfig.Group = "shadow";.
If still no dice, I have no idea :(

Ok, thanks! Yeah, I did restart the nginx unit manually. But at least setting extraGroups for user nginx works..

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nginx-pam-access-to-etc-shadow/6218/7


Proposal: integrate babel-plugin-ast-literal

What would you think about implementing something similar to babel-plugin-ast-literal?
I'm doing it here https://github.com/caesarsol/traph.macro/blob/master/macro.js and seems very useful.
Wonderful project BTW, it's what I was waiting for!

I think I'll maybe start by building a macro for AST generation!
Do you think it would be possible for babel-macros to execute itself on the macro definitions? This would make it possible for macro authors to not transpile their code before publishing.

Do you think it would be possible for babel-macros to execute itself on the macro definitions?

If you're asking whether babel-macros should transpile your macro ahead of running it (via babel-register or similar), then I think no, I don't really want to do that... If you'd like to not transpile, then you can require babel-register yourself.

What would you think about implementing something similar to babel-plugin-ast-literal?

Not sure what you mean. Could you elaborate?
Also, thanks for joining the community! 🤗

Sorry for my vagueness, I mean to give the users a function to build the AST more easily, as I did in my example using the ast-literal plugin.

Gotcha! Thanks! It's unclear to me the advantage over babel-template. Could you explain?

I think the main difference is performance: since the transpilation step absorbs the paraing there's no duplicated work.
Second I had difficulties substituting an objectExpression, is that supported? Can't babel-template substitute only identifiers?
I think it's all described in the project readme. I could do a bit more research though.

Gotcha, thanks!

performance: since the transpilation step absorbs the paraing there's no duplicated work.

That makes sense that it would be faster, but babel-template is fast enough, so that's not reason enough for me to add support/complexity.

Second I had difficulties substituting an objectExpression, is that supported? Can't babel-template substitute only identifiers?

I've not found that to be an issue personally.
Because it's really easy for folks to add their own dependencies, I think that's what we're going to do. If you'd like to add a note to the README about babel-plugin-ast-literal that'd be fine with me :)

Thanks for your feedback!
I'm going to try replicate the issue I had with babel-template and I'll see if I can add something 😄

I'm going to go ahead and close this for now.


Enum querying using "or" condition

Hi,
Sorry if I've missed it but I haven't found any info for easily querying using "or" conditions.
Let say we have:
as_enum :status, { active: 0, pending: 1, declined: 11 }
And we want to query records that are either active or pending. It doesn't seem that there's a shortcut for doing this yet. I think this can be implemented as part of the solution suggested in https://github.com/lwe/simple_enum/issues/95
So, we can do something like the following:
Item.where_with_enum(status: [:active, :pending])
Thanks

Good point, it indeed makes sense to support this and I think we would get support for this out of the box.

I think this one can be associated to #95 and closed.


Bump Python Runtime

Description
Changes proposed in this pull request:

use new Python runtime

Related issue(s)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/test pre-master-hydroform

/test pre-master-hydroform

/test pre-master-hydroform

/test all


Provide a native CLI program to convert LaTeX source into typst source.

If I get it correctly, for the time being, mitex only works as a WASM module and thus only works on the typst web app, but not for the CLI.
It would be better to provide a CLI program that runs like:
mitex -i foo.tex -o foo.typ

Then we can deal with the typst source with typst-cli.
Another benefit of this is that we can easily build a testset with a bunch of TeX sources, which will largely assure the quality and stability of mitex.

It is in plan but we may not have sufficient bandwidth to implement that feature.
Also I prefer following interface (aligned with typst-cli), since we may have some other commands (such as mitex spec generate):
mitex compile foo.tex
# is same as
mitex compile foo.tex -o foo.typ

Accurately, mitex is a transpiler but we still use compile here.

Btw, you can also process tex files by typst scripts:
#import "/packages/mitex/lib.typ": *
// or #import "/@preview/mitex:0.1.0": *

#let tex-files = json("list-of-tex-files.json");
#let output = tex-files.map(path => mitex-convert(read(path)))
#metadata(output) <transpiled>

Then you can get it by shell command:
typst query --root . main.typ "<transpiled>" > output.json

mitex only works as a WASM module and thus only works on the typst web app, but not for the CLI.

That's not true. WASM module is uniformly supported in typst webapp and cli

That's not true. WASM plugin is uniformly supported in typst webapp and cli. But i agree that it is good to have a mitex-cli

That's great, so there's a WASM runtime embedded in typst-cli?

Yes, typst has its own wasm runtime.

Yes, typst has its own wasm runtime.

Oh I found it, it's wasmi.

you can also process tex files by a typst script

Thanks, I will try this first.

But at the moment MiTeX only supports math equations, and we are ready to develop text mode in the next step.

But at the moment MiTeX only supports math equations, and we are ready to develop text mode in the next step.

Roger.


Update README.md

updated readme. no other changes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: mmcoralogix:x: ryantanjunmingYou have signed the CLA already but the status is still pending? Let us recheck it.


fmt: Allow downcasting a FmtSubscriber to its components

This commit overrides the downcast_raw method on FmtSubscriber so
that a FmtSubscriber can also be downcast to pointers to its generic
components (its on-event callback, filter, and NewVisitor).
This will allow implementations of the components of a FmtSubscriber
to support "out-of-band" APIs that don't require knowledge of the types
of the other components to downcast the subscriber to a concrete type.
This is intended for use-cases such as dynamic filter reloading (#42).
Signed-off-by: Eliza Weisman<EMAIL_ADDRESS>

Note that this requires changing the tokio-trace-core dependency to a Git dependency (as it requires tokio-rs/tokio#974, which hasn't made it to crates.io yet). We probably shouldn't merge this until tokio-trace-core v0.1.1 is published.
I'm opening it now primarily as a demonstration that this works & to build an implementation of filter reloading on top of.

The subscriber downcasting API landed in tokio-trace-core 0.2, so this is ready for review now.

@LucioFranco lol, I was in the process of removing the patch right as you said that. should be good now.


[FEAT] Dockerize the app

We need to containerize the application so that it works on every machine & for that we want a Dockerfile to be added to the project.

https://github.com/singodiyashubham87/ScrapeIt/pull/185


index.html wont load

Hi The index.html etherwallet-v3.21.02.zip wont load properly on any browser.

@Kryystian74 can you open the console and see if there's any error? it seems to be working on my end

Hi
Sory for the delay .
Yes there are some errors
.please see attachment
2018-03-15 16:06 GMT+00:00 gamalielhere<EMAIL_ADDRESS>
@Kryystian74 https://github.com/kryystian74 can you open the console
and see if there's any error? it seems to be working on my end
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kvhnuke/etherwallet/issues/1686#issuecomment-373430395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjrgcBA3lxDAh5MTCwFhdztZjqc7M4xDks5tepFpgaJpZM4SsbZz
.

--
Regards / Pozdrawiam
Krystian Zelazny

Usually it happens when you don't unzip the file first, did you unzip the downloaded file before opening index.html?

closing this, reopen if not solved


Todo: change git instructions to use nano as default editor

As far as I can see, there's nothing in our git instructions that would instantiate the editor – the commit message is passed as a command line argument (-m).
With that in mind, and with the lack of activity on this issue, I'm going to close this – but feel free to reopen if I'm missing something.


Update homepage design.

Starting with the new homepage design:

Adding a tooltip component from mdc.
styling it with corners and borders and etc...
change the environment colors
display short environment tags on release cards
fix bug with release cards shadows
make release cards smaller and shift around where the details are displayed

SRX-OD9V6S

There was a bug in ReleaseDialo. The time gets displayed in UTC timezone at all times.
e.g. I create a lock at 12:15
when it shows up on the ui it just says 11:15.
The actual stored date is correct but it's displayed incorrectly.
https://github.com/freiheit-com/kuberpult/blob/beed1f7e0e5ab892d0ed2edbb1fe9d5fa547dd42/services/frontend-service/src/ui/components/ReleaseDialog/ReleaseDialog.tsx#L219-L225
After fixing this issue. the release dialog snapshot started failing. I updated the snapshot to match my local machine output. but when it runs on github, the timezone is different and it fails.
I updated the test to mock the time display function as it's tested in Release Card


feat: launch ACA-Py securely with API Key

Due to the nature AWS security groups, opting to have an API key to access the admin UI for ACA-Py.
Otherwise, given an alternative, these portions can be commented out.

Verified that the above changes work as expected / nothing breaks :)

What happens if we provide an empty value here? Does it require authentication?

@reflectivedevelopment It looks like it doesn't even come up (left it as "")
ubuntu-issuer-1  |   File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
ubuntu-issuer-1  |     exec(code, run_globals)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/__main__.py", line 74, in <module>
ubuntu-issuer-1  |     main(sys.argv)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/__main__.py", line 71, in main
ubuntu-issuer-1  |     run(args)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/__main__.py", line 64, in run
ubuntu-issuer-1  |     run_command(command, args)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/commands/__init__.py", line 38, in run_command
ubuntu-issuer-1  |     module.execute(argv)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/commands/start.py", line 49, in execute
ubuntu-issuer-1  |     settings = get_settings(args)
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/config/argparse.py", line 98, in get_settings
ubuntu-issuer-1  |     raise e
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/config/argparse.py", line 95, in get_settings
ubuntu-issuer-1  |     settings.update(group.get_settings(args))
ubuntu-issuer-1  |   File "/home/indy/.venv/lib/python3.9/site-packages/aries_cloudagent/config/argparse.py", line 197, in get_settings
ubuntu-issuer-1  |     raise ArgsParseError(
ubuntu-issuer-1  | aries_cloudagent.config.error.ArgsParseError: Either --admin-api-key or --admin-insecure-mode must be set but not both.

(Had ACAPY_ADMIN_API_KEY="" and
# admin-insecure-mode: true
admin-api-key: ${ACAPY_ADMIN_API_KEY}

)


support PCI Express extended capabilities

Documented at PCI Express base specification, REV. 3.0, section 7.9.

done - may need follow up work but the basics are there

done - may need follow up work but the basics are there


Update the required fields for task swagger

Closes #12276

@mark-rushakoff I believe we have several other fields that are always present. I am not sure if we want to make them "required" or not.
If we want to require a larger list of fields we could start with the group of fields that are not omitted when empty.
	OrganizationID  ID     `json:"orgID"`
	Organization    string `json:"org"`
	AuthorizationID ID     `json:"authorizationID"`
	Name            string `json:"name"`
	Status          string `json:"status"`
	Flux            string `json:"flux"`

What do you think?

The current swagger.yml requires "organization" on a task. but the task only has "orgID" and "org". When we changed organization which used to represent the org id we forgot to update the required section of swagger's task definition.

I'm pretty sure at this point that the Task value is only returned from the server, i.e. it is read-only from the API consumer's perspective. The TaskCreate and TaskUpdate values are used for POST and PATCH. If that's accurate, then setting them Required just indicates to the client that they can rely on those fields being present.
Maybe @influxdata/api can help clarify which is more appropriate here.

I think that is true mark. I think we should definitely make ID required.


How should we create documentation of the operations, modules, datatypes a plugin provides?

This documentation existing is really important for end-users as it tells them what each plugin can do for them. The content of this documentation is contained in the python code for each plugin, and can be accessed via the kiara API.
Existing examples of this documentation are here, and the content comes directly from the module code eg this datatype docstring
There's a distinction between plugins created by the internal team, and those created by external people. We probably want documentation for internal plugins to live in one place, alongside the main docs, assuming this matches with @MariellaCC's survey results.
But we also need external plugins to be able to create standalone docs, as they currently do. The plugin template should come with a github action that deals with building and publishing these docs automatically, with no intervention from the developer.
Because we can get all the content via Kiara's API and the docs can be built in Github actions, we aren't constrained to just using a python-based solution for this. It may be advantageous to use a javascript-based solution, using at least some of the technologies we use for the mini-apps to enable component and styling reuse. This would probably be Svelte for components, and possibly SvelteKit for site building.
There's some vague prototypes of what this could look like in this repo which could have some code that could be adapted into components, or a static site builder, but it isn't currently good, tested or documented.
Open questions I can think of

what features does a standalone plugin docs site need to have? Is just one big blob of HTML enough or does it need things like a search box, navigation etc.
What technology should we use to make the site(s)?

How easy is it to integrate components from the mini-apps into that (via an npm package?)?
How easy is it to make something that can build completely standalone with just input from a cookiecutter template?
what are other members of the team comfortable maintaining? I'm most comfortable using svelte/kit and/or astro, but maybe others have other areas of expertise. @makkus does this match with your comfort zone?

do the docs need to be able to cover multiple versions of a plugin? are there nice ways to communicate if a thing was added/removed in a particular version of a plugin?
do these docs need to support different languages? I guess probably not, since the content coming from kiara itself is (currently?) only in English?

Agree with everything said here, thanks for the write-up!

what features does a standalone plugin docs site need to have? Is just one big blob of HTML enough or does it need things like a search box, navigation etc.

A minimal navigation would probably good, with an overview page of what components are available in a plugin and a short description, and links to more detailed information.
One thing that would be really good to have is every component having it's own predictable url (or url & anchor), something like https://dharpa.org/kiara/plugins/PLUGIN_NAME/operations#table.sort (just an example, can be anything that works best -- if we can get that to work for external plugins it would be nice, but I'm mostly concerned about our own official plugins here), That would make it easier to integrate links into our app(s) to send users to places where they can get more information if they want/need.

What technology should we use to make the site(s)?

I'd also lean towards svelte/svelte-kit. It's easy to pick up, very powerful, actively developed, and has a high user satisfaction.
streamlit is nice in that it is Python only, but my experience working with it makes me think it'll be too inflexible for our needs, since a lot of the stuff we are doing UI wise is not a trivial top-to-bottom app.  @MariellaCC has experience with Plotly Dash, so she could comment on that. My instinct is going for a full JS framework though, because in the end it just gives us the most flexibility and powerful features without having to worry about yet another intermediate layer.
For extra cookie points, it would be interesting if we can make it so that we create ipython widgets/streamlit components/other tech components by wrapping our svelte components in an automated way. I do see some interesting use-cases for something like streamlit (simpler apps, simpler deployment, prototyping, quick 'UX design sketches', ...). We probably can't afford to spend too much time on this, but if we could at least in theory prove that it would be possible (which I think it is), it would be a valueable thing to have IMHO. But, as I said, this should not keep us from the more important things, and can always be done later on.

do the docs need to be able to cover multiple versions of a plugin? are there nice ways to communicate if a thing was added/removed in a particular version of a plugin?

Given our focus on reproducability/lineage/metadata, I do think it would be good to keep the history. We haven't really talked about how we version plugins, but keeping one version of documentation per git tag would be good.
Sidenote: I haven't really thought through all the implications, but in theory data types and modules would have independent versions from the plugin that contains them. For example, a module doesn't need to change because the plugin it contains is updated (e.g. by adding more modules). It's a complicated issue though, with lots of things to consider, so I just put this here in case we stumble upon something in our implementation where this might be relevant.

are there nice ways to communicate if a thing was added/removed in a particular version of a plugin?
Interesting question, didn't cross my mind yet. We could maybe maintain a database with all modules/data types versions and their metadata by feeding into it at every release of a plugin? That way, we could present that information in any way that becomes useful? A database like that might also prove useful for other metadata related features later on, for example we wouldn't need to have a running kiara service for some type of information rendering... Hmmmmmmmmm, something to mull over....

do these docs need to support different languages? I guess probably not, since the content coming from kiara itself is (currently?) only in English?
I guess, depending on how much effort it is, maybe we could use the i8n features that come with our selected framework, but only implement English for now? But that's mainly a trade-off between how much resources we can afford to spend on this now, against how likely it is in the future that we'll need it and how much more difficult it would be to implement it without this sort of preparation. I guess a question to answer once we have a rough plan and priorities? It would be best practice to prepare for it I guess.

Speaking about best practices, what should/can we do about accessibility? I don't have much experience in that field, but my guess is it's much easier to not have to retro-fit that, but consider it from the beginning.

One thing that would be really good to have is every component having it's own predictable url (or url & anchor),

Great idea! like a permalink for a component. Would/could this also include version information? Could the plugin package be able to communicate what the base URL for its docs is, for non-core plugins that can't use dharpa.org/kiara, so we can always give full links?

My instinct is going for a full JS framework though, because in the end it just gives us the most flexibility and powerful features without having to worry about yet another intermediate layer.

My one concern with JS is testing - not applicable so much to these docs, but definitely to other kinds, how do we make sure the code contained in the docs runs and is correct. IIRC there's already something that does this for the existing mkdocs implementation, but I'm not sure how I'd do that via JS

but keeping one version of documentation per git tag would be good.

this would be a kind of deploy once and leave running without ever changing thing? Does a git tag correspond to a python package version that can be installed? How do we know what version(s) of kiara core it could be installed alongside to get the documentation from the plugin via kiara's API?
It would be good to document how we do versioning, and what versions (of packages and of other things?) mean for end users, so they can know whether they can safely update things they are depending on. I'd kind of assumed it was something like semver at the python package level, but that's not the case? I'll add a note to the 'concepts' bit of the core docs outline to remind me this needs doing
Re permalinks for things, would it then look like  /plugins/PLUGIN_NAME/vX.Y.Z/operations/table.sort or is it more meaningful to version the operations etc themselves rather than the plugin? /plugins/PLUGIN_NAME/operations/table.sort/vX.Y.Z

are there nice ways to communicate if a thing was added/removed in a particular version of a plugin?

A database is a nice idea but not something I'd feel confident maintaining. Would something like a json/yaml file in the docs github repo be able to achieve something similar without needing to maintain a database server?
We could consider publishing changelogs for each package alongside this documentation, so users can get summaries of what changed in each version? Requires a bunch of effort to write for the plugin authors, but I think would be really useful for end users. (I keep getting tripped up by changes in the names of operations in the network analysis plugin, being able to see a list of what changed between versions and maybe something like a migration guide would be super useful)

maybe we could use the i8n features that come with our selected framework, but only implement English for now?

sounds good. It would be nice to make it easy to do translations in the future, but this isn't something I have any expertise in (technically or linguistically! my other languages are not fluent enough to write technical docs in).

Speaking about best practices, what should/can we do about accessibility? I don't have much experience in that field, but my guess is it's much easier to not have to retro-fit that, but consider it from the beginning.

Sorry I forget accessibility is even a question! I'll make sure that's done to the best of my ability from the start - I know a decent amount and care a lot. For our purposes, it will mostly look like generating semantic HTML, making sure everything is possible and logical to navigate with a keyboard, and using a clear colour scheme. Might also be worth adding an accessibility statement, to the effect of we're doing our best as a small team, tell us if something isn't working for your needs?

Proposal for the technical side of how to make a start on this in #3, but I'll leave this issue open since there's still a bunch of open questions.
Having done some research, it seems that there isn't a particularly good solution for translation in sveltekit at the moment. Since kiara's internal docs are also only in English, and the team has very limited resources, I think we should not consider translations for now, and wait until there's a need from kiara's users, more dev capacity and hopefully the sveltekit community has settled on a decent approach to take.

Great idea! like a permalink for a component. Would/could this also include version information?

Yeah, I think that would be best. Depending on how we version the docs themselves, it might just be a matter of <base_url>/<plugin_version>/<rest of docs> ?

Could the plugin package be able to communicate what the base URL for its docs is, for non-core plugins that can't use dharpa.org/kiara, so we can always give full links?

Yes, currently I've hardcoded dharpa.org in the template I think, but that would be easy enough to change and add to the metadata of the project.

this would be a kind of deploy once and leave running without ever changing thing? Does a git tag correspond to a python package version that can be installed? How do we know what version(s) of kiara core it could be installed alongside to get the documentation from the plugin via kiara's API?

The only piece of information we have is the kiara pip dependency (which can be investigated at runtime -- or in a pre-render step). I think we have no choice but to assume that this is correct.

Re permalinks for things, would it then look like /plugins/PLUGIN_NAME/vX.Y.Z/operations/table.sort or is it more meaningful to version the operations etc themselves rather than the plugin? /plugins/PLUGIN_NAME/operations/table.sort/vX.Y.Z

I guess that depends on the framework we are using in part, and whether we link to our 'central' site, or each plugins documentation directly for the permalinks. The latter would have the advantage of automatically also working for external plugins. But would mean that we would not link to our 'central' official doc, but each plugin independently. Maybe if we go with the first option it would work for both cases?

A database is a nice idea but not something I'd feel confident maintaining. Would something like a json/yaml file in the docs github repo be able to achieve something similar without needing to maintain a database server?

Yeah, as we talked about earlier, I think that is a great idea, and much better.

We could consider publishing changelogs for each package alongside this documentation, so users can get summaries of what changed in each version? Requires a bunch of effort to write for the plugin authors, but I think would be really useful for end users. (I keep getting tripped up by changes in the names of operations in the network analysis plugin, being able to see a list of what changed between versions and maybe something like a migration guide would be super useful)

Yes, I think we can partially automate that by establishing best practices for git commits, and then automatically generating those changelogs. It's going to be messy and incomplete either way though, I fear.
As for changes in operation names, this is something that happens at the moment because I don't have enough experience yet to have a sense of how to design modules well from the beginning, but I really want to minimize/discourage/forbid that sort of change, if at all possible. Modules should have a stable interface, and if a change is needed, the old module should stay in place and a new one with a different name created. Maybe we can be a bit smarter and have those module sub-versions and do some basic dependency resolution, but that goes back to our problem with having enough time and resources.

streamlit is nice in that it is Python only, but my experience working with it makes me think it'll be too inflexible for our needs, since a lot of the stuff we are doing UI wise is not a trivial top-to-bottom app. @MariellaCC has experience with Plotly Dash, so she could comment on that.

@caro401 I agree that Streamlit comes with too many limitations as soon as the scope of the app is beyond a certain level of complexity (it is difficult to give a precise scale). Still, I found it helpful for prototyping purposes or to create quick dashboards up to a certain level of complexity. For my needs in the past, Streamlit was not flexible enough, so I experimented with Plotly Dash. Before that, I had experimented with Flask combined with React (which remains my preferred experience in terms of flexibility but the choice of tech was quite arbitrary). As I am not specialised in front-end development, it is difficult to have an opinion on a suitable solution. My comment is only about the flexibility needed from past experiments, and I agree that, in general, Streamlit is too inflexible for sustainable mini-apps.

Ok, I implemented a first version of creating a data structure that contains all that info. I haven't added it to any CI runs yet, but I will do so in the future and probably create a json artefact with it whenever a tagged version is released.
It can be used like so from the commandline:
kiara info plugin explain kiara_plugin.tabular --format json

To get the json-schema for the data, you can do:
kiara info plugin explain kiara_plugin.tabular --format json-schema

Initially I also wanted to auto-create Typescript classes, but the library I used for that broke with the pydantic 2 release. I hope that the json-schema is good enough for now.
For development, I'd suggest you just write some example data into a json file and use that to retrieve any information you need. It should be trivial to convert that to a CI workflow where we first auto-write the json file, then pick it up from the doc render step.


Should not show dependencies in member lists

Normally when hitting Control + Space (on a Mac) to reveal members for an object VS Code will only show members of the object.

However, when ts-importer is installed it shows all your potential dependencies in your app. In this scenario this is just noise and unfortunately makes the member dropdown almost completely unusable.

I love this extension and recommend it to fellow developers but this specific issue is a show stopper for them. Its a shame as I must admit, I feel like ts-importer makes me much more productive with auto importing dependencies, but less productive by getting in the way of member lists. If this issue was fixed I feel like it would make a huge difference in productivity. 🙏

Please try the tsimporter.lowImportance option.
It is very hard to find out where the suggestion is required and where not.

Excellent, seems like a reasonable solution, thanks! 👍
CC @tomSawkins


Revert with no reason, TX appears to succeed when looking at stack trace on forked mainnet.

Component
Forge
Have you ensured that all of these are up to date?

[x] Foundry
[x] Foundryup

What version of Foundry are you on?
forge 0.2.0 (16b4ef6 2022-07-13T00:15:34.493056Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Apple Silicon)
Describe the bug
I am running tests against the curve SUSD pool on a forked version of mainnet. My contract calls the function remove_liquidity_one_coin with all of the proper parameters and approvals in place. For whatever reason, the test fails and I get a revert.
When I test with a stack trace, the stack trace leads to nowhere, and I can see that the emitted transfer event of sending the curve zap pool sending USDC back to my contract goes through successfully.
At this point I am just trying to nail down where exactly this error is originating from. I have included a picture of the stack trace at the bottom. The empty () simply leads back to the start of the test, not a particular function call.

This easiest way to reproduce this error would be to quickly write a test where you write a balance of sCrv to yourself, and attempt to call remove_liquidity_one_coin on the sUsd Zap Pool: 0xFCBa3E75865d2d561BE8D220616520c171F12851

Do you need to pass a provider url for the tests to run ? I ran into something similar the other day

yes I am passing a forked mainnet url via --fork-url

it was an error with my interface, it is fixed now.


Circular reference throw error

🐛 Bug Report
my data is circular reference，when I set data by use immer，I get a error Maxcallsize error，immer cannot deep clone a data that is circular reference？？
To Reproduce
let m = {}
let n = {}
m.n = n
n.m = m
... model reducer
state.m = m

Steps to reproduce the behavior:
Expected behavior
state.m is successed be m
Link to repro (highly encouraged)
Environment

Immer version:
[ ] Occurs with setUseProxies(true)
[ ] Occurs with setUseProxies(false) (ES5 only)

read api and know why

This is what ^ is referring to: https://immerjs.github.io/immer/pitfalls#immer-only-supports-unidirectional-trees


SharedClassesAPI_0 extended "libsharedClasses.so could not be opened" on linux, aix, osx

SharedClassesAPI_0 started failing in the extended system test run at the OpenJ9 project.
JVMT stderr JVMJ9TI001E Agent library /home/jenkins/workspace/Test-extended.system-JDK11-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.sharedClasses.jvmti/bin/native/linux_x86-64/libsharedClasses.so could not be opened (/home/jenkins/workspace/Test-extended.system-JDK11-linux_x86-64/jvmtest/systemtest/openj9-systemtest/openj9.test.sharedClasses.jvmti/bin/native/linux_x86-64/libsharedClasses.so: cannot open shared object file: No such file or directory)
JVMT stderr JVMJ9VM015W Initialization error for library j9jvmti29(-3): JVMJ9VM009E J9VMDllMain failed
STF 06:13:34.118 - **FAILED** Process JVMT ended with exit code (1) and not the expected exit code/s (0)

https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-linux_390-64_cmprssptrs/133
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-linux_390-64_cmprssptrs/109
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-linux_x86-64/129
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-linux_x86-64/112
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-linux_x86-64_cmprssptrs/128
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-linux_x86-64_cmprssptrs/116
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-linux_ppc-64_cmprssptrs_le/127
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-linux_ppc-64_cmprssptrs_le/111
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-osx_x86-64_cmprssptrs/6
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-osx_x86-64_cmprssptrs/22
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-aix_ppc-64_cmprssptrs/122

@Mesbah-Alam @smlambert

@pshipton - this failure was introduced by a change made by me in the sharedClasses.jvmti compile makefile recently. This will resolve it: https://github.com/eclipse/openj9-systemtest/pull/59

Guess I opened this at the wrong place? I'll just close it since we have a fix in hand.


API Reference Documentation

The API reference documentation needs to be auto-generated akin to other Python packages.

Should be solved by #171


Unable to sign-in

Hey guys,
When I run the project, the home page comes up but It doesn't go pass the signin page. When I click on sign in, It redirects to "https://login.windows.net", then it redirects to a blank page with http://localhost URL.
I've entered necessary credentials on web.config and register it on service manager.
    <add key="webpages:Enabled" value="false" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
    <add key="ida:GraphResourceId" value="https://graph.windows.net" />
    <add key="ida:GraphUserUrl" value="https://graph.windows.net/{0}/me?api-version=2013-11-08" />
    <add key="ida:TenantID" value="6f321bc2-998******************"/>
    <add key="ida:ClientID" value="71bd5ba8-2c38*****************" />
    <add key="ida:Password" value="LWCyzPloey5JJgTgAI*******/>
    <add key="ida:AuthorizationUri" value="https://login.windows.net" /></appSettings>```

![service_manager_screenshot](https://cloud.githubusercontent.com/assets/11508035/6793081/e35f502e-d17c-11e4-8c20-f7da131e032e.PNG)

Hey Zombieland,
To use the project as-is, you need to set the permissions as per step 6 in the Register app to consume Office 365 APIs part of the Readme. In particular, getting a blank redirect implies the Users and Groups permission isn't set.
Let us know if that helps,
Andrew

Hi Andrew,
It looks like I do have proper delegated permissions. Now, I've added application permissions but still no luck. Please see below screenshot.
I don't think it's an issue with my instance since calendar entries come back using the API Sandbox (which is awesome BTW). Please help.

Looking at your screenshot, I am not seeing permissions for Windows Azure Active Directory. The delegated permission in that case would be "Enable sign-on and read users' profiles". This would  have been added during the Add Connected Services step if you had set that permission.

Hi Andrew,
Please see my screenshot below. Am I looking at the wrong screen?

Hi Zombieland,
it is the right screen, but your permissions don't look right. It looks like you have super-user permissions for exchange :-)
You should be able to click on the big green button "Add application", then add Windows Azure Active Directory from the dialog that pops up. Once that succeeds, you should see a new line in your permissions to other applications list. It will look like this:

The actual permission you then need to select is this one:

The right permissions should have been added when you followed the Readme instructions. However, hopefully this will unblock you.
Andrew

Thanks a lot Andrew!! We are moving away from Google Apps to Office 365 here at Nutanix. You guys rock!

Woohoo on us rocking and your migration path! :-)  Glad I could help.

Awesome.
Sent from my Windows Phone

From: Andrew Byrne<EMAIL_ADDRESS>Sent: ý3/ý23/ý2015 19:41
To<EMAIL_ADDRESS>Subject: Re: [O365-ASPNETMVC-Start] Unable to sign-in (#12)
Woohoo on us rocking and your migration path! :-) Glad I could help.
—
Reply to this email directly or view it on GitHubhttps://github.com/OfficeDev/O365-ASPNETMVC-Start/issues/12#issuecomment-85310688.


Make FlameGraph parameters configurable

Add command-line option to tune certain FlameGraph attributes:

imagewidth
frameheight
minwidth
etc.

Added the following command-line options:
  --title TITLE
  --width PX
  --height PX
  --minwidth PX

--reverse is handy too.

flamegraph.pl --reverse and --inverted (ie. icicle graph) work together to keep the stack the right way up while grouping by the top of stack - I use it for the allocation profiling, it can be used elsewhere also.

@ceeaspb So what do you suggest?

add support for --inverted if possible

While this one is easy to implement, I don't actually plan to replicate and maintain all possible FlameGraph options. It will be enough to support just the most common use case. collapsed output provides the possibility to customize flame graphs using external script.
Does it make sense to combine --reverse and --inverted into one singe option? I have never used icicle graphs myself, but if this is a popular use case, I don't mind adding this option to async-profiler.


"possible authentication failure. wrong credentials?","user":"sensu"

Not sure if this is an issue with the playbooks or my intelligence, but I've exhausted all of the docs that I can find.  I am using ansible-sensu to install Sensu on a CentOS-7 host with the following playbook:
- hosts: sensu_masters
  become: yes

  tasks:
    - name: Install EPEL
      yum:
        name: epel-release

    - name: Install sensu
      include_role:
        name: sensu
      vars:
        sensu_master: true
        sensu_include_dashboard: true
        redis_server: true
        sensu_deploy_redis: true
        rabbitmq_server: true
        rabbitmq: true
        sensu_deploy_rabbitmq: true
        sensu_include_plugins: true
        dynamic_data_store: "{{ playbook_dir }}/sensu_data/store"
        static_data_store: "{{ playbook_dir}}/sensu_data/static"
        rabbitmq_host: <IP_ADDRESS>
        redis_host: <IP_ADDRESS>
        sensu_api_host: <IP_ADDRESS>
        rabbitmq_sensu_user_name: sensu
        rabbitmq_sensu_password: sensu
        sensu_api_user_name: sensu
        sensu_api_password: sensu

    - name: Allow ports through firewall
      firewalld:
        port: "{{ item }}"
        permanent: true
        state: enabled
        immediate: yes
      with_items:
        - 3000/tcp
        - 5671/tcp
        - 6379/tcp
        - 4567/tcp

Everything installs ok and I can log into the dashboard.  However, I get a Datacenter sensu-81 returned: 500 Internal Server Error and I see
{"timestamp":"2017-10-14T12:51:15.761755-0400","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2017-10-14T12:51:15.761841-0400","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2017-10-14T12:51:16.290375-0400","level":"info","message":"api response","request":{"remote_address":"<IP_ADDRESS>","user_agent":"Go-http-client/1.1","method":"GET","uri":"/stashes","query_string":null,"body":""},"status":500,"content_length":59,"time":0.0}

in /var/log/sensu/sensu-api.log.  It seems obvious that some component us using the wrong creds to access the API, but I do not know which those are.  Can someone point me to the doc that I am missing to make this work?
Thanks,
Steven.

I have the identical same issue but on ubuntu.
With an almost default setup:
---

- hosts: all
  user: ubuntu
  become: yes
  roles:
    - { role: cmacrae.sensu }

sensu-master host_vars:
sensu_master: true
sensu_include_dashboard: true
rabbitmq_server: true
redis_server: true

Hey @ismc and @jcoetsie,
So sorry for the delay in responding, are you still hitting this issue?

Hey @romainrbr - Thanks for the PR!
@hgfranco - Can you try to upgrade Erlang, this role is updated to support that now, let me know if that resolves your issue.

With https://github.com/sensu/sensu-ansible/pull/130 merged in, the updated version of Erland/RabbitMQ should resolve the issues here. I'll be cutting the 2.0.0 release of this role today/tomorrow as well which will officially have that change. If you'd like to use it before that feel free to pull the role directly from Github.
I think this is clear to close out but if I'm missing anything just let me know, happy to continue troubleshooting. I also invite anyone to swing by #help (or #ansible) in the Sensu Community Slack room for more real-time troubleshooting.

Hello All,
I seem to have a problem in the Uchiwa dashbord . It gives me an error "cannot load the uchiwa configuration" .
Using the puppet forge modules for
Uchiwa
Sensu
Rabbitmq
Redis .
Below are the log files :+1:
● uchiwa.service - LSB: Uchiwa, a Sensu dashboard.
Loaded: loaded (/etc/rc.d/init.d/uchiwa; bad; vendor preset: disabled)
Active: active (exited) since Wed 2018-02-14 04:08:47 EST; 1h 47min ago
Docs: man:systemd-sysv-generator(8)
Process: 5051 ExecStop=/etc/rc.d/init.d/uchiwa stop (code=exited, status=0/SUCCESS)
Process: 5061 ExecStart=/etc/rc.d/init.d/uchiwa start (code=exited, status=0/SUCCESS)
Feb 14 04:08:47 sensu.vm.com systemd[1]: Starting LSB: Uchiwa, a Sensu dashboard....
Feb 14 04:08:47 sensu.vm.com uchiwa[5061]: uchiwa started.
Feb 14 04:08:47 sensu.vm.com systemd[1]: Started LSB: Uchiwa, a Sensu dashboard..
Feb 14 04:08:47 sensu.vm.com su[5064]: (to uchiwa) root on none
[vagrant@sensu ~]$
[root@sensu conf.d]# tail -f /var/log/uchiwa.log
{"timestamp":"2018-02-14T05:42:23.13277836-05:00","level":"info","message":"Updating the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:28.133447015-05:00","level":"warn","message":"GET https://<IP_ADDRESS>:4567/sensu/stashes returned: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
{"timestamp":"2018-02-14T05:42:28.133561144-05:00","level":"warn","message":"Connection failed to the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:28.13361067-05:00","level":"info","message":"Updating the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:33.134123579-05:00","level":"warn","message":"GET https://<IP_ADDRESS>:4567/sensu/stashes returned: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
{"timestamp":"2018-02-14T05:42:33.134260766-05:00","level":"warn","message":"Connection failed to the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:33.134306015-05:00","level":"info","message":"Updating the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:38.134835092-05:00","level":"warn","message":"GET https://<IP_ADDRESS>:4567/sensu/stashes returned: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
{"timestamp":"2018-02-14T05:42:38.134939244-05:00","level":"warn","message":"Connection failed to the datacenter sensu"}
{"timestamp":"2018-02-14T05:42:38.134982673-05:00","level":"info","message":"Updating the datacenter sensu"}
sensu-api.service - sensu api
Loaded: loaded (/usr/lib/systemd/system/sensu-api.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-02-14 05:53:39 EST; 5min ago
Main PID: 12984 (sensu-api)
CGroup: /system.slice/sensu-api.service
└─12984 /opt/sensu/embedded/bin/ruby /opt/sensu/bin/sensu-api -c /etc/sensu/config.json -d /etc/sensu/conf.d -e /etc/sensu/extensions -p /var/run/sensu/sensu-api.pid -l /var/log/sensu/sensu-...
Feb 14 05:53:39 sensu.vm.com systemd[1]: Started sensu api.
Feb 14 05:53:39 sensu.vm.com systemd[1]: Starting sensu api...
[vagrant@sensu ~]$
[root@sensu conf.d]# tail -f /var/log/sensu/sensu-api.log
{"timestamp":"2018-02-14T05:41:25.540447-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:41:25.540922-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:41:45.539946-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:41:45.540261-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:05.539962-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:05.540192-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:25.540590-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:25.540669-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:45.542256-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:45.542469-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","u
sensu-client.service - sensu client
Loaded: loaded (/usr/lib/systemd/system/sensu-client.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-02-14 05:53:41 EST; 3min 51s ago
Main PID: 13001 (sensu-client)
CGroup: /system.slice/sensu-client.service
└─13001 /opt/sensu/embedded/bin/ruby /opt/sensu/bin/sensu-client -c /etc/sensu/config.json -d /etc/sensu/conf.d -e /etc/sensu/extensions -p /var/run/sensu/sensu-client.pid -l /var/log/sensu/...
Feb 14 05:53:41 sensu.vm.com systemd[1]: Started sensu client.
Feb 14 05:53:41 sensu.vm.com systemd[1]: Starting sensu client...
[root@sensu conf.d]# tail -f /var/log/sensu/sensu-client.log
{"timestamp":"2018-02-14T05:41:59.764609-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:41:59.764693-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:09.765490-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:09.765577-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:21.768444-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:21.768687-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:35.769374-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:35.769622-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}
{"timestamp":"2018-02-14T05:42:51.769198-0500","level":"warn","message":"transport connection error","reason":"tcp connection lost"}
{"timestamp":"2018-02-14T05:42:51.769386-0500","level":"warn","message":"transport connection error","reason":"possible authentication failure. wrong credentials?","user":"sensu"}

[root@sensu conf.d]# curl -i -u sur:sur http://localhost:15672/api/whoami
HTTP/1.1 200 OK
Server: MochiWeb/1.1 WebMachine/1.10.0 (never breaks eye contact)
Date: Wed, 14 Feb 2018 10:43:37 GMT
Content-Type: application/json
Content-Length: 83
Cache-Control: no-cache
{"name":"sur","tags":"administrator","auth_backend":"rabbit_auth_backend_internal"}[root@sensu conf.d]#
[root@sensu conf.d]# tail -f<EMAIL_ADDRESS>accepting AMQP connection <0.359.0> ([::1]:47110 -> [::1]:5672)
=INFO REPORT==== 14-Feb-2018::05:43:45 ===
accepting AMQP connection <0.366.0> ([::1]:47184 -> [::1]:5672)
=INFO REPORT==== 14-Feb-2018::05:43:45 ===
accepting AMQP connection <0.369.0> (<IP_ADDRESS>:51612 -> <IP_ADDRESS>:5672)
=INFO REPORT==== 14-Feb-2018::05:43:49 ===
accepting AMQP connection <0.372.0> ([::1]:47208 -> [::1]:5672)
COuld you please help me fix it . I ma trying to install this on an Centos7 machine.

<Adding he config files as well :+1:
[root@sensu conf.d]# cat rabbitmq.json
{
"rabbitmq": {
"port": 5672,
"host": "<IP_ADDRESS>",
"user": "sensu",
"password": "sur",
"vhost": "/sensu",
"heartbeat": 30,
"prefetch": 1
}
}
[root@sensu conf.d]# cat redis.json
{
"redis": {
"port": 6379,
"host": "<IP_ADDRESS>",
"reconnect_on_error": true,
"db": 0,
"auto_reconnect": true
}
}
[root@sensu conf.d]# cat api.json
{
"api": {
"port": 4567,
"host": "<IP_ADDRESS>",
"bind": "<IP_ADDRESS>"
}
}
[root@sensu conf.d]# cat transport.json
{
"transport": {
"name": "rabbitmq",
"reconnect_on_error": true
}
}[root@sensu conf.d]# cd ..
[root@sensu sensu]# cat uchiwa.json
{
"sensu": [
{
"name": "sensu",
"host": "<IP_ADDRESS>",
"ssl": true,
"insecure": true,
"port": 4567,
"user": "sensu",
"pass": "correct-horse-battery-staple",
"path": "/sensu",
"timeout": 5
}
],
"uchiwa": {
"host": "<IP_ADDRESS>",
"port": 3000,
"user": "",
"pass": "",
"refresh": 5
}
}

Below is the list of Modules in puppetfile :+1:
#!/usr/bin/env ruby
forge "https://forgeapi.puppetlabs.com"
mod 'puppetlabs-motd', '1.7.0'
#mod 'puppetlabs-registry', '2.0.1'
mod 'puppetlabs-registry', '1.1.4'
mod 'puppetlabs-stdlib', '4.24.0'
#Redis Modules
mod 'dwerder-redis', '2.1.0'
mod 'puppet-rabbitmq', '8.1.0'
mod 'puppet-archive', '2.2.0'
mod 'garethr-erlang', '0.3.0'
mod 'stahnma-epel', '1.3.0'
#sensu MOdules
mod 'sensu-sensu', '2.50.0'
mod 'lwf-remote_file', '1.1.3'
#uchiwa Modules
mod 'yelp-uchiwa', '2.0.0'
mod 'puppetlabs-apt','4.5.1'
Please help me sort this out :(
Thanks ,
Krithi


Fix modernizr url

If we are in a subdirectory it's not working anymore because the path of modernizr is all time _static/...

Thanks!

@ericholscher Is there a periodic release cycle with this fix or target date for v0.1.9?

@dghubble not yet. I believe the plan at this point is to release a v1.0.0 backwards incompatible release, as per #215. I'll be working on this more this week.


Adds pypy scheduler tests to tox

I just started running my scheduler with PyPy, and it's reducing latency
so I'd like to stick with it. I've added tests to tox.ini to ensure that
this functionality is not lost with future updates. Most of the database
libraries used in luigi aren't supported in PyPy, so I've made a second
requirements.txt that removes them and added ignore flags for the test
files that import them.

So we then say that you may use the scheduler with pypy, but not the client code. Ok sure makes sense.
Have you by the way measure if ping and add_task gets faster?
Why do you care about latency by the way? Just so the server doesn't get overloaded or so that interactive users of luigi get a smoother experience?
Thanks for the patch!!

I didn't look into ping and add_task. I don't think that ping was slow enough to make a difference on my setup. You can let me know if it seems to do anything for you.
 I also want to keep resource usage on the machine down as much as possible because I run all of my workers on it and it can get slow sometimes.


Nginx Read Only File System

A lot of Security people recommend running Images in Kubernetes or other Hypervisors in a read-only mode. one example
When trying to run the nginx image in read only mode like this:
docker run -it -p8080:8080 --read-only --tmpfs /tmp cgr.dev/chainguard/nginx:latest

I receive the following error:
s6-svscan: fatal: unable to mkdir .s6-svscan: Read-only file system

related ? https://github.com/chainguard-dev/apko/issues/497

related ? chainguard-dev/apko#497

This should not be related since we are using a pinned version of apko before that issue (497)
This may be able to be solved by creating this directory ahead of time in apko yaml, unsure about the inner workings of s6

Use docker run -it -p8080:8080 --read-only --tmpfs /tmp --tmpfs /sv cgr.dev/chainguard/nginx:latest to allow the supervisor to manage its state.

Same issue here.

Wondering if there is anything to reuse from this section below from the nginx-unprivileged container image:
# implement changes required to run NGINX as an unprivileged user
RUN sed -i 's,listen       80;,listen       8080;,' /etc/nginx/conf.d/default.conf \
    && sed -i '/user  nginx;/d' /etc/nginx/nginx.conf \
    && sed -i 's,/var/run/nginx.pid,/tmp/nginx.pid,' /etc/nginx/nginx.conf \
    && sed -i "/^http {/a \    proxy_temp_path /tmp/proxy_temp;\n    client_body_temp_path /tmp/client_temp;\n    fastcgi_temp_path /tmp/fastcgi_temp;\n    uwsgi_temp_path /tmp/uwsgi_temp;\n    scgi_temp_path /tmp/scgi_temp;\n" /etc/nginx/nginx.conf \
# nginx user must own the cache and etc directory to write cache and tweak the nginx config
    && chown -R $UID:0 /var/cache/nginx \
    && chmod -R g+w /var/cache/nginx \
    && chown -R $UID:0 /etc/nginx \
    && chmod -R g+w /etc/nginx

Oh, could be! Thanks @mathieu-benoit. I'm also not sure the supervisor process is strictly necessary.

@amouat this looks like P1, does that sound right?

(tl;dr: you should be able to get this working now with some experimentation and using -v (not --tmpfs)
I'm working on this at the moment. s6 has been removed from the image, so that no longer causes a problem. Unfortunately --tmpfs doesn't work for some reason, and the non-ro directories have to be explicitly mounted.
I intend for our default image to use a non-privileged user, which may result in some differences to the official image. Our image currently uses different directories for some files and I'm still trying to get to the bottom of that difference.

With:
docker run -d \
    -p 8080:8080 \
    -u 65532 \
    --cap-drop=ALL \
    --read-only \
    --tmpfs /tmp \
    cgr.dev/chainguard/nginx:next

I'm still getting this error in the logs:
nginx: [alert] could not open error log file: open() "/var/lib/nginx/logs/error.log" failed (30: Read-only file system)
2023/04/27 01:51:13 [warn] 1#1: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
2023/04/27 01:51:13 [emerg] 1#1: mkdir() "/var/lib/nginx/tmp/client_body" failed (30: Read-only file system)

Same with -v /tmp.

#478 takes care of this and includes instructions for running read-only. The alert message should be gone now.
Thanks to everyone for the bug report and help to debug.
Please open a new issue if there any further problems (note it will take a moment for the new image to build & upload).


Update tracing sample doc to not use exporter

Expected Behavior
Tracing doc does not use a trace exporter component, since exporter components are deprecated (see dapr/dapr#2337)
Actual Behavior
Still here:
https://github.com/dapr/java-sdk/blob/v0.10.0/examples/src/main/java/io/dapr/examples/tracing/README.md
Steps to Reproduce the Problem
See doc here https://github.com/dapr/java-sdk/blob/v0.10.0/examples/src/main/java/io/dapr/examples/tracing/README.md
Release Note

RELEASE NOTE: UPDATE Java SDK trace sample at https://github.com/dapr/java-sdk/blob/v0.10.0/examples/src/main/java/io/dapr/examples/tracing/README.md to not use exporter components.
Thanks @artursouza for calling this out.

So:

https://github.com/dapr/java-sdk/blob/v0.10.0/examples/src/main/java/io/dapr/examples/tracing/README.md only uses the components and configurations created by our CLI.
CLI is now doing the right thing https://github.com/dapr/cli/pull/542

As a result, this doc does not need to change

Thanks. LGTM
— Artur Souza

From: Nghia Tran<EMAIL_ADDRESS>Sent: Tuesday, December 8, 2020 7:44:19 PM
To: dapr/java-sdk<EMAIL_ADDRESS>Cc: Artur Souza<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dapr/java-sdk] Update tracing sample doc to not use exporter (#404)
Closed #404https://github.com/dapr/java-sdk/issues/404.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dapr/java-sdk/issues/404#event-4087885732, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAA77CTFUUA2QWQKJ5PHWYTST3XBHANCNFSM4USPGUXA.


Fix partial test failure handling

Fix #14

Codecov Report

Merging #16 into master will increase coverage by 0.13%.
The diff coverage is 62.9%.

@@            Coverage Diff            @@
##           master     #16      +/-   ##
=========================================
+ Coverage   70.37%   70.5%   +0.13%
=========================================
  Files           5       5
  Lines         243     278      +35
=========================================
+ Hits          171     196      +25
- Misses         72      82      +10

Impacted Files
Coverage Δ

side_runner_py/main.py
60.33% <62.9%> (+9.16%)
:arrow_up:

side_runner_py/side.py
85.14% <0%> (-3.97%)
:arrow_down:

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 a0ba343...e9f12ec. Read the comment docs.


preview the search files

Can I preview the search files (using quick open) but not open it ?  Reference to "ctrl + p" of sublime text

https://github.com/Microsoft/vscode/issues/8939


haskellPackages.minio-hs: Use crypton-connection instead of unmaintained connection

Fixes build of minio-hs by applying the patch of https://github.com/minio/minio-hs/pull/191
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The package is still marked transitively broken because of connection. Could you run ./maintainers/scripts/haskell/regenerate-transitive-broken-packages.sh to unmark it as broken?

Er actually you need to run ./maintainers/scripts/haskell/regenerate-hackage-packages.sh, sorry

Thanks, just tried it but got this error:
marc@Marcs-M3-Max nixpkgs % ./maintainers/scripts/haskell/regenerate-hackage-packages.sh
Obtaining Hackage data …
Generating compiler configuration …
Running hackage2nix to regenerate pkgs/development/haskell-modules/hackage-packages.nix …
hackage2nix: constraint doctest >=0.18 && <0.19 cannot be resolved in Hackage
This could be due the package being missing in the hackage directory
or the file system not being case sensitive.

CallStack (from HasCallStack):
  error, called at hackage2nix/Main.hs:205:34 in main:Main
hackage2nix: thread blocked indefinitely in an MVar operation

Have you seen this before?

Just manually removed it from the transitive broken list, hope this works as well 👍


typo fix: Amend addtional_kwargs to additional_kwargs

Description
This PR fixes a few typos.
Additional comments: I find that get_additional_kwargs has been defined twice, maybe it's better to define it as a utility?
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[x] No

Type of Change
Please delete options that are not relevant.

[x] Typo fix (non-breaking change which fixes a few typos)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

The unit tests seem to have some issues:
llama-index-integrations/embeddings/llama-index-embeddings-premai/tests/test_embeddings_prem.py:2: in <module>
    from llama_index.embeddings.premai import PremAIEmbeddings
llama-index-integrations/embeddings/llama-index-embeddings-premai/llama_index/embeddings/premai/__init__.py:1: in <module>
    from llama_index.embeddings.premai.base import PremAIEmbeddings
llama-index-integrations/embeddings/llama-index-embeddings-premai/llama_index/embeddings/premai/base.py:13: in <module>
    from premai import Prem
E     File "/home/runner/.cache/pants/named_caches/pex_root/venvs/s/c6184a23/venv/lib/python3.10/site-packages/premai/__init__.py", line 14
E       finetuning-admin: FinetuningAdminModule
E       ^^^^^^^^^^^^^^^^
E   SyntaxError: illegal target for annotation
- generated xml file: llama-index-integrations.embeddings.llama-index-embeddings-premai.tests.test_embeddings_prem.py.xml -
=========================== short test summary info ============================
ERROR llama-index-integrations/embeddings/llama-index-embeddings-premai/tests/test_embeddings_prem.py
!!!!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!!!!
============================== 1 error in 10.29s ===============================

Apparently finetuning-admin is not a valid variable name in Python. (original code)

@RussellLuo if you merge main, you'll see that I just deleted the premai tests for now to avoid cicd from blocking


Amend $GBT token name

Apologies, I misnamed this token in my original commit - https://github.com/solana-labs/token-list/commit/4b80d64295e2e9e001d73f58cf7d1708e911fcd9

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

@keone @bartosz-lipinski . If possible could you please merge this 🙏

added in https://github.com/solana-labs/token-list/commit/4b80d64295e2e9e001d73f58cf7d1708e911fcd9


⚠ Bofrost.at has degraded performance

In 48439cb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1504 ms

Resolved: Bofrost.at performance has improved in 5ff7a81.