Gakuen K - Wonderful School Days V Edition [PCSG00654]

App summary

App name: 学園K -Wonderful School Days- V  Edition
App serial: PCSG00654
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3173
Commit hash: https://github.com/vita3k/vita3k/commit/42d6b4ef
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Dystnine
OS: Windows 7
CPU: INTEL I3 4100U
GPU: AMD HD8500M
RAM: 8 GB

Issues

The emulator will freeze when loading.
Screenshots

Log
vita3k.log
Recommended labels

Menu

[load_self]: You're trying to load a vitamin dump. It is not supported.


LSTM internal weights in TFLite

As you know, LSTM cell has four internal gates: forget, input, output and cell gate (https://colah.github.io/posts/2015-08-Understanding-LSTMs/) When we convert a model containing LSTM to TFLite format, we can see the internal weights in groups like "std.constant9" (with no specific name). But it isn't clear that which weight group is related to which gate. In other words, how do we recognize weights for each internal gate?
Sample files are attached if needed. Thanks in advance.

tflite_models.zip

@efard please investigate this issue and submit a pull request with a fix.

For test reasons, I made some minor changes in code, like this (line 44 of tflite-metadata.json):
{ "name": "output_bias", "type": "T", "description": "Output gate bias tensor.", "visible": false},
to
{ "name": "output_bias", "type": "T", "description": "Output gate bias tensor.", "visible": true },
or this (line 86 of tflite-metadata.json):
{ "name": "input", "type": "T" },
to
{ "name": "input!!!!!!", "type": "T" },
But no changes are applied in netron GUI, even after system restart. Did I do something wrong?


Performance issue with video conference

We are having trouble achieving the performance stated on this page, https://jitsi.org/jitsi-videobridge-performance-evaluation/. We have Openfire with the ofmeet and offocus plugin installed on a 16 core, 16GB RAM CentOS 7 server. With a 3 party video conference call, CPU usage is about 55%. We have also built the latest SNAPSHOT of 0.9.5 of ofmeet, and the result is about the same. If we run jitsi-hammer with 100 users on a call, the load average shot up to 26+. The Java thread count was about 1200.
For those of you who have similar installation of Openfire with ofmeet, what kind of performance do you get? If it's better, did you make any change to the configuration?
BTW, we have also tried a standalone installation of Jitsi Videobridge on a Ubuntu 16.04 server with 4 core, 8GB RAM. The performance is slightly better, but not much. 3-party video conference call uses about 45% of CPU.
Thanks for your help!

Please note that OFMeet was designed to provide ease of installation. Although it should perform well in a light to moderate usage context, it has not been designed for high-performance. For that, I recommend you use the stand-alone Jitsi components. Note that the Jitsi team has provided numerous resources that showcase how a very resilient, high-performant setup can be achieved.

@guusdk Thanks for your quick response. In my original post, I mentioned that we also tried the standalone Jitsi Videobridge with default installation/configuration. The result wasn't much better. Following your recommendation, we'll look into that again, and may seek help from the Jitsi team.

Good luck. Jitsi has a bunch of videos like these, which can be very helpful: https://jitsi.org/news/tag/tutorial/

We are having trouble achieving the performance stated on this page, https://jitsi.org/jitsi-videobridge-performance-evaluation/.

I don't think you can achieve those figures any more as they were done a while back before WebRTC 1.0 was confirmed. Since then, there has been default multiplexing on a single UDP port, H264 and VP9 video codecs to all take into consideration as far the server CPU load is concerned.
What happens to your CPU when you hit the magic 32x31 media streams and run out of bandwidth with a 1GB network adapter?

@deleolajide That's good to know. I wonder what kind of realistic performance data does the latest standalone Jitsi Videobridge have.
Good point on the bandwidth usage. There was some DTLS error when running Jitsi hammer against the ofmeet server. However, it did generate enough load on the server, without saturating the network based on iptraf. The main issue is that, even with a 3 party call on the standalone Jitsi installation, it was using 45% of CPU.

I was curious about the 45% CPU, so I ran some tests on my CentOS 7 server

I tried both top and mpstat. I can see Java (openfire meetings) consuming 34%, but I can't reconcile that with the CPU reported as being 99.xx% idle

Your server has 32 cores, 64GB RAM. With 33.3% usage by all the cores, it should be about 99% idle. On ours, Java CPU usage ranged from 3x% to 6x%.

Thank you for the explanation :-)


Scrolling stopped working - "undefined is not a function (evaluating '$scope.direction.indexOf('x')')"

Ionic app scrolls  stops working due to this bug.
There is no more info besides this stacktrace below.
scroll error: Arguments (2)
0 Error
column: 51
line: 51583

message: "undefined is not a function (evaluating '$scope.direction.indexOf('x')')"
name: "TypeError"

sourceURL: "file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js"
stack: "prelink@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:51583:51↵invokeLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:17046:15↵nodeLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:16535:23↵compositeLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:15905:23↵nodeLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:16551:35↵compositeLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:15905:23↵publicLinkFn@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:15784:45↵appendViewElement@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:48439:11↵render@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:46629:58↵init@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:46549:26↵render@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:48295:18↵register@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:48253:16↵updateView@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:53645:31↵file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:53622:21↵$broadcast@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:23547:33↵file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:41017:32↵processQueue@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:22016:29↵file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:22032:39↵$eval@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:23228:28↵$digest@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:23044:36↵$apply@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:23333:31↵file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:20191:30↵eventHandler@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:11841:25↵dispatchEvent@[native code]↵triggerMouseEvent@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:2865:20↵tapClick@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:2854:20↵tapTouchEnd@file:///private/var/mobile/Containers/Bundle/Application/1A6FF180-5387-400F-85A0-32B8CF84D3C3/Demo.app/www/lib/ionic/js/ionic.bundle.js:2977:13"
Error Prototype

1"<ion-content has-bouncing=\"true\" class=\"parcel-communication has-footer chat scroll-content ionic-scroll\" delegate-handle=\"chatMessageScroll\">"

Greetings @thim81!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Ionic
"version": "1.0.1",
"codename": "vanadium-vaquita",

We tried something, we added to the templates where the error occured the following to ion-content
overflow-scroll='false'
Not really sure how this could solve the issue but the error seems gone for now?
Does this mean that we are using Native or JS scrolling?

Looks like it could be related to a variable naming conflict.
In our controller we use a variable $rootScope.direction which conflicts with the ionic core $scope.direction
We were pointed in this direction via: https://github.com/driftyco/ionic/issues/4068


added rotated array search in python

Assigned Issue Number?
No issue
Language Opted?
Python.
Number of files added or updated?
1
Name of these files?
Data_Structures => Array => Rotated_Array_Search.py
Checklist

[X] I was assigned for this otherwise my PR will be rejected.
[X] I've read the contribution guidelines.
[X] I've referred the correct issue number.
[X] I've filled up this entire template correctly.

:star2: this repository and support.

@PrajaktaS23 👍🏼


Fixed SSR bug in parseCookies in with-apollo-auth example

If you do a server-side GraphQL query without a cookie set in ctx.req.headers you will get the error: ReferenceError: document is not defined because there is no document in Node.js.
This PR fixes the logic in parseCookies to prevent that from happening.
Also wanted to say thanks @jesstelford for this example! It's great!

@arunoda can you merge this one 🙌

@timneutkens shouldn't this be merged into master and not v3-beta?

Keeps haunting me >.<


[UI] Create component for course > references

/courses/create/references -(next)->

@IsharaEkanayaka any progress on this issue or do you already completed?


rotate 511 api key

we should make a new secret, add it to kube secrets, then update the code to use the new one from secrets. The main reason we should do this is because it is committed to this public repo, so anyone could be using it right now.
https://github.com/bikehopper/graphhopper/blob/master/k8s/build-graphhopper-graph-cache.job.yml#L39

@Andykmcc this is done, right?

gentle bump, is this completed?

It must be. I don't even know what this is referring too. But we do t have any keys in got so far as I know.


Clarified Visual Studio Build Options

autotrack-master.zip
This option can only be modified in Visual Studio 2015 and earlier. Added Clarification.
Summary
3044128440
Describe your changes here.
Fixes #Issue_Number (if available)3044128440

@JRAlexander was this some sort of test branch you had?


EmptyReply / 404 for JSON not detected as a change. No notification was sent even though the required settings were enabled.

I was watching a JSON that had data and then went blank (404).
I was supposed to get a notification but I didn't get any notification even though all the settings shown in the picture below were enabled.
As you can see in the picture, the status literally shows the error "EmptyReply - try increasing 'Wait seconds before extracting text', Status Code 404" on the URL watch list but a notification was not sent.
Notifications are configured properly. They work on everything else.
I'm using the latest version (0.46.02) on Debian 12.6.
I also tested the previous release (0.46.01) but the same thing happened.
It looks like something similar happened with normal HTMLs on #2501 but the last reply was ignored and the issue was closed.

without knowing the URL theres not much to help with :-(


eternalness, florinda

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[e,f]

/trunk merge


Smooth Mode - Lag when scrolling

Since I updated, activating smooth mode seems to make my VSCode lag when I scroll.

Thank you for making an issue about this. I know what the problem is and it has to do with a complex css selector and I will get to fixing it very soon.

This should be fixed with the newest version 1.0.11.

Gonna try that 🙂


Complication secondary and some colors are not visible (observed on a Pixel Watch)

Similar as https://github.com/CsabaConsulting/VFDWatchFace/issues/3

First maybe we need the #3 rewrite and see if that solves this issue as well.


pa11y-reporter-json-oldnode

Because we still want the new JSON reporter format, but with compatibility with old versions of Node.js. Project is here: https://github.com/singingwolfboy/pa11y-reporter-json-oldnode

@benpatterson I think this will give us the best of both worlds: compatibility with old versions of Node, and the CSS selector information provided by the latest JSON reporter. Can you review?

I think this looks good... If you haven't done this already, could you enter a ticket for pa11ycrawler work we'd want to take on for when we do upgrade node on platform?
👍 for this PR


ocamlPackages.lsp: 1.18.0 -> 1.19.0

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

There is a better version of this change: https://github.com/nixos/nixpkgs/commit/f7a3ade7d35de8f24f53d2ef2090f9236864fd83.patch
However, this breaks linol…

linol is only used for ligo currently right? I'm not actively maintaining ligo anymore so either we should ask @EduardoRFS or someone on his team to step up as maintainer or it might be time to drop it as it's only getting more out of date.

In the end the linol issue is trivial to sort out:  #344686.

Done in https://github.com/NixOS/nixpkgs/pull/344686

I can step up as a maintainer, also linol will be dropped on a feature release. The team is 100% on Nix now.

@EduardoRFS you know where to find me if you want help adding yourself :)


[CQT-288] Fix bug in ZXZ decomposer

Fix check for needing to swap theta 1 and theta 3.
We were checking (b < 0 and c < 0) instead of (b <= 0 and c <= 0 and not (b ==0 and c == 0)).
Add test_specific_gate to test_zxz_decomposer.py.
Fix test_all_octants_of_bloch_sphere_rotation in test_aba_decomposer.py:

Change the number of steps for axes from 6 to 5, so  (e.g., 1, 0.5, 0, -0.5, -1).

Update test_cnot_decomposer in test_decompositions.py:

We had seen this before. We randomly write out Rz(pi) or Rz(-pi).

Thanks for picking this up and resolving the bug!

Thanks! I did because I had seen the code, and it occurred to me that there may be a corner case we were not handling correctly. Which it turned out it was.

The windows python builds seem to be failing. Could this be an issue to do with rounding?

Yes, kind of, np's definition of atol is stricter than ours (1e-08 instead of 1e-07).


Merge the Code Base to Main

The base application is an empty activity with Junit 5 in the gradle file.

Added folders for sorting classes and mostly worked on Player class and DBConnector


tasktools choice function unnecessary

isn't it the same as rng.choice(options)?

Yes. I changed it.


[AvatarGroup] Can't specify component prop

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
component prop does not work for AvatarGroup.
Expected behavior 🤔
should be able to change the semantics of AvatarGroup.
Steps to reproduce 🕹
// still returning `div` with type error
<AvatarGroup component="ul">

Context 🔦
This issue is coming from https://github.com/mui/material-ui/issues/33993
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Might be fixed by https://github.com/mui/material-ui/pull/33994

Does #33994 fix it?  Otherwise I would like this issue


/block API returning different values after sometime

Not sure if this is a rosetta implementation issue or core cardano but seems like the block response is now returning different value then a while back.
BEFORE (I saved this a while back)
POST /block
    {
        "block": {
            "block_identifier": {
                "index" 5125864,
                "hash": "a69091c4c87dad7829c670490969b4c3909d7ffc02d30d7a23ecc637089577de"
            }
            "timestamp":<PHONE_NUMBER>000,
            "transactions": [],
            "metadata": {
                "createdBy": "ShelleyGenesis-7f72a1826ae3b279",
                "epochNo": 237,
                "size": 3,
                "slotNo": 17392425,
                "transactionsCount": 0
            }
        }
    }

But now the same block index has a different hash, timestamp and metadata.
AFTER
{
    "block": {
        "block_identifier": {
            "hash": "293d9d2eb6f82fb4456a7d82b283edaef03c51d1a34b1a634abaab7ac481a571",
            "index": 5125864
        },
        "metadata": {
            "createdBy": "Pool-5b0f169af28ad308",
            "epochNo": 237,
            "size": 3,
            "slotNo": 17392411,
            "transactionsCount": 0
        },
        "timestamp":<PHONE_NUMBER>000,
        "transactions": []
    }
}

I'm a bit confused, how is it possible that the same index has different values now, I was expecting this to not change over time.

Nevermind got an answer on Telegram here: https://t.me/CardanoDevelopersOfficial/31504
for future reference.


The "Group By" icon disappears from the resources view after installing both Azure Function extension and App Service extension

OS: Win10
App Service Extension Build Version: 20220729.1
Azure Function Extension Build Version: 20220729.3
VS Code Insider Build:

Repro Steps:

Install Azure Function extension in VS Code Insiders.
Install App Service extension in VS Code Insiders.
Navigate to Azure View.
Check whether the "Group By" icon shows in the resources view.

Expect:
The "Group By" icon shows in the resources view.

Actual:
The "Group By" icon disappears from the resources view.

More Info:

This issue does not reproduce if only install one extension (Azure Function or App Service).
This issue does not reproduce in VS Code.

Duplicate of #330


Code Coverage doesn't fail if coverage is 0%

We are instantiating JEST with code coverage. It successfully generates a usage report in the console which shows the coverage as 0%,but it still says PASSED!

JEST configuration is below
"jest": {
"collectCoverage": true,
"coverageDirectory": "../coverage",
"testPathIgnorePatterns": [
"/node_modules/"
],
"verbose": true,
"coverageThreshold": {
"global": {
"branches": 50,
"functions": 50,
"lines": 50,
"statements": 50
}
}
},

Please conform to the issue template and provide a downloadable repro


select Up, Down, Left and Right panes

right now its only prev/next pane, the same as tabs. Its enough for tabs, because tabs are one dimensional array.
But as far as panes are two dimensional feature, we need to navigate between them in all four sides: go to up/down/left/right pane.

I was going to suggest numbers when I found this - I don't use prev/next for tabs, and the Ctrl-Option[-Shift]-Tab shortcut to do so for panes is particularly awkward.
Cmd-N to choose a tab and Option-(numbers appear on panes)-N to choose a pane would be great though.
I'm not suggesting it instead of directions, but directions instead of tabbing, and by-numbers available for panes too would be :+1:.

I like the iTerm2 shortcuts:

Cmd+left arrow, Cmd+right arrow navigates among tabs. So does Cmd-{ and Cmd-}.
Cmd+number navigates directly to a tab.
Cmd+Option+Number navigates directly to a window.
Cmd+Option+Arrow keys navigate among split panes.
Cmd+] and Cmd+[ navigates among split panes in order of use.

source: https://www.iterm2.com/documentation-one-page.html

I think the last point is the most important regarding UX
Cmd+] and Cmd+[ navigates among split panes in order of use
Now we need to use
selectNextPane: 'Ctrl+Alt+Tab',
selectPreviousPane: 'Ctrl+Shift+Alt+Tab'

I don't know about others, but for me this is difficult.

I like how tmux does it, where there is a single shortcut to toggle between the latest 2 panes.

Just to add, under Windows 10, Ctrl + Alt + Tab is another alternative for Alt + Tab. It is a cross between Windows + Tab and Alt + Tab. It keeps the task switcher on the screen but does not include any ability to manage desktops. Ctrl+Alt+Tab.
So, for me under Windows 10 (version 1511 build 10586.679), Ctrl + Alt +Tab brings up the task switcher and does not navigate between split panes.

Ctrl+Alt+Tab and Ctrl+Shift+Alt+Tab do not work under Gnome, as they're assigned by the window manager for switching panels.
If anyone is interested in releasing theirs to use Hyper, run dconf-editor and disable these two keybindings by overriding the defaults and configuring []:

I'm currently trying to achieve this navigation.
I think that the best keybindings to navigate are Ctrl+Alt+<Arrow> if we keep Ctrl+Alt+Tabfor moveNextPane() (Discussed here https://github.com/zeit/hyper/pull/1113)
This feature of navigation should be for example, starting from pane1 :
pane1 ⬇  pane2 ⬇  pane3 ➡  pane4 ➡  pane5 ➡  pane7 ⬆  pane6 ⬅  pane5 ⬅  pane1

We must keep a virtual position of a "focusPoint" in order to have 'pane5➡pane7' move because focus was on pane4 before pane5.
The rules of moving this point of focus would be:

When a pane is directly chosen (with a mouse click, for example), this focusPoint is set to the center of this pane. Same if a resize occurs. (Maybe after a delay too)
When a transition is made along x-axis

x-coord of focusPoint is set to the center of the next pane.
y-coord of foucsPoint is set to the center of the next pane ONLY if next pane border is totally included in previous pane border ('pane2⬇pane3' but not 'pane4➡pane5')

Same behavior along y-axis
Next pane chosen is the first intersected by moving this point of focus on the desired direction.

If point of focus intersect 2 panes (when 'pane2⬇' for exemple), priority is left or top pane.

For previous sequence,  point of focus is moving like this:

To achieve this, if will be simpler to have absolute frame (origin and size) of each TermGroup. These positions will be expressed in term of proportion. RootTermGroup's frame will be {x: 0, y: 0, w: 1, h: 1} and pane4 {x: 0.166, y: 0.666, w: 0.166, h: 0.333} in previous example.
As discussed here https://github.com/zeit/hyper/issues/1143, should it be a (core) plugin ? Even adding an absolute position of each TermGroup (which could be eventually useful for other features ?)

I'm currently trying to achieve this navigation.
I think that the best keybindings to navigate are Ctrl+Alt+<Arrow> if we keep Ctrl+Alt+Tabfor moveNextPane() (Discussed here https://github.com/zeit/hyper/pull/1113)
This feature of navigation should be for example, starting from pane1 :
pane1 ⬇  pane2 ⬇  pane3 ➡  pane4 ➡  pane5 ➡  pane7 ⬆  pane6 ⬅  pane5 ⬅  pane1

We must keep a virtual position of a "focusPoint" in order to have 'pane5➡pane7' move because focus was on pane4 before pane5.
The rules of moving this point of focus would be:

When a pane is directly chosen (with a mouse click, for example), this focusPoint is set to the center of this pane. Same if a resize occurs. (Maybe after a delay too)
When a transition is made along x-axis

x-coord of focusPoint is set to the center of the next pane.
y-coord of foucsPoint is set to the center of the next pane ONLY if next pane border is totally included in previous pane border ('pane2⬇pane3' but not 'pane4➡pane5')

Same behavior along y-axis
Next pane chosen is the first intersected by moving this point of focus on the desired direction.

If point of focus intersect 2 panes (when 'pane2⬇' for exemple), priority is left or top pane.

For previous sequence,  point of focus is moving like this:

To achieve this, if will be simpler to have absolute frame (origin and size) of each TermGroup. These positions will be expressed in term of proportion. RootTermGroup's frame will be {x: 0, y: 0, w: 1, h: 1} and pane4 {x: 0.166, y: 0.666, w: 0.166, h: 0.333} in previous example.
As discussed here https://github.com/zeit/hyper/issues/1143, should it be a (core) plugin ? Even adding an absolute position of each TermGroup (which could be eventually useful for other features ?)

@matheuss @ekmartin @rauchg @CodeTheory @albinekb : can one of you, give me an advice where all of this should take place ? plugin, future core-plugin, PR...

Don't forget me ? Huh

Ouuups :) your advice is really welcome too, of course 😄

Would :heart: to see this implemented. Please consider making the keybindings configurable :tada:

Just went through this thread. I think indeed, #1295 is far more efficient.

And maybe easier to develop 😛

Haha, definitely :D

Made with a plugin : https://github.com/chabou/hyper-pane
Feedback warmly welcome

@chabou thanks for this

so, this issue can be closed


chore: delete env and url from intialize xp

Change description
Improve RestQA init experience by using local env as the default configuration.
Type of change

[ ] Bug fix (fixes an issue)
[x] New feature (adds functionality)

Checklists
Development

[x] Lint rules pass locally
[ ] Application changes have been tested thoroughly
[x] Automated tests covering modified code pass

Security

[x] Security impact of change has been considered
[x] Code follows project security practices and guidelines

Code review

[x] Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
[ ] Changes have been reviewed by at least one other contributor

Let's see how the CI works with that 👁👁

CI passed! @olivierodo Note that I didn't find:

documentation about this command
no e2e cli test (bats)

Let me know if you want to keep it like this or introduce them?

You are right Bats can't cover this test because the command restqa init requires some input from the users but bats has a hard time to pass input to the command.
However we might be able to test the restqa init -y

Next:

Test that Initialize should ask for name and description if a pakcage.json doesn't exists (extract json package fetch)
Add bast test as @olivierodo Mentionned

@olivierodo I create this task and hope to make it separately.

@olivierodo friendly ping!

I'll merge it and create another pr for making the description optional.


Multi collection ACID transactions

Currently, there is no support for multi collection ACID transactions. In contrast, I believe Mongo DB allows this. There are use cases that require updating multiple collections simultaneously. Providing this functionality will bring better feature parity with Mongo DB. Please note that this request is for SQL API - not for Mongo DB API.

This is not specific to the Cosmos DB .NET SDK. Please post the feature request here: https://feedback.azure.com/d365community/forum/3002b3be-0d25-ec11-b6e6-000d3a4f0858


Disable THP when bootstrap

There are many customers enable THP and cause many problem. we should disable it
refer: https://www.percona.com/blog/2019/03/06/settling-the-myth-of-transparent-hugepages-for-databases/

Hi @liubo0127 please make sure THP is disable or always disable by:
echo never > /sys/kernel/mm/transparent_hugepage/enable
echo never > /sys/kernel/mm/transparent_hugepage/defrag

before deploy, no reboot need


When zoomed in: When dragging the playhead it is lagging behind

See screencast: When having zoomed in the timeline and dragging the playhead back or forward the playhead is lagging behind. I guess this is a result of the centering feature of the zoom function.
Annotation Tool Dragging playhead.mp4.zip

Bug still exists, but only when dragging the playhead 'out' of the actually shown part of the video. This is acceptable. Therefore, I close this issue.


pomerium: 0.22.2 -> 0.23.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pomerium is: Authenticating reverse proxy
meta.homepage for pomerium is: https://pomerium.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.3 with grep in /nix/store/c8c0mbhqj9n456cl65kfynnj5wpmy3vg-pomerium-0.22.3
found 0.22.3 in filename of file in /nix/store/c8c0mbhqj9n456cl65kfynnj5wpmy3vg-pomerium-0.22.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pomerium

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c8c0mbhqj9n456cl65kfynnj5wpmy3vg-pomerium-0.22.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pomerium https://github.com/r-ryantm/nixpkgs/archive/a7b651faf7031f8a9ba7916ae4ad621c6e382f80.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c8c0mbhqj9n456cl65kfynnj5wpmy3vg-pomerium-0.22.3
ls -la /nix/store/c8c0mbhqj9n456cl65kfynnj5wpmy3vg-pomerium-0.22.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pomerium

Maintainer pings
cc @lukegb for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for pomerium is: Authenticating reverse proxy
meta.homepage for pomerium is: https://pomerium.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.23.0 with grep in /nix/store/jyac6p9bxd95jmqcwvq4skcrc06qq9fl-pomerium-0.23.0
found 0.23.0 in filename of file in /nix/store/jyac6p9bxd95jmqcwvq4skcrc06qq9fl-pomerium-0.23.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pomerium

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jyac6p9bxd95jmqcwvq4skcrc06qq9fl-pomerium-0.23.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pomerium https://github.com/r-ryantm/nixpkgs/archive/3fd48a56c76bd2b75900ef7575287efd03ab1364.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jyac6p9bxd95jmqcwvq4skcrc06qq9fl-pomerium-0.23.0
ls -la /nix/store/jyac6p9bxd95jmqcwvq4skcrc06qq9fl-pomerium-0.23.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pomerium

Maintainer pings
cc @lukegb for testing.

@ofborg eval


Update profiles.json

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

Also check out https://xprofile.hellofaizan.me/


Feature: Add zip support

Can you add zip support using https://github.com/moncefplastin07/deno-zip ?
Thanks.

@arnu515
I guess I'll have time to deal with it in a week.
if you want, I am very happy to merge your pull request.

@zfx I can create a PR but I won't be able to write tests.
-------- Original Message --------
On 18 Apr 2022, 15:48, zfx wrote:

@.***(https://github.com/arnu515)
I guess I'll have time to deal with it in a week.
if you want, I am very happy to merge your pull request.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@arnu515 ok

@arnu515
v1.2.3 has bug

https://github.com/moncefplastin07/deno-zip/commit/30f0f126f05b7a9f14952d43614f3f44ffa6f4b0
Fixed, but the author did not release 1.2.4

I'll send the PR once the author updates the package

Any update ?

Any update ?

Can you submit a pull request to support zip?

Landed on 0.4.8


Fix manifest icons

PR for #1567.
To fix the issue, I grabbed a copy of the icon from the brand repository and generated a new manifest file using the Web App Manifest Generator. The icons have been run through imageOptim and the manifest theme and background colors are based on the icon and example app background color.
In addition to this, I added the favicon via a rel attribute as suggested by the W3C.
Happy to make any changes 😄

Coverage remained the same at 99.24% when pulling 638df38b799df77d9c5eca93a6c4fcf799031d1c on samit4me:fix-manifest-icons into d898c43e207fac4cdc9cd8895ed9c96b08d9b74b on react-boilerplate:dev.

Coverage remained the same at 99.24% when pulling 680b4f70a717f5e61039819ab166d20c0daab0ed on samit4me:fix-manifest-icons into bed2126f74e4e9374d43709fdc5ab835afa4cc12 on react-boilerplate:dev.

Coverage remained the same at 99.24% when pulling 680b4f70a717f5e61039819ab166d20c0daab0ed on samit4me:fix-manifest-icons into bed2126f74e4e9374d43709fdc5ab835afa4cc12 on react-boilerplate:dev.

Coverage remained the same at 99.24% when pulling 9c76b2ec778c84d11bdc70e6573b047af3608f25 on samit4me:fix-manifest-icons into 333d1515d024c24f9952f0201c0ba14bcb78c216 on react-boilerplate:dev.


#160 - Page.getPlainText broken - PlainTextConverter struggles to discriminate candidate methods and ends in 'VisitorException'

Fixes this issue by commenting out unused/empty candidate method public void visit(WtNode n).
Un-ignores and adapts test cases in PageTest. This way, testGetPlainText can now work correctly. No more ignored tests \o/.
Adds minor fix in PlainTextConverter to parse/handle standalone line breaks strings correctly.
Adapts demo data to the version from 2010 (initial DB import had "*" and multi-line breaks). I screwed them up slightly in June 2018 when bringing #2 to master.
Simplifies 2/3 PlainTextConverter constructors to reduce duplicate code.

Moreover, this kind of fixes #161, as no other problems remain once this commit is merged.
Please, @reckart or @daxenberger review and merge this PR.
Feedback by @tgalery / @rzo1 also very welcome.

@rzo1 Works on Linux and MacOS, but you might be right that on Windows the current demo data string is incomplete with respect to \n\r.

Thanks to support by @rzo1, the tests should now pass on all major platforms.
FYI: @reckart / @daxenberger / @tgalery

@rzo1 @mawiesne I try to set up a second Jenkins job that uses Windows. We have a Windows build node, but I haven't tried so far to set up two different PR builder jobs for the same project. Normally, I do the cross-OS builds after a PR has been merged.

@reckart sounds reasonable. In this context: Could you check why the current build job always reports "... vs. master 0%". Seems a bit odd to me, as the code on the master should produce around 20% coverage atm.

@mawiesne thanks so much for this PR, I just got back from holidays and was dreading  having to fix this, so really appreciate the work. I had a few comments, but they are mostly questions really. Let me know if you need help with anything else and probably after this gets merged we would be in a position to spin a release \o/ !!!

@tgalery Yw, hope you enjoyed holidays.
My focus was on pushing towards a release; that's why I tackled some of the open issues, be it in the issue tracker (existing) or in the code base (sleeping/waiting for improvements).
I'm really looking fwd for 1.2.0 being released. See #158 and/or comment on open issues we need to address from your perspective.


[GURPS] 2.10.6

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

ENHANCEMENTS: Updated layout for tools Damage to Objects and Repairs. Added option to select pounds or kiligrams for Damage to Objects.
NEW: Added Stealth vs Perception tool.

Character Sheet Info Roll20 Internal Use only.


sys/config: Add CONF_FLOAT

CONF_FLOAT was defined as a type but not implemented. This change adds CONF_FLOAT.

@kasjer or @sjanc Any chance for a quick review on this one? :-)


Tabs visual style changes when moving Terminal window to another display

Windows Terminal version
1.18.3181.0
Windows build number
10.0.22621.0
Other Software
No response
Steps to reproduce
I have two monitors, monitor 1 2560x1440 (125% scale, landscape) and monitor 2 1080x1920 (100% scale, portrait). Last few versions of Terminal the tabs are rendered with square bottom corners on the monitor 1. If I move the Terminal window to the monitor 2 the tabs are immediately rendered with the round bottom corners. The top corners of the tabs are always round.
Expected Behavior
The visual style of the tabs should be consistent with the look and feel of Windows 11 (like windows explorer tabs) regardless of the chosen display.
Actual Behavior
The visual style of the tabs is inconsistent when using multiple displays.

It seems the bug disappears when  Tab width mode setting is set to Equal.

This is super wacky, and great eye for catching this. You're right, it is definitely weird on equal tab width mode. And it's not even always!

I'd have to inspect my settings closer to understand why some profile's tabs do this, and others don't?

ho god this is horrifying, it seems to be related to the title length 😨

title cm: round corners
title cmd: straight corners
title cmdc: straight corners
title cmdcm: round corners

what
what


Proposal to add 'verify card' and 'recover card' sections to boltcard specifications

I am requesting the boltcard specifications are enhanced with new 'verify card' and 'recover card' sections.
I believe this would greatly enhance the usability and image of boltcards as well as make boltcards a leading example of sound and practical use of NTAG NXP 424 NFC cards.
In practice, such additional specifications build on my proposal to alter the number of specification recognised card states from two to four (recognising confirmed/unconfirmed of both set/reset card states). The two additional states require additional record keeping of key change attempts until a card key state (set or reset) has been confirmed. Example at https://github.com/NicolasDorier/boltcards-plugin/issues/6#issuecomment-2212384416.
In the BTCPay implementation, two boltcard services exist to users and admin that can alter keys. These are 'reset card to blank' and 'set card to use a pull payment'. The lack of confirmation of changes and lack of complete record keeping makes it very easy to brick boltcards.
There should be a two additional implemented boltcard services: 'verify card' and 'recover card'. They should also form part of the specifications. In combination with recognition of four card states and keeping temporary records, it would provide clear direction to users, lower user frustration and lower the need to engage with admin services. This would also inspire confidence.
For example the bolt card mobile app could state: "Set or reset has failed. Please verify card with your service and take recovery action if necessary". By making 'verify card' and 'recover card' an obligatory part of specification, apps can provide practical recommendations.
As an alternative to using the term 'verify card', an enhanced 'check balance' service could provide the same service under  the 'check balance' label instead.
The outcome of the 'verify card' service in an implementation to be one of:

"Card cannot be used as a boltcard"
"Card is reset"
"Card is set and unknown to us. It cannot be used with our service without being reset by another service"
"Card is known to us, can be reset and is in use with us with a balance of .... Link at ...."
"Card is known to us and cannot be used until using 'reset card' or 'recover card' with us." If there is a balance then add: "You should not reset your card until you have withdrawn remaining balance of ... using link ... You can also use a different reset boltcard."
"Card is known to us and cannot be used without attempting 'reset card' or 'recover card' with us (which may not be successful)." If there is a balance then add: "You should not attempt to reset your card until you have withdrawn remaining balance of ... using link ... You can also use a different reset boltcard."
"Card is known to us, cannot be reset, cannot be used with us and cannot be used elsewhere (the card is 'bricked')". If there is a known balance then add: "You can withdraw balance of ... from link... or use another boltcard that is in a reset state".

The outcome of the 'recover card' service in an implementation to be one of:

"Card cannot be used as a boltcard"
"Your card is already in a reset state. It can be used with this service"
"Your card is in use with another service and cannot be used with our service unless reset by the other service"
"Your card does not need recovery. If you want to reset your card then please choose 'reset card', which will be successful". If there is a balance then add: "Before reset you shoud withdraw your remaining balance of ... using link ..."
"Your card has been successfully recovered to its configured service."
"Your card cannot be recovered to its previous state but can be successfully reset. You can use your card elsewhere or use it here again when reset". If there is a balance then add: "You should not reset your card until you have withdrawn remaining balance of ... using link ... You can also use a different reset boltcard".
"Your card cannot be reset and cannot be used with this service or another service (the card is 'bricked')". If there is a known remaining balance then add: "You can withdraw remaining funds of ... with link .... You can also use a different reset boltcard".

I am closing this issue because there is an algorithmic issue with the bolt-nfc-crearor app whose solution is likely to dramatically reduce the incidence of bricked cards.
After proposed fixes, if a user is having problems with a card being set or reset, then as long as a user does not abandon using the app before notification of success, then a card should not become bricked.
Please see Fault in key change algorithm leading to bricked cards.
It is possible this issue will need to be reopened if too many users do not properly complete setting or resetting boltcards with the bolt-nfc-creator-app.


Plugin/viewerpreferences

Hey, if you look at the test logs you'll see the tests fail because they don't match the reference PDFs. You'll need to make a reference PDF for each test with a different file name.

Hi James,
i did create the needed reference-files.
https://github.com/arasabbasi/jsPDF/tree/plugin/viewerpreferences/tests/viewerpreferences/reference
But somehow my plugin isnt working in the test engine. If I use the same code on my PC it works without problems. And in the testing suite I dont see any errors as if the code is loaded but it doesnt put the generated text into the pdf.

I think it might be because you've used FitWindow.pdf multiple times and they're not identical?

Looks like it's just Internet Explorer. Maybe there's some JS that IE doesn't like?

[ ] IE 11.0.0 (Windows 10 0.0.0) viewerpreferences plugin HideToolbar FAILED
[ ] IE 11.0.0 (Windows 10 0.0.0) viewerpreferences plugin HideMenubar FAILED
[ ] IE 11.0.0 (Windows 10 0.0.0) viewerpreferences plugin FitWindow FAILED
[ ] IE 11.0.0 (Windows 10 0.0.0) viewerpreferences plugin ViewArea MediaBox FAILED
[ ] IE 11.0.0 (Windows 10 0.0.0) viewerpreferences plugin PrintPageRange FAILED

Dude... I changed everything. I really dont get it. Maybe I hacked some next level 💩.
Maybe there is some issue with testing it in saucelab?
https://github.com/MrRio/jsPDF/blob/master/tests/acroform/standard.spec.js
  // @TODO: Raise ticket with AcroForms developer about IE and other issues
  if (navigator.userAgent.indexOf('Trident') !== -1) {
    console.warn('Skipping IE for AcroForms')
    return
  }

Why do you disabled testin for AcroForms?

Haha. Ok, I've done a diff on the output that IE is getting:

I know. I am using the travis-log intensively. But the problem is that I dont get any hints why it is not working. I tested it with the IE11 on my PC and it does work.

I cant bugfix it if there is no bug :/

Can you get the test to run locally with IE?

The local test runner currently only defines Chrome/Firefox because I'm on a Mac, I'd need to boot up a Windows VM but I can't do that at the moment.

It passes!

Finally!!!
The code got a little bit unreadable...  Uncle Bob would be sad.
Let me activate the other tests... But it should pass again... then I can close this chapter of my life...

Sorry -- one last request (if you still have the will to live 😂). Can you document all the options and see what it looks like in npm run generate-docs.

Nice...
As a byproduct the viewerpreferences-settings are now per jsPDF instance and not shared globally by every jsPDF instance.
I guess there is a scoping problem.

I added a documentation, but i dont know if it works. I have no npm on my small netbook...
I develop right now just with notepad+ and chrome browser xD

It seems to add 'viewerpreferences' and 'viewerPreferences' to the docs (with different capitalisation)

I hope I removed the right comments...

I've updated the docs a bit and merged that plugin in.


Rich editor configuration per field

There is some things that could be added to rich text:

add support for different configurations
needs a way to unregister some plugins globally (there is only hooks for enabling a hallojs plugin)
make default whitelister configurable, for example disable "a" tag globally.

Example of rich text editor configuration for a field
# Simple TextArea, where we nee just a few options on editor
class SimpleDbWhitelister(WagtailDbWhitelister):
    element_rules = {
        '[document]': allow_without_attributes,
        'a': attribute_rule({'href': check_url}),
        'p': allow_without_attributes,
        'b': allow_without_attributes,
        'i': allow_without_attributes,
        'u': allow_without_attributes,
    }

class SimpleRichTexArea(WagtailRichTextArea):
    hallo_plugins = {
        'halloheadings': {
            'formatBlocks': []
        },
        'halloformat': {
            'formattings': {
                "bold": True,
                "italic": True,
            },
        },
        'hallolists': {
            "lists": {
                "ordered": False,
                "unordered": False
            }
        },
        'hallowagtaillink': {},
        'hallorequireparagraphs': {},
        'hallocleanhtml': {
            'format': False,
            'removeTags': ['span', 'div', 'table', 'strong'],
            'allowedTags': ['a', 'p', 'i', 'b', 'u'],
            'removeAttrs': ['class', 'style', 'id'],
            'allowedAttributes': [
                ["a", ['href', 'target', 'data-id', 'data-linktype']]
            ]
        }
    }

    def render_js_init(self, id_, name, value):
        return "makeRichTextEditable({0}, {1});".format(
            json.dumps(id_),
            json.dumps(self.hallo_plugins)
        )

    def value_from_datadict(self, data, files, name):
        original_value = super(SimpleRichTexArea, self).value_from_datadict(data, files, name)
        if original_value is None:
            return None
        return SimpleDbWhitelister.clean(original_value)

Some changes on page-editor.js
function makeRichTextEditable(id, plugins) {
   var instanceHalloPlugins = plugins || halloPlugins;
....
}

Globally disable a hallo plugin on editor
function unRegisterHalloPlugin(name) {
    if (!$.inArray(name, disabledHalloPlugins)) {
        disabledHalloPlugins.push(name);
    }
    if ($.inArray(name, halloPlugins)) {
        delete halloPlugins[name];
    }
}

Yes this is something I'd really like to be able to do too. At the very least, to be able to configure the global list of plugins. (For example, I'd like to remove the ability to add images and embeds to rich text areas, as I'm going to be providing separate fields inside StreamField blocks for adding these so I can better control their display.)

Wow, awesome, is the better wat for customize the richtextfield editor for the content. Thank you.

I mentioned wanting something like this in the Google Group. Now with StreamFields, being able to provide a stripped down editor for RichTextFields is important so editors will use the fields provided and not use a RichTextField for content that should be in a provided field.

+1
The ability to disable things like images and embeds would be great in combination with StreamField

:+1:

+1

+1 We need this functionality in order to provide a stripped down editor functionality for things like links in photo captions where we do not want the author to be able to add anything else but an anchor.

+1

+1. Has anyone found good ways to deal with this at the moment?

I believe #2697 (now in master) should address this. Haven't had chance to try it out myself, and it still needs docs, but if anyone's up for trying it out and reporting back, that would be much appreciated!

Now implemented in #3736.
(To correct myself above: #2697 only addresses this in a very basic way - you'd need to set up a configuration in WAGTAILADMIN_RICH_TEXT_EDITORS for each combination of features - and only for editors that recognise configuration options passed there, which hallo.js didn't until I implemented that in #3736)

Completed in #3736


Race condition of port calculation on delay exporting.

Two different ports may be assigned to service1 and service2 respectively.
<dubbo protocol="dubbo" port="-1"/>

<dubbo:service delay="5000" interface="service1"/>
<dubbo:service delay="5000" interface="service2"/>

3.0.11 and later


Demo mode notice

Banner at page top
Click to delete all the sample users
Confirmation before delete
Add "demo mode" flag
Should work with existing communities (add a migration to check if there are > 20 fake users still existing)
Admins only
Don't delete any sample users that are tied to non-deleteable records (not sure if this is possible, maybe moot)
If this happens, provide a brief report

Originally created by Tom Smyth at 2018-12-26 16:20, migrated from redmine-#9240

Tracker changed from Bug to Feature

By Tom Smyth at 2019-04-24 12:37

Follows Feature #5315: Community signup added

By Tom Smyth at 2018-12-26 21:21


Challenge cleanup improvements

I've added a test for the happy path of running cleanup when the Challenge has a DeletionTimestamp and the finalizer is present.
I'll try and improve things further in later PRs. Here are some of the problems I see:

[ ] Challenge Finalizer is always removed, regardless of whether solver.cleanup succeeds
[ ] Challenge Finalizer is assumed to be the only (first) finalizer (breaks if external controllers add their own finalizers)
[ ] Duplicate code for calling  Update and UpdateStatus. These can both be called in the deferred function at the top of Sync function, so as to reduce the complexity of the addFinalizer and handleFinalizer functions and their tests.

/kind cleanup
NONE

I will look at this on Monday, but I really don't understand where this comes from
This optimistic locking error should only ever occur on updates? https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L611

/test pull-cert-manager-make-e2e-v1-23

/test pull-cert-manager-e2e-v1-23

Thanks @irbekrm
Yes, I'll work on those finalizer bugs in another PR.
/unhold


Catalog APIService Object Failed

Bug Report
What happened:
Catalog APIService object failed (FailedDiscoveryCheck)
What you expected to happen:
Catalog APIService object should not fail.
How to reproduce it (as minimally and precisely as possible):
cd charts/catalog
helm install . --name catalog --namespace catalog
kubectl describe apiservice v1beta1.servicecatalog.k8s.io
Anything else we need to know?:
Name:         v1beta1.servicecatalog.k8s.io
Namespace:
Labels:
Annotations:
API Version:  apiregistration.k8s.io/v1
Kind:         APIService
Metadata:
Creation Timestamp:  2019-06-03T09:51:47Z
Resource Version:    354707
Self Link:           /apis/apiregistration.k8s.io/v1/apiservices/v1beta1.servicecatalog.k8s.io
UID:                 33aa59bb-85e5-11e9-8570-005056a591de
Spec:
Ca Bundle:               LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM5akNDQWQ2Z0F3SUJBZ0lRWnVOejlKSDV2SWxuVC9rNm9wT1JWVEFOQmdrcWhraUc5dzBCQVFzRkFEQVYKTVJNd0VRWURWUVFERXdwemRtTXRZMkYwTFdOaE1CNFhEVEU1TURZd016QTVOVE0wTkZvWERUSTVNRFV6TVRBNQpOVE0wTkZvd0ZURVRNQkVHQTFVRUF4TUtjM1pqTFdOaGRDMWpZVENDQVNJd0RRWUpLb1pJaHZjTkFRRUJCUUFECmdnRVBBRENDQVFvQ2dnRUJBTEJ0MXZCWkxxaE1aYWFMRWRZNmVjWGpwY2JXVmNOOWduZEc5L1FwZFVGVXM1eUEKR0lrbi95MTcvaWRmbHBqS2pYZDkrYzI2NmVmTTN1R0ZnNVRjczVETXFvWi81S3NLNVorVHVFd1cxeWdxWW1oagplRGV1WlhZWWxSNEFjbkpkQnpFV3RwcnY0eHI1V1hrNUdWTHMvVXRaOWpNSUFoY09uVU1aVnNEa0crUFk1ZU9hCmsydTdIYUs4clBKRldOYTYxemd3YS94c3N0S0xSbkFENlRFbnJWOEVuT3czMUFhWFZqaWN3WS95VGJqUzNyQUQKdy8vM096VG5scEhlaUFLYnM4MUZKdjRvbHdTM2Mrb1l5bkNpQm1DNmZzQmV0aHVHYkRzaDhqa2s0MXhJeUhNMwptNkVDanpxNmJXZFFqb3owaGh3WU5IZmtCbXAvTFVaRER3RkJYUE1DQXdFQUFhTkNNRUF3RGdZRFZSMFBBUUgvCkJBUURBZ0trTUIwR0ExVWRKUVFXTUJRR0NDc0dBUVVGQndNQkJnZ3JCZ0VGQlFjREFqQVBCZ05WSFJNQkFmOEUKQlRBREFRSC9NQTBHQ1NxR1NJYjNEUUVCQ3dVQUE0SUJBUUIzMHhBbjdrQ25ydE52T0xDV0J4MS9YRkN3NFF5UgplWGxQc3BDSzY0Q3Uyd1RtYzhMc29vMVFoNXVMb3VFamcyRnhBc0NTSzdZTnJjckJ3QzhhQkVIdXkxUE5qT081CmVVRHBaUzNrNXNCZUxCQ0Q3WnBHWjRhb3owc3BqdWVPR2pqcFlIa1R4clNMK3FMTXNLTGY3UncwcnRVeEwyc1UKZjFhdzlFY3BldnJsUS9xVUkvSC9VMVNRN1FSaDMwV3NMQzdxYU83ZEhIdDF2ZHZsVDVoYXVtYzloZUZSdXV1UgpwS25BeGo3VUIwaFl2Y2NYcnR2eHVJT1VTN04wWS9XV0pWSmpPL2RhNk5tQnlIZzlDdkljcFR4VEs1NktUaU5XCi9WK3ZrSW5qVWdyZnUwVFU2WDZpbktjRzk5VGRiVnBldzQyTUc4Z0RpU0s3WFVmLy82MDYxUGl2Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
Group:                   servicecatalog.k8s.io
Group Priority Minimum:  10000
Service:
Name:            catalog-catalog-apiserver
Namespace:       catalog
Version:           v1beta1
Version Priority:  20
Status:
Conditions:
Last Transition Time:  2019-06-03T09:51:47Z
Message:               no response from https://<IP_ADDRESS>:443: Get https://<IP_ADDRESS>:443: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Reason:                FailedDiscoveryCheck
Status:                False
Type:                  Available
Events:
Note:- I alreay have setup http_proxy and https_proxy in /etc/environment. also catalog-catalog-apiserver service and relater pods with this service are running fine.
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
service-catalog version:
Cloud provider or hardware configuration: Bare Metal
Do you have api aggregation enabled? Yes

Do you see the configmap in kube-system? Yes
Does it have all the necessary fields? Yes

kubectl get cm -n kube-system extension-apiserver-authentication -o yaml and look for requestheader-XXX fields

Install tools:

Did you use helm? Yes
What were the helm arguments? Did you --set any extra values? No

Are you trying to use ALPHA features? Did you enable them?

The detailed discussion was on our Service Catalog channel on k8s slack workspace, see: https://kubernetes.slack.com/archives/C232SF3TK/p1559642796001100
TL;DR;
The problem is the same as already reported some time on the k8s repo: https://github.com/kubernetes/kubernetes/issues/66231
This issue is not related directly to the Service Catalog, as you also confirmed that with the k8s metrics-server you also ran in that issue.
The root cause could be a misconfigured network layer.

this issues is fixed now. issue was with the kube-apiserver was running with http proxies. removing http proxies and no proxy from env of kube-apiserver fixed this issue.
but still catalog controller manager is failing with these errors:
1 round_trippers.go:438] GET https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s  in 32000 milliseconds
I0618 09:08:35.426432       1 round_trippers.go:444] Response Headers:
E0618 09:08:35.426462       1 controller_manager.go:311] Failed to get supported resources from server: Get https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
I0618 09:08:35.426615       1 controller_manager.go:306] Created client for API discovery
I0618 09:08:35.426716       1 round_trippers.go:419] curl -k -v -XGET  -H "Accept: application/json, /" -H "User-Agent: service-catalog/v0.2.1 (linux/amd64) kubernetes/6c6a49d/service-catalog-controller-discovery" -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJzZXJ2aWNlLWNhdGFsb2ctY29udHJvbGxlci1tYW5hZ2VyLXRva2VuLXpmaGNiIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6InNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJhNTdmMTgwZC05MWE1LTExZTktYmE1YS0wMDUwNTZhNWVmYjQiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06c2VydmljZS1jYXRhbG9nLWNvbnRyb2xsZXItbWFuYWdlciJ9.HNTDRl9Nw2UgKfp6nZzCafO_I4NDGRb1uCjNIUEQFr_KtMxdE53EAj9JKoYZEQwNqDCH8StJrnSVvKdmp0bXsYHoxnPWvX7l9k12l82XnhE29wijIcpcE8rCX_KE9mtZoDlpKyG2ngeDNOmv520Rsw87HO8ytMDGlATScVhkY5n9VpzcKw2AIe24UbFSeziXnhp5sd1SMvBpIbya2z9CQ4LuhWAfzx6RbgLiKvn-vsPrJnX200voVDEs0vsGJ0nQTXmcP5_croawu51QHmr4S0-TSGQjW6gCGOl9MMkBI6Ur7gAaxLnv_Ao6Pk7Z14iLye6Ub4USf04wI45Ft3Es5g" 'https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s'
I0618 09:09:07.426865       1 round_trippers.go:438] GET https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s  in 32000 milliseconds
I0618 09:09:07.426899       1 round_trippers.go:444] Response Headers:
E0618 09:09:07.427120       1 controller_manager.go:311] Failed to get supported resources from server: Get https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
F0618 09:09:07.427222       1 controller_manager.go:236] error running controllers: failed to get api versions from server: "timed out waiting for the condition", "Get https://<IP_ADDRESS>:443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
where <IP_ADDRESS> is the CLUSTERIP of the kubernetes service.
also vm running with these pods gone too slow. is there any performance impact with service catalog with existing K8S cluster ??
These are the logs of kube-apiserver:
Trace[2007787961]: [23m59.116296457s] [23m59.114330668s] Transformed response object
E0618 09:05:13.750206       1 controller.go:111] loading OpenAPI spec for "v1beta1.servicecatalog.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: request timed out, Header: map[]
I0618 09:05:13.750230       1 controller.go:119] OpenAPI AggregationController: action for item v1beta1.servicecatalog.k8s.io: Rate Limited Requeue.
E0618 09:05:32.967096       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E0618 09:06:34.979867       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
I0618 09:07:13.750376       1 controller.go:105] OpenAPI AggregationController: Processing item v1beta1.servicecatalog.k8s.io
E0618 09:07:36.991287       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
I0618 09:08:09.770424       1 trace.go:76] Trace[111176043]: "Get /api/v1/namespaces/kube-system/pods/catalog-catalog-controller-manager-5c5fb5d8f6-8f8jc/log" (started: 2019-06-18 09:06:06.927204232 +0000 UTC m=+11941.486482605) (total time: 2m2.843179696s):
Trace[111176043]: [2m2.843177011s] [2m2.841889191s] Transformed response object
E0618 09:08:13.750551       1 controller.go:111] loading OpenAPI spec for "v1beta1.servicecatalog.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: request timed out, Header: map[]
I0618 09:08:13.750582       1 controller.go:119] OpenAPI AggregationController: action for item v1beta1.servicecatalog.k8s.io: Rate Limited Requeue.
E0618 09:08:39.003511       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
I0618 09:09:13.750724       1 controller.go:105] OpenAPI AggregationController: Processing item v1beta1.servicecatalog.k8s.io
E0618 09:09:41.017192       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: context deadline exceeded
E0618 09:10:13.750889       1 controller.go:111] loading OpenAPI spec for "v1beta1.servicecatalog.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: request timed out, Header: map[]
I0618 09:10:13.750916       1 controller.go:119] OpenAPI AggregationController: action for item v1beta1.servicecatalog.k8s.io: Rate Limited Requeue.
E0618 09:10:43.028793       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0618 09:11:45.041314       1 memcache.go:135] couldn't get resource list for servicecatalog.k8s.io/v1beta1: Get https://[::1]:6443/apis/servicecatalog.k8s.io/v1beta1?timeout=32s: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
but catalog apiserver is running fine.
Any thoughts and suggestions on this would be much appreciated.

Ok, so it looks like the same issue that you had for api-server. So right probably the API Server can reach the Pod but Pods are not able to reach the API Server.
Quick illustration:

so the question is if you API Server is able to reach the Pod from the nodes?

Ok, so it looks like the same issue that you had for api-server. So right probably the API Server can reach the Pod but Pods are not able to reach the API Server.
Quick illustration:

so the question is if you API Server is able to reach the Pod from the nodes?

but catalog apiserver pod is running fine only controller manager is failing. I'm not able to understand why kube-api server is not accessible from catalog controller manager pod. is there any way to debug this issue ?? also master node became too slow. is it impacting performance somewhere ??

In Kyma we are doing Service Management using the Service Catalog. We do not encounter any performance issue with it.
In our case, we just create clusters using the GKE or AKS. In such setup, everything is working. Previously we also used the acs-enging to create clusters that were managed by us. And in such scenario, it also worked.
IMO it's still sth with the network between master and worker nodes.
And about the performence, it could be because you still have some errors with registering the service catalog api-server into k8s.
You can check if you are able to deploy the sample-api-server and use registered kind by generated client set.

In Kyma we are doing Service Management using the Service Catalog. We do not encounter any performance issue with it.
In our case, we just create clusters using the GKE or AKS. In such setup, everything is working. Previously we also used the acs-enging to create clusters that were managed by us. And in such scenario, it also worked.
IMO it's still sth with the network between master and worker nodes.
And about the performence, it could be because you still have some errors with registering the service catalog api-server into k8s.
You can check if you are able to deploy the sample-api-server and use registered kind by generated client set.

can you please suggest is there any way that i can make sure catalog apiserver is registered with kube-apiserver ??

#https://github.com/kubernetes/kubernetes/issues/56430

This issue is fixed now by enabling hostNetwork to true in apiserver-deployment.yaml and controller-manager-deployment.yaml i.e. by adding hostNetwork: true on containers level and adding insecureSkipTLSVerify: true in APIService Object i.e. apiregistration.yaml and removing caBundle. after this kube apiserver lagging and catalog controller manager pod crashing both are resolved. also for successful catalog api server registration with kube-apiserver, i suspect that kube-apiserver must be run without any http proxies set as env on container level.
Thanks @mszostok for all suggestions and advises.


How can I pass a commit callback

Hi!
Is there a specific reason, why you overwrite the commit callback? How can I receive commit errors? Wouldn't it be nice to pass an optional callback to the commit methods, which overwrites the default callback? Or am I overlooking something?
https://github.com/nodefluent/node-sinek/blob/452b16b76a5363ccfb1f20178fe474789337e21c/lib/librdkafka/NConsumer.js#L191
Thank you!

Hi @vuza, yup the reason is that I planned to use it to offer a "real" commit callback on message or commit basis in a future version of the API (did not really need it so far) - but you are right, I shouldn't overwrite it, without giving you an option to register your own callback.
I have fixed that in<EMAIL_ADDRESS>(NOTE: I have also upgraded node-rdkafka to 2.2.0)


racket: 6.9 -> 6.10

Motivation for this change
Update racket to the current version.
Things done
The compilation with the previous used --enable-shared-flag failed for the current version. However, compiling without this flag succeeded.
Furthermore the src/README says that even the distributed binaries are compiled without it.

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

We prefer shared libraries, whenever possible, so I fixed the build instead.

Thanks for your fix!
@Mic92: could you please explain me the new unset AR line? Thanks a lot.

this is a problem occurring in single packages since: https://github.com/NixOS/nixpkgs/commit/093cc00cdd9d8cf31ecce5bc1dd3645c460a1b98


Wrong default options for cache

Hi there! I just noticed these default plugin options in the plugin's source code:
https://github.com/tobimori/kirby-thumbhash/blob/cfc48966eb901d3b6a80142385ca70415d697073/index.php#L29-L31
While the documentation states that both these options should betrue by default.

LOL you're right. never noticed it. guess i've been running thumbhash without cache in production all the time 🙈

will be fixed in the next release


CockroachDB support

New

Added database mode selection to login screen

Warning

Need regenerate bindata

Limitations

Tested with CockroachDB CCL v1.1.5
Minimum version v.1.1.5
Currently root user supported
Login with none root user , require select role to pg_catalog tables
Connection partial information, missing client network information
Table information not supported ( later )

Supports

Structure view supported
Indexes view supported
Constraints view supported
Query, Explain query supported
History supported
Activity showing cluster query states
Activity query stop supported
Rows and filtering supported

Bookmarks

Not tested

Thanks for the contribution. I'd love to see a set of tests that run against real Cockroach db instance, like in the scropts/test_all.sh script, which runs tests against multiple Postgres versions using Docker. At least i will be able to test all this stuff locally.

Hi @sosedoff
Iclose request, and write more test for cockroachdb.
Thx

@backy-io I just started some work on getting the CockroachDB integrated (partially) into Pgweb, so your contribution will be useful here. Thanks.


update instructor guide

with

why we teach the lesson
intended learning outcomes
how to teach the lesson

merging then!


µRefactor PartialEq for WidgetCore

tremendously improve performance :)

Where does this improve performance? A short test shows no difference while browsing through a directory. Looks much nicer, so merged anyway.

Where does this improve performance?

It was just a silly joke

Oh, I see, so you just wanted in on that list of contributors ;).
If you're interested, I think I saw at least one other PartialEq implementation yesterday that looked just like that. Well, I guess there are a lot of places that could use clean ups like that...


Use ROCm on ubuntu VM hosted on windows ??

Is this possible ? Or does ubuntu need to be on bare metal.

Honestly we have not tired it yet on Windows via vm yet.    We been heads down on core features.
Greg
On Oct 30, 2016, at 8:44 AM, Aaron Boxer <notifications<EMAIL_ADDRESS>wrote:
Is this possible ? Or does ubuntu need to be on bare metal.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/43, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuRjsBFik16ahibSE28wdu-CEKI4jks5q5J9PgaJpZM4KkYQF.

Thanks. I will just dual boot windows/linux


role not available fix

Role names with spaces does not work yet.

We could make it so if you write the "role name with spaces" in quotation marks (") it will consider it as one role input.


Upgrade from 5.0 to 6.1 from stats page fails with apt-get update error

I ran into an issue when trying to upgrade via the adsb stats page. It seems to be related to the script run-apt-get. The command sudo apt-get update was failing when run in a terminal with the error  Repository 'http://archive.raspberrypi.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'oldstable' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Solution was to run sudo apt-get update --allow-releaseinfo-change in a terminal. After this I was able to update successfully from the adsb stats page.
This was on a custom install of piaware on Raspian 10

see https://github.com/flightaware/piaware_builder/issues/18#issuecomment-973697475 (tl;dr: out of our control and doesn't affect newer installs)


fix: cpp17 namespaces

Description
Replace C++17-style namespaces with nested ones to allow compilation on Edge-Auto on the Roscube, which has a noncompliant c++17 compiler for the nodes:

TensorRT YoloX
ByteTrack

Related links
Parent Issue:
https://github.com/tier4/edge-auto-jetson/pull/57
How was this PR tested?
It was tested on Edge-Auto platform on both the ADLink AVA3510 and Roscube RQX-58G. https://edge.auto/
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.

Thank for submitting this PR!!
IMO, changing namespace for the specific Hardware (e.g. Roscube) and non standard compilers is not good to keep the autoware codebase healthy.
How do you think about it? @vividf @amadeuszsz @tzhong518

Thank for submitting this PR!!
IMO, changing namespace for the specific Hardware (e.g. Roscube) and non standard compilers is not good to keep the autoware codebase healthy. How do you think about it? @vividf @amadeuszsz @tzhong518

Would be nice to keep compatibility with other devices by such a simple syntax change. I don't think we have a lot of nested namespaces within single component, thus this change will not decrease readability.
I can imagine that other Autoware CUDA-based packages find their use case on edge devices. We could populate this change for all packages which utilize CUDA compiler:
common/cuda_utils
common/tensorrt_common
perception/autoware_image_projection_based_fusion
perception/autoware_lidar_centerpoint
perception/autoware_lidar_transfusion
perception/autoware_shape_estimation
perception/autoware_tensorrt_classifier
perception/autoware_tensorrt_yolox
perception/autoware_traffic_light_classifier
perception/autoware_traffic_light_fine_detector

However, edge devices vendors slowly integrate JetPack 6.0 to their products and in near future this change will be not necessary.
Finally, I have no objection to this PR change. Regarding the other packages, I would like to hear other comments.

@amc-nu @a-yyg
I appreciate issuing PR!
@Shin-kyoto @amadeuszsz
Thank you for discussing. This kind of discussion has significant meaning in keeping OSS quality. As it was pointed out, this modification aims to make yolox package work on relatively old environments such as Jetson-based ECU. IMO, this package is one of the most common packages to be executed on such kinds of edge devices, which sometimes are still in old environments. Since I feel the proposed modification looks understandable and does not decrease code quality, I'd like to approve this proposal as a code owner. I don't intend to prevent this kind of discussion in future PRs, so I'd appreciate it if you guys would feel free to post comments when necessary!


Scope quickstart to local development in the README (BUG-77)

Scope the quickstart section to local development in the README. Replace the "configure providers" section with "configure docker" in the README as the secrets work has replaced the need to configure local providers, like "aws" for the "aws" CLI.

bors merge


[seer] dream mode

Dream mode called odo. Example -> https://github.com/taubyte/tau/blob/main/protocols/seer/api_announce.go#L48
We should be fine using devMode instead.

Hi @samyfodil was going through this codebase , can you elaborate on this issue. Thanks :D

In,
https://github.com/taubyte/tau/blob/main/services/seer/api_announce.go#L48
srv.odo==true, means it's not dreamland.
should be  srv.odo==true also means devMode==false, so we should use that instead and delete odo attribute from https://github.com/taubyte/tau/blob/main/services/seer/type.go#L69
@AayushVinayDev


Campvideo

jwplayer is used to playback the camp video.
Google Analytics is included and basic sharing is enabled, too.

Thanks for your awesome help!
Unfortunately, I experienced some issues while testing:

Only in Chrome 45 the player does autostart on pageload, which is an unwanted behavior.
Sometimes, a blue outline appears around the player and disappears when clicking again or trying to inspect the element. I was lucky to read <some-jw-class>:focus {outline: blue} in the inspector, before it disappeared again.
Also in Chrome, the video seems to stop when scrubbing forward and won't start again. There is no buffering indicated, so I don't know, what's happening. In FF or Safari, the player was working more steadily. Maybe you can find out, what Chrome fixes are needed here.

Google Analytics was not used so I removed the ga property from jwplayer setup.

Everything works fine now. Thanks again!


wip: wire-up confirmed "Add Liquidity" quote

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

develop

PR #6028

PR #6030   👈

This stack of pull requests is managed by Graphite.


Internal server error with gopkg.in/pivo.v2

Godoc.org cannot show documentation for gopkg.in/pivo.v2 package. It works for gopkg.in/pivo.v1 though.  Any clues?

Sometime, Error getting package files from gopkg.in. is returned.  However, go get gopkg.in/pivo.v2 works fine.

This page http://godoc.org/gopkg.in/garyburd/redigo.v0/redis also reports internal server error. I expect it to redirect to http://godoc.org/github.com/garyburd/redigo/redis.

http://godoc.org/golang.org/x/tools is also an internal server error :)

I managed to bring up a local copy of gddo. With a fresh database, all of the the packages mentioned in this bug work. So I suspect some kind of database corruption.
@adg @campoy if you can get me access to the server I can take a look.

It might also be some permissions problem.

I'm not proposing dropping the database, just that the code in this repository works and whatever is wrong with godoc.org can only be fixed by someone with access to it.

Somebody needs to look at the logs to see what's going on.
I suspect that the server is out of disk space.

I am having the same issue. The URL that is failing for me is http://godoc.org/gopkg.in/stomp.v2.
Something interesting about this is that the URL that points to the same code without redirection from gopkg.in works fine http://godoc.org/github.com/go-stomp/stomp.

FYI this is a full disk. Waiting on @adg before I go deleting random files.

Clearing out the disk. At least this time it took a long time to fill up.

Still rm'ing files, but stuff seems to be working again.


[Bug]: Unable to see included files in the chat panel

Your minimal.lua config
---@diagnostic disable: missing-fields

--NOTE: Set config path to enable the copilot adapter to work.
--It will search the follwoing paths for the for copilot token:
--  - "$CODECOMPANION_TOKEN_PATH/github-copilot/hosts.json"
--  - "$CODECOMPANION_TOKEN_PATH/github-copilot/apps.json"
vim.env["CODECOMPANION_TOKEN_PATH"] = vim.fn.expand("~/.config")

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

-- Your CodeCompanion setup
local plugins = {
  {
    "olimorris/codecompanion.nvim",
    dependencies = {
      { "nvim-treesitter/nvim-treesitter", build = ":TSUpdate" },
      { "nvim-lua/plenary.nvim" },
      { "hrsh7th/nvim-cmp" },
      { "stevearc/dressing.nvim", opts = {} },
      { "nvim-telescope/telescope.nvim" },
    },
    opts = {
      --Refer to: https://github.com/olimorris/codecompanion.nvim/blob/main/lua/codecompanion/config.lua
      strategies = {
        --NOTE: Change the adapter as required
        chat = { adapter = "copilot" },
        inline = { adapter = "copilot" },
      },
      opts = {
        log_level = "DEBUG",
      },
    },
  },
}

require("lazy.minit").repro({ spec = plugins })

-- Setup Tree-sitter
local ts_status, treesitter = pcall(require, "nvim-treesitter.configs")
if ts_status then
  treesitter.setup({
    ensure_installed = { "lua", "markdown", "markdown_inline", "yaml" },
    highlight = { enable = true },
  })
end

-- Setup completion
local cmp_status, cmp = pcall(require, "cmp")
if cmp_status then
  cmp.setup({
    mapping = cmp.mapping.preset.insert({
      ["<C-b>"] = cmp.mapping.scroll_docs(-4),
      ["<C-f>"] = cmp.mapping.scroll_docs(4),
      ["<C-Space>"] = cmp.mapping.complete(),
      ["<C-e>"] = cmp.mapping.abort(),
      ["<CR>"] = cmp.mapping.confirm({ select = true }),
      -- Accept currently selected item. Set `select` to `false` to only confirm explicitly selected items.
    }),
  })
end

Error messages
no error messages
Log output
no errors
Health check output
codecompanion: require("codecompanion.health").check()

- Neovim version: 0.10.2
- Log file: /Users/akash/.local/state/nvim/codecompanion.log

Plugins: ~
- OK plenary.nvim installed
- OK nvim-treesitter installed
- OK nvim-cmp installed
- WARNING telescope.nvim not found
- OK dressing.nvim installed

Tree-sitter parsers: ~
- OK markdown parser installed
- OK yaml parser installed

Libraries: ~
- OK curl installed

Describe the bug
Unable to see included files in the chat panel
https://github.com/user-attachments/assets/6a0b1521-3a16-4361-a2e3-771c935bfe95
Reproduce the bug

Open chat panel
Use /file command to include file

Final checks

[X] I have made sure this issue exists in the latest version of the plugin
[X] I have tested with the minimal.lua file from above and have shared this
[X] I have shared the contents of the log file

hey thanks for building this, I really like it.
I wasn't sure if it's a bug or it just doesn't support but I think I used to be able to see the included files in the chat panel before.
btw I also tried it with the minimal config you had in the bug template and still wasn't able to see the files in the chat panel.
I'm using following neovim version but let me know how can I help you debug this further.
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1727870382

Glad you're enjoying it.
All slash commands send a vim.notify call which outputs that a file has been added to the chat buffer. However, if your cmdline is set to zero, you may not see it. As a fallback, you can do gd to see the message stack but that's a lot of code to wade through.
A few user's have raised this recently so I will definitely look to address this in the near future.
I'll close for now but feel free to open up a discussion to talk about how we could resolve this.

Glad you're enjoying it.
All slash commands send a vim.notify call which outputs that a file has been added to the chat buffer. However, if your cmdline is set to zero, you may not see it. As a fallback, you can do gd to see the message stack but that's a lot of code to wade through.
A few user's have raised this recently so I will definitely look to address this in the near future.
I'll close for now but feel free to open up a discussion to talk about how we could add this feature.

Thanks! I do get the notification, but I swear I was able to see the linked files in the markdown chat panel itself, is that not the case?
Maybe I am just remember what zed does. In this case, should we add that functionality in?
Lot of the times I add multiple files in the buffer, and it'd be nice to see them being linked in the chat panel itself, does it make sense?


SAPIEN and ManiSkill updates (GPU parallel sim + rendering)

Thank you for this nice wiki, I often point newcomers to simulation to this wiki first :)
SAPIEN and ManiSkill recently have added support for GPU parallelized (diverse) simulation of rigid bodies, as well as a parallel rendering system. We would like to include that update info on the wiki, what would be the best way to do that?

Sure! Thank you for your attention and appreciation first! The easiest way is to fork the repo, add materials to the markdown files and submit a pull request. Also, you can submit an issue, write materials to us, and we can help you add them.


Correct sqlcmd commands for WID DB detach

Removed extraneous backslashes preceding (escaping?) the hash
put use master on its own line, followed by another GO
combined in-line code blocks into single block using code fencing, and defined language as 'batchfile'

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

Thanks for the fix! You should see it live by 4/16/2018.


Memory leak

This may be a Grow.js issue, so I've also opened an issue in that repo: https://github.com/CommonGarden/Grow.js/issues/102

http://www.jongleberry.com/understanding-possible-eventemitter-leaks.html

Ah, I'm just an idiot. https://github.com/CommonGarden/Grow-Hub/commit/ed1aa74d6881e873a1c65b7bbb6136ac82121776
Fixed.


Sync eng/common directory with azure-sdk-tools for PR 3250

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/3250  See eng/common workflow

/check-enforcer override


feat: add metrics exporters

This PR adds the ability to export metrics through OpenTelemetry protocol and add ability to expose metrics for prometheus on an HTTP server.
Description

This PR implements two ways to use metrics given by OpenFGA. The default behavior is that no metrics are exposed NoopMeter is used.
How OTLP is implemented ?
Metrics export can be either done by gRPC or by HTTP. The endpoint can also be configured. There isn't a lot of parameters implemented as the SDK can contain a lot of breaking changes through time. Moreover, OpenTelemetry SDK can be configured through environment variables (see SDK).
How to test OTLP implementation ?
openfga run --metrics-exporter "otlp" --metrics-otlp-endpoint "localhost:9000" --metrics-otlp-protocol "grpc"

(An Otel Collector can be installed easily with opentelemetry-collector-contrib/examples/demo)
How Prometheus exporter is implemented ?
Prometheus exporter creates a new HTTP server that will expose metrics on a specific path. Both listening address and path can be configured (default localhost:9090/metrics). Metrics are exposed on a different port than OpenFGA server for security purposes.
How to test Prometheus implementation ?
openfga run --metrics-exporter "prometheus" --metrics-prom-address "<IP_ADDRESS>:9090" --metrics-prom-path "/metrics"

References

#254
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] (Pending) I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

Wow! Thanks for this great PR. The OpenFGA team is on vacation this week, but we’ll try to get around to reviewing this early next week. Thanks again for the contribution!

Codecov Report
Base: 83.79% // Head: 83.70% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (b8e216b) compared to base (ab552b3).
Patch coverage: 71.55% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #360      +/-   ##
==========================================
- Coverage   83.79%   83.70%   -0.09%
==========================================
  Files          85       85
  Lines       13697    13808     +111
==========================================
+ Hits        11477    11558      +81
- Misses       1850     1875      +25
- Partials      370      375       +5

Impacted Files
Coverage Δ

cmd/run.go
47.98% <55.55%> (+0.58%)
:arrow_up:

pkg/telemetry/metrics.go
85.48% <85.00%> (-14.52%)
:arrow_down:

server/commands/check.go
88.09% <100.00%> (-0.03%)
:arrow_down:

internal/middleware/http/handler.go
54.41% <0.00%> (+4.41%)
:arrow_up:

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.

@AlexandreBrg thanks for contributing 👍 We've had telemetry on the todo list for a hot-minute.
I like the approach you've taken here, and we'd love to move forward with your contribution. However, we'd like to minimize the maintenance footprint of the OpenTelemetry integration in OpenFGA. For this reason, we'd prefer to support a single OpenTelemetry exporter and encourage the community to use the OTEL Collector if they need to collect and transform to an alternative format (e.g. prometheus, jaeger, etc..).
Would you mind repurposing this PR to expose only the otlp exporter ?

@AlexandreBrg thanks for contributing 👍 We've had telemetry on the todo list for a hot-minute.
I like the approach you've taken here, and we'd love to move forward with your contribution. However, we'd like to minimize the maintenance footprint of the OpenTelemetry integration in OpenFGA. For this reason, we'd prefer to support a single OpenTelemetry exporter and encourage the community to use the OTEL Collector if they need to collect and transform to an alternative format (e.g. prometheus, jaeger, etc..).
Would you mind repurposing this PR to expose only the otlp exporter ?

Thank you! I'll update the PR accordingly with your request 😄

Hello, I applied all of your reviews, thank you for the time given on this PR :)

@AlexandreBrg, we're considering replacing our OpenTelemetry metrics for Prometheus metrics. @jon-whit expanded more on our reasoning here: https://github.com/openfga/openfga/pull/514#issuecomment-1419878023
We wanted to check in with you and get your opinion on this change, please feel free to add any comments on @jon-whit's PR here


add v3 header

add vertex information to parse_ascii, to allow for the v3 header to be converted/skimmed

Hi Raymond,
I did what you suggested - i.e. removed the unspecified header parsing and just added that for v3 (also updating so that it can run with and without pt_hat). I tested and all looks OK, could you merge?
I understood from your comment that the tests wouldn't need changing as well, but let me know if I should do anything here.
Thanks!

Hi Jaime, you could enable v3 for the tests, but good enough for now. Merging

Thanks Raymond, could you also recreate the container when you get a chance?
On the tests - I thought that the tests were only for the unspecified setup, but if not I can add one for v3 as well.
On 29 Aug 2022, at 23:48, Raymond Ehlers<EMAIL_ADDRESS>wrote:
Merged #21https://github.com/jdmulligan/JETSCAPE-analysis/pull/21 into master.
—
Reply to this email directly, view it on GitHubhttps://github.com/jdmulligan/JETSCAPE-analysis/pull/21#event-7282643099, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGKGX4QV6RGRX5LZNU6RVATV3U42HANCNFSM56EVW25Q.
You are receiving this because you authored the thread.Message ID: @.***>

New container is ready. It's on OSN as usual, local v3.8 .
For the testing, I guess it's a bit ambiguous. I suppose if here is generalized to not use parser_v1_header_v1 as the reference array, it would probably be a more meaningful test. I don't really have the bandwidth to think through this further right now, so if you see the opportunity to add a meaningful test, go for it. Otherwise, just skip it

Thanks! It is working well with the new changes (and less failing jobs which I think you mentioned would be the case).
On 31 Aug 2022, at 13:05, Raymond Ehlers<EMAIL_ADDRESS>wrote:
New container is ready. It's on OSN as usual, local v3.8 .
For the testing, I guess it's a bit ambiguous. I suppose if herehttps://github.com/jdmulligan/JETSCAPE-analysis/blob/8177b07e5f3bcd1e13410680051efa34f8238e8f/tests/test_parsing.py#L70 is generalized to not use parser_v1_header_v1 as the reference array, it would probably be a more meaningful test. I don't really have the bandwidth to think through this further right now, so if you see the opportunity to add a meaningful test, go for it. Otherwise, just skip it
—
Reply to this email directly, view it on GitHubhttps://github.com/jdmulligan/JETSCAPE-analysis/pull/21#issuecomment-1232848062, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGKGX4WI6YI4TFPT5RSLYK3V35DBZANCNFSM56EVW25Q.
You are receiving this because you authored the thread.Message ID: @.***>


Reinstate tags-as-metadata adding option to merge tags. Fixes #699

Hello.
See #699 and linked issues for more information.
This is my first PR into spring-cloud-consul. To be honest I didn't explore the project due to lack of time so I wanted to make the few changes as possible. Please let me know if there is anything to change.
I also didn't had time to configure checkstyle so I will wait for for CI results.

Just saw I authored commits using another user account. My bad.

Thanks.

If you look at 2a667f48e0dcb665886b85796597ff947f181bba055c1216d573b68cb3764a8c, f672845 and 6485240 there is some more to do to get back to parity (though merged rather than replaced).

Looking into it. I solved other discussions but not committed yet.
I will remove draft status when ready.

If you look at 2a667f48e0dcb665886b85796597ff947f181bba055c1216d573b68cb3764a8c, f672845 and 6485240 there is some more to do to get back to parity (though merged rather than replaced).

Looking into it.
I will remove draft status when ready.
@spencergibb on f672845 we should set both tags and metadata if the merge is enabled? Because before we had a property for tags or metadata. Now we have a property for tags and metadata. What I should do?

If you look at 2a667f48e0dcb665886b85796597ff947f181bba055c1216d573b68cb3764a8c, f672845 and 6485240 there is some more to do to get back to parity (though merged rather than replaced).

Looking into it.
I will remove draft status when ready.
@spencergibb on f672845 we should set both tags and metadata if the merge is enabled? Because before we had a property for tags or metadata. Now we have a property for tags and metadata. What I should do?

Yes, I think it should be a merge.

@lucasoares any chance to update this?

@lucasoares any chance to update this?

Hello @spencergibb.
Unfortunately, I had no time to check it. I will try to get back to it this weekend.

Closing in favor of https://github.com/spring-cloud/spring-cloud-consul/pull/775