fmt: map printing sort does not deterministically sort differing types

What version of Go are you using (go version)?

$ go version
go version go1.12 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
fmt.Println(map[interface{}]string{
    3: "3",
    "a": "a",
    2: "2",
    "c": "c",
    1: "1",
    "b": "b"
})

What did you expect to see?
1:1 2:2 3:3 a:a b:b c:c

What did you see instead?
Non-deterministic result; differing types always compare to -1, so the result depends on map iteration, which is pseudo-random.

It's possible that I'm just misinterpreting the documentation here. The release notes say:

Interface values compare first by reflect.Type describing the concrete type and then by concrete value as described in the previous rules.

I read this as "values compare first lexicographically by type name, then by their concrete value." However, fmtsort.compare instead does:
c := compare(reflect.ValueOf(aType), reflect.ValueOf(bType))
if c != 0 {
	return c
}

Which results in the *reflect.rtype values being compared by their machine addresses. But since a and b have the same type, their addresses will be equal (not sure if this is always the case), so this compare is ineffectual.
I think the correct code implementation would be something like:
aConcreteType := aVal.Elem().Type().String()
bConcreteType := bVal.Elem().Type().String()
c := compare(reflect.ValueOf(aConcreteType), reflect.ValueOf(bConcreteType))
if c != 0 {
	return c
}

which produces deterministic output. I'm happy to submit a pull request for this if so desired.

Thank you @lukechampine for this report!
Kindly paging @robpike @rsc @mvdan.

What does text/template do in this scenario? If the template package is deterministic and fmt isn't, that's very likely a bug to fix in fmt.

The text/template package also is not producing deterministic output:
https://play.golang.org/p/wpbTEx1z9E9
package main

import (
	"os"
	"text/template"
)

func main() {
	tmpl := `{{ range $k, $v := . }}Key:{{ $k }}, Value:{{ $v }}, {{ end }}`
	t := template.New("hello")
	mp := map[interface{}]string{
		3:   "3",
		"a": "a",
		2:   "2",
		"c": "c",
		1:   "1",
		"b": "b",
	}

	tt, err := t.Parse(tmpl)
	if err != nil {
		panic(err)
	}

	if err = tt.Execute(os.Stdout, &mp); err != nil {
		panic(err)
	}
}

Output:
Key:1, Value:1, Key:2, Value:2, Key:a, Value:a, Key:3, Value:3, Key:b, Value:b, Key:c, Value:c,

The result of go1.12 run for
package main

import (
	"os"
	"text/template"
)

func main() {
	tmpl := `{{ range $k, $v := . }}Key:{{ $k }}, Value:{{ $v }}, {{ end }}`
	t := template.New("hello")
	mp := map[interface{}]string{
		3:   "3",
		"a": "a",
		2:   "2",
		"c": "c",
		1:   "1",
		"b": "b",
	}

	tt, err := t.Parse(tmpl)
	if err != nil {
		panic(err)
	}

	if err = tt.Execute(os.Stdout, &mp); err != nil {
		panic(err)
	}
}

Key:1, Value:1, Key:2, Value:2, Key:a, Value:a, Key:b, Value:b, Key:c, Value:c, Key:3, Value:3

@mvdan it looks like text/template just calls out to fmtsort:
https://github.com/golang/go/blob/b5a68a9e414dc1d412d623f80c54aafe3ada0f14/src/text/template/exec.go#L361-L369
So my proposed fix will also change the behavior of text/template.

@gopherbot, please open a backport issue for 1.12.


Turning on expansions by clicking its icon in SE

I have an idea for the future release (not now) which would make turning expansions easier and faster for a user.
The idea is, clicking an expansion's icon either:
a. moves a user directly to the Select Content's submenu with the expansion, where he/she can turn it on or off; clicking Back button causes a return to the SE (requires knowing what was a previous user's location in the app) to the same position (no reload of the list! Just a reload of the scenario's line).
or
b. toggles the expansion's activation; it'd require refreshing the scenario's line (not the whole list).

I'm not sure this enhancement is really required, this sounds like a very small improvement.
Most users would just go to select content.
And for B, I think some people would just press expansions icons by mistake while scrolling, and they won't understand what's happening with the refresh, and why they have the content activated.
And with the size of the expansions icons, this would not be usable on any mobile device.
I would put this one at the end of the todo list.
Please share your thoughts if you think otherwise.

Of course. It isn't something major.
Below I write my thoughts about the whole idea for the future reference.
Now knowing the app I can only imagine what it's to be a fresh user. But let's try:

Let's say, I have a physical base game and two expansions.
I run the app and click New game because I don't know what 'Select Content' does and I am interested in starting a new game immediately.
I want to play a game which uses all of my expansions so I look for a scenario which all of the icons associated with them (here the hover effect https://github.com/NPBruce/valkyrie/issues/1073 would be handy if I don't know the icons).
I find a suitable scenario but I notice that I am missing some expansions.
At this point, I need to think "how can I turn them on?". What I would do, would be clicking/tapping the expansion's name. If that doesn't work, I'd go back and check other menu options to find the answer and eventually I'd click 'Select Content'.

So, yes, it'd be a small improvement but the one that could make it easier and faster to turn on missing expansions.
In terms of usability.
I wouldn't be afraid of the problem of clicking icons by mistake if they are displayed clearly as buttons instead of text. Also activating/deactivating possibility to play a scenario should be clear after from one to two clicks. I hope people are that intelligent :).
I'd be rather worried about two things:

Strange behaviour of UI when clicking the buttons which I think could be hooked under your statement 'they won't understand what's happening with the refresh'. After a user clicks an icon it "magically" disappear and appear somewhere else in the line. It isn't something common, might be unexpected and confusing.
As you mentioned, the size of the buttons. Not even just for mobile devices but all. First of all, as mentioned above, the icons should be buttons. Second, they should be more separated than they are now (fortunately, there is enough space in terms of width for that). But it still leaves the problem of the height of the buttons as there isn't enough space as for now. A scenario line could be a little larger but it'd require testing.

Regarding the height (vertical size) of each scenario line, the purpose of this first version of scenario explorer was to keep the line as small as possible, in order to show as many scenarios as possible, while it stays practical and easy to read.
Making this bigger would allow more flexibility for improvement, but less scenarios on screen.

So maybe something else.
The longest scenario's name so far is the follwing:

About 46 characters.
And the scenarios with the numerous expansions are:

4 in total.
If the number of expansions was all 5 expansions with a little bit smaller font (~2 points smaller) a scenario line could look something like that:

The 'Missing Expansions' text could be removed and instead the previous version of the red/black icons could be used. But this time the expansions' icons should look like buttons/something clickable.
The design wouldn't require refreshing the whole line but just the icon's color and the play/stop button.
If the red icons are not clear enough that there is something wrong and that's the reson why there is the 'Stop' button there, a hovering effect on the 'Stop' button could be created (https://github.com/NPBruce/valkyrie/issues/1073) with an explanation why the scenario is not playable.
It'd be possible to earn more vertical space and put even more scenarios on the screen :).

I have an important question to the topic. I've just opened Editor to check how many expansions exist and I was surprised seeing this list:

Why so many of them have the same icon? If they are marked as 'the same', would I be able to play any scenario with a moon icon after buying just one expansion of the kind? If yes, why the list of scenario is not narrower if it doesn't matter? If no, why they are marked the same (or almost the same)?

You did not take into account the number of flags.
I moved the expansions below the title to leave some space for the flags.
Regarding the expansions, it is just the way it has been released by FFG I guess.
It is up to the scenario author to decide if the player should have the full expansion or just part of it (like just the tiles, or just the monster for example).

You're right again. And I had a good example right above :p.
To that issue there a simple solution:

Limit a title to 50 characters.
Create the languages part in a way the languages' icons wrap is necessary as presented in the below image.

But there is still this issue of possible dozen of expansions' icons... If there were just 5, it'd be a good design but no one can guarantee that :|.

Coming back to the expansions list. From what I understand, MoM1EI has a different set of tiles/monsters/etc than others with the key icon, right?
So, could you elaborate:

Why are they marked the same?
How would a user know which expansion he/she is missing if the only thing he/she sees is the icon?
I've just checked with a local scenario. I set Required Expansions to MoM1ET. After that, I activated RN expansion in the 'Select Content'. Why the scenario is active (I can play it) although the scenario required a different expansion and the only thing that both have in common is the icon? Aren't they different thing with different items?

If everything is fine, shouldn't the list of icons be limited to just these 5 icons instead of having something like that

two of the same icons because someone selected the expansion with a candle icon and SM expansion? It's a little messy here.
Of course, it's a topic for another big ticket but could we discuss it shortly here for the issue's reference?

RN contains MOM1ET MOM1EM MOM1EI
SM contains CotWT CotWM CotWI FAI FAM FAT

two of the same icons in the single scenario because someone selected the expansion with a candle icon and SM expansion? It's a little messy here.

Yes if you select SM as a required expansions in your scenario, you don't need to select the others.

Thank you, @BenRQ, for checking that. I didn't have time nor strength; it was almost midnight my time.
So that makes sense now and explains everything.
There is only one solution to it which is a good one, especially for a user.
Right now, as I said before if a creator selects MOM1ET as a required expansion you only see a key icon which tells you nothing and you may think 'ok, I have MOM1EM so I can play' but you can't as the scenario won't work with the expansion selected.
Solution: we are then coming back to my previous proposition of the hover effect with information on hovering an icon 'what kind of expansions from the type are used/what kind of expansion from the type you're missing' helping a user.
By doing so, it also helps us as we can get rid of displaying all expansions selected by a creator and instead display only max of these 5 icons when necessary and gain needed space for the proposition
https://user-images.githubusercontent.com/7532602/53086381-ddc4a100-3569-11e9-9c86-9cad00489222.png

I can imagine the enhancement requires a lot of work and is not something that will be commonly used (rather ones in a while when you buy a new extension). So it can put this at the end of the todo list but I think it'd be better to develop the hover effect (https://github.com/NPBruce/valkyrie/issues/1073) to at least display a list of expansions associated with the icon because, as shown above, it may be problematic to distinguish an expansions.

I agree hover effect would be quite useful.


Screen Flickering

Issue Type: Bug
In ubuntu 22.04 When using vs code in full window model screen is flickering
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:24.808Z)
OS version: Linux x64 5.15.0-27-generic
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 905)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 1

Memory (System)
11.58GB (0.15GB free)

Process Argv
. --crash-reporter-id c41bfa3f-0a03-427e-9bdd-8886ed55586c

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Is this in a VM ? Also is this with wayland or X11 session ?

No. I am using VS-code on my laptop.

I think this bug is related with Ubuntu 22.04 and has nothing to do with VS Code. I have experienced the same flickering on other apps.

Does the issue happen with chromium browser on your device ?
/gifPlease

@BuLLHACK I only experienced this issue with vs code. When the screen is flickering on vs-code if the change application flickering stops and then go to vs-code it's start flickering again.

@deepak1556 no it's only happening with vs-code.

Will try to update gif or screenshot when next time if happens.

@wmcmurray I don't use many other applications only firefox and vs code. maybe due to this, I have not noticed it with other applications.

This is a known bug in 22.04, the following steps may help you get rid of the flickering:
Open /etc/default/grub
Add these parameters to GRUB_CMDLINE_LINUX_DEFAULT:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" i915.enable_dc=0 intel_idle.max_cstate=2
Save the file and update grub
sudo update-grub
Then restart you computer
Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/comments/24


Move service resolving to .resolver, non-protect stuff

Allows .endpoints to only contain endpoint methods and data. .resolver will now resolve the user and service and may call the respective endpoint.
Additionally make the following non-protected:

endpoints._resolve_service (-> resolver.resolve)
endpoints._main (-> resolver.resolve_and_call)
endpoints._services (-> endpoints.SERVICES)

Travis will pass once merged. Problem has been fixed on main branch.


rho-calc/Rholang programming on Holochain

Holochain has many of the same design objectives as RChain. Like Rosette, Holochain is based on an actor model. The aim is to generate Holochain apps from the rosette output of the Rholang compiler.
To this end we have engaged in a cooperation with DigLife.com and Holochain.org in the Social Ledger trial.

Holochain is based on an actor model? Help me find any documentation about that? I looked for a few minutes without luck.

The white paper here can be  a good resource. Quite technical for me yet. Also the FAQ might help. I think it has element of concurrency (actor model) as RChain.

@jimscarver i see a reminder for the meeting but how can one join?

raymond will be in brooksville around jan 20th and we hope to have a meetup in the tampa bay area while he is here @patrick727
activity is in the holochain mattermst w.r.t. our collaboration.

@jimscarver @patrick727 When the meetup date gets nailed down please post it.

I see no movement in over six months.

I do not think this issue is closed. It is an issue looking for a team to embrace. It is an activity encouraged by Greg in a debrief/standup. Only interest has been express from both holochain and rchain but noone has stepped forward yet to take action. The issue is very open.

Open issues represent plans to complete work. I see no plan here. Monitoring issues takes time and effort. With no indication that anyone intends to make progress, this issue isn't worth tracking as open.

If we intend to scale and offer opportunity to participate we want to list issues that have been staffed as well as those that have not.  If managing stale issues is the issue, I think that should be delt with separately.
We can ask if rholang support on every platform is an objective of the coop. Or if interoperation with holochain is desired. If ether answer is yes the issue should remain open if we intend that someday it will be completed.

I read the whitepaper and watched a couple of the short videos. I see lots of stuff about agents, but nothing about the actor model.
Having this issue around hasn't catalyzed any momentum in just about a year.
And I don't see a separate plan emerging for dealing with stale issues. So I'm continuing with my "open issues represent plans to complete work" process.


Unable to use Rails 5.2.2

Getting this in 5.2.2 also
Bundler could not find compatible versions for gem "actionmailer":
  In Gemfile:
    rails (~> 5.2.2) was resolved to 5.2.2, which depends on
      actionmailer (= 5.2.2)

    refinerycms-authentication-devise (~> 2.0) was resolved to 2.0.0, which depends on
      actionmailer (< 5.2, >= 5.0.0)

Duplicate of refinery/refinerycms-authentication-devise#39


[TODO] Add getting started resources for new hackers

In the main readme and/or hackers.md file we need to add resources for people new to Ethereum/Solidity/Web3 development.
This will be somewhat subjective and opinionated, and we all likely have ideas, but let's make a start and handle the complete consolidation when merging the PR, likely easier to all work in the same branch, whoever starts the PR first.

Started here https://github.com/ethberlinzwei/KnowledgeBase/pull/27

continued in #37

also link everything that's in ./resources

Added more in #51


Help with installing on Mac

Hello! I apologize for the basic question, but I'm trying to figure out how to install this plugin on Catalina. I'm stuck at the step where I need to specify the VMD plugin directory—I never installed a VMD plugin before. I'm also not sure where the plugin headers and system-specific molfile libraries reside. These need to be defined when using cmake.

Plugins get installed into the same location as VMD. You should know where you installed VMD on your version of macOS (since you are also using Catalina, I guess it is a port)... it is probably somewhere in your Applications.
From the README:

VMD_PLUGIN_INCLUDE_PATH and VMD_PLUGIN_MOLFILE_PATH.

So, within your VMD installation, you need to do a find for molfile_plugin.h, which gives the VMD_PLUGIN_INCLUDE_PATH and for any built-in plugin like xyzplugin.so, which gives the VMD_PLUGIN_MOLFILE_PATH.
I would recommend trying to point to the VMD installation with VMDDIR first, though, as cmake can do this search automatically with the right hints. VMDDIR points to the base vmd directory that is common to Linux and macOS. The default guess for VMDDIR is /Applications/*/Contents/vmd on macOS, but you should set it to the appropriate value for your system, either as an env var or with -DVMDDIR.

Thanks a lot! That worked. It turns out I didn't realize that the Applications folder was the "installation" directory. If anyone else comes into this issue, just type in VMDDIR=/Applications after dragging the .app to your default Applications directory. cmake takes care of the rest; the plugins directory is a inside a subfolder of the .app in your Applications folder.


HTML5 target generates incorrect code for native JavaScript arrays in some cases

I ran into this issue in Haxe code generated by Stencyl. This haxe code:
Engine.engine.getGameAttribute("Level States").insert(Std.int(0), 1);

Generates the following JavaScript code:
com_stencyl_Engine.engine.getGameAttribute("Level States").insert(0,1);

getGameAttribute() returns a native JavaScript array, which doesn't have an insert() method. The problem seems to be that getGameAttribute() is declared this way:
public static function getGameAttribute(name:String):Dynamic

so the compiler can't know that .insert() should be mapped to something else.
Seems to me like the JS runtime environment Haxe uses should include an Array like class that can be used instead of the native JS Array.

This is probably a Haxe issue, rather than a problem with openfl or lime.

The problem isn't related to lime or Haxe, it seems to be a your code issue. When you (Stencyl in this case) use Dynamic the compiler won't be able to infer the type, apply optimizations,... It's a way to tell the compiler that you know what you are doing and to not bug you about anything. http://haxe.org/manual/types-dynamic.html
For that to work, you will need to cast it to the correct type.
cast(Engine.engine.getGameAttribute("Level States"), Array<Dynamic>).insert(Std.int(0), 1);

A smaller example: http://try.haxe.org/#CFe66

OK, I get the impression that the correct answer is "Haxe isn't a dynamically typed language, so stop trying to treat it like one."
It's somewhat surprising that accessing Dynamic objects works sometimes, but not at other times, and that this discrepancy seems to be due to an optimization - manipulating Haxe Array objects so they map to JavaScript Array objects. The problem could have been avoided if the Haxe JavaScript runtime included its own Array type, but that would probably be a bad idea for a whole lot of practical reasons...

Yeah, I think it's a matter of things that are compile-time or runtime features. For example, getters and setters really are "get_" and "set_" function calls.


Add counter to Task IO splice

Hello,
This is implementation I did so that counter can be used with task_io_splice call.
https://github.com/heiher/hev-task-system/compare/master...vavrecan:hev-task-system:master
Usage is simple them,
    size_t received;
    size_t sent;
    hev_task_io_splice_counter (cfd, cfd, fd, fd, 8192, task_io_yielder, self, &sent, &received);

Let me know if you find it useful or if it makes sense to integrate, I can make PR then.
Thank you

Thanks for sharing your implementation. Sorry, I have no plans to integrate it into the generic io splice at the moment. However, I'll write a customized example that override the generic implementation in hev-socks5-server to share with you.


docs: bump v0.1.0

v0.1.0 (2020-12-14)
:rocket: Type: Feature

components, tsconfig

#147 refactor(packages/components): use native onClick handlers (@9renpoto)

Committers: 2

Keisuke Kan (@9renpoto)
Tatsushi Kiryu (@tkiryu)

diff: https://github.com/caddijp/frontend/compare/v0.0.18...release

published :)

Rocket speed. :)
Thank you!


bind: address already in use

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
supabase start fails randomly due to a port already being in use. It seems to be a timing issue as it only happens every other time when running the Github Action below.
This is the error generated:
Digest: sha256:48d2fabef1b0b1e8f9b208518008686a1cd336503af4fd6f62e169268ed9066e
Status: Downloaded newer image for ghcr.io/supabase/postgres:<IP_ADDRESS>
failed to start docker container: Error response from daemon: driver failed programming external connectivity on endpoint supabase_db_jobmate (8a76852f7f3f62ebe3fbd7ebf9cff92182749ee130513dc2b2c51d2b672a422c): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:54322: bind: address already in use
Try rerunning the command with --debug to troubleshoot the error.

To Reproduce

Create a Github Action

name: "Push migrations"
on:
  push:
    branches:
      - main

jobs:
  test:
    runs-on: ubuntu-latest

    permissions:
      # Required to checkout the code
      contents: read
    env:
      SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
    steps:
      - name: Checkout repo
        uses: actions/checkout@v4
      - uses: supabase/setup-cli@v1
      - name: Link Supabase project
        run: supabase link --project-ref ${{ vars.SUPABASE_PROJECT_ID }} --password ${{ secrets.SUPABASE_DB_PASSWORD }}
      - name: Start Supabase
        run: supabase start
      - name: Push migrations
        run: supabase db push --password ${{ secrets.SUPABASE_DB_PASSWORD }}

Run the action

Expected behavior
I expect this action to run successfully every time.
Full logs
5_Start Supabase.txt

This is intermittent but common for us. I don't think it's every other time, it will often fail many times in a row, but it does sometimes succeed.

I've made some tweaks on the assumption that this is GHA keeping a "hot" function around to run the workflows, and so docker's already running and messing with things. None of this is robustly tested across test failures or concurrent workflows from other branches.
Try to start up more carefully
      - name: start or reset supabase db server
        run: |
          set +e
          supabase status
          if [ $? -eq 0 ]; then
            echo "Supabase is already running, resetting database..."
            supabase db reset
          else
            echo "Supabase is not running, starting database..."
            supabase db start
          fi
          set -e

Try to clean up by stopping supabase afterwads even in cases of test failures
      - name: cleanup supabase db service
        if: always()
        run: npx supabase stop

and also limit concurrency
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true


Refactoring of Atom Centered Radial Symmetry Function Modules

Description
This refactoring PR will make the Radial Symmetry Function class more modular and allow different distributions. The specific implementation associated with different Neural Network Potentials will be subclassed from a generic implementation.
Todos

[ ] Generic RBF class
[ ] Subclass for specific Neural Network Potentials

Status

[ ] Ready to go

Codecov Report

Merging #80 (d4c5166) into main (6b3b6ee) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

Additional details and impacted files


Update dependencies and build steps

Thank you. Looking forward to seeing this being merged, so I can catch up on pwsh on my Mac and go beyond PowerShell 7.2.11. Thanks for maintaining this for us on non windows powershell core versions.

The changes here have been superseded by https://github.com/jborean93/PSWSMan/pull/6


RNAseq input box should disallow the same fastq in both boxes

It's possible to put the same fastq file in the read file 1 and read file 2 slots in the paired end library

closed as a duplicate of #300


oauth user objects and friends in user migrator

Solves: https://github.com/CartoDB/cartodb/issues/14492
It works together with: https://github.com/CartoDB/cartodb-central/pull/2397

Acceptance 🔴

private method 'create_dataset_role' called for Carto::OauthAppUser <- seems we need to do that method public. I'm going to change it in staging and continue with acceptance

Acceptance 🔶

✅  I migrated successfully a user with several access tokens (including datasets access). After migrating all the previous access token worked as expected and I could retrieve more.
🔴 Migrating an organization fails with the following error

I suspect the reason is because we are creating the oauth_app_organization before the oauth_app has been created.
I guess this can be solved by saving the oauth_app_organizations in the same way as the groups and notifications, right after the user metadata has been saved, because there is where we are creating the oauth_app. See this and this


The examples in TCGC do not read the client parameters such as endpoint

Here is an example:
https://github.com/Azure/autorest.csharp/blob/f7828c6365fbde2401634b10a6fa0b52dc368ac1/samples/AnomalyDetector/examples/v1.1/TrainModel.json#L5

similar with this one: https://github.com/Azure/typespec-azure/issues/1419


Running :!program from VimEnter sends input to the program

Describe the bug
Executing a command with :! from VimEnter auto-command sends input to that process.
To Reproduce
Make your .vimrc look like this:
au VimEnter * !cat > wtf

And just start vim (use Ctrl+D to finish cat).
You'll see output like this:
^[[2;2R^[[3;1R^[[>41;367;0c^[]10;rgb:ffff/ffff/ffff^G^[]11;rgb:0808/0808/0808^G

and wtf file in current directory containing the same:
00000000  1b 5b 32 3b 32 52 1b 5b  33 3b 31 52 1b 5b 3e 34  |.[2;2R.[3;1R.[>4|
00000010  31 3b 33 36 37 3b 30 63  1b 5d 31 30 3b 72 67 62  |1;367;0c.]10;rgb|
00000020  3a 66 66 66 66 2f 66 66  66 66 2f 66 66 66 66 07  |:ffff/ffff/ffff.|
00000030  1b 5d 31 31 3b 72 67 62  3a 30 38 30 38 2f 30 38  |.]11;rgb:0808/08|
00000040  30 38 2f 30 38 30 38 07  3a                       |08/0808.:|
00000049

Expected behavior
No unexpected output on the screen and empty wtf file.
Environment (please complete the following information):

Vim version: 8.2.2876
OS: Slackware 14.2
Terminal: xterm

Additional context
This looks a lot like control sequences, although I'm not sure whether they are coming from Vim itself or that's a terminal responding to some query from Vim. I suspect the latter.

Describe the bug
Executing a command with :! from VimEnter auto-command sends input to that process.
To Reproduce
Make your .vimrc look like this:
au VimEnter * !cat > wtf

And just start vim (use Ctrl+D to finish cat).
You'll see output like this:
^[[2;2R^[[3;1R^[[>41;367;0c^[]10;rgb:ffff/ffff/ffff^G^[]11;rgb:0808/0808/0808^G

and wtf file in current directory containing the same:
00000000  1b 5b 32 3b 32 52 1b 5b  33 3b 31 52 1b 5b 3e 34  |.[2;2R.[3;1R.[>4|
00000010  31 3b 33 36 37 3b 30 63  1b 5d 31 30 3b 72 67 62  |1;367;0c.]10;rgb|
00000020  3a 66 66 66 66 2f 66 66  66 66 2f 66 66 66 66 07  |:ffff/ffff/ffff.|
00000030  1b 5d 31 31 3b 72 67 62  3a 30 38 30 38 2f 30 38  |.]11;rgb:0808/08|
00000040  30 38 2f 30 38 30 38 07  3a                       |08/0808.:|
00000049

Expected behavior
No unexpected output on the screen and empty wtf file.
Environment (please complete the following information):

Vim version: 8.2.2876
OS: Slackware 14.2
Terminal: xterm

Additional context
This looks a lot like control sequences, although I'm not sure whether
they are coming from Vim itself or that's a terminal responding to
some query from Vim. I suspect the latter.

Yes, Vim request status from the terminal, and since there is no side
channel these are mixed with keyboard input.
Vim does try to read the escape codes before starting the program, but
this is timing sensitive.
A simple way would be to not invoke the program directly from VimEnter,
but using a timer to run it a tiny bit later.
Hmm, perhaps we could have an autocommand event that is triggered when
the codes that are expected have been received.  Problem is though that
some requests may be unanswered, and then it would never trigger.
--
hundred-and-one symptoms of being an internet addict:
182. You may not know what is happening in the world, but you know
every bit of net-gossip there is.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

On 2021-07-19, Bram Moolenaar wrote:

A simple way would be to not invoke the program directly from VimEnter,
but using a timer to run it a tiny bit later.
Hmm, perhaps we could have an autocommand event that is triggered when
the codes that are expected have been received. Problem is though that
some requests may be unanswered, and then it would never trigger.

You could use a timeout to fix that.  A few seconds should be
sufficient.  If a user's terminal never responds and the user gets
tired of waiting that long, then they don't need the autocommand
anyway.
The timeout should be settable, and there should be a way to
determine whether the autocommand was triggered by the terminal
responses or by the timer expiring.  Some v: variable, perhaps.
Maybe just check for the presence of all the expected responses.
Regards,
Gary


Dplay ERROR: Unable to extract info url

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.08.04. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.08.04

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://it.dplay.com/nove/lisola-di-adamo-ed-eva-alle-origini-dellamore-xxx/stagione-1-episodio-7/']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2018.08.04
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg N-91407-g3c4af577aa, ffprobe N-91407-g3c4af577aa
[debug] Proxy map: {}
[debug] Using fake IP <IP_ADDRESS> (IT) as X-Forwarded-For.
[DPlayIt] stagione-1-episodio-7: Downloading webpage
ERROR: Unable to extract info url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpckoq891b\build\youtube_dl\YoutubeDL.py", line 792, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpckoq891b\build\youtube_dl\extractor\common.py", line 502, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpckoq891b\build\youtube_dl\extractor\dplay.py", line 316, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpckoq891b\build\youtube_dl\extractor\common.py", line 972, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract info url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description of your issue, suggested solution and other information
I cannot download anymore from Dplay site.
The error "unable to extract info url" occures.
Can it be solved?

Authentication is not supported. Pass authenticated cookies from browser.

How can I do that?


Fix behavior of color picker on sensor blocks

Resolves
https://github.com/LLK/scratch-blocks/issues/1381
Expectation:
Users expect behavior to mimic that of color picker found in paint editor.
Upon tapping or clicking in the color range of the slider, the thumb should move to that position
Actual Behavior, 2 issues:

For hue and brightness the thumb moves incrementally while the mouse button is held down.
The saturation does not work at all and can only be adjusted by dragging the thumb.

Proposed Changes
For issue 1:
a)  All 3 sliders ( Color, Saturation, Brightness ) should call setMoveToPointEnabled(true) .
For issue 2:
a)  orginal code was using range of  0 to 1 using step of 0.001.  However the sliderbase class rounds up steps so can only use steps of 1 or greater, this requires a max range to be scaled up as well, which in turn requires an external conversion (SATURATION_CONV) to be used to convert back to range of 0 to 1 outside the slider.  Note that this issue and solution is not enabled when setMoveToPointEnable(true) is called.
However this fix should remain in case in future it is decided that incrementally thumb movement is desired again.
Reason for Changes
Provide consistent color pick behavior with that on paint editor and as reported in
original issue on scratch-gui.
Test Coverage
Test manually using Chromebrowser on test file
file://.../scratch-blocks/tests/vertical_playground.html

drag 'touching color' block from sensors category onto workspace.
click on color,  color picker dialog pop ups.
move mouse pointer to some part of colored range bar for each of Color, Saturation, Brightness
Click or press down on left mouse button.

Expectation:

thumb to move to position
value to also be adjusted base on new thumb position
Results
passed with minor issue

Minior issue:
Repeated clicking in color range will cause thumb to move up and off of slider!
I traced this down to an issue with google ui sliderbase and its animation logic.
Issue will be submitted to github on that repo shortly later.
The issue is revealed because scratch uses thumb style property of margin-top: -1.
However, I believe this is a bug in google ui sliderbase.js, not in scratch code.

Issue and PR posted regarding minor issue mentioned above.
https://github.com/google/closure-library/issues/876

Thanks @ivanixgames! We'll take a look at this soon. Sorry for the slow response.

@paulkaplan
The saturation conversion is not needed if setMoveToPointEnabled is used.
That patch is only if the original intended behavior was desired.
For the drifting issue. if you want to fix in css,  make sure margin-top is not set or set to 0px  for horizontal slider, and margin-left is left unset or set to 0px for vertical slider.
See https://user-images.githubusercontent.com/858678/36078378-4a4e5a0e-0fb0-11e8-8abb-ae6ef686261d.png

@ivanixgames cool! Would you mind removing the saturation thing then, because we do want to use setMoveToPointEnabled?

@ivanixgames cool! Would you mind removing the saturation thing then, because we do want to use setMoveToPointEnabled?

Also @ivanixgames I found that if you just change margin-top: -1px to top: -1px (since it is position absolute) that the sliders don't drift but are still positioned correctly. So if you could make those two changes (removing the saturation change and changing margin-top to top in css.js line 837) we can merge this PR. Thanks for tracking down this issue!

@paulkaplan   Not mind at all, just  give me about a day to make and retest the changes.  Cheers


Renaming the app doesn't work

This is the command i'm using to install the starter
cli-rn new Aiminaabee -b com.aiminaabee.pro -t rnn
However still the ios directory name is RNNStarter.
I tried with sudo too.
any ideas?

@Yasir5247 I can not reproduce this. When I run the command you sent I get the following

i'm not sure why it cant file the file as seen the screen shot

@Yasir5247 I think react-native-rename doesn't support Windows. If you look closely, you will see that Windows has D:\node\MoonApp path, however react-native-rename is trying to access D:/node/MoonApp where slashes are different. Probably this is what causing a problem.
Try using react-native-rename-next which, as they state, has Windows support :)

I couldn't get it on my mac so i tried using windows.  doesnt have to do anything with NPM or node version.
mine is:
node: v16.13.1
npm: 8.3.1

did you try react-native-rename-next?

@kanzitelli hi, react-native-rename-next worked. Thank you as always. :)


chore(apps/staging/buildfarm): increase cpu and memory resource for shard workers

Changes

rename redis service name
increase resource for shard workers

Why

no need to add service suffix to service name since it's type is Service.
it will failed with OOM killing when build heavy targets.

/review default

/review default


Added a GitHub profile search engine app

Description:People can search the GitHub profiles. It can see their following, followers and repos
Tech stack: frontend technology
Screenshot:
After assigning issue make within 1 hour
About me: a GSSOC'24 extended member

Can you assign it to me under GSSOC'24 extended member


Add encoding iterator

This PR was inspired by discussion on https://github.com/rust-bitcoin/hex-conservative/pull/7
Add an encoding iterator BytesToHexIter. On the way there do a bunch of improvements, note carefully please the changes to error handling in commit: 51ba756 Improve error types.

I'm a little sad to see the entire internals crate being pulled in for a single instance of write_err. I'd suggest copying that macro into this crate, or even inlining it in the single location that it's used.
Other than that, ACK 0a3a01731788a2ae0ca19d6938e2a5e819d8c98d

Changes in force push:

Removed dependency on internals, copied the write_err macro instead.
Rebased and put formatting changes in the correct patch.

This branch is now used in the demo usage branch: https://github.com/rust-bitcoin/rust-bitcoin/pull/1833

cc @Kixunil will let you take a look before merging this

Hey @Kixunil do you have time to take a look at this one, would be cool to get it in a pre-release.

Changes in force push:

put typo fix in separate patch
changed associated error type trait bounds (I may have this wrong still, has Debug because I rekon its better and uses From because I could not work out the suggestion to use Into)
reduces trait bounds on iterator generics on HexToBytesIter

Rebased to pick up recent fuzzing changes and added a decode fuzz test for good measure.

I'm a little sad to see the entire internals crate being pulled in for a single instance of write_err.

I was playing around with creating bitcoin-units crate today and moved some stuff to internals. What's your heuristic on when its okay to pull in internals and when do we just inline/duplicate stuff?

Roughly

If we need more than 1 or 2 functions, or
we already depend on bitcoin or something that has internals in its dep tree

But I don't have a hard/fast rule.

Added got/want field names as a separate patch because the InvalidLength variant was not previously touched by this PR. (See git log of the last patch for serendipity :)

@Kixunil could you take another look at this?
Also, what do we need to do to get a 0.1 release out?

I'll undraft #12 if/when this goes in and from my perspective there is nothing else to do, we can release. @kixunil?

I'll undraft #12 if/when this goes in and from my perspective there is nothing else to do, we can release. @kixunil?

I just attempted to upgrade rust-esplora-client while trying to upgrade bdk and had to use bitcoin_internals to convert a vector to hex. We totally rugged everyone by not releasing this crate before we did the v0.30.0 release. The alternative, to add a dependency on hashes just to get hashes::hex::to_hex to super ugly when the same file is using use bitcoin::hashes::Foo.

@tcharding 100% agreed. In rust-elements I would up just copy/pasting the hex module from bitcoin-hashes into elements (and I delayed upgrading for like six months waiting for this to be released). In rust-miniscript I depended on bitcoin-private.

Rebased, no other changes. (Sorry for the noise, done to get the release PR upto date.)

I'm getting super tired of using CI to find my mistakes - why the f**k does cargo clippy --all-targets --all-features not work at the crate root when we have fuzz as part of the workspace?

Please baby Jesus, merge this PR already :)

Full disclosure, until 10 minutes ago this PR was unmergable because I had not actually removed all the ExactSizedIterator stuff that @Kixunil comment on above weeks ago - my fail.

Thanks for the review @apoelstra, was a bit sad to see I'd made so many mistakes after pushing for merge :(


Feature/systemd

I created an initial setup with a stakkr.sh bash script that loads the venv and then starts and stops stakkr. This wrapper script is then used by the systemd file stakkr.services to start and stop stakkr.
How to test;
Update the paths to your env (both files)
> sudo ln -s  stakkr.services /etc/systemd/system/stakkr.services
> sudo systemctl enable stakkr

If you need to reload systemd file after change
> sudo systemctl daemon-reload

So please provide me with some feedback about;

Where should we put the files. At this moment they are in the main folder.
Shoud we add option to stakkr to add stakkr to systemd.
Do we need to create a stakkr user? Is it needed, since all is running under docker?
Should we use env variable STAKKR_HOME for getting the correct stakkr Path? now the links are hardcoded to my local files. Or do you have an other idea?

Hi Roel,
It's a very interesting feature, thanks for it. A few remarks:

Better to remove the s from /etc/systemd/system/stakkr.services (for /etc/systemd/system/stakkr.service).
Why not having a config file where we would put the path and user of the stakkr instance to start such as /etc/stakkr.conf. Then no need to hardcode anything. That means also that we can have only one stakkr instance started .... do we need multiple ? In that case we can do a /etc/stakkr/ directory with a file per instance.
We can have a scripts directory at the root with a systemd subdirectory. That would contain : a README (to understand how to install the service), the bash script, the systemd file and a config example. No need to have a command for it.

Emmanuel

I updated according to your remarks.. Please check...
Open item is a user for running stakkr.

Thanks Roel, I have commited a few changes here : https://github.com/edyan/stakkr/tree/roelbindels-feature/systemd
In summary :

Put the doc in the right folder
Doc Rewrote to make copy of files and not symlinks (does not work with systemd)
Changed the location of scripts, to stakkr/tpls as it should be copied during stakkr installation or stakkr-init.

I am still facing an issue : it's not starting and not running with the right user (maybe it's linked). Everything is launched with root...


gitAndTools.transcrypt: 1.0.3 -> 1.1.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/transcrypt/versions.
These checks were done:

built on NixOS
/nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0/bin/transcrypt passed the binary check.
/nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0/bin/.transcrypt-wrapped passed the binary check.
2 of 2 passed binary check by having a zero exit code.
1 of 2 passed binary check by having the new version present in output.
found 1.1.0 with grep in /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0
directory tree listing: https://gist.github.com/74399ed2dc0f5e79c6face443cf11691
du listing: https://gist.github.com/6c7f5baa546117396d7b51993bf84dba

meta.description for gitAndTools.transcrypt is: '"Transparently encrypt files within a Git repository"'.
cc @elasticdog for testing.

Success on x86_64-linux (full log)
Attempted: gitAndTools.transcrypt
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0
gzipping man pages under /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0/share/man/
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0/bin
patching script interpreter paths in /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0
/nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0...
/nix/store/rnqjmp32pr8zq5y7bn9n0qcrnwg5qi82-transcrypt-1.1.0

Success on aarch64-linux (full log)
Attempted: gitAndTools.transcrypt
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0
gzipping man pages under /nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0/share/man/
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0/bin
patching script interpreter paths in /nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0
/nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0...
/nix/store/ivpml94mnzdwcipf4pq4p5vbayqwyp6a-transcrypt-1.1.0

Success on x86_64-darwin (full log)
Attempted: gitAndTools.transcrypt
Partial log (click to expand)
building
no Makefile, doing nothing
installing
post-installation fixup
gzipping man pages under /nix/store/qxby56318x9a2jppz092148m14rfp16v-transcrypt-1.1.0/share/man/
strip is /nix/store/r5mcn9vqq80v5pfqp45d7290cis7dwp4-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/qxby56318x9a2jppz092148m14rfp16v-transcrypt-1.1.0/bin
patching script interpreter paths in /nix/store/qxby56318x9a2jppz092148m14rfp16v-transcrypt-1.1.0
/nix/store/qxby56318x9a2jppz092148m14rfp16v-transcrypt-1.1.0/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/i9g6883w05pyj9aa4sl8hn945qyy6j53-bash-4.4-p19/bin/bash"
/nix/store/qxby56318x9a2jppz092148m14rfp16v-transcrypt-1.1.0


CLOUD-857: Add Helm Chart checkbox in PR template

CHANGE DESCRIPTION
Problem:
Changes made in the operator repository are not always reflected in the Helm chart repository, leading to inconsistencies between the two.
Cause:
This can happen due to manual oversight as there is no automatic synchronization between the two repositories.
Solution:
Add item in PR checklist to remind developers to add the necessary changes in Helm Chart repository.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PG version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

custom-extensions
passed

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
passed

monitoring
failure

one-pod
passed

operator-self-healing
passed

pitr
passed

scaling
passed

scheduled-backup
failure

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 19 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/907/commits/6174db72a513003dd9924d84a414898a4b5c8723
image: perconalab/percona-postgresql-operator:PR-907-6174db72a

Test name
Status

custom-extensions
failure

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
failure

monitoring
passed

one-pod
passed

operator-self-healing
passed

pitr
passed

scaling
passed

scheduled-backup
passed

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 19 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/907/commits/8f248aabd89bcb0df91f8f313f3f1060c6829d3d
image: perconalab/percona-postgresql-operator:PR-907-8f248aabd

Test name
Status

custom-extensions
passed

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
failure

monitoring
passed

one-pod
passed

operator-self-healing
passed

pitr
passed

scaling
passed

scheduled-backup
passed

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 19 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/907/commits/81fdc7b9a9824ef9b639823597cb247199406c5c
image: perconalab/percona-postgresql-operator:PR-907-81fdc7b9a

Test name
Status

custom-extensions
passed

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

pitr
passed

scaling
passed

scheduled-backup
passed

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 19 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/907/commits/81fdc7b9a9824ef9b639823597cb247199406c5c
image: perconalab/percona-postgresql-operator:PR-907-81fdc7b9a

Test name
Status

custom-extensions
failure

custom-tls
failure

demand-backup
failure

finalizers
failure

init-deploy
skipped

major-upgrade
skipped

monitoring
skipped

one-pod
skipped

operator-self-healing
skipped

pitr
skipped

scaling
skipped

scheduled-backup
skipped

self-healing
skipped

start-from-backup
skipped

tablespaces
skipped

telemetry-transfer
skipped

upgrade-consistency
skipped

upgrade-minor
skipped

users
skipped

We run 4 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/907/commits/67ace28d6bd791bb2d3e8fd75362d1a300db1627
image: perconalab/percona-postgresql-operator:PR-907-67ace28d6


compareScreenshot does not accept ActivityScenario but Activity instead

Using the example test theActivityIsShownProperly shown in the README with ActivityScenario does not work as intended
Expected behaviour
I expected using the default test in the README to work as intended when using ActivityScenario to launch the activity without any additional steps when using
class MyActivtyTest: ScreenshotTest {
    @Test
    fun rendersTheDefaultActivityState() {
        val activity = ActivityScenario.launch(MainActivity::class.java)

        compareScreenshot(activity)
    }
}

Actual behaviour
However I see the following error messages when inheriting ScreenshotTest

When I do the following setup, it works but I am not sure is this necessary or should I just need to rely on ScreenshotTest for it to work. Any help on the matter would be greatly appreciated.
@RunWith(AndroidJUnit4::class)
class MyActivityTest  : com.example.shot_snapshot_application.ScreenshotTest<MainActivity>(MainActivity::class.java) {

    @Test
    fun theAcitivityIsShownProperly() {
        val scenario = startActivity()

        compareScreenshot(scenario)
    }
}

and
@LargeTest
@RunWith(AndroidJUnit4::class)
abstract class ScreenshotTest<T : Activity>(private val clazz: Class<T>) :
    ScreenshotTest {
    private var scenario: ActivityScenario<T>? = null

    @Before
    fun setup() {
        Intents.init()
    }

    @After
    fun tearDown() {
        scenario?.close()
        Intents.release()
    }

    fun startActivity(args: Bundle = Bundle()): T {
        val intent = Intent(ApplicationProvider.getApplicationContext(), clazz)
        intent.putExtras(args)
        scenario = ActivityScenario.launch(intent)
        return scenario!!.waitForActivity()
    }
}

Steps to reproduce

Setup a new project
Follow the setup steps as mentioned the readme
For the sample test theActivityIsShownProperly use val activity = ActivityScenario.launch(MainActivity::class.java) instead of    val mainActivity = startMainActivity();

Version of the library
5.11.0

ActivityScenario.launch(MainActivity::class.java) does not return an activity object. You need to call onActivity for that.
In all honesty this isn't a very useful API in my humble opinion. Though maybe I'm misunderstanding. My solution for this was to wrap the whole thing in a suspending coroutine and utilise the @Before method. Like this
`    fun setup () = runBlocking {
    val (activity, activityScenario) = MainActivity::class.launch(intentOptions, this)
   // Store the activity in a field but BE CAREFUL, you're not actually meant to do this if you've got configuration changes
}.let {}`

And this util method

`suspend fun <T: Activity> KClass<T>.launch(
options: Bundle? = null,
scope: CoroutineScope

): Pair<T, ActivityScenario> {
val intent = Intent(ApplicationProvider.getApplicationContext(), java).apply {
    replaceExtras(options)
}

val scenario = ActivityScenario.launch<T>(intent)

val activity = suspendCoroutine<T> {
    scenario.onActivity { activity ->
                it.resume(activity)
    }
}

return Pair(activity, scenario)

}`
I've ripped out a load of domain logic from there but hopefully that gets you started

Thanks, @SamCosta1. You are absolutely right. The framework does not integrate for now with the scenarios. However, this could be a nice improvement.
The android team changed long ago the scenario integration and stopped returning an activity so our only solution is what Sam mentions.
Actually, this could be a nice addition to the ScreenshotTest interface. Adding a new method to consume directly an activity scenario.

Any status updates on how you're going to solve this or how we can help with this? I was previously using Espresso's IntentsTestRule. As it's deprecated now, I'd like to use one of Google's API's to resolve it.


empty Markdown preview window

Issue Type: Bug
Ubuntu 18.04.4 LTS.
Clean install of VSCode.
No one extention installed.
Mardown preview window show nothing for any .md file.
Language indicator show correct value.
Installed "shd101wyy.markdown-preview-enhanced" extension works correctly.
Dual graphics system: i5-6400/GTX 1060 (Clevo n950kp6) - both graphics modes are tested.
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:44:52.965Z)
OS version: Linux x64 5.3.0-40-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
0, 0, 0

Memory (System)
31.25GB (26.91GB free)

Process Argv
--no-sandbox --unity-launch

Screen Reader
no

VM
0%

Extensions: none

Did this work in the previous VS Code release? In VS Code, if you run Developer: Toggle developer tools, do you see any errors in the developer console related to markdown?

This is the first VS Code release I use.
No any unusual messages in developer console.

Have you tried a markdown files that doesn't start with ---?  You example is likely being parsed as front matter

Oops.
It looks like all the files in this project start with these characters. :)
Adding any character to the beginning of the file solves the problem.
Is this a bug or a feature?

Feature. Used to be configurable but now always hidden unless you add an extension. See #66312

So it looks like this was my problem, not the VS Code problem.

Always something new to learn. Please close this issue.


Replace JacksonFactory with GsonFactory.

Fixes #210.

I cannot get the gradle wrapper to work as is:
$ ./gradlew build test
FAILURE: Build failed with an exception.

* What went wrong:
Failed to load native library 'libnative-platform.so' for Linux amd64.

The installed version of gradle I have (4.4.1) runs into other errors.

Apparently this is at least https://github.com/gradle/gradle/issues/1493, because after 3.5 I get a different error, and it appears because I have the JDK11 installed, it confuses anything earlier than Gradle 5.0 :/

/cc @josheinhorn


/testing endpoint testing pictures

Testing pictures 1,2 will be updated tomorrow. Current pictures will display unavailable or not show

fix added next update

fixed


Add image example

Todo:

[ ] Add links to readme
[ ] Maybe find some more interesting things we can show in this example

Rebased

(haven't forgotten about this, just haven't had the chance to check it out and take a proper look - will try to get to it this week!)

Sorry for the delay. This looks reasonable to me - if you add the links to the readme I'll merge it.
(I should also publish a release, since there are some fixes that still haven't been published!)

No worries. Links have been added.

Thanks!


Backport "HBASE-28672 Ensure large batches are not indefinitely blocked by quotas (#6003)" to branch-2

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 12s

branch-2 passed

+1 :green_heart:
compile
2m 53s

branch-2 passed

+1 :green_heart:
checkstyle
0m 38s

branch-2 passed

+1 :green_heart:
spotbugs
1m 33s

branch-2 passed

+1 :green_heart:
spotless
0m 45s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  6s

the patch passed

+1 :green_heart:
compile
2m 50s

the patch passed

+1 :green_heart:
javac
2m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 36s

the patch passed

+1 :green_heart:
spotbugs
1m 39s

the patch passed

-1 :x:
hadoopcheck
10m 53s

The patch causes 10 errors with Hadoop v3.4.0.

+1 :green_heart:
spotless
0m 43s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

31m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 78fc6a1216ab 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Eclipse Adoptium-11.0.23+9

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/artifact/yetus-general-check/output/patch-javac-3.4.0.txt

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 19s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 21s

branch-2 passed

+1 :green_heart:
compile
1m 19s

branch-2 passed

+1 :green_heart:
javadoc
0m 33s

branch-2 passed

+1 :green_heart:
shadedjars
6m 39s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  7s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
javadoc
0m 34s

the patch passed

+1 :green_heart:
shadedjars
6m 24s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
209m 54s

hbase-server in the patch passed.

240m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux b0815dc3d5ca 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/testReport/

Max. process+thread count
4796 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 17s

branch-2 passed

+1 :green_heart:
compile
0m 50s

branch-2 passed

+1 :green_heart:
javadoc
0m 26s

branch-2 passed

+1 :green_heart:
shadedjars
6m 13s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  4s

the patch passed

+1 :green_heart:
compile
0m 50s

the patch passed

+1 :green_heart:
javac
0m 50s

the patch passed

+1 :green_heart:
javadoc
0m 26s

the patch passed

+1 :green_heart:
shadedjars
6m 12s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
220m 21s

hbase-server in the patch passed.

246m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 11c2d1cdfa1c 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/testReport/

Max. process+thread count
4483 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 12s

branch-2 passed

+1 :green_heart:
compile
0m 45s

branch-2 passed

+1 :green_heart:
javadoc
0m 30s

branch-2 passed

+1 :green_heart:
shadedjars
6m 30s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 47s

the patch passed

+1 :green_heart:
compile
0m 49s

the patch passed

+1 :green_heart:
javac
0m 49s

the patch passed

+1 :green_heart:
javadoc
0m 27s

the patch passed

+1 :green_heart:
shadedjars
6m  2s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
245m 58s

hbase-server in the patch passed.

272m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 413fb8436ab0 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/testReport/

Max. process+thread count
4330 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  6s

branch-2 passed

+1 :green_heart:
compile
2m 56s

branch-2 passed

+1 :green_heart:
checkstyle
0m 39s

branch-2 passed

+1 :green_heart:
spotbugs
1m 34s

branch-2 passed

+1 :green_heart:
spotless
0m 47s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
2m 53s

the patch passed

+1 :green_heart:
javac
2m 53s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 37s

the patch passed

+1 :green_heart:
spotbugs
1m 42s

the patch passed

+1 :green_heart:
hadoopcheck
16m 55s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 45s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s

The patch does not generate ASF License warnings.

37m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 7f6fbb8cbe08 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
82 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  0s

branch-2 passed

+1 :green_heart:
compile
0m 56s

branch-2 passed

+1 :green_heart:
javadoc
0m 30s

branch-2 passed

+1 :green_heart:
shadedjars
5m 28s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 52s

the patch passed

+1 :green_heart:
compile
0m 55s

the patch passed

+1 :green_heart:
javac
0m 55s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed

+1 :green_heart:
shadedjars
5m 29s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
220m  9s

hbase-server in the patch passed.

244m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux f5abf9c8caea 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/testReport/

Max. process+thread count
4514 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 41s

branch-2 passed

+1 :green_heart:
compile
0m 51s

branch-2 passed

+1 :green_heart:
javadoc
0m 33s

branch-2 passed

+1 :green_heart:
shadedjars
6m  2s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  7s

the patch passed

+1 :green_heart:
compile
0m 53s

the patch passed

+1 :green_heart:
javac
0m 53s

the patch passed

+1 :green_heart:
javadoc
0m 39s

the patch passed

+1 :green_heart:
shadedjars
6m  6s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
300m 32s

hbase-server in the patch passed.

327m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6058

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux bc56ada9747b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 955f8fddffb570e414a18eac6a0e3a4a7554f0cf

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/testReport/

Max. process+thread count
4333 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6058/2/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Modernize/refresh plugin pom

Use Jenkins BOM
Setup dependabot

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did

Thanks for the PR @jonesbusy any particular reason for switching the protocol on git?

Thanks for the PR @jonesbusy any particular reason for switching the protocol on git?

Hi,
The old protocol is deprecated.
Many plugins are changing to https (Example https://github.com/jenkinsci/display-url-api-plugin/pull/151)
Best regards,

Thanks for sharing. I wasn’t aware of this change.


docs: Use a proper text for our packaging support program

this pr aims to update our current text about the packaging support program in order to have it reflecting our current state and plans

@EverVino , I need to have this pr merged in order to move other topics.
so if the ci is green i will merge that asap, but please feel free to add any comment and concerns here, so I can work on that later. thanks!


use modules to split the code into more idiomatic rust

Discussion, in what modules could we split up the code ?
then i'd like to do the splitting

The only sensible thing I can think of is splitting up the methods that modify the graph ( add_point(), connect_points(), add_square_grid etc.), methods that recalculate the Dijkstra map ( recalculate() ) and methods that read out results ( get_direction_at_point(), get_cost_at_points() etc. ). That's kinda how they are split up in the documentation too.

i have pupt my ideas in motion, i close this issue and open a more appropriate one


Chat on Fullscreen

I want to use chat on fullscreen is there way to do that?

You can with mpv.

Thank you very much


for wrangler 3.7, the trace API call is not working

the trace API is not called on the fetch
==> is not returning success or failure, and it seem like the fetch is not called at all.
  ==>     BTW, if make the same request via POSTMAN, it works.  (with the same body)

i found a workaround but not sure why you have to call the unwrap<> twice..
=> if you unwrap twice, the traceAPI is called correclty

There was a bug with the wrap function in rc.9 that I fixed in rc.10. Could you check if this also solved this issue?


"Recall" Button

When STC has finished repairing a laptop we want to recall laptops, so the admin currently changes the due date to be sooner. Also before break, etc we want to recall them all.
We could facilitate this with a recall button which changes the due date and sends another email to the student with a different precomposed body.
Recall button

Should appear on the specific reservation page
Have form input for the new due date, auto-set to an admin preference (2 days for STC)
When form submits, confirm (jspopup? modal box?) that reservation has a new end_date
Update end_date in controller
Also when form submits, an email is generated to the student. This is an additional email for the admin settings to write.

"Recall all" button
(if it's easy enough to implement at the same time):
Mostly the same, but it should appear on the model or category page to recall all equipment of a specific category/model.

I feel like this is independent of the JS rewrite (should it ever happen), so I'm sticking this back in the Wish List.


Virtual properties from parent model are not accessible in child model

Parent or base model:
var ParentModel = bookshelf.Model.extend({
  /* ... */
  virtuals: {
    parentVirtual: function() { return 'foo' }
  }
}
var ChildModel = ParentModel.extend({
  /* ... */
  virtuals: {
    childVirtual: function() { return 'bar' }
  }
}
var child = new ChildModel()

child.get('childVirtual') // 'bar'
child.get('parentVirtual') // undefined

If the child model doesn't define any virtuals of its own, then the parent virtuals are accessible in the child.

The only way around this is for virtuals to patch extend and merge the object. That'll break with ES6 or CoffeeScript extends. I'm always uneasy about coupling behavior tightly to extend.

You mean the Model's extend? Isn't it derived from Backbone's extend anyway?

Right — extend versus extends. Right now extend just a generic subclassing function, with the same output as the extends keyword in Coffee or ES6. Doing merge behavior like this would require breaking that convention. The issue here is not where the function comes from, but whether it's a good idea to start embedding specific inheritance behaviors in Model.extend that will break when using a generic extends keyword. And I say it's a bad idea.

Sure, I agree. The regular way of extending means that properties defined in the child take precedence over those defined in the parent. What I hadn't realized was that the built-in extend was working like the ES6 one, since I'm not using that stuff yet.
I guess anyone affected by this issue (only me?) would have to do the merging explicitly since it's a custom behavior. That can probably be done in a plugin.
BTW, I'm pretty sure there will be a lot of plugins for Bookshelf once you guys finish the rewrite.

Well the interface is totally open now. Registry and computed properties will probably become core features and the concept of built-in plugins will go away to clarify that people are expected to bring their own.


Add example of math equations rendering using MathJax to the markdown…

@KyleAMathews please review this code.  I'd like to add some MathJax rendering examples, however, I'm not sure where is the best place to put this bit of code:
    MathJax.Hub.Config({
      TeX: {
        equationNumbers: {
          autoNumber: "AMS"
        }
      },
      tex2jax: {
        inlineMath: [ ['$','$'], ['\(', '\)'] ],
        displayMath: [ ['$$','$$'] ],
        processEscapes: true,
      }
    });

The way it is right now in md.js means the equation numbers do not always begin from 1 when you return to the page after hitting back.  Also, putting this bit code in a function getInitialState() gives a blank page.

I'm not at all familiar with MathJax so am not 100% sure what the problem is. Perhaps there's some sort of state it stores or whatever. Does the numbers keep going up every time you visit a page?

Actually I've figured out the problem - it had nothing to do with the md react component, but rather a missing option in the mathjax config structure.  I'm closing this PR because I'll create a separate example that uses this plus a few other features that a typical math blog would require. Cheers!

great!


Cooperation Task - 5

We'd like to add a forced delay after the stimulus presentation (to avoid button spamming which throws off the sound/image pairings)

i' added 1 second delay after outcome image is done displaying. lmk if this is too long.


Go: Add debugger, trace, and iam admin

These look fine to me. I'll approve, but should someone else take a look?

@jba I pinged @garrettjonesgoogle on this. One other engineer's approval is OK for this repo.


[Bug]: Checkbox Group widget - inline disabled, Label position Top or Auto, Style Alignment - End/Center/Around - label and options overlap

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I add a check box group widget to canvas, add around 3 / 4 more options, set inline to off, label position to top or auto, and style alignment to either end/center/around, the label and options get overlapped and UI is not clear.
Steps To Reproduce

Drag and drop a checkbox group widget
Add around 3 or 4 more options.
Set the inline property to off, and label position to top or auto
Set Style Alignment to either - End/Center/Around.

Observe that the label and options get overlapped and UI is not clear.

Public Sample App
No response
Version
Production

Also seeing this behavior on deploy if the checkbox group widget is placed at the top of the page -

Ok the alignment option is only useful when inline is switched on, once off we can choose to hide the alignment option.
If the inline field is js controlled then alignment will only work when inline is true.
Another bug with checkbox group is that when inline is on and there are options which exceed a line, resizing the widget other options which are outside don't come within the widget boundaries.

Stats

Stat
Values

Reach
84

Effort (months)
0.5


Vampire: The Masquerade - Bloodline (Unofficial Patch) glitches

Running Vampire: The Masquerade - Bloodline with the Unofficial Patch mod (game wont launch without) visual glitches can be observed like parts of people being offset from their model. This does not happen with Wined3d

Example screenshot

Unofficial Patch can be downloaded here https://www.moddb.com/mods/vtmb-unofficial-patch/downloads/unofficial-patch-1131
Happens both with the Basic install and the Extras option. Once installed launch the game with -game Unofficial_Patch
Savegame made with basic install of Unofficial Patch:
Vampire-000.zip
Goes into steamapps/common/Vampire The Masquerade - Bloodlines/Unofficial_Patch/save/
Software information
Vampire: The Masquerade - Bloodline (Unofficial Patch)
System information

GPU: 7900xtx
Driver: mesa-git
Wine version: Proton bleeding edge
DXVK version: master (not a regression from what i know)

Apitrace file(s)
https://mega.nz/file/9gYmUQJA#Ecg9aurL1Ri5e3z3mFVFCi3nI4EQVGcfD25ZK_ru6R4
Log files
Vampire_d3d9.log

Sounds to me like it might be an RDNA3 specific Mesa bug, works fine here on a 6700XT and has done so since basically forever.

Oh you are right. Doesn't happen with amd pro. Didn't even cross my mind it could be a driver bug. Thanks!
Will make a mesa issue after checking if it's a regression.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/8712


Upload multiple files

The documentation discusses adding multipart/form-data. But what about adding a request that takes multiple files (not 1 big file in separate parts) as input. See html example below. I've been trying to do this in fuel but simply get bad request.
<form action="/post">
  <input type="file" name="image1">
  <input type="file" name="image2">
  <input type="submit" value="Submit">
</form>

Multiple files is the same as adding multiple parts with different names. Using multiple parts with the same name will merge them into 1 file at the end.

Then here, why does my server return 400 bad request? I'm passing 2 files with the specified input name. Same thing in postman and it works. Where am I going wrong?
fun imageUpload(image1: File, image2: File) {

        Fuel.upload("/path", method = Method.GET)
                .add(
                    FileDataPart(image1, name = "image1"),
                    FileDataPart(image2, name = "image2")
                )
                .response { result ->
                    println(result)
                }

    }

To give more context. My backend is written in python/flask. the code below is essentially a request which expects image1 and image2 to be file inputs with the names image1 and image2.
@app.route('/path')
def makeup_transfer():

    image1 = request.files['image1']
    image2 = request.files['image2']

That's a good question and I don't have a perfect answer :O.
I think it would be good to compare what it sends / receives in the fuel case and in the postman case. Would you be able to get those 2 datapoints?

I think it would be good to compare what it sends / receives in the fuel case.
Where exactly? The request header or...?
Also note the files I was sending was created through File.createTempFile().

Figured it out.
doAsync {
              Fuel.upload("/post").add(
                      FileDataPart(n!!, "image1_file", "image1.png", "image/png"),
                      FileDataPart(m!!, "image2_file", "image2.png", "image/png")
              ).responseObject(RequestResponse.Deserializer()) { result ->
                  when (result) {
                      is Result.Success -> {
                          println("Success")
                      }

                      is Result.Failure -> {
                          println("Failed")
                      }
                  }
              }
          }


Using organization to_poro method instead of direct object dump

@javisantana  CR please

Frontend tests were OK :+1: (details)

@viddo added that change so he should know if this works

By looking at the code it should work fine, but to be certain we would have to verify by visiting a new public page with a logged in organization user.

@viddo could you take care of that testing?

sure!

Found another bug while at it, fixed and verified :+1:

Frontend tests were OK :+1: (details)


FlatCar Beta 3913.1.0 with systemd 255 enables DHCP rapid commit by default

Description
The new Beta FlatCar with version 3913.1.0 updated systemd to version 255. With this new version comes support for DHCP RapidCommit which seems to be enabled by default:
RapidCommit=

    Takes a boolean. The DHCPv4 client can obtain configuration parameters from a DHCPv4 server through a rapid two-message exchange (discover and ack). When the rapid commit option is set by both the DHCPv4 client and the DHCPv4 server, the two-message exchange is used. Otherwise, the four-message exchange (discover, offer, request, and ack) is used. The two-message exchange provides faster client configuration. See [RFC 4039](https://tools.ietf.org/html/rfc4039) for details. Defaults to true when Anonymize=no and neither AllowList= nor DenyList= is specified, and false otherwise.

    Added in version 255.

Our cloud provider (CloudSigma) seems to have a faulty implementation of DHCPv4 rapid commit which means that we are no longer getting an IP address.
This can be fixed (for existing servers) by copying the default config from /etc/systemd/network/za-dhcp-no-rapid-commit.network as an own config and adapting the DHCPv4 section as follows:
[DHCPv4]
RoutesToDNS=false
RapidCommit=false

Impact
Not getting an IP address. Because the CloudInit process for CloudSigma requires an assigned lease this also means that the whole setup doesn't work anymore.
Environment and steps to reproduce

Upload current beta FlatCar CloudSigma vendor image to CloudSigma
Create a new machine
No public IP is assigned and the CloudInit process never runs

Expected behavior
Server correctly setup with IP and CloudInit config.
Additional information
We are also in discussions with CloudSigma in order to fix their DHCP implementation. Not sure when and how this will go though.
This is not really a bug on Flatcars side but rather a break for us because the network config is now different with the new version.
The question is how this could be fixed (if you are open to do it on the FlatCar side). I currently see the following options:

Update the default network config to disabled rapid commit
Add a custom network config file to the vendored CloudSigma image

I would like to get some feedback for this and probably can provide a PR if you would be fine with one of the proposed solutions :).

Add a custom network config file to the vendored CloudSigma image

this would definitely be a good idea if the default does not cause widespread problems for other platforms

@jepio if added only to oem-cloudsigma it shouldn't affect other platforms, should it? And it potentially affects all CloudSigma deployments the way I read the summary.
@daMupfel I would argue that implementing this should be done as an OEM sysext so the change is also distributed to existing nodes when these update (@pothos please keep me honest).
Using an OEM sysext would also allow to change the config with future updates if required. As sysexts cover /usr, the config should go to /usr/lib/systemd/network/.
This is slightly (but only slightly) more complicated than just dropping a config file to the oem-cloudsigma provider. The biggest challenge is to introduce OEM sysext to the cloudsigma image as this image is currently not using OEM sysexts afaict. But that shouldn't keep you from working on a PR, OEM sysexts are used for most other images. The concept should be easily portable to cloudsigma.

I think the OEM sysext might get loaded too late? For most clouds the small network config files are part of the base image because they need to be in bootengine and in init.

Hmmm, good point, re-reading the summary it states that bootstrap configuration fails, so this is required in the initrd. No sysext then.

When adding it to the oem image it won't be updated on existing installations (the oem partition seems to keep the state of the original install), is that correct? At least that was my observation so far.
If so, are there any options to make this work for existing installations which update?

I added a PR regarding this issue in flatcar/scripts. This probably won't fix existing installations (during update) but we can manually fix those in our system quite easily. Please let me now if you think this is a good solution.

Hi,
I created the PR more than 2 months ago and haven't received any feedback yet. I don't want to rush anyone, but I'd appreciate an idea of the expected timeline for this review. This information is important for my company to decide whether to invest in a custom build job on our CI system or wait for it to be integrated upstream. Currently, we are building the images manually.
Thank you very much for your work.
Best regards,
David