Move the filters to a drop down list

Will be a better ux experience and will save space on mobile

Deven has created a demo on Niranjan's deployment. If it looks good, we can push it

Fixed by #19


do_testsetup() has too much logic inside a string passed as argument to ssh

The function do_testsetup() https://github.com/SUSE-Cloud/automation/blob/master/scripts/qa_crowbarsetup.sh#L1138 has a string of 186, which is a shell script with a lot logic passed as argument to ssh to be ran in $novacontroller.
This function at least should scp a script to novacontroller and run it in a similar way qa_crowbarsetup.sh is executed.

was solved with https://github.com/SUSE-Cloud/automation/commit/a0d1fe9bc40e82d1a54c218aaaa190159d2d2b41


Update getting_started_linux.md cmake build instructions.

Updates the CMake build instructions to reflect current target dependencies causing -DIREE_BUILD_COMPILER=OFF to fail per issue #1142.

Yeah you could also add a comment about why this is required, but I think it might be too much for a getting started guide.


Hack container hash method to make it compatible when upgrading cluster from 1.7 to 1.8.

What this PR does / why we need it:
Hack container hash method to make it compatible when upgrading cluster from 1.7 to 1.8.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Ref: https://jira.qiniu.io/browse/KE-2999
PR for k8s 1.9:
https://github.com/qbox/kubernetes/pull/53
Special notes for your reviewer:
Release note:

在 vm-spock 环境测试完成


YARN-9834. Allow using a pool of local users to run Yarn Secure Conta…

1446

 Quality gate: Failed
36 Issues

 12 Vulnerabilities
 24 Code issues

Details

 Quality gate: Failed
32 Issues

 12 Vulnerabilities
 20 Code issues

Details


Allow nested toplevels

It would be useful for several problems to be able to spawn a Toplevel object that is loosely coupled to another Subsystem.
I.e. it should receive global shutdown requests, but should have its own local shutdown context that catches and handles errors and panics locally.

Rejected for now. This library isn't written with performance in mind, as it was originally intended as a more highlevel management library for static subsystems. Spawning a large number of short lived Toplevel objects might hurt performance and is probably better done by other means.
Might revisit later.


CCF returns different carbon emission values for the readings taken on different days

[ x] I have read the Contributing Guidelines for this project.
[x ] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Operating System:
Windows 10 (1803)
Browser:
Microsoft Edge

Expected Behavior
CCF should return same carbon estimation for a period . Even after multiple restart of the server, the json cache should yield same carbon emission for the past dates.
Actual Behavior
Carbon usage chart shows different values for the same observation period for 2 readings taken on 2 different days.
i.e. Emission period : Nov 2023
Emission Noted Date : 29 Nov 2023
Cumulative Carbon Emission: 3.1 metric tons (for 29 days)
Emission period: Nov + 13 days of Dec
Emission Noted Date: 13 Dec 2023
Cumulative Carbon Emission:  2.9 metric tons (for 45 days.)
To Reproduce
Run CCF on 2 different days
Screenshots
Nov 29 , 2023:

Dec 13, 2023:

Dec 29, 2023:

@4upz : Could you please address this issue as well. We have initially escalated these 2 issues over mail. Created the 2nd one just now. Are we missing any configuration ?

@4upz : Could you please show some light here ? :)

Hi @PadmarajBhat I am looking into replicating this and will share insights soon

Thanks for your patience @PadmarajBhat. This seems to be weird behavior that occasionally occurs as a result of #1281. I was able to replicate it and the cache data remains the same, but the client is aggregating the totals for the results incorrectly due to duplicate values. Although the decrease in the cumulative numbers shown for your first two comparison images is a bit erratic, allow me to work on a fix for that issue and circle back to this one to see if the fix either inherently solves this one or sheds further light on a different issue that may be contributing to this.

We've just pushed up a fix for the client-side bug that we mentioned. Feel free to pull down the recent changes and let us know if you see different behavior.
Your estimate totals displayed in the dashboard should be more consistent, but I'd be interested in knowing if you still see behavior where the cumulative totals are decreasing as you add more days

@PadmarajBhat Closing this for now since I haven't heard back and unable to replicate it after the referenced fix. But feel free to leave a message if you still see this occurring, and I'd be happy to reopen and look at it further.

We have scheduled run of CCF on every month last working day as the tool is capable of pulling only current month data.
Today, we took the latest code and ran CCF. The chart is unusual. Not sure, if the Azure has improved drastically or it is CCF issue. Please comment.

@PadmarajBhat That's certainly unusual. The issue we discussed above was UI-related but shouldn't have affected your cache or previously stored estimates. Troubleshooting would require additional details/visibility. I would recommend taking a look at the logs of your API. Do you notice any warnings regarding services being skipped during the last request? Or any other errors?
You could also look to see if a service inside of your cache is showing the same drop in numbers between two different dates. This could help verify if these differences are being returned from the Azure API, is occurring during estimation, or on the front-end.

@4upz : I remember seeing such drastic changes in chart last month also. However, when we restarted the CCF ; the new lower value were generalized for older date. With the new code, no matter how many times we restart it does not change. Chart remains the same.
I think fundamental issue is that
Nov 29:  average Emission was 0.108 metric ton,
Dec 29 : 0.072
Jan 31: 0.005 (appr)
Every month average emission is decreasing though there are no changes in the production system.  There are  weekend should down operations at Dev & QA system but they are very minor part of the total emission. Here, in the chart, average emission itself is low.

@PadmarajBhat Yes, I've noticed the decrease in averages based on your initial post and the most recent image you've posted. It's good that the latest pull has caused numbers for the old data to now be unaffected, but it is unusual that the new numbers are. I think the important part is to isolate which aspects of the application may be contributing to this issue (i.e. azure's api response, estimation logic, cache storage, or dashboard).
Since we're unable to replicate this issue on our end and are also using a different Azure Enterprise account type, I'm a bit limited in ability to troubleshoot on my end. Have you tried any of the recommended troubleshooting steps from my previous message?

@PadmarajBhat Just wanted to give this a friendly bump to see if you've had any luck or a chance to check out my most recent message.
Since this issue is stale, I'll go ahead and close it. I'm happy to open it again if it warrants further investigation


Replace link into main branch of Identity and Consent Management within "Authorization and authentication" text template

What type of PR is this?
Add one of the following kinds:

correction

What this PR does / why we need it:
See #185, updating the first paragraph of the mandatory text for all APIs
Which issue(s) this PR fixes:

Will only partly fix #185, readme update will be within #181
Special notes for reviewers:
I consider this correction as essential for the rc.2
Changelog input
Replaced link into main branch of Identity and Consent Management within "Authorization and authentication" text template

@hdamker To fix #185, we would need another PR to update the README file as requested. We may do this as part of #181.

@hdamker To fix #185, we would need another PR to update the README file as requested. We may do this as part of #181.

Yes, I'm working already on suggestion on #181. Have updated the description above.

@AxelNennker  @sebdewet @tanjadegroot If it's okay with you, I can merge this PR.


It's hard to find errors in long REPL queries

EdgeDB Version: 1.0-alpha.2+dev.505.g5b68ec24

Description
Error output currently looks this way:

This is fine for small queries, but what if query has 100 or more lines?
I faced this problem trying to debug my migration, python driver does not return line number of error yet.
REPL does this by using small ^ symbol without syntax highlighting.
Proposals

REPL can print number of line if length of query is more than X lines
Highlight problematic part with colors somehow
Put something something like #!! at the beginning of line containing error instead of ###

Thank you for reporting!
The new rust version of the REPL now shows only the erroneous line, like this:

Hopefully, it's good enough.


Allows optionally removing rel from privacy and terms

Fix for issue #5047.
This will allow to optionally remove the rel attribute from privacy and terms links. Default is still "rel=nofollow" but it could now either be changed or removed entirely from the ascx file.
Unfortunately the asp.net control doesn't have a rel attribute, so we have to add it ourselves.
Added Rel attribute to Privacy and Terms class and added rel="nofollow" to privacy.ascx and terms.ascx skin file.

Summary

Also, we use the PR titles mainly to write the release notes, so I changed the title to explain what the PR does.

Unless I am misunderstanding something, this will not make it configurable, it will always be rel="nofollow" this way...

Yes, correct. This is the current behavior. The difference is that it could now be removed from the ascx file if desired, without recompiling.

Also, we use the PR titles mainly to write the release notes, so I changed the title to explain what the PR does.

OK. Thank you, will do it properly the next time.

Yes, correct. This is the current behavior. The difference is that it could now be removed from the ascx file if desired, without recompiling.

But it's not a best practice to edit core files anyway, I was thinking it could be made an option in a parameter like you did but it looks to me like the parameter is not being used this way.

Yes, correct. This is the current behavior. The difference is that it could now be removed from the ascx file if desired, without recompiling.

But it's not a best practice to edit core files anyway, I was thinking it could be made an option in a parameter like you did but it looks to me like the parameter is not being used this way.

The reason why rel ended up in the cs file in the first place is because Microsoft's asp hyperlink doesn't have a rel attribute, so it cannot be set from the markup usually. Attempting to set it from the ascx produces an error. I found this workaround on stackexchange for example.
The (in my opinion) better alternative was to add the missing attribute to the class(es). It works. I tested it yesterday. With the change in place, it will still render the rel as nofollow. When removing it from the ascx t will disappear entirely. It looks a bit strange because the classes member Rel is not used anywhere, but it will still get rendered (magically).

The way I see it, the login one has it hardcoded in the view and it cannot be customized (without editing the core files, which we do not recommend).

OK. Interesting to see the devs perspective. Am more in the user perspective here. :)
I made a couple of such changes and merge them during each update. From my perspective this is totally acceptable. And of course I prefer changing some (core) markup files over having to recompile DNN.

Rel is now initialized twice, once from the rel attribute in the HTML markup and once from the code behind file. But the markup will win

If you accept the suggestions @bdukes made above by clicking the "Commit suggestion" on each, then it will have a default and theme developers will have a setting on the skin object to override that default. The class will change it at runtime accordingly thus no longer needing to modify the core ascx file, it will be simply a theme implementation that does not get overridden upon upgrades.

Oh....wasn't aware of that.

@Andy9999 the intention of the Platform is that you should not have any changes which get overwritten by an upgrade. Any changes that you want which would be overwritten by an upgrade should use an extension point which DNN does not overwrite (or a new extension point if one doesn't exist, e.g. adding a Rel property to the Privacy theme object control)
ASP.NET web controls can have their Attributes collection set via the ascx markup if an attribute in the markup doesn't match an existing property on the control's class. So the asp:HyperLink control doesn't need any special support to set rel="nofollow", it just renders it directly as an attribute on the rendered <a> tag. We want the Privacy control to allow a theme developer to set <dnn:Privacy runat="server" rel=""/> (which sets the Rel property defined on the class), which then sets the "rel" attribute on the asp:HyperLink, resulting in rel="" being rendered).

Thanks....maybe the exception I saw, when adding rel to the markup without that change, was because the code behind attempted to add an attribute that already exists in the markup/skin. I didn't investigate the crash any further.

Seems I also missed out that Login.Ascx or User.Ascx use hyperlink directly whereas Privacy and Terms have their own classes.

To sum it up and if I got your feedback right, you would prefer to have a setting somewhere, e.g. in PortalSettings to turn it on and off?
Then....no core files would have to be touched. Right?

I don't think we would need anything added to PortalSettings. Wherever the privacy and terms controls are used (i.e. in the theme) is the place where rel could be set, which wouldn't require any core changes, just theme changes.

Shall I add the semicolons?

I love to contribute by adding semicolons. ;) That's easy and I do it the whole day anyways.

@bdukes I am a bit confused about the build error, how do we find the problem nowadays, is the only way with the binlog with the viewer ?

My last update (semicolons) doesn't have the Green verified thingy https://github.com/dnnsoftware/Dnn.Platform/pull/5054/commits

@valadas 😕it should be posting build errors as errors in DevOps, but apparently that isn't working, so viewing the binlog is the only way to get more details

Sorry, my typo. Fix building now.

Very agile!

Would probably be easier if we were in the same room or in a chat somehow.

If you really don't want rel="" you can set the value to null:
<dnn:Terms runat="server" ID="TheTerms" />

<script runat="server">
protected override void OnLoad(EventArgs e)
{
  TheTerms.Rel = null;
}
</script>

I think the whole change could now be undone, because that was possible before. :)

We can add a if (!string.IsNullOrWhiteSpace(this.Rel) { this.hypTerms["rel"] = this.Rel; } wrapper around the defining of the attribute if you want to make a follow-up contribution.
It is now possible to change or remove the rel="nofollow" attribute from the link without making any changes to the core files, but only adjusting your theme. This is a valuable contribution, otherwise we wouldn't have accepted it. I'm sorry if there was miscommunication on what our goals were.

We can add a if (!string.IsNullOrWhiteSpace(this.Rel) { this.hypTerms["rel"] = this.Rel; } wrapper around the defining of the attribute if you want to make a follow-up contribution.
It is now possible to change or remove the rel="nofollow" attribute from the link without making any changes to the core files, but only adjusting your theme. This is a valuable contribution, otherwise we wouldn't have accepted it. I'm sorry if there was miscommunication on what our goals were.

I guess this won't help due to the order of execution.

Rel is initialized to nofollow
OnLoad is execute and add the attribute to the hyperlink (nofollow)
Then Rel is set to whatever is in the markup code without any effect

Are you trying to set the Rel property on the <dnn:Terms> control in your theme file?

No, maybe that's the culprit! I did it in the Terms.Ascx file, the file you told me to not change. :)

I slowly start to understand what we are doing here.

Wow! Works perfectly if including your last suggestion. Now it matches the issue title again. Can I still submit it or is it too late now?

Just submitted the change and will change the skin files. The way it should be done! Thanks Daniel and Brian.

New issue??

No, you can associate it with the same issue. Thanks!

You will have to open a new PR, but it'll be associated to the same issue #5047

Like this? https://github.com/dnnsoftware/Dnn.Platform/pull/5057

That works 👍🏻
The one thing to do differently is instead of include #5047 in the PR title, in the description include "Fixes #5047" (or "For #5047" if it's not a complete fix). This will let GitHub automatically create a link between the PR and the issue.

Thanks.

Got it deployed on the production server now along with the other issue (search result category localization). Looks great now! I find nothing to complain about.
Somehow (with my limited understanding) it did not seem to be a big difference if rel would be changed in the Terms/Privacy markup files or the skin. I have to watch out when updating the skin as well and merge changes with the ones we did. We use the awesome EasyDNN themes. But I clearly see the advantage now. :)

One final question.....would it make a big difference to initialize the new Rel attribute from the markup instead of having it in the code behind file? And...would this raise more awareness for the skin developers that there is now such an attribute that could be customized? Or would they consult the code behind anyways or get that info from the release notes?
Just a question for future issue of similar nature.

<dnn:Terms runat="server" ID="TheTerms" Rel="" /> is the way you would initialize the property via markup. There isn't a place to do that initialization in the Terms control itself, it has to be in the codebehind.
We probably do need to document this new property by creating a page on https://docs.dnncommunity.org/content/tutorials/themes/theme-objects/index.html#breadcrumb-theme-object-example (e.g. like the breadcrumb docs)

Doc comments are always appreciated :-)

@Andy9999  documentation about theme objects is also welcome if you have the time https://docs.dnncommunity.org/content/tutorials/themes/theme-objects/index.html


java.lang.IllegalArgumentException: Image dimensions must be > 0

When panning and zooming a map I get this exception:
java.lang.IllegalArgumentException: Image dimensions must be > 0
at com.sun.prism.Image.(Unknown Source)
at com.sun.prism.Image.(Unknown Source)
at com.sun.prism.Image.fromByteBgraPreData(Unknown Source)
at com.sun.javafx.webkit.prism.RTImage.getImage(Unknown Source)
at com.sun.javafx.webkit.prism.PrismImage.getPlatformImage(Unknown Source)
at com.sun.javafx.webkit.UIClientImpl.startDrag(Unknown Source)
at com.sun.webkit.WebPage.fwkStartDrag(Unknown Source)
at com.sun.webkit.WebPage.twkProcessMouseEvent(Native Method)
at com.sun.webkit.WebPage.dispatchMouseEvent(Unknown Source)
at javafx.scene.web.WebView.processMouseEvent(Unknown Source)
at javafx.scene.web.WebView.access$2500(Unknown Source)
at javafx.scene.web.WebView$14.handle(Unknown Source)
at javafx.scene.web.WebView$14.handle(Unknown Source)
at com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(Unknown Source)
at com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(Unknown Source)
at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Unknown Source)
at com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(Unknown Source)
at com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(Unknown Source)
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Unknown Source)
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Unknown Source)
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Unknown Source)
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Unknown Source)
at com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(Unknown Source)
at com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(Unknown Source)
at com.sun.javafx.event.EventUtil.fireEventImpl(Unknown Source)
at com.sun.javafx.event.EventUtil.fireEvent(Unknown Source)
at javafx.event.Event.fireEvent(Unknown Source)
at javafx.scene.Scene$MouseHandler.process(Unknown Source)
at javafx.scene.Scene$MouseHandler.access$1800(Unknown Source)
at javafx.scene.Scene.impl_processMouseEvent(Unknown Source)
at javafx.scene.Scene$ScenePeerListener.mouseEvent(Unknown Source)
at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(Unknown Source)
at com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.javafx.tk.quantum.GlassViewEventHandler.handleMouseEvent(Unknown Source)
at com.sun.glass.ui.View.handleMouseEvent(Unknown Source)
at com.sun.glass.ui.View.notifyMouse(Unknown Source)
at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
at com.sun.glass.ui.win.WinApplication.access$300(Unknown Source)
at com.sun.glass.ui.win.WinApplication$4$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception in thread "JavaFX Application Thread" E

Is this problem still occuring?

Not abe to replicate the issue.


Improve UI of user management view

following the #63

@sahbi-ktifa : I think it has been already done here https://github.com/jhipster/jhipster-vuejs/pull/63

Oh, right! Thanks 😊


Passing arg to bypass X11 cause permission denied error

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I am not quite sure, if this is a bug. Let me explain what i have done. Id decided to migrate a dizzy java swing application into a podman. I also got some ideas from X11 and podman So i reused a fedora system and added some software to run remote X11 sessions:
FROM fedora
ENV HOME=/home/yourhome
RUN mkdir -p ${HOME}

#
# mount the data file to an external ressource
#
VOLUME [ "/home/yourhome/export"  ]

#
# Packages
# perform updates
RUN dnf -y update

# perform install (disabled php-fpm)
RUN dnf -y install xorg-x11-server-utils xorg-x11-xauth java-11-openjdk curl unzip wget

#
# get your java app as a zip
RUN cd ${HOME} && wget -N http://  ....

# unzip arvice and delete archive
RUN unzip ,,,
ADD startjl.sh  /home/yourhome/startjl.sh
RUN chmod +x /home/yourhome/startjl.sh

# for testing
CMD tail -f /dev/null
# this should be exexuted CMD /home/yourhome/startjl.sh

The problem does not seem to be the dockerfile but its execution:

This one runs without any X11 bypass arguments
podman run -ti   myImage
This one fails with this error message:

podman run -ti -e DISPLAY --net=host --rm  \
  --interactive --tty \
  -v  ${DATA_STORE}/data:/home/yourhome/export:z \
  -v ~/.Xauthority:/root/.Xauthority:z \
  jlohn01

-- i get this:
{"msg":"exec container process `/bin/sh`: Permission denied","level":"error","time":"2020-02-17T09:54:39.000393894Z"}

I already allowed the access on both directories:
chcon -t container_file_t -R  ${DATA_STORE}/data
chcon -t container_file_t -R  ~/.Xauthority

Steps to reproduce the issue:

simply try both runner

Describe the results you received:
sometime this:
{"msg":"exec container process /bin/sh`: Permission denied","level":"error","time":"2020-02-17T09:54:39.000393894Z"}
in another constellation i saw this weired message, that a executable was not found in the path.
`
Describe the results you expected:
An application that is beeing display on my remote screen.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.8.0
RemoteAPI Version:  1
Go Version:         go1.13.6
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.6
  podman version: 1.8.0
host:
  BuildahVersion: 1.13.1
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.10-2.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.10, commit: 6b526d9888abb86b9e7de7dfdeec0da98ad32ee0'
  Distribution:
    distribution: fedora
    version: "31"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>2
  OCIRuntime:
    name: crun
    package: crun-0.12.1-1.fc31.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.12.1
      commit: df5f2b2369b3d9f36d175e1183b26e5cee55dd0a
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree:<PHONE_NUMBER>8
  SwapTotal:<PHONE_NUMBER>4
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: buster
  kernel: 5.4.18-200.fc31.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.3+dev
      commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
  uptime: 1h 48m 19.17s (Approximately 0.04 days)
registries:
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /home/cgroove/.config/containers/storage.conf
  ContainerStore:
    number: 4
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.5-2.fc31.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7.5
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /home/cgroove/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 89
  RunRoot: /run/user/1000
  VolumePath: /home/cgroove/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-docker-1.8.0-2.fc31.noarch
cockpit-podman-13-1.fc31.noarch
podman-compose-0.1.5-2.git20191107.fc31.noarch
podman-1.8.0-2.fc31.x86_64
podman-plugins-1.8.0-2.fc31.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):

update: I changed the cmd to the shell, that calls the java app and added also the volume arg /tmp/.X11-unix/ but still receiving the eror:
[cgroove@buster lohnbuchhaltung]$ podman run -ti -e DISPLAY --net=host --rm    --interactive --tty  -v /tmp/.X11-unix/:/tmp/.X11-unix/  -v  ${DATA_STORE}/lohnbuch:/home/lohnf/jlohn:z   -v ~/.Xauthority:/root/.Xauthority:z  jlohn05
+ export HOME=/home/lohnf
+ HOME=/home/lohnf
+ export LD_LIBRARY_PATH=/home/lohnf/jlohn28
+ LD_LIBRARY_PATH=/home/lohnf/jlohn28
+ export DISPLAY
+ cd /home/lohnf/jlohn28
+ exec java -Xmx512m -jar jlohn.jar
Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.
	at java.desktop/sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
	at java.desktop/sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:102)
	at java.base/java.security.AccessController.doPrivileged(Native Method)

So the DISPLAY env-var does not work. I think that i am getting closer, but still missing something.

SELinux is going to block container_t from communicating with the XServer process.  Just chcon on /tmp is not going to help.  Disable selinux and see if you get further.
--security-opt label=disable

Salut Dan,

i disabled selinux on the hosting system
and called the container with:

podman run -ti -e DISPLAY=$DISPLAY --net=host --rm   --security-opt label=disable  -v  ${DATA_STORE}/data:/home/lohnbucher/jlohn:z   -v ~/.Xauthority:/home/lohnbucher/.Xauthority:z   -v /tmp/.X11-unix/:/tmp/.X11-unix/   jlohn06

But i still get the same error. Did you meant, that i should disable selinux on the host ? (i did)

I think the Toolbox folks forward X into the container - @debarshiray Did you need to do anything special to do that?

Salut Matthew,
i think they work with CoreOS oder Silverblue, i gave 'fedora:latest' a try. Anyway any help is appreciated to get the java application to work inside a podman.
Thank you in advance!

No you do not need to disable SELinux on the host.
I take this it works with --privileged?
If yes, then we have an issue with Capabiltiies, SECCOMP or SELinux.  You seem to have eliminated SELinux, but just to make sure.
Can you try in permissive mode
setenforce 0
If this does not fix it and --privilege does, could you try without --privileged and just
--cap-add all
If this does not fix it, try with
--security-opt seccomp=unconfined
Then we might have a better idea of what security feature is blocking your access.

@groovyman
Not exactly what you are looking for but I am using the following commands in an HPC like setup to run a container (rootless) with X forwarding:
export `scontrol show job $SLURM_JOBID | grep BatchHost`
srun -N 2 -n 2 podman pull quay.io/adrianreber/mpi-life:latest
srun -N 2 -n 2 touch /tmp/.Xauthority
srun hostname > hosts
ssh $BatchHost -X -C "cp .Xauthority /tmp/; mpirun --hostfile hosts podman run --rm --env-host --userns=keep-id --pid=host --ipc=host --net=host -v /tmp/podman-mpirun/:/tmp/podman-mpirun/:z  -v /tmp/.Xauthority:/home/mpi/.Xauthority:z quay.io/adrianreber/mpi-life:latest -b -p -m

This is on a host I connect to via ssh -X so it is even one level more complicated X forwarding. But this works rootless, so maybe there is something in this example which helps you.
If remember it correctly it was important that the user ID in the container is the same as outside, because X relies on that.

Thank your very much for your help.
I got another idea to run a sshd inside the podman. That would change its behaviour to a running service. By ssh -Y i could tunnel X11.

@rhatdan
Just give you a reply on your suggestions:

test (setenforce=1 / --privileged)  not working, same X11 problem
test (setenforce=0 / --privileged)  not working, same X11 problem
test  setenforce=0 does not help. The podman process seems to be unable to connect to the UNIX-domain socket under :0  Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.
test security-opt seccomp=unconfined also not working.

I think, one of both volume mounts cause the problem.

~/.Xauthority:/home/lohnbucher/.Xauthority:z
/tmp/.X11-unix/:/tmp/.X11-unix/

Well if this all does not fix it, then the only thing left would be user namespace. I guess login to the container and see if you can see these directories and what the permissions look like on them.

Salut @rhatdan ,
i fixed it using systemd and a running sshd.  I do not need any .X11 or socket bypassing by a mounted volume.
FROM fedora

#
# mount the data file to an external ressource
#

#
# Packages
# perform updates
RUN dnf -y update

# perform install (disabled php-fpm)
RUN dnf -y install firewalld openssh-server passwd xorg-x11-server-utils xorg-x11-xauth java-11-openjdk curl unzip wget firefox
RUN dnf clean all

#
# ## regitser an enable the postinstaller
ADD postInstaller.sh /usr/local/bin/postInstaller.sh

# install postinstall script as a service
RUN chown root:root  /usr/local/bin/postInstaller.sh
RUN chmod 740 /usr/local/bin/postInstaller.sh

ADD postinst.service /etc/systemd/system
RUN chmod 640 /etc/systemd/system/postinst.service
RUN chown root:root /etc/systemd/system/postinst.service
RUN systemctl enable postinst

#
# enable sshd and allow remote access, firewall needs to be configured later
RUN systemctl enable sshd.service

#
# create user lohnbucher
ENV LBHOME=/home/lohnbucher
RUN useradd -m lohnbucher
RUN chown -R lohnbucher:lohnbucher  ${LBHOME}
RUN echo "secret\nsecret\n" | passwd --stdin --force lohnbucher

#
# get a ole sh....  desktop application
RUN cd ${LBHOME} && wget -N http://   somewhere from the net

# unzip arvice and delete archive
RUN cd ${LBHOME} && unzip -o javaZip.zip
RUN cd ${LBHOME} && rm -f  javaZip.zip
# do some chown and chmod and publish a data directory as a volume

# export standard sshd port number
EXPOSE 22

# run systemd
CMD [ "/lib/systemd/systemd" ]

The postinstaller is the only service that takes over the nasty things, that podman-build is unable to carry out (i.e. start services, reconfigure systemd etc etc)
#!/bin/sh
#
# magic postinstaller

# config the firewalld and restat sshd
firewall-cmd --permanent --zone=public --add-service=ssh
systemctl restart sshd.service

# remove and restore lohnbucher Xauth file
mv ~lohnbucher/.Xauthority  ~lohnbucher/.XauthorityOLE
touch ~lohnbucher/.Xauthority
# perform some admin operations here

# add or start some addtional services here if you like

# run this installer only one
systemctl disable postinst

That was also the solution to run with multiple services in one container (see also #4909). I hope no composer will kill me due to my heretic misuse of modern container art. ;-)

Good, you got a result.  I am gong to close this issue, since this is not something that is a bug in podman, other people have found other ways to satisfy this requirement.  Reopen if you disagree.


Bug: getUsersInfoWithCache No "ex" field returned

What happened?
The getUsersInfoWithCache function did not return the 'ex' field, although the documentation describes that it should return 'publicInfo.' Similarly, testing with the Android SDK confirmed that the 'ex' field is returned.
What did you expect to happen?
return the 'ex' field
How can we reproduce it (as minimally and precisely as possible)?
use getUsersInfoWithCache 100% reproduce it
Anything else we need to know?
No response
version
OpenIMSDK  3.5.1-alpha.2
or
OpenIMSDK 3.4.0
Cloud provider
local
OS version
No response
Install tools
No response

I found the reason. The 'EX' field is not defined in OIMPublicUserInfo in OpenIMSDK/Model/OIMFullUserInfo.h. Once I defined it, I was able to successfully retrieve it.

I found the reason. The 'EX' field is not defined in OIMPublicUserInfo in OpenIMSDK/Model/OIMFullUserInfo.h. Once I defined it, I was able to successfully retrieve it.

Thanks for finding it, will update later.


remove crosses, equals, and touches geo region operators from JSDoc

The geo region query operators crosses, equals, and touches have been dropped from ML9. They need to be removed from the list of available operator values in the JSDoc for the operator param of  queryBuilder.geospatialRegion.
http://pubs.marklogic.com:8011/9.0/jsdoc/queryBuilder.html#geospatialRegion
I'm going to assign this to you for now, Mike. If I get around to it first, I'll steal it from you.

Thanks @kcoleman-marklogic, I will take care of it:
https://github.com/wooldridge/node-client-api/tree/ea4/issue-322-regiondoc


Split Resource  and Component Access

Objective

fix #13139
Currently, Bevy's system access does not differentiate between components and resources. This limitation can potentially lead to incorrect conflict detection in certain scenarios

Solution

Added a resource access in SystemMeta

Note that this method will double the memory used for access, but that would get fixed if #14385 gets merged.

Very nice!
Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

it appears to be a better solution than this pr.

Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

This is my preferred approach here I think.

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

I'm not sure what I suggested is possible actually. Because then you would also need to be able to track if an access has any_read_component or any_write_component

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

I'm not sure what I suggested is possible actually. Because then you would also need to be able to track if an access has any_read_component or any_write_component

Actually I have a working version here: https://github.com/bevyengine/bevy/pull/14561

Closing in favor of #14561.


Hook up Validation CLI task to build CI pipeline

User Story
We want failures to validate our YAML files to cause errors in our CI pipeline
Dev Notes

To start, we are only validating organizations.yml
Include a step to run created CLI task as a part of the CI pipeline on github

Acceptance Criteria

if there are errors in organizations.yml, the CI should not pass on github
pattern set up for other types of YAML to be included in the future (probably as a part of the CLI code)

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @jack-h-wang @jalbinson @mkalish @thetaurean

Please add your planning poker estimate with Zenhub @JFisk42


Excessive White Space and Unresponsive Layout

Description
There is excessive white space on the right side of the screen.
The page layout is not responsive and does not adapt well to different screen sizes.
Steps to Reproduce
Open the webpage in any browser.
View the webpage on different screen sizes (desktop, tablet, mobile).
https://aditya-bhaumik.github.io/Pathsphere/
Expected Behavior
The webpage should be responsive with well-structured content alignment.
Actual Behavior
Excessive white space and poor layout responsiveness.
Screenshots

https://aditya-bhaumik.github.io/Pathsphere/
Additional Information
Use Flexbox or CSS Grid for layout responsiveness to fix this issue.
What browser are you seeing the problem on?

[X] Firefox
[X] Chrome
[ ] Safari
[X] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Deployment takes time to open wait for sometime before the websitr loads


Possible workaround for PHP_BINDIR bug in PHP

Fixes #5

I think this should be fine now, because it use PHP_BINARY instead of PHP_BINDIR.


Revisit Options Order

1.The default implementation for option accessor and option setups seems to prevent scoped option setups from working. I believe these more dynamic scenarios are important and not necessarily exclusive to data.
2.I think it would be good to have a nice pattern to register option setups that override or not override other option setups, i.e. the issue of specifying the "Order" of the IOptionsSetup. Hao proposed using a flag, which I am ok with trying. Not sure it will make it to this checking though.
3.The implementation of binding to keys from configuration to matching properties on TOptions only work with core and desktop .NET and I haven't got a good answer on whether this can be addressed.

@HaoK do we still need this? Putting into backlog for now to remove it from triage list.

Yes, I think we should revisit this soon.

@lodejard, @kirthik and @HaoK met today and we agreed it would be good to get rid of explicit ordering for the application of IConfigurations<TOptions>. Instead you will get the order or registration in DI. Before we go ahead removing it we need to look at how it is being used in the frameworks (in particular in MVC) and makes sure the same behavior can be achieved.

Nuked order from Options.


Error related to RefFindNode and React 17

Bug Report
Steps

Clone my fork of the project on which I work: https://github.com/silviubogan/volto-slate/tree/eefee2c46c38bc7bd07e6a9681e27bebc6fc5983 into a new directory and cd into it.

Run this (fish syntax for putting output of pwd in the command):

docker run -it --rm -v (pwd):/opt/frontend/my-volto-project/src/addons/volto-slate \
                                                                           -e GIT_NAME=volto-slate \
                                                                           -e GIT_BRANCH=develop \
                                                                           -e NAMESPACE=@eeacms \
                                                                           -e DEPENDENCIES="@eeacms/volto-slate" \
                                                                           eeacms/volto-test test

Expected Result
The unit tests are passed.
Actual Result
There are some strange errors related to RefFindNode and I think they are related to React 17. I put here just the first jest test file that fails as the others present similar errors:
FAIL src/addons/volto-slate/src/editor/ui/ToolbarButton.test.js (14.107 s)
  ● Console

    console.error
      Error: Uncaught [Error: Unable to find node on an unmounted component.]
          at reportException (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:66:24)
          at invokeEventListeners (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:209:9)
          at HTMLUnknownElementImpl._dispatch (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:119:9)
          at HTMLUnknownElementImpl.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:82:17)
          at HTMLUnknownElementImpl.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:30:27)
          at HTMLUnknownElement.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:157:21)
          at Object.invokeGuardedCallbackDev (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:237:16)
          at invokeGuardedCallback (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:292:31)
          at commitRootImpl (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:22541:9)
          at unstable_runWithPriority (/opt/frontend/my-volto-project/node_modules/scheduler/cjs/scheduler.development.js:653:12) Error: Unable to find node on an unmounted component.
          at findHostInstanceWithWarning (/opt/frontend/my-volto-project/src/addons/volto-slate/node_modules/react-dom/cjs/react-dom.development.js:25377:19)
          at Object.findDOMNode (/opt/frontend/my-volto-project/src/addons/volto-slate/node_modules/react-dom/cjs/react-dom.development.js:26067:12)
          at RefFindNode.componentDidMount (/opt/frontend/my-volto-project/src/addons/volto-slate/node_modules/@fluentui/react-component-ref/dist/commonjs/RefFindNode.tsx:40:32)
          at commitLifeCycles (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:19814:22)
          at commitLayoutEffects (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:22803:7)
          at HTMLUnknownElement.callCallback (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:188:14)
          at invokeEventListeners (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:193:27)
          at HTMLUnknownElementImpl._dispatch (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:119:9)
          at HTMLUnknownElementImpl.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:82:17)
          at HTMLUnknownElementImpl.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:30:27)
          at HTMLUnknownElement.dispatchEvent (/opt/frontend/my-volto-project/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:157:21)
          at Object.invokeGuardedCallbackDev (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:237:16)
          at invokeGuardedCallback (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:292:31)
          at commitRootImpl (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:22541:9)
          at unstable_runWithPriority (/opt/frontend/my-volto-project/node_modules/scheduler/cjs/scheduler.development.js:653:12)
          at runWithPriority$1 (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:11039:10)
          at commitRoot (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:22381:3)
          at finishSyncRender (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:21807:3)
          at performSyncWorkOnRoot (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:21793:7)
          at scheduleUpdateOnFiber (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:21188:7)
          at updateContainer (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:24373:3)
          at /opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:24758:7
          at unbatchedUpdates (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:21903:12)
          at legacyRenderSubtreeIntoContainer (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:24757:5)
          at Object.render (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:24840:10)
          at /opt/frontend/my-volto-project/node_modules/@testing-library/react/dist/pure.js:99:25
          at batchedUpdates$1 (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom.development.js:21856:12)
          at act (/opt/frontend/my-volto-project/node_modules/react-dom/cjs/react-dom-test-utils.development.js:929:14)
          at render (/opt/frontend/my-volto-project/node_modules/@testing-library/react/dist/pure.js:95:26)
          at Object.<anonymous> (/opt/frontend/my-volto-project/src/addons/volto-slate/src/editor/ui/ToolbarButton.test.js:18:28)
          at Object.asyncJestTest (/opt/frontend/my-volto-project/node_modules/@jest/core/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:106:37)
          at /opt/frontend/my-volto-project/node_modules/@jest/core/node_modules/jest-jasmine2/build/queueRunner.js:45:12
          at new Promise (<anonymous>)
          at mapper (/opt/frontend/my-volto-project/node_modules/@jest/core/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
          at /opt/frontend/my-volto-project/node_modules/@jest/core/node_modules/jest-jasmine2/build/queueRunner.js:75:41
          at processTicksAndRejections (internal/process/task_queues.js:97:5)

      at VirtualConsole.<anonymous> (node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/virtual-console.js:29:45)

    console.error
      The above error occurred in the <RefFindNode> component:
          in RefFindNode (created by Ref)
          in Ref (created by Button)
          in Button (at ToolbarButton.jsx:10)
          in div (at ToolbarButton.jsx:9)
          in ForwardRef (at ToolbarButton.test.js:20)
          in IntlProvider (created by ConnectFunction)
          in ConnectFunction (created by Provider)
          in Provider (created by Provider)
          in Provider (at ToolbarButton.test.js:19)

      Consider adding an error boundary to your tree to customize error handling behavior.
      Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

      at logCapturedError (node_modules/react-dom/cjs/react-dom.development.js:19527:21)
      at logError (node_modules/react-dom/cjs/react-dom.development.js:19564:5)
      at update.callback (node_modules/react-dom/cjs/react-dom.development.js:20708:5)
      at callCallback (node_modules/react-dom/cjs/react-dom.development.js:12490:12)
      at commitUpdateQueue (node_modules/react-dom/cjs/react-dom.development.js:12511:9)
      at commitLifeCycles (node_modules/react-dom/cjs/react-dom.development.js:19883:11)
      at commitLayoutEffects (node_modules/react-dom/cjs/react-dom.development.js:22803:7)
      at HTMLUnknownElement.callCallback (node_modules/react-dom/cjs/react-dom.development.js:188:14)

  ● ToolbarButton › renders a toolbar button

    Unable to find node on an unmounted component.

      16 |       },
      17 |     });
    > 18 |     const { asFragment } = render(
         |                            ^
      19 |       <Provider store={store}>
      20 |         <ToolbarButton />
      21 |       </Provider>,

      at findHostInstanceWithWarning (src/addons/volto-slate/node_modules/react-dom/cjs/react-dom.development.js:25377:19)
      at Object.findDOMNode (src/addons/volto-slate/node_modules/react-dom/cjs/react-dom.development.js:26067:12)
      at RefFindNode.componentDidMount (src/addons/volto-slate/node_modules/@fluentui/react-component-ref/dist/commonjs/RefFindNode.tsx:40:32)
      at commitLifeCycles (node_modules/react-dom/cjs/react-dom.development.js:19814:22)
      at commitLayoutEffects (node_modules/react-dom/cjs/react-dom.development.js:22803:7)
      at HTMLUnknownElement.callCallback (node_modules/react-dom/cjs/react-dom.development.js:188:14)
      at Object.invokeGuardedCallbackDev (node_modules/react-dom/cjs/react-dom.development.js:237:16)
      at invokeGuardedCallback (node_modules/react-dom/cjs/react-dom.development.js:292:31)
      at commitRootImpl (node_modules/react-dom/cjs/react-dom.development.js:22541:9)
      at unstable_runWithPriority (node_modules/scheduler/cjs/scheduler.development.js:653:12)
      at runWithPriority$1 (node_modules/react-dom/cjs/react-dom.development.js:11039:10)
      at commitRoot (node_modules/react-dom/cjs/react-dom.development.js:22381:3)
      at finishSyncRender (node_modules/react-dom/cjs/react-dom.development.js:21807:3)
      at performSyncWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:21793:7)
      at scheduleUpdateOnFiber (node_modules/react-dom/cjs/react-dom.development.js:21188:7)
      at updateContainer (node_modules/react-dom/cjs/react-dom.development.js:24373:3)
      at node_modules/react-dom/cjs/react-dom.development.js:24758:7
      at unbatchedUpdates (node_modules/react-dom/cjs/react-dom.development.js:21903:12)
      at legacyRenderSubtreeIntoContainer (node_modules/react-dom/cjs/react-dom.development.js:24757:5)
      at Object.render (node_modules/react-dom/cjs/react-dom.development.js:24840:10)
      at node_modules/@testing-library/react/dist/pure.js:99:25
      at batchedUpdates$1 (node_modules/react-dom/cjs/react-dom.development.js:21856:12)
      at act (node_modules/react-dom/cjs/react-dom-test-utils.development.js:929:14)
      at render (node_modules/@testing-library/react/dist/pure.js:95:26)
      at Object.<anonymous> (src/addons/volto-slate/src/editor/ui/ToolbarButton.test.js:18:28)

Version
2.0.1
Testcase
I think the steps to reproduce are easier to follow than a possible testcase.

@silviubogan can you please provide an isolated example?

Closing this for housekeeping until we will have an isolated repro 😿
P.S. For sure we are open to accept fixes if you will be able to debug the issue.
P.P.S. Isolated repro is important as for example I even don't have Docker on my machine.

If react-test-renderer is used directly, you can try to use mocks:
https://github.com/facebook/react/issues/7371#issuecomment-323516392
However, it's really strange that issue came from React's upgrade.

A simple Button gives the same error in React 17 and up. Downgrading to react 16.x.x removes the error. There's a lot of npm packages which suffer the same issue!

@danydhondt feel free to make a repro case then


Weather

Introduction
This is my current design of the weather API that I want to go in to Krypton. It's a bit more complex than what I have seen in other APIs, so here's a list of some of its features:

Starting and stopping weather immediately
Queuing weather up for later application
Scheduling of weather starting and stopping
Proper per-world and per-player weather, and you can even apply the API to other things that may want controlling

The current design has Weather, which is simply a type that holds data about the weather, though this type is immutable, and does not hold any data that could tie it to a specific controller, so it can be easily reused.
Then, the heart of the design is the WeatherController, which can be used to start and stop weather, queue weather, clear weather, and also schedule weather starting and stopping (TODO).
There is also a container that holds a controller, mostly existing to avoid having to create two weather events, but it also allows users to create their own things that may have weather.
Questions that still remain unanswered:

Should we use a scheduler for weather at all?
Is this too much for something like weather?
Could this be abstracted and applied to other things in the API?

This API now seems pretty overkill for something as simple as weather. Though with the controller system, I am now thinking that we could expand that API in to something that covers more world events, which could be a very useful API. I will look at creating a reduced weather API without the controller system, that just allows you to get and set the weather in a world (and maybe individually for a player) at another time.


Added JSONSchema for plugin.json files

Pull Request Type

[ ] ✨ feat
[ ] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[ ] 🔨 chore
[x] 📝 docs

What is in this change?
Added a JSONSchema file that agent skill plugin developes can use to enable errors, warnings, intellisense and AI completions in their IDEs.
Additional Information
I didn’t find a really good place to put it to, and the folder of the JavaScript file that loads the plugin.jsons seemed to be the most sane.
The docs should mention it in plugin-json.mdx. JSONSchema files can be either referenced in plugin.json, like
{
  "$schema": "https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/refs/heads/master/server/utils/agents/imported-manifest.schema.json"
}

or be linked to appropriate files using IDE configuration.
Developer Validations

[x] I ran yarn lint from the root of the repo & committed changes
[ ] Relevant documentation has been updated
[x] I have tested my code functionality
[x] Docker build succeeds locally

Linked relevant docs issue that can be done later, thank you for this!


Change the language

Hello,
I find this project amazing. I would love to contribute and give a ton of inspirational messages.
I think there's two options to resolve this :

add language option in the API
add the option to use a CSV/JSON/... File to get the messages

Thank you !

For the language part, I searched a bit and found maybe an API for French citations: https://citations.ouest-france.fr/
But it seems like nobody ever used their API or not for a long time because it's kinda broken. I've sent them an e-mail, I'll keep you in touch and make a Pull Request with this whenever I have time and if they respond/I find another API.
For the CSV part there are two options again :

Add a CSV in the web part of the Balena Cloud thingy (never worked with Balena services so I don't think I'll go this away even if it seems better for the end-user)
Update the display message-based a local CSV file (simply override the message as done in https://github.com/balenalabs/inkyshot/blob/aff265f8be1d50554f70cb26134d2f3ca9644b33/inkyshot/update-display.py#L348)

As I said, I never integrated anything with Balena, so my Pull Request may be a little bit buggy. Plus I don't have any Raspberry Pi to test it. So if you give me a hand @gelbal and correct it, it may be a quick win for everyone.
Pull request is coming. Also, as the CSV file may be of variable length, I plan something based on a randomized variable put in Balena parameter thing. You may have to double-check this (my guess is that I have to announce/declare the variable somewhere in the deploy part but I have no idea or time to look further for this issue).

Here is the pull request :).
Based on https://forums.balena.io/t/maximum-length-of-application-environmental-variables/243168/18 variables may be up to 1MB so I created a CSV_MESSAGE variable.
As already said I'm new to this whole Balena universe and I've read a bit of documentation in order to simplify the work of testing this because I cannot do it myself for technical reasons.
Hope this gets added to the main project in order to help people.
@gelbal thank you in advance for the review.

For the CSV part there are two options again :

Add a CSV in the web part of the Balena Cloud thingy (never worked with Balena services so I don't think I'll go this away even if it seems better for the end-user)
Update the display message-based a local CSV file (simply override the message as done in https://github.com/balenalabs/inkyshot/blob/aff265f8be1d50554f70cb26134d2f3ca9644b33/inkyshot/update-display.py#L348
)

PS : Finaly, I did (or at least tried) both


titling labels manually

Hi
Is there a where to manually tilt labels I don't seem to be able find it in the documentation?
I have date labels on my bottom axis and are really hard to read when in a long line.

Are you talking about #729 or more specifically that want to specify the amount of rotation?

There is no way to manually rotate labels.


Batching for LabelRowV2

Introduction and Explanation
Current SDK interface implies that operations on different label rows in the same project performed independently.
Such approach causes significant slowdown for some use cases that might include thousands of different label rows.
So while keeping current interface intact, we want to add batching that would allow to speed up bulk label row operations using LabelRowV2
JIRA
None
Documentation
TBD
Tests
Added unit tests
Integration tests TBD
Known issues
None

Closed in favour of https://github.com/encord-team/encord-client-python/pull/310


asio strand scheduler

Summary by CodeRabbit

New Features

Introduced a new build configuration option to enable ASIO support in the RPP library.
Added a new preset for building with ASIO in the CMake configuration.
Integrated the rppasio module into the project structure, enhancing modularity.

Bug Fixes

Improved test coverage for the strand scheduler, ensuring correct task execution order.

Documentation

Updated documentation in new header files to clarify the integration of ASIO with ReactivePlusPlus.

Tests

Added unit tests for the strand scheduler to validate its functionality and behavior in various scenarios.

@CorentinBT , sonarcloud showing valid issues:
https://sonarcloud.io/project/issues?severities=BLOCKER%2CCRITICAL%2CMAJOR%2CMINOR&sinceLeakPeriod=true&issueStatuses=OPEN%2CCONFIRMED&types=BUG&pullRequest=627&id=victimsnino_ReactivePlusPlus&open=AZGlXtnEPhZvl699Zupo
you are trying to forward values but they just forwarded inside lambda: from this point it is regular variable and should be just moved. Forward inside lambda is ok in case of capturing by reference

@CorentinBT , sonarcloud showing valid issues: https://sonarcloud.io/project/issues?severities=BLOCKER%2CCRITICAL%2CMAJOR%2CMINOR&sinceLeakPeriod=true&issueStatuses=OPEN%2CCONFIRMED&types=BUG&pullRequest=627&id=victimsnino_ReactivePlusPlus&open=AZGlXtnEPhZvl699Zupo
you are trying to forward values but they just forwarded inside lambda: from this point it is regular variable and should be just moved. Forward inside lambda is ok in case of capturing by reference

done


chore: updating travis and godoc URLs

chore: updating travis and godoc
URLs were using 'WatchBeam', not using 'mixer'

Thanks for your contribution!


pico/stdlib.h not found

Hi, So I'm trying to start developing for pi pico but I'm unable to get the environment setup
I followed the steps that were provided in the readme
I'm running and developing on Windows 11 if that's necessary information
So my main.c looks like this
#include <stdio.h>
#include "pico/stdlib.h"

int main() {
    setup_default_uart();
    printf("Hello, world!\n");
    return 0;
}

my CMakeLists.txt
cmake_minimum_required(VERSION 3.13)

include(pico_sdk_import.cmake)

project(display C)

pico_sdk_init()

set(CMAKE_C_STANDARD 23)

add_executable(display main.c)

# Add pico_stdlib library which aggregates commonly used features
target_link_libraries(display pico_stdlib)

# create map/bin/hex/uf2 file in addition to ELF.
pico_add_extra_outputs(display)

Cmake log
PICO_SDK_PATH is C:/Users/<my user>/clib/pico
PICO platform is rp2040.
Build type is Debug
Using regular optimized debug build (set PICO_DEOPTIMIZED_DEBUG=1 to de-optimize)
PICO target board is pico.
Using board configuration from C:/Users/<my user>/clib/pico/src/boards/include/boards/pico.h
TinyUSB available at C:/Users/<my user>/clib/pico/lib/tinyusb/src/portable/raspberrypi/rp2040; enabling build support for USB.
Compiling TinyUSB with CFG_TUSB_DEBUG=1
BTstack available at C:/Users/<my user>/clib/pico/lib/btstack
cyw43-driver available at C:/Users/<my user>/clib/pico/lib/cyw43-driver
Pico W Bluetooth build support available.
lwIP available at C:/Users/<my user>/clib/pico/lib/lwip
mbedtls available at C:/Users/<my user>/clib/pico/lib/mbedtls
-- Configuring done
CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_ASM_COMPILE_OBJECT
CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILE_OBJECT
-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

[Failed to reload]

Thanks in advance and I apologize if this has already been solved before. I'm submitting this since I was unable to find a solution

Can you try changing the project line to...
project(display C CXX ASM)

That seems to have done it. thank you.


Fix import paths to be absolute

This PR fixes import paths to be absolute so that players can go-get and go-run.

Thanks!

Thanks for the tip. Ebiten seems like a pretty cool framework.

Awesome. Thank you for using Ebiten and developing your cool game with it!


Get some parser tests to pass

The main point of this PR was to get some additional parser tests to pass:

This PR:

Gets some parser tests to pass
Uses an index map to preserve order for element attributes, but hides it behind an AttributeMap type alias
Adds the ability to render a document in the format used in the tree construction tests

I assume order is not important when interpreting attributes in an element.  But in order to reliably reproduce the printed tree that is used in the tree construction tests, we can't use HashMap, which randomizes the order of the keys.  Instead we use IndexMap, which preserves insertion order.  In order not to create too much of a dependency on the indexmap library in case we want to replace it in the future, an AttributeMap type alias has been used in the code in place of IndexMap.

I think maybe this PR might not be opportune at this time.  I'll close it, and maybe we can revisit some of the topics at a later point.


Login with GitHub tokens

I don't really want to use my GitHub account password. And I have 2-factor auth anyway. It seems like bower does not support token authentication at the moment at all.

You can provide --token option if you don't want to type your password.
Bower supports 2-factor auth.


HKG: EV6 - improved LAT_ACCEL_FACTOR and FRICTION values

Description
This PR improves understeering in the 2022 Kia EV6. This is done simply by cherry-picking a commit from https://github.com/commaai/openpilot/pull/25801, per my comment: https://github.com/commaai/openpilot/pull/25801#issuecomment-1279170301.
Verification
@hoomoose and I have found that in both of our EV6s, these torque values perform significantly better. Without them, stock OP can only maintain centering on straightaways.
Route
without: 859ffc6fd4e4168c|2022-10-13--17-49-56
with: 859ffc6fd4e4168c|2022-10-07--20-13-11

@nuwandavek do we want to wait for all the live torque params we get back to fix all the data?

@sshane I'm going to retune all values next week (same with the ionic PR) once the low speed controls are stable on good torque cars (toyotas mostly).

#26261 has new values that work really well on our EV6. It will also enable the live torque parameter learner on the EV6. Let us know if you still have issues after that's merged.


App crash when user not provide permission for camera?

I have added the notAuthorizedView for iOS as well as checkAndroid6Permissions and permissionDialogTitle, permissionDialogMessage for android. But when I declined the camera permission app crashed.
What's happening?

How to avoid crash when the permission is declined in both android and iOS.
How can it be reproduced?

Prepare the setup as described in react-native-qrcode-scanner doc. Launch the app. Application will ask for the camera permission. Declined the permission and app crashed.
Build details?

react: "16.3.1",
react-native: "0.55.4",
react-native-camera: "^1.1.4",
react-native-qrcode-scanner: ^1.0.1
macOS: 10.13

I had the same issue. You might say that this guy sounds dumb, but I followed him and it worked :))
https://github.com/moaazsidat/react-native-qrcode-scanner/issues/94#issuecomment-395737055


problem with Depth

Hello ,
I am using pyocto,  I need to calculate depth of events to 300km. But the last depth that it gave me is 250. I change some parameter like association_cutoff_distance= 300, but it doesn;t change. could you please help me with this if ut is possible<
thanks

Hey!
Thanks for your interest in PyOcto. Regarding the depth, you should check that the zlim covers the range you're looking for. In addition, if you use a 1D model, it needs to cover a sufficient depth range. One potential reason for poor depth estimates might also be that the picks constrain the depth poorly. In that case, PyOcto might associate the right set of picks but the location might be poor. In general, I'd recommend to use locations from PyOcto only as a first orientation and use a dedicated tool like NonLinLoc for precise locations.

Thanks for your answer, I am working on chile data and set parameter  like you did, the only thing that we want to know if we have depth until 300km. ya, we will relocate events in next step.


good_till_date cannot be null in create_working_order

Hi again,
In the REST api, in the create_working_order method, parameter good_till_date is converted to date. I noticed that this parameter is not mandatory and can be null.
I would suggest to replace in the trading_ig/rest.py file on line 518
good_till_date = conv_datetime(good_till_date, 1)
by
if good_till_date != None:
            good_till_date = conv_datetime(good_till_date, 1)

Ok I did
    def create_working_order(self, currency_code, direction, epic, expiry,
                             guaranteed_stop, level,
                             limit_distance, limit_level, size, stop_distance,
                             stop_level, time_in_force, order_type,
                             good_till_date=None,
                             session=None):
        """Creates an OTC working order"""

        if good_till_date is not None:
            good_till_date = conv_datetime(good_till_date, 1)

see https://github.com/ig-python/ig-markets-api-python-library/commit/372e7fcdf8fda8319f351feb08fd615615e02182
You just need to git checkout
Feel free to reopen this issue if it's not correctly solved


container not movable when top is outside of the canvas

when a container is placed too high and the WireIt-Container-ddhandle is outside of the canvas, the scrollbars don't appear (when placed too far right or down then the scrollbars do appear), resulting in not being able to move or delete the container ever again.

same Issue


fix(overlay-directives): update offsets if they change after overlay creation

This PR allows the offset to be updated after the overlay is created.
r: @jelbourn

LGTM


Trackpad reversed after reboot, when only mouse is reversed in SR settings

I have used Scroll Reverser for a while (since before paid). Recently (I would say since the most recent update of Scroll Reverser?) I am seeing a new issue, whereby if I have mouse wheel reversed (vertical only) and trackpad not reversed then randomly, after a certain amount of time, trackpad becomes reversed vertically too.
I have scroll reverser 1.8.1 on Mac OS 11.5 Beta 20G6065a. I suspect the issue is not to do with the version of Mac OS, though of course it may be.

Can confirm that the issue is the same on 11.5 RC.
Btw, to fix this issue, I just need to disable then re-enable scroll reverser (it its own menu).

I believe the issue occurs reliably (or quite reliably) after a reboot. The scroll of my trackpad is reversed even though I have requested that only mouse scroll is reversed in ST settings. Unchecking then rechecking 'Enable Scroll Reverser' fixes it.

Thanks for reporting and the extra details. When you say a reboot you mean a full shut down and reboot of the OS - you don't mean a sleep/wake? (I ask because sleep/wake has been an issue in the past.)

Yes, full reboot

So it's definitely not all the time. I think it may happen after wake from sleep too, but I've definitely just had one after a reboot, not a wake from sleep. Also, I reboot my Mac several times a day, for testing some bootloader stuff I'm working on, so this does happen usually at least once a day.

I'm having this exact same issue. It seemed to only start happening after updating to Big Sur (I'm now running macOS 11.4). My scroll reverser version is 1.8.1 (10490). This will randomly happen at least once a day, but usually more frequently. I can also get it to go back to the expected behavior by toggling scroll reverser disabled/enabled in the menu bar.

I can confirm I've just had a case after wake from sleep - so this is definitely occurring in both cases: wake from sleep and reboot.
I believe I could be related to Big Sur 11.4+ (I'm on 11.5, I would say it definitely was not happening on 11.3 and earlier)? Or to a recent update of Scroll Reverser itself?

Have just gone back to 1.8 - will update as to whether issue still occurs.

Thank you - yes that would be useful to know
Sent from my iPhone

On 1 Aug 2021, at 09:33, Mike Beaton @.***> wrote:

Have just gone back to 1.8 - will update as to whether issue still occurs.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @invariant first off thanks for such a great utility! Just want to confirm that I have the same problem after updating to the 1.8.1. The trackpad scrolling got reversed with the following setting:

Reverse Vertical
Reverse Mouse
The system I'm using macOS 11.5.x. This happens on both my MacBookPro (2018, 15inch) with different system configurations.

I have to close and reopen the app to resolve this problem.
Would like to know if there's any idea about it.
Thanks in advance!

@MikeBeaton, @mspoehr, @sysctI: Thanks for your patience on this. I haven't seen this happen yet for myself so I will need all your help to track down what is going wrong. Let's start with the debug log. When this next happens can you please Option(⌥)-click the Scroll Reverser menu bar icon which reveals a debug console. Then do some scrolling with trackpad, pause the log and paste me the log (it doesn't have to be hundreds of lines, just a screenful ought to be enough).

@invariant I promised to update, FYI I have not been getting this since rolling SR back to 1.8.

@invariant Just had this happen. Anecdotally, it does seem to happen after unlocking.  It looks like macOS is not sending trackpad touch data to Scroll Reverser. Can you confirm if unchecking and rechecking "Enable Scroll Reverser" really is sufficient to resolve it or if it is necessary to quit and restart Scroll reverser?
Also can you tell me if you have Scroll Reverser in the "Input Monitoring" list in Security & Privacy → Accessibility?

@invariant I promised to update, FYI I have not been getting this since rolling SR back to 1.8.

Thanks, that is useful. Do let me know if it does happen. I've been poring over the code changes between 1.8 to 1.8.1 and and there's nothing I can understand that could account for the change. It's so frustrating, which is added to that it doesn't happen on my Mac so I can't even fault find.

I can also 100% confirm that just checking and unchecking is sufficient to restore correct behaviour. I could go back to 1.8.1 and send you a log when it misbehaves. I guess it would be useful to see the log when misbehaving, and then also the log after checking and unchecking to restore behaviour?

I can also 100% confirm that just checking and unchecking is sufficient to restore correct behaviour. I could go back to 1.8.1 and send you a log when it misbehaves. I guess it would be useful to see the log when misbehaving, and then also the log after checking and unchecking to restore behaviour?

Thanks for the solid confirm, that's really interesting. Yes might be worth switching to 1.8.1 again to double check that it really is a difference between the two.
Also can any of you tell me if you are using any other mouse utilities, drivers etc. at the same time? I'm wondering if there is an interaction going on with another app.

Reversed again very quickly when I went back to 1.8.1 (confirming sense that it is very different, believe it does not happen at all, on 1.8).
FYI log window looks like this(!):

However, can still pause, copy, and paste.
 Looks like this matches @mspoehr's report.

Yes, simply unchecking and rechecking "Enable Scroll Reverser" has resolved the issue 100% of the time. I don't think I've ever restarted Scroll Reverser completely.

Also can you tell me if you have Scroll Reverser in the "Input Monitoring" list in Security & Privacy → Accessibility?

Yes, it appears in the list and is checked.
 I'm wondering if there is an interaction going on with another app.

Not that I am aware of. FWIW, the only other apps checked under Security & Privacy > Privacy > Accessibility are iTerm and Microsoft Teams.

Happy to install test versions btw, though obviously it takes longer to be sure when the problem is not happening.
Was wondering whether to download, build and do binary search for the commit which caused the problem - though it looks like I'd have to do a bit of messing around with code signing to get the build up and running! (I don't think you already conveniently have any CI with build artefacts per commit, or anything?!)

Happy to install test versions btw, though obviously it takes longer to be sure when the problem is not happening.
Was wondering whether to download, build and do binary search for the commit which caused the problem - though it looks like I'd have to do a bit of messing around with code signing to get the build up and running! (I don't think you already conveniently have any CI with build artefacts per commit, or anything?!)

If you have your own Developer ID code signing certificate it should be a case of simply swapping mine for yours in the Xcode project settings. However if you want to sign to run locally it currently won't build because of Sparkle throwing errors. One of my eternal todos is to make a "out of box" build that just works but until then....

Happy to install test versions btw, though obviously it takes longer to be sure when the problem is not happening.
Was wondering whether to download, build and do binary search for the commit which caused the problem - though it looks like I'd have to do a bit of messing around with code signing to get the build up and running! (I don't think you already conveniently have any CI with build artefacts per commit, or anything?!)

If you have your own Developer ID code signing certificate it should be a case of simply swapping mine for yours in the Xcode project settings. However if you want to sign to run locally it currently won't build because of Sparkle throwing errors. One of my eternal todos is to make a "out of box" build that just works but until then....

Unfortunately I don't. The only Mac related project I'm contributing to is bootloader (so any code-signing involved is a different thing), and I'm not joined to any Mac developer program, currently. Looks like there exist plausible instructions for creating a self-generated cert and approving the (self-generated) CA on my machine, so I believe that's what I'd need to do!

Just checking in as this is continuing to happen for me. I generally just lock my mac (rarely shut down or reboot), but I've noticed that this issue pretty much happens 100% of the time after I unlock if the screen turns itself off. If I manually lock then unlock, it doesn't happen, but I suppose it could be tied to how long the screen is off and not the method used to get there.

I've gone back to version 1.8, which works fine for me. (Apologies, but I have not yet found the time to set up the build and bisect to search for the offending commit, as I suggested I would - and still would/will given enough time.)

I thought I had this issue. Turns out that Logitech mice also have such an option to be "standard". So it seems that the scroll reverser was fighting with the Logitech software. Maybe this can be in the FAQ?

https://apple.stackexchange.com/questions/116617/how-to-separate-mouse-and-trackpad-settings

I do not have a logitech mouse, it happens for me on all mice! So that is not the (only) issue.
@invariant - I have not had a chance to get your build working - I'm sure it's not really that hard, it's just that I'm working on my own OSS contributions elsewhere (plus a day job!). If you fancy building versions at various commits, for some kind of binary search towards the issue, I'm happy to run them and report back.


Announcement banner on TenFour.org

From tenfour-archive created by caharding: ushahidi/tenfour-archive#1451
We need a way of creating a small banner that features new announcements at the top of our page. I recommend a ~40px TenFour green box with white bold lettering in it, something simple

@Angamanga is there a place I can see this if it's ready? so I can Design QA :)


Fix rotation yaw in compass element

It will be better to use yaw from active render info. In some cases real camera yaw can be different from player yaw (with mirrored third person mode).

Please add similar fix to other (supported) versions for Forge and Fabric.


Plans for Open Container Format compatibility?

Now that opencontainers.org has launched, and the runC implementation in Go is released, are there any plans to make Vagga compatible with these?

Someone would need to write an runC implementation in Rust first.

Given that runC is basically a copy of appC, don't you have a substantial
franction of that in
https://github.com/tailhook/vagga/tree/master/src/container already?

Sure, I plan to do that (sorry, development is a bit slow now, because I should do rust 1.0 porting, which is a huge and atomic piece of work).
But I don't think you should look forward to it too much. Because vagga has two powerful things:

It's a fully unprivileged container runner (runc doesn't able to run unprivileged AFAIK). And there are limitation of what can be run unprivileged. So vagga will have somewhat limited features.
Vagga is a powerful and easy to use build tool for containers. Opencontainer doesn't say anything about how containers would be built.

So basically integration looks like a way to import OCP container and to export to OCP container. Which you can basically do now (by using !Tar command and by tar'ing .vagga/container_name folder respectively), except some vagga.yaml <-> config.json convertation may help.
Note also that as part of No.1 above, vagga not only runs unprivileged, it also does its best to isolate application to never touch any files outside of the project dir. So it will likely never be able to mount arbitrary directories and support arbitrary privileges.
Anyway having rusty libcontainer and simple runc-like utility would be nice. I even have to consider publish it earlier than vagga for rust 1.x, because it's smaller in scope. But I'm not sure I'm able to do good API (and I'm not sure libcontainer's API is rich enough for vagga itself, if I would copy that). Sure src/container/container.rs is mostly same thing, except it was created specifically for vagga.
Thoughts?

Well, I was looking for a copy of runC in Rust (mostly to see if I should consider writing such myself as a project to learn Rust) when I came across vagga.
So I figured I'd ask if the equivalent work was already planned and I shouldn't bother duplicating effort.
It sounds as though vagga is different enough from Docker that such a library would be of very limited utility to it, but that a portion of vagga's existing code could be forked off to start writing an actual runC implementation.

So, @tailhook, is a compatible version of runC.rs something you want to work on yourself, or not?

Well, I'm more interested in container library that may be used for both runc and vagga. But not in the runc binary itself. But I may find time for it only after I'll port vagga to rust 1.x.

@webmaven, I've started some work at https://github.com/tailhook/unshare, its low-level library for dealing with namespaces/chroots, etc. It's written from scratch, so it's mostly stub now, but should be done shortly, as I have already done that twice (This time I want to get rid of C code so that's why I'm rewriting)
After it will be in working stage we also need:

dealing with mountpoints
handling signals (probably on top of eventfd/mio?)
setting up network (is it a part of runc for now?)

Then we can build runc on top of all this stuff.
Bonus points would be:

Some super-minimal musl-linked in-container process supervisor (i.e. init), it's not in current runc, too, right? Because it's wrong to run arbitrary application as pid 1.
Cgroup handling library (it's not clear whether they are part of runc too)

Thoughts?

Okay this issue doesn't represent current status any more.
We have pretty good unshare crate, handling namespaces stuff. The signal crate that works with signals. And just recently started libmount crate which handles mount points (not everything from vagga moved there yet).
With the time passed it looks like we don't need any runc compatibility. At least nobody complained on it since then.
While my opinion may be a little bit biased (because I'm the author of vagga), but I think vagga provides higher level building tools and versioning of containers, with a user friendly UI, rather than pure runner. For anybody not familiar with vagga reading this, I would describe it like: vagga is the tool that "gets base system, installs package X with version Y, and then is able to run command in that container or upload the image to a repository". On the other hand, runc is of the kind "download that image and run something in it". It looks like they are on the opposite ends of the spectrum.
We could also allow to download runc images in vagga. But again (in my biased opinion) it looks like vagga makes building images easier than runc and docker, so nobody needs it. So unless someone does a pull request, it doesn't going to happen.
Anyway, it would probably be nice if someone would write a runc clone with unshare and libmount so we could reuse most of the mission-critical code.

OK, so I am (tentatively) still interested in writing a runC clone in Rust (probably using unshare and libmount). I'll ping you if/when I get the project started.


How to send str json format ping

It seems bybit requires user to send custom ping in str type not byte type.

Its offical sdk using self.custom_ping_message = json.dumps({"op": "ping"}) which returns a str type. However, I am using orjson.dumps({"op": "ping"} which returns byte type and the websocket will return b'\x03\xe9'. How to solve it?
class Listener(WSListener):
    def __init__(self, logger, specific_ping_msg: bytes = None):
        self._log = logger
        self.msg_queue = asyncio.Queue()
        self._specific_ping_msg = specific_ping_msg

    def send_user_specific_ping(self, transport: WSTransport):
        if self._specific_ping_msg:
            transport.send(WSMsgType.TEXT, self._specific_ping_msg)
        else:
            transport.send_ping()

    def on_ws_connected(self, transport: WSTransport):
        self._log.info("Connected to Websocket...")

    def on_ws_disconnected(self, transport: WSTransport):
        self._log.info("Disconnected from Websocket.")

    def on_ws_frame(self, transport: WSTransport, frame: WSFrame):
        try:
            if frame.msg_type == WSMsgType.PING:
                transport.send_pong(
                    frame.get_payload_as_bytes()
                )  # if enabled auto pong, we don't need to send pong manually
                return
            # msg = orjson.loads(frame.get_payload_as_bytes())
            self.msg_queue.put_nowait(
                frame.get_payload_as_bytes()
            )  # I think we should decode the frame in the handler
        except Exception as e:
            self._log.error(f"Error processing message: {str(e)}")

However, If I send json.dumps({"op": "ping"}), I got:
Traceback (most recent call last):
  File "picows/picows.pyx", line 1080, in picows.picows.WSProtocol._auto_ping_loop
  File "picows/picows.pyx", line 344, in picows.picows.WSListener.send_user_specific_ping
  File "/root/tradebot-pro/tradebot/base.py", line 371, in send_user_specific_ping
    transport.send(WSMsgType.TEXT, self._specific_ping_msg)
  File "picows/picows.pyx", line 453, in picows.picows.WSTransport.send
  File "picows/picows.pyx", line 473, in picows.picows.WSTransport.send
  File "picows/picows.pyx", line 154, in picows.picows._unpack_bytes_like
TypeError: a bytes-like object is required, not 'str'

It seems bybit requires user to send custom ping in str type not byte type.

Its offical [sdk](https://github.com/bybit-exchange/pybit/blob/master/pybit/_websocket_stream.py) using `self.custom_ping_message = json.dumps({"op": "ping"})` which returns a str type. However, I am using `orjson.dumps({"op": "ping"}` which returns byte type and the websocket will return `b'\x03\xe9'`. How to solve it?
class Listener(WSListener):
    def __init__(self, logger, specific_ping_msg: bytes = None):
        self._log = logger
        self.msg_queue = asyncio.Queue()
        self._specific_ping_msg = specific_ping_msg

    def send_user_specific_ping(self, transport: WSTransport):
        if self._specific_ping_msg:
            transport.send(WSMsgType.TEXT, self._specific_ping_msg)
        else:
            transport.send_ping()

    def on_ws_connected(self, transport: WSTransport):
        self._log.info("Connected to Websocket...")

    def on_ws_disconnected(self, transport: WSTransport):
        self._log.info("Disconnected from Websocket.")

    def on_ws_frame(self, transport: WSTransport, frame: WSFrame):
        try:
            if frame.msg_type == WSMsgType.PING:
                transport.send_pong(
                    frame.get_payload_as_bytes()
                )  # if enabled auto pong, we don't need to send pong manually
                return
            # msg = orjson.loads(frame.get_payload_as_bytes())
            self.msg_queue.put_nowait(
                frame.get_payload_as_bytes()
            )  # I think we should decode the frame in the handler
        except Exception as e:
            self._log.error(f"Error processing message: {str(e)}")

However, If I send json.dumps({"op": "ping"}), I got:
Traceback (most recent call last):
  File "picows/picows.pyx", line 1080, in picows.picows.WSProtocol._auto_ping_loop
  File "picows/picows.pyx", line 344, in picows.picows.WSListener.send_user_specific_ping
  File "/root/tradebot-pro/tradebot/base.py", line 371, in send_user_specific_ping
    transport.send(WSMsgType.TEXT, self._specific_ping_msg)
  File "picows/picows.pyx", line 453, in picows.picows.WSTransport.send
  File "picows/picows.pyx", line 473, in picows.picows.WSTransport.send
  File "picows/picows.pyx", line 154, in picows.picows._unpack_bytes_like
TypeError: a bytes-like object is required, not 'str'

It is also wield, I receiving success ping message when sending byte type ping.

But still receiving the b'\x03\xe9' and one successful ping return corresponds to the error message b'\x03\xe9'.

bybit can't "require str not bytes". On a protocol level transmitted data are always just bytes.
"However, I am using orjson.dumps({"op": "ping"} which returns byte type and the websocket will return b'\x03\xe9'"
What does mean that "the websocket will return b'\x03\xe9'"?
After sending {"op": "ping"} you should receive {"op": "pong"} from bybit. Since you are using custom ping messages you should let picows know that pong has indeed arrived.
To do that you either overload WSListener.is_user_specific_pong or call transport.notify_user_specific_pong_received() from on_ws_frame
Check the guide on auto ping feature. It explains exactly that.
https://picows.readthedocs.io/en/stable/guides.html#auto-ping


Documentation

Is there documentation somewhere on all the editors and how to use them?
Thanks

Some are in wiki https://github.com/volkanceylan/Serenity/wiki/Editor Types
other can found in Serenity Manual


CVAT deployment on Kubernetes with Helm - 404 page not found

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Description
Hi,
I try to run cvat with using helm-chart and instruction plased in documentatiom but I have problem. When I try to open CVAT via web browser (aws elb treafik service adres) I get 404 on that page. I don't know where can be aproblem becasue in configuration of services allowed hosts is equals "*". I try to run it with default configuration without any overited variables.
Expected Behaviour
Access to service.
Current Behaviour
404 page not found

@marekpawlowski Hi you have to override host value here https://github.com/opencv/cvat/blob/develop/helm-chart/values.yaml#L283
like this:
helm upgrade -n default cvat -i --create-namespace helm-chart -f helm-chart/values.yaml -f helm-chart/values.override.yaml --set ingress.hosts[0].host=YOUR_DOMAIN


HARP-5431 Zoomlevel now based on distance from... low resolution terrain (level 4 tiles).

@heremaps-bot retest this please


Personabar TabOrder after Import

Description
Portal Import resets tab order in 9.1.1 if we have costume ordered tabs earlier.
Steps to reproduce
Create a fresh installation of 9.1.1 or 9.2.0
Create few pages with some content on them
Create few nested pages too.
Export this portal
Import this Portal
Current result
Pages order in new Portal is reset to default (on 9.1.1)
Pages are missing in 9.2
Expected result
Pages should not be missing or order should not be reset to default
Affected version

[x] 9.2
[x] 9.1.1
[ ] 9.1
[ ] 9.0

Fixed by #2074
@dnnsoftware/tag please close at will


improve the experience of stopping a recording

The hyperminimal version of this would be to reset the elapsed time to 00:00.
But ideally there's a visual indication that the recording was saved at the OS level, giving the user comfort and assurance that it was correctly recorded via Healthkit.
One way to do this could be to have a "recording complete" screen, with the elapsed time of the run, and an icon and button/link to open the recording in the official Workout app.

fixed this issue in this commit

new flow is great, even cleaner than original suggestion


fix issue that causes MissingPreviousEpoch error in CI

There was a lot of flakiness in the reconnect tests that this should address, while also making them faster.  Also sets a max delay on client requests to 1sec.
Fixes #860 or at least improves it...if anyone encounters again please ping me.

Codecov Report
Base: 66.50% // Head: 66.45% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (63d610f) compared to base (6cb928f).
Patch coverage: 85.71% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1025      +/-   ##
==========================================
- Coverage   66.50%   66.45%   -0.06%
==========================================
  Files         116      116
  Lines       17600    17603       +3
==========================================
- Hits        11705    11698       -7
- Misses       5895     5905      +10

Impacted Files
Coverage Δ

client/client-lib/src/query.rs
94.33% <0.00%> (ø)

client/client-lib/src/api.rs
79.22% <100.00%> (+0.05%)
:arrow_up:

fedimint-server/src/lib.rs
80.56% <100.00%> (-0.93%)
:arrow_down:

fedimint-server/src/net/peers.rs
88.82% <0.00%> (-0.89%)
:arrow_down:

fedimint-server/src/net/connect.rs
95.01% <0.00%> (-0.25%)
:arrow_down:

fedimint-api/src/core.rs
91.97% <0.00%> (-0.23%)
:arrow_down:

modules/fedimint-mint/src/lib.rs
80.20% <0.00%> (-0.14%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


support for 'stats' unix socket

Support for HAProxy's stats socket as described in http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#stats socket
It is enabled by using 'unix:/your/file' as the scape URI.
This saves setting up the HTTP admin website, and makes haproxy_exporter potentially easier to use with nbproc>1

For @grobie maybe?

The idea is to have the stats like this:
        stats socket /var/run/haproxy/stats.1.sock process 1
        stats socket /var/run/haproxy/stats.2.sock process 2
        stats socket /var/run/haproxy/stats.3.sock process 3

This is easier to configure than multiple statistic sites, imho.

Looks great on first glance. I'll give it a thorough look tonight.

Thanks a lot! I only have one question regarding closing connections upon write errors.
IMHO, we should have tests covering the unix connection path and an invalid URL input. Do you think you could add these?

Thanks for your quick review, @grobie!
I've added the (three) missing Close()-on-errors, and added a unittest with an actual unix socket. I guess this will break the tests on windows system (although HAProxy doesn't seem supported there it would be possible to run haproxy_exporter from a windows machine), so I could move that test to a different file which would be excluded on windows.
I can squash all the commits when done, if you want.

I've skipped the new unix socket test on windows, just to prevent some problems.

Thank you for your great contribution and the tests! It looks great, please
squash.
On Jun 7, 2016 10:55, "Harmen"<EMAIL_ADDRESS>wrote:

I've skipped the new unix socket test on windows, just to prevent some
problems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/haproxy_exporter/pull/58#issuecomment-224220143,
or mute the thread
https://github.com/notifications/unsubscribe/AAANaEe5bdUJOgyja4nl8pMyPFym_KKAks5qJTIQgaJpZM4IvFhE
.

@grobie: squashed

I missed that the unix connection doesn't use a timeout. We use socket connections in an internal controller (maintenance, draining, etc.) and ran into problems there before we introduced the timeout.
I'd suggest to pass the timeout flag and use net.DialTimeout() and a read deadline.

Added the deadline, with some tests. There is a change how read errors are counted, which I commented on inline.

Awesome! Thank you so much. I'll cut a new release this week.


Relationship between UCRs and Solid user-stories

On proposal
ACP, WAC, WAC+...
Details
What is the relationship between the UCRs defined by the authorization panel and the Solid user stories on authorization?
Acceptance criteria

[x] Understand how UCR and user stories overlap and what form of reuse or linking should be adopted
[ ] Agree on an adequate plan of action

The user stories, from my side, are intended as a extremely low threshold thing for the community to contribute their needs in a structured manner that can potentially be useful.
We learned very soon that it is actually very hard for people to come up with use cases that can inform spec in a useful way, the response is usually "yes, Solid can do that, just write some client code". We shouldn't have people wasting their time writing stuff that can be dismissed that easily, and we shouldn't spend time having to go through them and dismiss them either, it isn't nice and good use of time for anyone.
Therefore, we created the user-stories repo so that people can submit these one-liners, without making a huge effort, and yet, structure them better. This makes it more likely that a small effort can make something that is actually useful.
My idea is then that the user stories can be closed once we can point people to an implementation that does what they wanted.
The UCRs should be a more elaborate thing done by experts. They should be encouraged to review the user stories, but also other sources of information. The UCR are what is the immediate motivator for spec work, user stories a mere help to experts.
But then, I also hope that user stories can be a broader view, so that experts also find it useful to submit user stories.

Thank you for the clarification @kjetilk.
I guess the adequate plan of action would then be, when time allows, to go through the Solid user stories on authorization and link them back to existing answers. I would propose that this plan of action is generic to all user-stories issues as opposed to tightly coupled to the authorization panel and therefore, that this issue should be closed.