VDC unreachable by kubectl, won't deploy marketplace solutions

I deployed a VDC on testnet on February 8th. Today during testing, I noticed that I can no longer reach it via kubectl, which returns:
Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout
I am also unable to deploy marketplace solutions on this VDC any longer (it did work at some point). Marketplace deployments fail with alert id 2.
I am able to add and remove worker nodes on this VDC.
Here is the full info on the master node:
pub ip: <IP_ADDRESS>
ip: <IP_ADDRESS>
wid: 5736
node id: DJoL9ZV53K5YQurmxor2BLWTPf3WA9dT3RsFWeDeAx1z
pool id: 2141
size: 15

That's because the vdc entered the grace period, warning message will be updated to be more clear

Okay, I now see a warning about the grace period. However, even after funding the VDC's wallet, the warning remains and I'm still unable to access via kubectl.

@scottyeager can you add the vdc name & where it's deployed ?

Yes, the VDC is named "scott-kubie" and the master node is on TF node DJoL9ZV53K5YQurmxor2BLWTPf3WA9dT3RsFWeDeAx1z. I added 10 TFT to the wallet, which is being consumed as seen on the Stellar explorer.

@m-motawea correct me if I'm wrong, but 10 TFT aren't enough to get out of grace period, probably would have been better if we tell the user they need to pay HALF of what is in their user plan because that what we did to keep their workloads alive for 2 more weeks?

@scottyeager 10 TFT is not enough to get of grace period but enough to keep the workloads live, the VDC needs to be funded with  the plan's price which is 15 in silver added clear message

Okay, that makes sense. I thought that 10 would be enough for another week or two, especially considering that this VDC no longer has a worker node.
I've tried funding with another 15 TFT, then an additional 5 after that. Still no response from kubectl.

After investigation, the vdc has gone out of grace period

Yet I can't reach the public IP
(js-sdk-vpmH-Z_5-py3.8) root@vdc-testnet:~/js-sdk# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1017ms

Kubernetes workloads: https://explorer.testnet.grid.tf/api/v1/reservations/workloads/5736
Pool already has ipv4 units: https://explorer.testnet.grid.tf/api/v1/reservations/pools/2141
This issue should be moved to ZOS repo for further investigation

to be continued in https://github.com/threefoldtech/zos/issues/1202


OpenCvSharpExtern c++ project not building on VS2015

Hi,
this project links to:
opencv_calib3d249d.lib
opencv_contrib249d.lib
opencv_core249d.lib
opencv_features2d249d.lib
opencv_flann249d.lib
opencv_gpu249d.lib
opencv_highgui249d.lib
opencv_imgproc249d.lib
opencv_legacy249d.lib
opencv_ml249d.lib
opencv_nonfree249d.lib
opencv_objdetect249d.lib
opencv_photo249d.lib
opencv_stitching249d.lib
opencv_superres249d.lib
opencv_video249d.lib
opencv_videostab249d.lib
still older than current 300.
Is it correct?

The latest OpenCvSharp links to OpenCV3.0 or OpenCV2.4.10.
What branch did you check out?

I checked out the master branch, making the assumption was the 3.0 one.
Anyway here the additional dependencies from 3.0 branch:
opencv_calib3d249d.lib
opencv_contrib249d.lib
opencv_core249d.lib
opencv_features2d249d.lib
opencv_flann249d.lib
opencv_gpu249d.lib
opencv_highgui249d.lib
opencv_imgproc249d.lib
opencv_legacy249d.lib
opencv_ml249d.lib
opencv_nonfree249d.lib
opencv_objdetect249d.lib
opencv_photo249d.lib
opencv_stitching249d.lib
opencv_superres249d.lib
opencv_video249d.lib
opencv_videostab249d.lib

The OpenCvSharpExtern project in the master branch should link opencv_world300.lib.
https://github.com/shimat/opencvsharp/blob/master/src/OpenCvSharpExtern/OpenCvSharpExtern.vcxproj#L199
Your code seems to be old?? please try git pull.

Hi
pull done, same result, looking more in detail on the project file you mentioned
probably there is some misalignment from Debug and Release version...
see:
https://github.com/shimat/opencvsharp/blob/master/src/OpenCvSharpExtern/OpenCvSharpExtern.vcxproj#L167
Is it correct?

Thank you. I got it.  The Debug config is not updated :bow:
The managed OpenCvSharp assemblies utilize OpenCvSharpExtern.dll as not Debug but Release build. Please select the Release build configuration.

Thank You
Should I close the issue or You close it when updated the project?
My compliments for the excellent work you have done.

:+1:
fixed by https://github.com/shimat/opencvsharp/commit/738a263ebc79b8c09059bf59de651e42054d352b


Omnipay skeleton

Is there any need/interest in a Omnipay gateway skeleton package, similar to the phpleague one?
Just with an example Gateway, one method and a few examples methods, tests etc.
I've created that pretty much now I think, not sure if I should put it up thephpleague/omnipay-skeleton or something? If so, @kayladnls can you create the repo and grant me access?

@barryvdh I think it's an awesome idea.
You should have access here: https://github.com/thephpleague/omnipay-skeleton

Ok thanks.
I've put up the basic stuff, mostly based on the paypal one (because that's the most popular)
If you (or anyone else) has any ideas/suggestions, let me know! Probably best by just creating an issue there :)


Social icons in footer - hard coded http should probably be avoided

In the hydroshare footer, the footer links are mixed http/https.  Https for all would seemingly be best practice.

Not following what exact action is required of me. Is this mezzanine of help pages?
The pages.hydroshare.org admin page (help mezzanine) is not loading for me..

@Lizabrazil I will work with you together to fix this issue.

looks fixed


ipsec webgui, move building the $iflabels array outside if the loop

@rbgarga how can i remove that 'changes requested' label? It should have been back on 'review pending' for over a week..


Update rate capped to 60 times per frame when going into fullscreen

Godot version 3.0.2
When I turn on fullscreen and enable the "print fps" in the project settings, the update rate seems to be capped at 60 times/second. Vsync is disabled in graphics settings and in project settings as well. Also happen when setting resolution to screen resolution and enabling "borderless"
Steps to reproduce:
-create empty project
-enbale "print fps" in project settings
-turn off vsync
-enable fullscreen

When you go into fullscreen mode, does it still print out a higher fps than 60?

Yes, my fps is above 5000 on fullscreen, but I just tested it on Linux, I need to test it on windows now.

Ok, so I tested it on linux and I have no issues whatsoever. High fps when going fullscreen; I have no idea why this is happening on my windows machine..

I tested on win10 here and I've no problem, probably it's something in your system.
Your machine is a notebook right? Maybe the problem could be something related with the optimus technology (maybe godot it's not using the nvidia). I don't have any hybrid GPU to test, so I can't help much.

@k4sma Did you try what the comment above said? (or you can try Godot 3.2.1 too)
I tested with GTX 1060 on Windows 10 and don't have this issue either.

I'll close this as nobody else has been able to reproduce this recently. Please comment (with the issue template filled) if you can still reproduce this.


Pelorus is missing Troubleshooting documentation

Issue to cover various deployment Troubleshooting suggestions as we are missing one.

scope to oc command to show what apps are missing labels  / annotations to work properly w/ pelorus

[ ] "how to ready your data for pelorus" docs section
[ ] move troubleshooting from demo to top-level doc section
[ ] add oc oneliner(s) for common cases as wes has mentioned


lock scroll added

https://github.com/ankurk91/vue-loading-overlay/issues/51

Hey,
Thanks for the contribution, there are some issues with the PR.
Your current solution will also lock the scrolling when the loader is not in the full screen mode.
I would also like this feature to be configurable.
You have not included any tests.

Hey,
Thanks for the contribution, there are some issues with the PR.
Your current solution will also lock the scrolling when the loader is not in the full screen mode.
I would also like this feature to be configurable.
You have not included any tests.

okass. I'm going to work on that

This feature has been added in v3.4.0


jupyterlab demo out of date (version 1.0.10)

The link for jupyterlab on try.jupyter.org https://github.com/jupyter/jupyter.github.io/blob/459acf4446fc58f58d556cdac833d28b823e1125/_data/try.yml#L13 leads to the binder being outdated but it is out of date:

I looks like this link is tied to tag on that repo that has not been updated: https://github.com/jupyterlab/jupyterlab-demo/tree/try.jupyter.org
This URL could be switched to https://mybinder.org/v2/gh/jupyterlab/jupyterlab-demo/master?urlpath=lab  or that git tag could be updated.

hmmm - that's a good point. Ping @jasongrout or @ellisonbg - what would you like to do here?


.yb here doesn't seem to make sense

I think it should be binning.y.min() here, .yb doesn't seem to make sense.
The new line at the end of the file wasn't me ^_^.

Ignore the noise, a lot of history got rewritten in a bunch of commits.
I'm closing this out now as a WONTFIX. I don't want to touch any of the colorization surface because it works, but is in need of a substantial rewrite. I will look into this as part of that when I get to it.


Failure to comply with Apache License 2.0 for copied code

It would appear you forgot to follow Apache License 2.0 for all the code you seem to have... "borrowed" without mentioning that you borrowed it;
https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)
Feel free to look at my repo, which contains code that was obviously used. :)
https://github.com/strazzere/android-unpacker/tree/master/native-unpacker

I used to mentioned in my article that I have borrowed some of your code (http://www.freebuf.com/sectool/105147.html), but i'am sorry for not mentioned it in my project , i just update it.
By the way , your code has an error:
from:
https://github.com/strazzere/android-unpacker/blob/master/native-unpacker/kisskiss.c#L248
to:
https://github.com/strazzere/android-unpacker/blob/master/native-unpacker/kisskiss.c#L232
-1 is bool true

Ah, thats more of a remnant from previous code. According to standards, 0 is false and 1 is true. However I was attempting to pass back a different number for a specific error. However, that if check will still only pass if the returned value is true (1).


Streams not working

hey @streamich
this wont work as expected, what wrong here. it searched the PRs and Issues, and Streams should be resolved somehow (it probably uses all your fs related packages):
//patching everything
const { patchRequire } = require("fs-monkey");
const { ufs } = require("unionfs");
const { vol } = require("memfs");
const mock = require("mock-require");
const realFs = require("fs");

vol.fromJSON(
  {
    "./dir": null,
    "./file.json": "{\"foo\":\"bar\"}"
  },
  __dirname
);

ufs.use(vol).use(realFs);

patchRequire(ufs);
mock("fs", ufs);

//the code inside the app
const fs = require("fs");

// a file from the real FS with or without UFS
console.log("realfs buffer", fs.readFileSync(__dirname + "/package.json")); //buffer
console.log("realfs ufs stream", fs.createReadStream(__dirname + "/package.json")); //undefined
console.log("realfs stream", realFs.createReadStream(__dirname + "/package.json")); //stream
console.log(require(__dirname + "/package.json")); //works

// a file from the memory fs with or without UFS
console.log("memfs buffer", fs.readFileSync(__dirname + "/file.json")); //buffer
console.log("memfs stream", vol.createReadStream(__dirname + "/file.json")); //stream
console.log(require(__dirname + "/file.json")); //works
console.log("memfs stream through ufs", fs.createReadStream(__dirname + "/file.json")); //undefined + ENOENT error

it would be awesome if you can help me?
If im understanding the code correctly it should work (its testing all underlying fs's for createReadStream (continues if one errors, that might be the problem?)

i created a try to fix branch here: https://github.com/digitalkaoz/unionfs/tree/fix/streams
[x] failing test case
[ ] fix for readable streams
[ ] fix for writable streams
[ ] pick correct stream from the underlying fs

Streams are not well supported by unionfs, to make streams work properly somebody needs to port this code and adapting it to work with unionfs.

And this code:
https://github.com/streamich/memfs/blob/master/src/volume.ts#L2006-L2012

@streamich i might found a simpler solution (that fixes the above test scenario), see #160


Revert 45 revert 40 add template for issues

Reverts rexdivakar/Notifly#45

Hey @muthuannamalai12  going forward please make signed commits!

Hey @muthuannamalai12  going forward please make signed commits!


High CPU utilization

Windows Terminal version
1.11.3471.0
Windows build number
Microsoft Windows [Version 10.0.19043.1466]
Other Software
No response
Steps to reproduce

Reboot the computer
Start WindowsTerminal and Open a tab for Ubuntu 20.04 (WSL2).
Monitor "Windows Terminal" in Task Manager.
CPU utilization starts at 2-4% and then slowly climbs to exceed 90% even though the terminal is idle and acrylic features are disabled.
This behavior started after installing the January Windows 10 patches.
I only see this behavior when running WSL2 tabs.  No processes are using CPU (checked with ps -aux). No other Windows process are consuming significant CPU.

Expected Behavior
CPU utilization for an idle terminal should be very low (certainly less than 5%).
Actual Behavior
If left overnight CPU utilization will exceed 90% of the CPU.  Killing WindowsTerminal and restarting it resets CPU utilization to 2-4%, but it will grow over time back to very high values.

In this screenshot, cpu utilization is 28% on a machine with 12 cores (24 hw threads) and the terminal is idle (no running processes).

Can you expando that Terminal entry? It shows there are 10 processes attached to the Terminal, so I can't be sure which process is the one using the CPU:

If it's either a OpenConsole.exe or a WindowsTerminal.exe that's using up the CPU, a dump might be helpful:

Here's my current session (3 Ubuntu tabs and one powershell):


Add dependency check plugin

Add simple dependency check plugin gradle-versions-plugin
It adds gradle dependencyUpdates task which produces dependencies version report. With given configuration, only latest stable versions are proposed as update candidate

Codecov Report

Merging #830 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #830      +/-   ##
============================================
- Coverage     80.09%   80.02%   -0.07%
  Complexity      674      674
============================================
  Files           151      151
  Lines          3084     3084
  Branches        442      442
============================================
- Hits           2470     2468       -2
  Misses          337      337
- Partials        277      279       +2

This is awesome. I love updating dependencies. 🙂


Problem when php artisan authentication:install

PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in C:\xampp\htdocs\l_acl\vendor\laravel\framework\src\Illuminate\Container\Container.php on line 621
Why? :(

You need to increase the max memory in your php_ini you can google that i think

Thanks!


In /index.php, put FAQ/CONTACT link in the button.

The faq/contact link is out of (hanging under) the button.
Tested with Edge.

Stop testing with edge for now man
On Sunday, April 24, 2016, Acha Bill<EMAIL_ADDRESS>wrote:

The faq/contact link is out of (hanging under) the button.
Tested with Edge.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/achabill/cpc/issues/3

i have fixed it
i have resuced the font size alitle

Hi achabill/cpc,
A message from Daniel Carlson was left on IQ Elite for you.
Click here https://a.iqelite.com/j/NHVo5Q/iuc/ to read your message
The IQ Elite Team

This message was meant for<EMAIL_ADDRESS>If you do not want to continue receiving such mails from IQ Elite, please click on this link<EMAIL_ADDRESS>IQ Elite is a service with main office: C/ Gran De Gràcia 15, 1a 1a, 08012 Barcelona, Spain.


add support postgres hive metastore

add support postgres hive metastore

Sorry for the late reply @evolv34, I started the review and never pushed submit. :/

Hi @bitsondatadev any update on this PR ?!

Hi @bitsondatadev I addressed PR comments. Could you please review it ?


Remove repetitive logging

:recycle: Current situation
Advertising data is logged repetitively with standard logging.
:bulb: Proposed solution
Remove the logging because this information is already logged with debug logging.

Thanks


Add ability to read in pddl problem files to plansys2.

Add a new AddProblem service to the plansys2_problem_expert.
Adding problem_file node parameter to plansys2_problem_expert to load a single problem file at launch.
Signed-off-by: Alexander Xydes<EMAIL_ADDRESS>

Hi @xydesa
May you add some tests to this PR? It would be interesting to test what happens when the problem is not found, is not correct, there is errors in the file, or checking that the instances and predicates are correctly loaded.
Thanks!!

@fmrico that's a great idea, I'll start working on that. I'll let you know here when I'm done.

@fmrico I believe I've added tests for all the cases you suggested. I made sure to get coverage over as much of the new code as possible.

Thanks!!!!


The code is very bad. Fastapi provides dependency injection function, but developers don’t know how to use it.

Privileged issue

[X] I'm @tiangolo or he asked me directly to create an issue here.

Issue Content
The code is very bad. Fastapi provides dependency injection function, but developers don’t know how to use it.I suspect the developer has no real project experience

The directory structure of the project is not designed hierarchically. I would like to ask developers what is MVC?

The app/main.py file is at the top level of the directory structure, but it imports the api_router object from a lower-level file. This shouldn't be a mistake made by a developer.

菜鸡，看看你写的破烂代码。async def identify_ws(connection: WebSocketConnection):
while True:
# test identifyResult
try:
rec_data = await connection.receive_data(Face2SearchSchema)
logger.debug("rec_data:", rec_data)
search_data = Face2Search.from_schema(rec_data)
logger.debug(f"get the search data:{search_data}")
        await task_queue.put_async((TaskType.IDENTIFY, search_data.to_face()))

        try:
            res: MatchedResult = await result_queue.get_async()
            result = IdentifyResult.from_matched_result(res)
            await connection.send_data(result)
        except Empty:
            logger.warn("empty in result queue")

        # time_now = datetime.datetime.now()
        # result = IdentifyResult(
        #     uid=str(uuid.uuid4()),
        #     name=session.user.user_metadata.get("name"),
        #     time=time_now.strftime("%Y-%m-%d %H:%M:%S"),
        #     uid=search_data.uid,
        #     score=0.99
        # )

        # await asyncio.sleep(1)  # 示例延时
    except (
        ConnectionClosedOK,
        ConnectionClosedError,
        RuntimeError,
        WebSocketDisconnect,
    ) as e:
        logger.info(f"WebSocket error occurred: {e.__class__.__name__} - {e}")
        logger.info(f"Client left the chat")
        break

shut up,you are the shame of chinese developer.
useless issues should be closed.

建议你注销github账号，不要再给中国开发者丢脸

@alejsdev I respectfully request that this issue be closed. The content appears to contain unsubstantiated claims and potentially harmful remakes that does not align with our community guidelines.


Test branch

Checklist:

[ ] I have read and followed the contribution guidelines.
[ ] I have read and followed the how to open a pull request guide.
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

please don't open spammy PRs on this repo, use your own fork


Added parameter to get_board_visual to see the board from black's point of view

Adds feature suggested in #103
The get_board_visual function can optionally be passed a parameter to see the board from black's point of view.
To make this possible, the board part of the output from Stockfish is inverted both horizontally and vertically. The numbers at the edge and the letters at the bottom are added after the invert, so that they still remain on the right and bottom side respectively.
Test and REAMDE entry added

I have written something similar. You may or may not like it better. Just thought I'd share. I mainly did this for my own visualization using colors, highlighting moves and flipping the board.
I wrote this after I tried flipping the default string provided by this library by hacking it apart and reassembling it and it just became a giant mess.
I also wanted the row and file indicators on all sides.
# required for colored output. possibly linux only, who knows.
from termcolor import colored

class ColorConst:
    # red, green, yellow, blue, magenta, cyan, white.
    # on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white
    # bold, dark, underline, blink, reverse, concealed.
    WHITE_PIECE = "red"
    BLACK_PIECE = "blue"
    BOARD_WHITE = "on_white"
    BOARD_BLACK = "on_yellow"
    FEN_BG = None

def getBoardStr(stockfish: Stockfish, flip: bool = False, highlight: list[str] = [], color = True) -> str:
    # unfliped A8 is top left
    range_ranks = range(1, 8 + 1) if flip else range(8, 1 - 1, -1)
    range_files = range(ord('a'), ord('h') + 1) if not flip else range(ord('h'), ord('a') - 1, -1)
    white_squre = True # first square is white regardless of orientation
    lineSep = "  " + (("+---" * 9)[:-3]) # the seperator between the lines on the board.

    result = " " # spacing for header to line up right
    # make files header
    for file in range_files:
        file = chr(file)
        result = result + f"   {file}"
    result = result.rstrip() + "\n"

    # print actual board
    for rank in range_ranks:
        result = result + lineSep + "\n"
        result = result + f"{rank} |"
        for file in range_files:
            file = chr(file)
            sqr = f"{file}{rank}"
            piece = stockfish.get_what_is_on_square(sqr)
            fieldStr = "   " if piece == None else f" {piece.value} "
            if color:
                fg = None
                bg = ColorConst.BOARD_WHITE if white_squre else ColorConst.BOARD_BLACK
                attrs = ['bold']
                if sqr in highlight:
                    attrs.append('reverse')
                if piece != None:
                    if piece.value in ['r', 'n', 'b', 'q', 'k', 'p']:
                        fg = ColorConst.BLACK_PIECE
                    else:
                        fg = ColorConst.WHITE_PIECE
                fieldStr = colored(fieldStr, color=fg, on_color=bg, attrs=attrs)
            result = result + f"{fieldStr}|"
            white_squre = not white_squre
        result = result + f" {rank}\n"
        white_squre = not white_squre
    result = result + lineSep + "\n"

    # make files footer
    result = result + " " # spacing for footer to line up right
    for file in range_files:
        file = chr(file)
        result = result + f"   {file}"
    result = result.rstrip() + "\n"
    return result

Looks interesting. I would also be willing to create a PR to add this to the existing code.
@zhelyabuzhsky has to decide if he wants to include it in the library.

@FalcoGer I got it running on powershell in Windows, but the graphics are messed up:

Pretty sure it's just a windows problem since I got similar output with termcolor on another chess project (but on linux the output was fine).

It should also work in Powershell if you do the following before outputting the text:
import colorama
colorama.init()

But I could imagine that this could be a basic problem, because we don't know for all systems if colouring works and it could confuse some people if you only get the escape characters displayed.

i think it would be too much to add the coloring as a dependency to a chess algoritm


kitex: 0.10.0 -> 0.10.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cloudwego/kitex/releases.
meta.description for kitex is: A high-performance and strong-extensibility Golang RPC framework
meta.homepage for kitex is: https://github.com/cloudwego/kitex
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.10.1 with grep in /nix/store/l4g458iqly9fgl5dji1qw271g5r1839h-kitex-0.10.1
found 0.10.1 in filename of file in /nix/store/l4g458iqly9fgl5dji1qw271g5r1839h-kitex-0.10.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kitex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l4g458iqly9fgl5dji1qw271g5r1839h-kitex-0.10.1 \
  --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 kitex https://github.com/r-ryantm/nixpkgs/archive/56f4ea65f81d47fc9212f09be3ef26823d207f8b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/56f4ea65f81d47fc9212f09be3ef26823d207f8b#kitex

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l4g458iqly9fgl5dji1qw271g5r1839h-kitex-0.10.1
ls -la /nix/store/l4g458iqly9fgl5dji1qw271g5r1839h-kitex-0.10.1/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

kitex

Maintainer pings
cc @aaronjheng for testing.

Result of nixpkgs-review pr 322175 run on x86_64-linux 1

1 package built:

kitex


Cannot double click to edit DataType of parameters in Function Signature Window

Describe the bug
Double clicking the datatype cells does not allow editing of the entries, although name is perfectly fine. I haven't had the time to bisect, but it appears to be a fairly new bug

Environment (please complete the following information):

OS: Ubuntu 22.04
Java Version: openjdk 17.0.5
Ghidra Version: 5b543c184

I  see the issue and will fix.

Please ensure F2 works as an alternative to the mouse.
Also, any chance of keyboard acccelerators added to the various input places?
Also the subsequent dialog Storage Address Editor cannot be used without a mouse.  There's no way to move the caret out from the Datatype input box.

@ryanmkurtz please reopen this for 2 reasons:

Pressing F2 in the Datatype column of dialog Edit Function at ... doesn't allow the user to change the type without having to use the mouse first (it does however enable the user to go to the Storage Address Editor dialog);
Once in the Storage Address Editor dialog, tabbing forward from the Datatypebox or backward from the Addbutton, when no storage is allocated, appears to lose focus forever as continued tabbing (forward/backward) does nothing and has no visual feedback to tell the user they are actually in the Storage Locations table (that requires Ctrl+[Shift+]Tab to navigate out).

To solve 2, I suggest bypassing that table if it's empty.

@Wall-AF Are you finding that the original issue has not been fixed?

@ryanmkurtz Okay, mouse works fine.  Just seems daft to open another issue for keyboard, although I did create one prior to this #3561!

@Wall-AF I will investigate the issues you mentioned above.

@Wall-AF Here are my observations:

Pressing F2 in the Datatype column of dialog Edit Function at ... doesn't allow the user to change the type without having to use the mouse first (it does however enable the user to go to the Storage Address Editor dialog);

If the cell containing the data type to be edited is selected, then F2 will start the edit.    Once the table itself has focus, you can use the arrow keys or the tab key to change the current cell selection.   If there is a cell selected, it will have a colored border.

Once in the Storage Address Editor dialog, tabbing forward from the Datatypebox or backward from the Addbutton, when no storage is allocated, appears to lose focus forever as continued tabbing (forward/backward) does nothing and has no visual feedback to tell the user they are actually in the Storage Locations table (that requires Ctrl+[Shift+]Tab to navigate out).

In the Dark Theme, the empty table, when selected, has a blue border to indicate the table is focused.   The Nimbus theme appears to have no visual indicator of focus.   When the table is focused, you can press Ctrl-Tab to jump to the Add button, which will allow you to add an entry to the table.  From there you should be able to Ctrl-Shift-Tab to go back to the table, or simply Ctrl-Tab until you get back there.

Pressing F2 in the Datatype column of dialog Edit Function at ... doesn't allow the user to change the type without having to use the mouse first (it does however enable the user to go to the Storage Address Editor dialog);

If the cell containing the data type to be edited is selected, then F2 will start the edit. Once the table itself has focus, you can use the arrow keys or the tab key to change the current cell selection. If there is a cell selected, it will have a colored border.

@dragonmacher Here is my experience:
After moving the cursor using the keyboard only (on the Windows version of Ghidra running from Eclipse) to the required datatype, pressing F2 does change the appearance of the cell (see image below):

but it isn't editable and the customery datatype dropdown doesn't appear.  In fact the only keys that have any subsequent response are these: , , , ,  and arrow keys; all of which move you off the selection.


Fix examples in kustomization

Page preview:
https://deploy-preview-26040--kubernetes-io-master-staging.netlify.app/docs/tasks/manage-kubernetes-objects/kustomization/#customizing
Thanks!
/approve

Page preview:
https://deploy-preview-26040--kubernetes-io-master-staging.netlify.app/docs/tasks/manage-kubernetes-objects/kustomization/#customizing
Thanks!
/approve


(Ready to land with v0.18.0) Re-naming factors-->hello-world; moving tutorial out of readme

This PR renames the factors example to hello-world in order to more clearly establish its role at the heart of our zkVM curricular content.
In addition, this PR separates the Tutorial into a dedicated page, and builds out the README to the hello-world example in line with the approach in #683 and #764

Realizing that this PR also necessitates changes to the crate documentation. Not sure the best way to proceed here; iiuc the crate documentation only gets updated when we push a new tagged release.
Given that we're about to land zeth and TimZ is out this week, I'm thinking I'll probably let this sit until next week...

We are deliberately leaving this open until shortly before the release of 0.18, as between when this PR lands and when 0.18 is released, the 0.17 docs.rs link to the "factors" tutorial will be broken

I just updated for compatibility with https://github.com/risc0/risc0/pull/793

We are deliberately leaving this open until shortly before the release of 0.18, as between when this PR lands and when 0.18 is released, the 0.17 docs.rs link to the "factors" tutorial will be broken. Other than that, this is ready to land.

I think we're close enough that this can get landed.


Problem: electron dependency vulnerability

Solution: Update electron

Closing in favour of dependabot
https://github.com/crypto-com/sample-chain-wallet/pull/71


Binary release

Hi,
is the "from source" the only way to get flecs-cs? Are releases planned for dlls that could be just dropped into the project as dependency?

Hello @slimshader,

is the "from source" the only way to get flecs-cs?

Technically no, in the GitHub Actions I have the native libraries built through CI/CD.

You can download the artifact as a .zip.

I have the idea rolling in my head to use a special case of NuGet packages for packaging only the shared object binaries for runtime, no code. This is something Microsoft does for example with https://www.nuget.org/packages/libclang.runtime.win-x64/.

The NuGet package path of "runtimes/[RID]/native/[LIBRARY][.so|.dll|.dylib]" is special and is handled by .NET when searching for loading libraries at runtime in a special way according to the RID that matches for the runtime.
The problem for Microsoft is that these files are relatively large and have expressed that delivering them through NuGet is not ideal if the frequency is too frequent. I'm still trying to grasp what would the appropriate timeframe be for uploading NuGet packages of the binaries to NuGet. That would most likely dictate a release cycle.

Sorry for late reply, I only had time now to go back to trying Flecs-cs again. With your help I was able to run C# example pojects with no problems so thank you, unfortunately I was not so lucky after importing flecs-cs into Unity, which I reported in other issue.

Hey @slimshader, I'm experimenting with NuGet packages at this time which would cover binary release. See the README.md of the repo for more details.


Don't expose as_texture2surface OSL shader

See @est77's comment here: https://github.com/appleseedhq/appleseed/issues/2744#issuecomment-581274862

What is this shader for?  If it's for Max or Maya shouldn't it be in their directories?


Change themes

modify one-dark themes color to Atom one-dark default
add new one-dark-green themes

A year on and no review or reply
@ivankravets this is unlikely to go anywhere. Close? If not a review?


Add dependencies for discord bot build environment

We'll be using discord.js for this bot, but there are likely other dependencies and quirks with setting it up for ts

currently in the wrong repo due to switching halfway through this sprint


Missing binary when installing v5 on Windows 10: win32-ia32-79_binding.node

NPM version (npm -v): 6.13.7
Node version (node -v): 13.11.0
OS: Windows 10 x64
Node-Sass (trying to install) v.5.0.0

Description of the problem
Running C:\foo>npm install node-sass -g  produced the following error:
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
C:\Users\bar\AppData\Roaming\npm\node-sass -> C:\Users\bar\AppData\Roaming\npm\node_modules\node-sass\bin\node-sass

><EMAIL_ADDRESS>install C:\Users\bar\AppData\Roaming\npm\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v5.0.0/win32-ia32-79_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v5.0.0/win32-ia32-79_binding.node":

HTTP error 404 Not Found

I've checked the release page and the binary win32-ia32-79_binding.node is not on the list. Any chance of adding support for this?
We really don't want to ask everyone to install Python.
Thanks.

https://github.com/sass/node-sass#node-version-support-policy


Bug 296

Connects to SmartSocietyServices/Webapps#296

This pull request makes the build fail.

All is well.


Privacy Policy

As a user, I want to read the privacy statement so that I know what is going to happen with my data
+Alex

Not relevant anymore for the website


error info is not proper when show segments without table exists

when table "t3" is not exists, and  execute "show segments for table t3" , the error info is NPE, and the proper should be table not exists. i will raise a pr for this.

i have raised a pr for this. #500

pr is merged. close it.


all: Switch to Ubuntu 16.04 base VM images

Packer has been switched to use virtualbox-iso rather than virtualbox-ovf as I couldn't get the latter working with the xenial cloud image (the OVF file targets VMWare rather than VirtualBox).
Using an ISO is slower, but given we only release once a month I don't think it is worth the hassle trying to get the OVF to work.
I have also added a custom script to install Docker 1.9.1 as we still need it for building images (although that will soon change: #3753).
CI is still using Ubuntu 14.04 as I am planning a larger refactor.
Closes #2789.

I have successfully released Ubuntu 16.04 AWS AMIs and a Vagrant box with version 	v20161215.2 and installed a 3 node cluster via the installer in AWS and DigitalOcean.
I think this is good to go.


Update kinesis, s3, sns, sqs to 2.20.130

About this PR
📦 Updates

software.amazon.awssdk:kinesis
software.amazon.awssdk:s3
software.amazon.awssdk:sns
software.amazon.awssdk:sqs

from 2.20.123 to 2.20.130
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #388.


Type of nextThrow

Should nextThrow have the more general type forall a. HandlerM a?
Thanks.

Hi! Thanks for the report. It should be more general, sure.


Provide single-line output of tablet info.

Copied from ACCUMULO-2873 - It would be very useful to have a utility that generates single line tablet info.  The output of this could be fed to sort, awk, grep, etc in order to answer questions like which tablets have the most files.The output could look something like the following
$accumulo admin listTablets --table bigTable3
 #files #walogs #entries #size #status #location #tableid #endrow
 6 2 40,001 50M ASSIGNED <IP_ADDRESS> 4:9997[abc]  3 admin
 3 1 50,002 40M ASSIGNED <IP_ADDRESS> 5:9997[abc]  3 helpful

All of the information can be obtained by scanning the metadata table and looking into zookeeper. Could possibly contact tablet servers to get info about entires in memory.

I've take a first run at this - current available at: https://github.com/EdColeman/accumulo/tree/listTabletsCmd exploring what may be possible at to start a discussion.

This still needs addition work.

What is the proper way to determine status?  One way would be to check if the tablet has a loc: assigned.  Is there something else that is more appropriate?
The original ticket mentioned that some information could be pulled from zookeeper - with the
current implementation, all information is coming from the metadata table. What information is missing / would be helpful?
Formatting of size and number of entries to allow human readable option.

What is the proper way to determine status?

Could use TabletLocationState.getState().  One way to get TabletLocationState objects is via TabletStateStore.  The set of live tservers can be obtained using LiveTServerSet.

The original ticket mentioned that some information could be pulled from zookeeper - with the current implementation, all information is coming from the metadata table. What information is missing / would be helpful?

LiveTServerSet pulls the set of active tablet servers from zookeeper.

@keith-turner @ctubbsii I have been working on this as it seems like a very useful tool.  One of the issues I am running into is that the only way to get the current state of tablets is to use objects in the master and this introduces a dependency in the shell on accumulo-server-base.  There are other parts of the code that depend on accumulo-server-base, like the GC here.  The information is coming from ZK and metadata so I was wondering if having something in Ample would be appropriate.  I am not sure what is the best solution.

Ampl might be okay for this. It might also be okay to have a public API for the shell to use.

@milleruntime I suspect the code could be moved to accumulo core OR reimplemented in core (and existing code migrated to Ample). One possible way to add it to ample would be to modify TabletMetadata class to add a method like the following.
TabletState getTabletState(Set<Location> liveTservers) {
   //use tablet metadata + liveTservers to determine the state of this tablet.
  // Location is an inner class TabletMetadata
}

Then maybe Ample could have a getLiveTservers() method.

For my previous comment, the Location type will not really work for this case.  Need a type that just encapsulates (server,session) for the set of live tservers. TabletMetadata.Location has those plus LocationType, which makes no sense for a live tserver.

For my previous comment, the Location type will not really work for this case. Need a type that just encapsulates (server,session) for the set of live tservers. TabletMetadata.Location has those plus LocationType, which makes no sense for a live tserver.

What do you think about a new type in core.metadata (similar to what I did for TabletFile) that could be used everywhere?  And would we want to keep the ZK session Id?  @EdColeman and I were talking about the usefulness of storing the internal session ID.  It seems like its used as a unique identifier of the ephemeral ZooLock for that tserver.  This is a separate issue but I don't think we would want to have the session in this new type.

And I suppose it would need to replace this type here:
https://github.com/apache/accumulo/blob/d1b06d317983d460039861d4ab462d5a65ca3c11/core/src/main/java/org/apache/accumulo/core/metadata/schema/Ample.java#L191

. What do you think about a new type in core.metadata (similar to what I did for TabletFile) that could be used everywhere? And would we want to keep the ZK session Id?

I like that. That Location type in TabletMetadata could possibly extend it.

. What do you think about a new type in core.metadata (similar to what I did for TabletFile) that could be used everywhere? And would we want to keep the ZK session Id?

I like that. That Location type in TabletMetadata could possibly extend it. Not sure about ZK session id would have to look at it. Using the same type to represent the same info throughout the code seems like a big win. Seems like it can follow the pattern of add it and then later adapt code to use it.

Instead of a new type, since the class is much simpler from TabletFile, I am playing around with just moving TServerInstance from master to core and using it.  https://github.com/apache/accumulo/blob/main/server/base/src/main/java/org/apache/accumulo/server/master/state/TServerInstance.java


Changed 4th blog on blog-sidebar-right.html

Changed 4th blog on blog-sidebar-right.html  took idea from https://indianapublicmedia.org/amomentofscience/surprising-science-part-3-geology-in-space.php

Too small of a commit.  Make it larger to avoid conflict.


Issues with New Memory Error Collectors (continuation of issue #43) (Masha)

First, as Suresh noted, the new memory collectors are failing to import to SQL Nexus. Additionally...
The new memory output collects SO much data it's difficult to even go through. Can we maybe try to recycle these files as well? Running it for a few hours got me 28gb of data! Which, even with a file splitter, is pretty difficult to read through. Maybe we can also collect less data?
These are super useful:
-- sys.dm_os_memory_objects (total memory by type, >1MB)
-- memory_workingset_trimming
-- query execution memory --
-- proccache_summary
But these are causing so much bloat and (I could definitely be wrong)  but I'm not finding much value in them:
-- dm_os_memory_cache_counters
-- dm_os_memory_clerks
-- dm_os_memory_cache_clock_hands
-- dm_os_memory_cache_hash_tables
-- dm_os_memory_pools
Maybe we can loop these less frequently and/or split them off into a different file?

Finally getting around to this: I bet you were hitting an issue that others reported. The issue is with the way the data is coming in from PSSDIAG and I have filed an issue there.
Otherwise, we have recently fixed many of the mentioned DMVs not importing - the fix would be in the latest release build https://github.com/microsoft/SqlNexus/releases/tag/<IP_ADDRESS>
Thank you.


Bug in searching when password and username are not set

Endpoint /passwords?q=searchField.
It returns 500 internal server error when searching a word that appears in a saved element which has no password or username.

it seems that it is not related to username and password

api/v1/passwords?q=string with development mode enabled return: The data to decrypt cannot be empty

{     "exception": {         "class": "Laminas\\Crypt\\Exception\\InvalidArgumentException",         "code": 0,         "message": "The data to decrypt cannot be empty",         "file": "/var/www/html/vendor/laminas/laminas-crypt/src/BlockCipher.php",         "line": 463,         "trace": [             {                 "file": "/var/www/html/src/Password/src/Api/V1/Facade/PasswordFacade.php",                 "line": 555,                 "function": "decrypt",                 "class": "Laminas\\Crypt\\BlockCipher",                 "type": "->",                 "args": [                     ""                 ]             },             {                 "file": "/var/www/html/src/Password/src/Api/V1/Action/ListPasswordAction.php",                 "line": 130,                 "function": "decrypt",                 "class": "Password\\Api\\V1\\Facade\\PasswordFacade",                 "type": "->",                 "args": [                     ""                 ]             },             {                 "file": "/var/www/html/vendor/laminas/laminas-stratigility/src/Middleware/RequestHandlerMiddleware.php",                 "line": 54,                 "function": "handle",                 "class": "Password\\Api\\V1\\Action\\ListPasswordAction",                 "type": "->",                 "args": [                     {}                 ]             },


Fix for issue #447. Ignore bean properties without a proper setter/ge…

…tter

Thanks for working on this!
I'm looking at the code now to try to remember how it works, and I think I may have given a bad suggestion on #447. I thought we wrote directly to the field and that was causing the exception. But in fact looking now it looks like we only use the field to decide if the property is optional, and we always write using the setter?
If so, maybe a better fix would be that in ConfigBeanImpl.isOptionalProperty, if field is null, return false (the same as for "no optional annotation found"). That way it is possible to have beans that don't have matching field names, we just won't be able to find the annotation in that case? Would still be an easy one-line fix just in a different place, fortunately the hard part you did here (writing the test) would still apply.
Or maybe I'm confused still, but see what you think.

First and foremost, you're welcome.
Yes, the field is only used to check if the property is optional, the actual writing is performed via an invocation to the setter.
You're right, the correct fix would be to only say that a field is optional if indeed the field is not null and the annotation is present.
I'll submit a new PR with this little change.

Merged! Thank you.


switch New York Times case study to use youtube shortcode (ko)

issue https://github.com/kubernetes/website/issues/25124

review page
https://deploy-preview-25287--kubernetes-io-master-staging.netlify.app/ko/case-studies/newyorktimes/
/assign @pjhwa
/assign @seokho-son

@Arhell Thank you for your contribution!
/lgtm
/unassign @seokho-son

@Arhell Korean working branch is now set to dev-1.19-ko.6. And I'm working on the outdated files of dev-1.15-ko.5  for dev-1.19-ko.6. This file is one of outdated files. (#25284)
Could you rebase the target to our working branch, dev-1.19-ko.6 instead of master?

Thank you very much, @Arhell ! 👍
/lgtm

/lgtm
/approve
Thank you!


Avoid passing default watchlist

Fixes #46. This is PR is a permanent fix after the hotfix in #47.
I've verified that this code works with the old XGBoost (tested 2.3.0) and the new XGBoost (2.5.0). I've set the lower bound to 2.3 because 2.2.0 failed (and we also don't have resources to support all these old XGBoost versions, so a slight bump should be okay?).

Thanks!  Sorry, I forgot about this when I merged in XGBoost.jl.


appman.xml: Advance -> Advanced

Seems to be a typo, it's "Advanced" in this thread as well: http://www.flashdevelop.org/community/viewtopic.php?f=4&t=12200

Updated.


Ninja status format string from argv.

Ninja supports a status format string from NINJA_STATUS env. This is a great feature to have.
Though, in an automated build environment provisioning environmental variables could be tricky.
This patch adds a support for a command line option (--status-format=) to set the status format string. If given, the status format string from the command line would override the one from NINJA_STATUS env.
Only a long option is supported for now. Easy to add a short form if it will be a use case for that.

If you want to set NINJA_STATUS just for a single process invocation, you can do env NINJA_STATUS='foo' ninja. Note that depending on your shell, you may even omit the call to the env program.

Right. Though, it is not always launched from a shell. Addressing that use case was the original motivation of the patch.

Thanks, that looks like a good feature.
(Note to self: Related to #746)

Though, it is not always launched from a shell.

env doesn't require a shell though :)

@gkistanova Could you rebase this PR on the latest master branch?

@jonesmz The PR has been rebased on the latest master branch.


[Bug] Variant getString() -Error: input is not valid Modified UTF-8

I use mbtiles vector data and when clicking to get object information, there is an error. Maybe due to Variant's getString () function, you can add the getBytes() method to Variant and I can decode string with my encoding.
Thank you very much,
A/.geotech.vtool: java_vm_ext.cc:570] JNI DETECTED ERROR IN APPLICATION: input is not valid Modified UTF-8: illegal start byte 0xa7     java_vm_ext.cc:570]     string: 'C.ty TNHH MTV LN ��k Glei'     java_vm_ext.cc:570]     input: '0x43 0x2e 0x74 0x79 0x20 0x54 0x4e 0x48 0x48 0x20 0x4d 0x54 0x56 0x20 0x4c 0x4e 0x20 <0xa7> 0xa8 0x6b 0x20 0x47 0x6c 0x65 0x69'     java_vm_ext.cc:570]     in call to NewStringUTF     java_vm_ext.cc:570]     from java.lang.String com.carto.core.VariantModuleJNI.Variant_getString(long, com.carto.core.Variant) A/.geotech.vtool: runtime.cc:630] Runtime aborting...     runtime.cc:630] Dumping all threads without mutator lock held     runtime.cc:630] All threads:     runtime.cc:630] DALVIK THREADS (37):     runtime.cc:630] "Thread-451" prio=4 tid=37 Runnable     runtime.cc:630]   | group="" sCount=0 dsCount=0 flags=0 obj=0x12e00000 self=0x7364e10800     runtime.cc:630]   | sysTid=24619 nice=10 cgrp=default sched=0/0 handle=0x72bed92d50     runtime.cc:630]   | state=R schedstat=( 479801232 7037869 74 ) utm=8 stm=39 core=7 HZ=100     runtime.cc:630]   | stack=0x72bec9c000-0x72bec9e000 stackSize=991KB     runtime.cc:630]   | held mutexes= "abort lock" "mutator lock"(shared held)

Interesting. Can you share a code snippet to reproduce the issue? Internally, SDK assumes that all strings are UTF-8 encoded and all string inputs coming from Java side should be automatically converted from unicode to UTF-8. So I am not sure how this can happen.

@mtehver,
I'm using MBTiles DataSource for Vector Tile Layer and set VectorTileEventListener for get properties when click to a feature.
I using GDAL for create mbtiles data from Shapefile with font encoding TCVN3 (Vietnamese) not UTF8
MBTiles data sample: https://www.dropbox.com/s/d8xb8mbz7wy15oo/DakGlei_DinhVanHuu.mbtiles?dl=0
CartoCSS for mbtiles:
#DakGlei_DinhVanHuu {line-width:2.0;line-color:rgba(46, 213, 115, 1.0);polygon-fill:rgba(112, 161, 255, 0.47843137);text-name:[TK]+ "\n" + [KHOANH]+ "\n" + [LO];text-face-name:'Roboto Regular';text-size:18;text-fill:#036;text-allow-overlap:false;text-halo-fill:fadeout(white, 25%);text-halo-radius:2.5;text-halo-rasterizer:fast;text-wrap-width:125;text-wrap-before:true;text-placement:point; }
And code snippet
`private class VectorTileListenerCustom extends VectorTileEventListener {
    @Override
    public boolean onVectorTileClicked(VectorTileClickInfo clickInfo) {
        if (clickInfo.getClickType() == ClickType.CLICK_TYPE_SINGLE) {
            Feature feature = clickInfo.getFeature();
            if (feature.getProperties().containsObjectKey("CHURUNG")){
                Variant val = feature.getProperties().getObjectElement("CHURUNG");
                String s = val.getString(); //Error if input is not valid UTF-8
            }

        }
        return true;
    }
}`

Hope you can handle this error, thank you

So the string attributes for vector tiles are encoded as TCVN3, not UTF8? In that case the .mbtiles file has illegal encoding - MapBox vector tiles inside .mbtiles use protobuf format. Protobuf specifies that all strings must be UTF8 or ASCII7 (https://developers.google.com/protocol-buffers/docs/proto#scalar). If possible, I suggest re-encoding the .mbtiles file.

Thank @mtehver and your comment.
And I think i need to convert encoding to UTF-8 to solve this problems.
Best regards,


doctest outputs ANSI escapes to non-color TTYs, resulting in visible junk

Description
doctest’s check for whether to enable color output is too simplistic: it just tests isatty(STDOUT_FILENO) (e.g. in the color_to_stream function.) But not all TTYs support ANSI color; one common exception is Xcode’s console pane.
This causes junk to appear in the output for just about anyone developing native Mac or iOS apps unless they disable color on the command line.
Steps to reproduce
Run doctest tests in an Xcode project, with output going to the console pane as usual.

Expected: Plain output
Actual: Lots of “[0;36m and the like in the console output

Extra information
On Unix systems you can test the TERM environment variable, but that doesn’t work on Windows. Here’s a reliable function that I’ve used in other projects:
static bool isColor(int fd) {
    if (!isatty(fd))
        return false;

    if (const char *term = getenv("TERM")) {
        if (strstr(term,"ANSI") || strstr(term,"ansi") || strstr(term,"color"))
            return true;
    }

#ifdef _MSC_VER
#ifndef ENABLE_VIRTUAL_TERMINAL_PROCESSING
#define ENABLE_VIRTUAL_TERMINAL_PROCESSING  0x0004
#endif
    if (GetRealOSVersion().dwMajorVersion >= 10) {
        HANDLE hConsole = GetStdHandle(STD_OUTPUT_HANDLE);
        DWORD consoleMode;
        if(GetConsoleMode(hConsole, &consoleMode)) {
            SetConsoleMode(hConsole, consoleMode | ENABLE_VIRTUAL_TERMINAL_PROCESSING);
        }
        return true;
    }
#endif

    return false;
}

Thanks! And for now you could use DOCTEST_CONFIG_COLORS_NONE

I actually haven't added the code by @snej in the dev branch, and it would be cool if the library simply works by default - reopening

You must have, the -nc,--no-colors switch is implemented in 2.4.11 at least.

I tried using #define DOCTEST_CONFIG_COLORS_NONE before including the doctest header and that works as well.

yeah, that works, but it would be cool if the library detected as much as possible and handle stuff automatically so users don't have to dig through the docs - I don't see automatic detection as feature creep (while many other things could be considered as such)

Sure thing, though I think it's more effort than just squeezing in an isatty call somewhere if that is supposed to work across all platforms without generating any compiler warnings. But it's possible that the change is trivial ofc.
@snej If you are up for it then you can have a stab at implementing it and make a PR.


chore: Remove AREnableMyCollectionOrderImport feature flag

The type of this PR is: chore

This PR resolves CX-2269
🔴  Blocked by https://github.com/artsy/metaphysics/pull/3668
Description
Remove AREnableMyCollectionOrderImport feature flag.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Remove AREnableMyCollectionOrderImport feature flag - ole

This PR contains the following changes:

Dev changes (Remove AREnableMyCollectionOrderImport feature flag - ole)

  Generated by :no_entry_sign: dangerJS against 61cb3b0c0f6b01cb875b292bbcc0a264f702ad17

Thanks Ole!


Sketch: compile auto mark to explicit marks

To satisfy my curiosity, just looking into what it would take.
The easy problem: it should have the accessor in the options, not the materialized array.
The hard problem: I wasn't thinking about this before, but obviously Plot doesn't know the name of the data that was passed in (or rather, it doesn't know the literal expression), so this couldn't really work. And the compiler can't actually execute the code. So… I don't know where this would live. It's both dynamic and needs "reflection". It'd have to be something wild like: editor asks the worker, worker calls this, this returns a function that takes the literal data expression, worker passes that back to editor, editor calls compiler with the returned function, compiler passes in the data source expression, that returns a string which we insert as a new cell…

Superseded by https://github.com/observablehq/plot/pull/1504


Add big-core multi-threaded benchmarks

This adds multi-threaded big-core benchmarks for the full configuration
matrix. We are optimizing performance primarily on big cores right now.
This also includes switching our single VMVX benchmark to use big cores
instead of little. This benchmark is mostly for reference and big cores
are more useful for this, plus the benchmark will take less time. Note
that this will mean we are starting a new series for this and won't be
able to easily compare with previous history. I don't think we care.
Fixes https://github.com/google/iree/pull/7807

LGTM. It's just that now we are taking almost 1.5 hours for each run, which makes iterations on pull requests even harder.. Some effort towards #7792 would be truly appreciated! :D

Yeah :confused: I believe I did warn about the consequence of "pause infrastructure work except benchmarking". The benchmarking stuff really follows naturally from general CI improvements...

oh, did we not trim a bunch of the little core ones yet?  I thought we'd be just swapping some little core with big core ones.

We did not. Based on our discussions (in #7804 and elsewhere) I believe we really should be measuring both

some of both is useful, the full grid isn't- for example, we could get by with sync and 4 thread only for quite awhile, and for the cpu cases I'm not even sure there is a difference between experimental flags and not - cutting down the suite size by 8x+ feels like an unquestionable win given that no one is looking at those numbers - I think we'd all rather have things take sub-1hr instead of 1.5hr and be able to more effectively use the infra than have a bunch of extra graphs that all show the same stuff :)

(or if the full grid was nightly and per commit was the one with numbers we cared about that'd be better, too)

(or if the full grid was nightly and per commit was the one with numbers we cared about that'd be better, too)

Something like that  is indeed the end goal I am aiming for.

some of both is useful, the full grid isn't- for example, we could get by with sync and 4 thread only for quite awhile

:+1:

and for the cpu cases I'm not even sure there is a difference between experimental flags and not

The experimental flags have "--iree-llvm-loop-unrolling=true" right now. Leaving that config was my compromise after endless arguments about whether our CPU benchmarks should include special flags. If people optimizing CPU performance are OK with not including that configuration, then that is certainly fine with me

cutting down the suite size by 8x+ feels like an unquestionable win given that no one is looking at those numbers - I think we'd all rather have things take sub-1hr instead of 1.5hr and be able to more effectively use the infra than have a bunch of extra graphs that all show the same stuff :)

I think the key thing I need is for everyone to say what numbers they are looking at :-) It would be easy to just comment out various configurations so that they series stop getting new data points and I think we don't lose much. We can re-enable them quite easily as well. And now that we have the full grid defined it means that re-enabling them doesn't create some random new series each time. So to that end
@bjacob @MaheshRavishankar @antiagainst @benvanik @hanhanW @rsuderman @ThomasRaoux @stellaraccident (I believe that's everyone who may be actively looking at benchmarks)
Can you say which benchmark configs you are actively monitoring?
In particular, whether there are any experimental flags that you do find useful and want to keep monitoring? I'm guessing that Mahesh, Lei, and Thomas are mostly looking at GPU stuff, which is faster and has less fan out than little cores (but would still be nice to know if there are some configs that aren't useful). I think no one is actively optimizing little cores right now, so Ben's suggestion of sync + 4 threads and no experimental configs makes sense to me. Are the big core loop unrolling configs useful? There are a lot more settings on the GPU experimental flags. Are those still useful?

The experimental flags have "--iree-llvm-loop-unrolling=true" right now. Leaving that config was my compromise after endless arguments about whether our benchmarks should include special flags. If people optimizing CPU performance are OK with not including that configuration, then that is certainly fine with me

I've been playing with these flags for a while. This flag shows that there are some rooms of improvement for vector unrolling. (vector unrolling in MLIR versus vector unrolling in LLVM backend). The reason that we have this mostly because of legacy. I think it's introduced when we're actively working on CPU performance burndown. And it helps the performance. IMO, we can exclude the configuration because the flag is turned off by default and we care more about default flags.

Can you say which benchmark configs you are actively monitoring?

I mostly monitor CPU default-flags performances on Pixel 4 (sync + 4 threads).

I think the key thing I need is for everyone to say what numbers they are looking at :-)

good question - that's probably what's been missing from all this!
Today I look exclusively at:

1-thread,big-core,full-inference,experimental-flags with IREE-Dylib
4-thread,big-core,full-inference,experimental-flags with IREE-Dylib
full-inference,experimental-flags with IREE-Vulkan
kernel-execution,experimental-flags with IREE-Vulkan (for ones that have it)

little core 1 and 4 thread would be interesting if we had any focus on them - today they are untuned (or so I'm told) and not really representative enough to worry with. I think they're useful to have as they tell us where we are and will help once we do start tuning them. I never touch the others unless participating in one of these "which do we need" discussions to verify that I don't need them :P
If I look at single threaded stuff to get an idea for total model CPU time I use 1-thread and not dylib-sync as that by nature is much noisier (as it's running inline with the VM), and if I want multithreading I look at the highest thread count as that's where multithreading effects are most visible. The in-betweens (2-3 thread) may be useful for some models to track how we scale, but not for every model and not for every configuration (and eventually not for every device) - and I'd be fine if those were only on request (I've done that comparison once in the last 6mo). I'm not sure I care if we even track dylib-sync, given that it's guaranteed to be noisier and is less relevant to codegen people (no codegen people should look at dylib-sync and should look at 1-thread for measuring kernel performance - I feel like having it there throws people off - especially seeing above that hanhan is looking at dylib-sync :).
As for experimental vs default I think we should work harder to not have experimental flags (as many have mentioned in the past) - especially ones that linger forever. For example deeplabv3 dylib-sync default is 1.16s and experimental is 640ms - tells me that it's probably worth making that flag default because I'm never going to look at the one that is slower :) Vulkan ones don't differ much IME (are we even setting any flags?).
So when looking at traces for example, I only look at 5 of the 22:

Maybe a step here without impacting the reporting would be to have a tag that we put on the tests to indicate which ones we want traces from and skip otherwise. That said, the above set is also the only numbers I look at in the reported numbers too - the only time I've looked at the others is when there's an outlier and it always ends up just being benchmark variance instead of real divergence.

Echoing what Hanhan said above. I dont really look at the LLVM unrolling flags (though Hanhan more mointors the perf now for x86 backends). Hanhan just sent out a PR to make use of vector unrolling by default which would reduce the impact of these flags. The deeplabv3 example above would be interesting to see where the difference is (the dispatches should be identical, so its a stronger signal). I am personally happy with dropping the experimental set, just rely on the default. If that means that some benchmarks have a higher number than what we see with those flags, thats good. The purpose of these models and perf numbers is more to track regressions and guide work. If the experimental flags are hiding some of it, that is deteremental.

That's interesting - most of the models have the same spread (mobilenetv2 is 172->91ms default->experimental, mobilenetv3 is 46->23ms, etc). Seems to me that if we still have flags with 2x perf deltas that aren't enabled we should probably prioritize turning them on by default (sounds like that's what hanhan is doing here 🎉). I don't find it useful to look at things that are 2x slower than they could be and don't want us to be blindly tracking and telling people only numbers that are 2x worse than they are - but understand and agree with not wanting non-default flags - I'd much rather have 2x faster stuff by default :)

I think the issue with a lot of the flags was that the best for CPU was not the best for GPU (and came with significant performance penalties). I believe Mahesh was working on making it so that these sorts of decisions could be made within the compiler based on the target backend, rather than controlled only by a global flag. We may also have had correctness issues in some cases? I think the use case for experimental flags while developing a new feature remains. But generally I agree that flipping defaults that give us big speedups is something we should do :-)

For other models besides MobileBert, there are many convolution ops. It's better in experimental flags because we don't tile these conv ops correctly.
My experiments tell me that tiling the op with native vector sizes helps a lot in this case. I do observe this behavior when working on gemms.
I'm going to look into the conv cases and we will see how we can tile, fuse, and vectorize conv ops. It will definitely help the experimental-flag issue for these models.

That's interesting - most of the models have the same spread (mobilenetv2 is 172->91ms default->experimental, mobilenetv3 is 46->23ms, etc). Seems to me that if we still have flags with 2x perf deltas that aren't enabled we should probably prioritize turning them on by default (sounds like that's what hanhan is doing here tada). I don't find it useful to look at things that are 2x slower than they could be and don't want us to be blindly tracking and telling people only numbers that are 2x worse than they are - but understand and agree with not wanting non-default flags - I'd much rather have 2x faster stuff by default :)

Depends on what you are tracking. Having the LLVM unrolling flag is just to paper over something that is not being done the correct way in the CPU backend. So I dont really count it as us having gotten to the 2x better perf. In terms of prioritization, there are so many things that are to be prioritized, I need a uber prioritization of prioritizations.

Auto-search of prioritization :P
I think my meta point is that if we know we can be 2x better - whether via this flag or fixing the CPU backend - that's extremely valuable information during prioritization and planning: it's all about amdahl's law and if we falsely have something that's really 20% of the perf impact showing as 80% of the perf impact it'll ripple out and affect all other prioritization in the system. If we are 300ms then I'm not going to prioritize removing 5ms of overhead somewhere that's 1.6% of the total time vs if we are 75ms and it's 7%, etc. I definitely empathize with the long TODO list (I mean, look at how long I hand-waved over allocations and such!) but I was only able to do that because I had visibility into what the target was - all I'm wanting to ensure here is that we are tracking our targets so we have visibility.

(I guess more concretely: I need to know what the codegen targets are in order to prioritize my work even if the codegen team is not actively using them, which is why gcmn's request for hearing all our usage is such a great one :)

I think what you're saying Ben actually is a reason to keep experimental flag configurations that give us large speedups :-)

yep! So long as they differ like this they are really useful (if they were like 1% different then not as useful). If we get to the point where there are no experimental flags we could treat them like branches and disable those benchmarks until needed again for long-running work like this. Being able to hide the inactive benchmark series from dana would make that pretty slick!


ci: 新增tag到发布工作流

当package.json中的版本变化时，触发tag-release.yml工作流，生成一个新版本的tag并推送到repo
当有新的tag推送到仓库时，触发生成镜像并发布的工作流，构建带有版本号tag的镜像并推送

Codecov Report
Base: 64.61% // Head: 64.61% // No change to project coverage :thumbsup:

Coverage data is based on head (db6ea9b) compared to base (eadc319).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #426   +/-   ##
=======================================
  Coverage   64.61%   64.61%
=======================================
  Files         105      105
  Lines        2962     2962
  Branches      370      370
=======================================
  Hits         1914     1914
  Misses       1002     1002
  Partials       46       46

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.


PHASE 1: Update Invite card text

"Invite your friends now
and let them also claim free G$’s"
*** RELEASE ONLY WHEN PHASE 1 IS LAUNCHED ***

the small letter should be displayed in the "your" word

@sirpy As i got it ...according to this ticket #2135 the "and let them also claim free G$'s" text should be regular, not bold

@AnastasiiaOdnoshevna the changes pushed to master - please wait some time and test again. Thanks.

@yaroslav-fedyshyn-nordwhale @sirpy
A feed is displayed according to require
As i got it ...according to this ticket #2135 the "and let them also claim free G$'s" text should be regular, not bold
Checked on DEV V0.25.0
LG V30+ // Android 8.0 // Google Chrome 83.0.4103.106
Desktop: Windows 10 // Google Chrome  83.0.4103.116

The invite card is displayed according to require
Checked on QA V0.25.6
LG V30+ // Android 8.0 // Google Chrome 83.0.4103.106
Desktop: Windows 10 // Google Chrome 83.0.4103.116


change uns structure for spatial

New version of uns as discussed in https://github.com/theislab/anndata/issues/295#issuecomment-596164456
The reason for setting a dummy library_id (as "0" for instance) is:

The library_id information is in the molecule_info file explained here. Recover it would require to input an additional file path
All the 10x data I had a look at, both from the same tissue (so 2 slides from same tissue slice) and from different tissues, have library_id entry set to "0". So I am not really sure how space ranger set that value but it does not appear to be unique (and therefore not a natural batch_key value).
I think it would be more useful if this value is set according to user choice. Only in the context of adata.concatenate it should be modified according to batch_key. This is also the only point in the analysis where the library_id entry matter.
I agree with respect to maintaining the tree structure before and after concatenation, so the reason for keeping the library_id entry and setting it to a dummy variable by default.

Looking forward to hear what you think @ivirshup and if agree I'll go on with PRs for anndata.concatenate.
Also, let's keep this spatial branch open until we really have (almost) everything up and running for spatial analysis.

Thanks for the H/T @ivirshup ! I was able to find the library ids and I also added the metadata as suggested.
This should do for now. I have also changed the plotting function to make it work with the new uns structure.
The idea for uns concatenation is exactly that one yes. Basically, if the keys are unique, then concatenate, if they are the same, override and throw a warning.
With respect to mixed anndata objects (e.g. one visium adata concatenated with one scRNA-seq), I will just concatenate the obsm and add empty entries to the one missing (like zeros) or something along the lines of masked arrays (although I don't think it's particularly useful in this case).

The idea for uns concatenation is exactly that one yes. Basically, if the keys are unique, then concatenate, if they are the same, override and throw a warning.

I was thinking that this should have multiple modes, chosen by an argument like merge_uns. I'm thinking options would be:

None: the default. Maintain current behaviour of just not merging.
"unique": Only keep values which are uniquely specified
"identical": Only keep values which are the same in all objects
"override": Just take the first value from each

You wouldn't have to implement all of these, just one that makes spatial concatenation work for now.

With respect to mixed anndata objects (e.g. one visium adata concatenated with one scRNA-seq), I will just concatenate the obsm and add empty entries to the one missing (like zeros) or something along the lines of masked arrays (although I don't think it's particularly useful in this case).

Could there be a fill_value  argument here? A way for people to specify what the fill value should be?
I'm mainly against masked arrays since I don't think they're going to work with sparse matrices, and I'm not sure about other array subtypes.

Some tests are still failing, but not because of uns/spatial. They all throw errors along these lines:
assert 'Error: Image files did not match.\n  RMS Value: 15.114361035293829\n

@giovp or @flying-sheep, any idea how to get travis to run this? I'd like to see what's happening there.
Also @giovp, were you going to change the coordinates obsm entry key "coords"?

I did not change the basis to coords because a lot of the time the basis is specified as
elif f"X_{basis}" in adata.obsm.keys():
        basis_key = f"X_{basis}"

hence maintaining the X makes it consistent with the others.

Is that in embedding? I had thought we'd removed all that. There shouldn't be any special meaning to strings starting with X_ anyways, it's just a convention.
I'd like to give this a review, but I'd need to see that tests are passing. Do you know why travis isn't running on this?

Just re run it, tests passed

Is that in embedding? I had thought we'd removed all that. There shouldn't be any special meaning to strings starting with X_ anyways, it's just a convention.

Well but until it has not changed I would leave it as is no?

If you change X_coords to coords, where do errors occur? Could you also point me to where you're seeing this code? I've definitely been using embeddings in obsm whose keys don't start with "X_".

Right, my bad, switched to that.

Hi @ivirshup this is ready to be reviewed again.

Used lightweight figure for testing
Changed docstrings

Tests failing are not related to anything addressed by this PR.

Hi @ivirshup this would be ready for review.
Travis test are failing for some figure in diffusion maps, not sure why though :(
Thank you!


Small Issues from pre-beta testing

I couldn't find an actual zip file created by the ./gradlew command.  I eventually got it to work by copying the full contents of the confluentArchive directory to ~/confluent-7.2.2/share/confluent-hub-components
In the Confluent Control Center UI, there are dots at the end of the labels for the configuration values
Similarly, there is an * after the hostname label in the Confluent Control Center UI

the zip can be found in build/confluent,but we have published a release


master: Makefile Automate operator-sdk install, preserve nullables.

Might fix make deploy-olm image override workarounds by forcing use of a GitHub release binary which hopefully uses tagged version of opm instead of latest by default.

Codecov Report
Base: 33.53% // Head: 33.53% // No change to project coverage :thumbsup:

Coverage data is based on head (82dc2f0) compared to base (0ce4b79).
 Consider uploading reports for the commit cf44973 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #846   +/-   ##
=======================================
  Coverage   33.53%   33.53%
=======================================
  Files          17       17
  Lines        3152     3152
=======================================
  Hits         1057     1057
  Misses       2003     2003
  Partials       92       92

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.

/retest

/cherry-pick oadp-1.1


Issues faced when installing ledokku in an existing Dokku server with deployed apps

This is a general report of the issues I faced when following the installation wiki (https://www.ledokku.com/docs/installation). I ended up following the manual installation steps (https://www.ledokku.com/docs/advanced/manual-installation) to get ledokku working.
Services were not created/linked
When I listed the redis and postgres services, there was no service created for ledokku
dokku redis:list
# only my existing redis services. No ledokku

dokku postgres:list
# only my existing pg services. No ledokku.

So I had to create and link these services,
dokku redis:create ledokku
dokku redis:link ledokku ledokku

dokku postgres:create ledokku
dokku postgres:link ledokku ledokku

Then deployed ledokku from image and set up config values,
dokku git:from-image ledokku ledokku/ledokku:0.7.0

IP was being used by another app
An existing app was being served on port 80. So visiting my droplet's IP showed that app. But the previous step deployed the app at ledokku.example.com. So I added a DNS record for ledokku.example.com and the UI finally appeared.
GitHub redirection link broken
GitHub was redirecting me to my IP address. But as another app was served on the IP, I had to manually replace the IP part in the URL to ledokku.example.com. I guess setting ledokku.example.com in the DOKKU_SSH_HOST config variable would have fixed this issue?

As you are already running apps via dokku, let me give you a solution that requires the usage of Dokku CLI.

Meanwhile we were having some internal discussion to adopt a separate CLI for ledokku, which leverages dokku CLI with minimal documentation and which is beginner-friendly.

First, let's confirm whether your previous efforts have created an app name: ledokku. If there is any app with that name we would like to destroy it and reinstall it; so that everything works properly as expected.
Step 01: Finding Previously Installed Ledokku
With the below command, you can check the existing apps.
dokku apps:list

Step 02: Deleting existing ledokku
Now, if there is an app named after ledokku, let's delete it and
dokku apps:destroy ledokku

This command will prompt you verification "by manually entering the name of app:ledokku"; do as it says and proceed
Step 03: Clearing old ledokku script
Let's delete the already existing, ledokku-bootstrap script and download the new one.
Deleting the old one

If you know the location, go to the location and remove it using sudo rm -r ledokku-bootstrap.sh
If for some reason, you forgot the location of your downloaded script  find . -name ledokku-bootstrap.sh helps you find the location of the download. Once you know the location, you can use the above-mentioned command to remove it.

Downloading the new script
Let's go to the home directory of root.
cd

Also, if you are not a root user, the new script will not work, the below commands will help you enter into root and root directory.
sudo su
cd

Downloading the new script
wget https://raw.githubusercontent.com/ledokku/ledokku/master/ledokku-bootstrap.sh

Making it executable
chmod +x ledokku-bootstrap.sh

Step 04: Installing Ledokku via new script
./ledokku-bootstrap.sh

Ledokku is compatible with dokku versions v0.24.0 to v0.24.10.

Don't about the versions, the new ledokku script will take care of all the checking and will prompt you the necessary update requests and will update your dokku accordingly.
We are on our way to automate all these processes via our CLI. Also, if you were facing any issues, let us know via comments or by creating a new issue or discussion, we might not be able to reply to you immediately, but we consider every issue, comment and discussion.

@j-a-h-i-r

An existing app was being served on port 80. So visiting my droplet's IP showed that app. But the previous step deployed the app at ledokku.example.com. So I added a DNS record for ledokku.example.com, and the UI finally appeared.

Thanks for your general insights; we will make our installation script look into the existing dokku apps to provide more flexibility.


Simple cool improvements for the project!

Hi!
I want to suggest some interesting and easily implemented (already made by me) improvements.
And so the first thing is the smoothness of the animation of pressing the button, it seems to me that when you click on the button, there is no return, so I tried to add transition:. 08s; and it turned out very cool. It feels like the button is actually being pressed and the shadows are not changing.
Then I think that the transparency of 0.6 for a disabled element is a lot, you can confuse it with the usual one. You can set (opacity) at least 0.5.
The following also applies to the disabled button. Can be done (I already did) animation of shaking when you click on it.
.is-disabled:active {
	animation: .08s shaking;
}
@keyframes shaking {
	25% {
		transform: translate(-3px, -3px);
	}
	50% {
		transform: translate(-3px, 3px);
	}
	75% {
		transform: translate(3px, 3px);
	}
	100% {
		transform: translate(3px, -3px);
	}
}

You can do better in more frames.
I would also like to see a slider in the NES style. I can do it if you want.
Well, and many more new improvements and translations to a newer version of html. Again, I can do this if you pay attention to it.
Thank you, I hope my advice will help in improving the project.

Hello @NQUARE, thank you for your issue and all your suggestions.
To be honest with you, we are not working actively on this project for a while now.
I've been trying to maintain it from time to time, however I don't have access/authorization to accept new features or publish new releases.
So for now, I do apologize, but I don't think there's much we can do here.
Thank you again.


[dvsim] Address duplication of values in hjson

The duplication of tests in regressions is not reported as
an issue. The issue instead manifests after the test is run
and it fails. The test duplicated in regressions gets merged into
itself, duplicating the entire list of run_opts. This commit
uniquifies the list of tests in regressions.
The second commit removes duplicate tests in the ci regression
target of otbn.

@andreaskurth , I have merged this PR. If you have any more CRs, I can address them in subsequent PRs.


Include query params in filterflex request forwarding

What
Includes query params when proxying requests in the filterflex package.
How to review
Check code quality.
Who can review
Anyone.

For context, this is to ensure that the pagination changes made here work when proxied.


[FLINK-14287] Decouple leader address from LeaderContender

What is the purpose of the change
This PR is based on #9812.
Change LeaderElectionService#confirmLeadership to accept leader address so that
the LeaderContender does not need to know the address of the potential leader
before gaining leadership. This allows to decouple the leader election from the
actual leader component.
Verifying this change
This change is already covered by existing tests, such as (please describe tests).
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Since we decouple leader address from LeaderContender, shall we remove #getAddress from LeaderContender?

Yes @TisonKun. This is actually one of the next PRs I will open. It actually replaces LeaderContender#getAddress with LeaderContender#getDescription.

@flinkbot run travis

Thanks for the review @TisonKun and @azagrebin. Addressing your comment and merging this PR.


"The term 'json-server' is not recognized as the name of a cmdlet..." even after installed

i'm getting a message of the error below,  even tough i've installed and test it both locally and globally.
"The term 'json-server' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, see if the path is correct and try again."
in the print screen you can see in details my node -v and npm -v, i'm running on windows 11, in a powershell.
anyone know how can i fix tis?
thanks

that works, thanks! Can you explain to me what the problem was? :}

Thanks for solving my issue, i have been searching how to resolve this issue in chatgpt,google,stackoverflow,youtube etc.. etc .since from morning i keep on searching and got fuc**d up.

This issue happening because of the alpha version of json-server  installed when we run npm i json-server. So, I have checked that the alpha version doesn't have a json-server executable. That's why json-server is not recognized.

Fixed, thanks for the heads up

Thanks
that fixed


Remove non-paged relationship methods from ManagerInterface

What
Remove non-paged methods from ManagerInterface
Why
Does the additional implementation overhead really benefit the Manager? Right now, a manager has to implement all four variations of the getWithRelationship* methods - with equivalent results. The host selects which method it calls based on the traits of the relationship. The runtime overhead of the pager doesn't seem prohibitive, so the hope is that removing the non-paged variants from ManagerInterface greatly simplifies the implementation on the manager side as they no longer need to match results between paged and non-paged versions. We can still present non-paged conveniences for the Host as we do with the non-callback versions of the other methods.
ACs

Non-paged methods removed
Paged removed from method named

What about having paging related stuff as optional arguments to the same functions? From our point of view, in most cases paging isn't required on backend side but I guess there are cases where it is, just not that much.

What about having paging related stuff as optional arguments to the same functions? From our point of view, in most cases paging isn't required on backend side but I guess there are cases where it is, just not that much.

Sorry, forgot we'd not put that much detail here (updated now). The motivation was that as it is today, the manager has to implement all 4 versions of the method with equivalent results. The overhead of the pager at runtime didn't seem too concerning as these are likely to be lower call volume methods than resolve*, so could we make the manager's life easier if you only have to implement 2 methods, with one result style (paged) and we can provide the conveniences for the host in the middleware. If we bundled it into args, you'd still have to implement both return types. Just wondered if limiting it to one type would save you a load of extra coding (it did in our simple, albeit contrived, cases).
(* though USD may affect that if we want to support the whole alternative asset thing).


Core styling changes in Foundry v9 cause some minor UI glitches

Some upstream changes to the core css file used by Foundry in v9 break our current tab styling on the various sheets.
Current look:

Foundry v9:

The fix should be simple (a single line of css), but we might need to investigate whether this change can be made pre v9 release or if it will need to wait for v9 to become stable.

Ok, I have determined that the fix for this doesn't affect v8 at all. So, I've already merged in the fix for development.


Bug: Rubberbanding when minimizing the window

When maximizing the game window after minimizing it again one runs into a nasty case of rubberbanding. The characters jumps all over and movement is lagging. The game is playable but not enjoyable. Apparently this is a Godot networking issues so a workaround me be found there.

Is the player teleporting or just taking forever to move when you click somewhere?
Because i think this is due to the buffer clogging up or the timestamp part of movement getting out of sync (since attacking enemies seems to work just fine).
The game and server run fine on my end, but the inputs get some extreme delay.

Is the player teleporting or just taking forever to move when you click somewhere? Because i think this is due to the buffer clogging up or the timestamp part of movement getting out of sync (since attacking enemies seems to work just fine). The game and server run fine on my end, but the inputs get some extreme delay.

The player is just stuttering when moving. Like moving in jumps with 1-2 seconds of delay. Same thing happens when minimizing Guild Wars 1 actually. Attacking still works normally.

Huh, i wonder if this is OS related.
Sounds like the game's connection is being throttled.

I was wondering the same if it's OS related. Like that the priority of the minimized screen is lowered and thus not all packets being received anymore, making the game go out of sync.


Can't get to work on new vscode installation

Platform: Windows 11
Tried : Reinstalling the extension and one-by-one trying both Custom CSS JS Loader and Apc Customize UI++ install methods while having one only of them installed and changing to the respective method and enabling animations + reloading.
Help would be appreciated :D

Have you tried running Animations: Install Animations from the command palette?

Did you run as an administrator? That may fix all of your issues.你是以管理员身份运行的吗？这可能会解决你所有的问题。
this really work! thaks a lot