Unbound: excessive private-address entries.

Currently Unbound in OPNsense does not allow to query spamhaus/spamcop (and others) DNSBLs. That's because of entry private-address: <IP_ADDRESS>/8' that was added at https://github.com/opnsense/core/commit/fd00370ab1830b1ea2d98f808f4b7386569feee5
That was a paranoid solution from https://forum.opnsense.org/index.php?topic=1416.0 that breaks RFC and it's effect is noted in unbound.conf(5) man.
Section "private-address:  " clearly states:

Turning on <IP_ADDRESS>/8 would hinder many spam- blocklists as they use that.

That problem was raised a few times but no answer from developers was given. ( https://forum.opnsense.org/index.php?topic=9633.0 and https://github.com/opnsense/core/issues/1783 )
Is it possible to remove that entry from configuration or add a way to override that entries completely? Manual editing of configuration on each update is not a good way to allow DNSBL requests.

I'm not sure how paranoid it is if multiple projects are doing it independently: https://github.com/pfsense/pfsense/commit/afeb18ff0ec https://redmine.pfsense.org/issues/9708 even if it takes a while to land in other projects.
You can use Dnscrypt-proxy or Bind to do the filtering, see https://docs.opnsense.org/manual/how-tos/dnscrypt-proxy.html and https://docs.opnsense.org/manual/how-tos/bind.html and both explicitly work fine with Unbound.
Cheers,
Franco

That's a recent commit for pfsense and they will discover that problem soon.
There should be a toggle in settings for entries that could cause such problems.

Is there anything else we can help you with? I'm unsure what to do, because we're not simply removing a line that was put in for a reasons without a proper replacement strategy.

There is no way to do that without removing a line or adding a toggle for administrator to disable that check.
I'll just switch to another dns server in that case.

Ok. I've mentioned "proper replacement strategy" here to indicate that nothing is set in stone, but a toggle doesn't look very useful. It's not a fix, it's at best a workaround with real world security implications.
@mimugmail wants to build an adblocker into unbound via plugin so I guess that would be a better course of action in the midterm.

@mimugmail wants to build an adblocker into unbound via plugin so I guess that would be a better course of action in the midterm.
That's not a solution. Not even a workaround.
Spamhouse, spamcop and other DNSBLs that people use in mentioned threads are used for mail antispam protection by Microsoft Exchange's antispam,  rspamd and other antispam filters. That is not similar to dns adblockers.

That's not a solution. Not even a workaround.
Spamhouse, spamcop and other DNSBLs that people use in mentioned threads are used for mail antispam protection by Microsoft Exchange's antispam, rspamd and other antispam filters.

I thought I have rspamd successfully running against spamcop with Unbound ... did you really check this or did you just copy from the man page?

I've checked it. With default settings I get "No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for <IP_ADDRESS>.zen.spamhaus.org" on test requests. It returns correct 127.0.0.x addresses with correct settings.
Can you check that your rspamd uses Unbound as resolver?

I've checked it again. The only line I change in config is 'private-address: <IP_ADDRESS>/8'. First request done with default settings, second with line commented out.  I've replaced my domain name to DOMAIN.TLD.
> <IP_ADDRESS>.zen.spamhaus.org
 Server: routersrv.DOMAIN.TLD
 Address: <IP_ADDRESS>
 *** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for <IP_ADDRESS>.zen.spamhaus.org

> <IP_ADDRESS>.zen.spamhaus.org
 Server: routersrv.DOMAIN.TLD
 Address: <IP_ADDRESS>
 Non-authoritative answer:
 Name: <IP_ADDRESS>.zen.spamhaus.org
 Addresses: <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>

A possible solution would be to add a editable list of domains which are allowed DNS-Rebinding.
The administrator could then just add the DNSBL domains which are used to this list.
This can be implemented by adding private-domain entries for the domains on this list.
@fichtner Would this be a proper replacement strategy?

@ruffy91 how would this look like in unbound config?

From https://nlnetlabs.nl/documentation/unbound/unbound.conf/:
private-domain:
Allow this domain, and all its  subdomains  to  contain  private
addresses.   Give  multiple times to allow multiple domain names
to contain private addresses. Default is none.
example:
server:
private-domain: sbl.spamhaus.org
private-domain: xbl.spamhaus.org
private-domain: bl.spamcop.net

This allow sbl.spamhaus.org, xbl.spamhaus.org and bl.spamcop.net and all their subdomains (= DNSBL queries) to return private IPs.

Did you try to set this in custom config?

Did you try to set this in custom config?

Yes, mail blocklists work after adding next lines to custom options field in opnsense unbound settings. First line is required.
server:
private-domain: sbl.spamhaus.org
private-domain: xbl.spamhaus.org
private-domain: zen.spamhaus.org
private-domain: bl.spamcop.net

OK, will add this feature to unbound-plus plugin. :)


Try to read characteristic value but nothing Show up

Hi, I'm a newbie to ble. I try to read a value from the characteristic UUID like battery level, device name and current time. By far
device name can be read easily without any problem but other goes south with current time and battery level the output from serial monitor look like those value can be read but nothing shows up. But I can read those values when use another phone with nRF Connect to read it, Did I need to pair with passcode before read those values??. Below is my code modified from the
https://paste.ofcode.org/ebwGi5T9p6rm6x7urcveGK

You are trying to print string, but the value is most likely not string:
Serial.println(value.c_str());

Oh! Thank you, I'll try to find ways to prints the hex value

You are trying to print string, but the value is most likely not string:
Serial.println(value.c_str());

Or this library is on development for reading hex/binary from characteristic I do some research on these issues repo and found this https://github.com/nkolban/esp32-snippets/issues/596#issue-339059560 . And I still don't know how to print those values out. By far I've read and research for readValue() function it seems that it already read values into string type and store by this command.  std::string value = pRemoteCharacteristic->readValue();
How I can read hex or binary data from characteristics? Or I need to research for something more.
Thank you.

Try to print read value length to see if there is any value.
You can print bytes with Serial.write or use ESP_LOG_BUFFER_HEX.

I try to add other command to print byte but the result is still the same.

I add this to my sketch.
if (pRemoteCharacteristic->canRead()) {     std::string value = pRemoteCharacteristic->readValue();     int j = value.length();     Serial.print("Data length = ");     Serial.println(j);     Serial.print("The characteristic value was: ");     //Serial.println(value.c_str());     for (int i = 0; i < value.length(); i++)     {       Serial.write(value[i]);     }     Serial.println("");   }
And when I try to add ESP_LOG_BUFFER_HEX("value", value, value.length()); it can't compile or maybe I use the wrong buffer pointer. If the problems is a pointer please give me some advice I still confuse with pointer

I see some discussion on https://github.com/nkolban/esp32-snippets/issues/666
but still didn't understand that notifyCallback function where does it get input from I did not see this function use any input.
this function declare with
static void notifyCallback(BLERemoteCharacteristic* pBLERemoteCharacteristic,uint8_t* pData,size_t length,bool isNotify)

here you can use that notation, because you are giving length:
ESP_LOG_BUFFER_HEX("value", value.c_str(), value.length());
so it does not matter if there is 0x0 in middle, or any non printable value, or you can do it that way:
ESP_LOG_BUFFER_HEX("value", (uint8_t*)value.c_str(), value.length());
It makes no difference here, because IIRC buffer is type of void*

here you can use that notation, because you are giving length:
ESP_LOG_BUFFER_HEX("value", value.c_str(), value.length());
so it does not matter if there is 0x0 in middle, or any non printable value, or you can do it that way:
ESP_LOG_BUFFER_HEX("value", (uint8_t*)value.c_str(), value.length());
It makes no difference here, because IIRC buffer is type of void*

it can compile but still no data coming out did I need to pair or bond before reading Battery data because I've check the value.legth() result is = 0 so I have no idea.

Anyway I use nRF Connect to emulate BLE service from my mobile phone.

Did you set any value in nRF for that characteristic?

Haha, I didn't see any setting did it should have. When hit the add service button the application only let me choose a service but have no rights to set value for it.

For sure there is option to set value, at least on android it is.

Update I've added basic security to my sketch now I have output in string form

Next step is to convert this value to hex.


OVA to VHD Conversion

Are there any official documentation on Converting OVA to VHD? As OVA is essentially a tar file holding the VMDK File and OVF (Configuration File), is there a supported conversion or method to bring these files into Azure?

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

ID: 1b9c0d7a-bbf5-eccc-f2ca-a825bf42c82f
Version Independent ID: 58aa93af-4030-1541-a14c-c66c683ccf7c
Content: Prepare a Windows VHD to upload to Azure
Content Source: articles/virtual-machines/windows/prepare-for-upload-vhd-image.md
Service: virtual-machines-windows
GitHub Login: @glimoli
Microsoft Alias: genli

Thanks for the question. We are currently investigating and will update you shortly.

@PtMcBride I could not find any official documentation on converting OVA to VHD. Please check if this post is helpful:
https://superuser.com/questions/483756/converting-a-vmdk-to-vhd/515985#515985

@PtMcBride
As discussed offline, we will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


new UI no test service in user guide - [closed]

In GitLab by @luotian-github on Sep 26, 2017, 09:59
Merges doc2 -> dev
new UI no test service in user guide

In GitLab by @wknet123 on Nov 13, 2019, 10:04
closed


Exercise 2.31 answer

I think
r1 = v2;
should be illegal since r1 is an ordinary reference while v2 is a const int.

check #494


Add callback executed when slide/fade/zoom end

Currently z-index of each slide is not set.
When you want to add button on each slide, because of z-index unset, you cannot click the button.
To resolve this issue, I added onChange props to components.
Expected usage
<Fade onChange={ (oldIndex, newIndex) => {
             // Change z-index of oldIndex to 0
             ...
             // Change z-index of newIndex to 1
             ...
           }}
      {...props}
>
...
</Fade>

@Hinaser I think an easier approach will be to do this style={{opacity: key === index ? '1' : '0', zIndex: key === index ? '1' : '0'}} on this line. Can you try that out and let me know if it worked perfectly for you?

@Hinaser
I was thinking about this and I got a little bit confused.

What changed my mind is that there may be another container whose z-index is larger than 1.

Are you saying if we have something like this

  <Fade {...fadeProperties}>

<input type="button" value="first button" onClick={this.clicked} />

<input type="button" value="second button" onClick={this.clicked} />

<input type="button" value="Third button" onClick={this.clicked} />

  </Fade>

it won't work?
I don't think that will be an issue since it's just a container, it won't stop the buttons from being clickable.

Hi @andela-foladeji
Slightly different to my thinking.
This is it.
<Fade {...fadeProperties}>

<input type="button" value="first button" onClick={this.clicked} />

  ...
</Fade>

 Some container which disturbs <Fade />.
 This container is next to <Fade /> and may overlay <Fade />.

@Hinaser ok I get that now but if someone does that is it not safe to assume that they actually want portion of the div to probably overlay the fade and I don't think that scenario will occur regularly


Zabbix not sending alerts!

Hello and thank you for this script. I am curious if I need to ask for help in here or on the Zabbix forums. I am having the same issue as above. I can walk an alert via command line but zaabbix is not sending anything else. I am currently running Ubuntu 16.04 Desktop. The slack.sh script was originally owned by a different admin user in Zabbix, but I changed it to zabbix with sudo chown zabbix:zabbix /usr/lib/zabbix/alertscripts/slack.sh I also followed the instructions step by step for the media type,user and actions. I have also tried the above to put Defaults:zabbix !requiretty in the visudo file. I create a problem for a device and I get a report on my dashboard saying the device is down but no alert shows up in slack.
Any help would be greatly appreciated!

I have honestly never heard of any one ever running Zabbix on a desktop. In any case, you might want to look at the event details for a specific problem that has occurred to see which actions were triggered by that problem.
For example, here you can see a problem triggering an action which is sending an alert to a Slack #alerts channel (via a reader Zabbix user account):

Additionally, there is no reason for you to be granting sudo access to this script at all. This is nearly the equivalent of logging in to your desktop as the root user - so do not do this.

So it sounds like I have more steps to go then other than just following your instructions.  I am new to zabbix, I was able to set it all up and pull in templates I need and modify a few things for my dashboard but I have not done anything more with triggers, events or alerts other than what is already in the templates.  So you are saying I need to make sure to build an action off the problems I am monitoring?  I just assumed that with your scripts that anything that popped up under problems would automatically send an alert to Slack, you are saying this is incorrect?

A Zabbix item value can result in a Zabbix trigger occurring. A Zabbix trigger can then result in a Zabbix action. Per the README, you need to actually configure your Zabbix installation to use the script as part of a Zabbix action:
https://github.com/ericoc/zabbix-slack-alertscript#configuration

Finally, an action can then be created on the "Actions" sub-tab of the "Configuration" tab within the Zabbix servers web interface to notify the Zabbix "Slack" user ensuring that the "Subject" is "PROBLEM" for "Default message" and "RECOVERY" should you choose to send a "Recovery message".

I have a default action setup for Slack, would this action not catch anything with a problem by hostname?

You should probably reach out to the Zabbix community via their forum or IRC channel if you're not familiar with setting up Zabbix actions:
https://www.zabbix.com/forum


[ASCII-1160] Healthprobe component

What does this PR do?

Creates the healthprobe component
Motivation

Ensure core functionality is converted into components
I've used Fx lifecycle hooks to control the start and stop of the healthpobe.
Since the healthprobe component is not require by any other component nor provides any interface function use by any agent I had to relay on using _ healthprobe.Component to force initializing it.
Also, since the pkg/api/healthprobe code has been removed I had to update their go modules dependencies
Describe how to test/QA your changes

Validate that the healthprobe still works as expected for the main agent, cluster agent, dogstastd, and system probe agent

Modify the configuration to have a dedicated health probe port health_port: "1234"
Run the agent
Hit the health probe server using curl: curl 'http://<IP_ADDRESS>:1234/live', curl 'http://<IP_ADDRESS>:1234/ready', and curl 'http://<IP_ADDRESS>:1234

/merge


Including AAR into flutter project (Android Studio)

Steps to reproduce
Hi, I'm using an our external aar package connecting to an external usb device (with some C code).
This package works perfectly in a simple Android project and I added it into flutter project with success. I able to compile and create a apk package but when I try to run app on device, I can't try to connect to the device. How can I do? is there some kind of compilations for flutter project different to a simple nativa java one?
Please help me
Thank you
Expected results
Correctly connection on usb device and work
Actual results
Connection to usb device failed
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @gingu83
Could you share a minimal sample project for this case?

I can't try to connect to the device

Could you please be more specific? Does it have any error or warning?
And what is your Flutter version? (please provide the output of flutter doctor -v) Thanks!

Hi this is the flutter doctor log
/Users/Gingu/flutter/bin/flutter doctor --verbose
[!] Flutter (Channel stable, 3.16.9, on macOS 14.0 23A344 darwin-arm64, locale it-IT)
• Flutter version 3.16.9 on channel stable at /Users/Gingu/flutter
! The flutter binary is not on your path. Consider adding /Users/Gingu/flutter/bin to your path.
! Warning: dart on your path resolves to /usr/local/Cellar/dart/3.3.0/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/Gingu/flutter. Consider adding /Users/Gingu/flutter/bin to the front of your path.
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 41456452f2 (4 mesi fa), 2024-01-25 10:06:23 -0800
• Engine revision f40e976bed
• Dart version 3.2.6
• DevTools version 2.28.5
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/Gingu/Downloads/adt-bundle-mac-x86_64-20131030/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15E204a
• CocoaPods version 1.13.0
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[!] Android Studio (version unknown)
• Android Studio at /Applications/Android Studio 3.4 Preview.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
✗ Unable to determine Android Studio version.
✗ Unable to find bundled Java version.
• Try updating or re-installing Android Studio.
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
[✓] Android Studio (version 2021.3)
• Android Studio at /Applications/Android Studio 2.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
[✓] Android Studio (version 2023.2)
• Android Studio at /Applications/Android Studio 3.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
[!] Android Studio (version unknown)
• Android Studio at /Applications/Android Studio 4.0 Preview.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
✗ Unable to determine Android Studio version.
✗ Unable to find bundled Java version.
• Try updating or re-installing Android Studio.
[✓] Connected device (4 available)
• iPhone di Gingu (mobile) • 00008130-001A5C280E92001C            • ios            • iOS 17.4.1 21E236
• iPhone 15 Plus (mobile)  • 16D679BA-90C6-4A48-A9EC-FDBB64FD0126 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
• macOS (desktop)          • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
• Chrome (web)             • chrome                               • web-javascript • Google Chrome 124.0.6367.119
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 4 categories.
Process finished with exit code 0

This is the build.gradle
plugins {
id "com.android.application"
id "kotlin-android"
id "dev.flutter.flutter-gradle-plugin"
}
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
android {
namespace "com.example.altrotestkisok.kioskflutterandroid"
compileSdkVersion flutter.compileSdkVersion
ndkVersion flutter.ndkVersion
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.example.altrotestkisok.kioskflutterandroid"
    // You can update the following values to match your application needs.
    // For more information, see: https://docs.flutter.dev/deployment/android#reviewing-the-gradle-build-configuration.
    minSdkVersion 24
    targetSdkVersion 34
    versionCode 1
    versionName "1.0"
    multiDexEnabled true
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation files('libs/ConnectionLayer-3.0.41-20230130-release.aar')

}

}
flutter {
source '../..'
}

My aar library is a custom library and it worka perfectly in a simple android java project. In flutter one, it's imported correctly and classes, objects, ecc. and some calls work perfectly but not all. What can I do? I want to compile it (it's an only flutter android project and I don't need other platform) in the same way

@huycozy is it possibile why library is a 32 bit?

Could you share a complete sample project on GitHub? And please add license the code in the repository under some open-source license (e.g. MIT, Apache, BSD, GPL) so that we may look into it.
If AAR lib can't be shared, please provide the error/warning output so that we have more information to investigate further. Thank you.


Do inter-container requests go out over the internet?

Hi folks,
First, thanks a tonne for this Jason. Truly great work. And a snap to get up and running.
But I'm unsure of whether or not any requests from one container to another are being routed directly to the nginx-proxy container or are they going out over the internet and then back again?
I've run a traceroute from within one of my containers, and it looks like the hostname is being resolved to one of my ELB instances. But then then first hop is to <IP_ADDRESS>, which is the docker0 bridge IP.
Here's what I'm seeing from within my app.stellaverse.com container (from which I would send a POST request to my api.stellaverse.com container):
root@be494527b4c1:/# traceroute api.stellaverse.com
traceroute to api.stellaverse.com (<IP_ADDRESS>), 64 hops max
  1   <IP_ADDRESS>  0.003ms  0.001ms  0.001ms
  2   <IP_ADDRESS>  1.220ms  1.391ms  0.965ms
  3   *  *  *
  4   *  *  *
  5   *  *  *
  6   * ^C

Where <IP_ADDRESS> is the ip of one of my ELB instances.
Don't have the networking chops to make sense of this. Can anyone else shed some light on this?
Thanks in advance.

The docker bridge is just the network that containers are assigned IP address from on your host.  By default, nginx-proxy just forwards requests from the host IP to the private container IP through your hosts networking.  It shouldn't go out over the internet unless you've got some custom routing/network setup.

Thanks for the info, but I'm not sure I'm really following. This isn't urgent by any means, but I'm curious as to how my app container knows to send any requests for any domains setup on the local network to the nginx-proxy container instead of out over the internet.
So if I've got app.myapp.com as one container, and then api.myapp.com as another container on the same host and app.myapp.com sends a request to api.myapp.com, that request is somehow automagically routed to the nginx-proxy container? If so, how does that happen?
Thanks in advance if anyone can help clarify this for me.

@Stellaverse If app.myapp.com tries to connect to api.myapp.com, it will first do a DNS lookup for api.myapp.com. If that's resolving to your ELB, then that's the IP address to which app.myapp.com will connect. There is nothing that nginx-proxy can to do to change how your backend container's HTTP client library routes outbound connections.


Extended Quotas Support in WHMCS

Description
The following quotas are missing:

[x] Quotas/Metric Billing for Disk Usage on a Per Datastore basis
[x] Quotas/Metric Billing for Networking Usage
[x] Quotas for the remaining stats if necessary (VMs, Running Resources)

Tasks

[x] Add whmcs module to one-ee-repo
[x] Check that it packages correctly
[x] Test it with a scratch WHMCS and ONE isntall
[x] Need to add documentation about new features in WHMCS guide
[x] Add to resolved issues, as feature, with link to documentation

Progress Status

[x] Code committed
[x] Testing - QA
[x] Documentation (Release notes - resolved issues, compatibility, known issues)

code https://github.com/OpenNebula/one-ee-tools/pull/39
docs https://github.com/OpenNebula/docs/pull/2372
docs https://github.com/OpenNebula/docs/pull/2376


Autosnippets dont work with specifiy filetypes

First of all, I'm just getting started with Neovim/Vim in general because I want to write Latex for university with it so I'm sorry if I make some obvious mistakes. ,:)
NVIM: v0.9.1
Plugins: lazy.nvim (v10.3.0), LuaSnip (v2.0.0)
init.lua:
require("config.lazy")

lua/config/lazy.lua:
-- Bootstrap lazy.nvim
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup("plugins")

lua/plugins/luasnip.lua:
return {
	"L3MON4D3/LuaSnip",
	-- follow latest release.
	version = "2.*", -- Replace <CurrentMajor> by the latest released major (first number of latest release)
	-- install jsregexp (optional!).
	build = "make install_jsregexp",

	main = "luasnip",

	opts = {
		enable_autosnippets = true,
		store_selction_keys = "<Tab>",
	},

	init = function()
		require("luasnip.loaders.from_lua").load({paths="~/.config/nvim/lua/snippets/"})
	end,
}

lua/snippets/tex/math.lua:
-- Abbreviations used in this article and the LuaSnip docs
local ls = require("luasnip")
local s = ls.snippet
local sn = ls.snippet_node
local t = ls.text_node
local i = ls.insert_node
local f = ls.function_node
local d = ls.dynamic_node
local fmt = require("luasnip.extras.fmt").fmt
local fmta = require("luasnip.extras.fmt").fmta
local rep = require("luasnip.extras").rep

return {
	-- Examples of Greek letter snippets, autotriggered for efficiency

	require("luasnip").snippet({filetype="<FILETYPE>", trig=";a", snippetType="autosnippet"},
		{
			require("luasnip").text_node("\\alpha"),
		}
	),
	require("luasnip").snippet({filetype="tex", trig=";b", snippetType="autosnippet"},
		{
			require("luasnip").text_node("\\beta"),
		}
	),
	require("luasnip").snippet({filetype="tex", trig=";c", snippetType="autosnippet"},
		{
			require("luasnip").text_node("\\gamma"),
		}
	),

	require("luasnip").snippet(
		{
			filetype="all",
			trig="hi",
			dscrd="An autotriggering snippet that expands 'hi' into 'Hello, world!'",
			regTrig=false,
			priority=100,
			snippetType="autosnippet"
		},
		{
			require("luasnip").text_node("Hello, world!"),
		}
	)
}

I'm following an article for writing latex with Neovim but it is not completly up to date and I made adjustments but sticking close to the documentation of lazy.nvim and Luasnip.
The autotrigger for "hi" triggers as expected in all filetypes.
I made tests for different filetypes for ";a" because it did not work with "tex" as .
Here are my results:
"tex": autotrigger does not work
"abc": autotrigger works
"json": autotrigger works
"test": autotrigger does not work
"md": autotrigger does not work
"java": autotrigger does work
"lua": autotrigger does work
"xyz": autotrigger does not work
I hope my tests can give you some insight but I really was not sure for what to test because I couldnt really find anything about this setting in the documentation.
Also thanks for this awesome plugin and for the help in advance. ^^

Hi!
All of this looks pretty good, is it possible you're only confusing filetype with file-extension?
luasnip will, when looking for the snippets for some buffer, look at its vim.o.filetype. For example, a.md will have filetype "markdown", not "md".
Hope this helps :)

Oh, that helps a lot. Thx ,:) i thought it gets the filetype by the specific extensions because it worked with "abc" but it solves my problem. :D


Internal error when merging PDF version 1.7

I get a message "an internal error has occurred: please contact technical support" when I try to merge PDF version 1.7

That's because PDFTk might not be able to merge PDFs for version > 1.7?
I plan to implement a solution for multiple "merger" in v7.

Hello @deedek
Version 6.4 might resolve your issue 👍

Hello @deedek
Version 6.4 might resolve your issue 👍


Refrigerator Support

Hello there,
I have a  Beko refrigerator. It seems to be integrated via HomeWhiz app. Does this addon integrate refrigerators?

Hi!
That's a good question, and I honestly don't know – have you tried setting it up with the integration?
Also, please include your device digital ID, thanks!

I'll close this issue for now. Without any testing of users with a fridge as well as logs in case fridges are not working, there is nothing we can do.


Some questions about PPO

Hello Zhou,
What a nice code. But I have some questions about your PPO part.

Do you test other continue space env like Mujoco? I test the Simple PPO code in Mujoco, which look like the code doesn't work. On the other hand, Pendulum-v0 result is good but not very good, which mean the best 100-episode average reward was below -200.

In Simple PPO code, you use the reward normalize. But I don't understand why the reward normalize can improve the result so much? You know, the reward normalize in the code is characteristic engineering, we had better not do it by ourselves.

I am looking forward your reply. : )

Hi @20chase ,

1.Do you test other continue space env like Mujoco? I test the Simple PPO code in Mujoco, which look like the code doesn't work. On the other hand, Pendulum-v0 result is good but not very good, which mean the best 100-episode average reward was below -200.

I haven't tried the Mujoco yet, and the simple_PPO code is a single-thread based structure, the data an agent collected is highly correlated, which is not good for training. But the simplePPO is a good example that demonstrates the PPO's structure. A better result could be achieved using multi-agents like A3C (My DPPO is using multi-agents).

In Simple PPO code, you use the reward normalize. But I don't understand why the reward normalize can improve the result so much? You know, the reward normalize in the code is characteristic engineering, we had better not do it by ourselves.

The normalization process is mentioned in google's DPPO paper. The reason under the hood should be that they consider a future return and discounted reward (not TD learning). I found in the Pendulum's environment, the reward is always negative. Taking account the discount factor when reward closes to zero (when pendulum achieves the highest point). the future return goes toward zero if it keeps staying at the highest point.  While if the highest reward is a positive number, the future return can be accumulated to a larger number (I think the cumulative fact encourages learning).


Interactive jsonschema demo running on notebooks.ai

Hi @Julian, following our discussion here https://github.com/Julian/jsonschema/issues/506, this PR adds a link to the DEMO Notebook running on https://notebooks.ai/.
** Note that the link won't work until this PR is merged, because it looks for a DEMO.ipynb file which is still not present in Julian's repo. If you want to see how it will look like, you can take a look at it here
Anything here can be changed. Post your thoughts and we can iterate from there.

Do you know what command it runs to install the package? pyrsistent is
declared in jsonschema's install_requires
On Fri, Apr 19, 2019, 14:13 Martin Zugnoni<EMAIL_ADDRESS>wrote:

@martinzugnoni commented on this pull request.
In demo.yml
https://github.com/Julian/jsonschema/pull/538#discussion_r277054753:

@@ -0,0 +1,3 @@
+requirements:

Hey @Julian https://github.com/Julian, I'm very sorry about the late
response. I've been super busy lately.
Requirements listed in the demo.yml file are the libraries needed to run
the DEMO.ipynb notebook. It seems that just by installing jsonschema the
DEMO is not fully working (see screenshot below). That's why I also added
pyrsistent.
[image: image]
https://user-images.githubusercontent.com/1155573/56437149-ba417c80-62b4-11e9-8f2a-195f0af73cd2.png
About notebooks.ai documentation, we are still working on it. We will
probably link the documentation to the main website once it's done.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Julian/jsonschema/pull/538#discussion_r277054753, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACQQXQ5RTACBXRQBJTYRVLPRIDUNANCNFSM4G4GRALQ
.

I've just checked and it's running pip install package1 package2 ... packageN with all the packages listed in the demo.yml file.
In this case, it would run:
pip install jsonschema==2.6.0 pyrsistent==0.14.7

Really odd...
I could of course just merge and make believe I didn't see this, but it worries me about future dependencies and whether that's going to mean now keeping them in both places -- I'm fairly sure jsonschema is doing the right thing here, but it's hard to tell what notebooks.ai is doing. It might be it's using a really old version of pip and/or setuptools?
But like, installing jsonschema installs pyrsistent as it should:
⊙  virtualenv venv; venv/bin/pip install jsonschema; venv/bin/python -c 'from jsonschema import validate'                                                              julian@Air
New pypy executable in /Users/julian/Development/jsonschema/venv/bin/python
Also creating executable in /Users/julian/Development/jsonschema/venv/bin/pypy
Installing setuptools, pip, wheel...
done.
DEPRECATION: A future version of pip will drop support for Python 2.7.
Collecting jsonschema
/Users/julian/Development/jsonschema/venv/site-packages/pip/_vendor/msgpack/fallback.py:222: PendingDeprecationWarning: encoding is deprecated, Use raw=False instead.
  PendingDeprecationWarning)
  Using cached https://files.pythonhosted.org/packages/aa/69/df679dfbdd051568b53c38ec8152a3ab6bc533434fc7ed11ab034bf5e82f/jsonschema-3.0.1-py2.py3-none-any.whl
Collecting attrs>=17.4.0 (from jsonschema)
  Using cached https://files.pythonhosted.org/packages/23/96/d828354fa2dbdf216eaa7b7de0db692f12c234f7ef888cc14980ef40d1d2/attrs-19.1.0-py2.py3-none-any.whl
Collecting pyrsistent>=0.14.0 (from jsonschema)
Requirement already satisfied: setuptools in ./venv/site-packages (from jsonschema) (41.0.1)
Collecting six>=1.11.0 (from jsonschema)
  Using cached https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
Collecting functools32; python_version < "3" (from jsonschema)
Installing collected packages: attrs, six, pyrsistent, functools32, jsonschema
Successfully installed attrs-19.1.0 functools32-3.2.3.post2 jsonschema-3.0.1 pyrsistent-0.14.11 six-1.12.0

Will have a think.

I agree @Julian. Don't worry, I will further investigate before we merge this. Will come back when I have any news. Thanks for reporting BTW.

Awesome! Thanks! Let me know what you find.

WTF! Now I can't reproduce the error I pasted above :/
I just removed pyrsistent from the demo.yml file and it works fine (as expected). Could you please double check it and confirm me it's working also for you?

Hah, well, glad it's working now at least.
Does look like it's working here too!

The last thing from me I think at this point is really just the styling or size of that button :D -- is there anything quick that could be done about that? If not, happy to merge I think at this point -- much appreciated of course!

Thank @Julian
That blue button is the default image we use everywhere. Feel free to propose a different button image if you want. I'm 100% open to any design change.
In case this button is at least acceptable, we can move forward and merge it for now, until we work in a redesign.

@martinzugnoni thanks for being so amenable!
I think what rubs my design feathers a bit is probably just having such a big button on its own line, it's even bigger than the text introducing it.
I think even just shrinking it by ~30% size-wise would look better visually, and even better would be possibly putting it underneath a small screenshot of the notebook? But even just the shrinking I think would be awesome.
And really thanks again regardless, looks like a great project.

Cool @Julian, appreciate your comments. What about now?
Note that the notebook preview is a gif, which I think makes more sense to give the user a quick overview of how it will look like.

I think the gif is returning a 404 -- might need to have that alongside directly here in the repo or something to make sure it stays up? getting close

Fixed it, the previous link expired. Now I hosted on Github.

Great, thanks!


Regression testing

I'd like to offer my help to create regression test automation.
Do you have:

a list of configurations/layouts you'd like to test
a list of actions/commands you'd like to test

for each release as it arrives?

I have some kitchen/inspec tests in my openshift3 wrapper cookbook over this one, which I can contribute too.

Just sent you a collaboration link:+1:
I am sure we shall do great stuff going forward

Hi @IshentRas, I just submitted PR with the first integration tests.

Running tests it all looked OK until I got this:
  Service etcd
     ✔  should be installed
     ✔  should be enabled
     ✔  should be running
  Service origin-master-api
     ✔  should be installed
     ✔  should be enabled
     ✔  should be running
  Service origin-master-controllers
     ✔  should be installed
     ✔  should be enabled
     ✔  should be running
  Service origin-master
     ✔  should not be installed
  Service origin-node
     ✔  should be installed
     ✔  should be enabled
     ✔  should be running

Target:  ssh://vagrant@<IP_ADDRESS>:2201

     No tests executed.

Test Summary: 13 successful, 0 failures, 0 skipped
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 2 actions failed.
>>>>>>     Failed to complete #verify action: [undefined method `[]=' for nil:NilClass] on standalone-centos-72
>>>>>>     Failed to complete #verify action: [undefined method `[]=' for nil:NilClass] on cluster-native-centos-72
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

Output in kitchen log looks like:
E, [2017-01-09T16:22:18.237980 #32679] ERROR -- Kitchen: ----End Backtrace-----
E, [2017-01-09T16:22:18.238004 #32679] ERROR -- Kitchen: ---Nested Exception---Failed
E, [2017-01-09T16:22:18.238025 #32679] ERROR -- Kitchen: Class: Kitchen::ActionFailed#verify action: [undefined method `[]=' for nil:NilClass]
E, [2017-01-09T16:22:18.238073 #32679] ERROR -- Kitchen: Message: Failed to complete #verify action: [undefined method `[]=' for nil:NilClass]
E, [2017-01-09T16:22:18.238099 #32679] ERROR -- Kitchen: ----------------------
E, [2017-01-09T16:22:18.238121 #32679] ERROR -- Kitchen: ------Backtrace-------ms/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:633:in `add_example'
E, [2017-01-09T16:22:18.238141 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:633:in `add_example'nd_conE, [2017-01-09T16:22:18.238165 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:363:in `create_or_find_control'017-01-09T16:22:18.238221 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:53:in `block in stop'
E, [2017-01-09T16:22:18.238197 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:287:in `format_example'
E, [2017-01-09T16:22:18.238221 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:53:in `block in stop'
E, [2017-01-09T16:22:18.238243 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:52:in `map'p'
E, [2017-01-09T16:22:18.238266 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:52:in `stop'
E, [2017-01-09T16:22:18.238302 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/rspec_json_formatter.rb:114:in `stop'
E, [2017-01-09T16:22:18.238345 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:189:in `block in notify'
E, [2017-01-09T16:22:18.238371 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `each'
E, [2017-01-09T16:22:18.238395 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:188:in `notify'
E, [2017-01-09T16:22:18.238450 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:183:in `stop'
E, [2017-01-09T16:22:18.238505 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:157:in `block in finish'
E, [2017-01-09T16:22:18.238554 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:175:in `close_after'358:in `transition_to'
E, [2017-01-09T16:22:18.238615 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:156:in `finish'e.rb:157:in `verify'
E, [2017-01-09T16:22:18.238660 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:79:in `report'd.rb:197:in `public_send'
E, [2017-01-09T16:22:18.238702 #32679] ERROR -- Kitchen: /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:117:in `run_specs'rb:197:in `run_action_in_thread'
E, [2017-01-09T16:22:18.238749 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/runner_rspec.rb:77:in `run'block (2 levels) in run
E, [2017-01-09T16:22:18.238779 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/runner.rb:117:in `run_tests'
E, [2017-01-09T16:22:18.238811 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/inspec-1.9.0/lib/inspec/runner.rb:101:in `run'
E, [2017-01-09T16:22:18.238834 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/kitchen-inspec-0.17.0/lib/kitchen/verifier/inspec.rb:94:in `call'
E, [2017-01-09T16:22:18.238858 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:434:in `block in verify_action'
E, [2017-01-09T16:22:18.238883 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:527:in `synchronize_or_call'
E, [2017-01-09T16:22:18.238906 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:489:in `block in action'
E, [2017-01-09T16:22:18.238928 #32679] ERROR -- Kitchen: /usr/lib/ruby/2.3.0/benchmark.rb:293:in `measure'
E, [2017-01-09T16:22:18.238949 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:488:in `action'
E, [2017-01-09T16:22:18.238972 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:426:in `verify_action'
E, [2017-01-09T16:22:18.239003 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:359:in `block in transition_to'
E, [2017-01-09T16:22:18.239027 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:358:in `each'
E, [2017-01-09T16:22:18.239051 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:358:in `transition_to'
E, [2017-01-09T16:22:18.239076 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/instance.rb:157:in `verify'
E, [2017-01-09T16:22:18.239099 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/command.rb:197:in `public_send'
E, [2017-01-09T16:22:18.239159 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/command.rb:197:in `run_action_in_thread'
E, [2017-01-09T16:22:18.239187 #32679] ERROR -- Kitchen: /var/lib/gems/2.3.0/gems/test-kitchen-1.14.2/lib/kitchen/command.rb:169:in `block (2 levels) in run_action'
E, [2017-01-09T16:22:18.239212 #32679] ERROR -- Kitchen: ----End Backtrace-----

kitchen diagnose --all
---
timestamp: 2017-01-09 16:25:07 UTC
kitchen_version: 1.14.2
plugins:
  driver:
    Vagrant:
      class: Kitchen::Driver::Vagrant
      version: 0.21.1
      api_version: 2
  provisioner:
    ChefZero:
      class: Kitchen::Provisioner::ChefZero
      version: 1.14.2
      api_version: 2
  transport:
    Ssh:
      class: Kitchen::Transport::Ssh
      version: 1.14.2
      api_version: 1
  verifier:
    Inspec:
      class: Kitchen::Verifier::Inspec
      version: 0.17.0
      api_version: 1
loader:
  process_erb: true
  process_local: true
  process_global: true
  global_config:
  project_config:
    filename: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/.kitchen.yml"
    raw_data:
      driver:
        name: vagrant
        customize:
          cpus: 2
          memory: 1024
      provisioner:
        name: chef_zero
        environments_path: test/environments
        roles_path: test/roles
        client_rb:
          solo: false
      driver_config:
        require_chef_omnibus: 12.17.44
      verifier:
        name: inspec
      platforms:
      - name: centos-7.2
        driver:
          vm_hostname: origin-centos-72
        attributes:
          cookbook-openshift3:
            openshift_common_public_hostname: <IP_ADDRESS>
            openshift_master_router_subdomain: cloudapps.<IP_ADDRESS>.nip.io
            ose_major_version: 1.3
            docker_log_driver: journald
            master_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
            node_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
      suites:
      - name: standalone
        run_list:
        - role[openshift3-base]
        verifier:
          inspec_tests:
          - test/inspec/standalone
          - test/inspec/shared
        attributes:
          cookbook-openshift3:
            openshift_HA: false
      - name: cluster-native
        run_list:
        - role[openshift3-base]
        verifier:
          inspec_tests:
          - test/inspec/cluster-native
          - test/inspec/shared
        attributes:
          cookbook-openshift3:
            openshift_HA: true
            openshift_cluster_name: test-cluster.domain.local
            etcd_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
  local_config:
  combined_config:
    filename:
    raw_data:
      driver:
        name: vagrant
        customize:
          cpus: 2
          memory: 1024
      provisioner:
        name: chef_zero
        environments_path: test/environments
        roles_path: test/roles
        client_rb:
          solo: false
      driver_config:
        require_chef_omnibus: 12.17.44
      verifier:
        name: inspec
      platforms:
      - name: centos-7.2
        driver:
          vm_hostname: origin-centos-72
        attributes:
          cookbook-openshift3:
            openshift_common_public_hostname: <IP_ADDRESS>
            openshift_master_router_subdomain: cloudapps.<IP_ADDRESS>.nip.io
            ose_major_version: 1.3
            docker_log_driver: journald
            master_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
            node_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
      suites:
      - name: standalone
        run_list:
        - role[openshift3-base]
        verifier:
          inspec_tests:
          - test/inspec/standalone
          - test/inspec/shared
        attributes:
          cookbook-openshift3:
            openshift_HA: false
      - name: cluster-native
        run_list:
        - role[openshift3-base]
        verifier:
          inspec_tests:
          - test/inspec/cluster-native
          - test/inspec/shared
        attributes:
          cookbook-openshift3:
            openshift_HA: true
            openshift_cluster_name: test-cluster.domain.local
            etcd_servers:
            - ipaddress: <IP_ADDRESS>
              fqdn: origin-centos-72
              labels: region=infra custom=label
              schedulable: false
instances:
  standalone-centos-72:
    platform:
      os_type: unix
      shell_type: bourne
    state_file:
      hostname: <IP_ADDRESS>
      last_action: setup
      last_error: NoMethodError
      port: '2200'
      ssh_key: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/.kitchen/kitchen-vagrant/kitchen-cookbook-openshift3-standalone-centos-72/.vagrant/machines/default/virtualbox/private_key"
      username: vagrant
    driver:
      boot_timeout:
      box: bento/centos-7.2
      box_check_update:
      box_download_insecure:
      box_url:
      box_version:
      cache_directory: "/tmp/omnibus/cache"
      customize:
        cpus: 2
        memory: 1024
      gui:
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      linked_clone:
      log_level: :info
      name: vagrant
      network: []
      pre_create_command:
      provider: virtualbox
      provision: false
      ssh: {}
      synced_folders:
      - - "/home/imiell/.kitchen/cache"
        - "/tmp/omnibus/cache"
        - 'create: true'
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      vagrant_binary: vagrant
      vagrantfile_erb: "/var/lib/gems/2.3.0/gems/kitchen-vagrant-0.21.1/templates/Vagrantfile.erb"
      vagrantfiles: []
      vm_hostname: origin-centos-72
    provisioner:
      always_update_cookbooks: false
      attributes:
        cookbook-openshift3:
          openshift_common_public_hostname: <IP_ADDRESS>
          openshift_master_router_subdomain: cloudapps.<IP_ADDRESS>.nip.io
          ose_major_version: 1.3
          docker_log_driver: journald
          master_servers:
          - ipaddress: <IP_ADDRESS>
            fqdn: origin-centos-72
            labels: region=infra custom=label
            schedulable: false
          node_servers:
          - ipaddress: <IP_ADDRESS>
            fqdn: origin-centos-72
            labels: region=infra custom=label
            schedulable: false
          openshift_HA: false
      chef_client_path: "/bin/chef-client"
      chef_omnibus_install_options:
      chef_omnibus_url: https://omnitruck.chef.io/install.sh
      chef_zero_host:
      chef_zero_port: 8889
      client_rb:
        solo: false
      clients_path:
      command_prefix:
      config_path:
      cookbook_files_glob: README.*,metadata.{json,rb},attributes/**/*,definitions/**/*,files/**/*,libraries/**/*,providers/**/*,recipes/**/*,resources/**/*,templates/**/*
      data_bags_path:
      data_path:
      deprecations_as_errors: false
      encrypted_data_bag_secret_key_path:
      environments_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/environments"
      ftp_proxy:
      http_proxy:
      https_proxy:
      json_attributes: true
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_file:
      log_level: auto
      max_retries: 1
      name: chef_zero
      named_run_list: {}
      nodes_path:
      policyfile:
      policyfile_path:
      profile_ruby: false
      require_chef_omnibus: 12.17.44
      retry_on_exit_code: []
      roles_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/roles"
      root_path: "/tmp/kitchen"
      ruby_bindir: "/embedded/bin"
      run_list:
      - role[openshift3-base]
      sudo: true
      sudo_command: sudo -E
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      wait_for_retry: 30
    transport:
      compression: false
      compression_level: 0
      connection_retries: 5
      connection_retry_sleep: 1
      connection_timeout: 15
      keepalive: true
      keepalive_interval: 60
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_level: :info
      max_ssh_sessions: 9
      max_wait_until_ready: 600
      name: ssh
      port: 22
      ssh_gateway:
      ssh_gateway_username:
      ssh_key:
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      username: root
    verifier:
      chef_omnibus_root: "/opt/chef"
      command_prefix:
      ftp_proxy:
      http_proxy:
      https_proxy:
      inspec_tests:
      - test/inspec/standalone
      - test/inspec/shared
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_level: :info
      name: inspec
      root_path: "/tmp/verifier"
      sudo: true
      sudo_command: sudo -E
      suite_name: standalone
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
  cluster-native-centos-72:
    platform:
      os_type: unix
      shell_type: bourne
    state_file:
      hostname: <IP_ADDRESS>
      last_action: setup
      last_error: NoMethodError
      port: '2201'
      ssh_key: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/.kitchen/kitchen-vagrant/kitchen-cookbook-openshift3-cluster-native-centos-72/.vagrant/machines/default/virtualbox/private_key"
      username: vagrant
    driver:
      boot_timeout:
      box: bento/centos-7.2
      box_check_update:
      box_download_insecure:
      box_url:
      box_version:
      cache_directory: "/tmp/omnibus/cache"
      customize:
        cpus: 2
        memory: 1024
      gui:
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      linked_clone:
      log_level: :info
      name: vagrant
      network: []
      pre_create_command:
      provider: virtualbox
      provision: false
      ssh: {}
      synced_folders:
      - - "/home/imiell/.kitchen/cache"
        - "/tmp/omnibus/cache"
        - 'create: true'
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      vagrant_binary: vagrant
      vagrantfile_erb: "/var/lib/gems/2.3.0/gems/kitchen-vagrant-0.21.1/templates/Vagrantfile.erb"
      vagrantfiles: []
      vm_hostname: origin-centos-72
    provisioner:
      always_update_cookbooks: false
      attributes:
        cookbook-openshift3:
          openshift_common_public_hostname: <IP_ADDRESS>
          openshift_master_router_subdomain: cloudapps.<IP_ADDRESS>.nip.io
          ose_major_version: 1.3
          docker_log_driver: journald
          master_servers:
          - ipaddress: <IP_ADDRESS>
            fqdn: origin-centos-72
            labels: region=infra custom=label
            schedulable: false
          node_servers:
          - ipaddress: <IP_ADDRESS>
            fqdn: origin-centos-72
            labels: region=infra custom=label
            schedulable: false
          openshift_HA: true
          openshift_cluster_name: test-cluster.domain.local
          etcd_servers:
          - ipaddress: <IP_ADDRESS>
            fqdn: origin-centos-72
            labels: region=infra custom=label
            schedulable: false
      chef_client_path: "/bin/chef-client"
      chef_omnibus_install_options:
      chef_omnibus_url: https://omnitruck.chef.io/install.sh
      chef_zero_host:
      chef_zero_port: 8889
      client_rb:
        solo: false
      clients_path:
      command_prefix:
      config_path:
      cookbook_files_glob: README.*,metadata.{json,rb},attributes/**/*,definitions/**/*,files/**/*,libraries/**/*,providers/**/*,recipes/**/*,resources/**/*,templates/**/*
      data_bags_path:
      data_path:
      deprecations_as_errors: false
      encrypted_data_bag_secret_key_path:
      environments_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/environments"
      ftp_proxy:
      http_proxy:
      https_proxy:
      json_attributes: true
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_file:
      log_level: auto
      max_retries: 1
      name: chef_zero
      named_run_list: {}
      nodes_path:
      policyfile:
      policyfile_path:
      profile_ruby: false
      require_chef_omnibus: 12.17.44
      retry_on_exit_code: []
      roles_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/roles"
      root_path: "/tmp/kitchen"
      ruby_bindir: "/embedded/bin"
      run_list:
      - role[openshift3-base]
      sudo: true
      sudo_command: sudo -E
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      wait_for_retry: 30
    transport:
      compression: false
      compression_level: 0
      connection_retries: 5
      connection_retry_sleep: 1
      connection_timeout: 15
      keepalive: true
      keepalive_interval: 60
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_level: :info
      max_ssh_sessions: 9
      max_wait_until_ready: 600
      name: ssh
      port: 22
      ssh_gateway:
      ssh_gateway_username:
      ssh_key:
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"
      username: root
    verifier:
      chef_omnibus_root: "/opt/chef"
      command_prefix:
      ftp_proxy:
      http_proxy:
      https_proxy:
      inspec_tests:
      - test/inspec/cluster-native
      - test/inspec/shared
      kitchen_root: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3"
      log_level: :info
      name: inspec
      root_path: "/tmp/verifier"
      sudo: true
      sudo_command: sudo -E
      suite_name: cluster-native
      test_base_path: "/tmp/shutit_cookbook_openshift3_test_JTFbvY/cookbook-openshift3/test/integration"

@ianmiell can you tell me more about your chef-dk setup? In the kitchen diagnose --all output, I see this line:
      vagrantfile_erb: "/var/lib/gems/2.3.0/gems/kitchen-vagrant-0.21.1/templates/Vagrantfile.erb"

On my system the same line looks like:
      vagrantfile_erb: "/opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/kitchen-vagrant-0.21.1/templates/Vagrantfile.erb"

Which makes me think that your chef-dk is not using the same paths as me. I am running Ubuntu 16.06 on my workstation and use chef-dk v1.1.16 downloaded from https://downloads.chef.io/chefdk#ubuntu

Oh, good point!
https://github.com/ianmiell/shutit-library/blob/master/chefdk/chefdk.py
I see I've been using the 12.04 version. I need to improve this module a lot...

It seems that kitchen does not multi-node Vagrant clusters (I'm quite shocked tbh), which means that as far as I know ShutIt is the only test framework that can do a multi-node OpenShift setup.
https://github.com/test-kitchen/test-kitchen/issues/873
Anyone know any different?

Yes, I never managed to test multi-VM with kitchen; even with Vagrant, which a lot of people use, the multi-VM feature is quite advanced and I often was the first to report some obscure bugs. I'll subscribe to the kitchen issue above, I'm interested.

Hmm, how is one supposed to test and multi-node vagrant cluster setup? Are there other frameworks that offer it? To me, these are the interesting things to test...

@IshentRas @jperville @taylok
OK, I have done some work to create a fuller testing framework that deals with multiple nodes.
Have a look at this folder:
https://github.com/ianmiell/shutit-openshift-cluster/tree/chef/tests
Each folder contains some files:

environment.json
init.py
machines.py
solo.rb
Vagrantfile

The environment.json file defines the chef solo environment.
The machines.py is a callback import that sets up the machine data structure, which defines the machines that are created in the test run.
solo.rb is the chef-solo config file (very standard).
The Vagrantfile is used by Vagrant to set up the VMs.
The test suite goes through each subfolder in https://github.com/ianmiell/shutit-openshift-cluster/tree/chef/tests and builds the multinode environment.
The tests are run by running:
https://github.com/ianmiell/shutit-openshift-cluster/blob/chef/run_tests.sh
There are some other items that can be configured at present. Specifically the other cookbook versions (which default to 'latest'). @taylok I was thinking this could be used to automatically test changes against our particular configuration.
I appreciate this framework is pretty complex, but as far as I can tell it is the only option to get beyond kitchen's single-node paradigm.
I intend to hook this up to my home jenkins server so I can run tests automatically on checkin, and mail interested parties on failure.
Give me a shout if you have any queries, or requests for regression combinations. @IshentRas I'm wondering whether RedHat would be interested in this for their ansible deployments.

OK guys, you all have access to the Jenkins repo now, and should get emails on failure.
I am checking branches: 'master', and 'release*', so any changes on either will get reg-tested.
At some point soon I will add the kitchen tests also, as that's an easy addition.
I just spoke to will about adding some sanity tests in the shutit scripts, which he thinks he can do quickly.

I just received 2 failure emails, so I guess that the notifications work :)

Yes, now to figure out which is wrong, my tests or the code :)
On Sat, Feb 11, 2017 at 1:39 PM, Julien Pervillé<EMAIL_ADDRESS>wrote:

I just received 2 failure emails, so I guess that the notifications work :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/41#issuecomment-279144398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczZMwUI2JrKuivkTMQnPK081ia9_wks5rbbomgaJpZM4Laeus
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

Your test :-)

Yes... fixed - re-running master test.
On Sat, Feb 11, 2017 at 2:12 PM, William Burton<EMAIL_ADDRESS>wrote:

Your test :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/41#issuecomment-279146186,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGrczSvS0LiRqQwZflb5jYGgt1egnn9Aks5rbcG6gaJpZM4Laeus
.

--
My book on Docker in Practice: Get 39% off with the code 39miell
http://manning.com/miell/?a_aid=zwischenzugs&a_bid=e0d48f62

Jenkins back to normal, am sure you got mails :)

Reg testing now includes kitchen tests.

Do we have syntax checks we want to include as part of the tests, or is this already part of the kitchen tests?

@ianmiell please include "cookstyle" checks (the version bundled in chefdk v1.1.16).

Reg testing in place with Jenkinsfile. Closing off.
Could use more meaningful app-level tests though :)

Thanks very much @ianmiell @jperville I am back now (New laptop lol)


pull request for e2e test at 12/08/2016 13:26:02

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


reset() before first run?

In the run.py code, the first reset() is done after the evaluation of run_episode. Would I get a penalty if I perform the reset before? E.g.:
def run_evaluation(env):
    while not env.done_grading():
        env.reset()
        run_episode(env)

In particular, would this consider the first run as a failure with a reward of 0?
I have made some modifications to the ObstacleTowerEnv, part of which involve some initial setup in the reset() method.

Hi @Holt59
@harperj Should be able to answer this for you.

Hi @Holt59 -- it should not be a problem if you run multiple resets before step().  I'm going to close this issue but please feel free to reopen if you do see any problem with this in practice.


Fix: Typescript process null values

Fixes https://github.com/microsoft/kiota-typescript/issues/1188
2 part for processing null values

Can you please add a changelog entry? (unreleased, changed)

Where to look for the example of changelog?

@Kindest13 The changelog file is at the repository root. You just need to add an entry to the unreleased section.
https://github.com/microsoft/kiota/blob/main/CHANGELOG.md#unreleased


Element has no focus error

I've been testing my fiori app and thus have been making use of the OData V4 test library. I am trying to change the row of a table using the ObjectPage.onTable().iChangeRow() function. But I keep running into the following error:
the string "Changing row values of table '{id: fe::table::conversations::LineItem::i18nConversations}' with old values='0' to new values='{Message: ABCDEFGHIJK, Timestamp: 19 Nov 2023, 20:57:38}' - FAILURE\nFailure in Opa success function\nException thrown by the testcode:'Error: DOM representation of control 'Element sap.m.Input#__input0-__clone40-__clone41' has no focus DOM reference
NOTE : until yesterday this code worked fine when running the script in non-headless mode. this problem first occurred when running it headless and now I am facing the same problem when running it normally as well.
Here is the function call:

The intention is to create a new row in the table Conversations (as shown below). Here are the corresponding elements:

Here are the corresponding error logs received:

Runtime Env :
wdi5/wdio-ui5-service : 1.5.0
@ui5/cli : "12.14.10",
@wdio/cli: "8.16.11",
node : v18.14.0
OS: MacOS Ventura
Browser + Version : Firefox, Version : 116.0.0

Have same error here.. maybe somebody can pick this issue up and have a look at it?


flush tty input buffer before asking users for decisions

Requires cgo to work, and it only works on Unix.
Fixes #157.

Thank you very much @minux for the help!

I don't know why this is "closed".  This is still an issue in Go 1.5.1.  Will it be fixed in 1.5.2?


Support for rest_framework 3.8

According to rest_framework 3.8 announcement list_route is going to be deprecated. @EliotBerriot do you have any plans to look into this?
I just updated one of my apps to 3.9 and started to see annoying warnings while running my tests which is why I'm asking 😬

Thank you for opening the issue, I'll consider that before next release :)

Is this still an issue? I saw that #180 which contains djangorestframework 3.10.x compatibility commit was merged.

Yep, we can close, thanks!


[AutoRelease] t2-elastic-2023-05-11-80113(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4153
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=2697

issue link:https://github.com/Azure/sdk-release-request/issues/4153


Local tests run smoothly, but Travis hangs them

It seems that Travis doesn't like the concurrency tests

Right now, we're going to disable the conflicting test: MemoryReleaseTest.autoReleaseMemoryWorks()
Help will be really appreciated :·)

Working with @alorma we've seen that the issue is related with canEditWhileIteratingWithRandom() test

Probably the issue is related to this smart answer: http://stackoverflow.com/a/18542170/2191890

Solved! 0ee9dd5e9139a0674cbd7ce4115c87d860027888


docs: add salaxander as SIG docs tech lead

Adding salaxander as a SIG docs tech lead
CC @natalisucks @divya-mohan0209 @reylejano

/lgtm

/approve


Linter tries to upload bundle to apigee by default

Seems that linter tries to upload bundle here https://github.com/apigeecs/bundle-linter/blob/master/lib/package/bundleLinter.js#L103
If apiUpload option is not set up properly, private bundle which is linted might be uploaded to csdata organization. This might cause critical security issues.

Seems like it's not documented feature. I agree that default destPath should be removed.
Meanwhile, it will not upload anything unless you specify config.apiUpload.


APU: Option Enable SMM BIOS write not found in the list

Device
APU2
RTE version
1.1.0
Affected component(s) or functionality
No response
Brief summary
APU: Option Enable SMM BIOS write not found in the list
How reproducible
No response
How to reproduce
Try to run VBO tests.
Expected behavior
VBO tests should pass.
Actual behavior
VBO tests fail with "Option Enable SMM BIOS write not found in the list"
Link to screenshots or logs

Additional context
No response
Solutions you've tried
No response

OK, that test run was executed on Friday, so I probably don't have that commit yet.

Indeed seems to work now.


Templates do not compile

I've put *.jst.skim templates into app/assets/javascripts/templates
For example, chat.jst.skim.
I've added
config.assets.precompile += ['templates/*.skim']

to my config/application.rb
It works seemlessly in Dev, but I can't compile them with
RAILS_ENV=production rake assets:precompile
None of these templates are compiled.
Could someone help me? I have no idea what I do wrong.

I figured it out myself looking through sprockets/manifest.rb and sprockets/legacy.rb
tempates/*.jst.skim files are compiled to templates/*.js and tempaltes/*.skim filter doesn't work.
Instead, tempates/*.js filter should be used.


Don't overinject scripts into frames

Reviewer: @Charlie-belmer @kdzwinel

Description:

We were injecting into all frames on every onCommitted event, which was leading to injecting multiple instances into each frame. This PR fixes that.
Steps to test this PR:

Install extension
Navigate to onet.pl, check console. There shouldn't be any errors related to content scripts

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

Yep, updating that as well to reflect this change and the extension conflict guidelines 👍


[joltphysics] Add usage

Fixes: https://github.com/microsoft/vcpkg/issues/28048
Added usage and tested on x64-windows.

This is incomplete. You have to link against Jolt.lib
target_include_directories does not solve this.

This is incomplete. An user needs to link against Jolt.lib target_include_directories does not solve this.

I also believe this is incomplete. As a result I think this issue has been closed in error:
https://github.com/microsoft/vcpkg/issues/28048
Unless I'm misunderstanding it seems like this port is partially malformed. There are no targets exported/installed by jolt so right now the user would have to manually find the dbg/rel libs and link them explicitly. Which is a pain. I can't imagine this is the first port that has had this problem? Is there a good example of how this should portfile should look?

Yeah i saw the suggested usage and immediately noticed something was wrong. So this needs to have a second look


Parameter Labels Not Working as Expected In Subcommands As Method

in picocli documentation, parameter labels section:

By default, the field name is shown in < and > fish brackets.

I use subcommand as a method in CLI class, actual class that have business logic cli inherit functionality from CLI class, just for separation of CLI interface and logic.
@Command(name = "bionic", version = ["0.1.0"], mixinStandardHelpOptions = true)
abstract class CLI : Static(), Callable<Int> {
    fun run(args: Array<String>) {
        CommandLine(this).execute(*args)
    }

    override fun call(): Int {
        return 0
    }

    @Command(
        name = "setWebhook",
        description = ["Use this method to specify a URL and receive " +
                "incoming updates via an outgoing webhook."],
        mixinStandardHelpOptions = true,
    )
    protected open fun setWebhook(
        @Option(names = ["-u", "--url"], required = true) url: String,
        @Option(names = ["--certificate"]) certificate: InputFile?,
        @Option(names = ["--ipAddress"]) ipAddress: String?,
        @Option(names = ["--maxConnections"]) maxConnections: Int?,
        @Option(names = ["--allowedUpdates"]) allowedUpdates: List<String>?,
        @Option(names = ["--dropPendingUpdates"]) dropPendingUpdates: Boolean?,
        @Option(names = ["--secretToken"]) secretToken: String?
    ): Boolean? {
        return this.setWebhook(
            url,
            certificate,
            ipAddress,
            maxConnections,
            allowedUpdates,
            dropPendingUpdates,
            secretToken,
        )
    }

parameter labels of cli output is like this:
Usage: bionic setWebhook [-hV] [--dropPendingUpdates] [--certificate=<arg1>]
                         [--ipAddress=<arg2>] [--maxConnections=<arg3>]
                         [--secretToken=<arg6>] -u=<arg0>
                         [--allowedUpdates=<arg4>]...
Use this method to specify a URL and receive incoming updates via an outgoing
webhook.
      --allowedUpdates=<arg4>

      --certificate=<arg1>
      --dropPendingUpdates
  -h, --help                 Show this help message and exit.
      --ipAddress=<arg2>
      --maxConnections=<arg3>

      --secretToken=<arg6>
  -u, --url=<arg0>
  -V, --version              Print version information and exit.

Expected Results: field name shown in synopsis, Actual Results: argN shown in synopsis

You need to provide an extra parameter at compile time so the that byte code retains this information.
There is a note for this in the picocli user manual: https://picocli.info/#command-methods

If compiled with the -parameters flag on Java 8 or higher, the paramLabel of positional parameters is obtained from the method parameter name using reflection instead of the generic arg0, arg1, etc

@SinaMobasheri  Does that help?

🙏🏻💡 yeah, that was helpful, thank you, everything works now.


[4.0][Bug] Not all options on dropdown button are shown

Bug report
What I did
Added a button like the edit button in https://demo.backpackforlaravel.com/admin/product
What I expected to happen
Dropdown always is fully visible wherever it is opened
What happened
When having 6+ options, the bottom options of the dropdown are no longer shown
What I've already tried to fix it
Tried to add
data-boundary="viewport"
to the button.  Although in theory that should help, it does not ...
Backpack, Laravel, PHP, DB version
PHP VERSION:
PHP 7.3.1-1+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Jan 13 2019 10:19:33) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.1, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.1-1+ubuntu18.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
with blackfire v1.24.3~linux-x64-non_zts73, https://blackfire.io, by Blackfire
LARAVEL VERSION:
laravel/framework                       v6.9.0
BACKPACK VERSION:
backpack/crud                           4.0.30
backpack/generators                     2.0.5
eduardoarandah/backpacklogviewer        1.0.6

Hmm... indeed @timbertens , the dropdown should be visible. Can't replicate this. Can you please send a screenshot and the code from your blade file?

Same thing is happening for the "column visibility" which can be choose just bellow the table. If you have a lot of options those won't be shown. There will only show 3,4 items instead of all of them.

@tabacitu Do you think I could be added to one of the following releases?

Indeed @timbertens thanks for re-surfacing this. Just merged @pxpm 's PR #2953 that fixes this. Will tag in a few minutes, so you'll be able to get it with a composer update backpack/crud.
Sorry for taking so long to squash such a minor bug - must have slipped through the cracks.

Update - while the simple fix for this was merged in #2953 . The larger problem (for when there are even more items in the dropdown, and it gets even bigger than the viewport) is not yet solved, we're working on it in #2945

Wow didn't know you can do an action dropdown like that! Will revisit this page again in the future


hvsock related systemd and nm config files

the network manager file configures a vsock0 network interface with the specific mac-address that gvproxy needs.  this must be run before the vm command is run.
the systemd file is for running the vm command after network manager creates the network interface.  the url must be modified with the vm ID when using hvsock and Microsoft HyperV virtualization.  Once the vm command has been run, we issue a postexec to ask NM to bring the "link" up.  this may not be entirely necessary but wfm.

Fwiw, the golangci-lint failures are fixed in git main

updated

/lgtm
/approve


Add GHA workflow to build CLI API docs

resolves #5942
Description
Add a github actions workflow to build. Anything under core/dbt/docs/build is auto generated and does not require review.
Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[X] I have run changie new to create a changelog entry

It seems that closing and reopening a PR cause the workflow to fail. I'm going to do some testing around this, so apologies if closing and reopening the PR triggers notifications for reviewers!

Apologies for the force push, need to test with only one commit in the PR.


[polskieradio] Add support for Polskie Radio.

Polskie Radio is the main Polish state-funded radio broadcasting service.

@TRox1972, thank you for the review. I have addressed your concerns.

@dstftw, thank you for the review. I have made the suggested changes.

Is this good to go now?

@dstftw, @TRox1972 – any objections?

Could we move further with this, please? It would be much appreciated.

Thank you. :)


new suno protection? "This is a fake app"))))

does not pass user verification. (looks like cookies?)
and from here it is added to the lyrics:
"This is a fake app http://suno.com"

maybe you need to change the domain?
new api https://studio-api.prod.suno.com (studio-api.suno.ai)but the headings need to be different.

and now i think Suno block other API as well

Actually SUNO hCaptcha detected not only the captcha result, but also detect the mouse path, clicking behavior, etc.  The crack result token contains all of the behavior infos. And SUNO can know if you are a real human according to the final hCaptcha crack token.
So, the only way is you need to totally simulate the human behavior of hCaptcha using browser, otherwise you will always get "This is a fake app....", even though you cracked it.
I have successfully cracked using above solution, and now it works well now, and the result does not contains "This is a fake app anymore".
Also I exposed and provided above API for suno, but paid, just FYI if you are interested:

API: https://platform.acedata.cloud/services/suno
Doc: https://platform.acedata.cloud/documents/suno-audios-integration

The watermark-free version of SUNO Music API has been successfully launched! Supports the latest V4! No This is a fake app! (99% of APIs on the market may have the watermark This is a fake app)
API: https://surl.id/1uHGou0lxy
Documentation: https://surl.id/1uHGou0Iyp
Background: SUNO recently launched hCaptcha, which caused problems in the generation of almost 99% of APIs, and the generated audio contained This is a fake app content. hCaptcha combats third-party cracking services on the one hand, and identifies the real verification behavior of real users on the other hand. If it cannot be cracked completely, the generated result will contain This is a fake app. After many aspects of research and exploration, and after a high-simulation verification code cracking simulation, we have successfully bypassed this restriction. 99% of the services on the market may not have solved this problem. Welcome everyone to test and use it~

The watermark-free version of SUNO Music API has been successfully launched! Supports the latest V4! No This is a fake app! (99% of APIs on the market may have the watermark This is a fake app)
API: https://surl.id/1uHGqEcJ6A
Documentation: https://surl.id/1uHGqEcN2a
Background: SUNO recently launched hCaptcha, which caused problems in the generation of almost 99% of APIs, and the generated audio contained This is a fake app content. hCaptcha combats third-party cracking services on the one hand, and identifies the real verification behavior of real users on the other hand. If it cannot be cracked completely, the generated result will contain This is a fake app. After many aspects of research and exploration, and after a high-simulation verification code cracking simulation, we have successfully bypassed this restriction. 99% of the services on the market may not have solved this problem. Welcome everyone to test and use it~

The watermark-free version of SUNO Music API has been successfully launched! Supports the latest V4! No This is a fake app! (99% of APIs on the market may have the watermark This is a fake app)
API: https://surl.id/1uHGqFVHSD
Documentation: https://surl.id/1uHGqFWkp4
Background: SUNO recently launched hCaptcha, which caused problems in the generation of almost 99% of APIs, and the generated audio contained This is a fake app content. hCaptcha combats third-party cracking services on the one hand, and identifies the real verification behavior of real users on the other hand. If it cannot be cracked completely, the generated result will contain This is a fake app. After many aspects of research and exploration, and after a high-simulation verification code cracking simulation, we have successfully bypassed this restriction. 99% of the services on the market may not have solved this problem. Welcome everyone to test and use it~


set_data window size example does not work

https://mavue.mavo.io/set-data/#win_size
See console for Vue warnings, didn't inspect what's happening yet.

Did you read the text right above it? That's exactly what it demonstrates: that this code doesn't work 😄

I rearranged the text a bit to make this more clear.


WSL should support makeptr ()

Migrated from https://bugs.webkit.org/show_bug.cgi?id=176197:
At 2017-09-01T00:03:20Z<EMAIL_ADDRESS>wrote:
Patch forthcoming.

At 2017-09-01T00:05:42Z<EMAIL_ADDRESS>wrote:
Created attachment 319543
the patch

At 2017-09-27T19:47:41Z<EMAIL_ADDRESS>wrote:
rdar://problem/34694027

At 2017-09-01T00:07:43Z<EMAIL_ADDRESS>wrote:
Comment on attachment 319543
the patch
View in context: https://bugs.webkit.org/attachment.cgi?id=319543&action=review

Tools/WebGPUShadingLanguageRI/Evaluator.js:132

           throw new Error("Cannot get type or argument; i = " + i + ", argument = " + argument + ", type = " + type + "; in " + node);

if you use a template literal here I'd think it'd be easier to read.

At 2017-09-01T00:09:58Z<EMAIL_ADDRESS>wrote:
Landed in https://trac.webkit.org/changeset/221460/webkit


support huawei api

Codecov Report

Merging #14 (8cad383) into master (198896d) will increase coverage by 8.88%.
The diff coverage is 74.02%.

@@            Coverage Diff             @@
##           master      #14      +/-   ##
==========================================
+ Coverage   68.60%   77.49%   +8.88%
==========================================
  Files          12       13       +1
  Lines         395      471      +76
==========================================
+ Hits          271      365      +94
+ Misses        103       75      -28
- Partials       21       31      +10

Impacted Files
Coverage Δ

internal/server/ecs/list.go
50.00% <0.00%> (-10.00%)
:arrow_down:

internal/tenanter/tenanter.go
65.62% <60.00%> (-1.05%)
:arrow_down:

internal/ecser/huawei.go
83.01% <70.00%> (+83.01%)
:arrow_up:

internal/configger/huawei.go
76.08% <76.08%> (ø)

internal/server/statistic/statistic.go
96.42% <100.00%> (+0.97%)
:arrow_up:

Continue to review full report at Codecov.

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


update plot_pred_vs_actual_from_file to have an uncertainty flag inst…

…ead of forced uncertainty plotting

Following your recs @mcloughlin2 I updated the code so that all pred_vs_actual plots call the _from_df() function to graph each axis. However, the stds are always None for live pipes, according to perf_data.get_pred_values(). I think it is how the data is passed into perf_data.accumulate_preds(), but didn't trace this any further. So, when pp.plot_pred_vs_actual(regr_pipe, error_bars=True) is called, it just plots with no error bars because stds is None.

I changed the flag from uncertainty to error_bars.
the plot titles are consistent between _from_file() and from pipe. They are necessarily different in from_df().
threshold is implemented in all 3 versions of the function.
I also added new code to find the split file by searching for the split uuid instead of painstakingly constructing it by the full file name. If you don't see any errors in this method I want to start implementing it in more places.

Oh right, I forgot that uncertainties aren't computed during training, so they don't get stored in the PerfData structures. So to get error bars in plot_pred_vs_actual, we'd have to run predictions from the live pipe. That's certainly doable, and would be a little faster than simply calling plot_pred_vs_actual_from_file on the just-saved model, since the model is already loaded.
It's weird, though...we've been thinking all along that 'uncertainty' is a parameter of the model training process, when really it only comes into play at prediction time. Does it change anything about the training process (other than forcing you to include dropouts in every layer)? I guess I'll have to look at the DeepChem code to find out...

I updated the plot_pred_vs_actual to call plot_pred_vs_actual_from_file to get the predictions. I first tried to do pipe.predict_full_dataset directly but it modifies the pipeline object in place and got pretty confusing pretty fast.
I think of uncertainty as influencing model selection or HPO but not directly influencing the training process.


Remove flow from .npmignore

Coverage remained the same at 99.547% when pulling 38355c25780842804add858ebcb58e3a21be77d6 on leos:patch-1 into 4230a692b8afb649a21842a90ebddc256b4005bb on evcohen:master.

v5.0.3 published!

Whoo! flow runs clean on my project now. Thanks for being on top of this!

thank you @leos for all of the help in resolving!!


Fixing e2e tests

Summary

Fixed broken e2e tests after the v5 release
Adjusted customCards.config.js to get errors from the onChange callback and apply them in the custom card fields

Tested scenarios

Run yarn test:e2e-remote in the packages/e2e repo

Good fixes! Nice to have the e2e tests working again for v5. :-)
Regarding the change to: "customCards.config.js to get errors from the onChange callback " - if this is working to help the tests pass then great.
However the thing to consider is that the contents of the playground directory (or the equivalent directory in the e2e tests: pages) mimic what the merchant has to create in order to run Checkout.
So the change to customCards.config.js represents what the merchant would have to do to in order to keep the same functionality in v5 as they used to have with the v4 onError handler.
I think a more robust solution is to enhance the object stored in state.errors, for a particular securedField, with the properties that we used to send to the onError handler.
This would mean that the mapErrorsToValidationRuleResult function in SecuredFieldsProvider should now look like this:
    /**
     * Map SF errors to ValidationRuleResult like objects, for CardInput component
     */
    public mapErrorsToValidationRuleResult(): object {
        const errorKeys = Object.keys(this.state.errors);
        const sfStateErrorsObj = errorKeys.reduce((acc, key) => {
            if (this.state.errors[key]) {
                acc[key] = {
                    isValid: false,
                    errorMessage: getError(this.state.errors[key]),
                    // For v5 the object found in state.errors should also contain the additional properties that used to be sent to the onError callback, namely: translation, errorCode & ref to rootNode
                    errorI18n: this.props.i18n.get(this.state.errors[key]),
                    error: this.state.errors[key],
                    rootNode: this.rootNode
                   // end v5 changes
                };
            } else {
                acc[key] = null;
            }
            return acc;
        }, {});
        return sfStateErrorsObj;
    }

(and there would need to be a small change to SecuredFieldsInput.tsx to call this function the way that CardInput currently does).


Wrong documentation with "currency" contract?

I am trying to run the currency contract in the main page https://github.com/EOSIO/eos
I create a account with the command: ./cleos create account eosio currency PUBLIC_KEY_1 PUBLIC_KEY_2
It seems to work good but when I run the command ./cleos get account currency
I get that:
{   "account_name": "currency",   "permissions": [{       "perm_name": "active",       "parent": "owner",       "required_auth": {         "threshold": 1,         "keys": [{             "key": "EOS8cAbAbevzuh2pFn2n7uQd9ijPYJaNFYqveZ7DbtgcA4BjUqMJG",             "weight": 1           }         ],         "accounts": []       }     },{       "perm_name": "owner",       "parent": "",       "required_auth": {         "threshold": 1,         "keys": [{             "key": "EOS7WTGdq12tvrNG3NQq5qLVtz5vcj7548eRnZJtEN1isi17LyRpg",             "weight": 1           }         ],         "accounts": []       }     }   ] }
In the documentation it says that I should take something like that:
{   "account_name": "currency",   "eos_balance": "0.0000 EOS",   "staked_balance": "0.0001 EOS",   "unstaking_balance": "0.0000 EOS",   "last_unstaking_time": "2035-10-29T06:32:22",    ... }
Also I noticed that when I create a account I get in the nodeos this messege:
561853ms thread-0   chain_api_plugin.cpp:79       operator()           ] Exception encountered while processing chain.push_transaction: {"code":3040000,"name":"action_validate_exception","message":"message validation exception","stack":[{"context":{"level":"error","file":"eosio_contract.cpp","line":62,"method":"apply_eosio_newaccount","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.850"},"format":"Cannot create account named ${name}, as that name is already taken","data":{"name":"currency"}},{"context":{"level":"warn","file":"eosio_contract.cpp","line":87,"method":"apply_eosio_newaccount","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.851"},"format":"","data":{"create":{"creator":"eosio","name":"currency","owner":{"threshold":1,"keys":[{"key":"EOS7WTGdq12tvrNG3NQq5qLVtz5vcj7548eRnZJtEN1isi17LyRpg","weight":1}],"accounts":[]},"active":{"threshold":1,"keys":[{"key":"EOS8cAbAbevzuh2pFn2n7uQd9ijPYJaNFYqveZ7DbtgcA4BjUqMJG","weight":1}],"accounts":[]},"recovery":{"threshold":1,"keys":[],"accounts":[{"permission":{"actor":"eosio","permission":"active"},"weight":1}]}}}},{"context":{"level":"warn","file":"apply_context.cpp","line":27,"method":"exec_one","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.852"},"format":"","data":{"_pending_console_output.str()":""}},{"context":{"level":"warn","file":"chain_controller.cpp","line":1662,"method":"__apply_transaction","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.853"},"format":"","data":{}},{"context":{"level":"warn","file":"chain_controller.cpp","line":1681,"method":"_apply_transaction","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.853"},"format":"","data":{}},{"context":{"level":"warn","file":"chain_controller.cpp","line":373,"method":"_push_transaction","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.853"},"format":"","data":{}},{"context":{"level":"warn","file":"chain_controller.cpp","line":311,"method":"_push_transaction","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.853"},"format":"","data":{}},{"context":{"level":"warn","file":"chain_controller.cpp","line":258,"method":"push_transaction","hostname":"","thread_name":"thread-0","timestamp":"2018-04-04T09:09:21.853"},"format":"","data":{}}]}
Is that normal?

OBE, closing since the currency contract has been removed


Fix inserting epoch_stake_progress

Fixes https://github.com/IntersectMBO/cardano-db-sync/issues/1620
Description
Add your description here, if it fixes a particular issue please provide a link to the issue.
Checklist

[ ] Commit sequence broadly makes sense
[ ] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] Any changes are noted in the changelog
[ ] Code is formatted with fourmolu on version <IP_ADDRESS> (which can be run with scripts/fourmolize.sh)
[ ] Self-reviewed the diff

Migrations

[ ] The pr causes a breaking change of type a,b or c
[ ] If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
[ ] Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

Done in https://github.com/IntersectMBO/cardano-db-sync/commit/2fad1b50cf515d3bf5ce686bde17393b11c50fc9


Migrate from welcomeScreen to loadingScreen

https://github.com/endlessm/kolibri-explore-plugin/pull/793 reworked the welcome screen so that it runs entirely out of the plugin and doesn't need to be run as a separate JS interface. This will be be in the next major release, so the flatpak needs to be prepared for that.

FYI, you can use the following from the RC release I made earlier today:
https://pypi.org/project/kolibri-explore-plugin/7.0.0rc3/
https://github.com/endlessm/kolibri-explore-plugin/releases/download/v7.0.0rc3/apps-bundle.zip
https://github.com/endlessm/kolibri-explore-plugin/releases/download/v7.0.0rc3/loading-screen.zip

This works fine from a user flow, tested with plugin 7.1 onwards.