langgraph up with syntax errors creates dangling Docker images (and eats up available disk)

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangGraph/LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangGraph/LangChain rather than my code.
[X] I am sure this is better as an issue rather than a GitHub discussion, since this is a LangGraph bug and not a design question.

Example Code
from typing import Any, Dict, List, Optional
from pydantic import BaseModel
from langgraph.graph import StateGraph, START, END

class State(BaseModel):
    string_default: Optional[str] = None
    int_default: Optional[int] = None
    float_default: Optional[float] = None
    dict_default: Optional[Dict[str, Any]] = None
    list_default: Optional[List[str]] = None

def node(state: State):
    return {
        'string_default': state.string_default,
        'int_default': state.int_default,
        'float_default': state.float_default,
        'dict_default': state.dict_default,
        'list_default': state.list_default,
    }

graph_builder = StateGraph(State)
graph_builder.add_node("default", node)
graph_builder.add_edge(START, "syntax_error")
graph_builder.add_edge("default", END)

graph = graph_builder.compile()

Error Message and Stack Trace (if applicable)
Doing this enough times will result in Docker errors like:

failed to solve: failed to copy files: userspace copy failed: write /var/lib/docker/overlay2/f89z6c11ya4bjzmal3lonj3tk/merged/deps/[repo]/.env.dev: no space left on device

Description
Initial state
> docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          0         0         0B        0B
Containers      0         0         0B        0B
Local Volumes   0         0         0B        0B
Build Cache     0         0         0B        0B

Amend graph code to have one syntax error and langgraph up
> docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          3         2         1.042GB   257.3MB (24%)
Containers      2         0         5.002MB   5.002MB (100%)
Local Volumes   1         1         40.85MB   0B (0%)
Build Cache     21        0         98.84MB   98.84MB

Amend graph code to have a different syntax error and langgraph
> docker system df
docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          4         2         1.143GB   685.5MB (59%)
Containers      2         0         5.002MB   5.002MB (100%)
Local Volumes   1         1         40.85MB   0B (0%)
Build Cache     25        0         98.84MB   98.84MB

Doing a verbose df reveals that dangling images are not being cleaned up:
docker system df --verbose
 Images space usage:

REPOSITORY                        TAG       IMAGE ID       CREATED         SIZE      SHARED SIZE   UNIQUE SIZE   CONTAINERS
ewalker-langgraph-langgraph-api   latest    ad138f07385a   4 minutes ago   686MB     584.1MB       101.4MB       1
<none>                            <none>    bfe00bd0a94c   4 minutes ago   686MB     584.1MB       101.4MB       0
<none>                            <none>    46d4c46c4981   6 minutes ago   686MB     584.1MB       101.4MB       0
langchain/langgraph-api           3.11      799a89355392   17 hours ago    257MB     257.3MB       0B            0
postgres                          16        35042a754d27   6 days ago      453MB     97.11MB       356.3MB       1
...

System Info
System Information

OS:  Darwin
OS Version:  Darwin Kernel Version 23.5.0: Wed May  1 20:17:33 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6031
Python Version:  3.12.3 (main, May 28 2024, 11:22:04) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]

Package Information

langchain_core: 0.2.28
langchain: 0.2.12
langchain_community: 0.2.11
langsmith: 0.1.96
langchain_anthropic: 0.1.22
langchain_openai: 0.1.20
langchain_text_splitters: 0.2.2
langgraph: 0.2.2

Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langserve

@ewalker11 this issue should be fixed -- please let me know if you're still running into it

hi @ewalker11  can you run this code standalone
I think the default node is unreachable here also syntax_error node is defined anywhere


Adding a lot of Beej's Guides and their official translations.

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
Adding a lot of Beej's Guides and their official translations.
Why is this valuable (or not)?
Really valuable books.
How do we know it's really free?
As mentioned on the official website.
For book lists, is it a book? For course lists, is it a course? etc.
Books.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

Overdue additions!
Please add author names where appropriate. (Maybe not needed where "Beej" is already in the title, consider adding translator name - your decision; I would generally add it if its on the title page.)

Is this a good way to add the translator name?
@eshellman

Socket Programmierung in C - Translated by Tobias Kerst (HTML)

Is this a good way to add the translator name?
@eshellman

Socket Programmierung in C - Translated by Tobias Kerst (HTML)

I have made the changes according to the above format. I won't push those changes until you confirm.
Suggestions are welcome.

your format for translator looks fine; the author should be added to the german entry
Socket Programmierung in C - B. Hall, translated by Tobias Kerst (HTML)

I'll add authors and translators both as per the above format on all entries.

@eshellman I think this completes the work on this PR.
Lemme know of any other requested changes.


Suggestion: Swift Hex Mythic ability?

since classes with access to domains can get access to domain zealot to make their powerful domain abilities swift actions why not give witches an equivalent ability to improve their action economy? no clue about a good name for it tho

Yeah, why not.

an alternative would be to make chanting/cackling become swift instead of hexes themselves

I added the feature swift hex. Ingame name Cursing Gaze. I left out grant hexes. Since cackle is also a hex, it's probably affected too. Maybe I should exclude it? Let me know, if the feature works as intended or if there are bugs.


016 National bibliographic agency control number

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/0XX.csv

@CECSpecialistI @sarahruska @corialanus  I looked at what appears to be a decision not to map 010 - LC Control Number.  Unless we want to revisit this I would like to apply the same decision to this tag which is for control numbers from other national bibliographic agencies than LC.  This data doesn't apply to an RDA entity derived from the content of the record.
It would not be mapped, unless we want to treat the MARC record as a metadata work, to be described and associated with an RDA/RDF data set, or something like this - right?  That's not currently planned (at least for this phase), right?
If you agree.  can someone record the decision not to map both 010 and 016 in the Decisions Index?

Hi @lake44me - could you share where you found the decision not to map? I was trying to familiarize myself with it but haven't found it. I was able to find that 010 is signed out to @corialanus (meeting notes), a discussion on identifiers, and another on MARC21 Breadcrumbs in LRM/RDA/RDF Output that I think is saying to use 010, but I definitely could be missing/misunderstanding the decision!

Hi @sarahruska
To my chagrin, I am not able to find it today.  Maybe I was hallucinating!  I don't think so, but in any case,
It's worth taking a second look.  What is the LCCN an identifier for?  I think it's for a MARC record.  How do we relate that to an RDA entity?
Mint an IRI for the MARC record as a metadata work and relate it to the manifestation?  http://rdaregistry.info/Elements/w/P10617
Give the LCCN as:  the appellation or title of the metadata work?  (if not, what do we use?)
Give the LCCN as :  identifier for the work?
What other properties should we have?
@coriolanus, would you like to take 016 since you have 010 and they're so similar?
Sorry folks, I just have bitten off some rattlesnakes and am having a hard time chewing them all...


[27.x] Fix for WFLY-17285, Upgrade Bootable JAR to 8.1.0.Final

Issue: https://issues.redhat.com/browse/WFLY-17285

Thanks @jfdenise


VIM Toggle function error in X11

Using vim in an xterm on OSX:
Hitting F5 generates this error:
Error detected while processing function 15_TogBG:
line    1:
E121: Undefined variable: g:colors_name
E15: Invalid expression: "colorscheme " . g:colors_name
Press ENTER or type command to continue
The F5 toggle works fine in macvim and AppleTerminal.app.
Using:
commit 4727d3afd6ac9278e4e5dcee6762ed8bb3501eef
Date:   Sun Apr 10 00:10:24 2011 -0700

I have the same issue when I set g:solarized_termcolors=256
g:colors_name does not exist after the first toggle..
Otherwise it works fine.
I'm using Terminator on Linux Mint 12 (Had the same problem on ubuntu 11.10).

This still doesn't work in anything but  MacVim, and even there you have to call togglebg#map("F5") to get it to load.  Tested with vim 8.0.134 on iTerm2 (build 3.0.12), Terminal (2.5.3), XQuartz 2.7.11 (xorg-server 1.18.4), and MacVim 8.0.119


Is it possible to remove the transformations?

I'd like to use this program without flipping the Y axis and without changing  the X axis.
My SVG file's points are in the same units as my plotter..
<svg>
<path d="M10,10 L 25,25"

I want to send to the plotter
G01 X10 Y10
G01 X25 y25

I believe the dpi setting is throwing off my X axis I can't pass a float (25.4) as a parameter. Also the Y axis is flipped upside down.
I'm hoping that you could provide (or help me to add a --as-is parameter so as to not adjust the points prior to plotting them.
I found your program trying to find a way to convert a bezier curve into a series of G2 and G3 (arcs) I have not found a way to do this.
Thanks

In theory we could add a flag, but it does not feel good tbh. These transformations implement the correct SVG semantics, your SVG is non standard 😉 How did you end up with this SVG? Also, would it no be easier for you to produce in a natural way?

Thank you for the response.
Actually where I'm stuck in my own effort is to convert a bezier curve to a series of arcs (the plotter tool speaks G2 & G3 but not G5).  I found some python code buried in inkscape and also you're program. I'm writing this all in node but really this is more of a math/how-to question.
If you are interested, I'm writing a tool for a children's school that will help users to "write" with software. There's a ton of unusual customizations throughout this process.
I was able to change your code removing the Y transformation and changing the dpi from 2.45  to a hard-coded 1. I'm still getting slightly different numbers out (not sure why) but I think I can adjust for this. -- I'll close the ticket.
Thanks

I see. Have you seen this? https://github.com/domoszlai/bezier2biarc
The bezier to G2/G3 conversion is pretty hard, this was a POC much easier to understand, also there is some visualisation
Also, a brief explanation of the algorthm: https://dlacko.org/blog/2016/10/19/approximating-bezier-curves-by-biarcs/


Replace VIP, origin name, and clientName with a composite object.

The top level idea here is to make the VIP, Origin Name, NIWS Client name, and app name a single struct, which is passed around throughout or pooling code.  Additionally, we need to get away from verbiage and idioms that come from dependencies  such as NIWS, Eureka, and Ribbon.
High level changes:

Replace String forms of origin name, client name, and vip with a composite OriginName class.   This class is the primary key of an origin.
VIP is renamed to Target.  A Target is something to be used for looking up servers to connect to.
the VIP Prefix, origin name, and client name are now renamed to niwsClientName.   It is used to define IClientConfig values, as well as for use in Fast properties.
The niwsClientName is also normalized into a metric ID, usable for Atlas metrics.
useFullVip (and variants) have been un-wired through out code, and only have an effect when building the OriginName.

Minor note: the App name, trusted-ness, and origin equality haven't really been fleshed out.  They will likely be changed as this code is integrated into internal Zuul.    I have audited internal Zuul enough  that I am confident these changes can be made internally without excess effort.

There's a lot here, but generally LGTM. I like the direction.


Implementation of an optionally activatable process that can detect weak passwords

The Free/Libre Open Source Software (FLOSS) Nextcloud has implemented a functionality that detects (very) weak passwords and informs the users that the chosen password would be easily crackable.
The same functionality with a hint to use a (FLOSS) password manager could be useful to implement under certain circumstances.

Stick to the issue template.
Seems to be pretty easy and should be client only.
user-detail-component and password-component would require a service to check the (new) password before saving the request.


add eslint-plugin-graphql

https://github.com/apollographql/eslint-plugin-graphql

We use the @kiwicom/eslint-config as common the eslint's setting across the company.


Add the ability to use "time" as "times" alias

resolves https://github.com/rspec/rspec-mocks/issues/1269

I don't know if I did the right thing for the documentation
Do we need that number of tests?
Do we need to run https://github.com/rspec/rspec-mocks/blob/master/Rakefile#L42-L61 after merge?

Cheers

Looks good to merge, happy for you to merge and do a change log :+1:

Thanks @JonRowe


TD Framework Update

This provides a refactoring of the Tonti Diagram backend to allow for non-elementwise transitions (allowing for more complex transitions like the Laplacian and Lie derivatives. This also includes examples of simple CFD physics expressed with this API.

Just realized I made this PR with my wrong github account, will be remaking this with the appropriate account.


How long does it take to train this model?

It's a good work! I would like to know how long it will take to train this model.

Thanks. Under current implementation, it takes about 48 hrs to train on the LAION-OCR dataset (batchsize=64, iters=100k, gpu=NVIDIA A40)

Thanks. Under current implementation, it takes about 48 hrs to train on the LAION-OCR dataset (batchsize=64, iters=100k, gpu=NVIDIA A40)

Thanks for your reply！ How many GPUs are needed for 48h training?

I used 8*A40


Doesn't seem to work with  element

I'm trying to detect  element size changes. addResizeListener for  doesn't seem to work. Any thoughts how to make it working or at least why it's not working?

@kopach Is it working when listening to a wrapping block of a <video> element ?

@malikba, I haven't tested this, but don't think there should be any problem with this.
But, what I was needed is to recognize resizing of <video> element and not it's wrapper.
But, the problem with the <video> element is that you cannot put element inside it and detect events. Everything inside <video> tag is ignored by browser (except <source>, I guess, which is not really helpful in this case).
So, maybe, there is another solution for this.


Immediately unpair sensors with bad MAC and log

It should be possible to detect when a sensor tries to pair with a bad MAC address and automatically remove it, rather than forcing a manual remove later. In order to be useful, this would need to log the failure so that it would be obvious why the pairing failed.

This branch of HA-WyzeSense includes doing an auto unpair. Something similar could be done here, but at the higher level rather than the underlying library to avoid additional library fragmentation in WyzeSensePy.
https://github.com/kevinvincent/ha-wyzesense/compare/photinusdev


Indicate parameters on modern-root-site.md

Indicate parameters of the PowerShell to indicate which parameter used in the command

[x] Update content

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@esjimenezp Please correct changes suggested.

@esjimenezp Hi Eduardo, following up on this. Could you please make the changes that are being asked for? Thanks!

@esjimenezp Hi Eduardo, following up on this. Could you please make the changes that are being asked for? Thanks!

@MikePlumleyMSFT Hello! Wondering if this change is necessary. The submitter has not responded. I can have a freelancer look at this.

@kaarins?


Ampersand (&) is no longer converted to & in link tags

I am upgrading Nokogiri to version 1.13.x and hitting a possible bug where an ampersand (&) in the URL is not treated as ampersand.
The code:
require 'nokogiri'
doc = Nokogiri::XML::Builder.new(encoding: 'UTF-8') do |xml|
  xml.root do
     xml.string({}) {
        xml << "ss sss ss"
     }
  end
end
puts doc.to_xml

Nokogiri before 1.13.0 (notice it accepted both & and &):
<?xml version="1.0" encoding="UTF-8"?>
<root>
    <string>ss sss ss</string>
</root>

Nokogiri after 1.13.0 (notice the single &  disappeared together with the "bar" key just after):
<?xml version="1.0" encoding="UTF-8"?>
<root>
  <string>ss sss ss</string>
</root>

Looks like &bar got treated as an escape sign but with no value so it disappeared.
Here's the script again:
#! /usr/bin/env ruby

require 'nokogiri'
doc = Nokogiri::XML::Builder.new(encoding: 'UTF-8') do |xml|
  xml.root do
      xml.string({}) {
        xml << "ss sss ss"
      }
  end
end
puts doc.to_xml

Expected behavior
I would expect the old behaviour where the  & sign in URL gets transformed to &. Not sure if this is wrong, but that's what I would expect.
Environment
$ nokogiri -v
# Nokogiri (1.13.3)
    ---
    warnings: []
    nokogiri:
      version: 1.13.3
      cppflags:
      - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.3-x86_64-linux/ext/nokogiri"
      - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.3-x86_64-linux/ext/nokogiri/include"
      - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.3-x86_64-linux/ext/nokogiri/include/libxml2"
      ldflags: []
    ruby:
      version: 3.0.3
      platform: x86_64-linux
      gem_platform: x86_64-linux
      description: ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-linux]
      engine: ruby
    libxml:
      source: packaged
      precompiled: true
      patches:
      - 0001-Remove-script-macro-support.patch
      - 0002-Update-entities-to-remove-handling-of-ssi.patch
      - 0003-libxml2.la-is-in-top_builddir.patch
      - 0004-use-glibc-strlen.patch
      - 0005-avoid-isnan-isinf.patch
      - 0006-update-automake-files-for-arm64.patch
      - '0008-htmlParseComment-handle-abruptly-closed-comments.patch'
      - '0009-allow-wildcard-namespaces.patch'
      - 0010-Revert-Different-approach-to-fix-quadratic-behavior.patch
      libxml2_path: "/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.3-x86_64-linux/ext/nokogiri"
      memory_management: ruby
      iconv_enabled: true
      compiled: 2.9.13
      loaded: 2.9.13
    libxslt:
      source: packaged
      precompiled: true
      patches:
      - 0001-update-automake-files-for-arm64.patch
      datetime_enabled: true
      compiled: 1.1.35
      loaded: 1.1.35
    other_libraries:
      zlib: 1.2.11
      libgumbo: 1.0.0-nokogiri

Note I tested 1.13.0 as well, which is the version where this behaviour was likely introduced.

Okay so it's not just about URLs, it's about ampersand in general.
Here's another example:
require 'nokogiri'
doc = Nokogiri::XML::Builder.new(encoding: 'UTF-8') do |xml|
  xml.root do
      xml.string({}) {
        xml << "bar & bar"
      }
  end
end
puts doc.to_xml

and on Nokogiri > 1.13.0 the result escapes it:
<?xml version="1.0" encoding="UTF-8"?>
<root>
  <string>bar  bar</string>
</root>

I'm not an expert on XML, but isn't
xml << "bar & bar"

invalid because the right hand side is supposed to be a raw XML string but it has the & in it.

@strzibny For your second example, you should use the text method.
require 'nokogiri'
doc = Nokogiri::XML::Builder.new(encoding: 'UTF-8') do |xml|
  xml.root do
      xml.string {
        xml.text("bar & bar")
      }
  end
end
puts doc.to_xml

For your first example, you'll either need to provide valid XML on the right hand side of << (as I suspected, your XML is invalid) or you'll need to use the builder API to construct the anchor.

Sorry for my slow reply, I was on vacation for a bit last week.
Summary
I'll spend a bit of time today bisecting libxml2 just to make sure I understand when this behavior changed, but right now I think that attribute entity is handled consistently and correctly; and the dropped bare ampersand in a text node is a duplicate of #2267 which was reported upstream at https://gitlab.gnome.org/GNOME/libxml2/-/issues/270 and is still unresolved.
Details
I'm going to unify the two things being reported, simplify by using the DOM parser (not the Builder) and demonstrate how the parsers behave in the XML, HTML4, and HTML5 parsers, along with any parsing errors encountered:
#! /usr/bin/env ruby

require 'nokogiri'

html = <<~HTML

   foo & bar

HTML

document = Nokogiri::XML::Document.parse(html)
puts document.to_xml
pp document.errors

puts "----------"

document = Nokogiri::HTML4::Document.parse(html)
puts document.to_html
pp document.errors

puts "----------"

if defined?(Nokogiri::HTML5)
  document = Nokogiri::HTML5::Document.parse(html)
  puts document.to_html
  pp document.errors
end

outputs:
<?xml version="1.0"?>

   foo  bar

[#<Nokogiri::XML::SyntaxError: 2:46: FATAL: EntityRef: expecting ';'>,
 #<Nokogiri::XML::SyntaxError: 2:71: FATAL: xmlParseEntityRef: no name>]
----------
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

   foo & bar

[#<Nokogiri::XML::SyntaxError: 2:46: ERROR: htmlParseEntityRef: expecting ';'>,
 #<Nokogiri::XML::SyntaxError: 2:71: ERROR: htmlParseEntityRef: no name>]
----------

   foo & bar

[]

and on JRuby (to check consistency against the Xerces and NekoHTML parsers):
<?xml version="1.0"?>

[#<Nokogiri::XML::SyntaxError: The reference to entity "bar" must end with the ';' delimiter.>,
 #<Nokogiri::XML::SyntaxError: The reference to entity "bar" must end with the ';' delimiter.>]
----------

   foo & bar

[#<Nokogiri::XML::SyntaxError: Bare ampersand found.>,
 #<Nokogiri::XML::SyntaxError: Unknown general entity "bar".>,
 #<Nokogiri::XML::SyntaxError: Bare ampersand found.>]
----------

Note that all of these parsers are consistent in flagging the use of a bare ampersand as a parsing error, and although the XML parsers recover differently, all of the HTML parsers recover consistently.
@strzibny Are you intentionally using XML::Builder for what looks like HTML content? Just curious, the behavior of libxml2's HTML parser is consistent, but I did want to suggest that you can avoid the second issue being reported (dropping the bare & in a text node) by using an HTML4 or HTML5 parser.

@strzibny Can you tell me what version of Nokogiri you're upgrading from? I went back to libxml2 2.9.10 (Nokogiri v1.11.3) and the behavior of the parser to replace bare ampersands in the href attribute hadn't changed since then.

Thanks a lot for all the answers, as I said I wasn't sure if this is an actual bug, just that it surprised me. After thinking more about it, I believe I simply have to escape ampersand in cases when this previously work.
@flavorjones I was upgrading from 1.12.5 to 1.13.0 (and then 1.13.3) both on libxml2-2.9.13-1.fc35.x86_64.
Although I am still interested what change caused this, I am closing the issue as this is regarding invalid XML.

@strzibny I'm not able to reproduce what you're reporting using stock libxml2 2.9.13 and Nokogiri 1.12.5. Here's the script I'm using (note that I try both XML DOM parser and the XML Builder):
#! /usr/bin/env ruby

require 'nokogiri'
require 'yaml'

puts Nokogiri::VERSION_INFO.to_yaml

html = <<~HTML

   foo & bar

HTML

document = Nokogiri::XML::Document.parse(html)
puts document.to_xml
pp document.errors

puts "=========="

doc = Nokogiri::XML::Builder.new(encoding: 'UTF-8') do |xml|
  xml.root do
     xml.string({}) {
        xml << "ss sss ss"
     }
  end
end
puts doc.to_xml
pp doc.doc.errors

Here's what I see:
---
warnings: []
nokogiri:
  version: 1.12.5
  cppflags:
  - "-I/home/flavorjones/code/oss/nokogiri/ext/nokogiri"
  ldflags: []
ruby:
  version: 3.1.0
  platform: x86_64-linux
  gem_platform: x86_64-linux
  description: ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [x86_64-linux]
  engine: ruby
libxml:
  source: system
  memory_management: ruby
  iconv_enabled: true
  compiled: 2.9.13
  loaded: 2.9.13
libxslt:
  source: system
  datetime_enabled: true
  compiled: 1.1.34
  loaded: 1.1.34
other_libraries:
  libgumbo: 1.0.0-nokogiri
<?xml version="1.0"?>

   foo  bar

[#<Nokogiri::XML::SyntaxError: 2:46: FATAL: EntityRef: expecting ';'>,
 #<Nokogiri::XML::SyntaxError: 2:71: FATAL: xmlParseEntityRef: no name>]
==========
<?xml version="1.0" encoding="UTF-8"?>
<root>
  <string>ss sss ss</string>
</root>
[#<Nokogiri::XML::SyntaxError: 1:47: FATAL: EntityRef: expecting ';'>]

@flavorjones Yet I see it there:

   foo  bar

Notice the missing &.

@strzibny I run your script in both versions. The old version looks same like yours. The new one:
---
warnings: []
nokogiri:
  version: 1.13.0
  cppflags:
  - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.0-x86_64-linux/ext/nokogiri"
  - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.0-x86_64-linux/ext/nokogiri/include"
  - "-I/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.0-x86_64-linux/ext/nokogiri/include/libxml2"
  ldflags: []
ruby:
  version: 3.0.3
  platform: x86_64-linux
  gem_platform: x86_64-linux
  description: ruby 3.0.3p157 (2021-11-24 revision 3fb7d2cadc) [x86_64-linux]
  engine: ruby
libxml:
  source: packaged
  precompiled: true
  patches:
  - 0001-Remove-script-macro-support.patch
  - 0002-Update-entities-to-remove-handling-of-ssi.patch
  - 0003-libxml2.la-is-in-top_builddir.patch
  - 0004-use-glibc-strlen.patch
  - 0005-avoid-isnan-isinf.patch
  - 0006-update-automake-files-for-arm64.patch
  - 0007-Fix-XPath-recursion-limit.patch
  - '0008-htmlParseComment-handle-abruptly-closed-comments.patch'
  - '0009-allow-wildcard-namespaces.patch'
  libxml2_path: "/home/strzibny/.gem/ruby/3.0.3/gems/nokogiri-1.13.0-x86_64-linux/ext/nokogiri"
  memory_management: ruby
  iconv_enabled: true
  compiled: 2.9.12
  loaded: 2.9.12
libxslt:
  source: packaged
  precompiled: true
  patches:
  - 0001-update-automake-files-for-arm64.patch
  - 0002-Fix-xml2-config-check-in-configure-script.patch
  datetime_enabled: true
  compiled: 1.1.34
  loaded: 1.1.34
other_libraries:
  zlib: 1.2.11
  libgumbo: 1.0.0-nokogiri
<?xml version="1.0"?>

   foo  bar

[#<Nokogiri::XML::SyntaxError: 2:46: FATAL: EntityRef: expecting ';'>,
 #<Nokogiri::XML::SyntaxError: 2:71: FATAL: xmlParseEntityRef: no name>]
==========
<?xml version="1.0" encoding="UTF-8"?>
<root>
  <string>ss sss ss</string>
</root>
[#<Nokogiri::XML::SyntaxError: 1:47: FATAL: EntityRef: expecting ';'>]

Yes, but just after that I mentioned the result for 1.13.0. The whole issue is simply about the change from < 1.13.0 to >=1.13.0.

I am sorry if I made it confusing somehow.


In the subscriber & publisher SDK's, we get a generic error like this: com.ably.tracking.BuilderConfigurationIncompleteException: Some of the required builder parameters are missing. It would be useful for users to know which parameters are missing.

+1, I wanted to report the same issue, but not only for the notification. In the subscriber SDK, we get a generic error like this: {{com.ably.tracking.BuilderConfigurationIncompleteException: Some of the required builder parameters are missing}}. It would be useful for users to know which parameters are missing.
Originally posted by @ikurek in https://github.com/ably/ably-asset-tracking-android/issues/672#issuecomment-1143324167

The corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2650


Initialize window.getRandomValues()

If window is defined, ensure window.getRandomValues() is also defined (use react-native-randombytes to generate the underlying random data). Also fixes a bug from the original getRandomValues() shim function, which would leave some bytes uninitialized if the passed Typed Array was not Uint8.

for the updated browserify-sign algos, we'll need<EMAIL_ADDRESS>as 4.0.0 doesn't have exports.sha256

Ok, weird, when I look at this commit it looks like 4.0.0 is when they added exports.sha256: https://github.com/crypto-browserify/browserify-sign/commit/b48ffff8a22f04c30f09afdd5ac84918b1a07b27
No harm in bumping the requirement to 4.0.4 though, let me add that.

you should move the getRandomValues definition up, because some of the imports depend on randomBytes/getRandomValues somewhere in their dep trees (e.g. diffie-hellman->miller-rabin->brorand->window.getRandomValues)

Ok, done.

any reason why not have it at the very top?

i mean maybe change the import react-native-randombytes to require and have the getRandomValues definition first?

merged, thanks!

Cool!


feat(fsapp): FS-2511 expose hydrate RNW config option

I spoke with the team this is intended for and they're migrating to FS 10 soon so we don't need this.


Use fugit for timing

This is needed to work with: https://github.com/BlackbirdHQ/ublox-cellular-rs/pull/54 where embedded-time is replaced by fugit.

Could you run rustfmt?
Otherwise this looks great! Thank you very much!


Could not load kubeconfig file /var/lib/kubelet/kubeconfig when using vagrant to provision single node

Hi,
I try to provision single node according this guild . When executing the kubectl get nodes, I got that error:The connection to the server <IP_ADDRESS>:443 was refused - did you specify the right host or port?.
using MacOS 10.11.4,  Virtualbox 5.0.16r105874 and vagrant 1.7.4
I use the journalctl -u kubelet command to inspect and got the following logs. It seems that kubeconfig can't be found during starting the kubelet.
Apr 10 07:50:18 localhost kubelet-wrapper[1310]: Quay.io ACI Converter (ACI conversion signing key<EMAIL_ADDRESS>Apr 10 07:50:18 localhost kubelet-wrapper[1310]: Trusting "https://quay.io/aci-signing-key" for prefix "quay.io/coreos/hyperkube" without fingerprint review.
Apr 10 07:50:18 localhost kubelet-wrapper[1310]: Added key for prefix "quay.io/coreos/hyperkube" at "/etc/rkt/trustedkeys/prefix.d/quay.io/coreos/hyperkube/bff313cdaa560b16a8987b8f72abf5f6799d33bc"
Apr 10 07:50:18 localhost kubelet-wrapper[1310]: image: downloading signature from https://quay.io/c1/aci/quay.io/coreos/hyperkube/v1.2.0_coreos.1/aci.asc/linux/amd64/
Apr 10 07:50:18 localhost kubelet-wrapper[1310]: Downloading signature:  0 B/473 B
Apr 10 07:50:18 localhost kubelet-wrapper[1310]: Downloading signature:  473 B/473 B
Apr 10 07:50:20 localhost kubelet-wrapper[1310]: Downloading ACI:  0 B/87.7 MB
Apr 10 07:50:20 localhost kubelet-wrapper[1310]: Downloading ACI:  16.4 KB/87.7 MB
Apr 10 07:50:21 localhost kubelet-wrapper[1310]: Downloading ACI:  277 KB/87.7 MB
Apr 10 07:50:22 localhost kubelet-wrapper[1310]: Downloading ACI:  1.06 MB/87.7 MB
Apr 10 07:50:23 localhost kubelet-wrapper[1310]: Downloading ACI:  2.12 MB/87.7 MB
Apr 10 07:50:25 localhost kubelet-wrapper[1310]: Downloading ACI:  3.36 MB/87.7 MB
Apr 10 07:50:26 localhost kubelet-wrapper[1310]: Downloading ACI:  4.61 MB/87.7 MB
Apr 10 07:50:27 localhost kubelet-wrapper[1310]: Downloading ACI:  5.85 MB/87.7 MB
Apr 10 07:50:28 localhost kubelet-wrapper[1310]: Downloading ACI:  7.12 MB/87.7 MB
Apr 10 07:50:29 localhost kubelet-wrapper[1310]: Downloading ACI:  8.39 MB/87.7 MB
Apr 10 07:50:30 localhost kubelet-wrapper[1310]: Downloading ACI:  9.68 MB/87.7 MB
Apr 10 07:50:31 localhost kubelet-wrapper[1310]: Downloading ACI:  11 MB/87.7 MB
Apr 10 07:50:32 localhost kubelet-wrapper[1310]: Downloading ACI:  12.3 MB/87.7 MB
Apr 10 07:50:33 localhost kubelet-wrapper[1310]: Downloading ACI:  13.6 MB/87.7 MB
Apr 10 07:50:34 localhost kubelet-wrapper[1310]: Downloading ACI:  14.9 MB/87.7 MB
Apr 10 07:50:35 localhost kubelet-wrapper[1310]: Downloading ACI:  16.2 MB/87.7 MB
Apr 10 07:50:36 localhost kubelet-wrapper[1310]: Downloading ACI:  17.7 MB/87.7 MB
Apr 10 07:50:38 localhost kubelet-wrapper[1310]: Downloading ACI:  19.2 MB/87.7 MB
Apr 10 07:50:39 localhost kubelet-wrapper[1310]: Downloading ACI:  20.9 MB/87.7 MB
Apr 10 07:50:40 localhost kubelet-wrapper[1310]: Downloading ACI:  22.7 MB/87.7 MB
Apr 10 07:50:41 localhost kubelet-wrapper[1310]: Downloading ACI:  24.4 MB/87.7 MB
Apr 10 07:50:42 localhost kubelet-wrapper[1310]: Downloading ACI:  25.9 MB/87.7 MB
Apr 10 07:50:43 localhost kubelet-wrapper[1310]: Downloading ACI:  27.5 MB/87.7 MB
Apr 10 07:50:44 localhost kubelet-wrapper[1310]: Downloading ACI:  29.1 MB/87.7 MB
Apr 10 07:50:45 localhost kubelet-wrapper[1310]: Downloading ACI:  30.7 MB/87.7 MB
Apr 10 07:50:46 localhost kubelet-wrapper[1310]: Downloading ACI:  32.3 MB/87.7 MB
Apr 10 07:50:47 localhost kubelet-wrapper[1310]: Downloading ACI:  33.9 MB/87.7 MB
Apr 10 07:50:48 localhost kubelet-wrapper[1310]: Downloading ACI:  35.5 MB/87.7 MB
Apr 10 07:50:49 localhost kubelet-wrapper[1310]: Downloading ACI:  37.1 MB/87.7 MB
Apr 10 07:50:50 localhost kubelet-wrapper[1310]: Downloading ACI:  38.7 MB/87.7 MB
Apr 10 07:50:52 localhost kubelet-wrapper[1310]: Downloading ACI:  40.4 MB/87.7 MB
Apr 10 07:50:53 localhost kubelet-wrapper[1310]: Downloading ACI:  42.1 MB/87.7 MB
Apr 10 07:50:54 localhost kubelet-wrapper[1310]: Downloading ACI:  44.1 MB/87.7 MB
Apr 10 07:50:55 localhost kubelet-wrapper[1310]: Downloading ACI:  46.7 MB/87.7 MB
Apr 10 07:50:56 localhost kubelet-wrapper[1310]: Downloading ACI:  49.9 MB/87.7 MB
Apr 10 07:50:57 localhost kubelet-wrapper[1310]: Downloading ACI:  53.6 MB/87.7 MB
Apr 10 07:50:58 localhost kubelet-wrapper[1310]: Downloading ACI:  58 MB/87.7 MB
Apr 10 07:50:59 localhost kubelet-wrapper[1310]: Downloading ACI:  63 MB/87.7 MB
Apr 10 07:51:00 localhost kubelet-wrapper[1310]: Downloading ACI:  68.2 MB/87.7 MB
Apr 10 07:51:01 localhost kubelet-wrapper[1310]: Downloading ACI:  73.4 MB/87.7 MB
Apr 10 07:51:02 localhost kubelet-wrapper[1310]: Downloading ACI:  78.6 MB/87.7 MB
Apr 10 07:51:03 localhost kubelet-wrapper[1310]: Downloading ACI:  83.9 MB/87.7 MB
Apr 10 07:51:04 localhost kubelet-wrapper[1310]: Downloading ACI:  87.7 MB/87.7 MB
Apr 10 07:51:05 localhost kubelet-wrapper[1310]: image: signature verified:
Apr 10 07:51:05 localhost kubelet-wrapper[1310]: Quay.io ACI Converter (ACI conversion signing key<EMAIL_ADDRESS>Apr 10 07:51:25 localhost kubelet-wrapper[1310]: W0410 07:51:25.681627    1310 server.go:445] Could not load kubeconfig file /var/lib/kubelet/kubeconfig: stat /var/lib/kubelet/kubeconfig: no such file or directory. Trying auth path instead.
Apr 10 07:51:25 localhost kubelet-wrapper[1310]: W0410 07:51:25.682129    1310 server.go:406] Could not load kubernetes auth path /var/lib/kubelet/kubernetes_auth: stat /var/lib/kubelet/kubernetes_auth: no such file or directory. Continuing with defaults.
Apr 10 07:51:25 localhost kubelet-wrapper[1310]: I0410 07:51:25.682202    1310 plugins.go:71] No cloud provider specified.
Apr 10 07:51:25 localhost kubelet-wrapper[1310]: I0410 07:51:25.682639    1310 manager.go:132] cAdvisor running in container: "/system.slice/kubelet.service"
Apr 10 07:52:13 localhost kubelet-wrapper[1310]: I0410 07:52:13.926526    1310 fs.go:109] Filesystem partitions: map[/dev/sda9:{mountpoint:/var/lib/docker major:8 minor:9 fsType:ext4 blockSize:0} /dev/sda3:{mountpoint:/etc/ssl/certs major:8 minor:3 fsType: blockSize:0} ov
Apr 10 07:52:16 localhost kubelet-wrapper[1310]: I0410 07:52:16.684915    1310 manager.go:169] Machine: {NumCores:1 CpuFrequency:2294581 MemoryCapacity:1045590016 MachineID:c0bb99276bc74b86b88d83396764e3f7 SystemUUID:6E4687DC-F9AD-47EA-8CA3-2B4FD8DB4F86 BootID:44a5ed53-4e
Apr 10 07:52:16 localhost kubelet-wrapper[1310]: I0410 07:52:16.688227    1310 manager.go:175] Version: {KernelVersion:4.5.0-coreos-r1 ContainerOsVersion:Debian GNU/Linux 8 (jessie) DockerVersion:1.10.3 CadvisorVersion: CadvisorRevision:}
Apr 10 07:52:16 localhost kubelet-wrapper[1310]: I0410 07:52:16.692075    1310 server.go:673] Adding manifest file: /etc/kubernetes/manifests
Apr 10 07:52:16 localhost kubelet-wrapper[1310]: I0410 07:52:16.692106    1310 server.go:683] Watching apiserver

Do I miss some steps? I have redone this for several times, but always get this error.

@Leorowe if you docker ps, do you see the apiserver container running? Can you curl localhost:8080/api successfully while ssh'd into the vagrant vm?

Hi,
No, there is no any container was running and connection refused when curl localhost:8080/api

Same thing happens on the multi-node setup as well.

We recently encountered this as well. The instructions recommend exporting KUBECONFIG:
$ export KUBECONFIG="${KUBECONFIG}:$(pwd)/kubeconfig"

which I think is a recent change that seems to not actually work with kubectl. Our workaround is to unset KUBECONFIG. I don't know why it's necessary since (I think) the set-context calls record the config in ~/.kube/config for use by kubectl.

I'm able to get things working if I drop the vm box_version from '1029.0.0' to '1010.1.0'.

Hi,
Finally, I figured out this issue is caused by the network problem. Because of GFW in China, these images couldn't be downloaded. After setting proxy, everything work fine.

image: downloading signature from https://quay.io/c1/aci/quay.io/coreos/hyperkube/v1.2.0_coreos.1/aci.asc/linux/amd64/
Apr 30 11:10:44 localhost kubelet-wrapper[1205]: Downloading signature:  0 B/473 B
Apr 30 11:10:44 localhost kubelet-wrapper[1205]: Downloading signature:  473 B/473 B
Apr 30 11:11:15 localhost kubelet-wrapper[1205]: run: Get https://quay-registry.s3.amazonaws.com/sharedimages/bbf48108-4be9-43d0-8b3a-d02cdf16a459/layer?Signature=xYf%2BFBovmAG3PFWUqwP6XuPId8o%3D&Expires=1462014736&AWSAccessKeyId=AKIA
Apr 30 11:11:15 localhost systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
mage: using image from file /usr/share/rkt/stage1-fly.aci
Apr 30 11:11:25 localhost kubelet-wrapper[1311]: image: searching for app image quay.io/coreos/hyperkube
Apr 30 11:11:27 localhost kubelet-wrapper[1311]: image: remote fetching from URL "https://quay.io/c1/aci/quay.io/coreos/hyperkube/v1.2.0_coreos.1/aci/linux/amd64/"
Apr 30 11:11:27 localhost kubelet-wrapper[1311]: image: keys already exist for prefix "quay.io/coreos/hyperkube", not fetching again
Apr 30 11:11:27 localhost kubelet-wrapper[1311]: image: downloading signature from https://quay.io/c1/aci/quay.io/coreos/hyperkube/v1.2.0_coreos.1/aci.asc/linux/amd64/
Apr 30 11:11:28 localhost kubelet-wrapper[1311]: Downloading signature:  0 B/473 B
Apr 30 11:11:28 localhost kubelet-wrapper[1311]: Downloading signature:  473 B/473 B
Apr 30 11:11:59 localhost kubelet-wrapper[1311]: run: Get https://quay-registry.s3.amazonaws.com/sharedimages/bbf48108-4be9-43d0-8b3a-d02cdf16a459/layer?Signature=qjsqRILHR%2B9GM6kg2SPdlQwmWEU%3D&Expires=1462014779&AWSAccessKeyId=AKIA
Apr 30 11:11:59 localhost systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 11:11:59 localhost systemd[1]: kubelet.service: Unit entered failed state.
Apr 30 11:11:59 localhost systemd[1]: kubelet.service: Failed with result 'exit-code'.

@Leorowe, what, if any, changes did you have to make? I am still unable to make this work and have had to revert the Vagrantfile to use 1010.1.0.

Actually I just set the HTTP proxy. May be you should use journalctl -u kubelet to check whether these is any exception log?

I've got the same problem - tried destroying the vagrant setup and re-provisioning around 3 times on a bad/flaky connection, and ran into this every time. After the 230MB image was downloaded, I also got an error about "Missing required config value: ETCD_ENDPOINTS" on c1.
I reprovisioned using a good/stable connection and now it works. Not sure if this is a problem of having to wait longer on a poor connection or not - but on the good connection, I didn't get any error related to ETCD_ENDPOINTS.


Address CVE-2020-7690

Sorry if it's a duplicate, wasn't able to find anything related to CVE-2020-7690 among issues and PRs.
Unfortunately, I don't have all the details about this vulnerability, besides knowing that it's being identified by vuln scanners that discover jspdf as a dependency.
Does anyone have more insights into the issue? What are the plans to address it?

I must be turning blind... see  #2795 now.

@ikornienko do you happen to know how we can tell the side that this vulnerability was fixed with 2.0.0?

I'm not quite sure NVD specifies this kind of data about when the issue was fixed. But let me double check and come back to you.
I did see that in Snyk Vuln DB it specifies that the remediation is to upgrade to 2.0.0. So vuln scanners that rely on Snyk should correctly notify their users about the available fix.

@HackbrettXXX my awesome colleagues from StackRox helped to get the following info:

NVD database shows in "Known Affected Software Configurations: cpe:2.3:a:parall:jspdf:*:*:*:*:*:node.js:*:* and nothing more, which means that VersionEndIncluding isn't defined, and therefore they indeed don't know that the issue was fixed at some point.
One can submit an update to the existing CVE Entry as described here. Probably makes sense for maintainers of jsPDF to do so.


Initialize aerial as a plugin

With this, Aerial works just by being present in runtime path. No requires are called on
initialization, which should keep its impact on startup time to the minimum.
Configuration is read from vim.g.aerial_nvim_config on the first
load of aerial.config, highlights are similarly created on the
first execution of aerial.highlight. This allows one to set up
configuration adjustments in, for example,
.config/nvim/plugin/aerial.lua and have the plugin just work, if it's
present.
I've intentionally dropped an eager command repeat on potentially
loading state. If information is not present, it's simply not present.
With LSP, it's natural to wait for LSP to initialize, with TreeSitter
current symbols fetcher is synchronous, so waiting for parsing is baked in.

I don't use recession, and with no tests for recession integration, this change might've broken something.
While this partially reverts an older move away from global configuration, I believe that this PR achieves the best of both worlds by using global configuration once with an ability to use .setup call to reapply changes in configuration or apply a separate configuration altogether.

I'm not sure what makes "update docs" task fail on CI. When isolating it locally, it passes without any problems.

Ah, apologies I should have been more clear: performance was the impetus for switching from global-variable configuration to the current system, but I do not believe that your PR would introduce any performance problems. I put that in just to flesh out the history, but should have realized it would come across sounding like I was still worried about performance.

Primary goal - the plugin works just by adding it. This is an editor plugin, not a runtime library.

This is a high-level guiding principle, but what is the actual problem? I can think of two possibilities:

Adding a require("aerial").setup() line to configuration is undesirable (presumably for the reasons below)
Doesn't align with how most vanilla vim plugins work

Is there anything else that I'm missing?

Secondary goal - when plugin is not yet present (e.g. initial setup, performance triage, testing out other plugin) the default editor just works. Plugins should gradually enhance user experience with as little demand for intervention as possible. Plugin configuration presence shouldn't throw errors if plugin is not present.

If I'm interpreting this correctly, you're saying that you want the code that configures the plugin to not throw errors if the plugin is not installed. This makes it easier to try different plugins, have different configs, or just :help bisect. Is that a fair statement?

I'm currently still in the camp of using .setup(), and I'll explain my reasoning below, but I do want to make sure that I'm not overlooking anything. I think it's entirely possible for us to look at the same set of tradeoffs and disagree on which one is better, as that's a value judgement, but I want to ensure we're starting from a shared understanding of what those tradeoffs are. So if it seems like there's something I haven't considered, do let me know.
There are three main reasons I prefer the .setup() pattern:

It's a convention. Regardless of if the convention is good or bad, it still comes with benefits. Users are more likely to be familiar with it, so there's less to grok when getting set up. Other tools are built that leverage this interface (e.g. lazy.nvim offers super sick configuration merging of opts, which is passed into .setup())
Calling .setup() is explicit and imperative. It puts the user in complete control of when the plugin is initialized. If you leverage a plugin/ file to do this, it's completely possible to mess up the initialization order because it's no longer visible exactly when these scripts will run. I have been bitten by this before.
It's the way the plugin currently works. Adding a new mechanism adds more complexity. It's another thing to maintain, it's another thing to document, it's another thing for users to grok as they're getting set up.

None of these are overwhelming reasons. Honestly the differences between the two mechanisms are not that significant, but these do seem like positives, and they make me mildly inclined to use .setup(). Additionally, I don't find that the global variable pattern is necessary to achieve the goal of avoiding errors during configuration. It's very easy to do:
local has_aerial, aerial = pcall(require, "aerial")
if has_aerial then
  aerial.setup()
end

Maybe a bit more verbose than vim.g.aerial = { ... }, but it has advantages. You can explicitly choose what to do in the case that aerial is available, or is not available.
local has_aerial, aerial = pcall(require, "aerial")
if has_aerial then
  aerial.setup()
else
  vim.notify("Plugin missing: aerial", vim.log.levels.WARN)
end

Also, as soon as the configuration gets more involved by adding keymaps and autocmds, you're back to square one. Sure the vim.g.aerial = won't cause problems, but you'll have broken keymaps and autocmds. The way to fix that is by checking if aerial is installed or not with pcall(require, "aerial"), but at that point it seems like nothing is gained over .setup().

The problem ultimately is that when I add a plugin, I expect it to just work.
I don't initialize ftplugins, I don't initialize InspectTree, man, shada, or matchit plugins. In the same vein, I strive to have other plugins to simply work.

That aside, I do want to offer a deeper look into the arguments. I did spend last five of six years considering all the same things, funnily enough.
.setup being a convention is a self-defeating argument. Simply because plugin and ftplugin are older,wey better established, and actually codified conventions. For a time, neovim lacked support for .lua plugin files and many plugin writers either didn't want to deal with lua <<LUA or, which I see evidence for a lot, didn't know how neovim loaded plugins. Nowadays, setup is a bad pattern, because it forces an extra filesystem access when it least makes sense.
I do agree with explicitness of .setup call. There is a beauty to it that I desire as a software developer when I require a library, which is why I made sure to keep it working. Still, aerial.nvim is not a library, it's an editor plugin.
The new mechanism is an old mechanism with complexity removed. It replaces the old mechanism by merging .setup and vim.g... routes. I explicitly pursued this design to keep existing users oblivious, new users happy, and maintenance cost the same at worst.
As for lazy.nvim, it's not a standard and doesn't seem likely to become one. It's nice to acomodate it, but the standard that every plugin should absolutely work with is vim packages. I, for example, eschew lazy because it ironically does way too much.


Closing the directbytebuffer locally to prevent leaks

Related to the jira issue:
https://issues.apache.org/jira/browse/ARTEMIS-2696
Assuming this can be done locally, this could be a fix for the above issue.

ARTEMIS-2696 was resolved awhile back. If this is still an issue please open a new Jira or update this PR. Thanks!


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Please fill out the application in the correct format. Incorrect formats will result in the issue being closed. Also, please confirm that a liquidity pool has been created on SunSwap.


[Question] In this new version is possible to show an input action keyboard below the input field?

Dear developers,
Thank you very much for your development. I have a question, is it possible in this new version to add an action keyboard below the input field, as it was possible in the previous version with the option inputFooterBuilder? Now I try with chatFooterBuilder, but the options are over the input field is required that this options appears below the input field.
Thank you for your answer.

Hello, this is not possible at the moment, but a bottom param could be added to InputOptions. It would work like trailing and leading params


Google  VlSA

حل مشكلة اغلق حسابك

Not sure what this means. Please provide more info and a minimum reproduction of your issue or start a discussion if reporting an issue wasn't your intention.


Changes to support removal of both RD and IF

ENSVAR-5057

The tests are failing, the test genomicFeatureDiseasePanelAdaptor.t throws error:
ok 19 - fetch_by_dbID
ok 20 - fetch_by_dbID panel
ok 21 - fetch_by_dbID confidence category
ok 22 - fetch_by_dbID is visible
Could not get value for attrib: 49 and type: confidence_category

Updated the test files. Thanks for pointing this out @Diana

Merged into release/107 and master


standalone code doesn't work when ajv-formats and user code use different ajvs (solution here)

I followed the advise at https://github.com/ajv-validator/ajv/issues/1386 to generate standalone instance of validate. Still after having that done, occasionally we observe the following error when we try to run a generated validate
TypeError: formats4 is not a function
    at validate11 (/Users/medikoo/npm-packages/serverless/lib/classes/ConfigSchemaHandler/[generated-ajv-validate]9f269cb9d1ac9b6f0a2e48d232cc957067c41a6f.js:73:24798)

I looked into (prettified version) of generated code, and indeed something doesn't look right there.
At https://gist.github.com/medikoo/1d5f509c8d705b835c207fe1d3b37ef8#file-ajv-compiled-js-L9437-L9439 it's obviously the undefined that's assigned to formats4 variable
Then at L84237 (not shown in gist as file is too large), there's a if (!formats4(data331)) { which obviously crashes with above error, and I don't see in generated script any logic that will recover formats4 to be a function
Our standalone generator code can be inspected here:
https://github.com/serverless/serverless/blob/acd3b5b331c19fd70f620cc0b204992f6c21819a/lib/classes/ConfigSchemaHandler/resolveAjvValidate.js#L23-L34
What version of Ajv are you using? Does the issue happen if you use the latest version? v7.0.3
Ajv options object

{
      allErrors: true,
      coerceTypes: 'array',
      verbose: true,
      strict: false,
      code: { source: true },
}

JSON Schema
It's a large Schema as generated by Serverless Framework (we can provide a gist if needed)

As I investigated further this issue is characteristic to setup where dependencies are linked. In my case it's:
node_modules/ajv -> /usr/local/lib/node_modules/ajv (v7.0.3)
node_modules/ajv-formats -> /usr/local/lib/node_modules/ajv-formats (v1.5.1)

And /usr/local/lib/node_modules/ajv-formats has it's own installation of ajv (v7.0.3) in its node_modules.
If I install the dependencies normally via npm install, then standalone is generated without errors

As I investigated further this issue is characteristic to setup where dependencies are linked. In my case it's:
node_modules/ajv -> /usr/local/lib/node_modules/ajv (v7.0.3)
node_modules/ajv-formats -> /usr/local/lib/node_modules/ajv-formats (v1.5.1)

And /usr/local/lib/node_modules/ajv-formats has it's own installation of ajv (v7.0.3) in its node_modules.
If I install the dependencies normally via npm install, then standalone is generated without errors

Does it mean we can close it? To make it work in your case it may be enough to do npm link ajv (and/or ajv-formats in the right format, if the issue is the code not finding them.

Does it mean we can close it? To make it work in your case it may be enough to do npm link ajv (and/or ajv-formats in the right format, if the issue is the code not finding them.

Does it mean we can close it? To make it work in your case it may be enough to do npm link ajv (and/or ajv-formats in the right folder), if the issue is the code not finding it.

There's no issue with installation on my side. Each package sees its each dependency at expected version.
It's a definitive issue on AJV (or bundler it uses) side. Maybe it's simply lack of support for symlinked dependencies (of which resultion works perfectly in scope of Node.js process).
This blocks us from shipping, and due to dynamic nature of our schema, it's generated on user side, and now if users relies on some installer that favors symlinking (as e.g. pnpm), program may start to crash

Does it mean we can close it? To make it work in your case it may be enough to do npm link ajv (and/or ajv-formats in the right folder), if the issue is the code not finding it.

There's no issue with installation on my side. Each package sees its each dependency at expected version.
It's a definitive issue on AJV (or bundler it uses) side. Maybe it's simply lack of support for symlinked dependencies (of which resultion works perfectly in scope of Node.js process).
This blocks us from shipping, and due to dynamic nature of our schema, it's generated on user side, and now if users relies on some installer that favors symlinking (as e.g. pnpm), program may start to crash

Ok, it would help to have a reproducible small example to investigate/fix

Ok, it would help to have a reproducible small example to investigate/fix

Sure, I've published reproduction case here: https://github.com/medikoo/ajv-compilation-issue

Sure, I've published reproduction case here: https://github.com/medikoo/ajv-compilation-issue

@medikoo ok, so the reason for the problem is that ajv that is used by ajv-formats and ajv that is used by your code are different ajv's (you can check in node_modules), and because of that instanceof _Code that code generation uses to differentiate between strings and code snippets fails - ajv-formats uses one class to point to itself, and ajv uses another.
There are two solutions possible here:

use package.json with all dependencies you need - not sure what is the reason to avoid it - it would make ajv-formats use the same code of ajv, as used in your code.
manually assign ajv.opts.code.formats = require("ajv-formats/dist/formats").fullFormats (or .fastFormats) in your code, where  can be imported from ajv (const {default: Ajv, } = require("ajv")in JS,import Ajv, {} from "ajv" in TS`)

I will think whether it is something that should be solved in ajv (e.g. replacing instanceof with some other check).

@medikoo ok, so the reason for the problem is that ajv that is used by ajv-formats and ajv that is used by your code are different ajv's (you can check in node_modules), and because of that instanceof _Code that code generation uses to differentiate between strings and code snippets fails - ajv-formats uses one class to point to itself, and ajv uses another.
There are two solutions possible here:

use package.json with all dependencies you need - not sure what is the reason to avoid it - it would make ajv-formats use the same code of ajv, as used in your code.
manually assign ajv.opts.code.formats = require("ajv-formats/dist/formats").fullFormats (or .fastFormats) in your code, where  can be imported from ajv (const {default: Ajv, } = require("ajv")in JS,import Ajv, {} from "ajv" in TS`)

I will think whether it is something that should be solved in ajv (e.g. replacing instanceof with some other check).

I will think whether it is something that should be solved in ajv (e.g. replacing instanceof with some other check).

From my experience instanceof quite often proves to be not reliable, and I personally do not resort to it
In Node.js there are a lot of ways to introduce a setup where two different installations of same package are installed (even if not linking it can easily be introduced when practicing fixed versioning in package.json).
In browsers there can be different realms (frames) and e.g. array instanceof Array will not work for array coming from different realm (it's a sole reason why Array.isArray was introduced)
IMO best is to rely on some kind of duck typing (all types detection in native layer works like that), with symbols it can be done really cleanly. Check Symbol.for which ensures same symbol instances across realms (actually this API was created to address this use case)

I will think whether it is something that should be solved in ajv (e.g. replacing instanceof with some other check).

From my experience instanceof quite often proves to be not reliable, and I personally do not resort to it
In Node.js there are a lot of ways to introduce a setup where two different installations of same package are installed (even if not linking it can easily be introduced when practicing fixed versioning in package.json).
In browsers there can be different realms (frames) and e.g. array instanceof Array will not work for array coming from different realm (it's a sole reason why Array.isArray was introduced)
IMO best is to rely on some kind of duck typing (all types detection in native layer works like that), with symbols it can be done really cleanly. Check Symbol.for which ensures same symbol instances across realms (actually this API was created to address this use case)

A possible fix is to pass _ and potentially other code-generation functions via the instance to ensure that the dependencies use the same class. So ajv-formats and ajv-keywords would use ajv._ etc.

A possible fix is to pass _ and potentially other code-generation functions via the instance to ensure that the dependencies use the same class. So ajv-formats and ajv-keywords would use ajv._ etc.

use package.json with all dependencies you need - not sure what is the reason to avoid it - it would make ajv-formats use the same code of ajv, as used in your code.

This is the case, where standalone will be built on user side. Any installation that works for Node.js should be considered valid

manually assign ajv.opts.code.formats = _require("ajv-formats/dist/formats").fullFormats (or .fastFormats) in your code, where _ can be imported from ajv (const {default: Ajv, } = require("ajv") in JS, import Ajv, {} from "ajv" in TS

We can explore, still can you point exactly the code we should use? Our standalone generation code can be seen here: https://github.com/serverless/serverless/blob/acd3b5b331c19fd70f620cc0b204992f6c21819a/lib/classes/ConfigSchemaHandler/resolveAjvValidate.js#L23-L34 With what it should be replaced, to be bulletproof?

use package.json with all dependencies you need - not sure what is the reason to avoid it - it would make ajv-formats use the same code of ajv, as used in your code.

This is the case, where standalone will be built on user side. Any installation that works for Node.js should be considered valid

manually assign ajv.opts.code.formats = _require("ajv-formats/dist/formats").fullFormats (or .fastFormats) in your code, where _ can be imported from ajv (const {default: Ajv, } = require("ajv") in JS, import Ajv, {} from "ajv" in TS

We can explore, still can you point exactly the code we should use? Our standalone generation code can be seen here: https://github.com/serverless/serverless/blob/acd3b5b331c19fd70f620cc0b204992f6c21819a/lib/classes/ConfigSchemaHandler/resolveAjvValidate.js#L23-L34 With what it should be replaced, to be bulletproof?

as I wrote above you need to do:
const {_} = require("ajv")
ajv.opts.code.formats = _`require("ajv-formats/dist/formats").fullFormats`

after ajvFormats(ajv)

as I wrote above you need to do:
const {_} = require("ajv")
ajv.opts.code.formats = _`require("ajv-formats/dist/formats").fullFormats`

after ajvFormats(ajv)

As long as your compiled code can require "ajv-formats/dist/formats" it would work - if not, you can change require path to simply point to this file location on your filesystem.

As long as your compiled code can require "ajv-formats/dist/formats" it would work - if not, you can change require path to simply point to this file location on your filesystem.

Now that ajv-formats has ajv as peer dependency (starting from v1.6 and in v2) it should not happen.

Just as a note I still find it happening with the latest version of ajv and ajv-format. If there's interest I can provide reproduction steps.
However, the patch proposed in the comment above works.


Remove anonymous gists support.

resolves #7

I support this but my PR #10 I think needs to be merged first to work with the current Github gist token format.

@khalidelboray thank you, I mostly incorporated your modification into the code base. This PR itself would have been much harder to update at this point.


Use an env var for examples.json location

I could never get it to work with plain CLI arguments.
Fixes https://github.com/pulumi/pulumi-converter-terraform/issues/36
Otherwise it works well.

Closing in favor of https://github.com/pulumi/pulumi-converter-terraform/pull/29 which works now! Great!


rake docs: pull currently used rubocop version

We were hardcoding this tag, which of course led to it being forgotten
for an update when we updated rubocop.
Rubocop tags their repository reliably, so I think it's reasonable to
use the loaded rubocop's version here to decide what tag to checkout.
@codeclimate/review

LGTM. Thanks for the catch!

@jpignata and good thing we had a test for those doc contents: it caught a problem caused by some changes to Rubocop's sources. Fixed in ea0b161 if you want to take a look. Not exactly the cleanest code: I can refactor tomorrow if you'd like.

Closing since I made a duplicative fix in https://github.com/codeclimate/codeclimate-rubocop/pull/57. Oops.


⚠ Visual-Crew_Builder has degraded performance

In 6663cc0, Visual-Crew_Builder (https://visual-crew-builder.ai) experienced degraded performance:

HTTP code: 200
Response time: 917 ms

Resolved: Visual-Crew_Builder performance has improved in c59e5d5 after 6 minutes.


Pronunication Scoring

How is the pronunciation scored without text and alignment
Witt S.M and Young S.J [2000]; “Phone-level pronunciation scoring and assessment or interactive language learning”; Speech Communication, 30 (2000) 95-108.

requires the constrained phone loop

@yondu22
My-Voice-Analysis and MYprosody repos are two capsulated libraries from one of our main projects on speech scoring. The main project (its early version) employed ASR and used the Hidden Markov Model framework to train simple Gaussian acoustic models for each phoneme for each speaker in the given available audio datasets, then calculating all the symmetric K-L divergences for each pair of models for each speaker. What you see in these repos are just an approximate of those model without paying attention to level of accuracy of each phenome rather on fluency
In the project's machine learning model we considered audio files of speakers who possessed an appropriate degree of pronunciation, either in general or for a specific utterance, word or phoneme, (in effect they had been rated with expert-human graders). Here below the figure illustrates some of the factors that the expert-human grader had considered in rating as an overall score

S. M. Witt, 2012 “Automatic error detection in pronunciation training: Where we are and where we need to go,”


Related to JS #3509 Javascript Completion fails if 'exports' is qualified with 'module'

VSCode Version: 0.10.11 (0.10.11)
OS Version: OS X or Windows

This works:
-- foo.js --
'use strict';
 const circle = require('./circle');
 console.log( `The area of a circle of radius 4 is ${circle.area(4)}`);

 circle.   <= you get 'area' and 'circumference'

-- circle.js --
'use strict';
const PI = Math.PI;
exports.area = (r) => PI * r * r;
exports.circumference = (r) => 2 * PI * r;
This fails: (note in circle.js, 'exports' is qualified with 'module.'
-- foo.js --
'use strict';
 const circle = require('./circle');
 console.log( `The area of a circle of radius 4 is ${circle.area(4)}`);

 circle.   <= you DON't get 'circumference'

-- circle.js --
'use strict';
const PI = Math.PI;
module.exports.area = (r) => PI * r * r;
module.exports.circumference = (r) => 2 * PI * r;

Moving to TypeScript for investigation.

This issue was moved to Microsoft/TypeScript#7927


matplotlib not installable

While installing matplotlib there pops an error, I cant identify if it is pipenv or matplotlib...
$ uname -a
Darwin tBook 15.6.0 Darwin Kernel Version 15.6.0: Sun Jun  4 21:43:07 PDT 2017; root:xnu-3248.70.3~1/RELEASE_X86_64 x86_64
[goern@tBook p1]$ pipenv --version
pipenv, version 8.2.6
[goern@tBook p1]$ pipenv install matplotlib
Installing matplotlib…
Requirement already satisfied: matplotlib in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages
Requirement already satisfied: cycler>=0.10 in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)
Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)
Requirement already satisfied: six>=1.10 in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)
Requirement already satisfied: pytz in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)
Requirement already satisfied: python-dateutil>=2.0 in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)
Requirement already satisfied: numpy>=1.7.1 in /Users/goern/.local/share/virtualenvs/p1-hem_Ny3t/lib/python3.6/site-packages (from matplotlib)

Adding matplotlib to Pipfile's [packages]…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pipenv/cli.py", line 1852, in install
    do_lock(system=system, pre=pre)
  File "/usr/local/lib/python3.6/site-packages/pipenv/cli.py", line 1083, in do_lock
    pre=pre
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 421, in resolve_deps
    resolved_tree.update(resolver.resolve(max_rounds=PIPENV_MAX_ROUNDS))
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 101, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 199, in _resolve_one_round
    for dep in self._iter_dependencies(best_match):
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 293, in _iter_dependencies
    dependencies = self.repository.get_dependencies(ireq)
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 171, in get_dependencies
    result = reqset._prepare_file(self.finder, ireq)
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/pip/req/req_set.py", line 639, in _prepare_file
    abstract_dist.prep_for_dist()
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/pip/req/req_set.py", line 134, in prep_for_dist
    self.req_to_install.run_egg_info()
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/pip/req/req_install.py", line 438, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/pip/utils/__init__.py", line 707, in call_subprocess
    % (command_desc, proc.returncode, cwd))
pip.exceptions.InstallationError: Command "python setup.py egg_info" failed with error code 1 in /var/folders/h0/mm7t_nl57wbbm6hj8xknf49m0000gp/T/tmpalhruqwdbuild/subprocess32/

That's fixed by #833, which is in master but not yet released.

cool, I can wait a day for the release :)

Didn't realize we were waiting on a release from us. I'll try to get something out today.

@vphilippon continuing discussion from #871, pipenv lock --verbose --clear gave me:
Creating a virtualenv for this project…
⠋Using base prefix '/usr'
New python executable in /home/nighturs/.local/share/virtualenvs/tmp-9zohn9O5/bin/python3
Also creating executable in /home/nighturs/.local/share/virtualenvs/tmp-9zohn9O5/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /home/nighturs/.local/share/virtualenvs/tmp-9zohn9O5
Locking [dev-packages] dependencies…
Using pip: -i https://pypi.python.org/simple --trusted-host pypi.python.org

                          ROUND 1
Current constraints:

Finding the best candidates:

Finding secondary dependencies:
------------------------------------------------------------
Result of round 1: stable, done
Locking [packages] dependencies…
Using pip: -i https://pypi.python.org/simple --trusted-host pypi.python.org

                          ROUND 1
Current constraints:
  matplotlib

Finding the best candidates:
  found candidate matplotlib==2.1.0 (constraint was <any>)

Finding secondary dependencies:
  matplotlib==2.1.0 not in cache, need to check index
  matplotlib==2.1.0         requires cycler>=0.10, matplotlib==2.1.0, numpy>=1.7.1, pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1, python-dateutil>=2.0, pytz, six>=1.10

New dependencies found in this round:
  adding ['cycler', '>=0.10', '[]']
  adding ['matplotlib', '==2.1.0', '[]']
  adding ['numpy', '>=1.7.1', '[]']
  adding ['pyparsing', '!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1', '[]']
  adding ['python-dateutil', '>=2.0', '[]']
  adding ['pytz', '', '[]']
  adding ['six', '>=1.10', '[]']
Removed dependencies in this round:
Unsafe dependencies in this round:
------------------------------------------------------------
Result of round 1: not stable

                          ROUND 2
Current constraints:
  cycler>=0.10
  matplotlib==2.1.0
  numpy>=1.7.1
  pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1
  python-dateutil>=2.0
  pytz
  six>=1.10

Finding the best candidates:
  found candidate cycler==0.10.0 (constraint was >=0.10)
  found candidate matplotlib==2.1.0 (constraint was ==2.1.0)
  found candidate numpy==1.13.3 (constraint was >=1.7.1)
  found candidate pyparsing==2.2.0 (constraint was >=2.0.1,!=2.0.4,!=2.1.2,!=2.1.6)
  found candidate python-dateutil==2.6.1 (constraint was >=2.0)
  found candidate pytz==2017.2 (constraint was <any>)
  found candidate six==1.11.0 (constraint was >=1.10)

Finding secondary dependencies:
  matplotlib==2.1.0         requires cycler>=0.10, matplotlib==2.1.0, numpy>=1.7.1, pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1, python-dateutil>=2.0, pytz, six>=1.10
  pytz==2017.2 not in cache, need to check index
  pytz==2017.2              requires pytz==2017.2
  numpy==1.13.3 not in cache, need to check index
  numpy==1.13.3             requires numpy==1.13.3
  cycler==0.10.0 not in cache, need to check index
  cycler==0.10.0            requires cycler==0.10.0, six
  six==1.11.0 not in cache, need to check index
  six==1.11.0               requires six==1.11.0
  pyparsing==2.2.0 not in cache, need to check index
  pyparsing==2.2.0          requires pyparsing==2.2.0
  python-dateutil==2.6.1 not in cache, need to check index
  python-dateutil==2.6.1    requires python-dateutil==2.6.1, six>=1.5

New dependencies found in this round:
  adding ['cycler', '==0.10.0,>=0.10', '[]']
  adding ['numpy', '==1.13.3,>=1.7.1', '[]']
  adding ['pyparsing', '!=2.0.4,!=2.1.2,!=2.1.6,==2.2.0,>=2.0.1', '[]']
  adding ['python-dateutil', '==2.6.1,>=2.0', '[]']
  adding ['pytz', '==2017.2', '[]']
  adding ['six', '==1.11.0,>=1.10,>=1.5', '[]']
Removed dependencies in this round:
  removing ['cycler', '>=0.10', '[]']
  removing ['numpy', '>=1.7.1', '[]']
  removing ['pyparsing', '!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1', '[]']
  removing ['python-dateutil', '>=2.0', '[]']
  removing ['pytz', '', '[]']
  removing ['six', '>=1.10', '[]']
Unsafe dependencies in this round:
------------------------------------------------------------
Result of round 2: not stable

                          ROUND 3
Current constraints:
  cycler==0.10.0,>=0.10
  matplotlib==2.1.0
  numpy==1.13.3,>=1.7.1
  pyparsing!=2.0.4,!=2.1.2,!=2.1.6,==2.2.0,>=2.0.1
  python-dateutil==2.6.1,>=2.0
  pytz==2017.2
  six==1.11.0,>=1.10,>=1.5

Finding the best candidates:
  found candidate cycler==0.10.0 (constraint was >=0.10,==0.10.0)
  found candidate matplotlib==2.1.0 (constraint was ==2.1.0)
  found candidate numpy==1.13.3 (constraint was ==1.13.3,>=1.7.1)
  found candidate pyparsing==2.2.0 (constraint was >=2.0.1,!=2.0.4,!=2.1.2,!=2.1.6,==2.2.0)
  found candidate python-dateutil==2.6.1 (constraint was >=2.0,==2.6.1)
  found candidate pytz==2017.2 (constraint was ==2017.2)
  found candidate six==1.11.0 (constraint was >=1.10,==1.11.0,>=1.5)

Finding secondary dependencies:
  six==1.11.0               requires six==1.11.0
  matplotlib==2.1.0         requires cycler>=0.10, matplotlib==2.1.0, numpy>=1.7.1, pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1, python-dateutil>=2.0, pytz, six>=1.10
  numpy==1.13.3             requires numpy==1.13.3
  python-dateutil==2.6.1    requires python-dateutil==2.6.1, six>=1.5
  pyparsing==2.2.0          requires pyparsing==2.2.0
  pytz==2017.2              requires pytz==2017.2
  cycler==0.10.0            requires cycler==0.10.0, six
------------------------------------------------------------
Result of round 3: stable, done
Updated Pipfile.lock (e011c0)!

Now it works fine, thanks. So seems like updating to fixed version won't work until you clear cache.

8.2.7 was just released to PyPI so this should be resolved and available.

Affirmative. Thanks!

@nateprewitt Just in case you skipped it, I noticed there's no tag/release on github for 8.2.7 (which confused me at first).

Thanks for catching that @vphilippon. Looks like our release build hiccuped on that step and I didn't notice. Tag is pushed now.

@nateprewitt I think I'm still running into this one on 8.2.7 as described here: https://github.com/kennethreitz/pipenv/issues/712#issuecomment-338518518

I take it back - seems to have resolved it self after explicitly running pipenv install matplotlib. I was previously just running pipenv install with matplotlib listed in the Pipfile. ¯_(ツ)_/¯ works now!


Code Quality: Update folder structure to match solution configuration

Description
It would make more sense for the folder structure of the app to match that of the solution configuration (nested folders) in the Solution Explorer:

Although the more generic src and tests folders are used, the platforms and core folders don't quite match the repository folder structure.
Concerned code
The src directory.
Gains
N/A Self-explanatory
Requirements
No response
Comments
This might not be so possible for the Files.Package project due to the problems with it outlined in #16350

Pitting aside the WAP project issue, I don't agree upon this idea. Such over-nested structure makes things harder to be understandable. I've separated Core projects in "core" sln folder because I wanted bring them to the upper area of the Solution Explorer for developers to be able to understand the hierarchy (that's why I left "platform" as had been instead of "app" as well).

Since I've organized the solution structure and standardized the naming of the projects, I don't see any issue around the structures (rather far better than before and almost best now), and don't see benefits that can be gained by nesting just to create just two folders in the src folder.

It's bad code style to have nested folders in Solution Explorer that don't actually exist.

(rather far better than before and almost best now)

You're absolutely right, it has been far improved but strangely exactly like FluentHub idk why from when I last saw the codebase which would have looked like this:

Youch, look at the mix of Pascal case and lower case

Wait, Files used to use Directory.Build.props??
Just saw that in the image.

I can say it's not bad with definite confidence since the solution file is virtualized and serialized folder structure which VS can deserialize, and so many solution files should customize the structure to be convenient.

but strangely exactly like FluentHub idk why

FluentHub has worked like an infrastructure playground of Files repo. For example, it has the exact same CI infra as Files.

Wait, Files used to use Directory.Build.props??

Can you send the committish url?

FluentHub has worked like an infrastructure playground of Files repo. For example, it has the exact same CI infra as Files.

Yes, you've said. 😄

Wait, Files used to use Directory.Build.props??

Can you send the committish url?

265b46e20d4f2f06c02a63bfdbfff55232fc61e8


Update module golang.org/x/net to v0.33.0 release-1.14 [SECURITY]

Description of your changes
This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

golang.org/x/net
v0.26.0 -> v0.33.0

CVE-2024-45338
An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.
I have:

[ ] Read and followed Crossplane's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

/test-examples="examples/s3/v1beta2/bucket.yaml"


Fix content of toplevel-suites

As soon as one *suite* is defined, there's no mechanism to reset it.
So only the first one was recorded in *toplevel-suites*, making run-all-suites bothersome.

No longer relevant because of a46bb10d.


avoid initiateAuthentication call on any forms with POST method behind authentication

If we are use AuthenticationMiddleware and ZendAuthentication together then ZendAuthentication tries to initiate authentication on every POST request in protected area. Such behavior prevents using any form behind authentication
This pull request adds an hasIdentity check before validating method and allows forms with POST behind authentication

@sfortop Thanks for this PR!


refactor(storage): increase max supported sstable file size

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR addresses two issue:

It increases the supported SSTable file size from u32::MAX bytes to u64::MAX bytes, as well as u64::MAX key_count.
It rejects overflowed RestartPoint::offset value of u32 type. Because we both support u32::MAX bytes key, u32::MAX bytes value and u32::MAX kilobytes block_size, RestartPoint::offset can overflow.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

After some discussion, we decide to panic early on overflow, instead of this PR.


pass strip:false to the template engine (really, this time!)

So, #15 was broken. I got the order of the arguments to _.extend wrong.
So I'm redoing the PR.

(rebased and removed the extra unnecessary diffs in lib/*)

Thank you for your job 👍


Missing word in text about residual connections

Missing "have" in sentence:  A network can {have} several such blocks
Link: https://lena-voita.github.io/nlp_course/models/convolutional.html
Great course btw.

passing the message to @lena-voita


Refactor WebSocketClient and add userMessages state

This pull request refactors the WebSocketClient component and adds a new state called userMessages. The WebSocketClient component now uses the useWebSocket hook from the WebSocketContext and sets the readyState and messageClient variables. The ChatList component now receives the userMessages prop and sets the chats state based on the userMessages. The ChatInterface component now uses the useWebSocket hook to set the messages state based on the selectedChat and messageClient. The WebSocketClient class now has a new method called clientDetails that returns the serverLoginDetails. Additionally, the sendMessage method now checks if the serverLoginDetails is defined before sending the message.

Create merged


Fix CI tests

stub-check: set -T on tput

Fixes #191
@ErikSchierboom  what do you think?

@ErikSchierboom I cannot merge it.  I have not write access.

Merged!


Get slidePerView on Auto Slide

I'm using auto slide but I haven't found any way to get the number of slide on the view (without the name).
I needed to use slidesOffsetBefore and after to make some css tricks, but that way slider don't detect when there is not enough slides  and button next stay active.
I would like to cancel slidesOffset when there is not enough slide to complete screen.
Do you think there is a way to do this or this could be a (graphic) enhancement ?

If you set slidePerView with auto, I don't think you can get number of slide per one view.


Cas-561: Provide access to udev databse for mayastor container via additional volume mount.

Mayastor requires access to the udev database that resides in /run/udev
in order for the ListBlockDevices() gRPC request to function correctly.
This access must be provided via an explicit volume mount when Mayastor
is run from within a container. Without such access, the gRPC call
returns partial and (highly misleading) incorrect information.
@cjones1024 carried out the investigation and made the original changes.
I have moved the changes in his PR from their original place in
deploy/mayastor-daemonset.yaml to
chart/templates/mayastor-daemonset.yaml as this is now used to construct
the YAML file in the deploy directory.
For the purposes of review see https://github.com/openebs/Mayastor/pull/576 for the original PR.

bors merge


How to detect RouterOSAPI.stream's end

How to detect when a RouterOSAPI.stream is complete?
I'm testing using the /ip/address/print command.
I was expecting the stream returned from RouterOSAPI.stream to emit either the close or the end event, but neither one is emitted.

I can detect it using the channel property on the stream object, but TypeScript complains that it's private:
stream.channel.on("close", () => { observer.complete() });

error TS2341: Property 'channel' is private and only accessible within class 'RStream'.

I see. The idea of a stream in this context is that it never ends, you should define when you wanna close it.
If you are just printing the ip address, use this syntax instead:
conn.write("/interface/print").then((data) => {
    console.log(data);
});

// or with async/await
const data = await conn.write("/ip/address/print");
console.log(data);

Stream is used for things like /tool/torch, or when you use listen or intervals like:
conn.stream(['/ip/address/listen'], (error, packet) => {
    console.log(packet);
});

In theses cases, the stream never stops unless you tell it to.

I have a watch function that starts a /listen command, and then runs /print to get all the current records. The idea is to create an RxJS Observable that emits all active PPP connections, and then emits for every account that connects or disconnects.
I want to use RouterOSAPI.stream for the /print command as well, because there may be thousands of records to be received and the link between this program and the RouterOS device may be slow.

I see, you need to get small chunks of a large dataset from the print command, in that case I'll need to make some adaptations to the code.
Meanwhile, you can add a "// @ts-ignore" above the line that you listen to the channel event.
I had a similar use case but instead I used the data from the "/listen" itself to mutate a previous dataset from a "/print" command, so I don't need to print again to get the current state. I might as well implement such feature within the API to make things easier 😅.

Added a new method writeStream which behaves like the write command but it returns an EventEmitter object. From it you can listen to data, trap, close and done events.
The done event only triggers when the data finishes streaming and there was no error.
If a trap gets emitted, the done will not be emitted.

How may I close the stream without closing the connection? There is no end or close function on the stream object.
Another option would be to run the RouterOS API /cancel command manually, but I have not found any way to discover the stream tag.

Oops. Yeah, currently you can't stop it, I'm gonna update it so you can do that, hang tight.

I've updated the package to v1.6.0, now the writeStream will return an RStream object, the same event from before will still work plus you can call close(), pause() and resume() functions if you want. If you had any typescript declaration to the previous return EventEmitter class, you might need to update it.
Please, tell me if this update works for you.

Worked perfectly. Thank you!


Spyder naming for Arch Linux distribution

Description of your problem
There's some discussions in the Arch Linux bug tracker about the Spyder naming for the Python 2.x and Python 3.x versions.
Since the 2010 Arch Linux has changed the default python symlink to point to python 3.x, therefore the default python command now uses Python 3.x.
Every related Python command uses the same schema, except Spyder which actually is an exception in the Arch Linux world.
Can I have the upstream opinion on a naming change for spyder and spyder3 executables?
The naming change would be:
/usr/bin/spyder2 would point to the Python 2.x version
/usr/bin/spyder3 would point to the Python 3.x version
/usr/bin/spyder would be a symlink to /usr/bin/spyder3
My objections are mainly for upstream colliding names, in order also to avoid the issues opening with incoerent names with your naming.
What steps will reproduce the problem?

Install spyder and spyder3 packages in Arch Linux (pacman -S spyder spyder3)
Observe the executables names ($ pacman -Ql spyder spyder3 | grep '/usr/bin/spyder*')

spyder /usr/bin/spyder
spyder3 /usr/bin/spyder3

Execute spyder to launch Spyder for Python 2.x

This is something we can't do anything about. It has to be solved by the Arch developers.

I'm the Arch Linux spyder maintainer, I would be glad to hear your opinion.
The naming scheme will influence how the Arch Linux users will report you the issues.

We can do something about the setup.py though. At the moment, we install as spyder for Python 2 and spyder3 for Python 3 (on Linux). At some point we probably want to change this, probably on a major version (e.g. Spyder 4, or maybe that's too soon).
I think it will be helpful for Arch Linux and other distributions if we have a plan for this.

I'm the Arch Linux spyder maintainer, I would be glad to hear your opinion.

Sorry, I read this too quickly.

The naming change would be:
/usr/bin/spyder2 would point to the Python 2.x version
/usr/bin/spyder3 would point to the Python 3.x version
/usr/bin/spyder would be a symlink to /usr/bin/spyder3

I'm fine with this. This is, of course, an Arch particular problem. I think other distributions (e.g. Ubuntu) will maintain the convention to point the spyder executable to the Python 2 version.
As @jitseniesen said, we could revisit this in the future, but not until other major distributions decide to it.

The python distribution itself uses python2 and python3, and specifies that python should be a symlink to the default system python (which they recommend should be python2). This rule is also applied to all the commands shipped with python2 and python3.
I think thematically any application that works with the python interpreter itself should follow the same guidelines. (In fact, any application that ships executables for both python2 and python3, but in practice only for anything that has functionality specific to the version of python it runs with, e.g. IDEs, pip, source code linters... for anything else you only need the one for the default system python.)
It would be entirely appropriate for said application to use e.g. spyder2, even if you also default to symlinking spyder ==> spyder2 as Python itself does. Arch Linux can set our own symlinks for the default version. :smile:
This would essentially preserve the current state of things, while making it somewhat easier for downstream packagers to 1) intuit what the executable names are meant to be, and 2) package it appropriately as per downstream policy.

That's way too confusing for our current state of things.
As I said, I don't have objections to Arch renaming our Python 2 executable and making spyder to point to the Python 3 one. But we're not going to move in that direction in the short term, sorry.

So it was done in spyder 2.3.0-1

Yeah, 3 years ago.

ahah indeed... I meant 3.2.0-1


How to get categorical variables in the graph?

I am opening an issue because I am trying to reproduce the results obtained in this graph:

I would like to get the categorical features as text, just as it can be seen in the image. However, when doing it by myself, if I don't convert the categorical values to numeric I am getting an error, and therefore I am not able to reproduce the graph as it gets the number the variable was encoded with:

Do you know why is this happening and what should I do in order to get it with the text? Thanks

Hi @anaquio,
Are you using the ExplainableBoostingClassifier for this? If you pass in the text values directly to ebm.fit() and ebm.explain_local() as a Pandas dataframe, it should preserve the categories in the output.

if I don't convert the categorical values to numeric I am getting an error

What error are you running into? Could you paste the error message here and the code you are running?
Thanks!
-InterpretML Team


[Epic]: Plugin 2.0

### W3C specs support
- [ ] https://github.com/tokens-studio/figma-plugin/issues/999
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1811
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1747
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2052

### Variables M2
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2406
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1969
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1974
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2411
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2412
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2443
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2023
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2120
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2211

### Tasks
- [ ] https://github.com/tokens-studio/figma-plugin/pull/2467
- [ ] https://github.com/tokens-studio/figma-plugin/pull/2473
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1855
- [ ] https://github.com/tokens-studio/figma-plugin/issues/2393
- [ ] https://github.com/tokens-studio/figma-plugin/pull/2484

@six7 can we close this epic now that the release is done?

@six7 This release has passed. Can we close?


Fix code scanning alert - Uncontrolled data used in path expression

Tracking issue for:

[x] https://github.com/tugcantopaloglu/juice-shop/security/code-scanning/49

This doesn't lead to any issue.


Minor Doc Fix

from #27627

Thanks for the PR @gshashank84! Sorry we no longer accept patches to previous released branches. Will close this PR. Thanks again!


use cross-platform method to specify C++ standard

This new method of specifying the C++ standard has the following advantages:

it is more portable across compilers than to hardcode GCC/Clang -std=c++11

a packager can use a greater C++ standard directly from the CMake command line, using the following syntax, e.g. to compile in C++17 mode:
cmake -DCMAKE_CXX_STANDARD=17 .

the requirement can be automatically exported when it is set as a PUBLIC requirement, which I did in the 2nd commit for the graphqlservice target

The first commit has basically all these benefits and does not require a new CMake version.
The second commit use a slightly more modern method of specifying the flags but requires a newer CMake version CMake >= 3.8.
So if CMake 3.5 is a strong requirement, maybe only the first commit should be picked.

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

Thanks! This looks much better.

I decided to stick with CMake 3.5.1 and merge just the first commit for now since that's the CMake version that comes with Ubuntu 16.04 and I haven't upgraded all of my WSL images yet.


build: pull from alpha before rebase master

Description
Run git pull origin alpha after switching to alpha branch to ensure it has latest changes before we attempt to rebase with master
Deploy Preview
N/A
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

:tada: This PR is included in version 21.0.0-alpha.14 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


React 15 support ?

Hi,
Any updates on this version?
Thanks

Currently it seems like just a update in package.json, I'll test it soon and publish a compatible version.

1.6.2 is out, should be working. By the way I highly recommend you to try 2.0.0-beta.4, which is also compatible with React 15.0.0 with more simpler API and better performance.


feat: add arg(s) for layer_db name

Adds an arg to pass through the layer db name to the associated services.

bors merge


about regional/global/textual features graph

I wonder Where are you building the code about regional/global/textual features graph,Thanks a lot.
.

https://github.com/kywen1119/DSRAN/blob/main/model.py#L221


Add example eval scripts for dbrx PT sizes

Here's an example of how these work: eval-dbrx-U4Ew2U
Docs to come in https://docs.mosaicml.com/projects/mcli/en/latest/ (will link PR)

Also is there a good way to keep these yamls up to date with any changes we might make in PAPI in the future?

@b-chu

To reduce duplication, can we just have 1 yaml and put the model section of the different yamls into a README?

The goal was to make submitting eval yamls as easy as possible, ideally without modifying the checkpoint. See the mcli yaml in the docs here https://github.com/databricks-mosaic/mosaicml-cli/pull/1762