chore: add workflow to enforce Conventional Commit tags

Currently our release process is fairly manual:  someone with write access to this repo has to check out the latest from main, look at what has changed since the last release, decide on an appropriate new version number, create a git tag in the correct format (is it x.y.z or vx.y.z?), and push that tag back up to GitHub to trigger the release process.
By ensuring that our PR titles have Conventional Commit tags, we make it possible to automatically determine the next release version number, which means we can move to a push-button release process: click the release button, and the workflow does the rest.
This workflow has been in place for some time on metal-go and was recently adopted in metal-java; adopting it more broadly will make it easier for us to safely share the responsibility for releasing our various tools (and could even lead to automated / scheduled release workflows instead of push-button workflows).

Codecov Report
Patch coverage has no change and project coverage change: -0.02% :warning:

Comparison is base (c79e84c) 59.75% compared to head (79ee5f9) 59.74%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #370      +/-   ##
==========================================
- Coverage   59.75%   59.74%   -0.02%
==========================================
  Files          98       98
  Lines       19750    19750
==========================================
- Hits        11802    11799       -3
+ Misses       7654     7648       -6
- Partials      294      303       +9

see 8 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

This workflow checks the PR title, not the commit messages, so adding the Conventional Commit tag can be done by editing the PR title without making any changes to the commits in the PRs.
When a PR is opened without Conventional Commit tags, the workflow adds a comment to the PR that explains what the issue is and how to fix it (screenshot below is taken from equinix-labs/metal-go#134:

When the PR title is updated to fix the issue, the comment is deleted.  By enforcing tags on the PR titles, we make it possible for internal people to add the necessary tags if, for example, we get a good PR from an external contributor and that contributor is not motivated to add the necessary tag or picks the wrong tag.

By ensuring that our PR titles have Conventional Commit tags, we make it possible to automatically determine the next release version number, which means we can move to a push-button release process: click the release button, and the workflow does the rest.

We'll want to identify how breaking changes can be surfaced (and we'll want to use those sparingly, fitting the Terraform provider guidance on introducing breaking changes).
We may want to draw attention (through PR comments) to https://developer.hashicorp.com/terraform/plugin/sdkv2/best-practices/deprecations whenever we can detect (through code changes or commit messages) that a deprecation or breaking change has been introduced.


[Bug] Auto merge bot in unstable result in a bug

duplicated src defined here
after this commit my nixos can not be built

Should be fixed. Could you please test again?

daed version of unstable is identical to the main branch since it has no automatic update.

fixed.
thank you!


[ADAP-570] [Regression] Why dbt-redshift 1.5+ is available on pypi knowing the issues with it?

Is this a regression in a recent version of dbt-redshift?

[X] I believe this is a regression in dbt-redshift functionality
[X] I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior
Sorry, didn't know where to post this, but it's been 3 weeks from the last release that needs timeout tweaking to make it work.
Expected/Previous Behavior
Why is that release still exists? dbt-redshift should roll back to the last fully working version <1.5 I guess.
Steps To Reproduce

Install 1.5+, note that this version needs to be tweaked to run.
Rollback to previous version

Relevant log output
No response
Environment
- OS:
- Python:
- dbt-core (working version):
- dbt-redshift (working version):
- dbt-core (regression version):
- dbt-redshift (regression version):

Additional Context
No response

Thank you for reaching out @alejandrofm !
We've had several issues during our switch from psycopg2 to redshift_connector as the underlying Python connector, and https://github.com/dbt-labs/dbt-redshift/issues/427 is one of them. We're sorry for how this affects you and others.
Fully reverting back to 1.4.0 has its own downsides that we are unwilling to adopt. Instead our approach is to provide fixes or workarounds for dbt-redshift 1.5.x with dbt-redshift 1.4.x as the fall-back for those that can't upgrade yet due to a regression that affects them.
We realize that this might not be satisfactory, but we are doing our best to reestablish parity.
You are welcome to participate in the Discussion here along similar lines: https://github.com/dbt-labs/dbt-redshift/discussions/457
Workarounds in the meantime
Using 1.4.x
To use 1.4.x from PyPI, you can do something similar to the following:
python3 -m pip install dbt-redshift~=1.4.0

Timeout workaround
For 1.5.0, you can add an absurdly high timeout within your profiles.yml:
      connect_timeout: 999999

Thank you, we had some hiccups here and without the availability of this version, we would waited a little longer.
It resonates with me how the deploy passed tests against a Redshift database, and how can those tests be improved.
Another thing is, because this version isn't working, why not make a "hotfix" release a 1.5.1b that sets by default:
connect_timeout: 999999
and remove it for the next versions, so the users don't have to hardcode variables for this version only.
Thanks

Excellent question, but I'm moving the conversation to https://github.com/dbt-labs/dbt-redshift/discussions/457
See you there!


Closing some popup via mouse click breaks all subsequent popups

Description
If you open the popup (f)etch (e)lsewhere then mouse click outside it will close the popup and defunct all other subsequent popups.
Another popup that has this property is (m)erge (m)erge.
Neovim version
master
Operating system and version
linux
Steps to reproduce
See description
Expected behavior
Mouse clicking should either not close the popup or call the same clean up code that pressing <ESC> does.
Actual behavior
All popup don't work after this
Minimal config
-- NOTE: See the end of this file if you are reporting an issue, etc. Ignore all the "scary" functions up top, those are
-- used for setup and other operations.
local M = {}

local base_root_path = vim.fn.fnamemodify(debug.getinfo(1, "S").source:sub(2), ":p:h") .. "/.min"
function M.root(path)
  return base_root_path .. "/" .. (path or "")
end

function M.load_plugin(plugin_name, plugin_url)
  local package_root = M.root("plugins/")
  local install_destination = package_root .. plugin_name
  vim.opt.runtimepath:append(install_destination)

  if not vim.loop.fs_stat(package_root) then
    vim.fn.mkdir(package_root, "p")
  end

  if not vim.loop.fs_stat(install_destination) then
    print(string.format("> Downloading plugin '%s' to '%s'", plugin_name, install_destination))
    vim.fn.system({
      "git",
      "clone",
      "--depth=1",
      plugin_url,
      install_destination,
    })
    if vim.v.shell_error > 0 then
      error(string.format("> Failed to clone plugin: '%s' in '%s'!", plugin_name, install_destination),
        vim.log.levels.ERROR)
    end
  end
end

---@alias PluginName string The plugin name, will be used as part of the git clone destination
---@alias PluginUrl string The git url at which a plugin is located, can be a path. See https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols for details
---@alias MinPlugins table<PluginName, PluginUrl>

---Do the initial setup. Downloads plugins, ensures the minimal init does not pollute the filesystem by keeping
---everything self contained to the CWD of the minimal init file. Run prior to running tests, reproducing issues, etc.
---@param plugins? table<PluginName, PluginUrl>
function M.setup(plugins)
  vim.opt.packpath = {}                      -- Empty the package path so we use only the plugins specified
  vim.opt.runtimepath:append(M.root(".min")) -- Ensure the runtime detects the root min dir

  -- Install required plugins
  if plugins ~= nil then
    for plugin_name, plugin_url in pairs(plugins) do
      M.load_plugin(plugin_name, plugin_url)
    end
  end

  vim.env.XDG_CONFIG_HOME = M.root("xdg/config")
  vim.env.XDG_DATA_HOME = M.root("xdg/data")
  vim.env.XDG_STATE_HOME = M.root("xdg/state")
  vim.env.XDG_CACHE_HOME = M.root("xdg/cache")

  -- NOTE: Cleanup the xdg cache on exit so new runs of the minimal init doesn't share any previous state, e.g. shada
  vim.api.nvim_create_autocmd("VimLeave", {
    callback = function()
      vim.fn.system({
        "rm",
        "-r",
        "-f",
        M.root("xdg")
      })
    end
  })
end

-- NOTE: If you have additional plugins you need to install to reproduce your issue, include them in the plugins
-- table within the setup call below.
M.setup({
  plenary = "https://github.com/nvim-lua/plenary.nvim.git",
  telescope = "https://github.com/nvim-telescope/telescope.nvim",
  diffview = "https://github.com/sindrets/diffview.nvim",
  neogit = "https://github.com/NeogitOrg/neogit"
})
-- WARN: Do all plugin setup, test runs, reproductions, etc. AFTER calling setup with a list of plugins!
-- Basically, do all that stuff AFTER this line.
require("neogit").setup({}) -- For instance, setup Neogit

Fixed on nightly by adding better support for scroll/click actions. Thanks for the report :)


Loops within Sankey

Hi all!
I stumbled over this plugin where the demo site says :

The algorithm could be improved in the future, say to minimize link crossing or to support loopback in cyclical networks.

Does anybody know if the issue of Loops within the sankey are still present or have been already fixed?
Thank you in advance!
Cheers.

See d3/d3-sankey#1.


Simplified XWalkContent.java

Little change (simplification)

lgtm, thanks for the patch
@lincsoon, @wuhengzhi ^

LGTM, thanks.

No problem :)


IntelliJ checkstyle plugin dropped support for checkstyle 8.x, upgrade checkstyle to newer version

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
IntelliJ checkstyle plugin dropped support for checkstyle 8.x in the 5.88.0 version update.
Fails with this error message:

The Checkstyle rules file could not be parsed. cannot initialize module TreeWalker - cannot initialize module JavadocMethod - Property 'scope' does not exist, please check the documentation The file has been blocked for 60s

Solution

Upgrade buildtools/src/main/resources/pulsar/checkstyle.xml to support newer checkstyle 10.x version
Upgrade checkstyle to 10.x

Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

What do you think about https://github.com/diffplug/spotless?
This plugin supports check and format code, I think we can use spotless instead of checkstyle.
Once we notice that the code has been formatted by spotless on the master branch,  we will be limited when doing cherry-pick operations. If we can double-check by spotless and checkstyle, this will be simpler.

What do you think about https://github.com/diffplug/spotless?
This plugin supports check and format code, I think we can use spotless instead of checkstyle.
Once we notice that the code has been formatted by spotless on the master branch, we will be limited when doing cherry-pick operations. If we can double-check by spotless and checkstyle, this will be simpler.
We have this discussion thread on the<EMAIL_ADDRESS>but I don't know this URL, which title is [DISCUSS] Consistent code style (esp. ws/indent) and autotools

@nodece What you are proposing is a completely different thing. I don't think that we want to change the way how code is formatted in Pulsar right now. Such changes cause unnecessary code changes without valuable benefits.
We should simply upgrade checkstyle to a supported version right now. That requires migrating the configuration file slightly.

Upgrading the checkstyle is simpler, I agree with you.
Right now, the checkstyle is not strict, some places have extra indentation, while others have extra spaces, so I suggest using spotless.

Upgrading the checkstyle is simpler, I agree with you. PR: https://github.com/apache/pulsar/pull/22291
Right now, the checkstyle is not strict, some places have extra indentation, while others have extra spaces, so I suggest using spotless.

Making a change to formatting is a broad change that cause more harm than benefit to the Pulsar project currently. We can reconsider after the maintenance strategy has been revisited.


feat: XBlock.usage_key, XBlock.context_key convenience props

Reasoning
According to these warnings, we should eventually make these updates across the board:

block.location -> block.scope_ids.usage_id
block.course_id -> block.scope_ids.usage_id.context_key

The thing is... these new names are (subjectively, of course) not very good 😄 They take longer to type out, they take up more space on a line, and IMO are more intimidating to devs who don't have their heads way into XBlock land. Every time I update code from location or course_id to the new, longer name, I find the resulting line harder to read. It also took me a long time to remember whether to use id versus key, which is maddeningly inconsistent in the phrase "block.scope_ids.usage_id.context_key".
I propose:

block.location -> block.usage_key
block.course_id -> block.context_key

I'd also be open to:

block.location -> block.usage_id
block.course_id -> block.context_id

or, if we want the interface to remind people that a context key is, conceptually, just a component of a usage key:

block.location -> block.usage_key
block.course_id -> block.usage_key.context_key

To Do

shop this idea around
update the changelog and version
unit test
update the docs
post-merge: update warnings in https://github.com/openedx/edx-platform/blob/master/openedx/core/djangoapps/xblock/runtime/shims.py

Things I like:

no (fewer) warnings :)
the name of the var describes what it is and can possibly be.

Therefore, I think your changes make sense.
That being said, course_id -> context_key will require some evangelization. "Course id" is common parlance, and there certainly are a broad variety of contexts outside of xblocks where it is used. A line as to where context_key is used as opposed to course_id will require good, visible documentation.

I'm good with it. I agree with usage_key and context_key.

That being said, course_id -> context_key will require some evangelization. "Course id" is common parlance, and there certainly are a broad variety of contexts outside of xblocks where it is used. A line as to where context_key is used as opposed to course_id will require good, visible documentation.

Agreed, but I think it's important that we do. There's a VideoBlock handler that currently breaks in content libraries right now because there's no course_id in a v2 library.

I agree, and I like the proposed block.usage_key and block.context_key.
I have a question in turn, which is: can we specify a type hint that these return UsageKey and LearningContextKey? That would be nice (assuming we also added a py.typed file to this repo), but would be wrong in the specific case of using the new .usage_key convenience property in the XBlock-SDK which returns some other usage ID format ( a string I think?).

these new names

Also FWIW, the names (mostly) aren't exactly new... block.scope_ids.usage_id is 9 years old, vs. block.location 10 years old :p  Only context_key is somewhat new.

block.location -> block.usage_key
block.course_id -> block.context_key

This sounds good to me as well.

I have a question in turn, which is: can we specify a type hint that these return UsageKey and LearningContextKey? That would be nice (assuming we also added a py.typed file to this repo), but would be wrong in the specific case of using the new .usage_key convenience property in the XBlock-SDK which returns some other usage ID format ( a string I think?).

@bradenmacdonald Oof, I had no idea that xblock-sdk's runtime had different types for scope_ids. Is that difference considered a legit feature of the XBlock framework, or was it just that the opaque-keys project never got around to moving xblock-sdk from strings to keys?
I love adding type hints, but I don't want to add ones that will be wrong in certain cases.

My understanding was that "location" was a term we were trying to move away from. Am I incorrect?

@jansenk You're correct. It's just that the current replacement is unwieldy (block.scope_ids.usage_id).
This PR would make the replacement nicer (block.usage_key).

@kdmccormick

I had no idea that xblock-sdk's runtime had different types for scope_ids. Is that difference considered a legit feature of the XBlock framework, or was it just that the opaque-keys project never got around to moving xblock-sdk from strings to keys?

You can see the details here: https://github.com/openedx/xblock-sdk/blob/529c0c87a740e39f12ae42ec9ff735e198d983f1/workbench/runtime.py#L100-L157
The XBlock library has never cared what format your Scope IDs are in; they can be anything. XBlock SDK used strings, and edx-platform uses opaque keys.
The XBlock library also requires a "definition ID" as one of the Scope IDs and requires some usage of it in the API, though that hasn't proven to be a very useful concept, and Learning Core may not use it at all.
I think it would be reasonable at this point to change the XBlock SDK core lib to require that the scope IDs are opaque keys, and change the XBlock SDK accordingly. The XBlock SDK doesn't have to use the same opaque keys as edx-platform; since it uses scenarios instead of courses for example it could use its own type of usage key that references a scenario as its context, not a course. I think that would be a nice win for consistency if we're using opaque keys across the board, and let use do type hints.

@bradenmacdonald I opened https://github.com/openedx/XBlock/issues/707 and https://github.com/openedx/xblock-sdk/issues/342. I think we can merge this PR without tackling those first. Let me know if you disagree.

Sounds good to me @kdmccormick 👍🏻


227 해몽꿈 전체수정 오류

Closes #227

Codecov Report

Merging #228 (af83596) into main (eb10bfb) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main     #228      +/-   ##
============================================
- Coverage     46.43%   46.32%   -0.12%
  Complexity      433      433
============================================
  Files           153      153
  Lines          2063     2068       +5
  Branches         28       28
============================================
  Hits            958      958
- Misses         1094     1099       +5
  Partials         11       11

Impacted Files
Coverage Δ

...dream/interpretationdream/InterpretationDream.java
14.28% <0.00%> (-2.39%)
:arrow_down:

...interpretation/InterpretationDreamServiceImpl.java
1.49% <0.00%> (-0.10%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eb10bfb...af83596. Read the comment docs.


⚠ SpeakUpConference.com has degraded performance

In d513eda, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 7549 ms

Resolved: SpeakUpConference.com performance has improved in 7d2641a after 23 minutes.


Update sbt-ci-release to 1.5.9

Updates com.geirsson:sbt-ci-release from 1.5.7 to 1.5.9.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.geirsson", artifactId = "sbt-ci-release" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #1009 (1422001) into develop (0c45f93) will increase coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1009      +/-   ##
===========================================
+ Coverage    89.57%   89.70%   +0.13%
===========================================
  Files          124      124
  Lines         9905     9905
  Branches       511      511
===========================================
+ Hits          8872     8885      +13
+ Misses        1033     1020      -13

Impacted Files
Coverage Δ

...main/scala/com/twitter/algebird/monad/Reader.scala
52.94% <0.00%> (-5.89%)
:arrow_down:

.../main/scala/com/twitter/algebird/BloomFilter.scala
93.80% <0.00%> (-0.89%)
:arrow_down:

.../main/scala/com/twitter/algebird/HyperLogLog.scala
89.61% <0.00%> (-0.44%)
:arrow_down:

...re/src/main/scala/com/twitter/algebird/QTree.scala
79.76% <0.00%> (+1.19%)
:arrow_up:

.../main/scala/com/twitter/algebird/Applicative.scala
55.17% <0.00%> (+3.44%)
:arrow_up:

...rc/main/scala/com/twitter/algebird/SGDMonoid.scala
51.72% <0.00%> (+3.44%)
:arrow_up:

...src/main/scala/com/twitter/algebird/Interval.scala
86.08% <0.00%> (+6.95%)
:arrow_up:

...ala/com/twitter/algebird/ApproximateProperty.scala
82.00% <0.00%> (+10.00%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0c45f93...1422001. Read the comment docs.


Question: Can Malmö be used via a NAT setup?

I am trying to do the following:

start the Malmö Client in a docker container
start a Python Agent from a host machine (OS X) and get a mission to run successfully.

Due to Docker on Mac, the network connectivity is established via a NAT, and somehow this means the IP detected by the Client is not that of the Agent, but that of the bridge (of the VM in which Docker runs). To cut the story short, I can get some degree of connectivity if I inject the real IP of the host, but the only way I manage to do so is by modifying the code of the Client, while it seems to me that it would be possible doing the same thing during the initialization if there were a way of passing a Mission Init XML to a client from an agent, or if the AgentAddress could be set during the initialization o f the mission, but I didn't find a way of doing so.
It is not that important as my goal is playing with the algorithms, not with network setups (and the only difference would be if I use one or two computers to run client and agent, or no), but thought it was worth asking, just in case.

Running the agent from a different docker container (but in the same docker host, and therefore directly in the same network) works quite well, by the way.

I've had success running docker in host networking mode, i.e.
docker run --network=host quay.io/tambet/malmo:0.18

Ultimately we'd love to get Malmo working well in Docker. I spent some time yesterdat trying to run as per your initial setup - the Minecraft client running in a container, and the agent running on the host machine.
I'm new to Docker and all its intricacies, so I'd welcome any pointers. As far as I can tell, there are a few difficulties with the TCP code as it stands. The main issue is that ports are allocated dynamically, at the start of each mission. Both the mod (Minecraft-side) and the platform (Agent-side) choose their own ports (in the range 10000-11000), and then communicate them via the MissionInit message. We do this so that only one port ever needs to be fixed - the mission control port (10000 by default). All the other ports (for sending video, sending observations, sending rewards, and receiving commands) can then be picked according to what's free, ensuring there are never any port collisions.
This doesn't fit well with Docker (in non-host networking mode), which - if I understand this correctly - requires the ports to be specifically exposed and mapped when the container is run. Trying to cover all bases by exposing all the ports from 10000 to 11000 fails (whatever is involved in exposing the ports is clearly not something that ought to be done a thousand times...)
We could allow a user to pick specific ports - most of this code already exists, we just never exposed the interface to the user. I'll experiment a little and see if this helps.
I think it's especially worth getting this scenario working on Windows, because Docker doesn't seem to support interactive mode on Windows yet, which makes the other option - running the agent from a different docker container, on the same docker host - feel a bit cumbersome. (Though I guess it needn't be - I need to try this out.) More importantly, we need to make sure agents and clients can run on separate machines - this is pretty crucial.
Incidentally, I couldn't get host networking mode to work - I guess I need to do some firewall shenanigans, but I've been running on Windows, and most of the help on the Internet assumes Linux...


Reorganising biology taxonomy

If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

moving knowledge/STEM/Science/Natural_Science/Biology to knowledge/science/biology/
moving knowledge/biology/ to knowledge/science/biology

The purpose is to provide a single location for biology knowledge contributions. There were three previously

Hi! thank you so much for your submission. But please remove the reorganization of the tree, that needs to be another PR.
Also the submission you reference is not from one of our legally trusted places we can get content from at this moment. https://github.com/instructlab/taxonomy/pull/1205/files#diff-ef360a8f60b740a92a7b7b6e0caeb77c5e6b1b7fbaec3f436b4e9494c29b4806R2
I'll bring this up in the triage meeting, but it's unlilkely we can accept this in the the near future.

Hello! Thank you for this submission. Unfortunately, we need you to fill out the knowledge submission form before we can accept any submission from you. Please take a moment to fill it out so we can get this through the proper channels.
I will close this for now, but if/when you get the submission approval, you can reopen the PR, and we can look at adding it to the knowledge submission process.


[UI] Fix out-date README.md about Development Project

Why are the changes needed?

Fix out-date README.md about Development Project
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #4565 (a7ee5a4) into master (465e23a) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #4565      +/-   ##
============================================
- Coverage     53.29%   53.22%   -0.08%
  Complexity       13       13
============================================
  Files           573      573
  Lines         31501    31501
  Branches       4239     4239
============================================
- Hits          16790    16765      -25
- Misses        13132    13153      +21
- Partials       1579     1583       +4

see 8 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update and fix examples

I was just playing around with the alpha and needed an example of using this. When I came across the examples, they got me almost there, but I had to finish them like this PR does to get them to run in Ellie. I thought I'd contribute these back so that the next person looking for examples doesn't have to do this.
Here are some Ellies pointing to the working examples:
drag: https://ellie-test-19-cutover.now.sh/33pKWyW8mGJa1
wasd: https://ellie-test-19-cutover.now.sh/33pQTVhM7jga1
Note: In the drag example, I added the wrapping div to prevent a bug where you could accidentally mouseup outside the element and lose track of it.

Can you do a PR that only has the code changes? The reformat makes it really hard to tell what you had to change.

Sure, I can! @evancz, for my own information, is elm-format not the community standard when contributing?

It is the standard. The code here is sort of a draft, so it's just harder to review a PR if it does two things at once.

Okay, I totally understand. Thank you!


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/serving-wg-leads
/assign knative-sandbox/serving-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps

/retest

/retest


Fix broken peer OpenAI dep dependency range

https://semver.npmjs.com/

npm strictly checks peer dep ranges, which means the npm install of anything with a peer dep on Chroma was affected by this.

thank you!

@jacoblee93 will merge after tests pass , and then cut a new release tonight - will post here when that is done.

Wow that was fast! Thank you!

@jacoblee93 i have to live a certain way

@jeffchuber I think something's up with the last CI action?

Bump

@jacoblee93 digging in here this morning - sorry for delay


support more SSL related configurations in Kafka connector

right now, when connecting via SSL, the user is expected to input 4 fields:

properties.ssl.ca.location
properties.ssl.certificate.location
properties.ssl.key.location
properties.ssl.key.password

When RW is deployed in the cloud environment, the file needs to be mounted to the file system in the pod first and then the user can specify the path in the 3 location configs
Since we have supported create secret, it is easier if the user can just copy & paste the content of these files into RW as a secret. The Cloud user can still upload the file, but this uploading is just a widget on Cloud UI to copy & paste the content.
The change is that there is no longer a need to mount the file to the pod.
To support this, it requires the Kafka API, i.e. librdkafka to support configs of reading in credential content directly.
By checking https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md
each of the first three options has its corresponding API for reading in credential content, which is listed as follows:

properties.ssl.ca.location
->
ssl.ca.pem
ssl_ca

properties.ssl.certificate.location
->
ssl.certificate.pem
ssl_certificate

properties.ssl.key.location
->
ssl.key.pem
ssl_key

This makes the cloud deployment and usage easier

each of the first three options has its corresponding API for reading in credential content, which is listed as follows:

properties.ssl.ca.location
->
ssl.ca.pem
ssl_ca
properties.ssl.certificate.location
->
ssl.certificate.pem
ssl_certificate
properties.ssl.key.location
->
ssl.key.pem
ssl_key

This makes the cloud deployment and usage easier

Upvote for the option changes, but they are mostly for on-perm users. Cloud Kafka vendors seldom require using custom certs to connect to brokers. We need to be aware of the case.

I will keep the current ones, and add the "*.pem" ones for all three options, which is offered in other DB/ETL saas products
I will not add the ones without extension, they are in the form of special DER-encoded binary bytes.


Create integration tests suite

What was changed

Create a suite for running integration tests
NOTE depends on https://github.com/temporalio/temporal/pull/4026
Why?

adding integration tests
Checklist

Closes

How was this tested:

tested with History Replay integration test

Any docs updates needed?

sure let's just follow up here with tests https://github.com/temporalio/cli/pull/171


⚠ Jenkins Plugins Artifactory has degraded performance

In f4401ff, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1370 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 30388bc after 12 minutes.


fix update build-extension.yml

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

The change of this CI is not tested and covered.


Write tests

[x] unit test that 4*i lies on the 1/2 pleating ray and 37 lies on the 0/1 pleating ray and -43 lies on the 1/1 pleating ray (parabolic/parabolic case)
[X] unit test that riley_string * X * riley_string^-1 Y = farey_string
[x] unit test fixed points and words are equal to finite initial list
[x] verify trace of farey words equals value of farey polynomials

List in body is now implemented


No limit on stats increase

Once in the dungeon, I can just press R to open the character panel, use the left stick to select any stat I want and press B to increase it as much as I want.
There seems to be no check to limit the stats increase.

It seems to also leave the "+ LEVEL UP" icon on screen even though all the points are spent.


Remove DRIVER_EVENT_RECEIVER_URL env option, let Driver set URL dynamically

Driver should be able to set the event receiver URL dynamically (eg with POST /api/internal/webhook). The Driver may even want to use several event receiver URLs–– like separate endpoints per-community or per-plugin or per-plugin-per-community.

closing in favor of https://github.com/metagov/metagov-prototype/issues/97


[DOC] Index APIs and Datastream Limitations

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Our application stack collects log streams from several sources using Apache Kafka, then an AWS Lambda worker POSTs _bulk payloads against the OS API. One of our sources switched to using a datastream index and we immediately saw errors with the _bulk request.
The error message tells us that datastreams don't allow INDEX ops and require CREATE ops. The datastream documentation  don't mention this at all but instead indicate: "To ingest data into a data stream, you can use the regular indexing APIs."
This issue is to add explicit documentation of the API limitations when using datastreams. Either on the _bulk API documentation or in the datastreams documentation.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
PUT _index_template/ds-template
{
    "index_patterns": [
        "my-logs*"
    ],
    "data_stream": {
        "timestamp_field": {
            "name": "timestamp"
        }
    },
    "priority": 1,
    "template": {
        "settings": {
            "number_of_shards": 2,
            "number_of_replicas": 1
        },
        "mappings": {
            "properties": {
                "message" : {
                    "type": "text"
                },
                "timestamp": {
                    "type": "date",
                    "format": "yyyy-MM-dd HH:mm:ss||yyyy-MM-dd'T'HH:mm:ss.SSS'Z'||yyyy-MM-dd'T'HH:mm:ss.SSS'T'||yyyy-MM-dd||epoch_millis"
                }
            }
        }
    }
}

Then PUT a bulk payload to an index the pattern will match to
POST _bulk
{ "create": { "_index": "my-logs" } }
{ "message": "This is a log to test datastream creation via bulk API", "timestamp": "2023-02-09T23:04:08.162Z" }

Result:
{
  "took" : 130,
  "errors" : true,
  "items" : [
    {
      "index" : {
        "_index" : "my-logs",
        "_type" : "_doc",
        "_id" : null,
        "status" : 400,
        "error" : {
          "type" : "illegal_argument_exception",
          "reason" : "only write ops with an op_type of create are allowed in data streams"
        }
      }
    }
  ]
}

There is no current documentation on the Opensearch website I can find that tells us that Datastreams can only accept CREATE ops.

I had the same problem trying to make a Lambda function that collects all documents and does a _bulk operation. I found the problem in the Elasticsearch documentation.
Also, in my opinion the data stream documentation in OpenSearch is quite poor (there is no clear explanation about how the data stream works or that you need to apply an ism policy before creating the data stream). It would be nice to improve all this.

HI @bowenlan-amzn, can you help us update the documentation for this issue?

Not sure about this question. Need the data stream expert to help. @ketanv3


Validate modyn_config

There is currently no validation on modyn_config.
Add validation similar to validate_pipeline_config().

Hi @jenny011, there is something similar here, maybe extract that to the utils.

Done with https://github.com/eth-easl/modyn/pull/423, https://github.com/eth-easl/modyn/pull/435


[Patch] Flexbox padding for .explanator

The current explanatory section will break in certain languages, and this PR aims to fix that word-break situation by using the already-styled flexbox.
The following commit patches the issue described above:

🖼 fix: flexbox auto padding for explainatory subtitle (lifehome/Telegram-Limits@bc7b16d5b9814358b112f2029e5682b3f8a20e59)

Before:

After:

By design


WIP: Create job from job definition

WIP change for #209. Also fixes #225.
On the Job Definition Detail page, adds a "Run Job" button that brings the user to a minimal version of the Create Job form that displays only the job definition ID and lets the user edit parameters. The API to create a job this way is not yet available.
Demo video:
https://user-images.githubusercontent.com/93281816/198753293-50c90be5-7e93-4307-879a-0ccb52816195.mov

Overall, looks good. Wondering if we might want to name the action "Run job now" to emphasize that this is different from running it on a schedule. Also, the API in #228 will only allow users to set parameters, so we should hide the Additional options in this form. Also, will this form have the same job creation error handling as the normal create job (show the spinner, hide the buttons, show the error banner)?

I hesitated to use the word “now” because the button doesn’t take an immediate action, but rather brings the user to a form. (Perhaps “Run Job…” or “Run Job Now…” would be better.)
The button hiding behavior and error handling is the same as in the ordinary create job/JD form.
Sent from my iPhone
On Oct 29, 2022, at 12:12 PM, Brian E. Granger @.***> wrote:

Overall, looks good. Wondering if we might want to name the action "Run job now" to emphasize that this is different from running it on a schedule. Also, the API in #228https://github.com/jupyter-server/jupyter-scheduler/pull/228 will only allow users to set parameters, so we should hide the Additional options in this form. Also, will this form have the same job creation error handling as the normal create job (show the spinner, hide the buttons, show the error banner)?
—
Reply to this email directly, view it on GitHubhttps://github.com/jupyter-server/jupyter-scheduler/pull/227#issuecomment-1295941426, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWHV4GBJNTTODLLEDMF5V33WFVZGLANCNFSM6AAAAAARRQX3MA.
You are receiving this because you authored the thread.Message ID: @.***>

(Apologies for the botched non-rebase; I hadn't set up Git properly on my new computer yet)
Updates this change to remove advanced options from the run-from-JD form. Still WIP because no API is available yet.

This change is blocked until #228 is merged.

Request payload seems incorrect here, so passed parameters are not assigned. The payload should match the CreateJobFromDefinition model.
https://github.com/jupyter-server/jupyter-scheduler/blob/9dd885c967c98ee9bceb8046c066d1b2e5411de5/jupyter_scheduler/models.py#L272-L273


Possibility to group actions_list and actions_detail entries in a dropdown button

Do you have any examples?
When having a lot of actions available, it would be more user-friendly to group them in a dropdown button, exactly like the actions_row behavior.
Here is the existing feature :

And here, a proposal :

Is it a third party application feature request?
No
Describe your feature request
Maybe, an option in ModelAdmin allowing to group actions_list and another for actions_detail (False by default), would conditionally render the respective template.
actions_list_dropdown = True
actions_detail_dropdown = True
And maybe without any text (like "Actions") for the dropdown button, but just a hamburger menu icon ☰.

Oops, I just see my request is very close to #599 !
Thanks again for your great work 👍🏼 !


chore: Icon Widget

Fixes #30427

Summary by CodeRabbit

New Features

Introduced the WDSIconWidget for enhanced widget options, allowing users to integrate and configure icon widgets within the application.
Added icon widget configuration settings including icon selection, style customization, visibility toggling, and loading animation options.

Enhancements

Improved user experience with the addition of autocomplete functionality for the icon widget's properties.
Implemented a comprehensive property pane configuration for easier management of the icon widget's settings.

/build-deploy-preview skip-tests=true

Closing PR as not required as of now. cc: @KelvinOm


Documentation suggestion "Shard Stores for better concurrency" can be misread

"Shard Stores for better concurrency"
should be
"Sharded stores for better concurrency"
why?  Mild dyslexics may read Shard as Shared. Damn you brain!

fixed


Loader message describing gift feature

Heading: "Gift Sats"
Sub-heading: "Send sats as gifts to your friends and family. Gift sats that you receive can be added to your account or gifted further without any extra fees"
@cakesoft-shashank

Verified this issue on staging app v2.0.5(382)


Sphinx autodoc generates lots of warnings

Sphinx autodoc generates a lot of warnings related to items not existing in any toctree, changelog being the incorrect format, and duplicate attribute names in Lattice class

Resolved by ea06e3fec5aa2efb265ad824650d8448d6806652


Extract 2D Summary Output Data

Closes: #37, #38, #39, #40

Adds ability to export the following 2D Summary Output data from Plan HDF files:

Maximum Water Surface
Minimum Water Surface
Maximum Face Velocity
Minimum Face Velocity
Cell Maximum Water Surface Error
Cell Cumulative Iteration
Cell Last Iteration

Methods to export the above 2D Summary Output data as pandas DataFrame objects are added to the RasPlanHdf class:

mesh_max_ws
mesh_min_ws
mesh_max_face_v
mesh_min_face_v
mesh_max_ws_err
mesh_max_iter
mesh_last_iter

The following methods inherited by RasPlanHdf from RasGeomHdf are implemented, with ability to include (or exclude) summary the above 2D Summary Output data joined to the GeoDataFrame:

mesh_cell_points
mesh_cell_polygons
mesh_cell_faces

Also:

Adds test data from the "BaldEagleDamBrk" model from the HEC-RAS 6.5 Example Projects data. Note the included HDF file has been heavily pruned to only what's needed for summary output data extraction, in order to minimize file size in this repo.
Ability to export the above data via CLI
Fixes some hard-coded HDF paths in src/rashdf/geom.py

Example Usage
API
>>> from rashdf import RasPlanHdf, SummaryOutputVar
>>> plan_hdf = RasPlanHdf("tests/data/ras/BaldEagleDamBrk.p18.hdf")
>>> plan_hdf.mesh_max_ws()
          mesh_name  cell_id      max_ws         max_ws_time
0       BaldEagleCr        0  658.762207 1999-01-01 12:00:00
1       BaldEagleCr        1  648.673340 1999-01-01 12:00:00
2       BaldEagleCr        2  609.591919 1999-01-01 12:00:00
3       BaldEagleCr        3  622.499756 1999-01-01 12:00:00
4       BaldEagleCr        4  639.792175 1999-01-01 12:00:00
...             ...      ...         ...                 ...
1061  Upper 2D Area     1061  725.042358 1999-01-01 12:00:00
1062  Upper 2D Area     1062  694.854187 1999-01-01 12:00:00
1063  Upper 2D Area     1063  680.246826 1999-01-03 05:30:00
1064  Upper 2D Area     1064  680.081848 1999-01-03 05:32:00
1065  Upper 2D Area     1065  712.027466 1999-01-01 12:00:00

[4425 rows x 4 columns]
>>> plan_hdf.mesh_last_iter()
          mesh_name  cell_id  last_iter
0       BaldEagleCr        0          0
1       BaldEagleCr        1          0
2       BaldEagleCr        2          0
3       BaldEagleCr        3          0
4       BaldEagleCr        4          0
...             ...      ...        ...
1061  Upper 2D Area     1061          0
1062  Upper 2D Area     1062          0
1063  Upper 2D Area     1063         26
1064  Upper 2D Area     1064         11
1065  Upper 2D Area     1065          0
>>> # provide a list of outputs to include in the GeoDataFrame
>>> plan_hdf.mesh_cell_points(include_output=["Maximum Water Surface", SummaryOutputVar.CELL_MAXIMUM_WATER_SURFACE_ERROR])
          mesh_name  cell_id                        geometry      max_ws         max_ws_time  max_ws_err     max_ws_err_time
0       BaldEagleCr        0  POINT (2083680.700 370757.583)  658.762207 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
1       BaldEagleCr        1  POINT (2084180.700 370757.583)  648.673340 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
2       BaldEagleCr        2  POINT (2080680.700 370257.583)  609.591919 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
3       BaldEagleCr        3  POINT (2081180.700 370257.583)  622.499756 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
4       BaldEagleCr        4  POINT (2081680.700 370257.583)  639.792175 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
...             ...      ...                             ...         ...                 ...         ...                 ...
4420  Upper 2D Area     1061  POINT (1969828.738 290877.786)  725.042358 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
4421  Upper 2D Area     1062  POINT (1970328.738 290877.786)  694.854187 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00
4422  Upper 2D Area     1063  POINT (1968828.738 290377.786)  680.246826 1999-01-03 05:30:00    0.008994 1999-01-01 15:47:00
4423  Upper 2D Area     1064  POINT (1969328.738 290377.786)  680.081848 1999-01-03 05:32:00    0.009122 1999-01-01 15:47:00
4424  Upper 2D Area     1065  POINT (1969828.738 290377.786)  712.027466 1999-01-01 12:00:00    0.000000 1999-01-01 12:00:00

[4425 rows x 7 columns]
>>> # if "include_output" is True (default), return a GeoDataFrame with all available extractable summary output data
>>> plan_hdf.mesh_cell_faces()
          mesh_name  face_id                                           geometry  max_v          max_v_time  min_v          min_v_time
0       BaldEagleCr        0  LINESTRING (2065761.791 364007.583, 2066430.70...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
1       BaldEagleCr        1  LINESTRING (2066430.700 364007.583, 2066430.70...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
2       BaldEagleCr        2  LINESTRING (2066430.700 364695.876, 2066419.85...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
3       BaldEagleCr        3  LINESTRING (2047430.700 362507.583, 2047631.91...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
4       BaldEagleCr        4  LINESTRING (2047631.916 362708.798, 2047460.00...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
...             ...      ...                                                ...    ...                 ...    ...                 ...
9576  Upper 2D Area     2281  LINESTRING (1969578.738 289639.123, 1969608.17...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
9577  Upper 2D Area     2282  LINESTRING (2002308.817 323619.882, 2002136.09...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
9578  Upper 2D Area     2283  LINESTRING (2008279.679 319853.804, 2007812.00...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
9579  Upper 2D Area     2284  LINESTRING (1995261.183 317513.689, 1995038.21...    0.0 1999-01-01 12:00:00    0.0 1999-01-01 12:00:20
9580  Upper 2D Area     2285  LINESTRING (1966078.738 291981.202, 1966868.69...    0.0 1999-01-01 12:00:00   -0.0 1999-01-01 12:00:20

[9581 rows x 7 columns]

CLI
python src/cli.py mesh_cell_polygons ./tests/data/ras/BaldEagleDamBrk.p18.hdf \
  bald-eagle-mesh-cell-polygons.parquet --parquet

@sray014 @zherbz @slawler this is a pretty large PR and @bates-j is out on leave for a while. Figured we'd have a better chance of keeping stuff moving into main if I tagged 3 people for potential review instead of 2.


Moved component styles from core lib to default-theme

#Moved styles from core components into default-theme.
Slider is not rendering correctly, this is because react-themeable not only sets a className but also a key prop, which causes issues because the keys are currently hardcoded and results in dynamic children having the same key.

im going to pull this branch down, and try and separate these commits into individual pull requests so we can have a more self contained discussion/code review

also, a note on the last commit where you are refactoring autocomplete.
the way we are handling autocomplete doesnt actually need to be refactored. we are importing a third party autocomplete solution that already has react-themeable implemented.

Closing this PR as all the individual PRs have been successfully merged into Atlas as #40, #41, #42, #43, #44, #45, #46, #47, #48, #49, #50, #51, #52, #53, #54, #55, #56


Need a "Upload JSON File" feature in Workbench Form

When filling the form of workbench, there is a field of entering JSON input. There should also an option of uploading JSON file as input from the system. Incase of large JSON files, sometimes we need to upload them from the system.

This issue is addressed on #53.


Support Operator Hub in Rancher

OperatorHub is evolving a lot, and I think it would be a defeat for Rancher not to be able to incorporate it. it seems like the focus on RancherCatalog is decreasing, even though the GUI is one of the advantages of Rancher.
Since Rancher 2.6, the GUI has become less and less useful, so the benefit of using Rancher is decreasing.

Any news on Operator Hub support for Rancher?


TypeError encountered when recording video: Must be a real number, not NoneType

Description:
I encountered an issue when trying to record videos in my environment using the gymnasium.wrappers. RecordVideo wrapper. I receive an error indicating that the fps value is of NoneType when the code tries to save the video. Do I need to specify a specific frame rate (fps) when initializing the environment or in the configuration?
Steps to Reproduce:

Initialize a 'highway-v0' environment and wrap it using gymnasium.wrappers.RecordVideo.
Run the environment and perform actions.
Try to save the video upon environment termination or reset.

Expected Behavior:
The video should save successfully without any errors.
Actual Behavior:
A TypeError is thrown indicating that the fps value is NoneType.
Error Logs:
Traceback (most recent call last):
File "E:\DriveLikeAHuman-main\DriveLikeAHuman-main\HELLM.py", line 107, in
obs, reward, done, info, _ = env.step(output["action_id"])
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\record_video.py", line 180, in step
self.close_video_recorder()
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\record_video.py", line 193, in close_video_recorder
self.video_recorder.close()
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\monitoring\video_recorder.py", line 161, in close
clip.write_videofile(self.path, logger=moviepy_logger)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 54, in requires_duration
return f(clip, *a, **k)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 135, in use_clip_fps_by_default
return f(clip, *new_a, **new_kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 22, in convert_masks_to_RGB
return f(clip, *a, **k)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\VideoClip.py", line 300, in write_videofile
ffmpeg_write_video(self, filename, fps, codec,
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\io\ffmpeg_writer.py", line 213, in ffmpeg_write_video
with FFMPEG_VideoWriter(filename, clip.size, fps, codec = codec,
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\io\ffmpeg_writer.py", line 88, in init
'-r', '%.02f' % fps,
TypeError: must be real number, not NoneType
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:\DriveLikeAHuman-main\DriveLikeAHuman-main\HELLM.py", line 111, in
env.close()
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\record_video.py", line 217, in close
self.close_video_recorder()
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\record_video.py", line 193, in close_video_recorder
self.video_recorder.close()
File "C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\monitoring\video_recorder.py", line 161, in close
clip.write_videofile(self.path, logger=moviepy_logger)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 54, in requires_duration
return f(clip, *a, **k)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 135, in use_clip_fps_by_default
return f(clip, *new_a, **new_kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\decorators.py", line 22, in convert_masks_to_RGB
return f(clip, *a, **k)
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\VideoClip.py", line 300, in write_videofile
ffmpeg_write_video(self, filename, fps, codec,
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\io\ffmpeg_writer.py", line 213, in ffmpeg_write_video
with FFMPEG_VideoWriter(filename, clip.size, fps, codec = codec,
File "C:\Users\ASUS\anaconda3\lib\site-packages\moviepy\video\io\ffmpeg_writer.py", line 88, in init
'-r', '%.02f' % fps,
TypeError: must be real number, not NoneType
Moviepy - Building video E:\DriveLikeAHuman-main\DriveLikeAHuman-main\results-video\highwayv0-episode-0.mp4.
Moviepy - Writing video E:\DriveLikeAHuman-main\DriveLikeAHuman-main\results-video\highwayv0-episode-0.mp4
Moviepy - Building video E:\DriveLikeAHuman-main\DriveLikeAHuman-main\results-video\highwayv0-episode-0.mp4.
Moviepy - Writing video E:\DriveLikeAHuman-main\DriveLikeAHuman-main\results-video\highwayv0-episode-0.mp4
C:\Users\ASUS\anaconda3\lib\site-packages\gymnasium\wrappers\monitoring\video_recorder.py:182: UserWarning: WARN: Unable to save last video! Did you call close()?
Environment:
OS: [Windows 11]
Python Version: [3.10.13]
gymnasium version: [0.29.1]
moviepy version: [1.0.3]
IDE: [PyCharm 2023.2.1 (Professional Edition)]

hmmm... I'm not sure. Since I used Ubuntu to develop and test and I didn't encounter similar questions before.
My environment are:
gymnasium            0.28.1
moviepy                 1.0.3
Python                   3.8.16

Hope this can help!

This might be the compatible issue between moviepy and decorator. This solved my problem:
pip uninstall moviepy decorator
pip install moviepy

Refer to https://github.com/Zulko/moviepy/issues/1625#issuecomment-973056577


[odata-uri-builder] Support advanced search format

Feature request
Hi!
I might have skipped something and it might be there, but there seem to be missing advanced $search query API for odata v4.
Here is an example from the spec: http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_SystemQueryOptionsearch
Detail on formating: https://docs.oasis-open.org/odata/odata/v4.01/os/abnf/odata-abnf-construction-rules.txt
It would be a nice addition

Hey,
this feature has been implemented, but only in a simple form.
Since it's a V4 feature it's only to be found on the ODataUriBuilderV4 as method search.

Is this sufficient for you?

Hi!
We need to support multiple terms like "term1 term2" together, and also "term1" OR "term2", and combinaison of those.
Thanks

Hi @merlosy,
the advanced search format is now fully supported.
To get operators you need a QSearchTerm. A factory function called searchTerm should be used for that:
import { searchTerm } from "@odata2ts/odata-query-objects";

...
builder.search(searchTerm("test").or("my phrase"))

The search function as well as the factory function or any operator value allows for null and undefined to signal no value.
Passing strings instead of QSearchTerm objects will evaluate if this is a phrase (surrounded by double quotes) or only a single term.

Impolitely closed this ticket prematurely.


[AVOCADO-204] Add headers for hard filters.

Resolves #204.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/avocado-prb/163/
Test PASSed.


WIP: v4.0.0 Beta

Codecov Report

Merging #312 (fdca9cc) into develop (8ec39c1) will decrease coverage by 1.25%.
The diff coverage is 80.16%.

@@             Coverage Diff             @@
##           develop     #312      +/-   ##
===========================================
- Coverage    85.13%   83.88%   -1.26%
===========================================
  Files           17       17
  Lines          565      608      +43
  Branches       143      157      +14
===========================================
+ Hits           481      510      +29
- Misses          22       28       +6
- Partials        62       70       +8

Impacted Files
Coverage Δ

src/interfaces/listr.interface.ts
100.00% <ø> (ø)

src/listr.ts
88.46% <ø> (ø)

src/utils/prompt.ts
74.19% <ø> (ø)

src/utils/logger.ts
76.36% <16.66%> (-9.92%)
:arrow_down:

src/renderer/verbose.renderer.ts
68.57% <50.00%> (-4.16%)
:arrow_down:

src/renderer/default.renderer.ts
86.09% <83.14%> (-0.89%)
:arrow_down:

src/lib/task.ts
81.60% <88.88%> (+0.86%)
:arrow_up:

src/interfaces/state.constants.ts
100.00% <100.00%> (ø)

src/lib/task-wrapper.ts
90.32% <100.00%> (+0.32%)
:arrow_up:

src/utils/logger.constants.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e44e878...6f55cbf. Read the comment docs.


Show a failed activity log after deleting one blob snapshot successfully

Storage Explorer Version: 1.11.1
Build: 20191206.5
Branch: dev/marayerm/electron7/packaging
Platform/OS: Windows 10/Linux Ubuntu 18.04
Architecture: ia32
Regression From: Previous build (20191206.2)
Steps to reproduce:

Expand one storage account -> Blob Containers.
Create a new blob container -> Upload a blob to it -> Create snapshot for the blob.
Manage Snapshots -> Try to delete the snapshot.
Check the result.

Expect Experience:
Show a successful activity log.
Actual Experience:

Succeed to delete the blob snapshot.
The activity log shows 'Failed to delete...'.

More Info:
This issue doesn't reproduce on MacOS.

The issue is caused by an Electron bug https://github.com/electron/electron/issues/21515.
A workaround for this bug will be implemented.

This issue is fixed on build electron/8-20200504.7. So we close it.


Plugin Command: RegionLights with a cycle option

I don't fully know how the code works for the light tags, but I would like to see a way to see a way to set cycling lights for a region defined similarly to the tag for the events. If it was explained a little further; I could implement it myself.

Cycling lights are related to events. See Game_Event.prototype.incrementLightCycle and Game_Event.prototype.initLightData for more info.

I see. Unfortunately there is no container for the cycling lights if I were to try to changing lights for a region light. Thank you for answering my inquiry.


Configurable Line Length for Generator

Basically the title of the issue, right now the builder outputs a line length of 120 which I approve of, but most repositories I work with unfortunately still with a default of 80.
Happy to contribute a pull request. Just creating this issue to track.

Yes, we can add a build option to set this through build.yaml.


Drop dependency of TiDB for host info

Feature Request
Is your feature request related to a problem? Please describe:
Currently host info send queries to TiDB, which has several disadvantages:

The instance list may not be identical with the one in "instance" tab
Doesn't work when there is no TiDB
More potential bugs: A TiDB bug will break the functionality as well, even if original API works well.

Describe the feature you'd like:
Update the host info module to call debug API of each component directly.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

I didn't find implemented debug API to get host info in pd/tidb/tikv repos, so we should implement the API in pd/tidv/tikv first?

The implementation for TiDB and PD is in https://github.com/pingcap/sysutil.
We can start from dropping the dependency of CLUSTER_INFO table first, then CLUSTER_HARDWARE.


Add baseUrl to Medplum config file

coverage: 94.187%. remained the same when pulling 107c6b20332f692a85f1cd1d807e578a27ceb825 on config-base-url into 0d231211d54035ad091668955fa70829d6d234e1 on main.

Related: https://github.com/medplum/medplum/discussions/2006


Risk Tolerance Curve suggestion

This is not strictly required by the FAIR methodology but would be a nice addition.
Typically a CISO will draw the LOE for the inherent and residual risk, he will then ask his CTO/CEO/CFO to provide a few data points to build a risk tolerance curve.
An example from PAN talk is here:

The tolerance curve will be interpolated from the few datapoints (the user should choose from linear, expo or polynomial) provided.
The tolerance curve should then be intersected with the other two to find out the break out points.
Would be wonderful to have a class to inject such LOE from input data.
Cheers!

Found also an interesting tutorial here all in python:
https://fluidattacks.com/blog/quantitative-python/

From an API perspective, how do you see this working? I.e. how does an analyst define this curve?
t_curve = np.polyfit(
   [100, 1_000, 10_000],
   [1, .2, .1],
   3
)
fsr = FairSimpleReport([model_1, model_2))
fsr.add_tolerance_curve(t_curve)
fsr.to_html('output.html')

Hi @theonaunheim yes that would work!


Doesn't see any files? Can't save changes.

ecode starts in my home dir but the only folders it does see are ".local" and ".var".
No Documents and other home directories are detected. It even allows me to create Documents directory and then pretends to save a new file inside it but no changes are saved.

If you go to open a folder you can't navigate it? Which OS are you using? Can you send me a screenshot or a video? You can open any folder just passing the folder path as a command line parameter too: ecode /my/folder.

I'm experiencing the same problem on MX Linux Xfce (latest stable version), ecode 0.4.9 (Vajra) from Flathub. I can't see any folder other than ".local" and ".var", also, editing the path won't work, when I click the "Open" button it does nothing.

Ohh, I see... it seems that flatpak uses some kind of virtual file system. IDK if this was working before... I'll take a look, but this is a packaging issue. Meanwhile please use the available downloads from this repository.

Ohh, I see... it seems that flatpak uses some kind of virtual file system. IDK if this was working before... I'll take a look, but this is a packaging issue. Meanwhile please use the available downloads from this repository.

Hm, that might be the proble, it does not integrate well with the host system.
I hope it gets solved.

It can be solved, it's just a packaging issue. I was not responsible for creating the flatpak version so I never used it actively (I simply checked if the app was opening).
Here's the documentation for myself.
I tentatively should add to this the following options:
--filesystem=host
--socket=pulseaudio

I'll test it this weekend.

BTW, you can force the file system access, follow this guide.

Thanks for the info. By the way, I just downloaded the app image which doesn't have that problem, but I'd rather have it installed on my system so I can run commands from the terminal.

I made a few changes that will give host file system access, but ecode also relies on external CLI applications that cannot be acceded with the flatpak isolation model, so it's a really bad way to distribute ecode (I was not familiar at all with flatpak, I don't use it, but it was a contribution from another user so I continued updating the build. To enable access to external applications the user will have to configure ecode CLI dependencies manually, it's far from ideal and breaks the simplicity of ecode, but I'll continue making it available in flathub because it gives some visibility to ecode. Currently I'm waiting this PR to be accepted in order to be able to provide a way to users to access external CLI apps. They will need to follow some instructions that hope they help to guide the adventurous users. ecode will warn the user when running from flatpak on its first run that it's not the recommended user to use the editor and provided a link to the documentation mentioned.

Merged the fix here, it will be available in a few hours.


1.1.6

Landing this so i can publish and bump https://github.com/fractalwagmi/react-sdk/pull/127 on top of it


Legend for geometry data that is loaded from Assetstores

@danlipsa would be nice to address this next as we have discussed.

@aashish24 Sounds good. I'll start working on it in about a week.

Closed by https://github.com/Kitware/minerva/pull/441. Though it's not movable because it's created as a GeoJS UI layer.


[llvm] updated to 14.0.4 + add spirv backend support

Describe the pull request
the pull request updates vcpkg to be able to use the most resent version of llvm 14.0.4
also i added support to build llvm with the new spirv backend

What does your PR fix?
Fixes:

update latest version
add spirv backend

Which triplets are supported/not supported? Have you updated the [CI baseline]

I have not touched the CI
I have tested (windows| linux) (64bit) I do not have mac access.

Does your PR follow the maintainer guide?
Yes as far as I have Checked

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result? yes

PS D:\Desktop\vcpkg> ./vcpkg.exe x-add-version llvm
version 14.0.4 is already in D:\Desktop\vcpkg\versions\l-\llvm.json
version 14.0.4 is already in D:\Desktop\vcpkg\versions\baseline.json
No files were updated for llvm

same result for ./vcpkg x-add-version --all --verbose

Please use vcpkg x-add-version ... to update the files in versions. This ensure consistent formatting in every commit.

Forgot to do that last push on it

@BillyONeal thank you 😊 for the assistance

Thank you for the reviews 🙂 everything i'll use to improve future pr's

@JonLiu1993 what to you mean by requires all feature testing isn`t that what azure pipelines do? 😕😵💫

@JonLiu1993 what to you mean by requires all feature testing isn`t that what azure pipelines do? 😕😵💫 I mean it worked on my Linux and windows machine i'm confused? 😵💫 (please done take it as rude i really am just confused)

@pheonixfirewingz ,Take it easy, ci just test default-features, can't test other feature, we need test other features with x86-window,x64-windows,x64-windows-static and x64-linux triplet, if all successfully we will merge this pr.

@JonLiu1993 what to you mean by requires all feature testing isn`t that what azure pipelines do? 😕😵💫 I mean it worked on my Linux and windows machine i'm confused? 😵💫 (please done take it as rude i really am just confused)

@pheonixfirewingz ,Take it easy, ci just test default-features, can't test other feature, we need test other features with x86-window,x64-windows,x64-windows-static and x64-linux triplet, if all successfully we will merge this pr.

ok just with the label idk what i needed to do to fix it so was panicking that i missing something required forgive me  😅

@JonLiu1993 what to you mean by requires all feature testing isn`t that what azure pipelines do? 😕😵💫 I mean it worked on my Linux and windows machine i'm confused? 😵💫 (please done take it as rude i really am just confused)

@pheonixfirewingz ,Take it easy, ci just test default-features, can't test other feature, we need test other features with x86-window,x64-windows,x64-windows-static and x64-linux triplet, if all successfully we will merge this pr.

ok just with the label idk what i needed to do to fix it so was panicking that i missing something required forgive me 😅

this label just tell everyone this pr need test feature, that's all

@JonLiu1993 what to you mean by requires all feature testing isn`t that what azure pipelines do? 😕😵💫 I mean it worked on my Linux and windows machine i'm confused? 😵💫 (please done take it as rude i really am just confused)

@pheonixfirewingz ,Take it easy, ci just test default-features, can't test other feature, we need test other features with x86-window,x64-windows,x64-windows-static and x64-linux triplet, if all successfully we will merge this pr.

ok just with the label idk what i needed to do to fix it so was panicking that i missing something required forgive me 😅

This label just tell everyone this pr need test feature, that's all

ok 😅 thank you for your patience's with me to explain.🫂

@JonLiu1993 sometime is wrong with azure pipelines it been stuck for 3 hours this is not normal and it’s not just my pr that is doing it

@JonLiu1993 sometime is wrong with azure pipelines it been stuck for 3 hours this is not normal and it’s not just my pr that is doing it

It's most likely that there just were not more agents available.

I noticed an error in the output on this line in the logs (shows in red when running locally) https://dev.azure.com/vcpkg/public/_build/results?buildId=73447&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=da63cf11-1f12-503b-6d64-3b2fb713c172&l=3782
Error: Unrecognized identifer name spirv. Add to override list in triplet file.

Not sure what is actually causing it though... Maybe the "platform": "spirv" line in ports/llvm/vcpkg.json? Is this something to worry about?

I noticed an error in the output on this line in the logs (shows in red when running locally) https://dev.azure.com/vcpkg/public/_build/results?buildId=73447&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=da63cf11-1f12-503b-6d64-3b2fb713c172&l=3782

Error: Unrecognized identifer name spirv. Add to override list in triplet file.

Not sure what is actually causing it though... Maybe the "platform": "spirv" line in ports/llvm/vcpkg.json? Is this something to worry about?

What platform is this happening on i checking the azure and can't find what you are talking about

I noticed an error in the output on this line in the logs (shows in red when running locally) https://dev.azure.com/vcpkg/public/_build/results?buildId=73447&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=da63cf11-1f12-503b-6d64-3b2fb713c172&l=3782

Error: Unrecognized identifer name spirv. Add to override list in triplet file.

Not sure what is actually causing it though... Maybe the "platform": "spirv" line in ports/llvm/vcpkg.json? Is this something to worry about?

What platform is this happening on i checking the azure and can't find what you are talking about

Seems to be happening on all platforms. The link I posted should take you to the correct spot, but if not. Here's a pic

If you search the other OSs, it should also come up in the logs.

Idk where to start to fix is as the is not enough information to be useful

@JonLiu1993 @BillyONeal could you potentially tell me if this is a config error on my end or is it that azure is not set up to support the new backend for llvm?

"platform":"spirv" is saying "this feature may only be installed when targeting spirv", and vcpkg has no idea what "spirv" is. The allowable values for "platform"/"supports" are: https://github.com/microsoft/vcpkg-tool/blob/d2d696a5e87d5ab981b54a95e61bfb5bcf09c805/src/vcpkg/platform-expression.cpp#L44-L62

Dose that mean i have to submit a pr to the vcpkg tool?

Don't provide a "platform" element at all.

Don't provide a "platform" element at all.

@BillyONeal fixed! 😊

@pheonixfirewingz ,Could you test the features locally by command "./vcpkg install llvm[*]:x64-linux"?

@pheonixfirewingz ,Could you test the features locally by command "./vcpkg install llvm[*]:x64-linux"?

I could run it on my linux laptop if you need me to

@pheonixfirewingz ,Could you test the features locally by command "./vcpkg install llvm[*]:x64-linux"?

I could run it on my linux laptop if you need me to

Thanks for your help

I'll sent the log asap

@JonLiu1993 how do i compile with extra features without a vcpkg.json aka via command line? i wanting to add spirv to the log

@JonLiu1993 after me updating to the new Ubuntu 22.04 LTS the system-d memory daemon keeps killing the compile process because of it taking 75% of my ram at the linking stage what should i do? as i can not supply the log when it dose not complete

@JonLiu1993 after me updating to the new Ubuntu 22.04 LTS the system-d memory daemon keeps killing the compile process because of it taking 75% of my ram at the linking stage what should i do? as i can not supply the log when it dose not complete

I will find a free linux machine and try again

Thanks for the update and sorry for the runaround :D


Migrated the test project to NUnit

Related to issue #420, the TestFramework was changed to NUnit and several tests were updated to reflect NUnit framework principles.

My current Master branch has changes which should fix the issues mentioned


Change the way parameters are passed in

The way the parameters are now being passed in feels inconsistent with the API. The API provides named parameters (like track, artist, mbid, etc), but with this library, you have to know the order of the parameters to be able to use the API call.
What I've done with my fork is to use a hash to act as the named parameters from the API call. For example:
@lastfm.track.share('foo artist', 'foo track'<EMAIL_ADDRESS>'this is a message')

now becomes
@lastfm.track.share(:artist => 'foo artist',
                    :track => 'foo track',
                    :recipient =><EMAIL_ADDRESS>                    :message => 'this is a message')

This way, we don't have to know what order the parameter goes in.
Since I can't pick and choose what commits go into this pull request, there are some commits from @magnolia-fan for additional endpoints.

any news on this, pretty please?

bump


How to change the Standard Deviation which is by default 1

How to change the Standard Deviation to like 2 or 3, which is by default 1 in the DataDrift Dashboard?

Hi @nageshsinghc4
Unfortunately, we do not have this option in the configurations yet.
At the moment in can be done in the source code by changing the implementation of the https://github.com/evidentlyai/evidently/blob/main/evidently/widgets/data_drift_table_widget.py
To be more precise, this:
reference_std = np.std(reference_data[feature_name][np.isfinite(reference_data[feature_name])], ddof=1)
should be updated somewhat like that:
n_std = 3
reference_std = n_std*np.std(reference_data[feature_name][np.isfinite(reference_data[feature_name])], ddof=1)

And after this update the project should be rebuilt internally.
Do you think this parameter should be presented in the config as well?

Hi @emeli-dral,
Thanks that is quite helpful.
Indeed I think this should be included because in some use cases we need to consider normal distribution and filter out data points that lie within 3 Standard Deviation along with the mean.


SyncBot: Discourse adapter to confirm credentials earlier

When a Discourse adapter is constructed, ie during connect it could verify credentials.

Repurposing this one to reflect the use of the all-users token.


Doesn't restores repos from backup file

Steps to reproduce

restore backup from file.

Expected behavior
It should restore repo.
Actual behavior
It doesn't restores repo.
Crash logs
No response
Aniyomi version
<IP_ADDRESS>-7814
Android version
15
Device
Google pixel 6A
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extension's repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

It should restore repo.
It shouldn't, as extension repos aren't included in backups atm


Add function to compute fidelity of two density operators

Coverage remained the same at 0.0% when pulling 09462f1fdb161b68a80338aece4d932f9db2f440 on david-pl:fidelity into ae49302be23096f93c70da4df9a1317ceacd3183 on bastikr:master.


Arrow keys are not working in tmux

I'm a real fan of this setup. But I also really like tmux. When I run vim now in tmux my arrow keys kick me out of insert mode and print a,b,c, or d on a new line until I hit the ESC key. I'm not sure how to begin to debug this so I can fix it. But I would love it if someone either knows how to fix it or can point me to how I would start to debug it. Just to clarify, everything works fine outside of tmux.

could you paste your tmux arrow keys shortcuts from tmux config file here?

This is my tmux config file
# 0 is too far from ` ;)
set -g base-index 1
set -g default-terminal screen-256color
set -g mouse on
set -g monitor-activity on
bind > setw synchronize-panes

# No delay for escape key press
set -sg escape-time 0

# Reload tmux config
bind r source-file ~/.tmux.conf

#Plugins
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-resurrect'
set -g @plugin 'tmux-plugins/tmux-continuum'

#Continuum Settings
set -g @continuum-restore 'on'

#Vim restore settings
set -g @resurrect-strategy-vim 'session'

#Initialize TMUX plugin manager (Keep this line at the very bottom of the config file)
run '~/.tmux/plugins/tpm/tpm'

And here are all the keys that tmux list-keys reports as being bound to arrow keys.
bind-key    -T copy-mode    Up                send-keys -X cursor-up
bind-key    -T copy-mode    Down              send-keys -X cursor-down
bind-key    -T copy-mode    Left              send-keys -X cursor-left
bind-key    -T copy-mode    Right             send-keys -X cursor-right
bind-key    -T copy-mode    M-Up              send-keys -X halfpage-up
bind-key    -T copy-mode    M-Down            send-keys -X halfpage-down
bind-key    -T copy-mode    C-Up              send-keys -X scroll-up
bind-key    -T copy-mode    C-Down            send-keys -X scroll-down
bind-key    -T copy-mode-vi Up                send-keys -X cursor-up
bind-key    -T copy-mode-vi Down              send-keys -X cursor-down
bind-key    -T copy-mode-vi Left              send-keys -X cursor-left
bind-key    -T copy-mode-vi Right             send-keys -X cursor-right
bind-key    -T copy-mode-vi C-Up              send-keys -X scroll-up
bind-key    -T copy-mode-vi C-Down            send-keys -X scroll-down
bind-key -r -T prefix       Up                select-pane -U
bind-key -r -T prefix       Down              select-pane -D
bind-key -r -T prefix       Left              select-pane -L
bind-key -r -T prefix       Right             select-pane -R
bind-key -r -T prefix       M-Up              resize-pane -U 5
bind-key -r -T prefix       M-Down            resize-pane -D 5
bind-key -r -T prefix       M-Left            resize-pane -L 5
bind-key -r -T prefix       M-Right           resize-pane -R 5
bind-key -r -T prefix       C-Up              resize-pane -U
bind-key -r -T prefix       C-Down            resize-pane -D
bind-key -r -T prefix       C-Left            resize-pane -L
bind-key -r -T prefix       C-Right           resize-pane -R

Thanks for you help.

+1
I can confirm it on both using a Cygwin terminal on Windows 10 connected to an Ubuntu server through ssh and a vte console/terminal locally.
The problem exists when trying to move the cursor with the arrow keys in insert mode.
In a plain terminal the arrow keys move the cursor correctly, but they exit insert mode (stays in normal mode).
In tmux the behaviour is similar than in vi compatibility mode: in normal mode the arrows move the cursor correctly, but in insert mode they insert a new line just above the last cursor position with a single uppercase letter depending on the arrow key pushed.
Other vim ide configurations I tried (vim-ide by sebdah, yavide) do not have this problem.

I know this is an old thread, but just had this issue and solved it by adding set nocompatible to ~/.vimrc.


[KYUUBI #6373] Add empty RowSet for OpertationLog

:mag: Description
Issue References 🔗

This pull request fixes #6373
Describe Your Solution 🔧
ThriftUtils#EMPTY_ROW_SET is not suitable for OperationLog , so I add a new LOG_EMPTY_ROW_SET
Types of changes :bookmark:

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[X] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

ThriftUtils#EMPTY_ROW_SET is not suitable for OperationLog , so I add a new LOG_EMPTY_ROW_SET

Doesn't it work properly with thrift calls?

ThriftUtils#EMPTY_ROW_SET is not suitable for OperationLog , so I add a new LOG_EMPTY_ROW_SET

Doesn't it work properly with thrift calls?

Referring to the client reading log code, I did the following test and it worked very well.

https://github.com/apache/kyuubi/blob/12c5568c9b020b1212c9514f046c67fcb267467e/kyuubi-hive-jdbc/src/main/java/org/apache/kyuubi/jdbc/hive/KyuubiStatement.java#L736-L740

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 58.42%. Comparing base (12c5568) to head (7219d35).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #6378      +/-   ##
============================================
- Coverage     58.51%   58.42%   -0.10%
  Complexity       24       24
============================================
  Files           653      653
  Lines         39895    39896       +1
  Branches       5482     5482
============================================
- Hits          23345    23308      -37
- Misses        14055    14088      +33
- Partials       2495     2500       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Shall we fix it by asserting getColumns() != null

Shall we fix it by asserting getColumns() != null

I guess that's enough for this issue, should we do that?

Yes. It's a straightforward way

Yes. It's a straightforward way

thanks, changed.

thanks, merged to 1.8.3


Test Discovery Failure on python 3.9 after EOT support added

Type: Bug

Behaviour
Expected vs. Actual
I expect all my various tests to load in the testing pane, but my python 3.9 tests fail to load, while my python 3.11 tests load successfully. The exception raised is from line 609 of https://github.com/microsoft/vscode-python/blame/main/pythonFiles/vscode_pytest/init.py which was updated with this PR 3 days ago to add EOT testing: https://github.com/microsoft/vscode-python/pull/21876
Stack Trace in Python Test Output:
File "/.vscode/extensions/ms-python.python-2023.17.12611008/pythonFiles/vscode_pytest/init.py", line 609, in
class EOTPayloadDict(TypedDict):
File "/.vscode/extensions/ms-python.python-2023.17.12611008/pythonFiles/vscode_pytest/init.py", line 612, in EOTPayloadDict
command_type: Literal["discovery"] | Literal["execution"]
TypeError: unsupported operand type(s) for |: '_LiteralGenericAlias' and '_LiteralGenericAlias'
Steps to reproduce:

Open the testing pane, the 3.11 tests load and the 3.9 tests do not

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.11.5
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2023-09-18 11:14:59.718 [info] Experiment 'pythonTestAdapter' is active
2023-09-18 11:14:59.718 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-09-18 11:14:59.718 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-09-18 11:14:59.718 [info] Experiment 'pythonSurveyNotification' is active
2023-09-18 11:14:59.718 [info] Experiment 'pythonTerminalEnvVarActivationcf' is active
2023-09-18 11:14:59.718 [info] Test server listening.
2023-09-18 11:14:59.718 [info] Python interpreter path<EMAIL_ADDRESS>2023-09-18 11:15:01.312 [info] Starting Pylance language server.
2023-09-18 11:15:06.268 [info] Discover tests for workspace name: B - uri: ~Documents/B
2023-09-18 11:15:06.268 [info] Running discovery for pytest using the new test adapter.
2023-09-18 11:15:06.279 [info] > . ~/Documents/venvs/venv3.9/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2023.17.12611008/pythonFiles/printEnvVariables.py
2023-09-18 11:15:06.299 [info] shell: bash
2023-09-18 11:15:06.565 [info] > ~/Documents/venvs/venv3.9/bin/python -m pytest -p vscode_pytest --collect-only .
2023-09-18 11:15:06.594 [error] Subprocess exited unsuccessfully with exit code 1 and signal null. Creating and sending error discovery payload
2023-09-18 11:15:06.751 [info] Test server connected to a client.
2023-09-18 11:15:06.757 [info] Firing data received event,  {"cwd": "/~/Documents/3.11Project", "status": "success", "tests": {"name": "", "path": "~/Documents/3.11Project", "type_": "error", "children": [], "id_": ""}, "error": []}
2023-09-18 11:15:06.757 [info] Firing data received event,  {"command_type": "discovery", "eot": true}
2023-09-18 11:15:06.757 [info] ResultResolver EOT received for discovery.

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

formatting
• provider: "none"

experiments
• optInto: ["pythonTestAdapter"]

Extension version: 2023.17.12611008
VS Code version: Code 1.82.2 (Universal) (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:59:47.790Z)
OS version: Darwin arm64 22.6.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
4, 4, 3

Memory (System)
32.00GB (3.83GB free)

Process Argv
--crash-reporter-id f85e293f-1fc8-4935-9132-aca59d4b4a65

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstes516:30244333
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
282f8724:30602487
89544117:30613380
showlangstatbar:30737416
0bi6i642:30835152
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
copilotsettingc:30834057
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30829745

Thank you for filing this bug- I will get to this right away!

Thank you very much!


⚠ Bofrost.lu has degraded performance

In 8daa01f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1372 ms

Resolved: Bofrost.lu performance has improved in 3a9b903 after 18 minutes.


Allow ELASTIC_APM_ENVIRONMENT in config

Fixes #161
Other config values were correctly looking for APM_ first, then checking ELASTIC_APM_. The environment configuration was missed.

Thanks @arkaitzgarro. Would you consider making a new release? That would help us so we don't have to change our deployment configuration.

Yes, I will create a release right away.


[Bug]: Flink fails with "cannot handle nodes with more than 64 outputs"

What happened?
I am using Tensorflow Transform with Flink as the Beam runner, and the versions I am using are Beam 2.48.0 and Flink 1.16.2. After adding too many features, the Flink job cannot be submitted due to the exception
org.apache.flink.optimizer.CompilerException: Cannot currently handle nodes with more than 64 outputs

This is coming from this line: https://github.com/apache/flink/blob/fb4d4ef57439cd7fde4fb5a4972733d13e69a226/flink-optimizer/src/main/java/org/apache/flink/optimizer/dag/OptimizerNode.java#L356
I am not entirely sure whether it is the responsibility of Beam or Tensorflow Transform to fix this, but at a glance it seems like something that should be fixed within Beam by not adding more than 64 outgoing connections and instead handling this case in some other way.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[X] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

I am also facing the same issue, do we have any fix for this?


Question on building a chart

Hi ! I have a question, is it possible to make three graphs with one OX axis?

Hi @Tonypz, thanks for opening this issue!
It is not possible, but it is really easy to create three charts with the same configuration and then hide the first two x axes with CSS.
It would be something like:
let barChart = bar(),
        barContainer1 = d3Selection.select('.js-bar-chart-container-1'),
        barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
        barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
        containerWidth = barContainer.node() ? barContainer.node().getBoundingClientRect().width : false;

    if (containerWidth) {

        barChart
            .width(containerWidth)
            .hasPercentage(true)
            .enableLabels(true)
            .labelsNumberFormat('.0%')
            .height(300);

        barContainer1.datum(dataset1).call(barChart);
        barContainer2.datum(dataset2).call(barChart);
        barContainer3.datum(dataset3).call(barChart);
    }

Then, use CSS to display:none; the first two x-axis ticks. Maybe you need to adjust the margins though.
Let me know if that works for you!

Hi @Tonypz, thanks for opening this issue!
It is not possible, but it is really easy to create three charts with the same configuration and then hide the first two x axes with CSS.
It would be something like:
let barChart = bar(),
        barContainer1 = d3Selection.select('.js-bar-chart-container-1'),
        barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
        barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
        containerWidth = barContainer.node() ? barContainer.node().getBoundingClientRect().width : false;

    if (containerWidth) {

        barChart
            .width(containerWidth)
            .hasPercentage(true)
            .enableLabels(true)
            .labelsNumberFormat('.0%')
            .height(300);

        barContainer1.datum(dataset1).call(barChart);
        barContainer2.datum(dataset2).call(barChart);
        barContainer3.datum(dataset3).call(barChart);
    }

Then, use CSS to display:none; the first two x-axis ticks. Maybe you need to adjust the margins though.
Let me know if that works for you!
@Golodhros
Thank you very much for the quick reply, I will try

Thank you very much for the quick reply, I will try
вт, 5 мая 2020 г. в 18:39, Marcos Iglesias<EMAIL_ADDRESS>
Hi @Tonypz https://github.com/Tonypz, thanks for opening this issue!
It is not possible, but it is really easy to create three charts with the
same configuration and then hide the first two x axes with CSS.
It would be something like:
let barChart = bar(),
barContainer1 = d3Selection.select('.js-bar-chart-container-1'),
barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
barContainer2 = d3Selection.select('.js-bar-chart-container-2'),
containerWidth = barContainer.node() ? barContainer.node().getBoundingClientRect().width : false;
if (containerWidth) {

    barChart
        .width(containerWidth)
        .hasPercentage(true)
        .enableLabels(true)
        .labelsNumberFormat('.0%')
        .height(300);

    barContainer1.datum(dataset1).call(barChart);
    barContainer2.datum(dataset2).call(barChart);
    barContainer3.datum(dataset3).call(barChart);
}

Then, use CSS to display:none; the first two x-axis ticks. Maybe you need
to adjust the margins though.
Let me know if that works for you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/britecharts/britecharts/issues/812#issuecomment-624131073,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQX6UCZL6PMCHV23KC3DRTRQAXL7ANCNFSM4MZTV4OA
.

--
С уважением, Подколзин А.С.
Контактный телефон: +7(926)-734-01-98

if display: none . @Golodhros  How remove the gap ?

Hi @Tonypz,
You will need to adjust the margins. Maybe you want to start with the bottom one, with regular margins, and then adjust the margins for the top two. I would start with top and bottom 0 and take it from there.

I tried to do according to your advice, but in the DOM only this line is
drawn userActionContainer.datum (a) .call (this.userChartMain);
[image: image.png]
[image: image.png]
__drawUserChart() {
this.userChartMain = new StepChart();
const userContainerMain = d3Graphics.d3.select('.js-user-main');
    const userErrorContainer = d3Graphics.d3.select('.js-user-errors');
    const userCountContainer = d3Graphics.d3.select('.js-user-count');
    const userActionContainer = d3Graphics.d3.select('.js-user-actions'

);
    const a = this.__parseUser({ data: this.data, type: 'action' });
    const b = this.__parseUser({ data: this.data, type: 'count' });
    const c = this.__parseUser({ data: this.data, type: 'error' });

    const containerWidth = userContainerMain.node() ? userContainerMain.

node().getBoundingClientRect().width : false;
if (userContainerMain) {
this.userChartMain
.width(containerWidth)
.height(900)
.xAxisLabel('Date')
.xAxisLabelOffset(10)
.yAxisLabel('Errors')
.yAxisLabelOffset(-45)
.margin({
top: 100,
right: 150,
bottom: 170,
left: 150
});
userActionContainer.datum(a).call(this.userChartMain);
userCountContainer.datum(b).call(this.userChartMain);
userErrorContainer.datum(c).call(this.userChartMain);
}
},
ср, 6 мая 2020 г. в 17:23, Marcos Iglesias<EMAIL_ADDRESS>
Hi @Tonypz https://github.com/Tonypz,
You will need to adjust the margins. Maybe you want to start with the
bottom one, with regular margins, and then adjust the margins for the top
two. I would start with top and bottom 0 and take it from there.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/britecharts/britecharts/issues/812#issuecomment-624672755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQX6UFEUBIDSZTAOL2NSKLRQFXELANCNFSM4MZTV4OA
.

--
С уважением, Подколзин А.С.
Контактный телефон: +7(926)-734-01-98

Oh, it seems the images didn't upload properly.
It would be a lot easier for me to help you if you could recreate this on a Codepen. You could use this one https://codepen.io/Britecharts/pen/yEwpeg as a jumpstart.

I think this is already solved, right?