Not listed on bosh.io/releases

Hi,
This bosh release is not listed on bosh.io/releases. It would be great if it was there. :)

See #1.


Not showing shaded map

Hi bro, I have problem with "Variable_3 by shaded contours". My result not showing shaded map (also no error message)
(I used your namelist.wrf). How can fix it ?

namelist.wrf.txt.

Hi.
Is this image the only result? What about other plots (next time slots)? All of them are empty?
The namelist looks fine to me. Maybe there are some issues with your WRF file. If the size of your WRF file is not much large, can you please send it to me to take a look at it? My email is ah.nikfal (gmail.com).
If the size of your WRF file is very large, you can run the command below and send output.nc to me instead. For running this command, you need to install NCO on your machine.
ncrcat -d Time,0,1 wrfout output.nc

Hi.
My result only show contour map.
This is my wrfout.
output.nc.txt

Thanks for sending the file. Your WRF file is okay.
In your namelist.wrf, please put Location_point_mark_on_off and Shapefile_on-off to 0, and plot again. It will be plotted without problem.
If you want to overlay points and shapefile on your plots, please try to give correct values and path to the aforementioned parameters, as well as Location_names, Location_latitudes, and Location_longitudes.
Sample output:

Your shapefile should also have a lat/lon projection to be overlaid on the plot. If the projection is something else (e.g. UTM), you can convert it to lat/lon and give its path to namelist.wrf.

Hi.
I edited namelist.wrf, but it still not showing (contour map is good). Maybe library  is problem.
namelist.wrf.txt

I ran it again with your new namelist and the plot was okay.
What is your system information? Your Linux distro? NCL version?
Does it show any error while you're running PostWRF?

Hi.
My system is Ubuntu 23.04 (Desktop). NCL 6.6.2
No error while running .
Postwrf.log

Try again, but in the last step (Format Of The Images: 1, 2, 3, or 4?), choose 2 (pdf) or 3 (png).
Maybe your system cannot handle x11.

Try again, but in the last step (Format Of The Images: 1, 2, 3, or 4?), choose 2 (pdf) or 3 (png). Maybe your system cannot handle x11.
In case of pdf or png, your plots will be saved in directories started by outputs_postwrf.

I have tried with 2 (pdf) and 3 (png) but the result is still the same.

Put the NCL lines below in a file (1.ncl) and run it.
Before running, replace the file name in the line f = addfile ("wrfout_d01_2020-01-15_____", "r") with your own WRF file name.
begin
;---Open file; substitute your own WRF output file here
  f = addfile ("wrfout_d01_2020-01-15_____", "r")
;--Read variables
  times = wrf_user_getvar(f,"times",-1)  ; get all time values on file
  p     = wrf_user_getvar(f,"p",-1)  ; calculate pressure across all time, levels
  nt = 0 ; timestep to plot
  nl = 0 ; level to plot
;---Create simple contour plots
  wks = gsn_open_wks("png" ,"wrf_plot")
  res                       = True            ; plot mods desired
  res@gsnMaximize           = True            ; maximize plot size
  res@tiMainString          = times(nt)       ; main title
  res@cnFillOn              = True                 ; turn on color
  res@cnFillPalette         = "BlAqGrYeOrReVi200"  ; change color map
  res@cnLinesOn             = False           ; turn off contour lines
  plot                      = gsn_csm_contour(wks,p(nt,nl,:,:),res)
end

After running ncl 1.ncl, you should have a png (pdf) file starting by wrf_plot. Does it show any colors?
I was thinking maybe some problem is with your NCL.

Hi,
I run 1.ncl , the result is same. i 'll try reinstall NCL.
Thank for helping.

Hi.
I reinstall NCL 6.4 and it works now, seem problem with NCL 6.6.2.
Thank for support.

Hi. I tested it for this new issue and it was okay in my system (Fedora). However, it seems to have problems in Ubuntu.
I think your only option is to run PostWRF in CentOS, Fedora, Redhad, or similar OS. But not Ubuntu.
I will try to handle the issue to make it possible to work in Ubuntu without problem.

I found the problem. That was a bug in the code. I will try to solve it today.
Please clone PostWRF tomorrow. It will work for Ubuntu.


Nirant/upgrade-fastembed-version

All Submissions:

[ ] Contributions should target the dev branch. Did you create your branch from dev?
[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

[ ] Does your submission pass tests?
[ ] Have you installed pre-commit with pip3 install pre-commit and set up hooks with pre-commit install?

Changes to Core Features:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?

We need to fix our tests to run them without fastembed installed as well

#522


Types for Header component

Closes #564
Changes

Props types.
Fix type errors:

isResponsive default value to false.
ContentContainerComponent receives children parameter.

Documentation:

content prop type changed to node.

Should we remove Icons.jsx and add the icons inside the component, as it is done in Select or TextInput? Just to remove the .jsx file.


Feature/macros

:tada: This PR is included in version 11.1.0 :tada:
The release is available on:

11.1.0
GitHub release

Your semantic-release bot :package::rocket:


This fixes add iframe, if responsive = false and not have DOM Node

If we need the iframe for responsive option why should we add it for not responsive one?
http://codepen.io/sem_eleven/pen/bwgyqr

Duplicates #3333 and currently a work in progress.

Implemented in #3364, closing. Thanks @Ralf8686!


Upscaling

Thread Link for current discussion about feature:
https://discord.com/channels/925093472464146442/1099725981071200307

Implemented!


very usefull

Very nice document.
Very useful for me.

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

ID: ae9b6d88-c6c9-0411-fb06-1c20d3dc0bd7
Version Independent ID: 26314e11-e241-8f0c-2d84-23520ca9be7c
Content: WebView Mixed Content on Android - Xamarin
Content Source: docs/xamarin-forms/platform/android/webview-mixed-content.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Thanks @aghajani59


Rename the internal WebSockets implementation

We have a WebSockets implementation that is internal to SignalR (right now at least). It's causing some confusion, so we should rename it to something with SignalR in the name to reduce confusion.

Related, but not part of this issue: What's the future of that? Do we continue to use it or should we just move to the public implementation (i.e. the one based on CoreFX). Also, we need to reopen the discussion on creating a code-sharing arrangement that is better than what we're doing now (copying and pasting code...)


Carthage still embedding sub-frameworks

The shell script build phase that embedded the Alamofire and ObjectMapper frameworks into AlamofireObjectMapper was removed from the xcodeproj in #8, but it doesn't appear to be enough as building via Carthage still results in the embedded frameworks.
My Cartfile.resolved has the latest rev:
github "tristanhimmelman/AlamofireObjectMapper" "dc6fda6176e944c73caf0fe76b6bf1db5a37013f"

and I can confirm that if I run
$ cd Carthage/Checkouts/AlamofireObjectMapper/; xcodebuild

the build product does not have the embedded frameworks, so I wonder I Carthage is building the project via some other mechanism.

The Carthage README suggests a build can be simulated via carthage build --no-skip-current but doing so with the AlamofireObjectMapper project HEAD rev doesn't result in embedded frameworks either.

Very strange, I cleared out ~/Library/Developer/Xcode/DerivedData/ and then everything was good - it was almost as if the tools were grabbing an old version of the framework, bit like Carthage/Carthage#385.


Add an option to configure a Time Limit for quizzes

if time limit is configured user will have a limited time to complete the quiz; if quiz is not completed within the time limit it will be marked as a "FAILED" attempt

PR #2388

:+1:


Fix CPU resource leak issue

No more high CPU usage when idle
Affects both Linux and Windows, hence issue is fixed with this change.
:)

You can't be serious commenting a line and saying that this fixes the issue, this completely removes the play time feature. Please take things more seriously next time you “wish” to contribute to an open-source project. Closing this.


internal/unsafeheader compile: version "go1.16.6" does not match go tool version "go1.17.5"

After running oswee.generic.golang role Go seems to be broken.
Current system version is 1.17.5

Seems that sudo rm -rf /usr/local/go and clean role run helped.


Seller Has Dispute Button Before Fulfilling order

The dispute button is present and clickable for the seller when the order is accepted, but not fulfilled. Attempting to start a dispute shows a server error.
The button shouldn't show when it's not usable, should it?

Should this be in the desktop repo?

Should this be in the desktop repo?

Yep. I'll move it.


Convert inpage provider to Class

Convers the inpage provider to a class. Should exhibit no behavioral changes except now work even when web3.js tries to ruin it for no reason.
Unresolved Questions
Minor or patch version bump?
Misc

Bump eth-json-rpc-errors
Use @metamask/eslint-config

If I’m not mistaken, a similar situation is the historic reason for the proxy we wrap around the provider in the extension (truffle was doing something funny, deleting a property):
https://github.com/MetaMask/metamask-extension/blob/8e307f8d714bfd06051f68add4ef03af7eb8226b/app/scripts/inpage.js#L66-L70
This Proxy allows us to prevent bad consumers from manipulating the provider in unexpected ways. We probably could just @agoric/harden the provider before exporting, on the inpage-provider module itself, and solve both these problems of consumer-mutation.
I don’t see which part of this PR does that change (the class wrapping as described), though, so I’m not sure.

@danfinlay
The problem was that enable became unbound.
I've confirmed that the chosen solution works, and it is to bind the functions, see here: https://github.com/MetaMask/metamask-inpage-provider/blob/51f3d4a2da7f22d8e628f920470b22045a6b278d/index.js#L61-L68
I'm aware of the Proxy wrapping. I'd be down to harden it, although I'm hesitant because of all the voodoo web3 does. I wouldn't be surprised if we break it by doing that.


v2.0.4 (which is used by GEOSgcm fixture v11.4.0) fails when regridding merra2 to something other than 72 levels with remap_restarts.py

A user reported that with the v11.4.0 of the GEOSgcm fixture (which uses v2.0.4 of GEOS_Util) they were getting error when regridding merra2 restarts to something other than 72 levels with remap_restarts.py.
I was able to reproduce this. The upper air regridding just fails with all kinds of errors like this and you don't get the upper air restarts when I try to regrid merra2 restart to 181 levels:
 PSDRY_NEW:<PHONE_NUMBER>3441      PSDRY_OLD:<PHONE_NUMBER>5962      RATIO:   1.00000807053438368      DIF:  0.79336747883644E-02
 PSDRY_NEW:<PHONE_NUMBER>3441      PSDRY_OLD:<PHONE_NUMBER>3441      RATIO:   1.00000000000000000      DIF:   0.0000000000000
 Updating FV3 NonHydrostatic State
 Writing : fvcore_internal_rst_c0090_181L
pe=00000 FAIL at line=00037    NetCDF4_put_var.H                        <status=-57>
 MAPL_VarWriteNCpar_R8_1dError writing variable          -57
 NetCDF: Start+count exceeds dimension bound

pe=00000 FAIL at line=01735    NCIO.F90                                 <status=-57>
pe=00000 FAIL at line=00037    NetCDF4_put_var.H                        <status=-57>
 MAPL_VarWriteNCpar_R8_1dError writing variable          -57
 NetCDF: Start+count exceeds dimension bound

pe=00000 FAIL at line=01735    NCIO.F90                                 <status=-57>
 Writing : fvcore_internal_rst_c0090_181L U
 Global Area=<PHONE_NUMBER>10264.
 U      115.8030      -107.6895      0.1908877
 Writing : fvcore_internal_rst_c0090_181L V
 V      123.6169      -159.9293     -0.6733837
 Writing : fvcore_internal_rst_c0090_181L PT
 T      307.9005       162.3629       285.4557
 Writing : fvcore_internal_rst_c0090_181L PE
pe=00000 FAIL at line=00037    NetCDF4_put_var.H                        <status=-40>

Now I believe this is not interp_restarts.x, but rather something about the remap_restarts.py or other code in the GEOS_Util repo because if I update to this branch
feature/wjiang/add_ease_grid
which I had originally done because @weiyuan-jiang it was milan node aware, I'm able to regrid all the upper air restarts. So clearly it is not the actual fortran code but something about how it is executed but he python scripting.
So seems like clearly something have been fixed and you probably need to make a new release sooner rather than later that @sdrabenh  can use in a new fixture release. If there is stuff in this branch that is not ready for prime time, then we need to figurewhat has changed that fixed this and perhaps get just that in a new release.

Yes, that was a problem and it was fixed with this PR: https://github.com/GEOS-ESM/GEOS_Util/pull/44 we had release with fix https://github.com/GEOS-ESM/GEOS_Util/releases/tag/v2.0.5


Reproduce results

Upon examination of your code, I noticed the existence of a parameter named "sub_pixel," which is set to False by default. Upon further investigation, I discovered that enabling this parameter by setting it to True can result in improved performance. I am interested in understanding whether there are any potential drawbacks to enabling this parameter during inference. Furthermore, I would like to inquire about the rationale behind disabling this parameter by default.

It's just an attempt to save GPU memory and for demonstration. You should enable "sub_pixel" if you want better performance.


Replace DEFAULT_LAST_N in plotting with integer default + add % support

DEFAULT_LAST_N as default value is comfy but ugly for the end user: from the docs it's not clear what the default is.

Add float support: if 0.1 -> plot 10% of the series
Add an heuristic to plot e.g. 10% if it has < 1000 points, 5% if < 10_000 else 1%.

Last PR #235 partly addressed this. No weird logics for defaults. Will create a separate issue for % support.


Rollup Issue with Macros

Environment
System:

OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
Memory: 406.95 MB / 16.00 GB
Shell: 2.7.1 - /usr/local/bin/fish

Binaries:

Node: 12.3.1 - ~/.asdf/installs/nodejs/12.3.1/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.9.0 - ~/.asdf/installs/nodejs/12.3.1/bin/npm

npmPackages:

babel-plugin-styled-components: ^1.10.6 => 1.10.6
styled-components: ^4.3.2 => 4.3.2

Reproduction
package.json
"dependencies": {
    "prop-types": "^15.7.2",
    "styled-components": "^4.3.2",
    "styled-theming": "^2.2.0",
    "styled-media-query": "^2.1.2"
  },
  "devDependencies": {
    "@babel/cli": "^7.5.5",
    "@babel/core": "^7.5.5",
    "@babel/plugin-external-helpers": "^7.2.0",
    "@babel/preset-env": "^7.5.5",
    "@babel/preset-react": "^7.0.0",
    "@storybook/addon-actions": "^5.1.11",
    "@storybook/addon-knobs": "^5.1.11",
    "@storybook/addon-links": "^5.1.10",
    "@storybook/addon-viewport": "^5.1.11",
    "@storybook/addons": "^5.1.11",
    "@storybook/react": "^5.1.11",
    "babel-loader": "^8.0.6",
    "babel-plugin-styled-components": "^1.10.6",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-scripts": "3.1.0",
    "rollup": "^1.19.4",
    "rollup-plugin-babel": "^4.3.3",
    "rollup-plugin-commonjs": "^10.0.2",
    "rollup-plugin-json": "^4.0.0",
    "rollup-plugin-node-resolve": "^5.2.0",
    "rollup-plugin-peer-deps-external": "^2.2.0",
    "rollup-plugin-replace": "^2.2.0",
    "rollup-plugin-url": "^2.2.2"
  },
  "peerDependencies": {
    "react": "^16.9.0",
    "react-dom": "^16.9.0"
  },

.babelrc
{
  "presets": [
    ["@babel/env", {"modules": false}],
    "@babel/preset-react"
  ]
}

rollup.config.js
import babel from 'rollup-plugin-babel'
import commonjs from 'rollup-plugin-commonjs'
import resolve from 'rollup-plugin-node-resolve'
import external from 'rollup-plugin-peer-deps-external'
import json from 'rollup-plugin-json'
import url from 'rollup-plugin-url'
import pkg from './package.json'

export default {
  input: './src/index.js',
  output: [
    {
      file: pkg.main,
      format: 'cjs',
      sourcemap: true
    },
    {
      file: pkg.module,
      format: 'es',
      sourcemap: true
    }
  ],
  external: ['styled-components'],
  globals: { 'styled-components': 'styled' },
  plugins: [
    external(),
    json(),
    url(),
    babel({
      exclude: ['node_modules/**', '../../node_modules/**'],
      plugins: ['@babel/external-helpers'],
    }),
    resolve(),
    commonjs({
      ignoreGlobal: true,
      namedExports: {
        'node_modules/babel-plugin-macros/dist/index.js': ['createMacro'],
        'react-is': ['isElement', 'isValidElementType', 'ForwardRef'],
      }
    })
  ]
}

Steps to reproduce
Use create-react-app to create a new instance
Add in the listed dependencies above ^^^
Run npm run build
Expected Behavior
Should roll things up nicely 🥳
Actual Behavior
Throws an error when using import styled, { css } from 'styled-components/macro' – says:
[!] Error: 'css' is not exported by node_modules/styled-components/dist/styled-components-macro.esm.js
https://rollupjs.org/guide/en/#error-name-is-not-exported-by-module
src/styles/button.js (1:17)

I'm not so familiar with rollup, but I guess Babel should run on your file first. Without Babel there is no macro. It's being resolved by babel-macros-plugin at build time.

Most of the time Rollup build issues are caused by:

Misordered or misconfigured plugins
Transpilation (sometimes even double) to CJS which isn't needed
Misconfiguration of the commonjs plugin
Bundling externals when that isn't even necessary or intended

All of these lie outside of what makes sense as an issue here, so Rollup may have more helpful help channels.
But for now I'll go ahead and close this

Maybe it has something to do with this recommendation from Rollup

Using With @rollup/plugin-commonjs
When using @rollup/plugin-babel with @rollup/plugin-commonjs in the same Rollup configuration, it's important to note that @rollup/plugin-commonjs must be placed before this plugin in the plugins array for the two to work together properly. e.g.

https://www.npmjs.com/package/@rollup/plugin-babel


collection.insert is deprecated.

I used "mongolass": "^4.4.6" and got the follow warning.
"DeprecationWarning: collection.insert is deprecated. Use insertOne, insertMany or bulkWrite instead."
How to fix it?Thanks!

”Use insertOne, insertMany or bulkWrite instead.“


[SPARK-41422][UI] Protobuf serializer for ExecutorSummaryWrapper

What changes were proposed in this pull request?
Add Protobuf serializer for ExecutorSummaryWrapper
Why are the changes needed?
Support fast and compact serialization/deserialization for ExecutorSummaryWrapper over RocksDB.
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UT

@gengliangwang this is ready for review

Merging to master


Using the Nylas Python SDK, list last 10 emails that contain a keyword, like 'unsubscribe'

Using the Nylas Python SDK, list last 10 emails that contain a keyword, like 'unsubscribe'

hey @relaxedtomato can I work on this?

Go for it @SouvikDcoder!


fix v2 issues

Bugfix webView.html missing
Added npm run compile-wsl cuz Windows has no alias for cp 🙃

Looks good 👌 lots of 'changes' xD

wont work without mkdir

it will, I left a "placeholder" file in the dist folder 🙃

👌  placeholder is normally a .gitkeep tho. But we do want we want 🕺


SSL handshake failed / SSL error errno:1 reason: UNSUPPORTED_PROTOCOL

Home Assistant release with the issue:
0.90.1 / 0.90.1
Last working Home Assistant release (if known):
None, new installation (one month, earlier release as well
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
SSL Handshake fail & SSL Error using DuckDNS/Let's Encrypt Addon
Description of problem:
No connection possible via the https-protocol on several occasions per day.
It seems a random problem. When error is happening no https connection via DuckDNS possible. It stops working, than it just works again without any problem solving.

Additional information:
Using port-forwarding on EdgeRouter X port 8123 and 443 to RPI 3b+.

Hi,
I have similar problem, for me nothing through https and duckdns will work. http and duckdns works so i am using http at the moment. Same error message in logs as Rick
Error doing job: SSL error errno:1 reason: SSLV3_ALERT_CERTIFICATE_UNKNOWN

15:11 /usr/local/lib/python3.7/site-packages/homeassistant/core.py (ERROR) - message first occured at 15:06 and shows up 23 times

Error doing job: SSL handshake failed

15:11 /usr/local/lib/python3.7/site-packages/homeassistant/core.py (ERROR) - message first occured at 15:06 and shows up 24 times

Thanks

same here . tried many things disabling, etc, nothing helps.  i can log in fine thru https but thousands of errors in log

Same here, and I don't use the duckdns add on, just using a Let's Encrypt wildcard cert I pulled from another machine. SSL is completely broken!

What are you trying to connect from? Is it possible that only TLS 1.3 is being allowed and you're connecting with a device that doesn't support TLS 1.3?

I am connecting from Macbook/OSX High Sierra
So I just ran the following command to make sure TLS 1.3 was enabled from OSX:
sudo defaults write /Library/Preferences/com.apple.networkd tcp_connect_enable_tls13 1
I then restarted and went to link below to verify TLS 1.3 capability:
https://www.ssllabs.com/ssltest/viewMyClient.html
I then re-enabled https in configuration.yaml, restarted Homeassistant, and I can connect via https to the UI now.
To be honest I'm not sure if it was the OSX TLS change or the restart that did it, but if others want to try the same and report back, we'll know if that was the issue.

For me the error showed it self when i was using Tasker in android, bothg with api password and with long lived token using https-duckdns. And it also showed when using chrome both in an updated win10 aswell as android chrome. And rss_feed_template using android simple rss also broke with https.
as soon as a went over to http all was working.
Have tried reinstalling duckdns addon aswell as manually deleting ssl-files.
Nothing was working except going to http, and duckdns with http is also working.

Start by checking https://www.ssllabs.com/ssltest/viewMyClient.html
Then check what HA is even willing to accept: https://www.cdn77.com/tls-test

I don't know for sure if its a client problem.
The errors also show up at night and I sure am not using the webinterface at 3:43 ;-)
2019-04-03 03:43:41 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/handles/stream.pyx", line 609, in uvloop.loop.UVStream._on_eof
  File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:1056)
2019-04-03 03:43:41 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:1056)

Also at this time no other people trying to log even, I'm not seeing any "Login attempt or request with invalid authentication from" rows in the log.

Also at this time no other people trying to log even, I'm not seeing any "Login attempt or request with invalid authentication from" rows in the log.

If you have a site that is open to the world, bet on it being scraped by bots trying to find vulnerabilities like wordpress installs, phpmyadmin with default credentials, and other various things that people leave open and don't change.
also, your error is different from the two posted in the OP. OP's issues were:
[SSL: UNSUPPORTED_PROTOCOL], which likely means something isn't capable of what the server will allow
[SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN], which is likely a client trying to do SSLv3 and the server not allowing it
[SSL: HTTP_REQUEST] sounds like something is requesting things on port 80 instead of port 443.

Also at this time no other people trying to log even, I'm not seeing any "Login attempt or request with invalid authentication from" rows in the log.

If you have a site that is open to the world, bet on it being scraped by bots trying to find vulnerabilities like wordpress installs, phpmyadmin with default credentials, and other various things that people leave open and don't change.
also, your error is different from the two posted in the OP. OP's issues were:
[SSL: UNSUPPORTED_PROTOCOL], which likely means something isn't capable of what the server will allow
[SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN], which is likely a client trying to do SSLv3 and the server not allowing it
[SSL: HTTP_REQUEST] sounds like something is requesting things on port 80 instead of port 443.

You're right, the error is very different. Didn't know the last thing when it's requesting 80 instead of 443.
So why is it giving so many errors for port 80? Port 80 is closed from the internet. Nobody's on the network.
And I really do know that 'when it's open to the internet people are trying'.
That's why I'm also mentioning no login errors occur.

That's why I'm also mentioning no login errors occur.
you won't get a login error if someone is hitting yourdomain.duckdns.org/wp-admin/

is anything connecting to HA via IP address from inside your network using 8123 or http?

Just to report in on my problem, I think I fixed it!  I really suppose we all may have separate things causing this but for me it was port 80 was forwarded to my HA server ... This had not been a problem in the past but when I disabled that forward, the SSL errors seem to be gone!

could you check to see what your server is accepting? https://www.cdn77.com/tls-test
if it's only accepting TLS 1.3 I think you are able to relax the settings to also allow TLS 1.2.

this is what I get when I check it

TLS 1.3
NO

TLS 1.2
YES

TLS 1.1
NO

TLS 1.0
NO

SSLv3
NO

SSLv2
NO

Here we go again:
Error doing job: SSL handshake failed
09:33 /usr/local/lib/python3.7/site-packages/homeassistant/core.py (ERROR) - message first occured at 08:36 and shows up 175 times

What ever I do, I cannot login via HTTPS anymore. Every device is failing.
Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
  File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

With 0.91 freshly installed i tried going back to https through letsencrypt in duckdns addon, cause i dislike using http with HA open to internet.
I have same error still where https will not let me in at all, not through duckdns adress or https internal ip. I recieve access error, like there is nothing behind.
As soon as i ssh in and change configuration.yaml to use http all is working again.
Using chrome to access UI, Tasker to update sensors, simple rss widget in android for rss-data.
I have some of my config in git if there could be error in my config. the config i have in git is from before https stopped working, 0.90.0 for me. But i will update configuration.yaml so older versions can be used to check what i have changed and so on.
Hope someone might have a solution for this.

This has just happened to me on 0.91.3.  I've been using LetsEncrypt/DuckDns for over a year with no issues and this morning I can't connect at all to https://my_domain.duckdns.org:8123
Trying to visit on my phone I get
Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
  File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

instantly in the logs.
My Addon log
# INFO: Using main config file /data/workdir/config
+ Account already registered!
Fri Apr 12 06:52:45 BST 2019: OK
xx.xx.xx.xx
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing xxxxxxxx.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jun 22 11:38:14 2019 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!

My config:
http:
  base_url: xxxxxx.duckdns.org
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 3

ip_bans.yaml empty.  I'm at a loss!
I can access locally via IP address if I ignore browser certificate warnings.  All my automations are firing and my hadashboard is working too.

Hi, i just fixed my problem with this.
reference: https://community.home-assistant.io/t/bizarre-ui-access-issue/99055
duckdns addon seems to be the problem?

Same error message in logs:
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
My cert was expired, renew certificate - resolved issue

I recently upgraded to the latest and enabled the stream component. My SSL will occasionally stop working (can't connect) and then sometimes after will crash HA. Curious, anyone else have the new stream component on? May be related.

Same here @Mark612
After some time I can't access anymore my UI, stuck at performing TLS handshake.}
Nothing in the HA log when this happens.
I'll try to disable the stream component.

Same issue in log
2019-05-15 22:05:00 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed Traceback (most recent call last):   File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete   File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake   File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake     self._sslobj.do_handshake() ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
Duckdns log shows  + Valid till Jul 22 06:55:46 2019 GMT Certificate will not expire (Longer than 30 days). Skipping renew!

@sirs2k are you using the stream component? Just to check if it may be related or not.

@sirs2k are you using the stream component? Just to check if it may be related or not.

Not sure what the stream component is my friend...

@sirs2k are you using the stream component? Just to check if it may be related or not.

Not sure what the stream component is my friend...

This one https://www.home-assistant.io/components/stream/
Ok so I assume that the answer is no.

@sirs2k are you using the stream component? Just to check if it may be related or not.

Not sure what the stream component is my friend...

This one https://www.home-assistant.io/components/stream/
Ok so I assume that the answer is no.

Oh, nah I'm not using that :)

Same thing for me:
 File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete   File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake   File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake     self._sslobj.do_handshake() ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
Weird because I know the cert is valid and current. I'm not using DuckDNS, just Let's Encrypt on a domain pointing to my public static ip4.
Home assistant is just inoperable until I get this working as I've set callbacks to remote data to the domain that isn't validating.

Any Fixes in place for this yet?

I get this error when connecting to my HA with the internal IP.
So configured for https://xxxxxx.duckdns.org/
Can access it correctly from outside my network (via Port Forward 443=>8123). However from inside https://xxxxxx.duckdns.org/ nor https://xxxxxx.duckdns.org:8123/ is working.
So I then connected using the ip address. Browsing to https://192.168.x.y:8123/ works, but with browser SSL warning, and then the errors of sl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] came along.
Maybe this helps a bit to solve the problem.

You should edit your local hosts file and add record like this: your internal IP - DNS name
In windows path to file is: c:\windows\system32\drivers\etc\hosts
Record to add:
<IP_ADDRESS> xxxxx.duckdns.org
Or if your router support host-dns mapping, add mapping to your router configuration

@ittchmh Yes I already added the entry and it works without browser ssl error. Also HA did not show the ssl errors anymore.


ISPN-7826 LocalClusterExecutor doesn't apply timeout properly upon

chaining
https://issues.jboss.org/browse/ISPN-7826

Needs a rebase

Rebased

Integrated, thanks @wburns


Ignore import lists for producing completions

Given a module header like the one below with explicit import lists, ghcide should provide completions for all of Control.Monad and not limit to just join:
module MyModule where

import Control.Monad (join)

It would be great if selecting a completion would also check and expand the corresponding import list if needed.

@pepeiborra I would like to take a look at this one. Should I be starting in Completions.hs to find out where the list is getting restricted?

Completions are driven by the LocalCompletions and NonLocalCompletionsrules. To achieve the goal in this ticket, theNonLocalCompletions` rule needs to be relaxed to generate completions for the unrestricted imports. This should be quite easy, the code is in:
https://github.com/haskell/ghcide/blob/master/src/Development/IDE/Plugin/Completions.hs#L55-L81
Basically, use map unrestrictImport imps instead of imps

Great. Thanks for the pointer. Will review this item this week.

I did some preliminary research on this. Before, I take a wrong path approaching this, I wanted to confirm my understanding. Any feedback on this is appreciated.
Currently, the import list is being restricted because we map over  [GlobalRdrElt] at  https://github.com/haskell/ghcide/blob/863392b9b94777a069a2a31e9b909d1ce45e93d4/src/Development/IDE/Plugin/Completions/Logic.hs#L257.
My understanding is that GlobalRdrElt already only has the restricted elements based on the explicit import list.
To address this issue, we cannot use GlobalRdrElt anymore. Instead, we need to get all available completions, for each LImportDecl GhcPs. To accomplish that, we have to access the parsed module HsModule from each ImportDecl and then access the hsModExports values to build the CompItem.
This essentially means, the logic in cacheDataProducer will change entirely.
Is this a approach I can pursue?
Thanks!

This is not what I had in mind, almost no changes are needed if my suggestion below works.
We are in control of the import list used to generate the [GlobalRdrElt], since we explicitly call tcRnImportDecls. So just modify the import list before calling:
https://github.com/haskell/ghcide/blob/master/src/Development/IDE/Plugin/Completions.hs#L74

Thanks. That makes sense.

Regarding automatically expanding the import list would work here.
Will the command be part of the _command in Completion? (http://hackage.haskell.org/package/haskell-lsp-types-<IP_ADDRESS>/docs/Language-Haskell-LSP-Types.html#t:CompletionItem)
It could also happen that the same function comes from different imported modules. In that case, automatically extending would not work.  Can the _command handle it?

I think this is what _additionalTextEdits :: Maybe (List TextEdit) is for

Great. I will take a look at that. Thanks for the pointer.

Reopening for the automatic extension of import lists when needed.

Thanks for merging the previous changes.  I will leave some notes here on how I am approaching the pending task.
I think the _additionalTextEdits is the way to go.  For this I am thinking we need to do that following

(Add back) Continue carrying the original import we filtered, as part of our earlier change(#919). We will need this to decide how to update the text.
Update the CompItem record to capture this information by parsing the list in ImportDecl and generate a new Import statement.
Transfer over these values to CompletionItem.

As a side note, this information is already available in the resulting CodeAction, but I think we may not be able to use it since this become available on the consecutive round trip between client and server.

We have some code to extend import lists that would be appropriate to reuse:
https://github.com/haskell/ghcide/blob/master/src/Development/IDE/Plugin/CodeAction.hs#L935-L977
You won't be able to directly reuse the existing CodeAction since that is driven by a GHC diagnostic so you would need to typecheck the module for every CompItem, which would take too long.

@pepeiborra  I left some questions in the TODO list of the new PR. Can you or others provide suggestions on how to address those issues.  Thanks!
Also, in general, is it desired to discuss these on the PR or over here on the issues ticket?

Can we close this or should we keep this open till we get user feedback on how the imports are automatically added?

Also, in general, is it desired to discuss these on the PR or over here on the issues ticket?

We have not a established rule so i usually link or quote the relevant comments in both

Can we close this or should we keep this open till we get user feedback on how the imports are automatically added?

I think we can close this one and open new ones with the concrete issues or suggestions from users


502 bad gateway error

Hi,
I am getting the following error both from python and cli usage. archive.cli is working fine though.
Error (The Internet Archive): 502 Server Error: Bad Gateway for url: https://web.archive.org/save/www.google.co.in
I used it successfully last month. However, currently I am getting this error. I tried using the web page and it is working fine.
Thanks

I haven't tried it yet but maybe it's because they introduced a new SPN API: https://blog.archive.org/2019/10/23/the-wayback-machines-save-page-now-is-new-and-improved/


Figure out what link changes (if any) we need for signup

cc @ChristieQ

Quick grep for co.uk comes up with:
$ grep -Iinr co.uk src/* | grep -v _posts
src/site_source/devtrial/index.html:76:            — and — View
src/site_source/devtrial/index.html:99:            <a href="https://buyonline.rackspace.co.uk/cloud/userinfo?promo=UK_DevTierDiscountDeal"
src/site_source/marketing/the-changelog-lon.html:40:
Get  started with £35/month credit

src/site_source/marketing/the-changelog-lon.html:81:
Get started with £35/month credit

this is the new link, but the new site doesn't have the US vs UK link
https://cart.rackspace.com/en-gb/cloud/developer-plus

Are you saying the current site is busted since it sends everyone to US link?

When did we lose the "uk" and "everyone else" buttons?

I believe we were doing that through vwo, but @ChristieQ will have to chime in.


Define deployment process

On each merged PR?
On release?
Depending on decision, extend CI / CD to perform deployment.

Deploying to the test environment on PR merge would be nice so we can quickly get feedback. However that would require that merge results are relatively stable though so we don't annoy the pilots with bugs.
If we're not sure about that stability yet, I'd suggest we deploy manually for starters, but still try to deploy rather often (once a week or more often). Once we get the hang of Django, don't add depencies every couple days anymore and have some tests, we can deploy automatically on merge.

We could also use two branches test-system and production-system. Any commit/merge to them will automatically deploy to the corresponding system via GitHub Actions.

Sounds cool, but that would require automatic container builds. I'd like that, but we have to see if it's possible with the free quota.

Deployment according to Bene:
Here is what I did on my machine:
docker build . -t cpmonitor --platform linux/amd64 && docker image save cpmonitor -o ~/cpmonitor.image
scp -i ~/.ssh/id_rsa_live_germanzero_org ~/cpmonitor.image bene@monitoring-test.localzero.net:.
scp -i ~/.ssh/id_rsa_live_germanzero_org config/nginx/nginx.conf config/nginx/htpasswd bene@monitoring-test.localzero.net:tes
ting/config/nginx
scp -i ~/.ssh/id_rsa_live_germanzero_org docker-compose.yml bene@monitoring-test.localzero.net:testing

On testing:
docker image load -i ~/cpmonitor.image
# edit docker-compose.yml
-    build: .
+    user: "1003"
+    image: cpmonitor
-      - ./:/db
-
# shutdown the old
docker-compose down --volume
# start the new
docker-compose up --detach
# have a quick look at the logs
docker logs djangoapp
# get a shell
docker exec -it djangoapp sh
# in the shell see that there are migrations to apply
/cpmonitor $ python manage.py showmigrations
# apply them
/cpmonitor $ python manage.py migrate

SSH key handling in GitHub actions: These links might help:

https://stackoverflow.com/questions/60477061/github-actions-how-to-deploy-to-remote-server-using-ssh
https://zellwk.com/blog/github-actions-deploy/

Try to avoid that the private key is part of a command line with
printenv SSH_PRIVATE_KEY > ~/.ssh/id_ed25519

Not sure, if https://github.com/marketplace/actions/install-ssh-key does that right.

Looked into https://github.com/marketplace/actions/install-ssh-key and it seems pretty solid. Probably best to use it and rely on its documentation.

I built a simple deployment script based on the deployment docs in the README and pushed it to a branch (see here). It still needs work (especially regarding error handling during the SSH commands), but it's a first step...

We now have a script that can perform the deployment, but it still struggles with creating tags from within github actions:

https://github.com/GermanZero-de/klimaschutzmonitor/actions/runs/6393685249/job/17353430022

The following step can be added to deploy.yml with an if-condition triggering only if the environment is testing:

Test only: Before doing migrations copy DB from production.


Footer icon spacing

From issue: #49.
I added some margin to the icon.
I also added some padding-left to the footer itself
I used a Footer.css file, because I really do not like using inline styles.
A screenshot:

seems like you have other changes as well in this PR. You might need to create a new branch from main and then add these changes on top of that.

I created a branch for the footer from a previously used branch. That is in a different PR.


Problem with custom error messages on empty input fields

Description
To check if a confirmation field contains the same value than the main input field I am using a very small javascript function which just compares both values on keyup and if they missmatch adds the invalid class to the second input which should confirm the new password.
The problem is that if the confirmation input field is empty it displays the custom error message at an incorrect position when the invalid class is applied to such an empty input field.
Repro Steps
Use the codepen I provided and just input something in the first input field.
Screenshots / Codepen
http://codepen.io/clearwood/pen/BWGBaB

An empty input field does not get the active class which applies the transform.
So far this is by design.
You have a special case (which is not so special), linked inputs where the validation of the seconds input is triggered by the first or another input. Normally the empty inputs are not directly validated, just on submit or when something is typed.
Try this codepen, not sure if this is what you meant: http://codepen.io/anon/pen/JWeoBr

Thank you very much for this way to fix it for me, i just wonder if there ever should be a time when the success or error message should not be in place directly beyond the input field, so I would like to bring into discussion whether this position should be fixed for those message on input fields and not changed during the transformation.

Could depend on how the Material Design guidelines of Google define this and if not how it should work. I did not check how it should be. The CSS transformation is applied to the labels (the error / success message seems to be in a label too).

@DanielRuf But it is a problem because only the main label should be transformed, and the error/success label shouldn't be affected by this (it should be in it's "transformed" style by default). Perhaps we could just make a separate label for the error/success message, or we could keep it the way it is and move the main label to the :before and apply the transformation on it.

@NonameSLdev right, splitting it makes somehow sense as the transform on the label creates problems as we see.

@NonameSLdev it should solve also #2697 and #4506

@DanielRuf Could we update forms.js to correctly/completely use HTML5 form validations (HTML5 ValidityState? So changing element[0].validity.badInput to element[0].validity.valid or element[0].checkValidity() would then allow a developer to use setCustomValidity(error) to set the state of the input label. Then some logic could be added to take the error message input.validationMessage and set it to the label's 'data-error' attribute. I'd be happy to make a PR with these changes, but I figured discussing it first would be better.

Error and success messages have been decoupled from the label element in aa03660 on the v1-dev branch. These styling issues will be fixed for v1


Version 0.3

We have finished the client part in Version 0.2 #2. Starting from version 0.3, we will focus on implementation of the server part.
Tasks of version 0.3:

[x] Specification of Authorization Code Flow of OAuth 2
[x] Specification of Implicit Flow of OAuth 2
[x] Specification of Password Flow of OAuth 2
[x] Specification of Client Credential Flow of OAuth 2
[x] Bearer Token rfc6750
[x] Authorization Server
[x] Resource Server

Note: take OpenID Connect into account when designing these specifications
Also, we need a real provider in Flask:

[x] Implement an OAuth 2 provider in Flask.

[x] Test cases for OAuth 2 provider
[x] Documentation

Deadline: The end of this year.

I'll create a real OAuth 2 server in playground.


kubei: init at 1.0.11

Motivation for this change
Kubei is a vulnerabilities scanning and CIS Docker benchmark tool that
allows users to get an accurate and immediate risk assessment of their
Kubernetes clusters. Kubei scans all images that are being used in a
Kubernetes cluster, including images of application pods and system pods.
https://github.com/Portshift/kubei
Related to #81418
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120703 run on x86_64-linux 1

1 package built:

kubei


Converted Image From Batch Came Out As 0 Bytes

Describe the bug
I did a few batch conversions that were successful with one image (out of 100+) that appears to be 0 bytes.
The odds are way better than last time, but I figured I should do the usual reporting in case it's indicatave of a deeper issue and not just a fluke.
To Reproduce
Steps to reproduce the behavior:
All I did was a large batch conversion of images (various-to-jpeg 96 quality).
Screenshots
It just gives the "Oops (!)" Screen in fullview and "Jpeg" on the thumbnail. Info has correct information about the file name, but says it is 0 bytes.
System information and logs:
Package: deckers.thibault.aves.libre
Installer: dev.imranr.obtainium
Aves version: 1.8.9-libre, build 10002
Flutter: stable 3.10.3
Android version: 13, API 33
Android build: lineage_ocean-userdebug 13 TQ2A.230505.002 eng.root.20230607.204517 dev-keys
Device: motorola moto g(7) power
Geocoder: ready
Mobile services: not available
System locales: en_US
Storage volumes: /storage/emulated/0/, /storage/3062-3833/
Storage grants: /storage/emulated/0/Movies/, /storage/3062-3833/Movies/, /storage/emulated/0/Pictures/, /storage/emulated/0/Documents/, /storage/emulated/0/DCIM/, /storage/3062-3833/Pictures/, /storage/emulated/0/Download/Pixel 4 Downloads and Photos/, /storage/emulated/0/Download/Image Converter/
Error reporting: false
aves-logs-20230621_202343.txt
Additional context
This has happened a time or two in the past and I just got around it by redownloading the file. But, I can't see a specific pattern to what kinds of files or anything else.

For the image that failed to convert, did you retry to convert the same image and it worked?
I'm trying to reproduce the issue by converting several hundreds of images at once but I can't reproduce the issue. I wonder whether it depends on the image, or the running environment (for example low memory, or low storage), or the OS, or something else.
Do you use a regular Lineage or some derivative? Do you enable some special memory or security features?

It might be related to low storage. This last time, it was the last file output from the converter, so it could be that it "finished operation" but couldn't write all the information it actually needed to. And I did that conversion to try to help free up space, so it may have filled too much space before I could remove the original files.
And my Lineage is the MicroG build of the stable releases. No special developer options tweaked, especially not with regards to memory.

For an update: I haven't encountered this particular issue since, on any of the devices I use Aves with. So, it is very likely just because of the available storage space running out.
I guess it's not a bug, then. But it could benefit from intelligently responding to this by stopping operations at the last successful output and inform the user about the error (Warning/Error: Could not complete operation. Reason: insufficient storage.)


(new) nixos test not run automatically

The features list includes "allow to build nixos tests", so i expect that a nixos test, that is added in a PR, get executed.

From https://github.com/NixOS/nixpkgs
   2a1bda47f7a..1b115789685  master     -> refs/nixpkgs-review/0
$ git worktree add /home/davidak/.cache/nixpkgs-review/pr-103705-1/nixpkgs 1b1157896857ae1467f5b0a421dee86388a55638
Preparing worktree (detached HEAD 1b115789685)
Updating files: 100% (24735/24735), done.
HEAD is now at 1b115789685 Merge pull request #115062 from manveru/cbonsai
$ git merge --no-commit 10fa80fd300ce9cd081b578621861332ddf3e411
Auto-merging pkgs/top-level/all-packages.nix
Auto-merging nixos/tests/all-tests.nix
Auto-merging nixos/modules/module-list.nix
Automatic merge went well; stopped before committing as requested
$ nix --experimental-features nix-command build --no-link --keep-going --option build-use-sandbox relaxed -f /home/davidak/.cache/nixpkgs-review/pr-103705-1/build.nix

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/103705

1 package blacklisted:
tests.nixos-functions.nixos-test

2 packages built:
plik plikd

error: --- Error ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ nix
build log of '/nix/store/immmi2c41zdcxzrw1bii0qv4q9m20f5x-nixos-system-nixos-test.drv' is not available
Posting result comment on https://github.com/NixOS/nixpkgs/pull/103705
$ nix-shell /home/davidak/.cache/nixpkgs-review/pr-103705-1/shell.nix

Or is it expected behavior that nixos tests get blacklisted and have to get enabled manually?
In that case, please add an explanation to the output and instructions how to run them. Maybe even interactive from within the nix-shell.
Running tests like described in the Readme works.
[davidak@gaming:~/code/nixpkgs]$ nix run -f channel:nixos-unstable nixpkgs-review -c nixpkgs-review pr --post-result --token ***** -p nixosTests.plikd 103705
$ git -c fetch.prune=false fetch --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/103705/head:refs/nixpkgs-review/1
remote: Enumerating objects: 51, done.
remote: Counting objects: 100% (43/43), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 25 (delta 20), reused 16 (delta 12), pack-reused 0
Unpacking objects: 100% (25/25), 8.39 KiB | 859.00 KiB/s, done.
From https://github.com/NixOS/nixpkgs
   1b115789685..7f76da8f7a4  master     -> refs/nixpkgs-review/0
$ git worktree add /home/davidak/.cache/nixpkgs-review/pr-103705-2/nixpkgs 7f76da8f7a497f216ca02a673fb4e051f0ed8754
Preparing worktree (detached HEAD 7f76da8f7a4)
Updating files: 100% (24735/24735), done.
HEAD is now at 7f76da8f7a4 Merge pull request #115118 from obsidiansystems/prebuilt-android-fix-eval
$ git merge --no-commit 10fa80fd300ce9cd081b578621861332ddf3e411
Auto-merging pkgs/top-level/all-packages.nix
Auto-merging nixos/tests/all-tests.nix
Auto-merging nixos/modules/module-list.nix
Automatic merge went well; stopped before committing as requested
$ nix --experimental-features nix-command build --no-link --keep-going --option build-use-sandbox relaxed -f /home/davidak/.cache/nixpkgs-review/pr-103705-2/build.nix

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/103705

1 tests built:
nixosTests.plikd

Posting result comment on https://github.com/NixOS/nixpkgs/pull/103705
$ nix-shell /home/davidak/.cache/nixpkgs-review/pr-103705-2/shell.nix

Thanks for providing this great tool!

I have seen that the PR adds a nixos test and
1 package blacklisted:
tests.nixos-functions.nixos-test

in the log, so my conclusion was that that is related to the added nixos test.
The "allow to build nixos tests" in the readme can be understood as it is an option to run nixos tests and it is described how to do so.
So my question is, would it make sense to run them automatically? I think that would make sense when you review and test a PR.
What do you think?

Yes. Feel free to implement that. However note that tests should be not evaluated with the other packages and build separately as they can consume a lot of memory. My recommendation is to retrieve the tests name from passthru.tests in nixpkgs_review/nix/evalAttrs.nix and than build those tests after the normal build and before starting the nix-shell.


Package is incompatible with the CPU-only PyTorch

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
Details about  conda and system ( conda info ):

$ conda info

     active environment : base
    active env location : /shared/raimis/opt/miniconda
            shell level : 1
       user config file : /home/raimis/.condarc
 populated config files : /home/raimis/.condarc
          conda version : 4.10.1
    conda-build version : 3.21.4
         python version : 3.7.10.final.0
       virtual packages : __cuda=11.3=0
                          __linux=3.10.0=0
                          __glibc=2.17=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /shared/raimis/opt/miniconda  (writable)
      conda av data dir : /shared/raimis/opt/miniconda/etc/conda
  conda av metadata url : https://repo.anaconda.com/pkgs/main
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          file:///shared/raimis/opt/miniconda/conda-bld/linux-64
                          file:///shared/raimis/opt/miniconda/conda-bld/noarch
          package cache : /shared/raimis/opt/miniconda/pkgs
                          /home/raimis/.conda/pkgs
       envs directories : /shared/raimis/opt/miniconda/envs
                          /home/raimis/.conda/envs
               platform : linux-64
             user-agent : conda/4.10.1 requests/2.25.1 CPython/3.7.10 Linux/3.10.0-1160.21.1.el7.x86_64 centos/7.9.2009 glibc/2.17
                UID:GID : 1006:1006
             netrc file : None
           offline mode : False

openmm-torch installs with the GPU-enabled PyTorch as expected:
$ conda create -n tmp -c conda-forge openmm-torch pytorch=1.8=cuda*

but it fails to install with the CPU-only PyTorch:
$ create -n tmp -c conda-forge openmm-torch pytorch=1.8=cpu*

Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package pytorch conflicts for:
openmm-torch -> pytorch-gpu[version='>=1.8.0,<<IP_ADDRESS>a0'] -> pytorch[version='1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.7.1|1.8.0',build='cuda102py36h8620ce9_1|cuda100py36hd82b6f9_1|cuda92py37hc3ec645_1|cuda100py38h679e3f5_1|cuda101py36h42dc283_1|cuda101py39h41d04a9_1|cuda102py38h9f8c3ab_1|cuda102py37h4454d97_0|cuda102py38h540557e_0|cuda110py36h7ef7e1d_0|cuda112py38h3bc52bc_1|cuda111py39h37e5b68_1|cuda111py36h3cb1cac_1|cuda112py36h5fea6e2_1|cuda112py37h946b90b_1|cuda111py37h50e976f_1|cuda112py39h716d6ff_1|cuda111py38he2736ed_1|cuda110py39hbc72f07_0|cuda110py38h65e529b_0|cuda110py37h5fb8b0b_0|cuda102py39hf89b2ab_0|cuda102py36hf4eb8d7_0|cuda92py38hb6ed0dd_1|cuda100py39h2b73809_1|cuda102py39h09d0254_1|cuda92py39hde86683_1|cuda101py38h2499a06_1|cuda100py37h50b9e00_1|cuda102py37h4d98c68_1|cuda101py37h7589291_1|cuda92py36h7ecc001_1']
pytorch==1.8[build=cpu*]
openmm-torch -> pytorchThe following specifications were found to be incompatible with your system:

  - feature:/linux-64::__glibc==2.17=0
  - feature:|@/linux-64::__glibc==2.17=0
  - openmm-torch -> __glibc[version='>=2.17']
  - openmm-torch -> cudatoolkit[version='11.1|11.1.*'] -> __glibc[version='>=2.17,<3.0.a0']

Your installed version is: 2.17

The package should depend on pytorch, but not pytorch-gpu.
conda search -i -c conda-forge openmm-torch

openmm-torch 0.2 py39h64e9529_0
-------------------------------
file name   : openmm-torch-0.2-py39h64e9529_0.tar.bz2
name        : openmm-torch
version     : 0.2
build       : py39h64e9529_0
build number: 0
size        : 147 KB
license     : MIT
subdir      : linux-64
url         : https://conda.anaconda.org/conda-forge/linux-64/openmm-torch-0.2-py39h64e9529_0.tar.bz2
md5         : a211ea29c811e2400f7634590bfbd18a
timestamp   : 2021-05-12 22:35:10 UTC
dependencies:
  - __glibc >=2.17
  - cudatoolkit 11.0|11.0.*
  - libgcc-ng >=7.5.0
  - libstdcxx-ng >=7.5.0
  - ocl-icd >=2.3.0,<3.0a0
  - ocl-icd-system
  - openmm >=7.5.1,<7.6.0a0
  - python >=3.9,<3.10.0a0
  - python_abi 3.9.* *_cp39
  - pytorch
  - pytorch-gpu >=1.8.0,<<IP_ADDRESS>a0

This was done intentionally to mimic behavior done at OpenMM: users will always get a GPU enabled variant to ensure they have access to the best performance instead of blindly falling in a CPU-only env.
Is there an use case where the CPU only version is required?

Is there an use case where the CPU only version is required?

CI/CD without a GPU to minimize the number of packages to download and install.
As this intentional and compatible with OpenMM, let it be so.


When opening an Inventory, the entire Log changes.

???
(Probably an issue that can be fixed at the same time as swapping lobbies)

This has actually become more confusing as I went to diagnose the bug. I'm not sure how to fix it.

The cause of the bug has been found!
It occurs because the items gain/lose sell prices.

Fixed in version 0.2.2.


Retransmission and new server API

I know this pull-request is a bit disruptive :)
When I implemented retransmission I found some part are missing in this CoAP implementation.
like token correlation, piggy-backed ack, etc..
It's still a work in progress, but I wanted to show it before I change too much of the original project

About piggy backed & separate responses:
https://tools.ietf.org/html/rfc7252#section-5.2

Would you be interested in helping maintain this?  I don't like having these things sit out too long.  I'd rather have someone actively using it push it forward than to hold it back since my needs are met.

Hi, sorry for the delay, august break :smile:
Thanks for the rust. Today it's not part of my CoAP stack (I mainly use Californium & Java) but I think I can help maintaining the project. Today my main focus is implementing DTLS with Go, with is a quite long challenge.


fix: Fix to delete cookie when AppSubURL is non-empty

Problem
We were observing a redirect loop, either when logging out or when trying to view a private repo with an expired session. This only seems to happen when AppSubURL is non-empty.
Using release/v1.21, several commits after the 1.21.10 release, on a server recently upgraded from 1.20.
Steps to reproduce:

Visit https://mydomain.com/sub_path/user/login (where ROOT_URL is configured to https://mydomain.com/sub_path/)
Click Remember This Device
Login
In the browser's dev tools, alter the Path of the gitea cookie from /sub_path to /sub_path/
Attempt to logout
You will now be redirected back to the home page

The logout only clears cookies in the /sub_path, not /sub_path/. Due to PR https://github.com/go-gitea/gitea/pull/29599, the login page now sees the gitea cookie that can't be deleted, auto logs in, and then redirects back to the home page.
Existing code already tries to delete the cookie at /sub_path. https://github.com/go-gitea/gitea/pull/24107/files#diff-7c540b84d46e33f1e7b33c7a4cc4daed15b765c11da81070d2313b42251aa48eR48-R53. But it doesn't delete cookies at /sub_path/. https://github.com/go-gitea/gitea/pull/29552 changed the default value of the path, but it didn't update code that clears it.
This is problematic because the longer path is more specific as far as the browser is concerned, and the browser prefers the old, outdated cookie with the trailing slash over newly set cookies. A similar problem may occur when no path is set on the cookie since browsers use the current page's path to determine the path of the cookie. The new, correct cookie path at the root should be /, but cookies without a path set may override it.
The workaround was to clear browser cookies, which is not desirable.
Solution
This PR changes it so that whenever a cookie is written, we also clear legacy cookies that could override the cookie currently being written. In this way, cookies are lazily upgraded. In the interim, legacy cookies are still sent from the browser to the server and used. This is fine.
Cookies are written in modules/web/middleware/cookie.go, but also deep inside the chi dependency. Rather than modifying the latter, we clear legacy cookies whenever regenerating a session. This is required to handle the case of an expired session that would otherwise cause a redirect loop.
Open to suggestions on a better approach.

I made a mistake. I will recreate the PR or re-open once fixes have been made.

Found more browsers that hadn't been cleared, and after some more testing, it seems like this doesn't completely solve the problem. Converted the PR to draft until we figure it out.

I think we need to settle on what the desired handling of cookies is, because it's not clear to me.
Here is what I propose (please correct me if anyone has other insights):

The application SHOULD treat cookies with trailing / equivalent to no trailing slash (i.e. ignore trailing slash)

This is mostly needed to fix the intermediate issue where we users have both cookies with and without trailing slash

The application should NOT delete or modify cookies at the root domain if there is a sub path (i.e. always use AppPath for cookies)

Because users could have installations at domain/path1 and domain/path2

Is this correct?
I think if a user as a cookie at the root domain, but the application has a path, the cookie will be ignored.

Based on https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#path_attribute, I recommend:

if the parsed path of ROOT_URL is either "/" or "", set cookie on "/"
if the parsed path of ROOT_URL is any other value, strip a single trailing slash off it and set cookie path to the resulting value.

Based on reading MDN, I recommend:

if the parsed path of ROOT_URL is either "/" or "", set cookie path to "/"
For any other value, strip a single trailing slash off it and set cookie path to the resulting value.

#29534 should already do that.
The issue is that there are cookies leftover from the old approach in people's browsers.
I think this PR fixes logging out, for users who were already logged in. But if someone is logged out and trying to login, code will still try to use the old cookie with the incorrect path.
I'm working on an additional change that clears cookies when logging in, just before setting them again.

The issue is that there are cookies leftover from the old approach in people's browsers.

Sounds like a good idea to issue path=$oldpath; expires=Thu, 01 Jan 1970 00:00:00 GMT during logout or login to eliminate any previously wrongly set cookies.

I think instead of doing this in the middleware, it'd be better to make setting.SessionConfig.CookiePath have the correct value in first place.

@wxiaoguang any other insight?

I broke some integration tests, so I'm working on that.

TBH I am not sure whether my question about cookie path "" vs "/" is right, whether they are the same in browsers ....

TBH I am not sure whether my question about cookie path "" vs "/" is right, whether they are the same in browsers ....
If it is unclear/risky, maybe we should skip the "" vs "/" case .... just like your previous approach.

They're not the same. When the Go code sees a path of "", it doesn't set a path on the cookie. The default path when a path is not set depends on the URI of the page when it's set. I don't think we want cookies to be set for various paths depending on the page that was accessed. Therefore, I'm pretty sure that the latest approach of clearing out the cookie with path "" in favor of "/" is correct. Preferring "/" is much simpler to reason about. There will only be one at the root, not potentially many overriding each other depending on the current URI of the page.

Reverting the change to delete cookies with no path fixed the integration test failures. So maybe we don't want that change. I'm a little unclear about the reasoning behind this.


Fix Program User Table Name

This PR is submitted for a minor fix, to change table name from "program_members" to "program_user".

When I prepare to deploy holpa PR #33, I did a testing in holpa staging env before deployment.
Error occurred regarding non existing table "program_members".
I proceed to merge the PR and staging env deployment.
"composer install" in deployment script failed because:

Required package "stats4sd/filament-team-management" is in the lock file as "dev-main" but that does not satisfy your constraint "^1.0".

I run "composer update" to fix it. Aimed to resume service in staging env first.
"composer update" executed successfully.
However, same error persists after deployment.
I go back to my local env for debugging. I updated User model in vendor/stats4sd/filament-team-management to see if it helps. Problem resolved. I did the same change in staging site via remote login.
Now I submit a PR to fix it.

Executed command and output in holpa staging env for reference:
PS C:\public\holpa-platform> composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
- Required package "stats4sd/filament-team-management" is in the lock file as "dev-main" but that does not satisfy your constraint "^1.0".
This usually happens when composer files are incorrectly merged or the composer.json file is manually edited.
Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md
and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r
PS C:\public\holpa-platform> composer update

Found another issue in holpa, not sure if I should post it here...
App panel > Settings > My Team

in local env, it works well to show xlsforms relation manager
in staging env, error occurred:

Call to undefined method Stats4sd\FilamentTeamManagement\Models\Team::xlsforms()

P.S. I pulled latest code from dev branch in both local env and staging env already.

Found another issue in holpa, not sure if I should post it here...
App panel > Settings > My Team

in local env, it works well to show xlsforms relation manager

in staging env, error occurred:

Call to undefined method Stats4sd\FilamentTeamManagement\Models\Team::xlsforms()

P.S. I pulled latest code from dev branch in both local env and staging env already.

This doesn't seem relevant to this PR? Seems like an issue with the Holpa staging environment to me...


downloaded runelite, cant access quest helper

i downloaded runelite and cant figure out how to get quest helper on there. if i could get some help with this i would really appreciate it. thanks.

Basically you need to install it from plugin hub.
Steps

Click the settings icon in Runelite.
Click plugin hub.
Search for the quest helper plugin in the search bar.
Finally, install the quest helper plugin.

Hope this helps!


Disable skip

Is there anyway to disable the skip button or remove/hide the button?

I guess you can
Just give empty string to skip text,
If you want to skip to the last page then you should take a look at the PR i've submitted,  I Hope that helps you 😃


[Bug] App crash

Describe the bug
Updated Android to 12.0 on galaxy s21 ultra and unable to open app. Keeps closing upon open. Cleared data and cache, updated app, Uninstalled and reinstalled with no change. Uninstalled and installed with apk not through play store with no change.
How to Reproduce
1 launch app
2 app crashes
Expected behavior
Expect to work
Environment
- DDG App Version:
- Device:galaxy s21 ultra
- OS:Android 12.0

Sorry about that. It seems a Samsung related issue. I think they are releasing to some devices a beta version of Android 12 which has some bugs. I've found a thread where users are facing the same issue in multiple apps:
https://eu.community.samsung.com/t5/galaxy-s21-series/official-android-12-one-ui-4-0-installed-on-s21-ultra-5g-but/m-p/4340763


GFP data

A GFP waveform of all data plotted (EEG or MEG) would surely be of great value !

where would you display this? are you aware of the butterfly mode? press
"b" to see it
Message ID: @.***>

The objective is to annotate epileptic spikes on the fly, precisely on the maximum of gfp in order to capture the maximum of activity, and after to average the spikes temporally aligned.
Having the gfp could be a nice way for that.
Maybe  the same as butterfly mode could be nice ? Press on g and switch to gfp trace ?
Best
JJ
Le 10 avr. 2022 à 21:45, Alexandre Gramfort<EMAIL_ADDRESS>a écrit :
where would you display this? are you aware of the butterfly mode? press
"b" to see it
Message ID: @.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/mne-tools/mne-qt-browser/issues/112#issuecomment-1094356144, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYUXF5XY6MXFZZNX235CPVLVEMVWBANCNFSM5TBDS5NA.
You are receiving this because you authored the thread.Message ID: @.***>
ATTENTION : Ce message a été envoyé par un expéditeur externe, en dehors des Hospices Civils de Lyon. Ne cliquez pas sur les liens ou n’ouvrez pas les pièces jointes… sauf si vous connaissez l’expéditeur et que vous lui faites confiance !

yes that sounds doable !

Message ID: @.***>


feat: add table name pragma and accessors

Closing in favor of #18 since #18 incorporates the same changes, though slightly modified by later commits (now squashed into a single commit for that PR).


Update cache-tag-helper.md

Fixes #6971

Thank you for your contribution, @songgun! Your changes will go live within the next 24 hours.

@songgun Great fixes, this is a HUGE improvement to the docs. Thanks again.


Support for common options, or option inheritance

Does Click have a way to support common options between different programs/CLIs?
To give more context, our package provides multiple programs: we'll call them process_input, do_design, compress_files. All of these commands are expected to have a --logfile option; that is, they should be able to be invoked on the command line like the following
process_input --logifle=/path/to/logfile …
do_design --logfile=/path/to/other_logfile …
…

In Click, we could simply repeat the same option in every CLI, e.g.,
# in process_input.py

@click.option('--logfile', help='Path to log file', …)
def main():
    …

# in do_design.py

@click.option('--logfile', help='Path to log file', …)
def main():
    …

# in compress_files.py

@click.option('--logfile', help='Path to log file', …)
def main():
    …

The obvious downside here is a DRY principle violation.
From reading the Click documentation, I get the idea that a Click-centric way to not repeat the same option is to turn the individual programs into subcommands (à la Git's CLI) and make the common/global option part of the master command. This would turn the invocation of our programs into the following:
my_program --logifle=/path/to/logfile process_input
my_program --logfile=/path/to/other_logfile do_design
…

The challenge here is — again, obviously — this changes the CLI of our programs, which incurs a cost to our users.
Does Click provide a route for us to define common options in one location, and use those options across multiple programs' CLIs?
Currently, we use argparse to construct our CLIs. We define a parent CLI with common options in a module, and the individual programs' CLIs inherit these common options via the parents parameter.

log_option = click.option(...)

@click.command()  # or group
@log_option
def foo():
    pass

@click.command()  # or group
@log_option
def bar():
    pass

@untitaker Thanks for your answer! I appreciate this!


docs: removed unnecessary exports previously added to api docs

Summary
Changes

Please provide a summary of what's being changed

This PR removes not supported api docs annotations and reverts exports that were previously added. Instead we now use missing-exports plugin to collect all implicit exports in api docs.
Current api docs build looks clean:
><EMAIL_ADDRESS>docs-generateApiDoc
> typedoc .

[info] Loaded plugin typedoc-plugin-zod
[info] Loaded plugin typedoc-plugin-missing-exports
[info] Converting project at ./packages/commons
[info] Converting project at ./packages/jmespath
[info] Converting project at ./packages/logger
[info] Converting project at ./packages/metrics
[info] Converting project at ./packages/tracer
[info] Converting project at ./packages/parameters
[info] Converting project at ./packages/idempotency
[info] Converting project at ./packages/batch
[info] Converting project at ./packages/parser
[info] Merging converted projects
[info] Documentation generated at ./api

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #2993

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

I see that we've added the packages/testing in the typedoc.json file, but I don't see it in the build API docs outputs.
I just wanted to make sure the package does not end up in the published docs.

I have added it to the exclude block.


"Start" Label has bug

#- the logic to set start label hide or not isnt correct, sometime it may cause bug.
sometime it may happen this.


This is a non-working pull request. Please fix to be merged.


Activate GUI for changing custom uniforms at runtime

After pressing the option button I can see any only the performance window in the upper left corner.
No Open Controls button like the one in your example.
Can you please provide more explanations on how to activate GUI ?
Thanks.

I'm having a similar issue. In a previous version of VSCode, or this plugin, I was able to see the Uniforms control GUI...

Same issue here, was trying to figure out how to use DAT.gui with glsl-canvas but it doesn't seem to be working anymore.

Same issue here

@AK82, @Chilus, @dom1817, @monster916 issue has been resolved in latest version 0.2.14. Thank you for your submissions, and sorry for late reply.

Great thanks! I think it would be very useful to specify in the readme file that the DAT.gui controls will be only available to uniforms that are declared in settings.json


[docs] (Add): Modern Python developer step by step roadmap

https://roadmap.sh/python

This is a useless yet distracting roadmap for beginners, there is already a roadmap in this repo by geeks for geeks, thanks for you contribution, you can do other commits that are unique to this repo.


"Attendees must read and follow our Code of Conduct"

Broken link on meetup and ctfeds.org ...

Fixed! Thank you for spotting it and letting us know. :)


IGNITE-8407  Wrong memory size printing in IgniteCacheDatabaseSnaredManager

usages of getInitialSize()/getMaxSize()) should go with U.readableSize(*, false)

IGNITE-8407
Closed


docs: added examples for setup and teardown apis

Maybe we could add a one line comment in each snippet explaining what is achieved? Like "count the number of tests", and "done with the first test" (maybe we could look for a better example for afterEach 🤔)

@patak-dev okay, I'll add that now

@patak-dev check it out and also suggest

@Snugug should we add examples for each option in the API section? Maybe it is better to move these to a guide and keep the API section compact?

@Snugug should we add examples for each option in the API section? Maybe it is better to move these to a guide and keep the API section compact?

I think having quick examples in the API section is a good thing; I personally find API documentation that's just types and arguments to be super unhelpful. As such, I think adding examples here are a net positive for the docs. To your point @patak-dev, I think it would be good to have a guide for these items, explaining them more in-depth, and have these examples be quick.
That said, I think these examples could be improved; the way they're written, if I skim them quickly, it looks like I can actually get something out of these because they're returning functions. I think to make it clear there's no way to get something in or out of these functions, they shouldn't return anything, but rather using async/await to wait for a promise to finish, or just call a function "with side effects" but without returning anything.
As an aside, while this is being updated, can we remove "global" from the first sentence? We're not showing them as globals.

@patak-dev setup and teardown APIs have been updated. Check it out

@patak-dev setup and teardown APIs have been updated. Check it out


Street view is not available on Jarbas

What is the problem?
Street view is not available on Jarbas (see the page visited):

When I click the image:

How can this be addressed?
Check if the API key is active and the implemented API calls still work.
Labels
[bug] [configuration]

Many thanks for the report. New API keys created and issue fixed ; )

Interface changed, but still doesn't work:

Signature error fixed too, but now there's no free tier for the Google Street View Static API, and I'm not sure we're willing to pay for that feature:

@cuducos, @turicas and @sergiomario, since there's no free tier, we could opt for an open source project. What about using Open Street Map? The drawback is that there's no street view, but we could have a workaround and just simply show the map centralized on the coordinates with a pin. It would look the mockup below:

The "COMPANY IN MAPS"  link can remain the same. When the user clicks on it, they'll continue going to GoogleMaps, this is nice because they will still have the choice to use the street view functionality, but in a manual manner.
What do you guys think?

The drawback is that there's no street view

Historically this feature was added due to Google Street View. While looking for suspicions, it was a big red light to see, for example, a car rented in a venue with a store front clearly suggesting it's a bakery. I see little value in adding the map and I vote for removing any integration as such (the “Company in Maps” is still useful for user to consult Street View manually). What do you think?
TLDR, I don't see how a map is helpful so I don't see value on that. But I might blind for some ideas I haven't conceived myself. Can you expand on your the purpose of your suggestion?

I agree with the reasons you have stated for the use of the street view functionality, they make total sense. With that, having a simple map indeed does not add any value, if so, just a little.
Given the current state, where the 4 street view tiles are showing errors, maybe it's better to just remove this functionally, leaving just the "Company in Maps" button. WDYT?

maybe it's better to just remove this functionally, leaving just the "Company in Maps" button. WDYT?

IMHO it sounds good : )

Alrighty, I will work on this :)

One thing that OKBR may want to check is Google's non-profit program. It includes a maps key with access to several features.

@chicocvenancio, that's a great idea! I think these two ideas are complementary. Temporarily removing the street view feature until, and if, we get access from Google's non-profit program.


fix: Fix parameter handling for PostgreSQL URLs

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources? N/A
[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation? N/A
[x] Testing: Have you written and run sufficient tests for validating the changes? N/A
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
This PR fixes PostgreSQL support so parameters like sslmode=require are honored and passwords containing special characters can be used.
Fixed

Correctly pass all parsed arguments to ReconnectingPostgresqlDatabase
Decode URL-encoded characters in passwords

Additional Information

Passing all parsed options as kwargs is the approach used in connect() in peewee. Without this fix, URLs without port numbers result in errors and parameters like sslmode=require are silently ignored.

Can confirm, had the problem with special characters (!) in the DB Password, could not connect

Did you test this won't cause any issues with our sqlachlemy codebase?

Both built-in SQLite and PostgreSQL (neon.tech) appear to work fine for me. Since it works end-to-end in my setup, my URL-encoded password as well as the sslmode=require parameter are used by both peewee (pre-alembic migrations) and sqlalchemy.
I triggered the integration tests on a separate branch, and the migration test and most of the Cypress tests pass. The failures appear to be flakey and unrelated.


Remove encryption at rest from unsupported serverless features

Fixes DOC-9777

We might also need to update this page: https://www.cockroachlabs.com/docs/cockroachcloud/serverless-faqs#is-encryption-at-rest-enabled-on-cockroachdb-serverless (waiting on an answer from eng).

I don't think we need to wait further on eng. Can merge once this is approved.

PTAL at the commit I just pushed as as proposal for keeping the info in the page but being more clear. I also found a few other improvements to make nearby (we missed adding some unsupported features around PCI DSS / HIPAA, and we were using an old variant of a Liquid variable).


esp32c3: Add initial support to esp32c3-devkit-rust-1 board

Summary
Add initial support to esp32c3-devkit-rust-1 board
Impact
Users could use the esp32c3-devkit-rust-1 board with NuttX (and eventually run Rust on it over NuttX)
Testing
esp32c3-devkit-rust-1

@acassis do you plan to mainline the rust porting to nuttx?

@acassis do you plan to mainline the rust porting to nuttx?

Hi @xiaoxiang781216, this board was developed by a colleague that is Rust fan and it will be used in the Ferrous Systems training: https://ferrous-systems.com/go/trainings/esp32-c3-devkit-rust-1/ Although its initial purpose was to be used in that training, this is a nice board to be used with NuttX. About the Rust porting we need to find a way to better support "cargo" in our Building System, this is the next step to get Rustix compiled on NuttX.

@acassis do you plan to mainline the rust porting to nuttx?

Hi @xiaoxiang781216, this board was developed by a colleague that is Rust fan and it will be used in the Ferrous Systems training: https://ferrous-systems.com/go/trainings/esp32-c3-devkit-rust-1/ Although its initial purpose was to be used in that training, this is a nice board to be used with NuttX. About the Rust porting we need to find a way to better support "cargo" in our Building System,

How about to leverage CMake?

this is the next step to get Rustix compiled on NuttX.

We are very interesting to support rust on NuttX.

@acassis do you plan to mainline the rust porting to nuttx?

Hi @xiaoxiang781216, this board was developed by a colleague that is Rust fan and it will be used in the Ferrous Systems training: https://ferrous-systems.com/go/trainings/esp32-c3-devkit-rust-1/ Although its initial purpose was to be used in that training, this is a nice board to be used with NuttX. About the Rust porting we need to find a way to better support "cargo" in our Building System,

How about to leverage CMake?

I think it is better to get CMake integrated and stable on NuttX first.

this is the next step to get Rustix compiled on NuttX.

We are very interesting to support rust on NuttX.

I think we can discuss it with @lupyuen and @sunfishcode how to do it. I think we need to create same generic rule in the make build system to run cargo when it enter inside a Rust directory, same way we do it automatically for regular C programs in the apps/ directory.


Update sbt-release to 1.0.12

Updates com.github.gseitz:sbt-release from 1.0.11 to 1.0.12.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

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

labels: semver-patch

Pull Request Test Coverage Report for Build 16

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 95.0%

Totals

Change from base Build 15:
0.4%

Covered Lines:
57

Relevant Lines:
60

💛  - Coveralls


Possibility to get service information

Hi,
In we connect app for Golf GTE (not we connect ID), we can get the "service" information.
Any way to have this information on your plugin ?
Thanks in advance !

You mean the days and kilometers until service?
If your car provides it, it should be already there:
[vehicleHealthInspection] Elements: 1 items
	[maintenanceStatus] (last captured 2022-03-01T07:26:33+00:00)
		Current milage: 10504 km
		Inspection due in: -436 days
		Inspection due in: -19600 km
		Oil service in: -4600 km
		Oil service in: -71 days
[vehicleHealthWarnings] Elements: 1 items
	[warningLights] (last captured 2022-03-01T07:26:33+00:00)
		Current milage: 10504 km
		Warning Lights: []

What you need is: [vehicleHealthInspection] in the capabilities. If it says: [vehicleHealthInspection] Status: MISSING_SERVICE disabling: False your WeConnect Plus may be expired.

any update on this one?

Hi @tillsteinbach !
Sorry for the delay :(
When i check my WeConnect app on iPhone, I can read inspection (in days and km).
But with this plugin, when I try /vehicleHealthInspection/maintenanceStatus/inspectionDue_days or /vehicleHealthInspection/maintenanceStatus/inspectionDue_km, I have "not found" response.
Any idea why ?
Thanks in advance !

Can you check in the WeConnect ID app if it has the maintenance data?

In WeConnect ID app, I can't find the maintenance date :( I think is the response right ?

It looks like this:


fix: add aruba mibs

:tada: This PR is included in version 1.15.4-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Add support for TLS, as per Issue #70

Add TLS support, as per Issue #70

Tested with empty files, results below.
chrroberts@chrroberts--MacBookPro16 pure-fa-openmetrics-exporter % ./out/bin/pure-fa-om-exporter -c blank.crt -k blank.key
2023/08/07 09:19:16 Start Pure FlashArray exporter v1.0.8 on <IP_ADDRESS>:9490
2023/08/07 09:19:16 tls: failed to find any PEM data in certificate input
chrroberts@chrroberts--MacBookPro16 pure-fa-openmetrics-exporter % ./out/bin/pure-fa-om-exporter -c -k
2023/08/07 09:19:49 Both certificate and key must be specified to enable TLS

Tested with valid keys without issue.
chrroberts@chrroberts--MacBookPro16 pure-fa-openmetrics-exporter % ./out/bin/pure-fa-om-exporter -c server.cert -k server.key
2023/08/07 09:27:15 Start Pure FlashArray exporter v1.0.8 on <IP_ADDRESS>:9490

Looks good, I would like to see a little more documentation on how to run in TLS mode in a docker env


Add Cities hexagon icons to spritesheets

What's interesting about the hexagon icons in cities is that the same image is used in an entire age, but colored differently based on the color of the card itself.
Not sure how that would be handled when extracting images, but I thought I'd point it out.  If we can have the colored parts be transparent, then we'd only need 10 icons.

Instead of trying to re-color the icons, I think it will be simplest if we add the 5x10=50 icons to the existing spritesheet. We have extra room in the 11th-15th column of the existing spreadsheet that we can cram them into (rows 2-10 and 13).
The reason for cramming them into the sheet without making it larger is because we are already close to the file size limit for BGA images.


Allow a resource to accept multiple verbs

It could be helpful to allow a resource to accept more than one verb (or config in general), or allow more than one resource with the same uri (which is the map key currently).

I believe you found a bug. You should be able to create multiple resources with same URI. I took a quick look and I can see the problem. It will be a simple fix. Thank you :+1:

In addition to that, I could maybe add a way to set ANY as HTTP method, so we don't need to create two resources for different methods with same response.

Good point, but in that case be careful that ANY should be the last matching method: if POST and ANY are defined for a given resource, the most specific (POST here) should be used, ANY being the « otherwise » case.
Nice suggestion, thanks for you time :+1:

Fix implemented on version v1.0.1. I'll keep it open for now as a reminder about the wildcard method ANY.


$services vs services

Intellisense says to use "services" but no code generation happens.
However use "$services" works.
{
    "$schema": "https://raw.githubusercontent.com/microsoft/devicescript-pico/main/boards/rp2040deviceconfig.schema.json",
    "devName": "pico bricks",
    "productId": "0x3ab4b07e",
    "$description": "Pico Bricks sensor kit with a RP2040 board from Raspberry Pi with a WiFi chip.",
    "archId": "rp2040w",
    "url": "https://www.raspberrypi.com/documentation/microcontrollers/raspberry-pi-pico.html",
    "log": {
        "baud": 115200,
        "pinTX": 0
    },
    "pins": {
        "P1": 1,
        "P11": 11,
        "P13": 13,
        "P14": 14,
        "P15": 15,
        "P16": 16,
        "P17": 17,
        "P18": 18,
        "P19": 19,
        "P2": 2,
        "P21": 21,
        "P22": 22,
        "P26": 26,
        "P27": 27,
        "P28": 28,
        "P3": 3,
        "P6": 6,
        "P8": 8,
        "P9": 9
    },
    "led": {
        "pin": 7,
        "isMono": true
    },
    "noScanI2C": true,
    "i2c": {
        "pinSCL": 5,
        "pinSDA": 4,
        "kHz": 200
    },
    "$services": [
        {
            "service": "buzzer",
            "pin": 20,
            "name": "buzzer"
        },
        {
            "service": "relay",
            "pin": 12,
            "name": "relay"
        },
        {
            "service": "button",
            "pin": 10,
            "name": "button"
        }
    ]
}

{
    "$schema": "https://raw.githubusercontent.com/microsoft/devicescript-pico/main/boards/rp2040deviceconfig.schema.json",
    "devName": "pico bricks",
    "productId": "0x3ab4b07e",
    "$description": "Pico Bricks sensor kit with a RP2040 board from Raspberry Pi with a WiFi chip.",
    "archId": "rp2040w",
    "url": "https://picobricks.com/",
    "log": {
        "baud": 115200,
        "pinTX": 0
    },
    "pins": {
        "P1": 1,
        "P11": 11,
        "P13": 13,
        "P14": 14,
        "P15": 15,
        "P16": 16,
        "P17": 17,
        "P18": 18,
        "P19": 19,
        "P2": 2,
        "P21": 21,
        "P22": 22,
        "P26": 26,
        "P27": 27,
        "P28": 28,
        "P3": 3,
        "P6": 6,
        "P8": 8,
        "P9": 9
    },
    "led": {
        "pin": 7,
        "isMono": true
    },
    "noScanI2C": true,
    "i2c": {
        "pinSCL": 5,
        "pinSDA": 4,
        "kHz": 200
    },
    "services": [
        {
            "service": "buzzer",
            "pin": 20,
            "name": "buzzer"
        },
        {
            "service": "relay",
            "pin": 12,
            "name": "relay"
        },
        {
            "service": "button",
            "pin": 10,
            "name": "button"
        },
        {
            "service": "analog:potentiometer",
            "pin": 26,
            "name": "pot"
        },
        {
            "service": "analog:lightLevel",
            "pin": 27,
            "name": "lightLevel"
        }
    ]
}

See in PR https://github.com/microsoft/devicescript/pull/462, the board definition was added to sampleprj and the 'board' generated is empty.

@mmoskal to refresh the schema for the pico.

added docs; schemas have been updated.