Use multiple stacks to give blocks. This closes #2607

Contains
Makes the giveBlock command send multiple times, until quantity runs out. The command is limited to 99 blocks per stack, since that is the max stack size. Fixes #2607.
How to test
Press (F1) to bring up the console. Use the giveBlock command by typing give  . Pull up the inventory with (i) to see if none of the stack sizes are above 99 and if the correct number of blocks were given.
Outstanding before merging
Sorry I had to reopen this again. I accidentally closed it when I force pushed. To answer @portokaliu 's question, unless I change stackCount in ItemComponent to an integer or create another component to contain the number of blocks to give, then I can't use InventoryAuthoritySystem to send blocks more than 127. If there's another way to do it, then please let me know. I apologize for the late response; I've been a bit busy with finals.

Can one of the admins please verify this patch?

@J0hnCena I'm pretty sure changing the stackCount from bye to int wouldn't have that much of an impact. Don't forget that you also have to change the blockItemFactory settings when you want to improve this system (since it casts the int quantity as a byte specifically).

I moved the logic of dividing the blocks into multiple stacks into InventoryAuthoritySystem.java and changed stackCount from an int to a byte.  This implementation works, but should I just add a separate field to ItemComponent just to contain the blocks when they are given? It would make these changes compatible with other modules, and it would be less lines changed overall, since I could revert the byte casting.

Heya @J0hnCena and sorry for the delay in catching back up with regular engine PRs :-)
In this case I would recommend sticking with byte for minimal changes and accept the limitation of 99 items, at least for now. Maybe then submit an issue for later consideration if we should increase the stack size limit. I pretty much thought 99 was the max stack size anyway, was surprised to see we could get to 127 (makes sense with the byte thing)
And that's actually more for API compliance than anything. It would technically be a breaking change as per SemVer requiring us to bump the major version number for the next release.

@J0hnCena are you still out there by chance?

Sorry about the long delay. I changed stackCount back to an int. I also removed the else statement surrounding item.destroy(), so that item is cleaned up.

Actually hold up, there is a bug with this where if I pick up items thrown with the give command, they get put back onto the same stack even if the stack is at max size. Should I just revert back to the multiple commands logic or create new entities for the stacks in the if(!emptySlots.isEmpty()) statement? If I do the former, the problem of giving more blocks than 127 is also solved, since it is taken care of in multiple commands.

No worries nor rush :-)
Yeah probably just keep it simple with the multiple commands. We can always enhance it more later.

I reverted my changes from InventoryAuthoritySystem and BlockCommands.

Thanks @J0hnCena :-)
Looks nice and simple now, with one code style issue remaining: looks like you've got tab characters in there instead of spaces. We're a 4-spaces kinda group. Not a big deal to fix during merge if needed but might want to tweak project setup if you've got more stuff coming (hopefully!)
@flo: any remaining concerns or looking good for merge?

Tested again both single and multi and merged!
Did note one sort of edge case: you can request a huge amount of blocks (like 9999999) and it'll stall the game while going through the command a whole lot of times. Probably an ideal fix there is to catch when you run out of inventory space then break the loop and stop giving more blocks.
Unsure how to ideally detect that and it may change with @jellysnake's work in #2789 - so I just noted it in the TODO for us to catch up on later :-)
Thanks @J0hnCena!


Message when trying to connect to my mysql 3.51 CLIENT_SECURE_CONNECTION is required

I try to connect to my MySql 3.51 server based on a Linux server I have in my office, connection working perfectly for years on old Navicat connection, I receive this message "CLIENT_SECURE_CONNECTION is required".
I set my MySql to version OLD.
Please can you tell me how to solve problem?
Thanks
Domenico

System information:

Operating system (distribution) and version
DBeaver version
Java version
Additional extensions

Connection specification:

Database name and version
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs

Please try to use SSL:
Fill necessary fields and enable Verify server certificate and Allow public key retrieval there.

Please try to use SSL:
Fill necessary fields and enable Verify server certificate and Allow public key retrieval there.


Complete chapter 1

Overview

Added new notes/ directory
Updated .gitignore
Complete Ch. 1 in notes/01_introduction/

Sorry about this, I meant to do the PR into my forked version of your repo!


webble: add disconnect

Adds missing disconnect event to webble bindings.

@monteslu if this looks good, please merge.


Create a Notification list

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

After building the component please raise a PR with a screenshot of the component and add the component in Widgets/notification-list.html file.
If you need to use any icon please use it from Hero Icons
Good luck.

@Rajdip019  assign me this issue

This is already done. @animesh156


Kong v0.11.0 release

CHANGELOG: https://github.com/Mashape/kong/blob/master/CHANGELOG.md
Updates:

SERF ports removed
VIP added to port definition for internal traffic
Migrations flag added

@shashiranjan84 PR looks good apart from requested change above.


Lack of Responsiveness and Misalignment in the "Our Services" Section

Hi @Naresh-chandanbatve,
I have identified an issue related to the responsiveness and alignment of the "Our Services" section.
Problem:
The current implementation of the "Our Services" section lacks responsiveness, causing inconsistent display across different devices and screen sizes. Additionally, there is a noticeable misalignment within the section's layout, impacting its visual presentation and user experience.

Approach:
To address this problem, I propose the following steps:

Implement Responsive Design: Apply responsive design principles to ensure that the "Our Services" section adapts seamlessly to diverse screen sizes, including mobile, tablet, and desktop views. This approach will enhance accessibility and provide an optimal user experience across all devices.

Correct Misalignment: Identify and rectify the misalignment within the "Our Services" section's layout. This involves aligning the elements precisely, maintaining consistent spacing, and ensuring visual harmony within the section.

Additional Information:
As a participant in GSSOC3 with experience in similar projects, I am confident in my ability to effectively address the responsiveness and alignment issues in the "Our Services" section. By implementing these improvements, we can enhance the overall refinement and usability of the project.
Thank you for considering my involvement in resolving this issue. I am eager to collaborate with the team to ensure the successful implementation of the necessary improvements.
Best regards,
Premsai Varma

Go for it @premsaivarmachekuri
But you have to create different prs for different issues..

Noted Naresh 👍
On Sat, May 20, 2023 at 10:01 PM Naresh Chandanbatve <
@.***> wrote:

Go for it @premsaivarmachekuri https://github.com/premsaivarmachekuri
But you have to create different prs for different issues..
—
Reply to this email directly, view it on GitHub
https://github.com/UBA-GCOEN/StichHub/issues/8#issuecomment-1555947239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2NVDOKQ7N2DVDM5MY7DA3LXHDWV7ANCNFSM6AAAAAAYI2J4RM
.
You are receiving this because you were assigned.Message ID:
@.***>

I want to work on this issue under gssoc'23

@vk20july I am assigning you this

@Siddhant-Patil0203 everything is responsive in our service section expect the title our service do you want our service text to be at the center while reducing the size of website?

@Siddhant-Patil0203 everything is responsive in our service section expect the title our service. Do you want our service text to be at the center while reducing the size of website?

No not required as of now


Sharded version of current hipstr script: str_iterative_hipstr_runner_sharded.py

Allows for parallelisation by sharding a big catalog into mini catalogs.

Planning to experiment with different storage and memory parameters with larger set of crams beyond the test dataset, so added them as command line params.


Customizing the exportFromJSON delimiter

Hi,
Can you add the option/props to customize the exportFromJSON delimiter ?
Thanks!

Thank you for your pull request, it has now been merged.


Add --iree-flow-data-tiling-assume-tile-sizes-divisors-of

This flag is a short-term workaround for the difficulty of properly solving #11360, const-evaluating pad + set_encoding. The difficulty is that the shape is not known at Flow, it is still a upper_bound_tile_size op there. See discussion below https://github.com/openxla/iree/issues/11360#issuecomment-1642234084 .
However, a common case can be unblocked: when the shapes are static and are known to be multiples of some power of two that one is willing to assume is divided by any tile size that could result from materialization. Typically at the moment, 16.
So this flag is meant to unblock such users to experiment with constant-evaluating the set_encoding dispatches in their data-tiled matmul workloads. Motivation = https://github.com/nod-ai/SHARK/issues/1589 . However, trying to apply that there currenrly runs into issues, at least the minimized issues filed as https://github.com/openxla/iree/issues/14437 and https://github.com/openxla/iree/issues/14439.  The former is orthogonal to the present PR and gives a different error message than I get on the e2e workload, while the latter depends on this PR and gives the same message as on the e2e workload.

Trying to understand the issue here. Looking at the gist from the tagged issue, is the issue that for this sequence
  %padded_0 = tensor.pad %cst low[0, 0] high[%7, %8] {
  ^bb0(%arg2: index, %arg3: index):
    tensor.yield %c0_i8 : i8
  } : tensor<100x100xi8> to tensor<?x?xi8>
  %9 = iree_linalg_ext.set_encoding %padded_0 : tensor<?x?xi8> -> tensor<?x?xi8, #iree_linalg_ext.encoding<user = MATMUL_I8I8I32, role = RHS, original_type = tensor<100x100xi8>>>

It looks the computation of the "constant frontier" gets blocked somewhere. Can you tell me where?

See #11360 (comment) - the constant expressions analysis thinks that all of this is a constant, but because the dims are dynamic, some tensor.dim end up where they shouldn't and we get a compile error.
Ok, ill carry the discussion over there.

Irrespective of that... can we just do this for the case where the operands of the matmul are constants.. This seems like a pretty heavy hammer.

Converted back to draft. Ordering of next steps:

https://github.com/openxla/iree/issues/14437 and https://github.com/openxla/iree/issues/14439 need to be resolved first as they block using this in practice.
Use this, observe some real benefit on e2e workload.
Then resume the conversation about this PR ; however, in the interim, maybe enough progress will have happened on https://github.com/openxla/iree/issues/11360 that this won't be needed anymore.

The pass itself is ready without changing the Flow pipeline. I added a lit test and revert the pipeline changes, and think that we can land this to unblock const_eval work.

If it isnt too much trouble, could you base your const eval work on top of this PR. I want to see if we can just fix the underlying issue for good before landing some code that we will have to undo quickly. The PR itself looks OK, but just a bit apprehensive w.r.t adding more flow level flags.

Sure. The pass is mainly for generating set_encoding %cst ops when they are aligned with 16. Here is the rest of code: https://github.com/openxla/iree/commit/7560493411ecb1f286c6e1da8e8ffef0b78b887b
I put IR dump and some snippets about what's happening to https://github.com/openxla/iree/issues/11360#issuecomment-1670094543

We are able to fold set_encoding(constants) now, this is no longer needed. Closing the PR...


'SyntaxNode' object has no attribute '_grab_beginning_comment'

Describe the bug
Upon loading a previously-readable MCNP input file, I get an
AttributeError: 'SyntaxNode' object has no attribute '_grab_beginning_comment'.
To Reproduce
deck = montepy.read_input(deckpath)

Error Message (if any)
If an error message was printed please include the entire stacktrace. If it includes any specific values please change or remove them. For example:
  File "xferpins.py", line 42, in _load
    deck = montepy.read_input(deckpath)
  File "montepy/input_parser/input_reader.py", line 31, in read_input
    problem.parse_input(replace=replace)
  File "montepy/mcnp_problem.py", line 388, in parse_input
    obj._grab_beginning_comment(trailing_comment)
  File "montepy/data_inputs/importance.py", line 379, in _grab_beginning_comment
    last_tree._grab_beginning_comment(last_padding)
AttributeError: 'SyntaxNode' object has no attribute '_grab_beginning_comment'

MCNP input file snippet
I will try to produce a MWE to reproduce the bug, but so far I have not been able to figure out which card input is triggering the failure (see #579).
Version

Version 0.5.0

Additional context
This occurs in one of the lab's internal models.

MWE
MCNP Test Model
C Cells
C Graveyard
99    0 +1010
C Seven spheres within a sphere
1 1 -10 -1001
2 1 -10 -1002
3 1 -10 -1003
4 1 -10 -1004
5 1 -10 -1005
6 1 -10 -1006
7 1 -10 -1007
8     0 -1010  1001  1002  1003  1004  1005  1006  1007

C surfaces
1001 SO      0.1
1002 SX -1.1 0.1
1003 SX +1.1 0.1
1004 SY -1.1 0.1
1005 SY +1.1 0.1
1006 SZ -1.1 0.1
1007 SZ +1.1 0.1
1010 SO 3

C data
fc7 Fission Heating
f7:n
     1
     2
     3
     4
C
C
c
C Importances-------------------------------------------------------------------
C
imp:n,p
            0 2 6r
            1
C
mode  n p
C UO2 5 atpt enriched
m1        92235.80c           5
          92238.80c          95
C execution
ksrc 0 0 0
kcode 100000 1.000 50 1050

AttributeError: 'SyntaxNode' object has no attribute '_grab_beginning_comment'
Error came from line: {obj._input.line_number} of {obj._input.input_file}.
imp:n,p
            0 2 6r
            1
C

Interesting. It's the comments that break everything.

Specifically, it seems to be a comment following a tally. When it was after materials, it did not break.

Well I found the underlying bug so 👍


*: Fix some errors in Travis CI

/assign @ScorpioCPH
Signed-off-by: Ce Gao<EMAIL_ADDRESS>

This change is

I will fix all errors after this PR and #476 merged.

Coverage decreased (-0.5%) to 55.007% when pulling 5a754ab594f393c504ae5ca66d85238a175bed72 on gaocegege:fix into 71a5a260e56d9f76a8d984c8c1e9a9b951befb1a on kubeflow:v1alpha2.

PTAL @ScorpioCPH


The current Visual Studio installation is incomplete

Steps to Reproduce

Install Flutter latest version on Windows 10 machine.
Install Visual Studio 2022 Professional Edition, choosing the "Desktop development with C++" workload.

Start a new cmd session and Run "flutter doctor -v" command and get the following Visual Studio-related error message:

Logs

Logs

[√] Flutter (Channel dev, 2.11.0-0.1.pre, on Microsoft Windows [Version 10.0.19043.1526], locale en-AU)
• Flutter version 2.11.0-0.1.pre at D:\Productivity\IDE\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision b101bfe32f (4 weeks ago), 2022-02-16 07:36:54 -0800
• Engine revision e355993572
• Dart version 2.17.0 (build 2.17.0-69.2.beta)
• DevTools version 2.10.0-dev.1
[!] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.1.1)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
• Visual Studio Professional 2022 version 17.1.32228.430
• Windows 10 SDK version 10.0.19041.0
X The current Visual Studio installation is incomplete. Please reinstall Visual Studio.
[√] Connected device (2 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19043.1526]
• Edge (web)        • edge    • web-javascript • Microsoft Edge 96.0.1054.62
[√] HTTP Host Availability
• All required HTTP hosts are available

@stuartmorgan thank you for the feedback. I have updated the log.
Could you please share any suggestions regarding this issue? I have searched all over the Internet.
Regarding VS installation, is there any way to explicitly set the path in config to VS installation?

I have managed to fix the problem after your initial feedback @stuartmorgan. I was getting this error in my VS installer "Couldn't install Microsoft.VisualStudio.AspNet45.Feature". I ignored this because it was totally unrelated to flutter.
After checking the JSON response of vswhere.exe, I found this "isComplete: 0" and it was because of the error within the VS installer. All I did is, install the missing component, that made Visual Studio installation complete and flutter started working.


UDT behavior when property is missing

Bicep version
0.24.24
Describe the bug
Statically declared complex typed parameters (objects) do not retain properties not specified by the parameter file, though explicitly declared in the UDT.
To Reproduce
type Nsg = {
  name: string
}

type Subnet = {
  name: string
  nsg: Nsg?
}

// simulate parameter passed by parameter file which doesn't mention nullable properties
// If we treat parameter JSON as serialized version of Subnet with null assigned nullable property outputs skipped,
// deserialization to Subnet should restore nsg property and assigned the default value (in this case null)!
param subnet Subnet = {
  name: 'subnet1'
}

//ISSUE:  Because the parameter subnet is a typed variable, nsg is expected to be present and null
output subnetContainsNsg bool = contains(subnet, 'nsg')
//Checking the existence of each property makes code complex
output nsgIsNull bool = (subnet.?nsg ?? null) == null
//ERROR: language expression property 'nsg' doesn't exist!
//ISSUE:  Even if contains() fails, subnet is a typed variable, nsg is expected to be present and null
output nsgIsNull2 bool = (subnet.nsg ?? null) == null

Additional context
Imagine having to check each property in a scenario like the below one:
module nsg 'nsg.bicep' = [for (subnet, index) in items(virtualNetwork.subnets): if(contains(subnet.value, 'nsg') && (subnet.value.?nsg ?? null) != null && (subnet.value.?nsg.?isExisting ?? false)  == false) {
  name: 'nsg-${subnet.value.?nsg.?name}-${index}'
  params: {
    location: location
    nameSuffix: ''
    nameOverride: subnet.value.?nsg.?name!
    coreTags: coreTags
  }
}]

The behavior was explained here: #11912
My solution is to apply the default values using union().
type Subnet = {
  name: string
  nsg: Nsg?
}

param subnet Subnet

var subnetSettings = union(
  { nsg: null },
  subnet
)

We need default values in UDT.

Closing as default of #9636

Closing as duplicate of #9636


⚠ Bofrost.es has degraded performance

In 78f2e6f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1421 ms

Resolved: Bofrost.es performance has improved in 39368c6 after 7 minutes.


Feature Request: Sync personal Trakt Ratings with Plex User Ratings

Add the stars from trakt to Plex if possible as half stars.

added mass_trakt_rating_update to settings defaulting to False when set to True it will update the user rating of all movies in your library with any trakt ratings you have

Works like a charm for movies and tv shows. Would be nice if it would pull them at season and episode level too but is a low level priority.


Implement other vehicle models

currently, our vehicle model is pretty simple (CTRA)
-> we should try more sophisticated models

this should be good enough for now


Move inactives to emeritus_approvers and add active users

Move inactives to emeritus
Add wongma7 to reviewers because he was only in approvers
Add Jay to approvers and reviewers

/assign @wongma7
/cc @jaypipes

Let me remove Jay, and after he becomes a member we can add him.

/lgtm


iCloud Device Tracker fails when found a unicode char

Home Assistant release (hass --version):
0.20.2
Python release (python3 --version):
3.4.2
Component/platform:
Device Tracker / iCloud
Description of problem:
My iPhone have as name: 'iPhone de Nélio' (with accent). When device tracker try to map that, show me a bug, as in the log bellow:
@400000005744eed6284aa4d4 ERROR:homeassistant.core:BusHandler:Exception doing job
@400000005744eed6284adf6c Traceback (most recent call last):
@400000005744eed6284aef0c   File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 809, in job_handler
@400000005744eed6284b1234     func(arg)
@400000005744eed6284b1dec   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/event.py", line 179, in pattern_time_change_listener
@400000005744eed6284b3d2c     action(now)
@400000005744eed6284b44fc   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/icloud.py", line 71, in update_icloud
@400000005744eed62866a4cc     gps_accuracy=location['horizontalAccuracy']
@400000005744eed62866cfc4   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/init.py", line 223, in see
@400000005744eed62866f6d4     update_config(self.hass.config.path(YAML_DEVICES), dev_id, device)
@400000005744eed628670e44   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/init.py", line 411, in update_config
@400000005744eed62878409c     out.write('{}:\n'.format(device.dev_id))
@400000005744eed6287867ac UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 7: ordinal not in range(128)
Expected:
Convert the device id and name to ascii chars before write in the Yaml device files. To solve that, I suggest the solution was I applied in my house:
In the file: homeassistant/components/device_tracker/init.py change the lines as a diff bellow:
13c13
<
---
> from unidecode import unidecode
411c411
<         out.write('{}:\n'.format(device.dev_id))
---
>         out.write('{}:\n'.format(unidecode(device.dev_id)))
413c413
<         for key, value in (('name', device.name), ('mac', device.mac),
---
>         for key, value in (('name', unidecode(device.name)), ('mac', device.mac),

Problem-relevant configuration.yaml entries and steps to reproduce:
configuration.yaml file, section device_tracker as bellow:
device_tracker:
  - platform: icloud
    username: "supressed"
    password: "supressed"

Additional info:
If you need anything I'm available to help, inclusive to share the solution or merge it in the home assistant if you want. OK?!
Thank you!

We should just store unicode in yaml. No need to recode it as ascii
On Tue, May 24, 2016, 17:58 nsfilho<EMAIL_ADDRESS>wrote:

Home Assistant release (hass --version):
0.20.2
Python release (python3 --version):
3.4.2
Component/platform:
Device Tracker / iCloud
Description of problem:
My iPhone have as name: 'iPhone de Nélio' (with accent). When device
tracker try to map that, show me a bug, as in the log bellow:
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284aa4d4
ERROR:homeassistant.core:BusHandler:Exception doing job
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284adf6c
Traceback (most recent call last):
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284aef0c
File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line
809, in job_handler
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284b1234
func(arg)
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284b1dec
File
"/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/event.py",
line 179, in pattern_time_change_listener
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284b3d2c
action(now)
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6284b44fc
File
"/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/icloud.py",
line 71, in update_icloud
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed62866a4cc
gps_accuracy=location['horizontalAccuracy']
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed62866cfc4
File
"/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/
init.py", line 223, in see
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed62866f6d4
update_config(self.hass.config.path(YAML_DEVICES), dev_id, device)
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed628670e44
File
"/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/
init.py", line 411, in update_config
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed62878409c
out.write('{}:\n'.format(device.dev_id))
@4000000
https://github.com/home-assistant/home-assistant/commit/400000005744eed6287867ac
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position
7: ordinal not in range(128)
Expected:
Convert the device id and name to ascii chars before write in the Yaml
device files. To solve that, I suggest the solution was I applied in my
house:
In the file: homeassistant/components/device_tracker/init.py change the
lines as a diff bellow:
13c13
<

from unidecode import unidecode
411c411
<         out.write('{}:\n'.format(device.dev_id))

    out.write('{}:\n'.format(unidecode(device.dev_id)))

413c413
<         for key, value in (('name', device.name), ('mac', device.mac),

    for key, value in (('name', unidecode(device.name)), ('mac', device.mac),

Problem-relevant configuration.yaml entries and steps to reproduce:
configuration.yaml file, section device_tracker as bellow:
device_tracker:

platform: icloud
username: "supressed"
password: "supressed"

Additional info:
If you need anything I'm available to help, inclusive to share the
solution or merge it in the home assistant if you want. OK?!
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/home-assistant/home-assistant/issues/2162

Are you have a plan to do that for the next versions? I'm asking that, because the Brazilian Users community love Home Assistant. This problem is impacting directly most of us.
We are doing weekly Hangouts to discuss about the best ways to implement Home Assistant,... because we are constructing a large base of IoT Developers around your solution. It's a clean, fast and beautiful solution and at top: agnostic from any vendors.
If you could provide this solution or give us the paths to do that, we really appreciate to help.
Kindly, Nelio and our BR IoT Community :)

I'm unable to reproduce it. Can you write a test case? What is the encoding on your known_devices.yaml file ?

If it can help, I am experiencing the same issue with an iCloud account with devices containing accent:
16-06-21 11:00:02 homeassistant.core: BusHandler:Exception doing job Traceback (most recent call last):   File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 809, in job_handler     func(arg)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/event.py", line 179, in pattern_time_change_listener     action(now)   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/icloud.py", line 71, in update_icloud     gps_accuracy=location['horizontalAccuracy']   File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/device_tracker/__init__.py", line 201, in see     dev_id = cv.slug(str(dev_id).lower())   File "/usr/local/lib/python3.4/dist-packages/homeassistant/helpers/config_validation.py", line 209, in slug     raise vol.Invalid('invalid slug {} (try {})'.format(value, slg)) voluptuous.Invalid: invalid slug iphonedeaurélie (try iphonedeaurlie)
Here is the encoding of known_devices.yaml:
pi@raspberrypi:~/.homeassistant $ file known_devices.yaml known_devices.yaml: UTF-8 Unicode text

I am getting this issue as well. But no of mine have accents here is what the log says on mine.
UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 14: ordinal not in range(128)

@balloob : What else do you need in order to address this issue? How can we help?

I'm not looking into this bug. I can't repro it nor do I use iCloud. This
is for someone else to address.
On Wed, Jul 20, 2016, 07:24 Axel Caspard<EMAIL_ADDRESS>wrote:

@balloob https://github.com/balloob : What else do you need in order to
address this issue? How can we help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/2162#issuecomment-233964801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYJ2unE6QhTH7XIvkCcNpe6mmXcVuIGks5qXi-IgaJpZM4ImEWO
.


Fixes #174

Related Issue
Fixes #174
Description
Removed the white space under the login screen, and added hover effect to the navbar
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/Muskansahuincredible/StudyNotion-An-Online-Education-Platform/assets/138088550/abe144ae-8613-4edf-91e7-239b574126f1
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:

@techmannih Sir kindly add the gssoc label and assign a level to this, otherwise it won't be counted towards my gssoc contribution.
Thank you!


Module 3 Week 2: Todo List App with React

In this pull request following tasks were completed.

React app created
Todo List Created using class and functional components
CSS styles added for todo list.
Readme Created
Linters fixed

Regards,
Usama Masood

@V-Blaze,
Thank You.


Get EU VAT number details doesn´t work

Hello,
I´m trying to replicate this example with real VAT number: https://github.com/mpociot/vat-calculator#get-eu-vat-number-details
But I get the following response:
object(stdClass)#1133 (6) {
  ["countryCode"]=>
  string(2) "ES"
  ["vatNumber"]=>
  string(9) "B75149773"
  ["requestDate"]=>
  string(16) "2020-01-22+01:00"
  ["valid"]=>
  bool(true)
  ["name"]=>
  string(3) "---"
  ["address"]=>
  string(3) "---"
}

The name and address is not defined as I can´t give them as input for the validation.

I checked the SOAP response and it doesn't returns the name nor address, so the problem is not related with this library :(


Update mongodb-introduction.md

Azure Cosmos DB API for MongoDB is compatible with the following MongoDB server versions:

Version 4.2
Version 4.0
Version 3.6
Version 3.2

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

#label:"aq-pr-triaged"

@wuwu71, thank you so much for your contribution! It looks like another contributor already made this change.
#please-close


ODF status should report on storagecluster status

ODF policy status is currently tracking operator availabilty not the storage cluster and storage classes which are more important to know about

The update is merged.  Thanks for opening the issue!


Add new instance type for T2 Unlimited instance pricing?

AWS has stopped releasing newer generations of instances below the now smaller: c5.large. IMHO T2 Unlimited appears to be the replacement when the risk of being limited by CPU burst credits is not acceptable. It's especially interesting when comparing smaller providers who offer cheap instances with no CPU cap.
RFC: Add t2.x instances with .05 added hourly computed, assuming 100% cpu usage from boot.
https://aws.amazon.com/blogs/aws/new-t2-unlimited-going-beyond-the-burst-with-high-performance/

I'm not opinionated on the specific implementation here as I don't have this use case. Seems like it'd be fine so long as there's an explanation in a tooltip?


[BUG] Unused packages "bitstring" and "bitarray"?

Go to repo search
Find "bitstring"
See no entries of bitstring

Expected behavior
Usages of package in .py files

bitstring is a dependency of bolt11
bitarray is a dependency of bitstring


Add Storybook support

Description
I would to use storybook with nx-plus and vue
Motivation
Nx supports storybook for angular and react
Suggested Implementation
We can take inspiration from nx and the way they implemented the schematics and builder

@BuckyMaler @ZachJW34 I would like to add the ability. Is that ok?

@BuckyMaler @ZachJW34 I would like to add the ability. Is that ok?

@mehrad-rafigh Go for it! Reach out if you have any questions.

@mehrad-rafigh Go for it! Reach out if you have any questions.

@mehrad-rafigh any update on this? Need any help in developing the feature?

@LuckeeDev I have not found the time to develop this. You can grab this issue and start programming :)

@mehrad-rafigh yes, I can take a look at it!

do you have a repo that you have successfully configure storybook for a vue library in nx that can be used as a template for future development?

I am currently working on a PoC to migrate to Nx and possibly convince of its benefits but this is a show stopper, @LuckeeDev any help needed, are you currently working on this?

@danielquintero sadly, I've not had the time to work on this :(

Is there an estimate if and when this feature will be available? I would like to do something for it myself, but my skills are not enough.

The solution is pretty easy (for nuxt), but it took me several hours to get there.

Install nuxt/Storybook as mentioned here: https://storybook.nuxtjs.org/getting-started/installation/
Add the following to your nuxt-targets in workspace.json|angular.json|project.json (replace the value of cwd with the path of your app):

    "storybook": {
      "executor": "@nrwl/workspace:run-commands",
      "options": {
        "cwd": "apps/cockpit-app",
        "command": "npx nuxt storybook --ci",
        "parallel": false
      }
    },
    "build-storybook": {
      "executor": "@nrwl/workspace:run-commands",
      "options": {
        "cwd": "apps/cockpit-app",
        "command": "npx nuxt storybook --ci build",
        "parallel": false
      }
    }

Add "build-storybook" to tasksRunnerOptions.default.options.cacheableOperations in nx.json

Please do it someone, who has the time for it, really cool and important thing


Is -strict flag supposed to work w/ CRD validation?

Hi,
I've noticed that the -strict flag when used against a CRD is not complaining about extra fields. Type validation and enum validation is working fine but if a YAML resource I'm validating has added undefined fields the -strict flag is returning valid. Is this known behavior?
I've tested w/ an older kubeconform version and I've also tried latest and v0.4.11.

My schema
{
  "description": "RouteConfig contains routing configuration.",
  "properties": {
    "apiVersion": {
      "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources",
      "type": "string"
    },
    "kind": {
      "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds",
      "type": "string"
    },
    "metadata": {
      "type": "object"
    },
    "spec": {
      "description": "RouteConfigSpec describes a RouteConfig.",
      "properties": {
        "proxy_group": {
          "enum": [
            "frontend",
            "internal"
          ],
          "type": "string"
        },
        "virtual_hosts": {
          "items": {
            "description": "VirtualHost is configuration for a virtual host.",
            "properties": {
              "domains": {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              "name": {
                "type": "string"
              },
              "routes": {
                "items": {
                  "description": "Route is configuration for a route in a virtual host.",
                  "properties": {
                    "backends": {
                      "items": {
                        "description": "RouteBackend specifies a Backend reference in a Route.",
                        "properties": {
                          "name": {
                            "type": "string"
                          },
                          "weight": {
                            "format": "int32",
                            "type": "integer"
                          }
                        },
                        "required": [
                          "name",
                          "weight"
                        ],
                        "type": "object"
                      },
                      "type": "array"
                    },
                    "host_rewrite": {
                      "type": "string"
                    },
                    "match": {
                      "properties": {
                        "exact_path": {
                          "type": "string"
                        },
                        "headers": {
                          "items": {
                            "description": "RouteHeaderMatch specifies a header matching rule.",
                            "properties": {
                              "exact_match": {
                                "type": "string"
                              },
                              "invert_match": {
                                "type": "boolean"
                              },
                              "name": {
                                "type": "string"
                              },
                              "prefix_match": {
                                "type": "string"
                              },
                              "regex_match": {
                                "type": "string"
                              },
                              "suffix_match": {
                                "type": "string"
                              }
                            },
                            "required": [
                              "name"
                            ],
                            "type": "object"
                          },
                          "type": "array"
                        },
                        "prefix": {
                          "type": "string"
                        }
                      },
                      "type": "object"
                    },
                    "prefix_rewrite": {
                      "type": "string"
                    },
                    "query_parameters": {
                      "items": {
                        "description": "RouteQueryParameterMatch specifies a query parameter matching rule.",
                        "properties": {
                          "exact_match": {
                            "description": "Match the value of the query parameter exactly.",
                            "type": "string"
                          },
                          "name": {
                            "description": "Name of a query parameter to match against.",
                            "type": "string"
                          },
                          "regex_match": {
                            "description": "Regular expression the value must match.",
                            "type": "string"
                          }
                        },
                        "required": [
                          "name"
                        ],
                        "type": "object"
                      },
                      "type": "array"
                    },
                    "rate_limit_zone": {
                      "type": "string"
                    },
                    "request_headers_to_add": {
                      "items": {
                        "properties": {
                          "key": {
                            "type": "string"
                          },
                          "value": {
                            "type": "string"
                          }
                        },
                        "required": [
                          "key",
                          "value"
                        ],
                        "type": "object"
                      },
                      "type": "array"
                    },
                    "timeout": {
                      "type": "string"
                    }
                  },
                  "required": [
                    "backends",
                    "match"
                  ],
                  "type": "object"
                },
                "type": "array"
              }
            },
            "required": [
              "domains",
              "name",
              "routes"
            ],
            "type": "object"
          },
          "type": "array"
        }
      },
      "required": [
        "proxy_group",
        "virtual_hosts"
      ],
      "type": "object"
    }
  },
  "required": [
    "spec"
  ],
  "type": "object"
}

my resource I'm trying to get to fail because it is defining a property at the wrong nesting level host_rewrite
---
apiVersion: routing.venmo.com/v1
kind: RouteConfig
metadata:
  name: foo
spec:
  proxy_group: internal
  virtual_hosts:
  - domains:
    - foo
    name: foo
    routes:
    - match:
        host_rewrite: bar # I want this to fail because it is defined at the wrong nesting level
        prefix: /
      backends:
      - name: outpost-internal-backend
        weight: 100

$ kubeconform -verbose -summary -kubernetes-version 1.23.9 -schema-location "routeconfig-routing-v1.json" -strict routeconfigs.yaml
/tmp/proxy-config/templates/routeconfigs.yaml - RouteConfig foo is valid
Summary: 1 resource found in 1 file - Valid: 1, Invalid: 0, Errors: 0, Skipped: 0

Hi @deepthawtz , that's a really good question - ideally it would work, but currently it won't.
Kubeconform vaildates against Kubernetes manifests against schemas in that repo - https://github.com/yannh/kubernetes-json-schema  . The tooling generates both a "strict" and a "non strict" version of the schemas. When you specify -strict, kubeconform will use the "strict" version of the schemas in that repository.
When you use CRDs however, you use a schema you generated yourself, and it depends how that schema was generated.
As for  https://github.com/datreeio/CRDs-catalog , it is good input and they might be interested in providing both a strict and non-strict version of their schemas. I would suggest opening a bug there asking for their opinion.

The parts in this script https://github.com/yannh/openapi2jsonschema/blob/master/openapi2jsonschema/command.py#L190 that refer to the "strict" mode should likely be also implemented in https://github.com/yannh/kubeconform/blob/master/scripts/openapi2jsonschema.py  so users could chose between strict and non strict mode when converting to JSON Schema. Is it correct to assume you used this tool to generate the schema you are validating against? Best, Yann

I'm using controller-gen crd to generate the CRD schemas. After looking into it more I realize that kubeconform -strict will work properly if the CRD schema contains "additionalProperties": false in whatever type: object you want to reject additional properties for. So I've found a workaround for now and looking into how I can generate "strict" schemas from our Go code directly (somehow).

After adding `` I am getting
kubeconform -verbose -summary -strict -schema-location "schema/routeconfig-routing-v1.json" -strict /tmp/proxy-config/templates/routeconfigs.yaml
/tmp/proxy-config/templates/routeconfigs.yaml - RouteConfig outpost-internal is invalid: For field spec.virtual_hosts.0.routes.0.match: Additional property host_rewrite is not allowed
/tmp/proxy-config/templates/routeconfigs.yaml - RouteConfig internal-proxy-health is valid
/tmp/proxy-config/templates/routeconfigs.yaml - RouteConfig frontend-proxy-health is invalid: For field spec.virtual_hosts.0.routes.0.match: Additional property timeout is not allowed
Summary: 3 resources found in 1 file - Valid: 1, Invalid: 2, Errors: 0, Skipped: 0

yes, probably a better way to do the conversion but I'm doing this:
ruby -rjson -ryaml -e "puts JSON.pretty_generate(YAML.load_file('schema/some-openapi.yaml'))" | jq ".spec.versions[0].schema.openAPIV3Schema" > schema.json

That's very interesting thank you! I am currently in touch with some members of the JSONSchema spec team who are explaining me that the schema in the OpenAPIV3 CRD is very close to being a JSON schema but not exactly :D Apparently from OpenAPIv3.1 what you are suggesting should be :100: If this works for you though :+1:

We can close this ticket since it doesn't look like any issue w/ kubeconform. The -strict flag works on CRD schemas, the schema just needs to set "additionalProperties": false under any objects they want to reject additional fields for. That was the key here. Thanks for the help.

I am having an issue with validating emissary's custom resources using the schema defined there in datree/CRD-catalog
schema that have been generated, as far as I understand, using the script in this current repo
And it seems to me the schema generated using this python script is always "strict".
Because additionalProperties is set to false when missing: https://github.com/yannh/kubeconform/blob/master/scripts/openapi2jsonschema.py#L28
There is only 1 override option for the root object.
Am I correct saying you can only generate "strict" variantes of the scehma using this openapi2jsonschema.py ?
If yes, would you be interested in a PR to add an option to generate "non-strict" schema ?


Add Typescript types definition for useKeyPress

As mentioned in #216, the experimental hooks have missing type definitions. This PR adds types for useKeyPress.

Closing this since we'll most likely add types for all the experimental hooks in one go rather than one by one.

Closing this since we'll most likely add types for all the experimental hooks in one go rather than one by one.

@tylermcginnis what are your thoughts about converting the hooks to typescript at source. #206 already adds type declaration but I suppose having full typescript support makes more sense. I am open to creating a PR for this, including the experimental hooks as well.

I ended up rewriting useKeyPress in typescript. Happy to help with some of the other hooks.
import { experimental_useEffectEvent as useEffectEvent, useEffect, useRef } from 'react'

// Based on:
// https://usehooks.com/usekeypress

const isKeyboardEvent = (event: Event): event is KeyboardEvent =>
  (event as KeyboardEvent)?.key !== undefined

export function useKeyPress(
  key: string,
  cb: (e: Event) => void,
  options?: {
    event?: keyof GlobalEventHandlersEventMap
    target?: Window | HTMLElement
    eventOptions?: AddEventListenerOptions
  }
) {
  const { event = 'keydown', eventOptions } = options ?? {}
  const eventOptionsRef = useRef(eventOptions)

  const onEvent: EventListener = useEffectEvent((event: Event) => {
    if (isKeyboardEvent(event) && event.key === key) {
      cb(event)
    }
  })

  useEffect(() => {
    const target = options?.target ?? window
    target.addEventListener(event, onEvent, eventOptionsRef.current)

    return () => {
      target.removeEventListener(event, onEvent)
    }
  }, [options?.target, event, onEvent])
}


Update Profile.json

Description
[Include a brief description of the changes you've made]
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
[Describe the changes you've made in detail. Be specific and include any relevant code snippets.]
Checklist

[x] I have read and followed the Contribution Guidelines.
[ ] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

I did something wrong, I'll try it later.

@StarKnightt No Problem. You can open a new PR.


YARN-11255. Support loading alternative docker client config from system environment

Description of PR
JIRA - YARN-11255
Support loading alternative docker client config from system environment
When using YARN docker support, although the hadoop shell supported
-docker_client_config

to pass the client config file that contains security token to generate the docker config for each job as a temporary file.
For other applications that submit jobs to YARN, e.g. Spark, which loads the docker setting via system environment e.g.
spark.executorEnv.*

will not be able to add those authorization token because this system environment isn't considered in YARN.
Add genetic solution to handle these kind of cases without making changes in spark code or others
Eg
When using remote container registry, the YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG must reference the config.json
file containing the credentials used to authenticate.

Unit tests and manually verified by running on EMR.
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

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

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 25s

trunk passed

+1 :green_heart:
compile
1m 46s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 48s

trunk passed

+1 :green_heart:
mvnsite
0m 58s

trunk passed

+1 :green_heart:
javadoc
1m  0s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 51s

trunk passed

+1 :green_heart:
shadedclient
21m 35s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 41s

the patch passed

+1 :green_heart:
compile
1m 25s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
1m 25s

the patch passed

+1 :green_heart:
compile
1m 21s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 29s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager: The patch generated 1 new + 15 unchanged - 0 fixed = 16 total (was 15)

+1 :green_heart:
mvnsite
0m 42s

the patch passed

+1 :green_heart:
javadoc
0m 38s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 31s

the patch passed

+1 :green_heart:
shadedclient
20m 29s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
24m  4s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

124m 55s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4884

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 73697f8f86f0 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 79be2bef4b6334b46c0f8845314f52e819a6ed22

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/1/testReport/

Max. process+thread count
562 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m  7s

trunk passed

+1 :green_heart:
compile
1m 38s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
1m 35s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 53s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

+1 :green_heart:
javadoc
0m 58s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 48s

trunk passed

+1 :green_heart:
shadedclient
21m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
1m 28s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
1m 28s

the patch passed

+1 :green_heart:
compile
1m 26s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
1m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 30s

the patch passed

+1 :green_heart:
mvnsite
0m 46s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 29s

the patch passed

+1 :green_heart:
shadedclient
21m  7s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
24m  7s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

129m  3s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4884

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux b96d121eb3ca 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 71159b4925e1924d92ec89d6bcd7a75e13049861

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/2/testReport/

Max. process+thread count
554 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

UT Failure
hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService

is not relevant to this change. Tried running it in local and its passing.

Thanks @ashutoshcipher for the patch. Overall looks good to me except a minor one.
Could you also document the steps to run an application like Spark using this new environment variable YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG in https://hadoop.apache.org/docs/r3.0.2/hadoop-yarn/hadoop-yarn-site/DockerContainers.html
For Example:
DOCKER_IMAGE_NAME=hadoop-docker
DOCKER_CLIENT_CONFIG=hdfs:///user/hadoop/config.json
spark-submit --master yarn \
--deploy-mode cluster \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_TYPE=docker \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=$DOCKER_IMAGE_NAME \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG=$DOCKER_CLIENT_CONFIG \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_TYPE=docker \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=$DOCKER_IMAGE_NAME \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG=$DOCKER_CLIENT_CONFIG \
sparkR.R

Thanks @ashutoshcipher for the patch. Overall looks good to me except a minor one.
Could you also document the steps to run an application like Spark using this new environment variable YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG in https://hadoop.apache.org/docs/r3.0.2/hadoop-yarn/hadoop-yarn-site/DockerContainers.html
For Example:
DOCKER_IMAGE_NAME=hadoop-docker
DOCKER_CLIENT_CONFIG=hdfs:///user/hadoop/config.json
spark-submit --master yarn \
--deploy-mode cluster \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_TYPE=docker \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=$DOCKER_IMAGE_NAME \
--conf spark.executorEnv.YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG=$DOCKER_CLIENT_CONFIG \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_TYPE=docker \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_DOCKER_IMAGE=$DOCKER_IMAGE_NAME \
--conf spark.yarn.appMasterEnv.YARN_CONTAINER_RUNTIME_DOCKER_CLIENT_CONFIG=$DOCKER_CLIENT_CONFIG \
sparkR.R

Thanks @PrabhuJoseph . Added the documentation

:broken_heart: -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.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 39s

trunk passed

+1 :green_heart:
compile
10m  0s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
8m 51s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
2m  8s

trunk passed

+1 :green_heart:
mvnsite
2m  9s

trunk passed

+1 :green_heart:
javadoc
2m 17s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 55s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
0m 55s

branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
21m  1s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  3s

the patch passed

+1 :green_heart:
compile
9m 11s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
9m 11s

the patch passed

+1 :green_heart:
compile
8m 49s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
8m 49s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
2m  0s

the patch passed

+1 :green_heart:
mvnsite
2m  4s

the patch passed

+1 :green_heart:
javadoc
1m 56s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 44s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
0m 43s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
23m 29s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
24m 31s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
unit
0m 51s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
asflicense
1m  9s

The patch does not generate ASF License warnings.

177m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4884

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 74a4f5d1d577 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 21aa9ab689a84f28a27313495baeec4492650770

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/3/testReport/

Max. process+thread count
559 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

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.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
28m 37s

trunk passed

+1 :green_heart:
compile
10m 37s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
9m  6s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
2m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 57s

trunk passed

+1 :green_heart:
javadoc
1m 51s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 40s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
0m 42s

branch/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
23m 31s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 57s

the patch passed

+1 :green_heart:
compile
9m 56s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
9m 56s

the patch passed

+1 :green_heart:
compile
9m  3s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
9m  3s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 51s

the patch passed

+1 :green_heart:
mvnsite
1m 43s

the patch passed

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 28s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
0m 38s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
23m 43s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
23m 58s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
unit
0m 38s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

182m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4884

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint

uname
Linux 57108abb0d6c 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a106f38a92212fb59bf2a8d6ab075e68c698e5d1

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/4/testReport/

Max. process+thread count
545 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4884/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Thanks @ashutoshcipher for the patch. LGTM, +1. Will commit it if no other comments.

Thanks @PrabhuJoseph for your reviewing and approving.


bug: Crash following 3.0 update

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.5
Operating system/version
MacOS 14.5
Describe the bug
After updating to which-key 3.0, the plugin crashes when NeoVim is opened with the following error.
Checkhealth does not report anything worrisome.
The which-key UI does not appear.

Steps To Reproduce
nvim -u repro.lua

Expected Behavior
The plugin does not crash.
The which-key UI appears
Repro
-- Bootstrap lazy.nvim
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
	local lazyrepo = "https://github.com/folke/lazy.nvim.git"
	local out = vim.fn.system({
		"git",
		"clone",
		"--filter=blob:none",
		"--branch=stable",
		lazyrepo,
		lazypath,
	})
	if vim.v.shell_error ~= 0 then
		vim.api.nvim_echo({
			{ "Failed to clone lazy.nvim:\n", "ErrorMsg" },
			{ out, "WarningMsg" },
			{ "\nPress any key to exit..." },
		}, true, {})
		vim.fn.getchar()
		os.exit(1)
	end
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
	spec = {
		{
			"folke/which-key.nvim",
			event = "VeryLazy",
			init = function()
				vim.o.timeout = true
				vim.o.timeoutlen = 300
			end,
			opts = function()
				local wk = require("which-key")

				wk.register({
					pv = { vim.cmd.Ex, "File Explorer" },
				})

				return {}
			end,
		},
	},
})

Fixed in version 3.10, currently waiting on this PR to be approved

Thank you! 💃


Unable to start the Program

I have this very helpful program running for a very long time, but now only a error at starting.
checking for online models
Traceback (most recent call last):
File "main.py", line 23, in
if should_record_model(conf.settings).check(model):
File "/home/ronald/Camsoda-Recorder/classes/camsoda.py", line 201, in check
if model['tpl'][1] in Wanted(self._settings).wanted_models:
KeyError: 1
Camsoda any Change on her Website?
Any Chance for Help?
Kind Regards
Powerbock
Windows 10 with Python3
Ubuntu 20 with Python3

any updates?


OpenSSL :  fix windows compilation error NASM not found

I guess the continus integration computer has NASM, but not every computer : I fixed it like with 1.0 OpenSSL scheme

As I mentined in gitter the 1.1.0 version doesn't work for me on Windows. Take a look at https://github.com/ruslo/hunter/tree/openssl.update branch. no-asm is already there but it doesn't help as far as I remember.


Feedback/Issue: on zcli apps:update

Issue
After I run zcli apps:update, the zcli.apps.config.json file get minified to a single line, after updating the app into the instance.
Ideally it should stay as is (un-minified or initial state).
Issue details

Command: zcli apps:update
Version: 1.0.0-beta.15
OS: Mac - Big Sur (11.6.1)

hello team,
any updates on this issue?


Inconsistent line breaks in short "if" expression

Consider the following two functions:
fn from(i: &'a Msg) -> Result<&'a OwnedFd, ()> {
    if let &Msg::A(ref b) = i { Ok(b) } else { Err(()) }
}

fn main() {
    let _x = if true { Ok(1) } else { Err(0) };
}

All lines are shorter than max_width, so why does rustfmt change the upper one but not the lower one, into this:
fn from(i: &'a Msg) -> Result<&'a OwnedFd, ()> {
    if let &Msg::A(ref b) = i {
        Ok(b)
    } else {
        Err(())
    }
}

fn main() {
    let _x = if true { Ok(1) } else { Err(0) };
}

It looks inconsistent to me, but if this is indeed correct behavior, I would like an option to keep the upper one as it is, too.

This seems to be because of the width_heuristics option single_line_if_else_max_width which is set to 50 by default.
The following config would do what you want:
version = "Two"
use_small_heuristics = "Max"

This seems to be because of the width_heuristics option single_line_if_else_max_width which is set to 50 by default.
The following config would do what you want:
version = "Two"
use_small_heuristics = "Max"

Okay,
I tried having only these two in my rustfmt.toml, then I ran rustfmt +nightly src/main.rs but it did not help - the upper one was still translated into several lines.

Are you sure you have the latest version ? I ran with 1.3.3 and the upper if stays on one line.

Indeed, that was it! Thanks!

Glad you got what you wanted! ;o)


F11.3: Variable Panel - Frontend

Acceptance criteria:

Allow changing each variable's origin attribute on edition or creation
Make Multiple attribute's first letter uppercase

The origin field should be a drop-down and not a text field


move interactive_test_util off q, rework to ES6 syntax

move interactive_test_util off q, rework to ES6 syntax
interactive_test.js and with_base_url.js still does not work as expected. Maybe we should rework commands or it does not work correctly together with common executor.

@cnishina , @heathkit could you take a look at this PR, please

@cnishina could you change label to yes and merge :)

@cnishina should I make some additional changes?

@cnishina , I merge selenium4 branch into this one. Now it is up to date.

Fixed the CLAs. This PR is great. I'm trying to remove q and this aligns well.
I also think I stabilized the Travis tests by updating the browser versions we use in Sauce Labs. If it doesn't pass, I'll restart it but I'm not concerned if it doesn't pass.


[Feature request] tmux buffer copy to system clipboard

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: MacOS 10.13.4
Hyper.app version: 2.0.0

Issue
In iTerm 2, if we enable option 'Applications in terminal may access clipboard':

Then in tmux, the copy mode can copy content to system clipboard, not just tmux's own clipboard. This is a very useful feature to me. It would be nice if hyper can also support this.

@DeciderWill I use tmux and can alt+click to copy on mac with https://github.com/zeit/hyper/issues/3592#issuecomment-492163239


serverless-1.4.1 did not become ready on OCP 4.4 RC

As such, kabanero-0.6 and 0.7 do not complete install
TODO whether serverless-1.5.0 starts up correctly on OCP 4.4 RC
status:
  conditions:
  - lastTransitionTime: "2020-03-19T21:14:03Z"
    message: 'Dependency installing: ServiceMesh control plane and member roll'
    reason: Installing
    status: "False"
    type: DependenciesInstalled
  - lastTransitionTime: "2020-03-19T21:14:49Z"
    status: "True"
    type: DeploymentsAvailable
  - lastTransitionTime: "2020-03-19T21:14:27Z"
    status: "True"
    type: InstallSucceeded
  - lastTransitionTime: "2020-03-19T21:15:29Z"
    message: 'Dependency installing: ServiceMesh control plane and member roll'
    reason: Installing
    status: "False"
    type: Ready
  version: 0.11.1

oc get smmr,smcp --all-namespaces
NAMESPACE                 NAME                                       MEMBERS
knative-serving-ingress   servicemeshmemberroll.maistra.io/default   [knative-serving]
NAMESPACE                 NAME                                               READY
knative-serving-ingress   servicemeshcontrolplane.maistra.io/basic-install   True

knative-openshift-serving pod

{"level":"error","ts":1584708857.3699315,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"knativeserving-controller","request":"knative-serving/knative-serving","error":"no matches for kind \"NetworkPolicy\" in version \"extensions/v1beta1\"","stacktrace":"github.com/openshift-knative/serverless-operator/knative-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/openshift-knative/serverless-operator/knative-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:217\ngithub.com/openshift-knative/serverless-operator/knative-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158\ngithub.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\ngithub.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134\ngithub.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait.Until\n\t/opt/app-root/src/go/src/github.com/openshift-knative/serverless-operator/knative-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

knative-serving-operator

{"level":"info","ts":"2020-03-20T07:09:06.659Z","logger":"serving_operator.knativeserving-controller","caller":"knativeserving/knativeserving_controller.go:156","msg":"Reconcile stages complete","commit":"c8dc098","knative.dev/controller":"knativeserving-controller","Request.Namespace":"knative-serving","Request.Name":"knative-serving","status":{"version":"0.11.1","conditions":[{"type":"DependenciesInstalled","status":"False","lastTransitionTime":"2020-03-19T21:14:03Z","reason":"Installing","message":"Dependency installing: ServiceMesh control plane and member roll"},{"type":"DeploymentsAvailable","status":"True","lastTransitionTime":"2020-03-19T21:14:49Z"},{"type":"InstallSucceeded","status":"True","lastTransitionTime":"2020-03-19T21:14:27Z"},{"type":"Ready","status":"False","lastTransitionTime":"2020-03-19T21:15:29Z","reason":"Installing","message":"Dependency installing: ServiceMesh control plane and member roll"}]}}

We've confirmed that Serverless 1.5.0 starts up correctly on OCP 4.4 (and OCP 4.3).  We are evaluating whether it's going to be necessary to support OCP 4.4 for Kabanero 0.6.x and 0.7.x.

It is not going to be necessary for Kabanero 0.6.x and 0.7.x to support OCP 4.4.  We should be able to support OCP 4.4 starting with Kabanero 0.8.0-rc.1.


Deb package not compatible with xenial

The deb assumes Upstart, while Ubuntu Xenial has switched to systemd

There is a systemd unit file for fullerite service, closing the issue.


Source mappings have no match on the AST

Environment information

py-solc-x Version: 0.8.2
solc Version: 0.6.8+commit.0bbfe453.Linux.g++
Python Version: 3.6.9
OS: Ubuntu 18.04.4 LTS

What was wrong?
I compiled the Fomo3D contract using the 0.4.24+commit.e67f0147.Linux.g++ solc version. Afterwards, while observing the trace of the following transaction, I noticed that some source mappings of the bytecode that py-solc-x outputs, have no match on the AST that py-solc-x outputs.
Below are the source mappings that have no match:
Could not find ast node from source mapping: 49693 : 37 : 0
Could not find ast node from source mapping: 49693 : 65 : 0
Could not find ast node from source mapping: 49693 : 37 : 0
Could not find ast node from source mapping: 49693 : 65 : 0
Could not find ast node from source mapping: 49693 : 65 : 0
Could not find ast node from source mapping: 15759 : 18 : 0
Could not find ast node from source mapping: 15759 : 18 : 0
Could not find ast node from source mapping: 18654 : 9 : 0
Could not find ast node from source mapping: 46882 : 21 : 0
Could not find ast node from source mapping: 46882 : 30 : 0
Could not find ast node from source mapping: 46882 : 21 : 0
Could not find ast node from source mapping: 46882 : 30 : 0
Could not find ast node from source mapping: 46882 : 30 : 0
Could not find ast node from source mapping: 11308 : 10 : 0
Could not find ast node from source mapping: 11429 : 8 : 0
Could not find ast node from source mapping: 10295 : 42 : 0

Note: The above message is not an actual error message, it's simply me annotating what I perceive the mistake to be in the example above.

Hi,
What are the exact outputs you're generating?  There are two types of AST, maybe you're looking at the legacy one.  It's just a guess though.. I've never run into this issue before.
If you aren't, I'd suggest compiling via the standard JSON input and using the source map and AST returned that way.

I am using the new AST, not the legacy one.

Can you share the code you're using?  I just compiled the contract source from etherscan, and I'm not seeing any of the offsets you listed in the deployedSourceMap or sourceMap outputs.

Here's where I got the code from.
Also, the compilation settings I used are the following:
{
    'language': 'Solidity',
    'sources': {
        '/tmp/temp.sol': {'urls': ['/tmp/temp.sol']}
    },
    'settings': {
        'optimizer': {'enabled': True, 'runs': 50},
        'outputSelection': {
            '*': {
                '*': ['evm.deployedBytecode.sourceMap', 'evm.deployedBytecode.object'],
                '': ['ast']
            }
        }
    }
}

Yeah, same thing. Compiling with the JSON you give above, and using the source as taken from contract-library, I'm not producing a sourceMap that has any of the offsets you mention in the original message.

I found a bug in my code and while it is now fixed and those messages are not being displayed, some others (very few) have taken their place. The whole point of this issue was to ascertain if it would be possible for source mapping mismatches to appear. As far as I understand, such behavior is not to be expected. I'll keep this issue open just in case.

From my experience, offsets is sometimes missing from the sourceMap (https://github.com/ethereum/solidity/issues/9006), but I've never encountered a mismatch when an offset is given.
Not sure if it's useful for you, but here's some code I wrote that does a lot of association between the source map and the AST: iamdefinitelyahuman/brownie:brownie/project/compiler/solidity.py

Well, in the same example, I did come across these unmatched mappings, which seem to be invalid.
15759 : 18 : 0
18654 :  9 : 0


Update crc32.cpp

some points in the code have been improved

Seems like actually there is nothing to do with current crc32 code


ngc error: Compilation failed - ionic build android

I have updated an application using Ionic2 RC. In my application, I managed to load/create a component dynamically. It worked fine when debugging, but when I tried to build android, I had the error below:
[14:38:42]  ngc: Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 65:17 in the original .ts file), resolving symbol COMPILER_PROVIDERS in<EMAIL_ADDRESS>resolving symbol AppModule in c:/MCNEXT/Vinci/Vinci-RSC%20Mobile/.tmp/app/app.module.ts, resolving symbol AppModule in c:/MCNEXT/Vinci/Vinci-RSC%20Mobile/.tmp/app/app.module.ts at simplifyInContext (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\static_reflector.js:469:23) at StaticReflector.simplify (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\static_reflector.js:472:22) at StaticReflector.annotations (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\static_reflector.js:61:36) at _loop_1 (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\codegen.js:53:54) at CodeGenerator.readFileMetadata (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\codegen.js:66:13) at c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\codegen.js:100:74 at Array.map (native) at CodeGenerator.codegen (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\codegen.js:100:35) at codegen (c:\MCNEXT\Vinci\Vinci-RSC%20Mobile\node_modules\@angular\compiler-cli\src\main.js:7:81) at Object.main<EMAIL_ADDRESS>Is COMPILER_PROVIDERS supported with AOT ?

Try npm run build --dev
I still have issues when I remove --dev

Hello, thanks for using Ionic! This is actually NGC (the Angular 2 template compiler) throwing about an error in your code. NGC does typechecking of your templates, which means that it also knows how to throw errors about methods and variables bound to in your template. I would recommend asking around on our forum for help tracking down the bug in your code. The reason this error does not happen when doing a dev build (by running ionic serve) is because our dev build does not run the Angular 2 template compiler. Thanks!

Thanks for the info @jgw96
@h2qutc Are you creating a new object in your providers array?

I too have this problem and am having great difficulty tracking down what is causing it. Is it possible to do ionic build ios in a dev build?

@vardas-bill I was creating a new object in the providers. If you are doing that you will want to use a factory function instead. Post what your app.module.ts looks like.

Thanks @tadchristiansenli that was it!

Hi,
@tadchristiansenli , can u show how you do please?  My app.module.ts looks like:
var APP_PAGES = [   BlogPage,   CommunitiesPage]
export function appPagesFactory(): any {   return [...APP_PAGES];  }
@NgModule({        declarations: [ MyApp,     DynamicComponent,     appPagesFactory(),      //APP_PAGES,     APP_DIRECTIVES   ],
I got the same error:
ngc: Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 20:13 in the original .ts file), resolving symbol CommunitiesPage
Do you have any idea ?


native example has no attribute IS31FL3741_FrameBuffer'

Adafruit CircuitPython 8.0.5 on 2023-03-31; Adafruit Feather ESP32S2 with ESP32S2
Board ID:adafruit_feather_esp32s2

https://github.com/adafruit/Adafruit_CircuitPython_IS31FL3741/blob/5ac6531e26ecc462da9a21c5dca2d16be038c85d/examples/is31fl3741_native.py#L29
Was this supposed to be changed to pixelbuf?  I see no mention in the library or examples of a reference to IS31FL3741_FrameBuffer.
is31_fb = adafruit_is31fl3741.IS31FL3741_FrameBuffer(
    width=54,
    height=15,
    is31=is31,
    scale=True,
    gamma=True,
    mapping=glassesmatrix_ledmap_no_ring,
)

AttributeError: 'module' object has no attribute 'IS31FL3741_FrameBuffer'

I believe IS31FL3741_FrameBuffer is only available natively from applicable CircuitPython firmware:  https://docs.circuitpython.org/en/latest/shared-bindings/is31fl3741/index.html#is31fl3741.IS31FL3741_FrameBuffer
Not exactly sure how it relates to the PixelBuffer, but based on how different the arguments, I think they're meant to be distinctly different.

I think additional information about compatibility is good, is that something you're interesting in helping out with?

@tekktrik It only needs a comment in the header.  I can do that sure.


v-else not work when together with v-show on custom component

Vue.js version
1.0.21
Reproduction Link
http://www.webpackbin.com/412B9bgJb
Steps to reproduce
click Toggle button
What is Expected?
when MyComponent is showing, the msg should be hidden
What is actually happening?
the msg always shows

I'm taking a look, not sure if it's a bug or not

Ok, confirmed. It only happens on v-show though, it works on v-if
Thanks for the bug submission! :smile:

seems to do the exact opposite on templates
http://codepen.io/ThatTomPerson/pen/vGdyoB

@ThatTomPerson v-show doesn't work on <template> by design, so that's working as intended.

@yyx990803 Ah ok, I'll just replace it with a div and hope the designer doesn't notice 😄

v-show shouldn't be connected to v-else. As this doesn't natively translate to traditional programmatically logic.

@blake-newman the v-show is just an if that hides instead of removing. v-else turns out to be very handy, it definitely reads better than v-show="!expr"

BTW I didn't forgot about the issue. I couldn't allocate enough time for it in the past two weeks 😞
I'll find some time this weekend for sure

@posva Understand about the internals. Question in my mind is: 'Should v-show be combined with v-else?'
One issue is that v-else is currently terminable. Which means the logic behind how v-else works will completely differ based on the prefixing directive. I believe in my own opinion that this would  be confusing.
What happents if there is a v-if and a v-show what would v-else be applied to. This is a weird case, but it is very valid to have v-if and v-show available on a single element.

The v-show would to apply to both I guess. I'm not sure about the use case thought
I think v-else should be replaced by v-show="!expr", and let v-if work as it is but I'm not sure this would solve the real problem which I cannot recall clearly but it has to deal with directives priorities that were not applied for components (component is a directive itself with a given priority)

I understand that it is tempting to get v-show to work with v-if once you think about it, but at first it felt a bit counter-intuitive because there would be no v-if to look for.
Anyway, I also agree that the framework shouldn't be changed to accommodate this behaviour.

@posva If targetting both, what if the case is that you don't want the v-show="!expr" and want the v-else applied to the v-if only. Lot more complexity involved internally where this could be done easily in user land.

But why would you need to use v-id and v-show ?

You have a scenario where you don't want the code to evaluate further, using v-if as terminable. At the same time you want v-show/v-hide to show and hide without removing an instance. I think it's very confusing to have a logical directive available to two other directives.

In that case you should use a :style bind

I don't see how :style could fix what @blake-newman just described.
But I do agree with you that v-show and v-if are used for content toggling. One works with v-else the other one doesn't. Makes sense to me that the framework behaves like this.

@ruiposse v-show toggles a display: none on the element

computed: {
  style () {
    if (!this.show) {
      return { display: 'none' }
    } else {
      return {}
    }
  }
}

Of course it does, that's why you use v-show to do that and you don't have a v-else along with it.

I might have not understood what @blake-newman said. I don't understand what you're trying to say, sorry... You can add a div at the end with a v-else and change the this.show on the computed property by something else. I was trying to show you how to achieve a v-if + v-show + v-else with v-else only affecting the v-if although I'm don't even know if there's a bug about that atm

This has to be the most controversial feature request for Vue haha.
What im trying to say is that it's been noted that trying to mimic JS logic in templates isn't generally a good idea. This is why we have dropped trying to add v-switch and v-case. If logic in templates is to exist then it should be as simple as possible.
Making v-show and v-hide work with v-else, may just cause unnecessary confusion, especially as scanning a template you will try to spot a matching v-if as it makes contextual sense.
As this is achievable in user land by a simple negate, i'd avoid adding more to Vue than is necessary. Expression logic in templates should be simple, so it should be just as simple to add ! to the expression. If any expression is complex then it really should be handled in the JS.

We're not mimicking js logic here, otherwise there should be no v-if nor v-show.

Making v-show and v-hide work with v-else ...

v-hide doesn't exist so I'm not sure what's your point there. v-else is already supposed to work with v-show but it doesn't work with components, that's the bug.
A simple negate duplicates the expression in multiple places which isn't good.
We cannot drop v-else support.
Also I don't understand what happened with @ruiposse , I really think you misunderstood what I was talking about: I am not talking about supporting v-show alongside v-if. And then @blake-newman brought the "v-else should not be used with v-show" subject. Can you both of you explain very shortly what are you trying to say and if it has anything to deal with the original bug, please?

<template>
  <my-component v-show="showMy"></my-component>

{{ msg }}

  <button v-on:click="toggle">Toggle</button>
</template>

v-else is a operator styled directive. ifand else are programmatically bound to each other in languages. v-show on the other hand has no relevance to any language. Expectations when looking at a template with v-else and v-show could be misleading.
It seems like an anti pattern to extend v-else to work with v-show. No real need as you can achieve easily with negating the expression, which in my view is alot more declarative.
Implementing this as suggested will complicate the internals of Vue to deal with such use case, which is fully achievable in user land.

In the original bug, looking at the webpackbin you provided, you're expecting v-else to work with v-show. I don't think this is something that the framework should support.
@blake-newman is literally saying the same thing!
In my opinion v-else shouldn't work with v-show, that's it.
I don't really know how to be much more clear than this.

In the original bug, looking at the webpackbin you provided, you're expecting v-else to work with v-show. I don't think this is something that the framework should support.

We cannot introduce such a breaking change in 1.1

After reading through the discussion, I'm inclined to agree that v-else should not work with v-show in the first place. That's going to be the case in 2.0 and this is going to be a wontfix for 1.x since the workaround is trivial.

At least fix the document.

@Centaur I'm doing that this evening. Thanks for reminding it. No need to be salty 😛


TypeScript error - "playerRef" is required prop

I am getting the error Property playerRef is missing on type '{src: string; autoPlay: true; controls: true; width: string;} 'but is required in type' HlsPlayerProps'. Can you please make this props an optional parameter, as it is in the examples?

I found that as well.  I modified index.d.ts to make playerRef optional.  After some time I ended up using directly hls.js instead.

This issue was fixed but unfortunately introduced a bug where it redefined the ref every render.
I maintain a fork with this fox, among other bug fixes here: https://github.com/cgilly2fast/react-hls


Could not find generator 'react_on_rails:install'.

I am trying to add react_on_rails on my rails exisiting application but when I run rails generate react_on_rails:install, I get the following error :-
Running via Spring preloader in process 28730
/Users/kush/.rvm/gems/ruby-2.5.7/gems/railties-<IP_ADDRESS>/lib/rails/generators/rails/app/app_generator.rb:245: warning: already initialized constant Rails::Generators::RAILS_DEV_PATH
/Users/kush/.rvm/gems/ruby-2.5.7/gems/railties-<IP_ADDRESS>/lib/rails/generators/rails/app/app_generator.rb:245: warning: previous definition of RAILS_DEV_PATH was here
/Users/kush/.rvm/gems/ruby-2.5.7/gems/railties-<IP_ADDRESS>/lib/rails/generators/rails/app/app_generator.rb:248: warning: already initialized constant Rails::Generators::AppGenerator::WEBPACKS
/Users/kush/.rvm/gems/ruby-2.5.7/gems/railties-<IP_ADDRESS>/lib/rails/generators/rails/app/app_generator.rb:248: warning: previous definition of WEBPACKS was here
Could not find generator 'react_on_rails:install'. Maybe you meant "react:install"?
Run `rails generate --help` for more options.

cc: @justin808 Any would be really appreciated!

Solved after clearing my rvm cache.


Run conformance tests for KafkaSource

Describe the bug
We don't run conformance tests for the new KafkaSource.
Expected behavior
Conformance tests for the new KafkaSource pass.
Knative release version
devel
Additional context
/area source
/priority important-soon
/area test

/remove-lifecycle stale

Is this issue Up for work?


Improve eBPF loading and chaining

@delaramamiri see the windows compilation error this is hitting:

Error: C:\Users\runneradmin\go\pkg\mod\github.com\cilium\ebpf@v0.10.0\link\socket_filter.go:34:34: cannot use int(fd) (value of type int) as type syscall.Handle in argument to syscall.SetsockoptInt


buildRustPackage uses different compilation options for tests

Issue description
https://github.com/NixOS/nixpkgs/blob/57b1f5386289dbe4be14ac8960687c12334d6dfb/pkgs/build-support/rust/default.nix#L105-L106
https://github.com/NixOS/nixpkgs/blob/57b1f5386289dbe4be14ac8960687c12334d6dfb/pkgs/build-support/rust/default.nix#L124
By defaul buildRustPackage runs

cargo build --release
cargo test
Which means that

All libraries must be recompiled for the tests to run
The code being tested has different compilation options

It'd be nicer to use cargo test --${buildType}

just for the record, this is addressed in #82342

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/rust-build-speed-improvements/7225/1

Just realized that this issue is still open, but it's in fact fixed -> closing.