[ZEPPELIN-1249] build all submodules w/ the same scala version

What is this PR for?
This uses the same Scala version throughout modules, allowing us to use only Scala 2.11.
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1249
https://issues.apache.org/jira/browse/ZEPPELIN-2681
Questions:

Does the licenses files need update?
No

Is there breaking changes for older versions?
No

Does this needs documentation?
No

Regarding verification, how do you suggest I go about that? We've been using this setup internally for some time, but we only use a few of the interpreters (spark, scalding, jdbc, md) - not sure if that could lead to any sort of runtime issue on other interpreters, but I find it highly unlikely..
Can you clarify on the flexibility bit? Not sure I understand what's the benefit of using different versions at the same time (not to mention Scala 2.10 is EOL since 2016).

I realize 2.10 is EOL but as mentioned, from a while back many platforms are still running only on 2.10. Even Spark still supports 2.10 as of the latest release 2.2.0 from yesterday. The reason is many enterprises have applications that cannot be easily migrated to 2.11.
It is possible that some users are only using a small number of interpreters (as you do) and they need a particular scala version. So instead of forcing all submodule to always use the same scala version, how about set a global scala version as the default but each submodule still has its own spark.scala.version that can be set in the maven command line when building?

sounds good, I’ll do that then

From: Felix Cheung <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 12, 2017 9:34 AM
Subject: Re: [apache/zeppelin] [ZEPPELIN-1249] build all submodules w/ the same scala version (#2480)
To: apache/zeppelin <zeppelin<EMAIL_ADDRESS>Cc: Herval Freire <hervalfreire<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>I realize 2.10 is EOL but as mentioned, from a while back many platforms are still running only on 2.10. Even Spark still supports 2.10 as of the latest release 2.2.0 from yesterday. The reason is many enterprises have applications that cannot be easily migrated to 2.11.
It is possible that some users are only using a small number of interpreters (as you do) and they need a particular scala version. So instead of forcing all submodule to always use the same scala version, how about set a global scala version as the default but each submodule still has its own spark.scala.version that can be set in the maven command line when building?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/apache/zeppelin/pull/2480#issuecomment-314824983, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAAV6pwoowBIvtcK7sFeNYkcva3qjV-Iks5sNPWAgaJpZM4OTkY9.

hmm, I did a quick check, eg, for beam it's still building against 2.10 https://github.com/apache/beam/blob/master/runners/spark/pom.xml#L229
Same for Ignite https://github.com/apache/ignite/blob/master/pom.xml#L521

IMO, it is not so urgent to do this. Interpreters and zeppelin server run in different process, so theoretically it is not necessary to build them together. After we move interpreters out of zeppelin project, most of problems can be addressed.

@zjffdu what's the benefit of not doing it, given it's a simple change?

@herval This is an improvement PR, not bug fix PR. And based on the discussion above, it may also introduce some other issues or overhead for users (e.g. some interpreters don't support scala 2.11).
Besides, after we move out interpreters from zeppelin project, scala version should not be an issue anymore. Let me know your concern and if I miss anything. Thanks


Fix handling of unknown column types

[x] Do only one thing
[x] Non breaking API changes
[x] Tested

What did this pull request do?

When using the go clickhouse driver, scanning into sql.RawBytes is not supported for most columns. I think the database/sql standard only guarantees that all columns can be converted to *interface{}, not RawBytes, so gorm should not make this assumption.
This issue doesn't affect most drivers like sqlite, mysql, postgres, but it does affect clickhouse. The following test will pass once this change is merged: https://github.com/go-gorm/clickhouse/pull/128
User Case Description

This might broken query with maps?
If it is possible to make the clickhouse driver support sql.RawBytes, I think this might be a better solution?

Why should it break maps? I think any driver would be happy to scan a map into interface{}?

I don't think changing the clickhouse driver is the right solution because the clickhouse driver isn't violating the spec


Consider use react-web

https://github.com/taobaofed/react-web

hi @yuanyan,
You can go with react-web if you prefer that.
Just replace 'react-native-web' with react web in webpack config.
alias: {
'react-native': 'react-native-web', //change this to react-web
}
and install the dependencies.


Drag is not working in wsl vim

Windows Terminal version
1.12.10982.0
Windows build number
10.0.19044.0
Other Software
vim 8.2.4827 (Arch Wsl)
Steps to reproduce

Start Vim

vim --clean +'set mouse=a' +'call popup_create("test", #{drag: 2, border: [2,2,2,2]})' +'split'

Try dragging the statusline and the popup

Expected Behavior
In wsltty:

Actual Behavior
In wt:

Hmm. I wonder which mouse sequence this is using that we don't support. It's not supported in conhost either, but tmux mouse dragging does seem to still work.


#17279 to #17326 checks via Muckrock

Via Muckrock, I
requested
Checks 17279, 17282,17305, 17306, 17310, 17312, 17315, and 17326

I have no idea why these are conflicting...


Fix array index overflow in CircularLossyQueue

This PR will fix possible array index overflow in CircularLossyQueue
Changes

Checklist

[x] tested locally
[ ] updated the docs
[x] added appropriate test
[x] signed-off on the DCO referenced in the CONTRIBUTING link below via git commit -s on my commits, and submit this code under terms of the Apache 2.0 license and assign copyright to the Quartz project owners
(If you're not using command-line, you can use a browser extension )

In submitting this contribution, I agree to the terms of contributing as referred to here:
https://github.com/quartz-scheduler/contributing/blob/main/CONTRIBUTING.md

Thanks


version of download on http://handlebarsjs.com/

Hi,
http://handlebarsjs.com/ offers to download version 3.0.0
Where's 3.0.1?

From the README

Alternatively, if you prefer having the latest version of handlebars from the 'master' branch, passing builds of the 'master' branch are automatically published to S3. You may download the latest passing master build by grabbing a handlebars-latest.js file from the builds page. When the build is published, it is also available as a handlebars-gitSHA.js file on the builds page if you need a version to refer to others. handlebars-runtime.js builds are also available.

Updated. Thanks for reporting this!


Equality testing instead of identity

Identity comparing here will result in errors when the input string is created in non trivial ways. for example:
import tensorflow as tf
import tensorflow.keras as keras

standardize = ''.join(['lower', '_and_strip_punctuation'])
layer = keras.layers.experimental.preprocessing.TextVectorization(standardize=standardize)
layer(tf.constant([['hello'], ['hello world']]))

# ValueError: lower_and_strip_punctuation is not a supported standardization. TextVectorization supports the following options for `standardize`: None, 'lower_and_strip_punctuation', or a Callable.

split = ''.join('whitespace')
layer = keras.layers.experimental.preprocessing.TextVectorization(split=split)
layer(tf.constant([['hello'], ['hello world']]))

# ValueError: whitespace is not a supported splitting.TextVectorization supports the following options for `split`: None, 'whitespace', or a Callable.

This was tested with
>>> tf.__version__
'2.1.0-dev20191119'

And Python3

@googlebot I signed it!

Looks good to me, but can you also write a test please? The one example you mentioned at the start of the issue should be good.

@mihaimaruseac just added the tests.

FAIL: Found 2 non-whitelisted pylint errors:
tensorflow/python/keras/layers/preprocessing/text_vectorization_test.py:475: [C0326(bad-whitespace), ] Exactly one space required after comma

tensorflow/python/keras/layers/preprocessing/text_vectorization_test.py:485: [C0326(bad-whitespace), ] Exactly one space required after comma

@mihaimaruseac Fixed the lining issues. I'm new to Python, running:
pylint --rcfile=/tmp/pylintrc tensorflow/python/keras/layers/preprocessing/text_vectorization_test.py

still returns a lot of warnings but they don't seem related to this PR.

@dfalbel Could you please check reviewer comments and keep us posted. Thanks!

yes, I'll do it


[BUG] Saswell SEA802-Zigbee only showing off button and gets stuck

Describe the bug
After adding my thermostat the climate card - aside of the temperature control - only shows the off-button. When I click on it, the thermostat is turned off and I can't control it anymore from HA. I have to manually set the thermostat to a specific temperature instead to switch the hvac_mode to heat. I tried overriding this with a customized yaml but then I get the following error while clicking on the heat button:
Nov  6 14:03:46 homeassistant homeassistant[909]: #033[33m2022-11-06 14:03:46.293 WARNING (MainThread) [homeassistant.components.zha.entity] climate.thermostat_thermostat: can't set 'heat' mode. Supported modes are: [<HVACMode.OFF: 'off'>]#033[0m

To Reproduce
Steps to reproduce the behavior:

Pair thermostat
set temperature
clickoff-button
try to set temperature again. It won't change.

Expected behavior
Offer a working off and heat button.
Screenshots

Device signature
IEEE: 84:ba:20:ff:fe:3c:e6:02
Nwk: 0xc598
Device Type: EndDevice
LQI: Unbekannt
RSSI: Unbekannt
Zuletzt gesehen: 2022-11-06T13:54:12
Energiequelle: Battery or Unknown
Eigenart: zhaquirks.tuya.ts0601_trv_sas.Thermostat_TZE200_c88teujp ``` marks.

Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant Supervised",
    "version": "2022.11.1",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.7",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Berlin",
    "os_name": "Linux",
    "os_version": "5.10.0-19-amd64",
    "supervisor": "2022.11.dev0401",
    "host_os": "Debian GNU/Linux 11 (bullseye)",
    "docker_version": "20.10.21",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.28.3",
      "requirements": [
        "aiogithubapi>=22.2.4"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.34.2",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.84",
      "zigpy-deconz==0.19.0",
      "zigpy==0.51.5",
      "zigpy-xbee==0.16.2",
      "zigpy-zigate==0.10.3",
      "zigpy-znp==0.9.1"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      }
    ],
    "dependencies": [
      "file_upload"
    ],
    "after_dependencies": [
      "onboarding",
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 50584,
    "manufacturer": "_TZE200_yw7cahqs",
    "model": "TS0601",
    "name": "_TZE200_yw7cahqs TS0601",
    "quirk_applied": true,
    "quirk_class": "zhaquirks.tuya.ts0601_trv_sas.Thermostat_TZE200_c88teujp",
    "manufacturer_code": 4098,
    "power_source": "Battery or Unknown",
    "lqi": null,
    "rssi": null,
    "last_seen": "2022-11-06T13:54:12",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": 260,
          "device_type": "0x0301",
          "in_clusters": [
            "0x0000",
            "0x0001",
            "0x0004",
            "0x0005",
            "0x0201",
            "0xef00"
          ],
          "out_clusters": [
            "0x0001",
            "0x000a",
            "0x0019",
            "0x0201"
          ]
        }
      }
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "sensor.thermostat_battery",
        "name": "_TZE200_yw7cahqs TS0601"
      },
      {
        "entity_id": "sensor.thermostat_hvac_action",
        "name": "_TZE200_yw7cahqs TS0601"
      },
      {
        "entity_id": "climate.thermostat_thermostat",
        "name": "_TZE200_yw7cahqs TS0601"
      }
    ],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "THERMOSTAT"
      }
    ],
    "user_given_name": "Heizung Arbeitszimmer",
    "device_reg_id": "35ffd04914ede394cd7822dc087fa932",
    "area_id": "arbeitszimmer",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "THERMOSTAT",
          "id": 769
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": "_TZE200_yw7cahqs"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": "TS0601"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0004": {
            "endpoint_attribute": "groups",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0005": {
            "endpoint_attribute": "scenes",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xef00": {
            "endpoint_attribute": "tuya_manufacturer",
            "attributes": {
              "0x0165": {
                "attribute_name": "system_mode",
                "value": 0
              },
              "0x0267": {
                "attribute_name": "occupied_heating_setpoint",
                "value": 90
              },
              "0x0266": {
                "attribute_name": "local_temperature",
                "value": 234
              },
              "0x0569": {
                "attribute_name": "battery_state",
                "value": 0
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 200
              }
            },
            "unsupported_attributes": {}
          },
          "0x0201": {
            "endpoint_attribute": "thermostat",
            "attributes": {
              "0x0000": {
                "attribute_name": "local_temperature",
                "value": 2340
              },
              "0x0012": {
                "attribute_name": "occupied_heating_setpoint",
                "value": 900
              },
              "0x001c": {
                "attribute_name": "system_mode",
                "value": 0
              },
              "0x001e": {
                "attribute_name": "running_mode",
                "value": 0
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x000a": {
            "endpoint_attribute": "time",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0201": {
            "endpoint_attribute": "thermostat",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}``` marks.

Additional logs
Paste any additional debug logs here.

Don't remove the extra line breaks outside the ``` marks.

Additional context
MQTT Information

The Saswell SEA802 is not updated with more function then basic from it was added for nearly 2 years ago.
Our users have trying fixing it and getting all function from this devices and its one working custom quirk for it but is not being merged in ZHA then the code is failing some test (code).
Configure local quirk in (Z)HA and adding the quirk from the post and restart HA
https://github.com/zigpy/zha-device-handlers/issues/1189#issuecomment-1287512365.
Also reading the thread for more information.

@MattWestb Thanks for pointing that out. I've read the whole thread and the quick seems to be broken. After adding it and re-pairing my thermostat, now I see a bunch of switches where I can only guess what they do. Why is this so difficult where zigbee2mqtt has no problems with that at all?

´ZHA can only using real Zigbee devices that is Zigbee compatible so we can only using the standard things and not investing new one then we is braking  the system.
Its possible writing custom GUI things but no user have not doing it for tuya TRVs.
TRVs that is more standard is no problem in ZHA but tuya is zero Zoigbee standard and we is trying doing the best of it.
If you is reading the first post in the issue you is having the matrix wot all switches is and can renaming them.
Since currently we are not able to change names of on_off entities below is the description:

Window Detection
Child Lock
Anti-Freeze
Limescale Protection
Schedule Mode On/Off
Away Mode

Have you testing if the TRV functionality is OK ?

@MattWestb

but tuya is zero Zoigbee standard and we is trying doing the best of it.
Yeah, that's what I have already learned while building my own system. I started with openhab and zigbee2mqtt first, but later changed to HA because this software really interacts with the setup process very well. Even though Linux is my daily business I sometime prefer not to write every config file by hand ;-)

Also, it's a pity what the European zigbee-market is offering right now. So many products having 'zigbee' written on their package but using proprietary implementations (like Bosch) or some EA-style subscription moneymaker licensing (like Tado). At least, Zigbee imho seems to be the best protocol right now aside from zwave where at least we have some open standard...
The quirk seems to be working fine. Thanks for telling me the correct order of the switches. I have had some very steep learning curves in the past few days from both automation systems and sometimes I'm getting tired from reading doc after doc.
I'll close this issue as solved. Thank you for you help!

I was having one RaspBee I but is in the black box bad devices now then the company is not supporting there sold products you have paying for.
Its 2 versions of the Sonoff Zigbee 3 stick one with TI chip and one newer with Silabs EZSP both shall being OK but i think they still have some problems with it but i think it shall being fixed in upcoming firmware releases.
Some clue for not so bad Zigbee devices you can finding if they have being certificated at https://csa-iot.org/csa-iot_products/?p_keywords=&p_type[]=14&p_program_type[]=966&p_certificate=&p_family= but is no grantee that they is working 100% then can still using custom cluster and attributes that we is not knowing or bad hard and / or software (OSRAM).
tuya have 2 types of Zigbee devices most is normal Zigbee devices that can working OK or need some patching for working OK (like most LIDL devices) and some that is using one zuya MCU and is only using Zigbee for tunneling tuya DP commands to the tuya cloud. You device is the last type and its not documented and must being squeezed to one "normal Zigbee device" for working OK in ZHA.
If having problems keep asking its lot of brave users with different experience and some great devs that is helping then have time here and in the end most is being fixes then its possible.
And we is learn new things all the life :-)

@MattWestb Just one last question in advance: would you recommend using tuya devices out of the box or use https://github.com/ct-Open-Source/tuya-convert ?

The link is using ESP or other WiFI chips and tunneling to the cloud the same way your device is doing but your device cant being converted then its using one Zigbee module and the MCU is locked to the type of radio module (Its little different protocol steering / init the modules).
If using tuya WiFi device with ESP i have converting them to ESPHome but i dont have that.
And tuya is saying over 11 000 devices and many is using  Zigbee for tunneling and is only using different DP (tuya commands) for all devices you is understanding wi is lost until some is getting the right commands in place.
Lights i using mostly IKEA then they is updating the device firmware (most no name and also known name is not doing that) but good sensors that is not very expensive you only finding CE ones (CE = China Expert and not Certificate European).


Update dependencies

Codecov Report
Patch and project coverage have no change.

Comparison is base (f8ecfc9) 100.00% compared to head (8ea99c0) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #66   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          130       130
  Branches         9         9
=========================================
  Hits           130       130

Impacted Files
Coverage Δ

src/hya/resolvers.py
100.00% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Labels for classification

Hello,
Thank you for sharing an interesting dataset.
I am currently exploring this dataset as it consists of sketches. I  wanted to know how to get a unique label from the sequence information , so that could be used for either classification or object detection task?
Also, what is the distribution of graphs sketches , are the graphs repeated in train-val and test sets?
Thank you
Anshu

Hi Anshu,
due to the way the data is presented, there are no specific graph level labels that are suitable for graph level property prediction. In our paper, we did consider the supervised problem of predicting constraints from entities ("autoconstrain"), which can be viewed as a sequence to sequence supervised problem.
The current version of the data presents repeats between train-val-test due to natural repeats occurring in the data. I recommend you de-duplicate the data if you require unique data (happy to provide some example code if you need).
Hope that helps!


Allow createWebviewPanel in row above active column

I have an extension that I'm writing which uses a webview, and the most suitable format for this extension is a banner at the top of the editor. It would be great if we could specify to place the view above the current active column (basically do a "Split Up"). I see that it's possible to place the new view beside the active view, then the user can manually switch the orientation to stack vertically, but it'd be nice if this could be automated.

Closing this since it has not received much interest since it was opened
This is not also not possible to do with normal text editor today. More fine grained control over editor layout may fall under #15178


Port prefixes for primitives

Recently we had changes to prim_fifo_sync and prim_fifo_async to get from full/empty to ready/valid signals. What I completely missed in the review was our naming convention, which requires _i/_o suffixes for these ports (https://github.com/lowRISC/style-guides/blob/master/VerilogCodingStyle.md#suffixes).
@NilsGraf sorry for missing this earlier, is this something you could open a PR for? (I know it's painful to change this again.)

Reviving this old issue so that we can address some of them then close. We would also have to revive the lint check to feel like we've covered enough to close it. So pinging @NilsGraf to see if he can remind us how to do that. I don't think we need to enable it for all time, but it would make sense to get a fresh accounting. This below is based upon the last run a year ago.

[ ] prim_subreg*.sv - I'm suggesting we leave this as is, _q / _d names at least are relatively standard, and the file count to be effected here is huge.
[ ] *_reg_top.sv - ditto above
[ ] ibex_*.sv - not seeing any errors here anymore, but I'm not sure how to run the rule, the scripts have changed
[ ] prim_fifo*.sv - I think this should be fixed, am creating a PR
[ ] rv_plic*.sv - I think this should be fixed, will create a PR
[ ] spi_fwm*.sv - there are just three signals here, could do a quick fix, but need to go in after #2743 goes through
[ ] prim_arbiter.sv - this doesn't exist anymore, replacements have been fixed
[ ] prim_sram_arbiter.sv - I think this should be fixed, will create a PR
[ ] prim_flop_2sync.sv - I think this should be fixed since prim_flop was fixed, will create a PR
[ ] prim_secded*.sv - uses in and out; could be fixed, but probably OK to leave
[ ] tlul_socket*.sv - just the n1 version is missing _i on dev_select
[ ] timer_core.sv - internal core, could skip
[ ] rv_timer.sv - already fixed
[ ] uart_*.sv- top is fixed, internals could stay, designer's discretion (@eunchan)
[ ] hmac_core.sv - internal file, could stay, designer's discretion (@eunchan)
[ ] sha2*.sv - ditto above (@eunchan)
[ ] usb*.sv - these appear to be all fixed
[ ] sram2tlul.sv - I think this should be fixed, will create a PR

Feel free to weigh in to this or the PR (#2825) if you don't think it is worth the changes at this point.

This could potentially be considered done. @eunchan the rest are your discretion, and don't need to be fixed. LMK what you are thinking there.

I'm closing this as "sufficient" for this point. We can revisit if we get the _i/_o suffix style checker


Adding language option at the end of the command line

Hope this works, since I mostly try to document data in my spanish language

Thanks for the PR. I'd love it if you could update this to default to en when no language is specified. (Also, it's best to include the docs change in the same PR as the code change)

Was thinking on that too, like a default, but my perl skills are next to nothing!
Will try do! Cheers!


Add default actuator endpoints - Tasklist

add loggers,usage-metrics,backup
according to https://github.com/camunda/tasklist/blob/708913dee39d4506d46d251e68888d1f2cd12dc3/webapp/src/main/java/io/camunda/tasklist/Application.java#L121-L121
Which problem does the PR fix?

What's in this PR?

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[ ] There is no other open pull request for the same update/change.
[ ] The commits follow our Commit Guidelines.
[ ] Tests for charts are added (if needed).
[ ] The main Helm chart and sub-chart are updated (if needed).
[ ] In-repo documentation are updated (if needed).

After opening the PR:

[ ] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

@aleksander-dytko Thanks for the PR :+1:
Could you please update the golden files to make the tests pass?
make go.test-golden-updated

@aabouzaid could you please help me with that?
I run the command on the root folder and get:

@aleksander-dytko I'm not sure what the issue is here. It could be the Go version on your machine or so.
So I just made the changes.

Thanks @aabouzaid!


Asks to save files with no changes

If I open a document, look at it, and then close it, Brackets thinks there have been changes and wants to save them. I can always choose "don't save," but it's annoying.

Per our discussion on Slack, this issue was caused by https://github.com/brad-jones/whitespace (cc @brad-jones) and is now fixed.
Closing as extension problem (not extension idea, heh).


What is the equivalent of mustacheFileRoot in 3.0-M1?

version 3.0 do not use mustache as template any more, will use Handlebars instead.


Update flyway-core to 9.21.0

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.flywaydb", artifactId = "flyway-core" }
}]

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

Superseded by #210.


Prepare roadmap for Software Freedom Day

Let us commit to having something to show at Software Freedom Day. In order to do so, there has to be something tangible, no matter how small. And I would like us to be well prepared. So can we come up with a roadmap for this?
@Prince-linux please label "SFD" and "proposal".

Wow, seems we have a SFD team in place. Then let's go for it.

Somebody also talk to Mawutor. He needs to be added here, but I'm not sure he has been added to github yet.

this is his handle: stevdok (if he hasn't gotten a new one)

@stevdok Can you get involved here?


Autofit Resource Timelines by Default

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
When continuous resources are first rendered after simulation or placed into the timeline view, the data usually does not fit nicely into the Y-range of the plot (data is either squeezed into a small portion of the y-range or goes beyond y-range). To solve this problem, you can click "Fit". However, if you change your zoom or change a parameter and re-simulate, the data no longer fits and you have to click "Fit" again. This process can get cumbersome fairly quickly.
Describe the feature request
Introduce an "autofit" feature that fits the data into the y-range automatically based on the data in view. I personally think this should be the default selection, and if users want to specify a fixed y-range, they could disable autofit and pick their y-range of choice.

Confirming I saw this produce a lot of confusion during TT-6: Users assume their resource data had disappeared or not properly loaded because the scale exceeds what is visible on the default y-axis.
A slightly different but related observation: Users are trying to adjust the y-axis on a resource layer before data has populated (because the default values are not appropriate to their anticipated data range). The plan must be simulated in order for resource data to appear but because they can add the row, they are met with the default Y-range which feels nonsensical to them in the moment. Recommend not pre-populating fixed default Y values, and instead taking the Y values from the simulated resource.

One interesting quirk here is that because the bounds for a resource layer is part of the view, autofitting means that every time you run a sim you are likely to also change the view. Though perhaps a solution would involve not storing the bounds if we are autofitting for a layer (which will presumably be on by default)?


Refactored using clippy and rustfmt.

I cleaned up a bit by running clippy and rustfmt on the code. Clippy still warns about some lints that I have been unable to fix.

@fenhl Thanks for taking a look. Whilst I understand you have preferences on how Rust code should be styled, rustfmt is opinionated for a reason. I don't agree with all of the formatting changes either, but it's important that we have a strict and consistent code style in the Rust community.

@fenhl Hi, just going through some unmerged PRs. What should with do with this? You are welcome to close it if you are unhappy with these changes.
Thanks.

This should stay open until someone has the time to go through and apply the improvements only. Since this project is pretty dead, I don't expect this to happen any time soon.

I'm going to close this, as the project is inactive and it probably isn't worth the risk of breaking anything at this point. Thanks.


Version1_Iteration_Plan_Week2

This is the first proposal for the implementation of the class "key".

You do not have absolutely to create a new class Key that is almost equal to Button. As you said, you could create a new parent class and extends both Button and Key, but I do not recommend it. "Less is more", and you should reduce the number of classes as much as you can.
To K.I.S.S. (Keep It Simple and Stupid), I would suggest to promote Button as parent class (you can keep it as it is, without any modification) and define the new Key class as a child. Something like this:
class Key extends Button {
  Key(int x, int y, int w, int h, String t) {
    // call the Button constructor
    super(x,y,w,h,t);
  }

  void dinamicColorChange(color a1, color a2, color a3, color b1, color b2, color b3, color c1, color c2, color c3, int trasparency) {
    // stuff here ...
  }
}

It is true that I could define "Key" as a class child of "button", but the issue with this implementation, is that "Key" would have "buttonClicked" and "mouseInside" In it.  It would be more cleaner to create a class "Animal", and extend "Dog" and "Cat" from it.

OK, good point about buttonClicked and mouseInside.
A couple of other hints:

variables and methods names in a class should not mention the name of the class itself, to avoid inconsistencies when subclassing
it is a good practice (if it is not too obvious or redundant) define the name of methods with a verb (remember that a method is an action).

I would suggest renaming variables and function with something like this:
boxWidth, boxHeight   --> width, height
boxColor()  --> setColors()
dinamicColorChange()  --> changeDynamicColors()

Look at Processing reference for a good inspiration about naming.


Issue with speaker image in The MetalLB custom resource & address pool added but could not find the amended config ConfigMap used to configure MetalLB

Issue 1: Speaker image with tag main not working after deploying MetalLB custom resource:
apiVersion: metallb.io/v1beta1
kind: MetalLB
metadata:
  name: metallb
  namespace: metallb-system

when deployed with quay.io/metallb/speaker:main :
NAME                                                   READY   STATUS             RESTARTS         AGE
speaker-7g5jr                                          0/1     CrashLoopBackOff   16 (4m9s ago)    2d20h

--------------------------------------------------------------------------------------------------------------------------------------------

Events:
  Type     Reason   Age                   From     Message
  ----     ------   ----                  ----     -------
  Normal   Killing  51s                   kubelet  Container speaker definition changed, will be restarted
  Normal   Pulled   6s (x14 over 2d19h)   kubelet  Container image "quay.io/metallb/speaker:main" already present on machine
  Normal   Created  6s (x14 over 2d19h)   kubelet  Created container speaker
  Normal   Started  6s (x14 over 2d19h)   kubelet  Started container speaker
  Warning  BackOff  1s (x137 over 2d19h)  kubelet  Back-off restarting failed container

I had to edit the container image and redeploy each speaker pod because it created five replicas quay.io/metallb/speaker:v0.12.1. Here is the result:
NAME                                                   READY   STATUS    RESTARTS         AGE
speaker-7g5jr                                          1/1     Running   18 (5m55s ago)   2d20h

---------------------------------------------------------------------------------------------------------------------------------------

Events:

  Type     Reason   Age                    From     Message
  ----     ------   ----                   ----     -------
  Normal   Killing  20m                    kubelet  Container speaker definition changed, will be restarted
  Normal   Pulled   19m (x15 over 2d20h)   kubelet  Container image "quay.io/metallb/speaker:main" already present on machine
  Normal   Created  19m (x15 over 2d20h)   kubelet  Created container speaker
  Normal   Started  19m (x15 over 2d20h)   kubelet  Started container speaker
  Warning  BackOff  10m (x184 over 2d20h)  kubelet  Back-off restarting failed container

now it's displaying running, but events didn't change. And I feel it's not working.
Issue 2: Due to the fact that I don't know if MetalLB custom resource is working or not, I could not see the amended config ConfigMap used to configure MetalLB when address pool was added to test it out:
$ kubectl get cm -n metallb-system

NAME                         DATA   AGE
kube-root-ca.crt             1      2d20h
metallb.io.metallboperator   0      2d20h

Hi @adeniyistephen , sorry for the delay.
Can you tell us the exact steps you are doing to deploy metallb?
Also, please note that when using main, the configmap is not rendered anymore because metallb handles the crds itself.

Hi @fedepaol sorry for the late reply as well.
I deployed metallb-operator using the readme guide here: https://github.com/metallb/metallb-operator following the Quick Start to deploy the operator.
I also found out that I could use OLM to deploy metalLB, but I and my team later moved to just using the metallb manifest. I even had issues updating the pod from v0.12.1 to v0.13.3, I opened an issue already.

also, what you mean by "updating the pod"? How did you run the upgrade?

my bad, I was meant to say image, and yes it's from the main branch. do you have any other public commit brach?

You should use the manifests as a whole (and not changing teh version only) because the parameters may change. So what you are doing now is running a random version's parameter with the image of 0.13.3
I'd recommend consuming the manifests from here https://github.com/metallb/metallb-operator/tree/v0.13.3 after deleting what you currently have.

sure, sounds like a legit answer, do you mean this manifest: https://github.com/metallb/metallb-operator/blob/v0.13.3/bin/metallb-operator.yaml

I was using this, and then changed the image version for controller and speaker: https://github.com/metallb/metallb/blob/v0.12.1/manifests/metallb.yaml
I would be using native, I'm sorry, but I didn't see the quay.io image for controller and speaker here: https://github.com/metallb/metallb/tree/main/config/manifests Thanks

I was using this, and then changed the image version for controller and speaker: https://github.com/metallb/metallb/blob/v0.12.1/manifests/metallb.yaml

The issue is, together with the images, the set of parameters we pass to the entry points changed, so changing just the image may result in issues.

I would be using native, I'm sorry, but I didn't see the quay.io image for controller and speaker here: https://github.com/metallb/metallb/tree/main/config/manifests Thanks

Here https://github.com/metallb/metallb/blob/main/config/manifests/metallb-native.yaml#L1579 for example (or even better, the tagged counterpart https://github.com/metallb/metallb/blob/v0.13.3/config/manifests/metallb-native.yaml )

oh, sounds good. the main is now the v0.13.3. I would reconfigure how I'm using the manifest and get back to you... to see if we could close the issue, Thanks.

oh, sounds good. the main is now the v0.13.3. I would reconfigure how I'm using the manifest and get back to you... to see if we could close the issue, Thanks.

Please consume https://github.com/metallb/metallb/blob/v0.13.3/config/manifests/metallb-native.yaml so you are sure you won't be affected by changes on the main tag

sure, that's what I will do... you have given me an example to follow.

correct.

@fedepaol to be clear, no more config maps but IPAddressPool is now available, correct?  So CRDs even without operator? That's good news actually! I saw CRDs in the manifest.

Correct!

Please just look at the docs and the configuration examples on the metallb repository here https://github.com/metallb/metallb/tree/main/configsamples. That is a template and not a full crd.
I am going to close this issue as it looks like the upgrade process wasn't followed correctly (https://github.com/metallb/metallb-operator/issues/215#issuecomment-1184396309).
If you need help in understanding how to configure metallb, please come to the # metallb slack channel on the k8s slack so other users will be able to help you, and try to go through the doc / the examples.


[feat]: split model support partition variables

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


adding coqPackages.ssprove

Description of changes
This adds the Coq module SSProve.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Great! Would you please update the other PR: https://github.com/coq-community/coq-nix-toolbox/pull/213

Definitely, but it takes a while to regenerate the files in the coq-nix-toolbox.

Done.

Thanks a lot!

Thanks a lot for your help on this PR, @vbgl!


NETOBSERV-204 source or destination match

This PR add a query option to match all Source OR Destination fields
http://localhost:3100/loki/api/v1/query_range?query={app="netobserv-flowcollector"}|json|(DstNamespace=~".*open.*"+and+DstPod=~`.*api.*`)+or+(SrcNamespace=~".*open.*"+and+SrcPod=~`prom.*`)&start=1645797646&limit=100

I suggest to release that as is to unlock https://github.com/netobserv/network-observability-console-plugin/pull/81 and add an extra custom match filter in the future to unlock custom grouping.
We can imagine custom grouping using drag and drop on UI side and match argument sent to the backend containing group infos (fields, criteria between each value of group / between each group)
Or wait for PF query builder https://github.com/patternfly/patternfly-design/issues/972

My initial thinking about this task was more to have new filters like "Pods" in the filters list, and that would match both for src and dest pods. So in terms of display you wouldn't this large box showing Source and Destination, you would just have the usual key-value "Pod: foo", and the underlying business logic of the filters would be hidden. WDYT?

My initial thinking about this task was more to have new filters like "Pods" in the filters list, and that would match both for src and dest pods. So in terms of display you wouldn't have this large box showing Source and Destination and complex filters, you would just have the usual key-value "Pod: foo", and the underlying business logic of the filters would be hidden. WDYT?

So this "Pods" filter would also be available as a column or just in the filters ?
How do you add "Namespaces" to the equation to avoid a match with a source pod name and destination namespace ?

/hold

To me, the main use case we want to solve is to filter for a given pod / namespace  (or whatever kube object), regardless it's source or destination. Is there another use case you wanted to address?

So this "Pods" filter would also be available as a column or just in the filters ?
It should be only a filter (in my initial vision at least)

How do you add "Namespaces" to the equation (SrcPod AND SrcNamespace) OR (DstPod AND DstNamespace) to avoid a match with a source pod and destination namespace ?

OK I get your point. I thought at first that we wanted something like (SrcPod=X OR DstPod=X) AND (SrcNamespace=Y OR DstNamespace=Y), but it catches too large (e.g. it catches the situation where a flow is: srcpod=X, srcns=other, dstpod=other, dstns=Y, which shouldn't be a match for pod=X, ns=Y)
So we want somehow, in the "match all" situation, end up with this:
(SrcPod=X AND SrcNamespace=Y) OR (DstPod=X AND DstNamespace=Y) instead of (SrcPod=X OR DstPod=X) AND (SrcNamespace=Y OR DstNamespace=Y) .. is that right, is that your point?

So we want somehow, in the "match all" situation, end up with this: (SrcPod=X AND SrcNamespace=Y) OR (DstPod=X AND DstNamespace=Y)

Let's imagine we want to build a more complex query with more filters, in "match all" mode, eg. with Workload (src+dest) and Port (only dst). The resulting query must be:
(SrcPod=X AND SrcNamespace=Y AND SrcWorkload=Z AND DstPort=999) OR (DstPod=X AND DstNamespace=Y AND DstWorkload=Z AND DstPort=999)
Sounds correct or not? I think it is...
So, to extract the rule from there, looks like when a "Src+Dst" filter is in the game, we can run 2 queries: first with all "Src+Dst" fields on "Src", + the non-"Src+Dst" filters, all ANDed; then all "Src+Dst" fields on "Dst", + the non-"Src+Dst" filters, all ANDed
This is maybe not super clear (and must be challenged), we can have a call if you want

Following our slack discussion, let's consider both way and test them.

(SrcPod=X AND SrcNamespace=Y AND SrcWorkload=Z AND DstPort=999) OR (DstPod=X AND DstNamespace=Y AND DstWorkload=Z AND DstPort=999) Sounds correct or not? I think it is...

That's currently working in this PR

If you feel groups takes too much room we can remove titles:

and optimize using show more / show less buttons if there is too many fields.
Let's try the super-columns source/destination way in parallel
Thanks for your feedback :+1:


🐛 BUG: creating project from template fails with EXDEV: cross-device link not permitted

Which Cloudflare product(s) does this pertain to?
C3
What version(s) of the tool(s) are you using?
3.3.0
What version of Node are you using?
18.16.1
What operating system are you using?
Linux (Fedora 38)
Describe the Bug
Going through the documentation located here I executed the following command:

npm create cloudflare@1 test worker-d1-api

which triggered: Error: EXDEV: cross-device link not permitted
You can find a test case triggering this error message here: https://github.com/cloudflare/workers-sdk/blob/f7ae0ead2a48453845fcdbe3366b2db63d93b008/packages/wrangler/src/tests/generate.test.ts#L229
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
npm create cloudflare@1 cf-d1-api worker-d1-api                                                             (code) 01:12:01
Error: EXDEV: cross-device link not permitted, rename '/tmp/880f3e5237c9b-3d1e918115827/worker-d1-api' -> '/home/mxschumacher/code/cf-d1-api'
npm ERR! code 1
npm ERR! path /home/mxschumacher/code
npm ERR! command failed
npm ERR! command sh -c create-cloudflare cf-d1-api worker-d1-api
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/mxschumacher/.npm/_logs/2023-07-19T23_12_25_510Z-debug-0.log

Hello @mxschumacher 👋  Thank you for filing this issue. I'm not able to replicate this on my machine so I assume it may be a Linux/create-cloudflare v1 issue. While the latest C3 does not support arbitrary templates like v1, you can perform the same action with npx wrangler generate cf-d1-api worker-d1-api. I'm going to close this as we do not currently support create-cloudflare v1 and will not fix issues related to it.


Visibility for NetworkClient.handlers and NetworkServer.handlers breaks NobleConnect compatability

In Version 9.0.2 (and newer) of Mirror (AssetStore Release) the NetworkClient.handlers and NetworkServer.handlers variables aren't public anymore, this breaks compatibility with the NobleConnect-Plugin, because they use the variable in their code.
Steps to Reproduce: Import Version 9.0.2 of Mirror then import Noble Connect Free from the Unity Asset Store (Version 1.10). You will get compiler errors right away, because it can't find the variables.
Fix: Can be fixed by making NetworkClient.handlers and NetworkServer.handlers public again.

what does noble connect need them for?
the registerhandler and clearhandler functions are still there

You are right, they are accessing the handlers variables directly to register new handlers, which should be done with RegisterHandler... So it's on their side,
Sorry, and thanks!


CAMEL-11791: Enhanced reconnection for rabbitmq consumer and producer…

… (including queue/exchange deletion)

Thanks for the PR it has been merged. Do you mind closing this?


ER_LOCK_DEADLOCK when multiple clients access the server

(@nclaidiere I'm moving this from open-cogsci/omm-client#16, because I'm fairly sure this is a server-side issue.)
On a regular basis the experiment stops with the following error message:
item-stack: omm_loop[run].omm_sequence[run].announce[run].experiment[run].trial_sequence[run].logger[run]
time: Mon Apr 11 18:59:13 2022
exception type: FailedToSendJobResults
exception message: {"message":"updateparticipationssetstatus_id= 2, updated_at= '2022-04-11 16:58:19' wherestudy_id= 17 andparticipant_id= 29 - Deadlock found when trying to get lock; try restarting transaction","name":"Error","code":"ER_LOCK_DEADLOCK","status":500}

This does not depend on the experiment, the ID or the box (I have attached a file with a few of these messages on github). It happens mostly when it’s busy, is it a conflict when two trials from the same individual are started? We had one experiment that did not use the new file system and this didn’t show up.
 Will look into this.

What endpoint are you calling here. Is it PATCH /participants/:identifier/:job_id/result?

I think I found the cause for the deadlock. It is caused by the section https://github.com/open-cogsci/omm-server/blob/develop/app/Models/Study.js#L362-L374
After every trial, the status of the study is checked and either set to 'in progress' or finished. The problem is that the status is even changed to 'in progress' when the study already has that status, which is an unnecessary write operation of course, and the write operations lock the record. My guess is that when 2 participants complete a trial for the same study, the deadlock can occur (but that's a very in short time window all things considered... wow). I think the fix is simple. I've added a condition to the query that only records should be updated that don't already have the current status:
await this.participants()
        .pivotQuery()
        .where('participant_id', ptcpID)
        .whereNot('status_id', statusID) // <-- new line
        .update({ status_id: statusID })

This should prevent the study record to be locked by two simultaneous queries, as the record no longer gets locked for updating if it already has the desired status. I do have difficulties reproducing the deadlock locally (even with an automated test), so I have no idea if this will really fix the issue. Would it be easy to check for you if it still occurs?

Hi Daniel, great! we can test it soon, probably next week. Do I just need to update the server?

Yes! I also did a quick release so you can also just use the docker image by updating it with docker-compose pull

Excellent, thanks!

Hi, the deadlock issue is back. I changed the experiment for something much quicker, choosing between 2 stims, and got the error back. But I don't think I have the last update.

Yes, I think you need version 0.7.4 where this should be fixed

Ok great, I'll let you know how this goes.
Le jeu. 19 mai 2022, 08:43, Daniel Schreij @.***> a
écrit :

Yes! I also did a quick release so you can also just use the docker image
by updating it with docker-compose pull
—
Reply to this email directly, view it on GitHub
https://github.com/open-cogsci/omm-server/issues/123#issuecomment-1131292731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMELDDATRUTO2ZOQLPMXFL3VKXPKDANCNFSM5TQCAFWA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Respect searchpath

fixes directus/next#842
this is basically untested, as I don't know how to test this, however I tested individual changes by editing node_modules stuff in my directus env...

https://github.com/MiniDigger/knex-schema-inspector/blob/respect-searchpath/lib/dialects/postgres.ts#L286 and https://github.com/MiniDigger/knex-schema-inspector/blob/respect-searchpath/lib/dialects/postgres.ts#L312 need to be changed to, to be able to deal with search paths with more than 1 entry, ill think about the query for that in a bit


Create a schema for editors when modifying the config YAML

This would be useful for auto-completion, valid options, etc.

I generated a JSON schema from our Zod schema using https://github.com/StefanTerdell/zod-to-json-schema
myschema.json
Then added a comment at the top of a config yaml file:
# yaml-language-server: $schema=myschema.json

Which gave me autocomplete, and warnings about missing mandatory fields!

See https://github.com/redhat-developer/yaml-language-server?tab=readme-ov-file#using-inlined-schema

This helps avoid errors, since the schema can point out invalid attributes.

Of course, @abukharov wants to be able to add random stuff to the YAML - so maybe there needs to be an option for that (or ignore the warnings)


:seedling: Revert "enable leader election of klusterlet-agent on single node man…

…aged clusters (#695)"
This reverts commit 8544ff1e2999ad774193186945aaa58938f56278.

Summary
In practice, we found the commit affect on some concern cases, revert the PR util we confirm the effect.

could you explain what cases is impacted? so that we can add tests in the future.

could you explain what cases is impacted? so that we can add tests in the future.

We have some e2e cases that detach and cleanup klusterlet resources many times. From my test, when using the latest images, there are about 3-6 cases often fail.

/approve
/lgtm


fix: error with missing assemblies

During first import,  the weaver will be called before all assemblies
are built.  No need to look for custom readers and writers if the assemblies
are not built.
fixes #1051

:tada: This PR is included in version 3.17.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: implement and test make install rules

Fixes #20 and fixes #18

I never did figure out how to run these locally, but I sort of can run the steps manually in a docker container sometimes.


why  the transformers vicuna-7b-v1.1 results is different from vllm vicuna-7b-v1.1 results,   How to solve it，thanks

transformers vicuna-7b-v1.1 script:
from transformers import AutoTokenizer, AutoModelForCausalLM

tokenizer = AutoTokenizer.from_pretrained("lmsys/vicuna-7b-v1.1")
model = AutoModelForCausalLM.from_pretrained("lmsys/vicuna-7b-v1.1").to(0)

import time
prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]

for prompt in prompts:
    inputs = tokenizer(prompt, return_tensors="pt").to(0)
    generate_ids = model.generate(inputs.input_ids, max_length=256)
    result = tokenizer.batch_decode(generate_ids, skip_special_tokens=True, clean_up_tokenization_spaces=False)[0]
    print(result)

the results is:
Hello, my name is Dr. David C. Preston, and I am a chiropractor serving the residents of the greater Phoenix area. I have been in practice for over 20 years, and I am dedicated to helping my patients achieve optimal health and wellness through natural, non-invasive chiropractic care.
At my practice, I offer a wide range of chiropractic services, including adjustments, massage therapy, and rehabilitation. I also offer nutritional counseling and weight loss coaching to help my patients achieve their health goals.
I believe that every person deserves to live a healthy, happy life, and I am committed to helping my patients achieve this through chiropractic care. If you are looking for a chiropractor who will take the time to understand your unique needs and provide personalized care, I would be honored to help.
Please feel free to contact my office to schedule an appointment or to learn more about the services I offer. I look forward to helping you achieve optimal health and wellness.

 He is a man who has been accused of rape by at least one woman, and who has been accused of paying hush money to cover up his sexual misconduct. He is a man who has been accused of sexual harassment by at least one woman, and who has been accused of using his position of power to force himself on women.  He is a man who has been accused of sexual assault by multiple women, and who has been accused of using his position of power to force himself on women. He is a man who has been accused of sexual misconduct by multiple women, and who has been accused of using his position of power to force himself on women. He is a man who has been accused of sexual misconduct by multiple women, and who has been accused of using his position of power to force himself on women. He is a man who has been accused of sexual misconduct by multiple women, and

The capital of France is Paris.
The currency of France is the Euro.
The official language of France is French.
The population of France is approximately 67 million people.
The flag of France is a tricolor flag with three horizontal bands of blue, white, and red.
The national symbol of France is the Gallic rooster.
The national sport of France is football (soccer).
The national animal of France is the Greyhound.
The national flower of France is the Rose.
The national tree of France is the Oak tree.
The national bird of France is the Hoopoe.
The national monument of France is the Eiffel Tower.
The national dish of France is Coq au Vin.
The national drink of France is wine.
The national holiday of France is Bastille Day, which is celebrated on July 14th.
The national anthem of France is "La Marseillaise".
The highest mountain in France is Mont Blanc.
The largest city in France is Paris.
The smallest country in the world is Vatican City, which is located within Rome, Italy.
The largest island in the world is Greenland.

The future of AI is bright, and it’s up to us to ensure that it benefits everyone. As we continue to develop and deploy AI technologies, we must prioritize ethical considerations and work to mitigate potential negative impacts. By doing so, we can create a future where AI is a force for good, driving progress and improving lives around the world.

vllm vicuna-7b-v1.1 script:
from vllm import LLM, SamplingParams
prompts = [
    "Hello, my name is",
    "The president of the United States is",
    "The capital of France is",
    "The future of AI is",
]

sampling_params = SamplingParams(max_tokens=256)

# Create an LLM.
llm = LLM(model="lmsys/vicuna-7b-v1.1")
outputs = llm.generate(prompts, sampling_params)
# Print the outputs.
for output in outputs:
    prompt = output.prompt
    generated_text = output.outputs[0].text
    print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")

the results is:
Prompt: 'The future of AI is', Generated text: 'here, and it’s called “Generative AI”. In this podcast, we introduce you to the key players in the industry and what makes Generative AI so special:</s>'

Prompt: 'The president of the United States is', Generated text: 'the leader of the free world, responsible for guiding the nation and its policies. In the past, no other occupation of an American president has been confirmed from flying a plane to being the mayor of a small town. However, being president of the United States is an important job requirement. It requires an individual who is willing to take on the challenges of office and lead the country through both good times and bad.</s>'

Prompt: 'Hello, my name is', Generated text: "D'Arcy, and I' Yeah, I know, it's a bit of a mouthful. My parents had high hopes for me, and then they met my sister. Anyway, I've been doing this stand-up comedy thing for a couple of years now, and I've been lucky enough to perform all over Scotland.  I hope you enjoy it!</s>"

Prompt: 'The capital of France is', Generated text: 'Paris, which is actually split into two main districts. The first is the City of Paris, which is the most central part of the city, and it is home to iconic landmarks such as the Eiffel Tower, the Louvre Museum, Notre Dame Cathedral, and the Pompidou Center. The second is La banlieue, which refers to the outer suburbs of Paris. This mainly residential area covers around 1,500 square kilometers, and it is home to around four million people. Many of La banlieue residents are immigrants or children of immigrants, who have moved to Paris looking for work or a better life. While the suburbs are considered somewhat isolated from the rest of France, they have a rich culture of their own, with many unique neighborhoods and a diverse mix of people.\n\nImportant landmarks in La banlieue include various sports stadiums, such as the Stade de France, the largest stadium in France, which is located in Saint-Denis, and the Parc des Princes stadium, which is home to the Paris Saint-Germain football club. There are also several theme parks in La banlieue, such'

The (default sampling parameters)[https://github.com/vllm-project/vllm/blob/main/vllm/sampling_params.py] for vllm and the (default generation parameters)[https://huggingface.co/docs/transformers/v4.30.0/en/main_classes/text_generation#transformers.GenerationMixin.generate] for huggingface seem to differ. For one, huggingface uses greedy decoding by default while vllm uses sampling. Does vllm still differ when set to greedy decoding?

Close this issue since it seems like to be the incorrect setting of sampling parameters. Feel free to reopen the issue if you meet any further problems!


Upload js and css to cdn after building the image.

Requires .ssh key configured and present in the current working
directory. This won't be checked in for security purposes.

lgtm


runtime test fails on Linux/arm

I built Go 1.5.3 from source on Linux/Arm (Raspberry Pi 2, Debian Jessie). All tests pass except one, both when run through all.bash and when run standalone after installation. Below is the standalone result.
I thought this might be in the same vein as #11959, which was fixed, but oddly enough I can't find the referenced commit that purportedly fixed it in the commit history of the go1.5.3 tag.
$ TMPDIR=$HOME/Tmp go test runtime
SIGQUIT: quit
PC=0x744cc m=0

goroutine 0 [idle]:
runtime.futex(0x30c168, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1f1c8, 0x0, 0x0, 0x0, ...)
	/usr/local/go/src/runtime/sys_linux_arm.s:246 +0x1c
runtime.futexsleep(0x30c168, 0x0, 0xffffffff, 0xffffffff)
	/usr/local/go/src/runtime/os1_linux.go:39 +0x68
runtime.notesleep(0x30c168)
	/usr/local/go/src/runtime/lock_futex.go:142 +0xa4
runtime.stoplockedm()
	/usr/local/go/src/runtime/proc1.go:1276 +0xa0
runtime.schedule()
	/usr/local/go/src/runtime/proc1.go:1598 +0x58
runtime.park_m(0x105000e0)
	/usr/local/go/src/runtime/proc1.go:1706 +0x16c
runtime.mcall(0x30bf00)
	/usr/local/go/src/runtime/asm_arm.s:178 +0x5c

goroutine 1 [chan receive, 2 minutes, locked to thread]:
runtime.gopark(0x26275c, 0x10512170, 0x221828, 0xc, 0x17, 0x3)
	/usr/local/go/src/runtime/proc.go:185 +0x148 fp=0x10543d70 sp=0x10543d5c
runtime.goparkunlock(0x10512170, 0x221828, 0xc, 0x17, 0x3)
	/usr/local/go/src/runtime/proc.go:191 +0x44 fp=0x10543d8c sp=0x10543d70
runtime.chanrecv(0x1b6c70, 0x10512140, 0x10543eac, 0x10543e01, 0x90000)
	/usr/local/go/src/runtime/chan.go:448 +0x4b8 fp=0x10543df8 sp=0x10543d8c
runtime.chanrecv1(0x1b6c70, 0x10512140, 0x10543eac)
	/usr/local/go/src/runtime/chan.go:349 +0x28 fp=0x10543e10 sp=0x10543df8
testing.RunTests(0x262538, 0x30a110, 0xa2, 0xa2, 0x1)
	/usr/local/go/src/testing/testing.go:562 +0x618 fp=0x10543ee0 sp=0x10543e10
testing.(*M).Run(0x10543f7c, 0x125e0)
	/usr/local/go/src/testing/testing.go:494 +0x6c fp=0x10543f28 sp=0x10543ee0
main.main()
	runtime/_test/_testmain.go:954 +0x118 fp=0x10543fa4 sp=0x10543f28
runtime.main()
	/usr/local/go/src/runtime/proc.go:111 +0x2b4 fp=0x10543fcc sp=0x10543fa4
runtime.goexit()
	/usr/local/go/src/runtime/asm_arm.s:1036 +0x4 fp=0x10543fcc sp=0x10543fcc

goroutine 20213232 [running]:
	goroutine running on other thread; stack unavailable
created by testing.RunTests
	/usr/local/go/src/testing/testing.go:561 +0x5ec

goroutine 20213203 [running]:
	goroutine running on other thread; stack unavailable
created by runtime_test.TestPrintGC
	/usr/local/go/src/runtime/gc_test.go:408 +0x16c

trap    0x6
error   0x0
oldmask 0x0
r0      0x30c168
r1      0x0
r2      0x0
r3      0x0
r4      0x0
r5      0x0
r6      0x10520a00
r7      0xf0
r8      0x30c0c8
r9      0x0
r10     0x30bee0
fp      0x30bdb4
ip      0x10e311b9
sp      0x7e92a5a4
lr      0x3af30
pc      0x744cc
cpsr    0xa0000010
fault   0x0
*** Test killed with quit: ran too long (10m0s).
FAIL	runtime	600.018s

/all.bash runs go test runtime -short, it is likely that the full tests suite will not pass on the rpi in under 10 minutes.
Please consult, http://dave.cheney.net/2015/09/04/building-go-1-5-on-the-raspberry-pi. I'm going to close this now, please reopen it if you have further questions, or feel free to take this to the golang-nuts mailing list.

I had missed that blog post. Indeed with the following the test does succeed:
$ ulimit -s 1024
$ go test runtime -short
ok  	runtime	158.323s

If I leave off the -short but set GO_TEST_TIMEOUT_SCALE=10 as per your post, it still gets killed after 600 seconds.
I added a tip to the GoArm wiki page, and also added a link to your blog post under the RPi 2 section (which is where I scrolled to, going right past the RPi section which does link to your post).


metagenomic binning service doesn't work

I am attempting to launch a binning job from a set of single-end reads.  The reads are located in the public workspace under PATRIC_Workshop/Metagenomic_Binning/ICU
Why can't I submit with single end reads?  Is this the problem?  I thought this did the assembly for me, is it asking for contigs?

As discussed in Skype channel, the backend currently does not support single end reads.


Purchasing flight DL 106 on 2024-12-06 fails

url for quote check
{"level":"debug","message":"proxy request ==> GET https://api.flightstats.com/flex/schedules/rest/v1/json/flight/DL/106/departing/2024/12/06?xxx","reqId":"x4nTA_vFii7FGPStrCEgF","timestamp":"2024-11-28 08:16:10"}

url for purchase data validation
https://api.flightstats.com/flex/schedules/rest/v1/json/flight/DL/106/departing/2024/12/07?appId=483244b1&appKey=078d253494c896ea92f2c6e37331c6dc

different dates!!

looks like some time conversion is off. 19:50 local time us is on the next day when using utc.


HBASE-28512 Update error prone to 2.26.1

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 58s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 31s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 48s
branch-2 passed

+1 :green_heart:
compile
9m 17s
branch-2 passed

+1 :green_heart:
checkstyle
1m 33s
branch-2 passed

+1 :green_heart:
spotless
1m  9s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
16m 45s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 59s
the patch passed

+1 :green_heart:
compile
9m 40s
the patch passed

-0 :warning:
javac
9m 40s
root generated 330 new + 912 unchanged - 159 fixed = 1242 total (was 1071)

+1 :green_heart:
checkstyle
1m 55s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
15m  3s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

-1 :x:
spotless
1m  6s
patch has 1 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
17m  7s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 51s
The patch does not generate ASF License warnings.

88m 18s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile xml

uname
Linux 252d077c485b 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Eclipse Adoptium-11.0.17+8

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5844/1/artifact/yetus-general-check/output/diff-compile-javac-root.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5844/1/artifact/yetus-general-check/output/patch-spotless.txt

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 49s
branch-2 passed

+1 :green_heart:
compile
1m 59s
branch-2 passed

+1 :green_heart:
shadedjars
5m 30s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m  7s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 43s
the patch passed

+1 :green_heart:
compile
2m  0s
the patch passed

+1 :green_heart:
javac
2m  0s
the patch passed

+1 :green_heart:
shadedjars
5m 23s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m  6s
the patch passed

_ Other Tests _

-1 :x:
unit
288m 12s
root in the patch failed.

322m 57s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 63eaa3f09350 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5844/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

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

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 29s
branch-2 passed

+1 :green_heart:
compile
1m 39s
branch-2 passed

+1 :green_heart:
shadedjars
4m 46s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 26s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 17s
the patch passed

+1 :green_heart:
compile
1m 43s
the patch passed

+1 :green_heart:
javac
1m 43s
the patch passed

+1 :green_heart:
shadedjars
4m 43s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 28s
the patch passed

_ Other Tests _

-1 :x:
unit
326m 38s
root in the patch failed.

356m 18s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1a729429bca3 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5844/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

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

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 48s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 59s
branch-2 passed

+1 :green_heart:
compile
5m 21s
branch-2 passed

+1 :green_heart:
checkstyle
1m 11s
branch-2 passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
10m 34s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 48s
the patch passed

+1 :green_heart:
compile
5m 28s
the patch passed

-0 :warning:
javac
5m 28s
root generated 330 new + 912 unchanged - 159 fixed = 1242 total (was 1071)

+1 :green_heart:
checkstyle
1m  7s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
9m 28s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
0m 45s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
11m  4s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

55m 54s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile xml

uname
Linux 7f6025b27b64 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Eclipse Adoptium-11.0.17+8

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5844/2/artifact/yetus-general-check/output/diff-compile-javac-root.txt

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  6s
branch-2 passed

+1 :green_heart:
compile
1m 55s
branch-2 passed

+1 :green_heart:
shadedjars
5m 47s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 54s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 47s
the patch passed

+1 :green_heart:
compile
1m 55s
the patch passed

+1 :green_heart:
javac
1m 55s
the patch passed

+1 :green_heart:
shadedjars
5m 47s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
277m 10s
root in the patch passed.

312m 39s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Eclipse Adoptium-11.0.17+8

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

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 42s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 24s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 38s
branch-2 passed

+1 :green_heart:
compile
1m 35s
branch-2 passed

+1 :green_heart:
shadedjars
5m 12s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 21s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 13s
the patch passed

+1 :green_heart:
compile
1m 31s
the patch passed

+1 :green_heart:
javac
1m 31s
the patch passed

+1 :green_heart:
shadedjars
5m  9s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 16s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
399m 50s
root in the patch passed.

429m 55s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 16baa8aa3d

Default Java
Temurin-1.8.0_352-b08

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

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

modules
C: hbase-http hbase-server hbase-thrift . U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


Added some additional, automated secrets maskers

@mjroghelia @damccorm do you see any issues with this?

@damccorm yeah if anything here becomes problematic for us, we have a few levers to pull:

an individual customer can disable with AZP_USE_CREDSCAN_REGEXES=false as an env var (the HostContext can't use runtime variables as knob sources for some reason)
we can update the "exclude patterns by name" list in CredScanPatternExtractor.cs
and of course, we can always ask the CredScan folks for a fix


OpenAppend - You cannot modify the position of a FtpDataStream.

Same problem with FileZilla. FluentFTP version 33.1.6.
I'm taking my code from this example
                using (Stream ostream = conn.OpenAppend("/full/or/relative/path/to/file")) {                     try {                         ostream.Position = ostream.Length;                         var sr = new StreamWriter(ostream);                         sr.WriteLine(...);                     }                     finally {                         ostream.Close();                     }                 }
given here https://github.com/robinrodricks/FluentFTP/issues/52
System.InvalidOperationException
HResult=0x80131509
Message=You cannot modify the position of a FtpDataStream. This property is updated as data is read or written to the stream.
Source=FluentFTP
StackTrace:
at FluentFTP.FtpDataStream.set_Position(Int64 value)
at VWUK.Utils.FtpService.FtpService.AppendMode(FtpClient ftp, String path, String data) in
Originally posted by @hrafnkel in https://github.com/robinrodricks/FluentFTP/issues/283#issuecomment-823149168

Please use the new append API - UploadFile(.... FtpExists.Append) - if it does not work, tell me and I'll document it better

I have tried UploadFile with Append. Creation works fine, but it does not append to a pre-existing file.
`        private FtpStatus AppendMode(FtpClient ftp, string path, string data)
{
ftp.UploadDataType = FtpDataType.ASCII;
        // make a local temp file
        string fileName = "tempFile";
        File.AppendAllText(fileName, data);

        // upload file
        FtpStatus status = ftp.UploadFile(fileName,path,FtpRemoteExists.Append, false);

        // delete temp file
        File.Delete(fileName);

        return status;
    }`

Additional. The debug log
Fred: Debug: >         Connect() Fred: Information: Status:   Connecting to fd1a:d1b0:320a:7777::a02:15f:21 Fred: Debug: Response: 220-FileZilla Server 0.9.60 beta Response: 220-written by Tim Kosse<EMAIL_ADDRESS>Fred: Information: Response: 220 Please visit https://filezilla-project.org/ Fred: Information: Status:   Detected FTP server: FileZilla Fred: Information: Command:  AUTH TLS Fred: Information: Response: 234 Using authentication type TLS Fred: Information: Status:   FTPS Authentication Successful Fred: Debug: Status:   Time to activate encryption: 0h 0m 0s.  Total Seconds: 0.1159128. Fred: Information: Command:  USER sabalmsftp Fred: Information: Response: 331 Password required for sabalmsftp Fred: Information: Command:  PASS *** Fred: Information: Response: 230 Logged on Fred: Information: Command:  PBSZ 0 Fred: Information: Response: 200 PBSZ=0 Fred: Information: Command:  PROT P Fred: Information: Response: 200 Protection level set to P Fred: Information: Command:  FEAT Fred: Debug: Response: 211-Features: Response: MDTM Response: REST STREAM Response: SIZE Response: MLST type*;size*;modify*; Response: MLSD Response: AUTH SSL Response: AUTH TLS Response: PROT Response: PBSZ Response: UTF8 Response: CLNT Response: MFMT Response: EPSV Response: EPRT Fred: Information: Response: 211 End Fred: Information: Status:   Text encoding: System.Text.UTF8Encoding+UTF8EncodingSealed Fred: Information: Command:  OPTS UTF8 ON Fred: Information: Response: 202 UTF8 mode is always enabled. No need to send this command. Fred: Information: Command:  SYST Fred: Information: Response: 215 UNIX emulated by FileZilla Fred: Debug: >         GetFileSize("/FTPTestHarness.csv") Fred: Information: Command:  SIZE /FTPTestHarness.csv Fred: Information: Response: 213 366 Fred: Debug: >         FileExists("/FTPTestHarness.csv") Fred: Information: Command:  SIZE /FTPTestHarness.csv Fred: Information: Response: 213 366 Fred: Information: Creating new file Fred: Debug: >         UploadFile("tempFile", "/FTPTestHarness.csv", Append, False, None) Fred: Debug: >         FileExists("/FTPTestHarness.csv") Fred: Information: Command:  SIZE /FTPTestHarness.csv Fred: Information: Response: 213 366 Fred: Debug: >         GetFileSize("/FTPTestHarness.csv") Fred: Information: Command:  SIZE /FTPTestHarness.csv Fred: Information: Response: 213 366 Fred: Debug: >         OpenAppend("/FTPTestHarness.csv", ASCII) Fred: Information: Command:  TYPE A Fred: Information: Response: 200 Type set to A Fred: Debug: >         OpenPassiveDataStream(EPSV, "APPE /FTPTestHarness.csv", 0) Fred: Information: Command:  EPSV Fred: Information: Response: 229 Entering Extended Passive Mode (|||65261|) Fred: Information: Status:   Connecting to fd1a:d1b0:320a:7777::a02:15f:65261 Fred: Information: Command:  APPE /FTPTestHarness.csv Fred: Information: Response: 150 Opening data channel for file upload to server of "/FTPTestHarness.csv", restarting at offset 366 Fred: Information: Status:   FTPS Authentication Successful Fred: Debug: Status:   Time to activate encryption: 0h 0m 0s.  Total Seconds: 0.071649. Fred: Debug: Status:   Disposing FtpSocketStream... Fred: Information: Response: 226 Successfully transferred "/FTPTestHarness.csv"

I'm having the same problem

I think everone has seen this by now - it will be mentioned in the FAQ section at some point in time,


"Attributes shorthand" in v-for cycles

What problem does this feature solve?
Vue is famous for its highly readable syntax and this can make it even more readable.
What does the proposed API look like?
Instead of writing duplicities in v-for cycles like this:
<elm
v-for="({ value, class, 'data-image' }, key) in elmprops"
:value="value"
:class="class"
:data-image="data-image"
:key="key"
/>
Would by nice to have "attributes shorthand" like this:
<elm
v-for="({ value, class, 'data-image' }, key) in elmprops"
:value
:class
:data-image
:key
/>
Like the object properties shorthand works in ES:
let routes = []
let router = { routes }
instead of unnecessary duplicities in older syntax:
let routes = []
let router = { routes: routes }

https://github.com/vuejs/vue/pull/2877

https://github.com/vuejs/vue/pull/2877


[HxSidebar] Custom collapsible item?

Hello,
I'm trying to figure out how in your documentation the theme dropdown disappears and only the github icon shows.
Before sidebar collapse

After sidebar collapse

I think I'm going to figure it out from CSS profiling...but it would be very cool if the documentation directly mentioned how to do it.
It would also be cool if there was a support for razor syntax distinguishing uncollapsed and collapsed sidebar item:
<HxSidebarItem>
   <Uncollapsed>
      some html
   <Uncollapsed>
   <Collapsed>
      some html
   </Collapsed>
</HxSidebarItem>

Hi @czmirek the HxSidebar has a collapsed class so hiding the theme input depends on it in custom styles of the docs page (display: none).
We know that there is some debt in the Collapsed/Uncollapsed API of HxSidebar, specifically in its footer and it will be subject of a further development.
There are multiple open issues related to HxSidebar so we will give it some upgrade soon.

There is new <ContentTemplate> parameter added to HxSidebarItem component in last release (2.7.3).
The desired effect can be achieved through the .collapsed class as mentioned above.
Closing this for now.
If you feel there is still something what should be fixed/added to the library, feel free to reopen the issue / add comments.


Use short array syntax

I've replaced all instances of the usage of array() with the Short Array Syntax [] which was introduced back in PHP 5.4.
Since this project currently only supports PHP 8.1+ there's no need to keep using the array() syntax for working with arrays.

Thanks for the contribution.
I am aware of  the short syntax but prefer using array() instead. I feel it is more expressive.


Add other users' authorized_keys not only root's

Not only root can have several public keys in their authorized_keys file. Imagine we have a demo user called demo and several people can login as a demo user. We'd like to know who used the demo account.
Looks like the database will need another field. Maybe it's time to switch to SQLite to use tables?

Fingerprint -> user@host comment should be fine for the database. No need to change the structure.
We will be able to find the username from the sshd journal, from the line
Accepted publickey for pavel from <IP_ADDRESS> port 53802

We can have a list of authorized keys in the YAML config. We don't have to scan all existing keys on the host.
Then if we see some user to log in but we don't have a authorized_keys for them we report about it in the log.


Issues with IE8 and jQuery 1.7

Hey,
Im getting the "Object doesn't support this action" error in IE8 with jQuery versions >= 1.7. It works fine with any versions < 1.7 and seems to work in all the other browsers with either. I have been testing with the latest release (1.1.3) and I've also tried with the latest dev release.
I would just use the older jquery version except I need the '.on' events introduced in this version.
Any ideas?
Cheers,
Tom

Ive put an example of this behaviour up here:
http://instantiate.co.uk/reel_with_jquery1.7/test.html

Thanks for the example. One problem though - you link Reel from http://fl3/js/jquery/, so it doesn't work. Please make it point to http://code.vostrel.cz/jquery.reel.js instead. Thanks again! ;)

Whoops sorry. Ive updated it now thanks

I believe this line in your source may be the cause:

It should look like this:

You don't put units into the width and height attributes. No other units than pixels can be used to define dimensions of HTML , so the px unit is implied and you define only numeric integer value.
Feel free to reopen if that's not it.

Hi pisi, this was another remnant of my testing. I have updated this and still have the same issue. I would reopen the issue but I dont have permission! Thanks, Tom

I too have the same issue with IE 8
included http://code.jquery.com/jquery.min.js in my html
works fine with other browsers, IE 8 cracks my head..

Hi pisi, have you made any progress on this? If you have any ideas let me know, Ive been trying to crack this for a while but not got very far. If you have any suggestions Id love to hear them, see if I can help with anything.

yeah mee too looking for a solution on this

@pelister has made a very useful observation, that the version of mousewheel plugin, which is shipped alongside Reel is incompatible with jQuery 1.7.x and IE combination.
Please update your copy of mousewheel with the latest version, it should free you of the  "Object doesn't support this action" error. It still won't drag correctly though, for that the changes done in the augmented-frames branch are needed and that one isn't online yet. Will keep you posted.

Can you please report back to me, if the fresh development version 1.1.3-devel makes any difference in your attempts to get along with IE. It should... Mind the aforementioned necessity of upgrading your mousewheel plug-in. Version 6.0.2 didn't get along with jQuery 1.7 very well.

Hey @pisi, still having the same problem with this latest dev release (have updated the test page above), though I havent done anything with the mousewheel plug in because I was not using it before. I am only linking jquery 1.7.1 and this latest dev reel release on the test page. Do I still need to do anything with the mousewheel plugin?

Ive made a copy of the latest dev release and commented out all references I can see to mouse wheel behaviour. Still getting same problem (http://instantiate.co.uk/reel_with_jquery1.7/test2.html).

hi lopsided take a look on this
using jquery.reel latest dev branch( https://github.com/pisi/Reel/tree/development)
jquery 1.7.1
mousewheel 3.0.6
works fine on all browsers,  if you want to take a look http://orscella.com (Joomla plugin development stage).
I have noticed two problems though..

stop button do not work after page loads. but works when we perform some other actions - mouse drag , mouse wheel etc.

conflict with mootools on opera only.

Hey pelister,
Ive updated my test page with the same links to reel and mousewheel as on the orscella link. I also copied the set up code (this bit: $('#testtn').reel({ ....})). There is definite progress! The reel is rotating now, but there are 2 problems I can see which are occurring in FF now as well as IE. All of the frames are appearing on the page and there is no indicator! Am I doing something wrong here?
I can see the orscella page is working great but there is a lot going on on it; maybe Ive missed something that needed extracting too...?
See it here http://instantiate.co.uk/reel_with_jquery1.7/test.html

ps. The indicator I could live without ;)

hi lopsided, the setup code on orscella is generated by a php file.
I read images from specified directory, sort them in asc order and pass the array to reel.
if your running it as a script better try this way, instead of passing path: images/ which is in your code.
pass the absolute path like home/..../html/sitename/folder
or you no need to use path option pass the image array with full link for each image as you see in my code.
if you need php test code that  I use I can give you ... but I dont know how to attach files here

Hi pelister,
I must be missing something still.
This is all Im linking to in :

In :

If you check this out in FF or IE its rotating fine, but with no indicator and all the images in the reel rendering on the page... Is there any css that I should be including?
Cheers

hi lopsided, code looks fine, this is my email id<EMAIL_ADDRESS>send me a mail I will forward the files I use test with that.

First to answer your question: no, the mousewheel plugin is not needed to get Reel running. It's just fine without it.
I know now! You've tapped it @lopsided, thanks! Reel keeps some its styling rules in a dynamically injected stylesheet in the head. The