Improve functionality for newer lean versions

This removes the bundled lean servers in favor of downloading newer versions directly from github. Alternatively, the user may also explicitly specify a folder from which to get the lean server (if they wish to use a custom build for example).
Also, this removes compression from the library zipfile when building in devmode. This is done because newer versions of mathlib are quite large and compression takes a long time (on my machine this reduced build times from around 4 minutes to just 45 seconds). Since devmode will usually be for local development using the loopback device for networking, the bandwidth will be quite large and the larger file size shouldn't cause problems (you'll save more time from reduced build times than you'll waste waiting for the network).

Additional commit is to properly support newer versions of lean, which have a problem with old versions of BrowserFS. This is ported from #38.


Add EntityCollection.show

Also add show property to CzmlDataSource, GeoJsonDataSource, KmlDataSource, and CustomDataSource, all of which just reference there own EntityCollection's show property.
This will make it much more efficient to toggle on and off data sources versus removing/readded them to viewer.dataSources, which causes all primitives to be destroyed and recreated.
I'm not entire happy with the implementation here, but I couldn't determine a better way of handling this without a larger refactor to the entity system.

Can someone please review and merge this?

@hpinkos do you want to review this?

I looked at this.  Feature works, tests pass, seems straightforward enough.  @hpinkos are you reviewing too?  This seems good to merge.

Merging.


Crash when configuring monitor in config file

I connected a new monitor to my PC. If I connected it when Hyprland is running, the monitor works great, and I can configure it with wdisplays. wdisplays changes are applied and everything works great.
Now I want to add a custom monitor config for this display. As it is rotated 180, it is a pain to configure it every time with wdisplay.
When I add the following simple config, Hyprland crash and did not start any more (always crash)
monitor=DP-3,preferred

hyprctl monitors output
Monitor eDP-1 (ID 0):
<EMAIL_ADDRESS>at 3640x300
	description: BOE 0x09B9
	make: BOE
	model: 0x09B9
	serial:
	active workspace: 2 (2)
	special workspace: 0 ()
	reserved: 0 35 0 0
	scale: 1.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: 0
	activelyTearing: false

Monitor DP-1 (ID 1):
<EMAIL_ADDRESS>at 1080x200
	description: HP Inc. HP E273q 6CM94221N8
	make: HP Inc.
	model: HP E273q
	serial: 6CM94221N8
	active workspace: 3 (3)
	special workspace: 0 ()
	reserved: 0 35 0 0
	scale: 1.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: 0
	activelyTearing: false

Monitor DP-3 (ID 2):
<EMAIL_ADDRESS>at 1393x1640
	description: ASUSTek COMPUTER INC ASUS MB16AC LALMTF127915
	make: ASUSTek COMPUTER INC
	model: ASUS MB16AC
	serial: LALMTF127915
	active workspace: 4 (4)
	special workspace: 0 ()
	reserved: 0 35 0 0
	scale: 1.00
	transform: 2
	focused: yes
	dpmsStatus: 1
	vrr: 0
	activelyTearing: false

Monitor HDMI-A-1 (ID 3):
<EMAIL_ADDRESS>at 0x0
	description: LG Electronics 23EA53
	make: LG Electronics
	model: 23EA53
	serial:
	active workspace: 1 (1)
	special workspace: 0 ()
	reserved: 0 35 0 0
	scale: 1.00
	transform: 1
	focused: no
	dpmsStatus: 1
	vrr: 0
	activelyTearing: false

hyprlandCrashReport1012365.txt

Finally working. It started not crashing with:
monitor-DP-3,preferred,auto,1

and finally is working correctly as follow
monitor=desc:ASUSTek COMPUTER INC ASUS MB16AC LALMTF127915,preferred,1354x1640,1,vrr,1,transform,2.0

I will let the issue open, as I think that showing an error would be a better outcome of a bad monitor configuration instead of a crash.

fixed


Add test to avoid creating existing table in MySQL.

The create-table option needed to test for whether the table already exists, to avoid a SQL error when reexecuting a migration whose later step failed.

Deployed.


source_gen: need access to constantInitializers in ConstructorElement

Right now, pkg/source_gen is using ConstructorElementImpl.constantInitializers. It'd be nice if this was defined as an abstract getter on ConstructorElement.
This is the only private usage remaining in pkg/source_gen

What is source_gen using the initializers for?

To work backwards from the field values in a constant to the const constructor call that generated it. This allows me to use Mirrors to create the instance.

I'm not sure why you want to use Mirrors to create the object when you already have a representation of the object. In the two cases I can see the annotation object has either a single String or two bool valued fields. Seems like you could just ask the DartObject representing the instance for the values of the fields and use toBoolValue() or toStringValue() to get the value. I think this would be both easier to implement and more performant.

Code flow:
User defines customer annotation class: @JsonSerializable(includeCtor: true, includeToJsonMethod: true)
I parse this with the analyzer, create the instance, and let the user write code that just consume the instance in the generator
class JsonSerializableGenerator {
  Future<Something> generate(JsonSerializable annotationValue, SomeAnalyzerElement element) { ... }

My fallback is ugly – making folks attach map literals as annotations (or something).

Note that this approach only works if the code generator built on top of your package always has all classes referenced in the annotations available at runtime. That's probably true 95% of the time, but there will be corner cases where it isn't possible for you to create instances of their annotations.
You could cover all of the cases if you let users understand that they are statically analyzing the code and don't actually have the code being analyzed loaded, and let them use a DartObject representation of the value of the annotation.

I'm currently trying to solve a problem that requires access to constantInitializers.
Is there a workaround / could anyone guide me in the right direction to make a PR to solve this?

I'm currently trying to solve a problem that requires access to constantInitializers. Is there a workaround / could anyone guide me in the right direction to make a PR to solve this?

Just ended up walking the AST to get them. Although I still think this issue is worth resolving for the sake of efficiency (unless I'm missing something obvious?)

has  It any update for this issue?


error downloading example project

Hello, I am working with Python 3.7 on windows. I managed to pip install, however when I try to download the Example Project, I get the following error :
Example types downloaded
Traceback (most recent call last):
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvUI.py", line 5018, in discover
obj['code'] = obj['code'].decode('utf8')
AttributeError: 'str' object has no attribute 'decode'
I managed to fix it by removing the ".decode('utf8')" as with python 3 all strings are unicode objects. Do I absolutely have to use Python 2.7 in order to test Mangrove ?
After that, the example types and graphs could be downloaded, but I then got the following error:
Traceback (most recent call last):
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvUI.py", line 5048, in discover
g.create()
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvApi.py", line 927, in create
node.create()
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvApi.py", line 1497, in create
v.create()
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvApi.py", line 2147, in create
self.setParameter(parameter, self.parameters[parameter])
File "C:\Users\MARTIN_FIXE\AppData\Roaming\Python\Python37\site-packages\mangrove\mgvApi.py", line 2264, in setParameter
original = self.node.type.getParameter(name, version_id=self.node.versionActive.typeForceVersion).default
AttributeError: 'NoneType' object has no attribute 'getParameter'
I was really interested in testing it out, maybe I am doing something wrong ? Thank you in advance
Martin

Hello!
Unfortunately, mangrove hasn't been updated to python 3 yet.
It would be awesome if it were :(
And PR are always welcome!
Thanks a lot


Adding code examples to readme

This might be a stretch, but this blog post that has some code examples that seem quite clear.  Hopefully I can contribute something bigger once I start getting deeper.

Thanks!!


Fix bug and modify checkrate

Context
Status cake contact group name passed in fails to populate contact group
field on deployment. Contact group ID fixes this issue. Default check
rate is too high means url could be down for few minutes without alerts
being sent. This commit address these to issues.
Trello card
https://trello.com/c/yZ1wrROi

 Fix Status cake bug and change check rate


How can I close "smart replace" feature?

For me, I don't need to open this feature. now when I just want to watch my cheatsheet for specified command. I must press <ctrl + G> twice, and delete the word which navi found the best match. In order to achieve this behavior, I must modify the widget.zsh (generated by navi widget zsh)
I hope have a option can control this action. Thank~

For now, the best solution is to indeed copy the contents from navi widget zsh and edit it to your preference


ROCK 4 Linux geek ;-)

R.T.

Currently I am on boarding baidu.com, I'll try this patch and handle this pull request later, I hope it could work.
Prerequesities for building this project (such as GLFW) is not documented yet, maybe I need to write something for it later.


Update how background EFO traits are assigned in Depo-curation to match how main EFO traits are assigned

If possible, I think it would be most efficient if main and background EFO traits can be assigned to studies using the same operation, e.g. using two different columns in the same .tsv bulk-assigning template.

@eks-ebi I have a few questions:

Does this mean we should add another Background EFO trait column to the Study | EFO | Reported trait template?
Should the behaviour be the same as the STUDY-EFO assignment? Meaning the existing value will be overwritten by the new one (including an empty value).
Should we accept multiple background EFOs (pipe separated)?

@ala great questions!

Yes, I would add an extra Background EFO column to the template
The behaviour should be the same: any existing value will be overwritten by the new one (including an empty value) - this will be especially important for background traits, as we often need to revise how we represent them and that might include removing the background trait entirely
Yes, we should accept multiple background EFOs (pipe separated)

Oops!

depocuration deployed, need to implement import

done.
Things to test:

assigning Background traits using the UI option in study details side drawer
assign Background traits using the Study/Trait mapping template
importing in one of the above scenarios, or combine both (assign with file then add more with UI)

sorry for delay @ala-ebi. These are now tested in wwwdev:

assigning Background traits using the UI option works perfectly for both single and multiple EFO terms - DONE
assigning Background traits using the template also works - DONE
a possible issue with the import - I used the template to add background EFO terms to just 5 studies (study tag 253-257) in this submission (https://wwwdev.ebi.ac.uk/gwas/depo-curation/submissions/62cf174ffd97600001ce3f8f) and also made a manual UI edit to add an additional background EFO for one of those studies (257). I left the remaining studies unedited (i.e. no background EFOs). When I look at the import preview for this submission (http://gwas-snoopy.ebi.ac.uk:9780/gwas/curation/submissions/62cf174ffd97600001ce3f8f?), the same single background EFO looks like it will be imported for every study in the submission, including the studies where no background EFO was added, as well as the study (257) where I added an extra EFO using the UI.

the error above was only seen in the import preview - after actually clicking 'import', the expected data was imported into the curation interface

@eks-ebi could youn please confirm this is ok, and should be be deployed

Yes, this is ok and can be deployed


Scheduler plugin refactoring

Goals:

turn plugin into a SchedulerLoop
move code out of the MesosScheduler into operations or the service

/cc @s-urbaniak

Further work on https://github.com/kubernetes/kubernetes/pull/16316 or in new PRs


Project should give an option to expose ports on Pod

When a user creates an integration, there should be an option to add the ports that the pod can expose

In quarkus application you can do this by using application.properties
https://quarkus.io/guides/deploying-to-openshift
quarkus.openshift.route.expose=true for OpenShift
https://quarkus.io/guides/deploying-to-kubernetes
quarkus.kubernetes.ingress.expose=true for Kubernetes

Is it a supported feature or need to be supported?

It is already in place. Just add a dependency and property in application.property

If you have a TCP socket Camel route such as
from netty:<IP_ADDRESS>:1234
then you would need to be able to make a port mapping to expose 1234 in the container.
I am pretty sure both SB and Q has a way to configure this fairly easily with application.properties but it would be good to find out.

First you need to configure services for that
https://github.com/quarkusio/quarkus/blob/main/integration-tests/kubernetes/quarkus-standard-way/src/test/resources/kubernetes-with-multiple-ports.properties

First you need to configure services for that https://github.com/quarkusio/quarkus/blob/main/integration-tests/kubernetes/quarkus-standard-way/src/test/resources/kubernetes-with-multiple-ports.properties

These properties mention HTTP, do they only work for HTTP?

yes its only for HTTP traffic, IMHO we also need a way to expose generic TCP ports like you do with docker ala -p 8080:8080

The following settings work to expose the port: We need to create a NodePort or Loadbalancer Service

Examples in https://github.com/apache/camel-karavan/pull/608


Add hidden flags

This is similar to #180, but then applied to flags. Implementation is done similar to #155

This feature is definitely a help to us for shipping products where some features are unlikely to be used by the end user (but we use them internally), ideally there would be a help all added after this lands that would allow displaying those flags as well

:+1:

I understand the motivation for a feature like this, but this could also be accomplished by checking for an environment variable and conditionally adding flags in the source (e.g. looking for INTERNAL_FLAGS=1).

@jszwedko perhaps this is not how you design your applications, but I would assume for most the app.Run() is their first entry point, to establish the environment within which the application will execute, creating a separate pre-run step that also establishes the environment seems like duplication of effort

@termie sure, but it doesn't need to be. The main entry point is always main and I don't think it is improper to vary the commands, flags, etc. that are allowed based on the environment the application is running under. Every feature adds cost to the library, so I'm just trying to consider the alternatives.

Oh wow, i should have seen this PR before i just submitted - https://github.com/codegangsta/cli/pull/201 .. damn!

Improved upon #201 with filtering flags at higher level than 'templates' so that we don't end up with odd formatting issues.  This way we don't also have to keep IsHidden() or IsNotHidden() exported functions.  Please review..
Also by default --generate-bash-completion flag is never printed along with help.

+1


Suggestion for translation_missing page

Happy Halloween eve. 🎃
As a Korean speaker myself, I'd like to contribute translation when I read Korean doc but it was not smooth to find the specific folder/file in the elixirschool repo. What about adding words of encouragement and connecting location where they can check in the GitHub repo directly?
For example, https://elixirschool.com/no/lessons/ecto/associations has no translation file. In case, we can add a link to go parent directory. ; https://github.com/elixirschool/elixirschool/tree/master/lessons/no
This is just an idea.

@sujinleeme this is a great idea! I'm sorry I missed this notification 😰 Do you have any interest in implementing this?

@doomspork  I'd like to help. 💜

Hooray! Thank you @sujinleeme 💜

Ig that's ok I'd like to take a stab on this issue

Please do @lubien!

I think this can be closed? 👀


Merging in develop branch changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

37 of 37 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on develop at 91.983%

Totals

Change from base Build<PHONE_NUMBER>:
92.0%

Covered Lines:
30487

Relevant Lines:
33144

💛  - Coveralls


fix(accordion): remove aria-expanded from dd

fix #1469

Deploy preview for pf-next ready!
Built with commit 3498e33ae95d752d2aa3b2d4dc973461287d0642
https://deploy-preview-1478--pf-next.netlify.com


Add remaining doxygen + link verification checks

Description of changes: Creating a cumulative PR for remaining status checks as earlier ones were auto-closed during the recent visibility update.
** Initial library content not yet added.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


RuntimeError about GPU

hello,Thank you for your work.
I have a trouble when I run bash HiFi_Net_loc.sh
RuntimeError: Attempting to deserialize object on a CUDA device but torch.cuda.is_available() is False. If you are running on a CPU-only machine, please use torch.load with map_location=torch.device('cpu') to map your storages to the CPU.
what should I do to make it correct，thank you so much

hello, I meet the same of problem also today.
you need modify the file HiFi_Net_loc.sh.
CUDA_NUM=0
CUDA_VISIBLE_DEVICES=$CUDA_NUM python HiFi_Net_loc.py

This CUDA_NUM needs to be set according to the actual situation of your computer
You need to use the cmd window, use the command nvidia-smi, get the number of GPU on you computer, the number of GPU on my computer is 1, so my CUDA_NUM is set to 0, CUDA_VISIBLE_DEVICES means the GPU number

If you have a GPU number of 2 and your GPU number is 0 or 1

@7summer Thank you so much for your answer


AudioGraph runs fast

AudioGraph has been known to have problems, I think I have some insight.
The actual sample rate of 44100 Hz audio arriving to AudioFrameOutputNode is around 44102 Hz . This is because Quantums that deliver 441 samples (10 ms of audio) are actually 9999.5 microseconds apart on average (well eventually, it starts high then decreases). Thus, at least for microphone input, AudioGraph must be distorting audio to produce a higher sample rate.
I found this bug by reading data from a fixed sized buffer between swapchain present calls (a QuantumStarted handler would write the data). The buffer eventually overflows, and my timer indicates that AudioGraph is at fault not VSync.
I have made a repro app. More info is in the readme.

My buffer isn't overflowing with file input, as it does with device input (it's probably just my microphone). Also I didn't manage to reproduce another bug I was getting with file input in the repro app.
I should have probably let this settle a bit before opening this issue. I may open another issue in the future if I think its worth exploring (if that's okay) but right now I'm not so sure.


Refactored a little bit

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

👍


Added word frequency input to GUI

Added an input to change the hack speed.
Cleaned up gui function - instead of having seperate variables for each element all of the gui's html is now stored into one variable.
Note: Hack value will only take come into effect when app.automate() is called (when hacking finishes). This is because the wordLoop variable is assigned the value of wordFreq in the automate function once. Can't seem to figure out how to go about updating it dynamically elsewhere in the script.

Looks good to me :shipit:   Thanks!

@LeeConnelly12
I just refactored all of the bot, and I wanted to show you how to you can include HTML with template strings instead of concatenation:
https://github.com/snollygolly/sourceio-automation/blob/master/main.js#L330-L354

@snollygolly
I never realised that was a thing, would of saved me quite a lot of time.
I'll be sure to use template strings from now on, thanks!


This is not example for FP

https://pub.dev/packages/dartz#-example-tab-
: (

@YuMuuu The examples are in the subfolder, as noted in the file.

Ok!


Improve Confluence vs Jira detection

Hey guys,
using wappalyzer recently I discovered, that a lot of times websites get marked as Atlassian Confluence AND Jira. However, only the Jira technology is capable of finding a version and the Confluence was not.
This is happening, because both applications have the "ajs-version-number" (which is stated within the Atlassian Jira app rule). As well, the provided html-regex ("Powered by...") is not working - at least on pages I encountered. Tested it as well manually.
So my suggestion for lower false-positives would be:

Remove "ajs-version-number" from JIRA - because both apps have it.
Jira pages have one attribute within a meta-tag and the body-tag: "data-version", which we can take advantage of -> therefore changed the html-regex
Confluence pages have in addition to "Powered by ..." the "Printed by Atlassian Confluence [version]" within the footer section. However, depending on the language the only useable part is "Atlassian Confluence [version]" ("Printed by" gets translated). I guess the "Powered by..." regex could be revised as well, but in my opinion it does make the regex simpler for the same result - this is why I suggest using it.

It is a proposal and I wanted feedback from the community about this.
If you have any input, let me know and I will work on it.
Greetings

Thanks!

So sorry for the extreme late response! Not the nice way - my biggest apologies.
I really like this project and will try to contribute in the future more.
If you need anything - let me know!
Best to you


Possibly broken app.error

Description
I'm having difficulties with using custom error handlers. Maybe I didn't understand the documentation right. Please take a look at the code snippets below.
This is my setup:
app.message("error", async () => {
  throw new Error("Error 1");
});

app.message("with next", ({ next }) => {
  next(new Error("Error"));
});

app.error(error => {
  console.log("Inside error handler:");
  console.log("Custom error handler", error);
});

None of these messages passes the execution flow to the error handler.  What I'm doing wrong?
I suspect that customizing this.on('error', ...) in ExpressReceiver may help to get desirable results (customizable error handler), but why do we need app.error(...) then?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: 1.2.0
node version: 12.6.0
OS version(s): macOS Mojave 10.14.5
Steps to reproduce:

Launch Bolt boilerplate.
Copy the code from the description section of this message.
Trigger both messages.
See that console.logs, placed in the custom error handler are not called.

Expected result:
I'm expecting app.error to catch all unhandled errors and errors from next() function. (I could be wrong about some details regarding error handling in Bolt).
Actual result:
It's impossible to get into the handler which you passed into app.error(...).
Attachments:

@stevengill @aoberoi My understanding is that this issue has been resolved by v2 release. Can we close this issue now?

@seratch I believe you are right. @aoberoi do you agree?

I agree! I just created a label for v1 and applied it to this issue so it’s easier to see that it was a bug but only applies to that version series.


Drop support for python 3.6

Closes #342
Adding this draft PR for reference, but not planning to merge it in right away.

Coverage decreased (-0.03%) to 97.557% when pulling 39d27fe7eb547f8bf40dff45b32beac932f3b361 on JWCook:drop-py36 into 6f21685411d6ba9c572b08cf9c3e1bd6a3dae1d6 on reclosedev:master.


Delay loading of bodyconv.def until expansion flags are known

By delaying this, we can eliminate BodyConvGroups entirely.

I think there are cases where the server doesn't send the animation packet

Ok, I added a check that if we haven't received any flags by the time it goes to log into the world, it parses all the files as if the flags are 0.


Set default number of entries?

For options, I have tried specifying the following
    'pageLength' => 100,
    'iDisplayLength' => 100,

At the top of the page, it does have 100 selected. At the bottom it also says "Showing 1 to 100 of 108 entries"
However on the page it still only shows 10 records. Only when I change between the pages does it display 100 entries on a page. Is there another way I should be setting the default number of entries that are displayed?

There is two scenarios here:

DataTables requests data from the server via AJAX. DataTables sets offset and limit in the request
The data is supplied when rendering the page. You have to ensure that offset and limit match the datatables configuration

Now how to ensure that in the second case? Have a look at the DatatablesComponent configuration:
protected $_defaultConfig = [
        'start' => 0,
        'length' => 10,
        'order' => [],
        'prefixSearch' => true, // use "LIKE …%" instead of "LIKE %…%" conditions
        'conditionsOr' => [],  // table-wide search conditions
        'conditionsAnd' => [], // column search conditions
        'matching' => [],      // column search conditions for foreign tables
        'comparison' => [], // per-column comparison definition
    ];

So in your example, you would have to set the length option of the component according to your page length.


iOS7 Safari crash on long press on text element

When you touch and hold text element created by Rapahel in Safari on iOS7, Safari crashes. On iOS6 everything works fine.
It can be tested on http://raphaeljs.com/easing.html . Just press and hold on any text element (long press).

Still happening on iOS?


Add better headers

Currently this package is using super simple headers for it's requests. I need to add better headers.
The location of this constant is in the following link:
https://github.com/amirinsight/py-bingx/blob/9b2942c7f0a4a2b0984b781c5f340c647e60e862/bingx/api.py#L17-L18

Hi, I would be happy to take on this task, but please be more specific.... what does better headers mean?

I'm looking for multiple common user agents (To be chosen randomly from). You can also check the headers which the browser sends in this request.


fix: get render start in vue 2 directive

closes #517

Description

Linked Issues
Additional context

@antfu any change getting new release with this fix?


pgwire: Set tcpNoDelay and keepAlive

Same as in NettyTransport
Reduces lateny from around 40ms to < 1ms

lgtm


RM-1: Reworked flow of adding object a bit, added wrappers around primitives

In my recent project in which my team is using Realm, I've meet few things that seems to be unintuitive for me. I tried my best to make it more clean and intuitive and hope that my idea will pass into project at some point :)
First of all, I believe way in which function realm.add(object, update: false) is a bit misleading. When I saw this function for first time, I thought that it's actually skipping object, if exists, without any changes, while realm.add(object, update: true) is updating existing object. Later I realised that realm.add(object, update: false) is actually throwing exception if object with such primary key already exists, what was a bit frustrating for me. The first change that I want to provide is to make realm.add(object, update: false) just skip object instead of throwing error if exists. It's quite critical for my project, since user of application can fire multiple requests at time and objects in result can already exists in database, but we don't want to update them, since it could overwrite local changes.
Second thing: wrappers around primitive types (Int, Double and String for now) for List to provide builtin possibility of saving list of primitive types  in Realm. Yes, it's not a big deal to write such thing for particular project, but I feel that it would be nice to have such possibility out of the box :)
I hope that I correctly read down the code and documentation and didn't duplicate features that already exists somewhere in Realm :)

Hi @IljaKosynkin. We really appreciate the PR and the time you've put in to preparing this.
Regarding your first change: updating the behavior of Realm.add(...), for starters this is a breaking change in semantics that could break lots of existing apps out there.
For example, Realm.add(_:update: false) currently always adds a new object. Some apps rely on this invariant behavior of Realm. For every user that would prefer realm.add(_:update: false) just be a no-op if the object already exists, there's another that relies on the opposite being the case.
We take making breaking changes very seriously, and therefore this is something we're unlikely to change. Especially given that it's trivial to obtain the behavior you'd like in your code by combining two very concise existing Realm APIs:
extension Realm {
  func addIfNonExistent<T: Object>(object: T) {
    if object(ofType: T.Type, forPrimaryKey: object.primaryKey) == nil {
      add(object)
    }
  }
}

As for your second proposal, adding a Realm model for each primitive type supported by Realm is also something we've thought about and ultimately rejected, because it has unfortunate consequences. For example, every app that uses Realm would now have these tables in the database, regardless of whether or not they use the functionality enabled by these wrappers. Also, these wrappers are trivial to implement in your own apps. Finally, it's a temporary workaround for a limitation, mostly preventing lists of primitives (#1120). We'd much rather remove the underlying limitation rather than introduce a temporary type. Adding these wrappers as a temporary measure would also require us to have a clear path to deprecation and migration to the "fixed" model once it's available. For all these reasons, we've decided not to move forward with that approach.

In the future, if you'd like to propose changes, I suggest you comment on an existing open issue if a relevant one already exists, or open a new one otherwise, where we can discuss the implications of those changes before you devote time to implementing them. Our team might share some edge cases you may not have considered, and conversely, you might open our eyes to an approach we haven't yet considered.
I hope the reasons I've provided here help clarify why we won't be accepting these changes and I sincerely thank you for your interest in contributing to Realm!

Hi @jpsim.
It's a bit strange for me, since I spent quite a bit of time thinking about providing such changes and didn't found any breaking changes in it.  I will be very grateful, if you can provide me real-world use case, when my change will really broke down something fatally.
About your solution with checking if object exists - yes, it's not hard to make such change, but it will provide additional layer above database, as well as give overhead in object searching. As I can see in Realm code - when somebody wants to add object, Realm is performing search of row by ID. With your code such search will be performed twice: in my code at first and then internally in Realm. May be it doesn't seems to be a big deal, but I don't see any point in doubling of operations either, especially since our application is supposed to download thousands of objects from our API and write it to the database.
As about wrappers - well, I can see your point. However, I feel like such limitation on List<> was here for quite a bit of time, so may be it's not a bad idea to give users of library a built-in solution, while you guys are working on correct solution? Also, I think it's possible to map Int to RealmInt internally, i.e. List would be mapped to List inside Realm and problem is basically resolved, no? Yes, once again it's not hard to implement in application all this wrappers, but I personally hate boiler-plate code and I'm trying to avoid it as much as possible. I will not feel happy if I will be forced to repeat wrappers over and over again in every project that is using Realm or write separate library for this, which will require additional time spent on its maintenance.
Hopefully, I made my point clear. I completely understand you concerns about my PR, but I doesn't feel like it's really something big :) Thank you for spending time on reviewing my code and I hope  you would think over about it once again :)

@IljaKosynkin just FYI, I haven't forgotten you! Reviewing and processing your last comment has been on my todo list since you posted this. I'll get to this... eventually.


Update three_dimensions.py

Changelog / Overview

Added documentation for the prism class. Added an example since there were no existing examples for the prism class

Motivation

Added example for new users
Explanation for Changes

Makes it more readable as the examples are useful to the newer users

Documentation Reference

Testing Status

Further Comments

Checklist

[x] I have read the Contributing Guidelines
[ ] I have written a descriptive PR title (see top of PR template for examples)
[ ] I have written a changelog entry for the PR or deem it unnecessary
[ ] My new functions/classes either have a docstring or are private
[ ] My new functions/classes have tests added and (optional) examples in the docs
[x] My new documentation builds, looks correctly formatted, and adds no additional build warnings

Reviewer Checklist

[ ] The PR title is descriptive enough
[ ] The PR is labeled correctly
[ ] The changelog entry is completed if necessary
[ ] Newly added functions/classes either have a docstring or are private
[ ] Newly added functions/classes have tests added and (optional) examples in the docs
[ ] Newly added documentation builds, looks correctly formatted, and adds no additional build warnings

Thanks for this pull request! :)
Here is the example:
https://manimce--1626.org.readthedocs.build/en/1626/reference/manim.mobject.three_dimensions.Prism.html?highlight=prism
As it is a last frame example, I would add the prisms with self.add(prismsmall) and put them next to each other. No self.play calls are needed here.
I would have expected a prism to look more like this:
https://www.google.com/search?q=Prism&sxsrf=ALeKk013R6pIjgop-QuiqAymHDRhbRpt2w:1622901262537&source=lnms&tbm=isch&sa=X&ved=2ahUKEwj6zIiq0oDxAhUiJcUKHTi6C2oQ_AUoAXoECAEQAw&biw=1639&bih=946
As your example looks very cube-like, can you maybe find an example that looks more like a prism? :)

As your example looks very cube-like, can you maybe find an example that looks more like a prism? :)
That's a problem with the class, not this example. It really is just a cuboid.

Thank you for your contribution! I agree with @kolibril13's suggestion: it would be better for the example if the small and large prisms were shifted and rendered next to each other in an image; and given that this is rendered as an image, the play and wait calls should then be removed.
Could you please adapt the example?

@behackl I have tried to implement the solution.

In addition, please also set a suitable camera orientation so that the 3D-ness of the prism can be seen, such as in the example here

@Darylgolden changed camera orientation


fix : print windows cmd error

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

scripts/build-windows/
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

 print cmd err to stderr and fix kclvm python3 check err

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.313%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2106

Relevant Lines:
2358

💛  - Coveralls


Need to add .crt extension when copying the ca certificate

The code snippet for Step 1 under **Configure IoT Edge on devices" should be this (adds the '.crt' file extension to the copied file).
sudo cp <path>/<root ca certificate>.pem /usr/local/share/ca-certificates/<root ca certificate>.pem.crt

This would make it similar to the instruction given for authenticating a regular IoT device.  The reason being that the next step to update-ca-certificates ignores the file if it's extension isn't .crt.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cf391207-5570-8bd5-7093-9ace84259f61
Version Independent ID: 1f885aee-a2bf-2e30-814e-460048ec657b
Content: Connect downstream IoT Edge devices - Azure IoT Edge
Content Source: articles/iot-edge/how-to-connect-downstream-iot-edge-device.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Thanks for bringing this to our attention. The author have created a PR with the update, changes will be live shortly.


Warning when spawning actor within an assign action

Description
When spawning an actor within an assign action, I'm getting a warning about attempting to spawn an actor outside of a service.
Expected Result
No warning printed.
Actual Result
"Warning: Attempted to spawn an Actor (ID: "(machine)") outside of a service. This will have no effect."
Reproduction
https://codesandbox.io/s/tender-leavitt-mv9le

How are you spawning this?
Also, this will be solved more holistically in V5.

I've tried a few different methods, but the failing case is using this:
function spawnFieldMachine(name, validators) {
  return spawn(
    FieldMachine.withContext({
      name: name,
      pristineValue: "",
      currentValue: "",
      validators: validators
    }),
    { name, sync: true }
  );
}
//...
      assign(() => {
        return {
          field: spawnFieldMachine("field", {
            isRequired: ({ currentValue }) => !!currentValue
          })
        };
      })

I can of course pull the spawn call outside of the helper function and into the assign action directly but that doesn't remove the warning.

Try this
assign(
  {
     field: (/* you were missing this callback*/ ) => spawnFieldMachine("field", {
       isRequired: ({ currentValue }) => !!currentValue
      })
  }
)

@CodingDive https://codesandbox.io/s/awesome-rhodes-c42u9  uses your suggested syntax but it also throws the warnings.

This is solved in V5. Is it making your code not work?

I think the code might be working correctly. If so I should be ok to just ignore it for now. I was mainly just prototyping different ways to work with forms in my system to try to come up with an easy way to share as much code as possible between them as I have quite a few different configuration forms in my application.

Don't worry about the warning; it can be ignored for now.

@Blacktiger your latest sandbox is not working properly, because it's using an older version of XState - if you upgrade it to the latest one then it works as expected and you receive no warnings of this kind.
There is another warning related to sync option though. It might be that your child actor gets actually spawned when reading .initialState, which would definitely be not a good thing. A further investigation has to be done though to check if that's true.

Correct, with this setup I'd need to skip most of the component's logic during the initial state. I don't really see any other way to handle it though unless I want to spawn the field machines outside the form machine and inject them as initial context.

I believe that ideally, you should be able to do exactly what you do and there is a small problem on our side, which we need to figure out.

Nice catch, if I just update to xstate 4.7.8 it appears that the warning is fixed. In that case this issue can be closed.


Refactor per Todd's request

Aligned to avoid the custom bootstrapping and getters/setters.

Thanks, can we change the examples of using ng-class in the template, rather than as part of the business logic inside a controller? Ideally this stuff should live in the view as classnames belong in the markup. Is there any reason we're avoiding ng-class to [ngClass] with [ngClass]="{active: isOn, disabled: isDisabled}" like examples? -> https://angular.io/docs/ts/latest/api/common/index/NgClass-directive.html

Ideally the table of contents should go along these lines like the other guides (we want to avoid showing just "one" or some way of doing something, it needs to be crystal clear for the reader):

Angular 1.x

ng-class and Objects
ng-class and functions (where you can demonstrate the controller usage if needed)
ng-class and Arrays
ng-class and ternary

And so on, and the same for Angular 2. We need to cover all bases here for what developers are likely going to be using, so they can resonate with the correct piece of the tutorial, for instance the coverage on ng-repeat to ngFor tackles each section independently: http://ngmigrate.telerik.com/from-ng-repeat-to-ng-for

Closing per additional changes.


Update attribute mappings to match assertions

[x] I read CONTRIBUTING.md

Notes
updated the attribute mappings to better reflect what you can get from gitlab.

removed attribute.sub; it just duplicates google.subject if both map to assertion.sub
added user_login and branch. actor doesn't exist, at least not in my pipeline, Hence removed it.

Using these attributes you can then setup Attribute Conditions. These are more flexible than putting it all in the principal, e.g. you can have something like  ( attribute.branch == "master" || attribute.branch == "dev" ) as condition then.

Hi,
thank you for the pull request.
Please do not remove attributes. I.e. attribute.sub is heavily used in Terraform by Google Profession Services.
assertion.ref can also be a tag. I think it is better to map as attribute.ref.
BR Nils

I quickly modified it myself because I want to add all the other claims right away. Thanks again 👍


ShapeShift DAO Router not processing approvals for Clearpool USDC Junior Tranche

Overview
When trying to approve usdc token with shapeshift dao router to deposit into Clearpool USDC Junior Tranche, it just spins on approval and gives a "Transaction Failed" error. you can select approval again and process repeats even though user is being charged for the approval.
References and additional details

Log into app.shapeshift and connect to wallet of choice
Navigate to DeFi page and find Clearpool USDC Junior Tranche
Select an amount to deposit
Select Approve
Note that the approval spins until a Transaction Failed error appears. see screenshot below for console error.

Acceptance Criteria
Approval should go through so can deposit into junior tranche
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@MBMaria do we have a link for the failed Tx ? 🙏🏽

@gomesalexandre just checked and looks like the transaction does complete. however, each time you go to deposit it asks for approval again.
https://etherscan.io/tx/0x6822e27168acfe0a195bef609208e47b5d0f5061c2f619bbbac04b41a6c59c51


[Feature] Ability to set page order

Summary
Should be able to set the ordering of pages
Motivation
Pages can be built in different order from what you want to display. Developer should be able to set an order of page tabs being shown

Figma link to designs: https://www.figma.com/file/NJB6wtUsWfYKIKICXKwWzY/Dynamic-Page-Visibility?node-id=150%3A2616

Related to #1092.
Note:

Pages can be edited by opening the "Pages" pane from the entity explorer (In designs)
Pages can be: reordered, renamed, set as homepage, deleted and copied and pasted to duplicate
In the pages pane, users can view and edit: page url, visibility
In the pages pane, users can also create a new page.

@jsartisan, I'm thinking we have an order field in the objects inside application.pages. This will be a numeric field that'll determine the order of the pages. The API to reorder would be something like:
PUT /api/v1/applications/page/{pageId}/reorder?order=2

This will get the page given by pageId to move to position 2, and incrementing other pages' order values appropriately.
Any new page gets added to the end of the list, and can promptly be reordered using this same API. Does this sound good?

Reopening this issue as I will be starting the integration with UI.

Is there an update to this issue?

The API to sort the pages got merged into release this Monday. I will be integrating it now.


DiscoveryClient maintains a STATIC reference to its EurekaClientConfig

DiscoveryClient keeps reference to its EurekaClientConfig via a STATIC variable. This may lead to unpredictable behaviour if multiple instances of the client are created.

The clientConfig static field is still used by static methods that are now deprecated. Removal of the static is therefore impossible until these methods are actually removed.
In the meantime, it would be useful to add a safe guard in the constructor to check if an instance has already been created and throw an exception otherwise. This would prevent people from creating multiple instances until actually supported.
What do you think?

Since most of the static methods are deprecated (and the remaining ones are fixable), one way out of this bind is to keep two copies of clientConfig, one static and one instance level. The static clientConfig will be used by the deprecated static methods, and the setting of this will be by each client construction (so slightly undefined as to which version you will get when referenced statically).

Don't you think it might be a better idea to simply prevent multiple instances from being created? I mean, if the the static field is already set, then throw an exception.
The now deprecated static methods are used by clients who assume the singleton pattern anyway - so they are not likely to create multiple instances. And if they do, they are already facing unexpected behaviour.

If the aim of this is to support multiple instances of DiscoveryClient to be created (for some specific use cases), and the only blocking item is the static client config, then adding exceptions would not be a good user experience, especially since it looks like it's not difficult to make the client config an instance variable of the client itself without compromising the singleton usage of client in the more main stream use case.

are there any plans and timelines to fix the issue, thanks

@KishorGrandhe this is on our list of items to fix. If you are interested, a pull request would be very welcome as well. Thanks.

@qiangdavidliu I could try and make a pull request for this one

This is fixed and now DiscoveryClient instances now have their own config instances. (A static reference still exist for backwards compatibility of some of the existing deprecated static methods, but the static config will be pointing a non-deterministic version of one of the client's instance level config).


Responses and prompts are not marked as headings, making it difficult for screen reader users to navigate through content efficiently.:A11y_VS Code: Copilot_Usability

GitHub Tags:
#A11yTCS; #A11ySev4; #DesktopApp; #A11yUsable; #DesktopApp; #Win32; #SH-VS Code Copilot-Win32-July23; #Visual Studio Code Client;
Environment Details:
Application Name: VS Code: Copilot
Visual studio code Insiders Version: 1.95.0(User Setup)
Microsoft Windows 11 Enterprise 23H2 Build 22631.4169
Repro Steps:

Turn on the screen reader.
Launch "Visual Studio Code" copilot.
Verify the issue

Actual:
Responses and prompts are not marked as headings, making it difficult for screen reader users to navigate through content efficiently.
Expected result:
Screen reader users wanted responses and/or prompts to be marked as headings to speed up navigating past messages.
User Impact:
It will affect the screen reader users who rely on headings to skip past messages and navigate more quickly.
Recommendation:
Explore feasibility of including headings or consider other hotkey navigation to move through responses.
Attachment:

@rperez030 do you agree with this issue? I believe they're referring to responses and requests (not prompts) in the panel chat. Those can be navigated using up and down arrow keys. I am not sure if a user would want to jump between headers also.

We already have hotkeys to jump between request/response headings - up and down arrow keys in the panel chat.
I suggest closing this.

This was discussed in the context of a usability study of a copilot extension. The issue was not about moving between chat responses but about reviewing long responses that contain rich content. Headings are not a significant concern, but imagine a response that contains tabular data, for example. It will be presented in the accessible view as just plain text. I think what this is really asking for is a UX in which the screen reader user can review a web representation of the response, something that I believe you are already working on. An HTML view may be more appropriate for reading chat responses than the existing text-based accessible view. At the same time, an editable view can still be helpful for reviewing something like code blocks. I'm happy to talk more about this.

This is now fixed. The response and requests now have tabbable h3 headers with labels. @rperez030, would be awesome if you could pls test this. It'll be released in insider's in about a week.


Update usage of Akk.actor 1

Akka.actor.TypedActor has been deprecated as of 2.6.0 in favor of the akka.actor.typed API which should be used instead.
Created by Sourcegraph batch change christine/update-akka-scala-1.

Testing on Tuesday


Unhandled rejection with .join

I'm having an issue where a rejection isn't bubbling up (possibly related to #721)
this gets unhandled rejection:
return Promise.join(
  rejectedPromise(), // this promise throws a rejection
  validPromise()
)
.then(reply, reply)

this handles unhandled rejection as expected:
return rejectedPromise()
.return(validPromise())
.then(reply, reply)

This is not the correct way to use join, Promise.join takes a handler function as the last argument, you're passing it only promises.
You probably want .all

Unable to reproduce:
13728 % npm install bluebird@latest
<EMAIL_ADDRESS>node_modules/bluebird
13729 % node join-bug.js
Should be error: [Error: hi]
13730 % cat join-bug.js
var Promise = require('bluebird')

return Promise.join(
  Promise.reject(new Error("hi")), // this promise throws a rejection
  Promise.resolve()
)
.then(reply, reply)

function reply(a) {
  console.log("Should be error:", a);
}

@benjamingr thanks for clarifying that - I misread the documentation and thought that .join was like .all for a fixed amount of promises but realize the last arg was a handler function

@benjamingr I just re-tested and .join is functioning the same as .all for me
When I don't add a function handler as the last argument, it returns an array - is that expected/reliable behavior?

@bsiddiqui yes it is; can you create a minimal example to reproduce the issue? I tried with the above code and was not able to

@spion you're right, not able to reproduce the original issue - I had mistakenly not required Bluebird and was using native Promise. Thanks for the help


Send survey utility & default num_tries

Makes the default of Session.num_tries 0.
Adds a generic utility to send a survey to a batch of connections.

Some other utilities for theirc/rescuesms#124 got tacked onto this pull as well.


Increase Test Coverage for XML Http Plugin

Which problem is this PR solving?

#1087

Short description of the changes

Added tests to increase code coverage in xhr.ts to at least 90%
note: opentelemetry-web already has it's code coverage increased to >90% now

@open-telemetry/javascript-approvers Please take a look when you get a chance.


Can't install unsigned msix on Windows 10

Hi --
I've tried to install this on my win10 machine using your recently published .msix installers but the OS refuses to allow installing unsigned packages, even in Developer Mode.  There are instructions to allow it using PowerShell as admin, but the module it requires isn't supported on Windows 10.  Unfortunately, my PC does not have much hard drive space available so I cannot use the source build at present.
Please advise!

The msix is basically a zip file. You can just rename it to .zip and unzip it to install.
Please see the https://github.com/kiennq/scoop-misc/blob/master/bucket/emacs-kl.json package as well.


feature request

please add the ability to select specific channels.
this would be useful since in many servers there are other bots that pokename supports which this script thinks of as poketwo and tries to catch and it looks extremely suspicious and also there are those post tag timer shiny hunt channels which ban u if u "steal" shiny hunts and that already got me banned from few servers..
and if you dont want to add this feature then please tell me how to modify this script to add some lines of code to make this possible or to like do that
i would be extremely extremely grateful if you could do this
and thank you alotttt for making this free❤

Thanks for the feedback!
Am glad that you liked it❤
I have added the specific channel feature
I would work on the shiny steal too but am currently going on with some personal problems T_T so can't make the change now
Open a ticket in the support server and explain this feature idea properly there . I will try to think for it once I get free.
Tip: This bot is most preferred to use in Private servers rather than public. Although I tried to make the bot as normal like a human but I would recommend using it in private servers only to avoid this problem of "sh steal ban"


re-initialize pip master working set after installs

When installing packages with dependencies on higher versions of the idna package, ipydeps will fail with a VersionConflict Exception.  For instance, ipydeps.pip('requests') will install (as of 15 June 2017) certifi-2017.4.17, chardet-3.0.4, idna-2.5, requests-2.17.3, urllib3-1.21.1.  A second call to ipydeps.pip('requests') or to any library that requires requests as a dependency will raise a VersionConflict saying that requests needs idna >=2.5 but it found idna 2.2 on the system.
One workaround is to explicitly call pip.utils.pkg_resources._initialize_master_working_set() in between ipydeps.pip calls.  For instance this will work -
import ipydeps
import pip
ipydeps.pip('requests') # installs certifi, chardet, idna-2.5, etc
pip.utils.pkg_resources.get_distribution('idna') # this will show idna 2.2

### if we ran ipydeps.pip('requests') again it would raise VersionConflict
pip.utils.pkg_resources._initialize_master_working_set()
pip.utils.pkg_resources.get_distribution('idna') # this will show idna 2.5 now.

ipydeps.pip('requests') # works

Pip documentation mentions "Invocation [of _initialize_master_working_set] by other packages is unsupported and done at their own risk."  I do not know what side effects this might have.  Fixing the VersionConflict exception is very important though.

Just to document what I tried today...

The issue appears to manifest itself when ipydeps.pip is called for the requests package (or something that depends on the requests package) twice in the same notebook
I tested out adding pkg_resources._initialize_master_working_set() right after the call to _invalidate_cache()
There was no effect.  pip.get_installed_distributions() continued to report idna 2.2 while pkg_resources.get_distribution('idna') reported idna 2.5
Started exploring custom loaders in importlib and the built in package called "site"

Possible the patch in #7 is connected?  Not sure that patch would cause this, but a fix here might also fix that.

Turns out that it's really important to use the vendored pkg_resources.  Had much better luck messing with this on Friday.  Please roll in the following changes for testing:
https://github.com/nbgallery/ipydeps/commit/ff822ed50fd33fe66ffb1877cc79f922d571bac7

Resolved in db7ea45


Updated broken links in ns-winnt-mem_extended_parameter.md

@Zymlex : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[SQL Migration] Fix overflow behavior on migration cutover dialog to avoid truncating backup file names

In this PR, we fix the CSS overflow behavior on the migration cutover dialog in order to avoid truncating fields such as the file names of the last applied backup files.
Previously, it looked like this, making it impossible for users to see the full file name if it was too long:

Now, the fields will wrap properly, making it possible to read full file names:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.01%) to 48.275%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/book/bookTreeView.ts
2
38.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
14806

Relevant Lines:
29124

💛  - Coveralls

the full text looks good. was that preferred over "someLongName..." showing the ellipsis and tooltip?

@brian-harris Tooltips on text components on ADS are a real pain. We already used word wrap for the other fields, such as 'Backup location' -- full text is easier/more intuitive for the user to read anyways


Consider separating cache package from rest of registry/image-related packages.

From https://github.com/GoogleCloudPlatform/minikube-build-tools-for-java/issues/90
The intention is to keep the registry client completely decoupled from any other parts of the code. Therefore, the registry client and its dependencies should live in its own package.
The new package tree should look like:
.cache
.registry
  .http, .image, .blob, etc.
  .client (the original registry package)

Closing for now. This can be reopened when actually porting out the registry client.


fixed fetch_vyper_language_spec to work with VYper 0.3

Hi!
The vscode vyper extension was missing some keywords so I fixed the script to pull the information from the new locations within the vyper module.

excellent! thanks @DataBeast-IT

You're welcome! I love this extension it just works without complaining 👍🏼


_ Patch Compile Tests _

-1 :x:
mvninstall
1m 18s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 20s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 20s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
javadoc
0m 27s

the patch passed

-1 :x:
shadedjars
3m 27s

patch has 10 errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
0m 20s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

17m 13s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8d8dbace6aa1 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8682fd15a23ed4bd8f3921e6d0de3512c44bd8d5

Default Java
Eclipse Adoptium-17.0.11+9

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6557/1/artifact/yetus-jdk17-hadoop3-check/output/patch-shadedjars.txt

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

Max. process+thread count
79 (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-6557/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 34s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 12s

master passed

+1 :green_heart:
compile
3m 11s

master passed

+1 :green_heart:
checkstyle
0m 37s

master passed

+1 :green_heart:
spotbugs
1m 34s

master passed

+1 :green_heart:
spotless
0m 46s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 19s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 24s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 24s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 35s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 5 new + 7 unchanged - 0 fixed = 12 total (was 7)

-1 :x:
spotbugs
0m 20s
/patch-spotbugs-hbase-server.txt
hbase-server in the patch failed.

-1 :x:
hadoopcheck
1m 41s

The patch causes 10 errors with Hadoop v3.3.6.

-1 :x:
hadoopcheck
3m 21s

The patch causes 10 errors with Hadoop v3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 15s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 21s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 21s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
javadoc
0m 26s

the patch passed

-1 :x:
shadedjars
3m 24s

patch has 10 errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
0m 20s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

15m 43s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 6aabc15ffef7 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3f5649e1c683d349c1c092d4c86d035386b1d911

Default Java
Eclipse Adoptium-17.0.11+9

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6557/2/artifact/yetus-jdk17-hadoop3-check/output/patch-shadedjars.txt

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

Max. process+thread count
84 (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-6557/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 32s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 32s

master passed

+1 :green_heart:
compile
3m 20s

master passed

+1 :green_heart:
checkstyle
0m 39s

master passed

+1 :green_heart:
spotbugs
1m 39s

master passed

+1 :green_heart:
spotless
0m 46s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 20s
/patch-mvninstall-root.txt
root in the patch failed.

-1 :x:
compile
0m 21s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

-0 :warning:
javac
0m 21s
/patch-compile-hbase-server.txt
hbase-server in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 35s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 8 new + 7 unchanged - 0 fixed = 15 total (was 7)

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hbase-server.txt
hbase-server in the patch failed.

-1 :x:
hadoopcheck
1m 38s

The patch causes 10 errors with Hadoop v3.3.6.

-1 :x:
hadoopcheck
3m 14s

The patch causes 10 errors with Hadoop v3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s

The patch does not generate ASF License warnings.

18m 39s

Subsystem
Report/Notes

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

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

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

uname
Linux eaa572cf1187 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
master / 3f5649e1c683d349c1c092d4c86d035386b1d911

Default Java
Eclipse Adoptium-17.0.11+9

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6557/2/artifact/yetus-general-check/output/patch-javac-3.3.6.txt

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

Max. process+thread count
83 (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-6557/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 29s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 10s

master passed

+1 :green_heart:
compile
3m 10s

master passed

+1 :green_heart:
checkstyle
0m 35s

master passed

+1 :green_heart:
spotbugs
1m 33s

master passed

+1 :green_heart:
spotless
0m 42s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  0s

the patch passed

+1 :green_heart:
compile
3m  9s

the patch passed

+1 :green_heart:
javac
3m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 36s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 5 new + 7 unchanged - 0 fixed = 12 total (was 7)

+1 :green_heart:
spotbugs
1m 47s

the patch passed

+1 :green_heart:
hadoopcheck
10m 59s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 41s

the patch passed

+1 :green_heart:
compile
0m 52s

the patch passed

+1 :green_heart:
javac
0m 52s

the patch passed

+1 :green_heart:
javadoc
0m 27s

the patch passed

+1 :green_heart:
shadedjars
4m 54s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
184m 24s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

207m 25s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux f5c68ff3dd2f 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 0e8a29309a69eab49f9741e462ce202209655d62

Default Java
Eclipse Adoptium-17.0.11+9

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

Max. process+thread count
5516 (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-6557/3/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 38s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 47s

master passed

+1 :green_heart:
compile
2m 37s

master passed

+1 :green_heart:
checkstyle
0m 31s

master passed

+1 :green_heart:
spotbugs
1m 29s

master passed

+1 :green_heart:
spotless
0m 42s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 37s

the patch passed

+1 :green_heart:
compile
2m 35s

the patch passed

+1 :green_heart:
javac
2m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 33s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 5 new + 7 unchanged - 0 fixed = 12 total (was 7)

+1 :green_heart:
spotbugs
1m 34s

the patch passed

+1 :green_heart:
hadoopcheck
9m 43s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 41s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 50s

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 27s

the patch passed

+1 :green_heart:
shadedjars
4m 59s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
181m 14s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

204m 38s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 2156561bf64f 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 4b489fb52532ad33a69a5d04ede46ef7ee287046

Default Java
Eclipse Adoptium-17.0.11+9

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

Max. process+thread count
5654 (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-6557/4/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 29s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m  8s

master passed

+1 :green_heart:
compile
3m 17s

master passed

+1 :green_heart:
checkstyle
0m 37s

master passed

+1 :green_heart:
spotbugs
1m 34s

master passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 52s

the patch passed

+1 :green_heart:
compile
3m 11s

the patch passed

+1 :green_heart:
javac
3m 11s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 36s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 5 new + 8 unchanged - 0 fixed = 13 total (was 8)

+1 :green_heart:
spotbugs
1m 40s

the patch passed

+1 :green_heart:
hadoopcheck
11m 17s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 39s

the patch passed

+1 :green_heart:
compile
0m 52s

the patch passed

+1 :green_heart:
javac
0m 52s

the patch passed

+1 :green_heart:
javadoc
0m 26s

the patch passed

+1 :green_heart:
shadedjars
4m 48s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
180m 37s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

203m  3s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 52fd4b4e55a7 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / e45484cb810bedeb2f5ffa6740e8255d4fa98d60

Default Java
Eclipse Adoptium-17.0.11+9

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

Max. process+thread count
5305 (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-6557/5/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 20s

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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 51s

master passed

+1 :green_heart:
compile
3m 33s

master passed

+1 :green_heart:
checkstyle
0m 39s

master passed

+1 :green_heart:
spotbugs
1m 50s

master passed

+1 :green_heart:
spotless
0m 47s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 39s

the patch passed

+1 :green_heart:
compile
3m 30s

the patch passed

+1 :green_heart:
javac
3m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 38s
/results-checkstyle-hbase-server.txt
hbase-server: The patch generated 5 new + 8 unchanged - 0 fixed = 13 total (was 8)

+1 :green_heart:
spotbugs
1m 45s

the patch passed

+1 :green_heart:
hadoopcheck
15m 22s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m  8s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 37s

the patch passed

+1 :green_heart:
compile
1m  7s

the patch passed

+1 :green_heart:
javac
1m  7s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed

+1 :green_heart:
shadedjars
5m 52s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
181m  4s

hbase-server in the patch passed.

208m 40s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 8aa279d51e08 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 80044c27c444c9d5a50fdd472a1b2bb34d457f23

Default Java
Eclipse Adoptium-17.0.11+9

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

Max. process+thread count
5216 (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-6557/6/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.

FYI @kadirozde


Ability to burst builds into cloud as capacity becomes limited

Alternative tools such as CloudBees have a central operations manager that controls where to schedule builds. As an on-premise cluster reaches capacity the operations manager is able to target builds to an alternative on a scale public cloud cluster. While Tekton tasks can be directed to a specific target, is there a way to have the target be controlled by the build queue depth, cluster capacity, etc?

This would be a cool feature but at the moment, the Tekton controller only schedules on the cluster it is running on. Could be a proxy of some kind that can schedule the calls to the right clusters based on load
/kind feature

At this point, the plan would be to have the user create a Condition for a build task that looks up the build queue length and/or available cluster capacity to target on-prem versus public cloud.

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen


[2019-02-14 19:44:16.140][1][debug][upstream] source/common/network/dns_impl.cc:158] Setting DNS resolution timer for 2811 milliseconds
[2019-02-14 19:44:16.181][1][debug][upstream] source/common/network/dns_impl.cc:158] Setting DNS resolution timer for 3083 milliseconds
[2019-02-14 19:44:16.181][1][debug][upstream] source/common/upstream/logical_dns_cluster.cc:88] async DNS resolution complete for colorteller.d
efault.svc.cluster.local
[2019-02-14 19:44:16.181][1][debug][upstream] source/common/network/dns_impl.cc:158] Setting DNS resolution timer for 3083 milliseconds
[2019-02-14 19:44:16.183][1][debug][upstream] source/common/network/dns_impl.cc:158] Setting DNS resolution timer for 5000 milliseconds
[2019-02-14 19:44:16.183][1][debug][upstream] source/common/upstream/logical_dns_cluster.cc:88] async DNS resolution complete for tcpecho.defau
lt.svc.cluster.local

i was able to curl on the red,blue and black but gateway i am having issues
root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080
blue
root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080
red
root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080
black
color gateway is not getting the output .
root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080/color
500 - Unexpected Error
root@curler-cc4fff495-m7zzr:/# env |grep -i gateway
COLORGATEWAY_SERVICE_PORT_HTTP=9080
COLORGATEWAY_PORT_9080_TCP_PROTO=tcp
COLORGATEWAY_SERVICE_PORT=9080
COLORGATEWAY_PORT_9080_TCP_PORT=9080
COLORGATEWAY_PORT_9080_TCP=tcp://<IP_ADDRESS>:9080
COLORGATEWAY_SERVICE_HOST=<IP_ADDRESS>
COLORGATEWAY_PORT=tcp://<IP_ADDRESS>:9080
COLORGATEWAY_PORT_9080_TCP_ADDR=<IP_ADDRESS>
services domain is blank
root@curler-cc4fff495-m7zzr:/# env |grep -i domain
SERVICES_DOMAIN=
root@curler-cc4fff495-m7zzr:/#

i tried to curl the svc gateway 10000 times i couldn't get the color switched from white to another color .

curl on gateway is getting me the same color tried more than 10000 times
curl <IP_ADDRESS>:9080/color
{"color":"white", "stats": {"white":1}}root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080/color
{"color":"white", "stats": {"white":1}}root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080/color
{"color":"white", "stats": {"white":1}}root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080/color
{"color":"white", "stats": {"white":1}}root@curler-cc4fff495-m7zzr:/# curl <IP_ADDRESS>:9080/color
{"color":"white", "stats": {"white":1}}root@curler-cc4fff495-m7zzr:/#

@daparthi001 you need to update the routes using this route canary script for the color gateway to hit the other color tellers.

@Y0Username I have switched traffic using canary.sh ,its taking more time to display just red ,being trying more than 15 mins ,is there way we can display output earlier ,it just displays blue only
aws appmesh update-route --mesh-name appmesh --profile default --cli-input-json file:////root/aws-app-mesh-examples/examples/apps/colorapp/servicemesh/config/update_routes//colorteller-route-red-100.json --query route.metadata.uid --output text
curl <IP_ADDRESS>:9080/color
{"color":"blue", "stats": {"black":0.04938271604938271,"blue":0.654320987654321,"red":0.2962962962962963}}

This might need further investigation. Do you see your envoy configs(/config_dump) being updated as soon as you update routes?


Is it possible to read Content-type: text/plain data

Hello,
I've been searching around on this issue and haven't found a good answer. I hope I'm not doing something silly.
I have a simple program that periodically generates a block of text data and I need to pass that data to a meteor application and parse the weird text format there.
I'm using curl to send the data to my meteor server; something like: curl -d 'foo\nbar' -H 'Content-Type: text/plain' https://myserver/api/test. The problem is that in the request handler, this.bodyParams is always an empty object.
If other content types are used, restivus tries to parse the data but this doesn't always capture every byte. Notably, if Content-Type header is removed, curl defaults to application/x-www-form-urlencoded which is reversible for the simple example I provided, but not for other more complicated use cases.
Now, it is possible to get at the raw data with something like this: https://stackoverflow.com/questions/35857250/how-can-i-get-post-raw-body-in-meteor-restivus but that sure seems like a convoluted way to get the raw POST data. This is also not possible in my use case as the meteor app that I'm using doesn't expose the raw request object from restivus.
Would it be possible and make sense to add a text/plain parser?

I just noticed #108. Unfortunately the this.request._readableState.buffer.toString() method seems to not work for me. I'm running node v8.5.0. I've seen discussions around changing _readableState as it's supposed to be private. Maybe behavior has changed?

@cinderblock Hi! Sorry, have you found any solution? I'm struggling with the same issue.

Gosh, I don't even remember why I was using meteor for... Sorry.


initial commit for median value calculation via R-ArcGIS bridge blog pos

initial commit for median value calculation via R-ArcGIS bridge blog post - please review and let me know if I can clarify anything or make any changes

Not covered in the directions but for the images we're embedding in this repo we want to resize them a bit so they're not so large.
Here's the same image shrunken from ~5MB to ~256K; can we update/replace?

no problem, just updated the image file

Looks good to me! Adding others from PSWD as reviewers for the final go-ahead.

@merit-amystuyv for markdown linting/checking you can use "markdownlint" plugin with VS Code.
Nearly all of the linting-related suggestions are whitespace around headings/paragraphs. The errors you can ignore are those for "single-h1" or "multiple level-one headings" as in the final blog post we want those level-one headings!
Also safe to ignore are ones about heading capitalization and other writing/style-related things.

@merit-schelcj formatting issues have been fixed


Could not deduce MonadSqlQuery for TransactionM

I'm following the README, where I have this schema:
share [mkPersist sqlSettings, mkMigrate "migrate"] [persistLowerCase|
Person
  name String
  age Int
  deriving Show Eq
|]

And then I attempt to "insert" a Person within a transaction:
foo :: MonadSqlQuery m => m ()
foo = withTransaction $ do
  insert_ @Person undefined

Which ends up with the following error message:
[typecheck -Wdeferred-type-errors] [E] • Could not deduce (MonadSqlQuery
+                            (Database.Persist.Monad.Class.TransactionM m))
+          arising from a use of ‘foo’
+        from the context: MonadSqlQuery m

How do I use functions from the shim module within a transaction?

This also doesn't compile for me:
let env = mkSqlQueryEnv pool $ \env -> env
        { retryIf = isSerializationError . fromException
        , retryLimit = 100 -- defaults to 10
        }

isSerializationError expects an SqlError, whereas fromException returns a Maybe. Is the README out of date?
Embarrassingly enough, I don't even know how to cast the SomeException to a SqlError so that it aligns with isSerializationError.
Could you drop another example on that as well? Thanks in advance!

ah seems like the withTransaction part of the README was written before TransactionM was a thing. A quick fix for that would be to add MonadSqlQuery (TransactionM m) as a constraint, but let me look into making the UX better there.
And seems like the retryIf example is slightly off. It should be maybe False isSerializationError. (fromException takes a SomeException and returns Just with the correct error type, or Nothing if the SomeException had a different error type)

https://github.com/brandonchinn178/persistent-mtl/pull/44

That was an incredibly quick fix. Looking forward to the PR being merged!
Thanks for the help, and for creating the library. I'm really enjoying it so far


SVG Icons for YOURLS

Summary
The icons are now many years old. In one of the last updates the YOURLS logo has been introduced as SVG file and I think that it's no time to vectorize the icons too.
Motivation
YOURLS is great and I've implemented the SVG icons already in my own YOURLS installation and now I want to provide those icons for the crowd too.
Is your feature request related to a problem? Please describe.
It's not related to a problem but it would look much better.
Describe the solution you'd like
I've already cloned the YOURS repository but I'm new at GitHub and I don't now if I'm allowed to upload it now or not.

Icons meaning the Actions buttons in the admin panel, for example? Great candidates for SVG, yes!
What you want is a "fork", the button for which you'll find in the top right of this repository. Once you have your own fork, you can clone it and then add your work to a branch there, then turn that branch into a pull request.

Icons meaning the Actions buttons in the admin panel, for example? Great candidates for SVG, yes!
What you want is a "fork", the button for which you'll find in the top right of this repository. Once you have your own fork, you can clone it and then add your work to a branch there, then turn that branch into a pull request.

Superseded by #2822

Superseded by #2822


Try Fargate in EKS

What are the implications?
How do we deal with the lack of DaemonSets for monitoring/logging etc?

Dupe of #1770

Dupe of #1770


Copy CHANGELOG to documentation website

User story
User wants to read the changelog without leaving the documentation website
Preferred solution
Like the docusaurus changelog, add a vitessce.io/changelog page which contains the contents of CHANGELOG.md

Fixed by #1441 - well not copied, but now there is a link to the CHANGELOG on GitHub which seems like a good compromise


User-based Recommendation and Item-based Recommendation by oryx

How can I   realize User-based Recommendation and  Item-based Recommendation by oryx2? what is the data format for User-based Recommendation  and Item-based Recommendation?

You would need to write new application-level code for a batch, speed and serving layer. You could reuse a lot of the existing ALS-based ones. However the logic to make the model would change, and update it, and make recommendations. It's an entirely different type of model. Not hard, but you would be making your own app.