install zig head failed

brew doctor output
  brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  six

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 3.6.16-6-g760ab63
ORIGIN: https://github.com/Homebrew/brew
HEAD: 760ab63978bcb6b4396d0303d87f6ff6ddf910e6
Last commit: 23 minutes ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 08e7183dcc78832ab3c5ba60ab199216b82001c2
Core tap last commit: 64 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_BAT_THEME: TwoDark
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: nvim
HOMEBREW_MAKE_JOBS: 8
http_proxy: http://<IP_ADDRESS>:1087
https_proxy: http://<IP_ADDRESS>:1087
Homebrew Ruby: 2.6.10 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit haswell
Clang: 14.0.0 build 1400
Git: 2.39.0 => /usr/local/bin/git
Curl: 7.84.0 => /usr/bin/curl
macOS: 13.0.1-x86_64
CLT: <IP_ADDRESS>.1.1666437224
Xcode: N/A

What were you trying to do (and why)?
run brew install zig --HEAD to install zig head version
What happened (include all command output)?
  brew install zig --HEAD
==> Fetching zig
==> Cloning https://github.com/ziglang/zig.git
Updating /Users/joyce/Library/Caches/Homebrew/zig--git
==> Checking out branch master
Already on 'master'
Your branch is up to date with 'origin/master'.
HEAD is now at 266e2e9a3 Revert "CI: workaround git bug regarding changed attributes"
==> cmake -S . -B build -DZIG_STATIC_LLVM=ON
Last 15 lines from /Users/joyce/Library/Logs/Homebrew/zig/01.cmake:
-- Check for working CXX compiler: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring zig version 0.11.0-dev.926+266e2e9a3
dyld[7852]: Library not loaded: /usr/local/opt/z3/lib/libz3.4.11.dylib
  Referenced from: <FFDA0103-7EB6-3739-95EE-D4DE25D3F6EF> /usr/local/Cellar/llvm/15.0.6/bin/llvm-config
  Reason: tried: '/usr/local/opt/z3/lib/libz3.4.11.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/z3/lib/libz3.4.11.dylib' (no such file), '/usr/local/opt/z3/lib/libz3.4.11.dylib' (no such file), '/usr/local/lib/libz3.4.11.dylib' (no such file), '/usr/lib/libz3.4.11.dylib' (no such file, not in dyld cache), '/usr/local/Cellar/z3/4.11.2/lib/libz3.4.11.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/z3/4.11.2/lib/libz3.4.11.dylib' (no such file), '/usr/local/Cellar/z3/4.11.2/lib/libz3.4.11.dylib' (no such file), '/usr/local/lib/libz3.4.11.dylib' (no such file), '/usr/lib/libz3.4.11.dylib' (no such file, not in dyld cache)
CMake Error at cmake/Findllvm.cmake:27 (message):
  expected LLVM 15.x but found using /usr/local/opt/llvm/bin/llvm-config
Call Stack (most recent call first):
  CMakeLists.txt:136 (find_package)

What did you expect to happen?
install success
Step-by-step reproduction instructions (by running brew commands)
just run install head command

Please don't open issues about failed source/HEAD builds. We do not provide support for this, and brew should have indicated as much in the error message you saw.
Try
brew reinstall z3


Option to make print immediately default

We use SRU almost exclusively with the "print immediately"-Option activated. It would be very nice to have the checkbox checked by default. Could probably use the existing "print immediately"-option in config.json as this is currently without function?

sounds like a good idea to me, i will implemet this in a future version

Works as expected - great!


Team update - Sep 28, 2022

This is a @Quansight-Labs/czi-a11y-grant team sync 🎉🎉🎉! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.
Copy and paste the template below, and answer questions as you wish!

Response Template
**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

:mag: Needs Triage
The Needs Triage issues require an initial assessment and labeling.
No issues need triage! 🎉
:dart: Project boards
Please make sure the boards reflect the current status of the project.
Jupyter a11y grant project

Updates from last week :heavy_check_mark:

I worked in the new pygments package: https://github.com/Quansight-Labs/accessible-pygments
Created an issue for adding the hamburger menu in Jupyterlab: https://github.com/jupyterlab/jupyterlab/issues/13148

Challenges I faced and things I'd like assistance with 🙏

I'm ok

My availability for next week

I'll be here

Important items for discussion 💬

I don't have anything super important to discuss

Thanks I'd like to give 🙌
Updates from last week :heavy_check_mark:

#133 has new mockups for 200% zoom behavior.
#146 planning for next set of tests. I have a timeline for the end of the year and polishing the things that came from the last test into PR form.

Challenges I faced and things I'd like assistance with 🙏

I think I'm okay right now.

My availability for next week

I'll be here all week.

Important items for discussion 💬

Eventually the new mockups, but I think that doesn't fit as well in an update-focused meeting.

@steff456

working on pygments - some pygments working there already 🎉  needs some polishing and bits here and there
will then move onto the hamburger/ellipsis fix issues

@gabalafou

will be moving to Colombia next week - so timezones will be slightly different from usual
🎉 got his expect-axe-playwright PR merged after a while
learned about pa11y + CI

@kulsoomzahra

working on https://github.com/Quansight-Labs/jupyterlab-accessible-themes/issues/37
preparing for show and tell on Monday

--

@isabela-pf

new suggestions for UI https://github.com/Quansight-Labs/jupyterlab-accessible-themes/issues/34#issuecomment-1262458172
Space telescope - planning new user testing at the end of the year (content focused)

Thanks I'd like to give 🙌

@isabela-pf for organizing the vote to elect a representative from the Jupyter Accessibility Subproject to the Jupyter Software Steering Council.

Updates from last week :heavy_check_mark:
I made a mistake this week and thought, maybe I'll use Monday and Tuesday to clear some small tasks from my plate, and then those ended up just taking up all my time. So the following bullet points are things I've worked on that are accessibility-related but not directly related to accessibility in Jupyter.

Good news: Finished upstreaming my changes to expect-axe-playwright. Bad news: not sure we'll use it, and it took too much of my time this week.
https://github.com/Widen/expect-axe-playwright/pull/24. Finished this PR, which felt like doing a little bit of public service. The aim here was to prevent unintentionally spreading the idea among developers that there's an automated tool out there that can stamp your page or app as "accessible" or not.
https://github.com/Widen/expect-axe-playwright/pull/23. Finished this PR. It will allow us to stop using my fork of expect-axe-playwright.
https://github.com/Quansight/Quansight-website/pull/262. Worked some more on adding Pa11y-CI to the Quansight website. Discovered more obstacles, specifically the default configuration for Axe flags a bunch of elements on the site for contrast that might not have contrast issues. These elements either have a background image or otherwise overlap some other element, and for some reason, that makes Axe incapable of ascertaining the foreground/background contrast ratio. So I'm going to have to hide a bunch of elements during testing in order to get the site to pass the CI/CD run or figure out a way to configure Axe differently.

My availability for next week

I am taking Monday off.


Document release process

Summary
This PR adds a documentation page under the "Contributing" section of the NuttX docs which contains the NuttX release process documentation from Alin Jerpelea's gist: https://gist.github.com/jerpelea/67895da8797f040ba3b113280fdcd57b
Impact
This contributes a step forward towards the issues discussed in #14062. The release process is now documented centrally on the NuttX website and can be modified there as a single source of information for new contributors to see how releases are made.
There is still more information which could be added, like the information in Lup's comment on #14062, but I am opening this PR to get the documentation which already exists in a consolidated form included on the website.
Testing
I performed a local build of the documentation, ensured there were no errors and visually inspected the rendered HTML in my browser to make sure that the formatting was okay.

@lupyuen please reopen the issue, if you want to add more info.


AI Traffic creation from BeamNGpy

Hello!
Is it possible to create AI traffic from BeamNGpy which could be launched together with a player-controlled car?
Can you share a code example if it is possible?

Take a look here :
https://github.com/BeamNG/BeamNGpy/issues/40#issuecomment-638174494

It seems like this issue has been resolved. Thanks for your input.

It seems like this issue has been resolved. Thanks for your input.


Optional Userland Proxy

Port https://github.com/docker/docker/pull/12165 to libnetwork
More tests will be added later

Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

LGTM

LGTM.


Add possibility to pass T::Structs as value for #with

The solution is rather straightforward:
In #recursive_stringify_keys add another branch to check for wether the value is a T::Struct. In this case just call serialize.
Motivation
Using the #with helper on T::Struct can be really useful especially when using immutable objects. Typical example is having an address or money type:
class Money < T::Struct
  const :amount, Integer
  const :currency, String
end

class Order < T::Struct
  const :value, Money
end

o = Order.new(value: Money.new(amount: 100_00, currency: "USD"))
o.with(value: Money.new(amount: 200_00, currency: "USD"))

Not only is this not possible, the error message is also very cryptic:
/gems/ruby/3.1.0/gems/sorbet-runtime-0.5.10526/lib/types/props/serializable.rb:72:in `rescue in rescue in deserialize': Error in Order#__t_props_generated_deserialize: <Money amount=20000, currency="USD"> provided to from_hash (TypeError)
at line 8 in:
    found = 1
    val = hash["value"]
  @value = if val.nil?
    found -= 1 unless hash.key?("value")
    self.class.decorator.raise_nil_deserialize_error("value")
  else
    begin
    Money.from_hash(val)
  rescue NoMethodError => e
    raise_deserialization_error(
      :value,
      val,
      e,
    )
    val
  end
/gems/ruby/3.1.0/gems/sorbet-runtime-0.5.10526/lib/types/props/serializable.rb:70:in `rescue in deserialize': Error in Order#__t_props_generated_deserialize: <Money amount=20000, currency="USD"> provided to from_hash (ArgumentError)
at line 8 in:
    found = 1
    val = hash["value"]
  @value = if val.nil?
    found -= 1 unless hash.key?("value")
    self.class.decorator.raise_nil_deserialize_error("value")
  else
    begin
    Money.from_hash(val)
  rescue NoMethodError => e
    raise_deserialization_error(
      :value,
      val,
      e,
    )
    val
  end
/gems/ruby/3.1.0/gems/sorbet-runtime-0.5.10526/lib/types/props/serializable.rb:209:in `from_hash': <Money amount=20000, currency="USD"> provided to from_hash (ArgumentError)

For the user there is a workaround by just calling #serialize on the passed in value:
o.with(value: Money.new(amount: 200_00, currency: "USD").serialize)
=> <Order value=<Money amount=20000, currency="USD">>

Test plan
See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_N7gfAJdklcZZmG
→ https://go/builds/bui_N7gf0ohANTfXyT

Sorry: this change causes 55,000 test failures on Stripe's codebase.
T::Struct and the underlying T::Prop APIs are very tightly coupled to Stripe's internal database libraries. Changing them is difficult to impossible while preserving backwards compatibility, because of how much code depends on the way it currently works.
There is more context written up here:

Legacy Code and Historical Context
Immutable property updates using with

Given that, we're going to have to decline this change. Thanks and best wishes.

For posterity, Stripe employees can see the runtime test failures here:
http://go/builds/bui_N7xbHxkRFHrrU2


RowKey prop not present in dist folder when installing the package at 4.4.0

Been finding since the version bump to 4.4.0 with the rowKey that it's not actually showing up anywhere in my dist folder when I npm install the package so I can't use it. Unsure if this is something my end if it's just related to the package build process.
Below is taken from a freshly created app that's installed the package at 4.4.0.

Thanks for the repport @Tibs7777 , now fixed in 4.4.1 ;)


add ability to use babel plugins without ejecting

@verbiricha I figured out how to get babel-plugin-react-intl-auto to auto inject the message descriptors with babel.

rebased 😀


[OSDEV-1346] Add moderation-event GET endpoint

Fix OSDEV-1346
Add GET api/v1/moderation-events

 Quality Gate failed
Failed conditions  7 Security Hotspots
See analysis details on SonarCloud

@VadimKovalenkoSNF If you disagree with those security fails from SonarQube you can resolved it redirecting to SonarQube service.

TODO: redo Match Status to PENDING,  APPROVED, REJECTED.

@mazursasha1990 Thanks for the comprehensive review. It encouraged me to look at the inheritance problem here from another angle. There current query builder inheritance will follow this pattern after my recent changes:
from abc import ABC, abstractmethod

class OpenSearchQueryBuilderInterface(ABC):
    @abstractmethod
    def add_sort(self, field, order_by=None):
        """Public method for adding sort functionality."""
        pass

class OpenSearchQueryBuilder(OpenSearchQueryBuilderInterface):
    """Base class that provides common query-building utilities."""

    def add_sort(self, field, order_by=None):
        """Public interface that calls the protected `_add_sort` method."""
        self._add_sort(field, order_by)

    @abstractmethod
    def _add_sort(self, field, order_by=None):
        """Protected method that subclasses can customize."""
        pass

class ModerationEventsQueryBuilder(OpenSearchQueryBuilder):
    """Concrete implementation of the OpenSearchQueryBuilder for moderation events."""

    def _add_sort(self, field, order_by=None):
        # Concrete implementation specific to moderation events
        print(f"Sorting {field} in {order_by} order for moderation events.")

In a nutshell, this allows to call add_... methods as public without breaking abstraction in  OpenSearchQueryBuilderInterface -> OpenSearchQueryBuilder ->  ModerationEventsQueryBuilder | ProductionLocationsQueryBuilder

UPD: OpenSearch query builder inheritance has been refactored again. I removed OpensearchQueryBuilderInterface. Instead use ABC for class OpenSearchQueryBuilder(ABC) from abc module. Also, for sake of readability, I removed protected methods signatures at all. Current logic for query builders is:
OpenSearchQueryBuilder(ABC) -> ModerationEventsQueryBuilder | ProductionLocationsQueryBuilder.
Also, restructured methods order in OpenSearchQueryBuilder(ABC).

@mazursasha1990 I made _build_os_id as protected, pls re-check.


Remove usages of obsolete APIs

https://github.com/aspnet/Razor/issues/2082
Follow up to https://github.com/aspnet/Razor/pull/2273

What's up with the conflicts?

Rebase fail. Will fix it.


opnsense /usr/local/etc/rc.bootup error in log

Found this after some testing tonight.  Not sure if this was in other releases or not:
opnsense: /usr/local/etc/rc.bootup: The command '/usr/sbin/pw groupadd -g -M 2001 2>&1' returned exit code '65', the output was 'pw: group name required'

Matt, I could not track this down. Does the problem persist? It is likely a custom user that you added to the system through the config.xml...

It seems related to https://github.com/opnsense/core/commit/49c891985fc733ec647094bec7c315e2af265fdf , when adding users sometimes an empty group item was put in to local_user_set_groups and then weirdness happened. I will close this issue.

Cool! :)


Missing: Listing Droplets by Tag

Ref: https://developers.digitalocean.com/documentation/v2/#listing-droplets-by-tag

@royalgarter you should be able to do this via:
var tag = 'foo';
client.droplets.list({ tag_name: tag }, callback)

See #1. Going to close this issue for now, but if there's a way we could improve the documentation or examples, please comment!


Introduce a Ballerina connector for LinkedIn REST API

We are planning to introduce a new Ballerina connector for the latest LinkedIn REST API by generated using it's OpenAPI specification.
Related links:

https://docs.microsoft.com/en-us/linkedin/shared/integrations/people/profile-api

This includes the following tasks:

Create a new repository under 'ballerina-platform' organization.
Create the OpenAPI specification manually or by converting it from other API descriptor formats.
Generate the connector client.
Implement a test suite covering the core functionalities.
Write documentation with examples.

Hi, I am interested to work on this issue, can you please assign this to me?

👋 Welcome, @Thenujan-Nagaratnam ! 🚀
We're thrilled to have you join the Ballerina Hacktoberfest community! The issue has been assigned to you, and we’re excited to see your contributions.
To help you get started, here are a few essential resources:

Connector Contributor Guide: Make sure to go through our Ballerina Hacktoberfest connector contributor guidelines and follow the exact steps, to contribute effectively.
Learn Ballerina: Whether you're new to Ballerina or looking to enhance your skills, check out our official learning resources.
Community & Support: If you have technical questions, feel free to ask on Stack Overflow with the Ballerina tag, or join us on Discord to connect with other community members.

No contribution is too small, and your feedback is always welcome! Don’t hesitate to ask questions, propose new ideas, or report issues.
We are currently in the process of creating a GitHub repository for this connector module and will update you once it’s available. In the meantime, please go through the relevant resources and documentation related to the connector.
Happy coding and welcome aboard! 🎉

@NipunaRanasinghe can you please assign me this issue, since it hasn't been resolved yet

Hi, if the original assigned person will not be able to start on this issue, could you please assigned it to me @Nuvindu ?

Hi @Nuvindu , I apologize that I will not be able to attend this issue. You can assign this to @tharindu432 .
Thank you!

👋 Welcome, @tharindu432 ! 🚀
We're thrilled to have you join the Ballerina Hacktoberfest community! The issue has been assigned to you, and we’re excited to see your contributions.
To help you get started, here are a few essential resources:

Connector Contributor Guide: Make sure to go through our Ballerina Hacktoberfest connector contributor guidelines and follow the exact steps, to contribute effectively.
Learn Ballerina: Whether you're new to Ballerina or looking to enhance your skills, check out our official learning resources.
Community & Support: If you have technical questions, feel free to ask on Stack Overflow with the Ballerina tag, or join us on Discord to connect with other community members.

No contribution is too small, and your feedback is always welcome! Don’t hesitate to ask questions, propose new ideas, or report issues.
We are currently in the process of creating a GitHub repository for this connector module and will update you once it’s available. In the meantime, please go through the relevant resources and documentation related to the connector.
Happy coding and welcome aboard! 🎉

Thanks @Nuvindu !. is there any repository to work ?

Hi @tharindu432,
You can start working in this repository: https://github.com/ballerina-platform/module-ballerinax-linkedin.
Please refer to the contribution process section for guidelines on raising a PR: https://ballerina.io/hacktoberfest/connector-contributor-guide/#contribution-process.
Happy coding! 🎉

@Nuvindu ! Thanks .

Hey @tharindu432 !
Just checking the progress of the connector development, were you able to start the development of the connector ? Just a quick update on the project deadlines: it's set for one month from the day you were officially assigned. But if you encounter any challenges or unforeseen issues, please feel free to reach out, and we can consider adjusting the deadline accordingly.
If you have any questions or need help with anything, please feel free to reach out. Keep up the awesome work! 🚀

Hi @tharindu432, any update on this?

We have decided to keep this issue open for reassignment as we haven't received any updates from @tharindu432 yet. If you are still interested in working on this issue, please comment below. Meanwhile, this issue is now open for contributions from others.


Test commit for code reveiw

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


X-Rocket-Nginx-Bypass + Connected user

Hi Maxime,
Today it's not possible to Bypass Wordpress when the user is logged because of the cookie.
If you find the cookie "wordpress_logged_in_" you set $rocket_bypass to 0.
With wp-rocket the cached files for a logged user ar inside a directory like : /wp-content/cache/wp-rocket/www.domain-Username-NUM-ID/
What if when a user is logged we add a function to create a cookie named Username-NUM-ID
and with rocket-nginx we check if this cookie exist to get his name and allow the nginx redirect ?
Do you think it will be possible ?
Thank you

I'm working on version 2.0 which is almost finished but as I'm not paid for this project, I only do it when I have free time... which does not happen really often.
That said, you will be able to control cookies, headers and so much more.  So what you are asking will be doable easily! :-)

I totally misunderstood what you were saying.  Sorry about that.
I'm not sure what would be needed but I have to look into it.

Sorry for the late answer.
I was thinking to create a specific cookie when a user is logged
This cookie name will be : Username-NUM-ID
In order to match the name of the cached directory created by wp-rocket : /wp-content/cache/wp-rocket/www.domain-Username-NUM-ID/
With X-Rocket-Nginx the goal will be to detect if this cookies exist, and use his name in order to set rocket_end correctly
Thanks for your help :)

For some reason, I never saw that answer. I would suggest that you send your code/request to WP Rocket. If they implement something like this in the official plugin, I would gladly consider doing what is needed to make it work with Rocket-Nginx.

Maybe @Tabrisrp could help or give insights about what they think.

The Username-NUM-ID identifier is already based on a cookie generated by WordPress, which name is wordpress_logged_in_ + the value of the  COOKIEHASH constant

The problem is that scripting with Nginx is really limited. You cannot get a substring the way you would do it in PHP.
I would need the exact key to be found somewhere "as-is".
Something like this:
Cookie name: wprocket-user-hashkey
value: maxime-0352fa113050320656c94
That way, the value of the cookie can be used to check if a file/folder exists.

Hi Maxime,
I've manage to make it work with my app, but my app need to send the wp logged username in the headers ( int he example bellow http_x_rest_username).
rocket-nginx.conf :
if ($http_x_rest_username != "") {
set $rocket_end "/cache/wp-rocket/$http_host-$http_x_rest_username-MY_ROCKET_CACHE_SECRET_KEY/$request_uri/index$rocket_https_prefix.html$rocket_encryp$
}
I've also add this on WP-Rocket in order to create the cached file for the connected user if it doesn't exist and the app is sending the http_x_rest_username header :
$headerStringValue = $_SERVER;
$username = $headerStringValue['HTTP_X_REST_USERNAME'];

if ($username != "") {
    $user_key = $username . '-' . $rocket_secret_cache_key;
    $request_uri_path = $rocket_cache_path . $host . '-' . $user_key . rtrim( $request_uri, '/' );
}else{
    $request_uri_path = $rocket_cache_path . $host . rtrim( $request_uri, '/' );
}

I'm closing this issue as it would almost be impossible to validate the user with Nginx. The authentication should be done by WordPress and the cache served by WP-Rocket. I understand the benefit of "skipping" WordPress and serving the cache file directly but there is no way of doing it directly with Rocket-Nginx in a configuration file.


Refactor virt-config

What this PR does / why we need it:
This PR:

Defines default config values in kubevirt-config that were hard-coded at defaultClusterConfig as consts
Introduces virt-config.go that holds the configuration that should be exposed outside (besides the feature gates) and its default values. Those are separated out from config-map.go that remains with the "infrastructure" part.
Update the documentation of feature-gates.go

Special notes for your reviewer:
This PR extracts the refactoring-related changes from #2406
Release note:

NONE

/cc @rmohr

/retest

/retest

@ahadas could you rebase?

@ahadas could you rebase?

sure, done

/approve

/retest

/retest

/retest

/test pull-kubevirt-e2e-k8s-1.11.0
/test pull-kubevirt-e2e-os-3.11.0
/test pull-kubevirt-e2e-os-3.11.0-crio

@ahadas merged #2463 and restarted the tests since they started before #2463

/retest

@ahadas merged #2463 and restarted the tests since they started before #2463

thanks :)

/retest

/retest


no need to FlutterActivity ref

Please merge this - otherwise plugins relying on FlutterFragmentActivity (like my https://github.com/jonasbark/flutter_stripe_payment plugin) fail to work.

I've done this in another branch. It's been merged to master. Closing this PR.


update old function names (hermitian_eigen) in user guide

Hi!
I found outdated function names in Decompositions and Lapack of the user guide.
The functions hermitian_eigen and try_hermitian_eigen have changed to symmetric_eigen and try_symmetric_eigen, so I have modified the names of these functions.

Thanks!


Relation "wiki_0" does not exist

Trying the demo from the README, the initial query works fine, and the CSV file appears to be downloaded to the correct path, but the second query returns Error: relation "wiki_0" does not exist (SQLSTATE 42P01).
I am new to steampipe - is there another setting required somewhere that also sets the CSV path for use in arbitrary queries?

Hey @psychemedia, I apologize for the delay in responding and for the inconvenience you’re experiencing.
The development of the plugin is on hold due to other higher-priority tasks. However, we will return to it shortly.


Refresh when VS Code tab is moved

Before

Then I move the CAD tab:

So the bottom view is empty now
If I save again, it appears:

While the cad adapts to the size of the tab, the objects camera view is sub optimal. Maybe you could reset the camera?
Can be done by calling viewer.reset().

ah, nope. reset doesn't help.
This is a bug in three-cad-viewer. I did only test it with width:height ratios of about 4:3 ...
See https://github.com/bernhard-42/three-cad-viewer/issues/5

@roipoussiere v1.5.9 fixes it. Now wide cad view with low height are supported as initial zoom and for viewer.reset()

The last version is based on three-cad-viewer v1.5.9.
I still need to update the viewer size according to the panel size, but the camera seems good.

yes, works now


Azure OpenAI lanchain example not working

I am trying to integrate Helicone with Azure-OpenAI using lanchain as in the following link:
https://docs.helicone.ai/getting-started/integration-method/azure
but when I am trying to send a message, I am getting the following error:
"Completions.create() got an unexpected keyword argument 'headers'",
I am using
langchain
Version: 0.0.343
openai==1.3.6

it is wokring whith default_header in case I set: openai_api_base="https://oai.hconeai.com/openai",
but if I follow the waring: UserWarning: As of openai>=1.0.0, if deployment_name(or aliasazure_deployment) is specified then openai_api_base(or aliasbase_url) should not be. Instead use deployment_name(or aliasazure_deployment) and azure_endpoint.
and use azure_endpoint="https://oai.hconeai.com/openai",
then it will not work

the docs are not updated to reflect this and I had to do the same as @mouhannadali, please update the docs for azureOpenAI langchain integration


feat: Add Range Date Picker

hello, does this package support date range picker.

hey @chuvanhoang888, thank you for open this issue. I'm working on this feature already, it should be ready for release next week.

Awesome, thanks for the update!
Vào 15:56, Th 3, 28 thg 11, 2023 Hasan M. Hallak @.***>
đã viết:

hey @chuvanhoang888 https://github.com/chuvanhoang888, thank you for
open this issue. I'm working on this feature already, it should be ready
for release next week.
—
Reply to this email directly, view it on GitHub
https://github.com/hasanmhallak/date_picker/issues/7#issuecomment-1829368516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY5GZ2FYCFJ3NKMXPJQGA53YGWRLNAVCNFSM6AAAAAA73URN6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRZGM3DQNJRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Move from per-experiment .json to .csv + one metadata file

It is at the moment a bit cumbersome to make a new experiment file-- you have to take the (typically .csv or similar) file and parse it before printing out as .json.
I propose a more easily modified format where we:

store limits etc. in .csv files
have the names of these files in a consistent format - SIGNATURE(_MODIFIER)_EXPERIMENT_YEAR_ARXIVNUMBER.csv [so e.g. WIMPSI_XENONNT_2023_2303.14729.csv
then use this same name as the key in a .yaml file where we store things we want to know about this .csv file, that is all the fields we previously had in a per-result .json
this also includes which .csv column is wimp_mass, upper_limit, sensitivity etc.

@yuema137, @ibles , @revive  and @cwittweg opinions :)? Seeing what @yuema137 contributed, I think this is an easier way for us to make updates straightforward.


Error response from daemon: invalid registry endpoint

I have tried to deploy distribution using the docs.
First let me tell you a bit about my environment.
$ docker version
Docker version 1.9.1, build a34a1d5

$ uname -a
Linux edel.XXX.YYY 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1~bpo70+1 (2015-04-27) x86_64 GNU/Linux

$ docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
registry                    2                   683f9cd9cf88        2 weeks ago         224.5 MB

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                                NAMES
4dbb0bd46610        registry:2          "/bin/registry /etc/d"   6 minutes ago       Up 6 minutes        <IP_ADDRESS>:5000->5000/tcp                                                                                registry-XXX-YYY

I have NGINX installed on the host installed using apt.
$ dpkg -l | grep nginx
ii  nginx                              1.6.2-1~wheezy                amd64        high performance web server

I have placed the following configuration in /etc/nginx/sites-enabled/registry.XXX.YYY.conf:
upstream docker-registry {
  server <IP_ADDRESS>:5000;
}

map $upstream_http_docker_distribution_api_version $docker_distribution_api_version {
    'registry/2.0' '';
    default registry/2.0;
  }

server {
  listen 443 ssl;
  server_name registry.XXX.YYY;

  # SSL
  ssl_certificate /etc/ssl/certs/wildcard.XXX.YYY.crt;
  ssl_certificate_key /etc/ssl/private/wildcard.XXX.YYY.key;

  # Recommendations from https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html
  ssl_protocols TLSv1.1 TLSv1.2;
  ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
  ssl_prefer_server_ciphers on;
  ssl_session_cache shared:SSL:10m;

  # disable any limits to avoid HTTP 413 for large image uploads
  client_max_body_size 0;

  # required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)
  chunked_transfer_encoding on;

  location /v2/ {
      if ($http_user_agent ~ "^(docker\/1\.(3|4|5(?!\.[0-9]-dev))|Go ).*\$" ) {
        return 404;
      }

      # To add basic authentication to v2 use auth_basic setting plus add_header
      auth_basic "Registry realm";
      auth_basic_user_file    /etc/nginx/conf.d/registry.htpasswd;
      add_header 'Docker-Distribution-Api-Version' 'registry/2.0';

      proxy_pass                          http://docker-registry;
      proxy_set_header  Host              $http_host;   # required for docker client's sake
      proxy_set_header  X-Real-IP         $remote_addr; # pass on real client's IP
      proxy_set_header  X-Forwarded-For   $proxy_add_x_forwarded_for;
      proxy_set_header  X-Forwarded-Proto $scheme;
      proxy_read_timeout                  900;
  }

}

I have a local PKI deployed, with one Root CA for signing other Root CA's for specific needs with custom defined policies. I am using OpenVPN/easyrsa for that.
I have issued a Hosts Root CA for the purpose of issuing client/server auth certificates for the hosts. Since I am in the testing phase, to keep things simple I have issued a wildcard, wildcard.XXX.YYY.crt certificate with subjectAltName: DNS:*.XXX.YYY so I can use it for the registry as well as for docker hosts to secure the TCP API.
I have copied the Hosts Root CA to /etc/docker/certs.d/registry.XXX.YYY/ca.crt. I have also, according to the docs, placed the Hosts Root CA in /usr/local/share/ca-certificates/hostsca.crt and run update-ca-certificates. I can now see the links in /etc/ssl/certs pointing to /usr/local/share/ca-certificates/hostsca.crt.
I have created a sys user with a simple password using the registry:2 image with the following command:
$ docker run --rm --entrypoint htpasswd registry:2 -bn sys pass > /etc/nginx/conf.d/registry.htpasswd

I have restarted the docker engine daemon and tried to do a login.
$ docker login --username=sys --password=sys -e<EMAIL_ADDRESS>registry.XXX.YYY
Error response from daemon: invalid registry endpoint https://registry.XXX.YYY/v0/: unable to ping registry endpoint https://registry.XXX.YYY/v0/
v2 ping attempt failed with error: Get https://registry.XXX.YYY/v2/: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large
 v1 ping attempt failed with error: Get https://registry.XXX.YYY/v1/_ping: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry registry.XXX.YYY` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/registry.XXX.YYY/ca.crt

I am running the registry with debug log level but after trying to authenticate I don't see any logs apart from:
 trace.line=154 version=v2.2.1
time="2016-01-19T07:33:08.819931981Z" level=debug msg="filesystem.List(\"/\")" go.version=go1.5.2 instance.id=812fb996-1296-4a26-8c14-45318376b14d service=registry trace.duration=49.859µs trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go" trace.func="github.com/docker/distribution/registry/storage/driver/base.(*Base).List" trace.id=78c24856-df1c-4e2f-89f3-d80397c4fc61 trace.line=154 version=v2.2.1
time="2016-01-19T07:33:18.81990011Z" level=debug msg="filesystem.List(\"/\")" go.version=go1.5.2 instance.id=812fb996-1296-4a26-8c14-45318376b14d service=registry trace.duration=63.677µs trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go" trace.func="github.com/docker/distribution/registry/storage/driver/base.(*Base).List" trace.id=d43a9b2e-af9a-4147-bfc1-1ca2bd9f968e trace.line=154 version=v2.2.1

Please point me in the right direction to solve this problem. Thanks :).

@valentinbud you can curl your registry host and see the information.Your can use command like
   curl -v https://yourregistryhost

The error seems to be the  https connection was not built successfully

@valentinbud a couple of remarks:

you are asking for trouble by using an old nginx version - the docs recommend 1.9 (https://github.com/docker/distribution/blob/master/docs/nginx.md)
@ghy200692162 is probably right, and your problem is with your SSL certificate, so, can you curl your nginx?
can you also provide your nginx logs?

@dmp42 here it is what you've asked.

you are asking for trouble by using an old nginx version - the docs recommend 1.9 (https://github.com/docker/distribution/blob/master/docs/nginx.md)

You are absolutely right but my current situation doesn't allow me to update the nginx in question. The machine is used by devs. Once I have a POC working I will switch to NGINX in containers running latest.
To have the same configuration as pointed out in the docs I have installed nginx-extras and now I have the following nginx registry configuration:
upstream docker-registry {
  server <IP_ADDRESS>:5001;
}

map $upstream_http_docker_distribution_api_version $docker_distribution_api_version {
    'registry/2.0' '';
    default registry/2.0;
  }

server {
  listen 443 ssl;
  server_name registry.XXX.YYY;

  access_log /var/log/nginx/creg.access.log;
  error_log /var/log/nginx/creg.error.log debug;

  # SSL
  ssl_certificate /etc/ssl/certs/registry.XXX.YYY.crt;
  ssl_certificate_key /etc/ssl/private/registry.XXX.YYY.key;

  # Recommendations from https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html
  ssl_protocols TLSv1.1 TLSv1.2;
  ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
  ssl_prefer_server_ciphers on;
  ssl_session_cache shared:SSL:10m;

  # disable any limits to avoid HTTP 413 for large image uploads
  client_max_body_size 0;

  # required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)
  chunked_transfer_encoding on;

  location / {
      if ($http_user_agent ~ "^(docker\/1\.(3|4|5(?!\.[0-9]-dev))|Go ).*\$" ) {
        return 404;
      }

      # To add basic authentication to v2 use auth_basic setting plus add_header
      auth_basic "Registry realm";
      auth_basic_user_file    /etc/nginx/conf.d/registry.htpasswd;
      # add_header 'Docker-Distribution-Api-Version' 'registry/2.0';
      more_set_headers 'Docker-Distribution-Api-Version: registry/2.0';

      proxy_pass                          http://docker-registry;
      proxy_set_header  Host              $http_host;   # required for docker client's sake
      proxy_set_header  X-Real-IP         $remote_addr; # pass on real client's IP
      proxy_set_header  X-Forwarded-For   $proxy_add_x_forwarded_for;
      proxy_set_header  X-Forwarded-Proto $scheme;
      proxy_read_timeout                  900;
  }

}

I have used more_set_headers to set the 'Docker-Distribution-Api-Version: registry/2.0' header because 1.6 can't add_headers by itself.

@ghy200692162 is probably right, and your problem is with your SSL certificate, so, can you curl your nginx?

Yes, I think I can.
$ curl -v https://registry.XXX.YYY
* Rebuilt URL to: https://registry.XXX.YYY/
*   Trying <IP_ADDRESS>...
* Connected to registry.ctxag.com (178.63.XX.YY) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
* Server certificate: registry.XXX.YYY
* Server certificate: Cortex AG (c) Hosts Certification Authority
> GET / HTTP/1.1
> Host: registry.XXX.YYY
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Server: nginx
< Date: Fri, 29 Jan 2016 12:02:04 GMT
< Content-Type: text/html
< Content-Length: 188
< Connection: keep-alive
< WWW-Authenticate: Basic realm="Registry realm"
< Docker-Distribution-Api-Version: registry/2.0
<

<title>401 Authorization Required</title>

401 Authorization Required

nginx

* Connection #0 to host registry.XXX.YYY left intact

Next let's try pull, tag and push an image to the repo.
$ docker pull alpine
$ docker tag alpine registry.XXX.YYY/alpine
$ docker push registry.XXX.YYY/alpine
The push refers to a repository [registry.XXX.YYY/alpine] (len: 1)
unable to ping registry endpoint https://registry.XXX.YYY/v0/
v2 ping attempt failed with error: Get https://registry.XXX.YYY/v2/: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large
 v1 ping attempt failed with error: Get https://registry.XXX.YYY/v1/_ping: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large

When I have built the Root CA certificates I have included in them fields needed for a certificate to be an EV-CERT. Maybe that's why asn1 is complaining that integer too large. Do you think it might be connected? Anyway I will start from scratch with a new Root CA and SubCAs without EV stuff.
For example the registry.XXX.YYY certificate looks like the following:
$ openssl x509 -text -in registry.XXX.YYY.crt
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 6 (0x6)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=DE, ST=Hannover, L=Isernhagen, O=Cortex AG, OU=Cortex AG (c) Trust Network, OU=Cortex AG (c) ***FOR AUTHORIZED USE ONLY***, CN=Cortex AG (c) Hosts Certification Authority/businessCategory=Private Organization/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=DE/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.2=Hannover/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.1=Isernhagen/serialNumber=HRB 208681/postalCode=30916/street=Tischlerstrasse 1a
        Validity
            Not Before: Jan 19 08:12:32 2016 GMT
            Not After : Jan 16 08:12:32 2026 GMT
        Subject: C=DE, ST=Hannover, L=Isernhagen, O=Cortex AG, OU=Cortex AG (c) Trust Network, OU=Cortex AG (c) ***FOR AUTHORIZED USE ONLY***, CN=registry.XXX.YYY/businessCategory=Private Organization/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=DE/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.2=Hannover/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.1=Isernhagen/serialNumber=HRB 208681
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
            RSA Public Key: (2048 bit)
                Modulus (2048 bit):
                    00:a5:5d:14:58:24:61:8e:a3:c6:9e:f6:36:e1:c3:
                    d7:6e:3c:b9:69:6a:fc:e8:66:b8:0f:22:3d:18:d1:
                    52:d2:26:75:54:99:2e:d3:38:50:79:54:ba:bd:4f:
                    64:e7:0f:ff:c0:5a:e3:8f:9d:51:d5:ec:79:61:d6:
                    aa:df:e9:77:cf:b4:c0:05:50:2b:4a:f5:85:f8:cd:
                    6c:6c:96:95:64:55:ce:74:fd:eb:c4:2b:27:82:b6:
                    52:00:6e:65:e6:cc:38:4f:a0:ec:08:5f:6d:fa:fe:
                    6f:9b:e5:c0:b1:80:39:19:3b:28:fe:ef:31:30:3d:
                    73:44:ce:d0:6f:91:dd:84:32:b8:2e:1e:57:55:ba:
                    c2:a9:74:4d:36:63:61:ee:d7:f4:71:b1:12:86:ce:
                    cc:25:5d:0c:9b:e2:f1:02:51:37:cf:aa:d3:01:40:
                    8e:cd:9f:56:b4:1a:f8:5c:ba:56:00:e7:b3:c8:32:
                    b2:e2:36:6d:75:a5:ff:46:6d:66:ca:5b:e8:4d:be:
                    fa:37:d7:a5:ad:a6:05:ca:d1:c9:bb:14:80:67:bd:
                    00:93:87:5d:7c:5a:35:eb:f4:21:20:10:56:9e:94:
                    84:b2:e9:b3:81:92:0e:b2:92:56:5a:c8:e7:a2:fe:
                    fa:cf:ac:05:48:2f:4a:c5:57:fd:54:71:c5:de:0f:
                    07:21
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Subject Key Identifier:
                0E:F8:32:A7:06:FA:61:70:3A:61:B5:8A:5E:BE:2D:BE:B9:EB:E7:54
            X509v3 Authority Key Identifier:
                keyid:83:8B:72:49:18:0A:C3:28:66:C9:3D:6D:5F:78:16:01:51:5B:15:D4
                DirName:/C=DE/O=Cortex AG/OU=Cortex AG (c) Trust Network/OU=Cortex AG (c) ***FOR AUTHORIZED USE ONLY***/CN=Cortex AG (c) Root Certification Authority/ST=Hannover/L=Isernhagen/businessCategory=Private Organization/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=DE
                serial:01

            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 CRL Distribution Points:
                URI:http://pki.XXX.YYY/crl/hostsca.crl

            X509v3 Certificate Policies:
                Policy: 2.25.2994168483698941754490116714543420388<IP_ADDRESS>
                  CPS: http://pki.XXX.YYY/cps/hostsca
                  User Notice:
                    Organization: Cortex AG (c)
                    Number: 1
                    Explicit Text: Cortex AG (c) Trust Network operates CAs in conformance with latest PKIX RFCs. Please read our CPS before thoughtfully deciding to put your trust in us. Cortex AG (c) thanks you for your cooperation.

            Authority Information Access:
                CA Issuers - URI:http://pki.XXX.YYY/crt/hostsca.p7b
                OCSP - URI:http://ocsp.XXX.YYY

    Signature Algorithm: sha256WithRSAEncryption
        97:21:59:c2:79:03:bb:9a:26:cb:a1:57:d4:41:3e:7e:04:ae:
        7d:bf:6b:a7:4e:87:e7:c4:5a:02:38:72:58:71:e2:56:e9:15:
        d9:68:fa:5b:48:05:09:fb:e0:f7:b8:e9:52:70:6c:58:de:3c:
        89:b8:34:91:3b:0c:eb:7e:b6:bb:8e:bc:24:87:74:39:dd:99:
        c7:41:ec:29:89:f0:54:40:bd:a4:3d:c2:c5:7a:61:66:b9:c1:
        d6:94:86:07:3a:8a:f1:c9:b5:db:df:79:c2:73:91:e5:c4:d8:
        5a:be:ee:a3:02:43:44:1f:0e:38:27:c2:b5:80:db:6e:82:f2:
        83:03:73:fc:a9:71:3a:d4:61:19:6b:16:27:18:97:96:ea:23:
        76:cc:1c:bf:03:03:24:53:c7:df:59:4d:d2:4b:b1:50:bf:e1:
        fe:63:86:dc:6b:ee:71:ca:e9:7d:19:56:75:ab:d4:63:34:b0:
        61:d1:6d:4d:3b:da:ec:ee:a2:39:15:d4:a3:fd:73:6a:2f:e1:
        40:bf:0c:be:c3:f3:30:73:0a:66:45:69:f0:da:83:b9:e6:b9:
        29:cc:86:ba:9f:da:5d:7c:fc:e8:5f:3b:5f:b8:00:22:98:a5:
        0f:c7:9c:e4:bb:57:2c:39:c3:1d:9e:5e:ca:5b:55:c7:aa:13:
        ea:69:43:b5

can you also provide your nginx logs?

For sure. The creg.access.log is empty and the error log is set on debug showing:
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL_do_handshake: -1
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL_get_error: 2
2016/01/29 13:16:45 [debug] 7528#0: *9 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *9 post event<PHONE_NUMBER>FE8BC8
2016/01/29 13:16:45 [debug] 7528#0: *9 delete posted event<PHONE_NUMBER>FE8BC8
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL handshake handler: 0
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL_do_handshake: 0
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL_get_error: 1
2016/01/29 13:16:45 [info] 7528#0: *9 SSL_do_handshake() failed (SSL: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:SSL alert number 42) while SSL handshaking, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2016/01/29 13:16:45 [debug] 7528#0: *9 close http connection: 24
2016/01/29 13:16:45 [debug] 7528#0: *9 SSL_shutdown: 1
2016/01/29 13:16:45 [debug] 7528#0: *9 event timer del: 24:<PHONE_NUMBER>060
2016/01/29 13:16:45 [debug] 7528#0: *9 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *9 free:<PHONE_NUMBER>D3B7E0, unused: 0
2016/01/29 13:16:45 [debug] 7528#0: *9 free:<PHONE_NUMBER>D32E60, unused: 118
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL_do_handshake: -1
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL_get_error: 2
2016/01/29 13:16:45 [debug] 7528#0: *12 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *12 post event<PHONE_NUMBER>FE8C30
2016/01/29 13:16:45 [debug] 7528#0: *12 delete posted event<PHONE_NUMBER>FE8C30
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL handshake handler: 0
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL_do_handshake: 0
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL_get_error: 1
2016/01/29 13:16:45 [info] 7528#0: *12 SSL_do_handshake() failed (SSL: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:SSL alert number 42) while SSL handshaking, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2016/01/29 13:16:45 [debug] 7528#0: *12 close http connection: 24
2016/01/29 13:16:45 [debug] 7528#0: *12 SSL_shutdown: 1
2016/01/29 13:16:45 [debug] 7528#0: *12 event timer del: 24:<PHONE_NUMBER>145
2016/01/29 13:16:45 [debug] 7528#0: *12 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *12 free:<PHONE_NUMBER>D3B580, unused: 0
2016/01/29 13:16:45 [debug] 7528#0: *12 free:<PHONE_NUMBER>D3B7E0, unused: 118
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL_do_handshake: -1
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL_get_error: 2
2016/01/29 13:16:45 [debug] 7528#0: *13 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *13 post event<PHONE_NUMBER>FE8C30
2016/01/29 13:16:45 [debug] 7528#0: *13 delete posted event<PHONE_NUMBER>FE8C30
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL handshake handler: 0
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL_do_handshake: 0
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL_get_error: 1
2016/01/29 13:16:45 [info] 7528#0: *13 SSL_do_handshake() failed (SSL: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:SSL alert number 42) while SSL handshaking, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2016/01/29 13:16:45 [debug] 7528#0: *13 close http connection: 24
2016/01/29 13:16:45 [debug] 7528#0: *13 SSL_shutdown: 1
2016/01/29 13:16:45 [debug] 7528#0: *13 event timer del: 24:<PHONE_NUMBER>223
2016/01/29 13:16:45 [debug] 7528#0: *13 reusable connection: 0
2016/01/29 13:16:45 [debug] 7528#0: *13 free:<PHONE_NUMBER>D3B580, unused: 0
2016/01/29 13:16:45 [debug] 7528#0: *13 free:<PHONE_NUMBER>D3B7E0, unused: 118

Thanks for helping :).

Ping @dmcgowan and other @docker/distribution-maintainers for additional SSL scrutiny.
Thanks @valentinbud : so, is it working with a non EV cert?

@dmp42 just finished testing with a certificate that's missing the EV stuff and changed the name to index.XXX.YYY.
When I have created the Root CAs I didn't quite understood if by the book the CAs should or should not include EV stuff, so to be sure I thought it wouldn't hurt to include it.
The index.XXX.YYY certificate looks like:
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 7 (0x7)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=DE, ST=Hannover, L=Isernhagen, O=Cortex AG, OU=Cortex AG (c) Trust Network, OU=Cortex AG (c) ***FOR AUTHORIZED USE ONLY***, CN=Cortex AG (c) Hosts Certification Authority/businessCategory=Private Organization/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=DE/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.2=Hannover/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.1=Isernhagen/serialNumber=HRB 208681/postalCode=30916/street=Tischlerstrasse 1a
        Validity
            Not Before: Jan 29 18:52:49 2016 GMT
            Not After : Jan 26 18:52:49 2026 GMT
        Subject: C=DE, ST=Hannover, L=Isernhagen, O=Cortex AG, OU=Cortex AG (c) Trust Network, CN=index.XXX.YYY
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
            RSA Public Key: (2048 bit)
                Modulus (2048 bit):
                    00:c8:96:75:78:fd:53:55:c9:7f:82:ed:b2:e2:89:
                    f7:89:68:c0:8d:e4:68:46:88:73:e6:0e:62:2e:b8:
                    4b:7a:1f:13:37:f9:06:85:48:4a:88:c6:9e:60:75:
                    b8:77:c9:42:51:de:18:f8:ab:9a:1c:be:50:c8:24:
                    b3:36:24:11:33:15:71:66:73:7c:e0:cb:6f:01:22:
                    57:71:8a:44:32:87:af:7f:03:36:74:4d:c1:b8:b6:
                    99:5e:87:17:82:f8:72:4d:2c:b3:61:42:6b:60:9c:
                    f7:97:c9:5e:4d:66:44:b3:a2:b5:86:18:88:19:7e:
                    38:7a:80:d6:98:73:39:5b:a4:2e:bd:11:9e:68:be:
                    1c:1c:ec:03:4a:04:46:18:89:bd:af:65:0a:55:ea:
                    c8:ab:bc:ae:c2:3c:24:03:00:b6:9d:8f:1a:6a:e6:
                    b3:78:37:1c:e2:ab:c6:c3:7d:21:d4:70:9a:85:ff:
                    57:b4:71:bb:ff:23:27:dd:6b:b7:69:19:a8:54:37:
                    5f:fb:23:04:b4:68:67:5e:5f:d4:38:ee:51:fd:0d:
                    14:8d:be:0f:94:ba:e8:19:d7:7c:4d:32:d9:cc:92:
                    16:49:5a:01:8f:46:14:6c:77:e8:85:3c:46:ae:1c:
                    2d:31:70:01:11:08:c4:d4:34:28:7e:be:77:ad:65:
                    f9:75
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Subject Key Identifier:
                6B:1E:F6:E6:2C:0A:BC:B6:EA:F9:5A:8F:34:A5:6C:F7:C1:F9:5D:4E
            X509v3 Authority Key Identifier:
                keyid:83:8B:72:49:18:0A:C3:28:66:C9:3D:6D:5F:78:16:01:51:5B:15:D4
                DirName:/C=DE/O=Cortex AG/OU=Cortex AG (c) Trust Network/OU=Cortex AG (c) ***FOR AUTHORIZED USE ONLY***/CN=Cortex AG (c) Root Certification Authority/ST=Hannover/L=Isernhagen/businessCategory=Private Organization/<IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=DE
                serial:01

            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 CRL Distribution Points:
                URI:http://pki.XXX.YYY/crl/hostsca.crl

            X509v3 Certificate Policies:
                Policy: 2.25.2994168483698941754490116714543420388<IP_ADDRESS>
                  CPS: http://pki.XXX.YYY/cps/hostsca
                  User Notice:
                    Organization: Cortex AG (c)
                    Number: 1
                    Explicit Text: Cortex AG (c) Trust Network operates CAs in conformance with latest PKIX RFCs. Please read our CPS before thoughtfully deciding to put your trust in us. Cortex AG (c) thanks you for your cooperation.

            Authority Information Access:
                CA Issuers - URI:http://pki.XXX.YYY/crt/hostsca.p7b
                OCSP - URI:http://ocsp.XXX.YYY

    Signature Algorithm: sha256WithRSAEncryption
        3a:23:5e:34:05:98:d6:7a:db:52:66:01:61:76:e3:00:40:f2:
        68:54:e6:c7:1c:95:80:38:68:64:b4:1e:67:60:b0:59:07:fd:
        11:71:90:b4:a1:45:53:4e:d1:b4:98:46:79:13:54:b7:f5:1b:
        e1:80:26:4d:14:73:c6:f4:8e:0b:d2:28:4b:48:40:20:4f:d5:
        f0:7b:41:49:cc:3d:d4:cc:3f:5c:80:ed:f3:60:86:a3:ca:5e:
        45:7c:fb:99:13:af:eb:bb:1c:42:61:08:27:2f:28:2a:f7:36:
        b9:61:be:fb:4e:97:27:d0:bc:71:0b:c6:c6:ca:cb:d5:d9:30:
        7a:9e:f5:ac:e0:dd:50:f3:40:fe:0d:c2:6d:2a:fb:c4:14:bf:
        16:18:61:02:a4:9e:58:66:9e:28:a7:c9:bd:b6:f7:ff:f5:0a:
        36:80:b1:59:1b:6f:71:ef:24:38:71:7b:89:37:c2:31:97:c6:
        47:48:29:50:96:26:61:f4:65:f1:0e:a3:7a:b0:aa:ba:f7:ad:
        65:d1:25:bb:1e:58:e9:36:86:ef:d7:ad:e0:d8:c2:87:77:a7:
        f8:c1:ad:b4:d3:d7:21:dd:cb:93:f2:db:13:fd:94:e6:19:8d:
        3a:fb:e9:d2:8c:d8:30:09:c3:d0:d5:df:45:8c:b9:99:27:3c:
        c0:82:11:5e
-----BEGIN CERTIFICATE-----

Still the same behaviour:
$ docker push index.XXX.YYY/alpiness
The push refers to a repository [index.XXX.YYY/alpiness] (len: 1)
unable to ping registry endpoint https://index.XXX.YYY/v0/
v2 ping attempt failed with error: Get https://index.XXX.YYY/v2/: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large
 v1 ping attempt failed with error: Get https://index.XXX.YYY/v1/_ping: tls: failed to parse certificate from server: asn1: structure error: base 128 integer too large

The Issuer still includes EV but the Subject doesn't. To be absolutely sure that the EV parts cause this behaviour I have to create a new CA, issue a cert, distribute it to the hosts and try again :).
I will come back with more information once I finish the above.

It is definitely EV that's causing the error. I have created a new Root CA and one SubCA. From each one of them I have issued a server certificate for the registry.
Docker Machines # CA
|___index.xxx.yyy
|___Docker Machines # SubCA
    |___registry.xxx.yyy

I have published the CA and certs to the hosts as well as insert them at boot in boot2docker.iso used by docker machine.
The index/registry certificate looks just like the ones created by docker machine:
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            8a:81:a6:bd:50:e6:23:33
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN=Docker Machines # CA
        Validity
            Not Before: Jan 29 19:39:32 2016 GMT
            Not After : Jan 26 19:39:32 2026 GMT
        Subject: CN=Docker Machines # CA
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
            RSA Public Key: (2048 bit)
                Modulus (2048 bit):
                    00:d0:1b:88:34:14:86:8f:e6:ae:da:af:40:3e:13:
                    a5:c6:d0:96:e9:ef:4e:ab:9e:e7:35:6c:cd:ac:52:
                    20:64:e1:19:67:f7:de:96:ca:82:71:57:52:51:9c:
                    2c:c3:9d:e7:6f:ba:c0:6a:c4:9b:b0:78:4d:d9:5d:
                    35:91:ad:97:c5:d2:b6:f0:d2:be:2a:d3:76:53:1c:
                    73:e6:0c:d6:d5:3b:a2:21:92:42:a9:1b:8c:8c:37:
                    19:b4:32:18:92:16:fb:82:c1:60:3b:dd:c1:ee:a1:
                    e6:a0:aa:72:65:dc:65:66:49:a6:b5:51:8e:68:f0:
                    b3:1e:fb:40:99:57:5a:b2:fa:2b:33:50:46:b1:a7:
                    f8:c3:ec:cd:10:44:6a:9e:1c:a7:9b:04:74:9c:41:
                    dc:bc:89:7c:e2:92:d6:a5:94:5f:23:a1:21:9d:74:
                    16:6b:09:4a:5a:ac:73:85:48:c1:ee:49:ea:5d:47:
                    cb:ff:14:9b:b7:f5:d5:5e:39:74:e2:ac:8b:e6:ce:
                    1a:4d:7c:2b:63:de:87:79:10:af:77:51:9d:03:38:
                    d8:e0:c0:bc:2d:04:93:1a:6d:03:a2:41:16:96:7e:
                    b4:6a:a3:78:6a:08:3a:36:a0:c4:a3:57:cd:51:26:
                    b8:de:ac:0f:b7:63:28:8a:85:5e:ec:14:22:60:58:
                    18:3f
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Subject Key Identifier:
                14:DE:86:DC:D5:8F:A7:75:25:F0:65:91:DE:9A:07:AA:B9:2A:46:EB
            X509v3 Authority Key Identifier:
                keyid:14:DE:86:DC:D5:8F:A7:75:25:F0:65:91:DE:9A:07:AA:B9:2A:46:EB
                DirName:/CN=Docker Machines # CA
                serial:8A:81:A6:BD:50:E6:23:33

            X509v3 Basic Constraints:
                CA:TRUE
            X509v3 Key Usage:
                Certificate Sign, CRL Sign
    Signature Algorithm: sha256WithRSAEncryption
        3e:4b:39:a6:f0:e0:26:00:fc:30:34:48:bb:b9:89:79:ba:82:
        7b:f7:8b:6c:2f:b0:1f:5a:c3:b3:00:f3:d0:8b:32:f0:e8:12:
        06:02:ec:c0:6b:13:47:dc:f3:fc:f7:d1:55:84:d1:63:9f:52:
        d3:fd:f2:03:06:92:28:0a:e4:3c:ea:c7:1f:4c:a2:76:a6:28:
        27:da:9e:ce:84:96:36:95:d2:1d:de:2f:f1:98:f6:98:1e:a7:
        09:71:ab:40:33:a2:90:71:18:79:ee:c7:98:10:54:8c:7a:3b:
        34:6e:40:67:b7:d4:83:c1:99:63:ee:e6:5b:df:e1:45:29:98:
        20:37:db:b4:19:b9:ab:9c:24:28:b4:4c:ab:03:94:fa:b8:fd:
        10:ac:79:b0:81:d8:66:db:72:c4:d4:e2:aa:c0:80:3d:1d:2b:
        71:e7:bc:8a:16:54:d5:3b:d3:1e:33:70:a4:0a:ef:5c:52:92:
        9e:d9:2b:d0:fe:f1:4a:62:a3:b7:d6:74:59:a8:03:ac:f7:2a:
        39:54:59:ee:45:91:09:35:64:5a:94:24:52:56:a9:eb:3b:bb:
        12:49:1c:71:49:72:b7:ac:82:2d:d4:d8:f3:88:aa:11:4e:af:
        99:b5:5b:14:10:2a:a6:94:b0:33:ca:fb:b0:42:f9:8f:79:48:
        97:c7:14:7c

Please advise if I should close the issue.

Thanks @valentinbud
Please leave it open - we would like to look into that.
Any chance you can send one of these EV certificates you would generate from your setup?

@dmp42 of course. I have already posted one above, the one with CN index.XXX.YYY. I would rather not disclose the real domain name.
 Please read our CPS before thoughtfully deciding to put your trust in us. Cortex AG (c) thanks you for your cooperation.

            Authority Information Access:
                CA Issuers - URI:http://pki.XXX.YYY/crt/hostsca.p7b
                OCSP - URI:http://ocsp.XXX.YYY

    Signature Algorithm: sha256WithRSAEncryption
        3a:23:5e:34:05:98:d6:7a:db:52:66:01:61:76:e3:00:40:f2:
        68:54:e6:c7:1c:95:80:38:68:64:b4:1e:67:60:b0:59:07:fd:
        11:71:90:b4:a1:45:53:4e:d1:b4:98:46:79:13:54:b7:f5:1b:
        e1:80:26:4d:14:73:c6:f4:8e:0b:d2:28:4b:48:40:20:4f:d5:
        f0:7b:41:49:cc:3d:d4:cc:3f:5c:80:ed:f3:60:86:a3:ca:5e:
        45:7c:fb:99:13:af:eb:bb:1c:42:61:08:27:2f:28:2a:f7:36:
        b9:61:be:fb:4e:97:27:d0:bc:71:0b:c6:c6:ca:cb:d5:d9:30:
        7a:9e:f5:ac:e0:dd:50:f3:40:fe:0d:c2:6d:2a:fb:c4:14:bf:
        16:18:61:02:a4:9e:58:66:9e:28:a7:c9:bd:b6:f7:ff:f5:0a:
        36:80:b1:59:1b:6f:71:ef:24:38:71:7b:89:37:c2:31:97:c6:
        47:48:29:50:96:26:61:f4:65:f1:0e:a3:7a:b0:aa:ba:f7:ad:
        65:d1:25:bb:1e:58:e9:36:86:ef:d7:ad:e0:d8:c2:87:77:a7:
        f8:c1:ad:b4:d3:d7:21:dd:cb:93:f2:db:13:fd:94:e6:19:8d:
        3a:fb:e9:d2:8c:d8:30:09:c3:d0:d5:df:45:8c:b9:99:27:3c:
        c0:82:11:5e

I can also post the Root CA and the Hosts CA if required. Thanks :).

Thanks @valentinbud
@dmcgowan / @BrianBland can you take it from there?

xref https://github.com/golang/go/issues/19933


fix(postgres): allow rust_decimal::Decimal in PgRange

I'm about to test if this works, but it should be fine, I believe, who knows!
I wish there weren't two decimal crates.

You could add a type test here: https://github.com/launchbadge/sqlx/blob/master/tests/postgres/types.rs#L429

Great, thanks!


Carbon Tutorial Step-3, GraphQL query REPO_TABLE, fails with 502

Step-3 of the Tutorial, https://v10.carbondesignsystem.com/developing/react-tutorial/step-3/#query, sets up the following gql query:
const REPO_QUERY = gql`
  query REPO_QUERY {
    # Let's use carbon as our organization
    organization(login: "carbon-design-system") {
      # We'll grab all the repositories in one go. To load more resources
      # continuously, see the advanced topics.
      repositories(first: 75, orderBy: { field: UPDATED_AT, direction: DESC }) {
        totalCount
        nodes {
          url
          homepageUrl
          issues(filterBy: { states: OPEN }) {
            totalCount
          }
          stargazers {
            totalCount
          }
          releases(first: 1) {
            totalCount
            nodes {
              name
            }
          }
          name
          updatedAt
          createdAt
          description
          id
        }
      }
    }
  }
`;

This fails in the POST to api.github.com/graphql with 502 Bad Gateway.
Using the GraphQL Explorer, the query failed in a similar manner, though the 502 wasn't surfaced there.   Only by removing the releases property,
   releases(first: 1) {
            totalCount
            nodes {
              name
            }
          }

was I able to get it to work.

Hi @rcbell, thanks for reporting this. We fixed this as part of updating the tutorial for v11. The current version of the tutorial can be found here. Our intent is to deprecate/remove the v10 tutorial soon. Hope this helps shed some light on the situation


fix: event StreamStateChanged use bool instead of String

@Grummfy , v5.0.0+4 has been released with your PR incorporated.


Update clients.md

Fix instructions for using SSMS

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

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

#signoff

#sign-off

#sign-off


Patch rabbitmq-delayed-message-exchange

Old versions of this package didn't have the version constrained properly, so it would install incompatible plugin versions into newer rabbitmq installations.
Checklist

[x] Used a static YAML file for the patch if possible (instructions).
[ ] Only wrote code directly into generate_patch_json.py if absolutely necessary.
[x] Ran pre-commit run -a and ensured all files pass the linting checks.
[x] Ran python show_diff.py and posted the output as part of the PR.
[x] Modifications won't affect packages built in the future.

Output of show_diff.py:
================================================================================
================================================================================
linux-armv7l
================================================================================
================================================================================
win-32
================================================================================
================================================================================
linux-ppc64le
================================================================================
================================================================================
osx-arm64
================================================================================
================================================================================
linux-aarch64
================================================================================
================================================================================
noarch
================================================================================
================================================================================
win-64
================================================================================
================================================================================
osx-64
osx-64::rabbitmq-delayed-message-exchange-3.10.2-h694c41f_0.tar.bz2
osx-64::rabbitmq-delayed-message-exchange-3.10.0-h694c41f_0.tar.bz2
-    "rabbitmq-server >=3.8.16"
+    "rabbitmq-server >=3.10.0,<3.11"
osx-64::rabbitmq-delayed-message-exchange-3.11.1-h694c41f_0.tar.bz2
-    "rabbitmq-server >=3.11.0"
+    "rabbitmq-server >=3.11.0,<3.12"
osx-64::rabbitmq-delayed-message-exchange-3.9.0-h694c41f_0.tar.bz2
-    "rabbitmq-server >=3.8.16"
+    "rabbitmq-server >=3.9.0,<3.10"
================================================================================
================================================================================
linux-64
linux-64::rabbitmq-delayed-message-exchange-3.9.0-ha770c72_0.tar.bz2
-    "rabbitmq-server >=3.8.16"
+    "rabbitmq-server >=3.9.0,<3.10"
linux-64::rabbitmq-delayed-message-exchange-3.10.0-ha770c72_0.tar.bz2
linux-64::rabbitmq-delayed-message-exchange-3.10.2-ha770c72_0.tar.bz2
-    "rabbitmq-server >=3.8.16"
+    "rabbitmq-server >=3.10.0,<3.11"
linux-64::rabbitmq-delayed-message-exchange-3.11.1-ha770c72_0.tar.bz2
-    "rabbitmq-server >=3.11.0"
+    "rabbitmq-server >=3.11.0,<3.12"

This matches the eight released packages (before it was fixed in the 3.12 version of the feedstock)

Is there anything extra I need to do here?


Sidebar item .active

There does not seem to be an active class that working in the sidebar menu?

Hello,
We have managed .active class code in our admin theme. Please refer to the below link:
http://propeller.in/templates/admin-dashboard/index.html
Else you can also include below code snippet in your template to add .active class:
$(document).ready(function() {
  var sPath=window.location.pathname;
  var sPage = sPath.substring(sPath.lastIndexOf('/') + 1);
  $(".pmd-sidebar-nav").each(function(){
  $(this).find("a[href='"+sPage+"']").parents(".dropdown").addClass("open");
  $(this).find("a[href='"+sPage+"']").parents(".dropdown").find('.dropdown-menu').css("display", "block");
  $(this).find("a[href='"+sPage+"']").parents(".dropdown").find('a.dropdown-toggle').addClass("active");
  $(this).find("a[href='"+sPage+"']").addClass("active");
  });
});

Please let us know if this solution worked for you.

Hi @sunil-digicorp
I was trying to say that the class .active does not exist in the default template. This means I would have to add the admin template to my project which I don't want to do.
I think you should add it to the standard template, since you have sidebar there and it's weird not to have an active state for a menu.

Hello,
Your point is noted. We will include in out next release.


Cant input Chinese in comment

hi bro , i found u r script in highend3d.com, i found i cant input chinese in comment , i searched, maybe the problem is QT5 ? or the hotkey conflict ? if u could solve the problem ,it's nice. Japanese neither.
well, i could ctrl-c ctrl-v the chinese in inputbox ,then it's display is right.
I also change some code , now  u just use pen fill all the key frame space. because the color overlay , it's hard to tell the keyframe (red) , so i just draw one line in the top.
here is where i modified in draw func
    # setup painter and pen
    painter = QPainter(self)
    pen = QPen()
    pen.setWidth(5)

    # draw Lines for each frame
    for f, c in zip(self.frames, self.colors):
        pen.setColor(QColor(c[0], c[1], c[2], 50))

        # calculate line position
        pos = (f-self.start+0.5) * self.step + (self.total*0.005)
        line = QLineF(QPointF(pos-5, 0), QPointF(pos+5, 0))

maybe u could make it better

https://www.highend3d.com/maya/script/colorkey-for-maya
here is a script that can change the keyframe color , i think it's also good ,but it's not compatible maya2017,maybe it's a good reference


nodal_data and elemental data show type MeshDataT -> docs don't show what data is available.

Duplicate


Program compiles but fails to execute

The following code compiles successfully on the latest compiler version (0.1.9 932a6360) but when running the program simply exits with an error code of 1. There are no error messages shown even in verbose mode:
use core {println}
use core.iter
use core.string

main :: () {
    iter.as_iter(string.split("hello\nthere", '\n')) |>
        iter.map((g) => println(g));
}

Running this in the Try Onyx playground causes an error "CompileError: wasm validation error: at offset 59234: popping value from empty stack".

Looks like there is an issue when the mapping function returns void, like println does. This should probably either error or it should be handled properly

This issue has been resolved with a better compiler error in #75.


[VL] Add BufferedOutputStream to track the memory usage in PrestoSerializer

A follow-up PR of https://github.com/apache/incubator-gluten/pull/5675
Discussion: https://github.com/apache/incubator-gluten/pull/5675#discussion_r1602744985

@kerwin-zk Could you help to review commit https://github.com/apache/incubator-gluten/pull/5785/commits/8efc88258c6274205efc6ef3bec4bb6064ba995b ? Thanks!


JDBC gives inconsistent date values for their years 1600 or below

To reproduce the issue

Create a table and populate two dates including years of 1500 and 1600 on MAPDQL
CREATE TABLE t_date(id SMALLINT, val DATE);
INSERT INTO t_date VALUES(1, '1500-01-01');
INSERT INTO t_date VALUES(2, '1600-01-01');

Run the SQL stmt against MAPD
SELECT * FROM t_date ORDER BY id;

Run the SQL stmt against MAPD thru JDBC
SELECT * FROM t_date ORDER BY id;

Data Results from No. 2
id|val
1|1500-01-01
2|1600-01-01
Data Results from No. 3
id|val
1|1499-12-23
2|1600-01-01
Explanation
Noticeably, JDBC displaying the date for the row 1 is not the same as MAPD.  JDBC displays "1499-12-23" as supposedly matched with "1500-01-01" from MAPD DB.  Does this difference tell JDBC doing date validation than MAPD?
According to NOSQL's document, the range for the Date datatype is from 1000-01-01 to 9999-12-31.  Is that correct?

@dwayneberry Do you think the JDBC functionality for datatype displays should be identical to MAPD?

@njmarshall we are in the weeds here.  Are you familiar with the 'Council of Trent'.  The calendar under went modifications in this time period to readjust.

Sorry didn't mean to close it.

I'm not sure where we would stand regarding UTC to pre "Council of Trent" definitely a conversation to be had over a beer :-)

Yes, my purpose is to find anything necessary to be fixed, improved or upgraded for rising a level of the software quality.


[DNM] test the (new) ESMValBot

Please don't merge (yet!). This is a sandbox to test the new ESMValBot :robot:

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

OK, progress, little bot! Now we can actually get a recipe run log and all - https://esmvaltool.dkrz.de/shared/esmvaltool/esmvalbot-output/test_esmvalbot-m2n7emhc/recipe_python_20241024_111539/run/main_log.txt - still no access to the data perse, but am in horly contact with DKRZ via Carsten :beer:

@esmvalbot you're a cutiepie, you and @bouweandela that is :laughing:

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

@esmvalbot please run examples/recipe_python.yml

yess you itty crappy bot, welcome back to life!!

ESMValBot is happy to report recipe examples/recipe_python.yml ran OK, output has been generated here

@bouweandela check that sweet message :robot: :heart:

@esmvalbot please run monitor/recipe_monitor_with_refs.yml

ESMValBot is happy to report recipe monitor/recipe_monitor_with_refs.yml ran OK, output has been generated here

thanky bot

OK @schlunma @bouweandela I have now set the following in the Bot's config-user:
output_file_type: png
save_intermediary_cubes: false (done yesterday)
remove_preproc_dir: true

gonna take it for another spin now

@esmvalbot please run monitor/recipe_monitor_with_refs.yml

OK we have plotty-plots and no more preproc dir in the Bot's output:
[b382109@esmvaltool4 ~]$ ls -la /mnt/esmvaltool_disk4/shared/esmvaltool/esmvalbot-output/test_esmvalbot-m2vtrybr/recipe_monitor_with_refs_20241030_120356/
total 56
drwxr-xr-x.  5 esmvalbot ik1017    60 Oct 30 13:12 .
drwxr-xr-x.  4 esmvalbot ik1017    66 Oct 30 13:03 ..
-rw-r--r--.  1 esmvalbot ik1017 43744 Oct 30 13:12 index.html
drwxr-xr-x. 10 esmvalbot ik1017  4096 Oct 30 13:12 plots
drwxr-xr-x. 10 esmvalbot ik1017  4096 Oct 30 13:12 run
drwxr-xr-x. 10 esmvalbot ik1017  4096 Oct 30 13:12 work

Perfect!!

we now have the autoPR to test the Bot, closing this :robot:


upgrade-ert fails for while downloading stemcells

Last night while trying to upgrade to Elastic Runtime 1.10.11, my pipelines (0.14.1, 1c90ccc7c4883a3d8ec2ccab23dcf23e120bc6e6) failed in the wait-opsman-clear  task with the following error:
Could not login to ops man
could not execute "curl": failed to make api request: failed submitting request: token could not be retrieved from target url: Post https://https/uaa/oauth/token: dial tcp: lookup https on <IP_ADDRESS>:53: no such host

It would appear that the task has changed incompatibly with existing pipelines and since the pipelines always look to the latest commit, most previously released versions of pcf-pipelines are now unusable.

This is due to a change in how the opsman URI is specified in the params, as per https://github.com/pivotal-cf/pcf-pipelines/commit/48ffc5ab2351aadf361a92b0d4a569e785b384f4
If you remove the protocol from the URI it should work. Re-open this issue if it does not.

Also, the Github release is not pegged to any specific version, unlike the Pivnet release. That means it will move ahead while your pipeline falls behind.
This is a known issue but that we have no pressing concern to address as the Github release isn't the official release; the Pivnet one is.


Remove: Splashtop.SOS version <IP_ADDRESS>

## Direct URL for Version does not exist, version is no longer latest

[X] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

Bump


clone tasmota flasher, change partitions, rename, update tool

Build of windows/ubuntu and macOS is gh-action, but not automatically relaesed. Partitions are taken online from the partitions folder.

yippy!

The binaries are stored under Artifacts on this page: https://github.com/emsesp/EMS-ESP-Flasher/actions/runs/3364151868
You eed to copy them to a new release, otherwise people don't find them.

You eed to copy them to a new release, otherwise people don't find them.

why can't you do this?

Here i have no access. I tried automatic release, but get unspecified errors and dont want to spend hours to figure out what is wrong for copying 3 files.

ok, strange. You should have full rights to the EMS-ESP organization. I'll check & fix

done. https://github.com/emsesp/EMS-ESP-Flasher/releases/tag/v1.0.0


Bug: Keyword text is not taken as keyword when letters are entered as value

The rule "Convert upper and lower case" is not working correctly for keyword "text", if the value has any letter in it.
Imagine two situations:
WRITE text-042
WRITE text-a42
For  the first one "text" will be converted to "TEXT" with default setting.
But in the second case "text" is not converted.
IMHO this is bug as Pretty Print converts it to upper case and abaplint reports it as error if not converted.

Hi Jan,
thanks for reporting this!
For some background: Code bits that aren't separated with a space – such as lo_any_instance->any_method( or ms_struc-component-subcomponent – are usually stored in one single token in ABAP cleaner, because except for display colors, there is no reason to ever tear them apart. In this case, however, some special processing was needed, because TEXT-a42 contains both a keyword and an identifier (unlike the other examples above).
The issue will be fixed in the next release, and coloring is now also adjusted to ADT:

As in ADT, the result depends on the settings for keywords and identifiers, so you could also get:

Kind regards,
Jörg-Michael

Hi Jan,
thanks again for opening this issue! This should now be fixed with version 1.5.3, which was just released.
Kind regards,
Jörg-Michael


Cache hasColumn response in crud->addColumn

Proposal
In CRUD method addColumn does not cache \Schema::hasColumn response. It should be cached.
What happened:
In query log I see many repetitive queries like
select column_name as  column_name from information_schema.columns where table_schema=...
Backpack, Laravel, PHP, DB version:
Backpack 3.3.0, L5.5, PHP 7.1

#923

Hi @diskortsev ,
We've introduced some sort of caching for hasColumn()  in an update, a while back. It is now:
    protected function hasColumn($table, $name)
    {
        static $cache = [];

        if (isset($cache[$table])) {
            $columns = $cache[$table];
        } else {
            $columns = $cache[$table] = $this->getSchema()->getColumnListing($table);
        }

        return in_array($name, $columns);
    }

So it will make a query to see if it has the columns, but only once.
Hope this is what you were looking for.
Thanks, cheers!

@tabacitu, thank you! The code is what I expected.
Will update my installation later and check it.


test env added for 3 submodules of ifu

Description
For this pr, I have set up several test environments for three sub modules of IFU, including PreDecode, F3Predecoder and FrontendTrigger. Moreover, some smelly code has been changed in PredChecker.
Changes related to concerning modules are listed as follows:
add files in those modules:
ut_frontend/ifu/predecode: test environment built, add bundle, agent and env wrapping predecode.
ut_frontend/ifu/f3predecoder: test environment built, add bundle, agent and env wrapping f3predecoder.
ut_frontend/ifu/frontend_trigger: test environment built, add bundle, agent and env wrapping frontendTrigger.
scripts: add build script support for predecode, f3predecoder and frontend_trigger
change content in those modules
ut_frontend/ifu/pred_checker: fixed known document problems; change some smelly code
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update
[x] This change makes change to code style

How Has This Been Tested?
make test target=path/to/testdir
For this case, ut_frontend/ifu/predecode and ut_frontend/ifu/rvc_expander will do
Test Configuration:
toffee: latest version
toffee_test: latest version
Checklist:

[x] My code follows the style guidelines of this project
[x] I have added the appropriate labels
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

finished then


[Feature]: disable ts-node

🚀 Feature Proposal
Add an option in Jest (maybe via a env variable) to disable enabling ts-node.
Another option would be to disable the typecheck in ts-node in https://github.com/jestjs/jest/blob/70b17d2e3d2bf40dd27fecdcdd06c159d26a7c6c/packages/jest-config/src/readConfigFileAndSetRootDir.ts#L116-L122 (with transpileOnly: true)
Motivation
In one of my projects, I use jest from a script already coded in TS and thus that already has ts-node started.
And applying a second time within jest throws TS errors
Example
No response
Pitch
ts-node is directly called by the internal of jest so we cannot be modified otherwise

Not stale


seccomp: enable bpf in unprivileged containers

Thing's aren't normal on Linux anymore and we have users that want to run bpf
in unprivileged containers. This is of course completely opt-in and not to be
used lightly.
This patch makes it possible for LXD to manage the bpf() syscalls of an
unprivileged task in a container.
For a start, this enables support for BPF_PROG_TYPE_CGROUP_DEVICE program types
and BPF_CGROUP_DEVICE attach and detach types. This serves as a POC that it is
possible to manage bpf programs for a task running in an unprivileged
container.
I expect this to be extended in the future should users have a need for it.
There are a several ways we could extend this:

supporting more program types
supporting maps of pre-compiled or pre-written bpf programs instead of
loading the container's own

Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

Can you split things some more?
We're not going to be backporting this to 4.0 but things like changing the function signatures or adding detection for the notify fd feature, this we could backport.

Can you split things some more?
We're not going to be backporting this to 4.0 but things like changing the function signatures or adding detection for the notify fd feature, this we could backport.

Done.

Testsuite passed


Unsorted lists are NOT QUICK OR EASY!

In what universe is an unsorted list that you cannot sort 'easy'?!

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

ID: 9cbbd8f5-8155-0057-b0cc-0b96ee35aad4
Version Independent ID: 8b085f6d-05f3-e213-6b2a-3f7274581111
Content: Install and manage packages in Visual Studio using the NuGet Package Manager
Content Source: docs/consume-packages/install-use-packages-visual-studio.md
Service: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

Microsoft, you are the very definition of PEBKACs.
Please keep this ticket open, age is irrelevant, this is fundamental less than first year computer science.
Sort your lists or don’t have them.  Also if I search newtonsoft, why don’t you return the main simple project?  Why do you return only sub or related projects??
From: github-actions[bot] @.>
Sent: Thursday, May 30, 2024 12:19 PM
To: NuGet/docs.microsoft.com-nuget @.>
Cc: Daniel Gavin @.>; Author @.>
Subject: [External]Re: [NuGet/docs.microsoft.com-nuget] Unsorted lists are NOT QUICK OR EASY! (Issue #3237)
Thanks for sharing your feedback. We apologize for our delayed response. Due to the sheer volume of feedback in our repo, we have decided to prioritize the newest issues and are automatically closing our oldest issues with an Issues bot. If you believe your feedback is still actionable, then either respond directly in this issue or open a new documentation issue and we’ll review. If no activity occurs in the next 14 days, this issue will be closed.
—
Reply to this email directly, view it on GitHubhttps://github.com/NuGet/docs.microsoft.com-nuget/issues/3237#issuecomment-2138450961, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BEPPBVBQE5ZDZFV7RKX3YFLZEZV63AVCNFSM6AAAAABDHOZLWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGQ2TAOJWGE.
You are receiving this because you authored the thread.Message ID: @.***>

Very sorry for the delayed response. We are phasing out GitHub issues as the feedback mechanism on documentation content and replacing it with a new feedback system. If you believe your feedback needs to be addressed, please submit a PR, or use the Feedback link on the article, or copy the content here to a new issue at https://github.com/NuGet/Home/issues

New issue logged.


Change "Work" label to "Occupations"

Problem Description:
The data is being parsed and returning "Work" as the primary name.
Expected Behavior/Solution:
If the label for "work" is caught in the frontend return "Occupations" instead.
Requirements:

[x] Add conditional to change work to occupations in getAllClassifiedAs function in the PersonAndGroupParser

   if (label === config.dc.occupation) {
      label = 'Occupation'
   }

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Wireframe/Mockup - Mike
[ ] ~Committee discussions - Sarah~
[ ] ~Feasibility/Team discussion - Sarah~
[ ] ~Backend requirements - TBD~
[x] Frontend requirements - Kam
[ ] ~Questions~

UAT/LUX Examples:

https://lux-front-dev.collections.yale.edu/view/person/4dc53d61-37e7-4a69-a05a-dbb8ce23c75f
Navigate down and on the right-hand side, you will find the listing Occupation.

Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:

Bugherd: https://www.bugherd.com/projects/284041/tasks/2008

Wireframe/Mockup:
Current:

Expected:

Approved per UAT

deployed


Fix issue #122

Hi,
I've undone the portion of f68fcae that seems to have broken things for me as commented in #122.  I haven't seen much action on the issue so I'm still not sure if its something weird for me, but I think that my particular changes are the more robust solution.
Also, I merged my fork up to the 2.9 commit and made the change off of there; however I didn't bother making a fix branch since the fork is basically the same thing (a branch of the same name) but if you'd prefer I can branch at 2.9 and make the change.  Also I didn't see any tag or existing branch for 2.9 so I just grabbed the commit in the history; again let me know if there's a better place to branch off from.
Thanks,
\Peter

Thanks for the pull request, I'll pull this in, I'm standing on the edge of a pretty big release right now, so I'll have to look carefully at this.
I'm pretty sure this isn't the correct solution, but you're not the only one with asset pipeline problems, so I'll experiment, and report back here with my progress.


Can't add depiction of accession book images

When I go to a collection object tagged with what was originally an accession code "e.g. a single label with a number that referred to a handwritten accession book data entry instead of a fully written label"
Then I want to see the depiction of the scanned accession book image (e.g. https://www.biodiversitylibrary.org/item/253124#page/26/mode/2up) as a depiction of the label of that specimen or of the original collecting event.
But I cannot get to the identifier itself to add a depiction.

Blocked by #1163 I think.

@mjy this was closed by adding metadata depictions. Close?

@tmcelrath Yes, I think so, display/other issues are covered in #1163.


BUG- Expandable not working properly with Python API

Description
If the user tries to create an expandable, they will not be able to expand or close this expandable. The user has to provide a title property to the expandable to make it possible. Note this property doesn't exist in the documentation.
How to reproduce
from taipy.gui import Gui
import taipy.gui.builder as tgb

with tgb.Page() as page:
    with tgb.expandable("Not working", expanded=False):
        tgb.text("The user cannot expand/close the expandable section")

    with tgb.expandable(value="Not working", expanded=False):
        tgb.text("The user cannot expand/close the expandable section")

    with tgb.expandable(title="Working"):
        tgb.text("The user can expand/close the expandable section")

Gui(page).run()

Expected behavior
We should either document this property or the two first examples should work as described in the documentation.
Runtime environment

Taipy version: 3.1

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Create related issue in taipy-doc for documentation and Release Notes if relevant

This is a doc issue and will be fixed and propagated to both develop and 3.1

Great! Will the default property of the expandable also change then?

Will the default property of the expandable also change then?

No


Search Bar in menu: Killer feature everybody wants!!!

can you please try to introduce a search bar on the menu to search based on contained string?
I already did by myself in a fork (https://github.com/vivi7/Clipy/tree/feature/search-bar) when I started as mobile ios dev, actually that code is so old and I don't have too much time to dedicate on it. so if you want I can work again on it, but if you already have in the roadmap please let me know. anyway depends also if you are going to accept this kind of feature ai'm asking.
Thanks

hear, hear !

I guess duplicate of ye old. https://github.com/Clipy/Clipy/issues/88
It would be nice if you chip in your +1 to that one too, have all requests in one makes it more clear.


Auto generate an SEO image for blog posts that don't have any

No, it's not in there, it doesn't work without this line https://github.com/subvisual/subvisual.com/pull/461/files#diff-f9ba7ecf60ea5af1dae0abe92b1909c94ace3aa290b376f41b35573f1d02203fR6


Add Linked List question of Striver SDE Sheet in Java

Middle of the Linked List
Merge Two Sorted Lists
Delete Node in a Linked List

Add your here under the Linked List package
Important:

Create a package for each question
And create a README file for each question, which will consist of the problem link, and time complexity and you have to write the approach towards the solution (both brute force and optimal one)

I want to do these plz assign me

Pls assign this to me @aritra-tech

Sure


Progresssion page still on the previous journal

When we index a second journal file the progress page show the previous indexing journal status.
The reproduction scenario is not precise yet.

Additional information :
This problem seems occur when the web socket connection is lost.

The front end has been fixed :

a change in the progression page (there a bad management in case of web socket disconnected).
the web socked has been improved to retry reconnection every 5 seconds in case of disconnection.

Done.


Problem with font and line rendering

The Problem:
It seems that in some cases, the line that is drawn on the top and bottom doesn't completely cover some glyphs. This is best illustrated with the following screenshot generated from the config below:

As you can see (probably only after opening the picture in fullscreen), in the right powerline symbol, the leftmost side of it is not covered by the line, even though everything else is.

;Example config

[colors]
background = #ffffff
background-light = #3b4252
background-alt = #144133
foreground = #d7ffd7
foreground-alt = #88c0d0
highlight = #39c6fe
secondary = #e60053
alert = #bf616a
alert2 = #ebcb8b

;==============================
;		BARS
;==============================

[bar/example]
; comment line below if you only have 1 screen
monitor = ${env:MONITOR:HDMI-1}
;monitor = ${env:MONITOR:eDP-1}

width = 100%
height = 32
fixed-center = true

background = ${colors.background}
foreground = ${colors.foreground}
line-size = 4
line-color = ${colors.highlight}

font-0 = "Fura Code Nerd Font:size=22;3"
font-1 = "Misc Termsyn:size=12;2"

; desktop PC modules
modules-center = xwindow

;==============================
;		MODULES
;==============================
[module/xwindow]
type = internal/xwindow

format = <label>
label = %{F#144133}%{R F-}%{T2}%title%%{R B-}
;label-maxlen = 75

format-foreground = ${colors.foreground}
format-overline = ${colors.background}
format-underline = ${colors.background}

The polybar log doesn't output anything.
Environment:

WM: i3
Distro: Arch Linux
Output of polybar -vvv:

polybar 3.3.1

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) -render -damage -sync +composite +xkb +xrm +xcursor

Build type: RelWithDebInfo
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wall -Wextra -Werror -Wno-noexcept-type -pedantic -pedantic-errors
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

Thank you for your hard work!

Hmm. I was able to reproduce this kind of (that vertical line is on the left powerline glyph for me). Don't really know what causes it, but was able to fix it by disabling anti-aliasing for the powerline font. Could you also try that?

Also have this problem with the Droid Sans Mono family fonts.
Option :antialias=false does not help
With Droid Sans font problem is gone.

Should be fixed by #2802


setPrefs error when called with a JSON array value for a JSON preference

The setPrefs endpoint will throw if a JSON array is provided for a JSON preference, looks like it is coded to only handle JSONObject types instead of looking for the base JSONElement type after parsing the new preference value.

Looks like John fixed this, and we simply never closed this bug!


Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python)

Found this error recurring in my Supervisior-Log:
2024-07-23 19:50:49.680 WARNING (MainThread) [supervisor.addons.options] Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python) (bf995ce7_saic_python_mqtt_gateway)
2024-07-23 19:51:24.598 WARNING (MainThread) [supervisor.addons.options] Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python) (bf995ce7_saic_python_mqtt_gateway)
2024-07-23 19:55:49.681 WARNING (MainThread) [supervisor.addons.options] Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python) (bf995ce7_saic_python_mqtt_gateway)
2024-07-23 20:00:49.680 WARNING (MainThread) [supervisor.addons.options] Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python) (bf995ce7_saic_python_mqtt_gateway)
2024-07-23 20:05:49.680 WARNING (MainThread) [supervisor.addons.options] Option 'SAIC_URI' does not exist in the schema for SAIC MQTT Gateway (Python) (bf995ce7_saic_python_mqtt_gateway)
Use the actual implementation of SAIC MQTT Gateway (Python) Current version: 0.6.2. Any idea where that comes from? The AddOn itself does not contain any errors in the Logfile.

If i open the Configuration in YAML then there is an entry SAIC_URI: https://tap-eu.soimt.com. Which seems correct. But still has the errors in the Log.

SAIC_URI has been removed in the latest version of the python mqtt gateway and can be safely removed


work with dates in the same way independent of local timezone

Steps to reproduce:

sudo timedatectl set-timezone US/Eastern
cp samples/* ./
npm start
Expected:
'input.xlsx 2021-06-01 2021-06-30' in console
Actual:
'input.xlsx 2021-06-02 2021-07-01' in console

Should be the same as expected in all timezones, US/Eastern and EET e.g.


node: ignore kvstore node events for the local node

Let's not propagate node updated/deleted events received from the kvstore for the local node to the NodeManager. This matches the behavior of the corresponding CiliumNode watcher, and prevents the unnecessary increase of the ipcache_errors_total (cannot_overwrite_by_source) metric, caused by information with source=local always taking precedence.

Ignore kvstore node events for the local node, to avoid unnecessarily increasing the ipcache_errors_total (cannot_overwrite_by_source) metric.

/test


Copy paste bug in slider attribute = this.MaxValue = minValue;

https://github.com/dbrizov/NaughtyAttributes/blob/b933f7e5698e7e57499f4b65839de18990d19f5b/Assets/NaughtyAttributes/Scripts/Core/DrawerAttributes/SliderAttribute.cs#L19

Oh, thanks. I will fix it when I get home

Already fixed some time ago, don't remember the revision


⚠ Bofrost.de has degraded performance

In 30308c8, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1283 ms

Resolved: Bofrost.de performance has improved in 6c2af9b.