How to use Template Weather Provider with new version ?

Version of home_assistant
Home Assistant 2023.10.1
Version of the custom_component
V2.0.4
Describe the bug
I use a Template Weather Provider to add local messurements of my own weather station (temp, humidity, wind etc) to the data provided from dwd_weather for my location. This has stopped working.
The online documentation has the following example, which is what I have been using so far:

# Example configuration.yaml entry
weather:
  - platform: template
    name: "My Weather Station"
    condition_template: "{{ states('weather.my_region') }}"
    temperature_template: "{{ states('sensor.temperature') | float }}"
    temperature_unit: "°C"
    humidity_template: "{{ states('sensor.humidity') | float }}"
    forecast_daily_template: "{{ state_attr('weather.my_region', 'forecast') }}"

but this seems to work no longer, because the forecast attribute is missing. The documentation may not be up to date.
(I have adjusted to  the new name for the weather station after the update in dwd_weather)
Release notes for HA 2023.9 advise to use the "newly added action part of a template entity", but I am clueless how to to this.
Debug log

Add your logs here.

Hi, the template sensors should have the option to declare actions and triggers. I have however no experience with the weather template integration. Nevertheless here is an example for a normal template sensor, which might be helpful for your tinkering:
template:
- trigger:
    - platform: time
      at: "00:00:01"
    - platform: homeassistant
      event: start
    - platform: event
      event_type: event_template_reloaded
  action:
    - service: weather.get_forecast
      data:
        type: daily
      target:
        entity_id: {INSERT WEATHER ENTITY HERE}
      response_variable: weather_data
  sensor:
    - name: "Max temp"
      unique_id: max_daily_temp
      state: >-
        {{ weather_data.forecast[0].temperature }}
      unit_of_measurement: "°C"
    - name: "Min temp"
      unique_id: min_daily_temp
      state: >-
        {{ weather_data.forecast[0].templow }}
      unit_of_measurement: "°C"

Thanks for the update. If I use a trigger based template this way I now can get a sensor entity with attribute forecast which contains the forecast. But I think I need this in a weather entity to use it for the Template Weather Provider, because it seems to expect this in forecast_daily_template

Some further Info: I was able to create a trigger based sensor that gives me the weather forcast as a sensor like this:
(weather.berlin is a dwd weather entity)
template:
  - trigger:
    - platform: time_pattern
      hours: /1
    - platform: homeassistant
      event: start
    - platform: event
      event_type: event_template_reloaded
    action:
      - service: weather.get_forecast
        data:
          type: daily
        target:
          entity_id: weather.berlin
        response_variable: daily
    sensor:
      - name: "DWD myplace daily"
        unique_id: weather_forecast_myplace_daily
        state: "{{ now().isoformat() }}"
        attributes:
            forecast: "{{ daily.forecast }}"

This should make it possible to construct a new weather entity with a weather template sensor that combines forcast and condition from the dwd integration with messurements from my own weather station (sensor.elv_weather_station_...)  like this:

## weather template
weather:
  - platform: template
    name: "Wetterstation myplace"
    condition_template: "{{ states('weather.berlin') }}"
    temperature_template: "{{ states('sensor.elv_weather_station_out_temp')  }}"
    temperature_unit:  '°C'
    humidity_template: "{{ states('sensor.elv_weather_station_out_humidity')  }}"
    forecast_daily_template: "{{ state_attr('sensor.dwd_myplace_daily', 'forecast') }}"
    pressure_template: "{{ states('sensor.elv_weather_station_abs_baro') }}"
    pressure_unit: "mbar"
    wind_speed_template:  "{{ states('sensor.elv_weather_station_wind_speed') }}"
    wind_speed_unit: "km/h"
    wind_bearing_template: "{{ states('sensor.elv_weather_station_wind_dir') }}"

But no luck so far - I get errors like this in HA log:
Logger: homeassistant.components.template.template_entity
Source: components/template/template_entity.py:220
Integration: Template (documentation, issues)

Error validating template result '[{'datetime': '2023-11-04T00:00:00Z', 'condition': 'rainy', 'wind_bearing': 148.93, 'wind_gusts': 9.26, 'precipitation_probability': 76, 'temperature': 10.0, 'templow': 7.0, 'wind_speed': 5.66, 'precipitation': 2.7}, {'datetime': '2023-11-05T00:00:00Z', 'condition': 'rainy', 'wind_bearing': 197.29, 'wind_gusts': 12.86, 'precipitation_probability': 74, 'temperature': 11.0, 'templow': 8.0, 'wind_speed': 6.69, 'precipitation': 10.6}, {'datetime': '2023-11-06T00:00:00Z', 'condition': 'rainy', 'wind_bearing': 216.71, 'wind_gusts': 9.77, 'precipitation_probability': 61, 'temperature': 12.0, 'templow': 6.0, 'wind_speed': 5.66, 'precipitation': 2.4},

(...)
 renders=4>' for attribute '_forecast_daily' in entity weather.wetterstation_myplace validation message 'Only valid keys in Forecast are allowed, unallowed keys: ({'wind_gusts'}), see Weather documentation https://www.home-assistant.io/integrations/weather/'

if I look up the documentation page that is mentioned in the error above there is a state attribute "wind_gust_speed" but no attribute "wind_gusts". Maybe this can be corrected in the forecast output of the dwd integration ?

Might also be related to #106. I'll check that.

Can you please test with v2.0.13?

perfect ! Template Weather Provider now working again.
Thank you !


Publishing package

Pull request made to Julia, see link https://github.com/JuliaLang/METADATA.jl/pull/2787

We can use package name JuliaFEM.jl if we want to. Question is that do we want?
I would consider FEM.jl also but nothing like FiniteElementAnalysis.jl or other like that. I personally like JuliaFEM.jl.

Ok we got merged. It's JuliaFEM now.


How about considering add jmx support for dubbo

Prometheus may collect a lot of metrics .
For java , we often use jmx_exporter to collect metrics to expose to prometheus.
But now dubbo never provide some jmx bean.
Even in healthEndpoint, jmx_exporter cannot collect java type other than Number Boolean Date and String
ref to https://github.com/prometheus/jmx_exporter/issues/548
I think dubbo may expose own jmxbean to support this.
For example ,the threadpool size or other metrics may help our system more stable.
Any advice is welcome~

I agree U. I need dubbo jmx expose like druid.

agree +1

+1

@AlbumenJ  Any progress?


Is there any plan to port envpool to windows?

Motivation
A lot of my software can only run under windows.
Solution
envpool can be installed under windows.

Yes, this is in our roadmap.


feat: add code signing to vault data integrity check lambda

Summary | Résumé

Added code signing to vault data integrity check lambda

PS: I could not fully test it in Localstack as it does not support AWS Signer and also we do not yet have a proper lambda implementation.

Closing - functionality implemented in #532


Open tag from command line?

With the built-in ctags support, I can type vim -t someTag to find some tag. Is there some way to have something similar for this project? I'm afraid I know very little about vim plugins so perhaps this is impossible.

@Muzer I have a command that does this in my .zshrc. Unfortunately, it's slow, so I dont use it much even for medium projects. Maybe it's possible to cache the results somehow or hack the rc tool to make it faster. Anyway, here it is:
vc() {
  local class=($(rc -S class | fzf-tmux --select-1 --exit-0 --query="$1"))
  local files=($(rc -F "${class}" --definition-only -K | head -n 1))
  local file=($(echo "${files}" | sed 's/:.*//'))
  local line=($(echo "${files}" | sed 's/.*:\([0-9]\+\):[0-9]\+.*/\1/'))
  local offset=($(echo "${files}" | sed 's/.*:\([0-9]\+\):\([0-9]\+\).*/\2/'))
  if [[ ! -z ${file} ]]; then
    ${EDITOR:-vim} ${file} +$line
  fi
}

I type vc in the terminal, hit enter and then fuzzy match the name with fzf, hit enter again and the location of the class is opened in vim. As you can see, it depends on fzf and fzf-tmux. Hope this helps. Please let me know if you come up with a better idea, or if you manage to speed up this.


Unable to upgrade

Hello, I can't upgrade my agent
here what I Got
<EMAIL_ADDRESS>~/tools/newrelic_plugin_agent-1.2.2# pip install newrelic_plugin_agent --upgrade
Downloading/unpacking newrelic-plugin-agent from https://pypi.python.org/packages/source/n/newrelic_plugin_agent/newrelic_plugin_agent-1.2.2.tar.gz#md5=d0c16ffdf491752483608b170af15a9d
  Running setup.py egg_info for package newrelic-plugin-agent
    /usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'entry_points'
      warnings.warn(msg)
    /usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'extras_require'
      warnings.warn(msg)
    /usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'install_requires'
      warnings.warn(msg)
    /usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'tests_require'
      warnings.warn(msg)
    Checking /usr for newrelic_plugin_agent installation manifest
    Checking /usr for newrelic_plugin_agent installation manifest
    Checking /root/.local/lib/python2.6/site-packages for newrelic_plugin_agent installation manifest
    Checking /tmp/pip-build-root/newrelic-plugin-agent for newrelic_plugin_agent installation manifest
    Did not find the installed-files.txt manifest uninstallation issue
    usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
       or: -c --help [cmd1 cmd2 ...]
       or: -c --help-commands
       or: -c cmd --help

    error: invalid command 'egg_info'
    Complete output from command python setup.py egg_info:
    /usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'entry_points'

  warnings.warn(msg)

/usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'extras_require'

  warnings.warn(msg)

/usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'install_requires'

  warnings.warn(msg)

/usr/lib64/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'tests_require'

  warnings.warn(msg)

Checking /usr for newrelic_plugin_agent installation manifest

Checking /usr for newrelic_plugin_agent installation manifest

Checking /root/.local/lib/python2.6/site-packages for newrelic_plugin_agent installation manifest

Checking /tmp/pip-build-root/newrelic-plugin-agent for newrelic_plugin_agent installation manifest

Did not find the installed-files.txt manifest uninstallation issue

usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]

   or: -c --help [cmd1 cmd2 ...]

   or: -c --help-commands

   or: -c cmd --help

error: invalid command 'egg_info'

----------------------------------------
Command python setup.py egg_info failed with error code 1 in /tmp/pip-build-root/newrelic-plugin-agent
Storing complete log in /root/.pip/pip.log

Thanks for your help ...
Regards, Guillaume

@glmrenard
I run into the same issue.I guess you had /usr/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg-info file saved somehow after deleting pip. If you remove it - it will work just fine.


Fixes when given an array as rspec_opt

Rspec raketask's rspec_opt accepts a string or an array of strings.
In Ruby 2.7 a deprecation warning is generated for arrays. This led me to find and error that was undetected because there is no spec for the array case. Moreover I realized that the existing spec for string was erroneously written. This PR fixes both issues

Thanks!


🚀 Feature Request: mf.waitOnExecutionContext, have mf.dispose wait on all waitUntils, or bring back Response#waitUntil()

Describe the solution
We have some old tests we want to migrate to Miniflare 3. However, Response#waitUntil() was removed. The following test fails, because there is no way to wait for waitUntil.
import { Miniflare } from "miniflare";
import { expect, it } from "vitest";

const getMf = () =>
  new Miniflare({
    script: `
  const delay = (n) => new Promise((res) => setTimeout(res, n)) ;
  export default {
    async fetch(req, env, ctx) {
      ctx.waitUntil(delay(2000))
      return new Response("ok", { status: 200 })
    }
  }`,
    modules: true,
    compatibilityDate: "2023-03-30",
  });

it("should wait for waitUntil correctly", async () => {
  const mf = getMf();
  const t1 = Date.now();
  const res = await mf.dispatchFetch("http://test");
  await mf.dispose();
  const t2 = Date.now();
  expect(res.status).toBe(200);
  expect(t2 - t1).toBeGreaterThan(2000);
});

If possible, we'd recommend using the new Vitest integration to test your Workers: https://developers.cloudflare.com/workers/testing/vitest-integration. In particular, it exposes a waitOnExecutionContext() API that sounds like it's what you want here.
Would that work for your use case?

We have by now migrated all our tests to Vitest.


Starborn Suit Voice Modulated Doesn't Apply

It seems that, even if they are wearing the armor, the voice modulation wont apply to lines delivered in settlements-- maybe because the game doesnt realize they are wearing their suit, helmet up, not their casual outfit.

Details
Any of the Starborn endgame suits, any constellation companion.
Game Version
1.7.37
Language
English (EN)
New Game
Yes
Reproduction Steps
Equip starborn suit on any companion. Interact. Hear the voice modulation. Travel to Akila City, let them have ambient dialogue. No helmet audio.

This is an engine-level issue with all spacesuits. Voice modulation will only last until a character's 3D is unloaded, then it reverts to a default modulation. This will require either an official fix, or an SFSE fix.


improve handling of map[string]string

This small PR partially fixes #5 by special casing map[string]interface{}.
It allows defining your config like:
var cli struct {
	Map   map[string]string
}

Still not working :x: :
var cli struct {
	Map   map[string]OtherType
}

PTAL and let me know if you think there's an elegant way to also deal with the second case.

Given this comment, is it safe to assume the second variant will never be supported (without implementing MapperDecoder)?

Sorry for the delay.
You are correct that the second form can't be supported as there's no way to express it reasonably through flags.
I'll merge the current support though, thanks.


On desktop Safari, Address and Postcode form fields should be full width

On wide viewports with Mac Safari 10.1.1, the "This site has been blocked by your ISP" popup's Address and Postcode form fields don't fill the form width, and I believe they should.

Should've just fixed this in https://github.com/fightforthefuture/battleforthenet-widget/commit/c5b3119be2d02667b6acb17ebf175704c9922ca9

@mikemorris You should close this please
Thanks!


[storage-blob 12 preview] Error using BlobServiceClient on production app

Package Name: @azure/storage-blob
Package Version: 12.0.0-preview 1 and 2
Operating system: Ubuntu 18.04
[x] nodejs

version: 12.9.0

[x] browser

name/version: Chrome Versión 76.0.3809.100

[x] typescript

version: 3.5.3

Describe the bug
I am working with react and azure storage blob.
On build the project for production with yarn build and running this with a server, it show the next error:
tslib.es6.js:32 Uncaught TypeError: Object prototype may only be an Object or null: undefined
    at setPrototypeOf (<anonymous>)
    at Object.i (tslib.es6.js:32)
    at AppendBlobClient.js:24
    at Object.<anonymous> (AppendBlobClient.js:23)
    at i ((index):1)
    at Module.127 (main.a4e705eb.chunk.js:1)
    at i ((index):1)
    at Object.98 (main.a4e705eb.chunk.js:1)
    at i ((index):1)
    at a ((index):1)

This error ever show if you use BlobServiceClient() function and with this error you can't see the my react app.
If you run in dev mode with ´yarn start´ this error does not appear.
To Reproduce
Steps to reproduce the behavior:

Create a react APP with typescript (yarn create react-app my-app --typescript)
Add a simple function of azure storage blob in App.tsx

export const getBlobServiceClient = (): BlobServiceClient => {
  const uri = "" // the uri of azure service
  const token = "" // the sas token
  const blobServiceClient = new BlobServiceClient(
    `${uri}?${token}`,
    new AnonymousCredential()
  )
  return blobServiceClient
}

Build for production with yarn build
Run a server: ´serve -s build´
Run a browser and open the server url
(if you run it in dev mode with yarn start this error does not show)

Seems to be something with webpack, we are facing the same error right now. Excluding this module (and all of its dependencies) from webpack fixes the problem... But that's a bad option. Please investigate

@ljgago Will v10 @azure/storage-blob package has this issue?
@HarshaNalluru Do you have time take a look?

@XiaoningLiu the @azure/storage-blob V10 has not this issue.

This may be related the circular references we have between the clients. It looks like the react app tries to load appendBlobClient.js first, while we have a specific loading order for the clients in index.js.

Simplified webpack repro: https://github.com/jeremymeng/webpacktest

also happens ts-node.

@mrsufgi, Thanks for the comment.
We are still fixing the issue with webpack at our end(probably, caused by the circular references between the clients).
From your comment https://github.com/Azure/azure-sdk-for-js/issues/4890#issuecomment-534622008, It looks like you tried modifying the entry points and lost the links to core-http.
If that's not the case or in case you find any new problems other than the webpack issue that is mentioned here, I would encourage you to create a new issue in this repository.

Yeah I figured, I ended up reverting to the current stable api:)

The next update of the storage blob library will have the fix to this issue


updated docs with announcements on perspectives and wdav reporting retirement

Announcement in "update-compliance-monitoring"

Announcement in "update-compliance-perspectives"

Announcement in "update-compliance-wd-av-status"

Looks quite good. May I request the addition of MarkDown indent marker compatibility spacing (add 1 blank space between each "greater-than" character ( > ) and any text following that character) for the [!NOTE] and [!IMPORTANT] blobs in these files?

BTW, @jaimeo, thank you for making the links language agnostic. Good work.

Thank you for checking and pointing it out. Changed.

Thank you for implementing the standard. Good work.

Looking good then? Shall we merge?

I think the application of the terminology is scenario-specific. Internal comms team did explicitly elect to use Microsoft Endpoint Manager. I believe MEM is more cloud-focused.

#sign-off

Regarding the naming of (former) Configuration Manager (and allied technologies): the over-arching umbrella solution is Microsoft Endpoint Manager. Its elements/features include: Microsoft Endpoint Configuration Manager, Microsoft Intune, Desktop Analytics, Autopilot, and the admin center in Azure portal.

Thank you for enlightening me on the subject. I will do my best to keep that in mind, for future needs.


Unclaim the nuget package name

@wizzard0 Hey mate can you rename your nuget package to not use the DT namespace. See : https://github.com/DefinitelyTyped/NugetAutomation/issues/14
Feel free to contact @staxmanade for any help :rose:

hmm, that's unfortunate. See the rest of the discussion at DefinitelyTyped/NugetAutomation#14 please.


Arbitrary delimiter in CSV I/O functions

Automatic detection of delimiter is complicated, and would need a list of acceptable delimiters anyway, so I chose not to do it. Furthermore, the lack of it encourages usage of the correct delimiter, namely the comma.
Multivariate CSV files have been modified accordingly.
Please rebase (😏) at will when you're done checking.

Can you please check that also the bayesmixpy interface works ? :)

Sure , which file should I run?

Any of the notebooks would be fine!

Specifically, I am worried about the use of  np.savetxt(data_file, data, fmt='%1.5f') and we might need to change that to comply with the new standard

You're absolutely right, default delimiter for both np.savetxt and np.savetxt is space. (Why do you do that, numpy? I thought we were friends.) Now it's fixed. Both notebooks run fine.


MAIN B-18753 Move History Log for Service Counselor Approves

B-18753
PR into INT: https://github.com/transcom/mymove/pull/12195
Summary
There are missing details for events logged in Move History where it only shows -.
This PR adds in details to missing fields in Move History when SC approve a PPM.
Changes:

Removed additional history log created for mto_shipments table when SC completes counseling a PPM shipment.
Shows status WAITING ON CUSTOMER in Move History when SC completes counseling a PPM shipment.
Shows status PAYMENT APPROVED in Move History when Closeout SC approves a PPM.

How to test

As a customer -> create a normal move with a PPM shipment.
As a SC -> Find the move and complete counseling by making all the edits necessary and clicking submit button.
Go to Move history tab and you should see rows with Counseling Completed and Status: WAITING ON CUSTOMER. Check the uploaded screenshots below for reference.
As a customer -> Upload PPM documents and fill out the form to submit to Closeout SC for a review.
As a Closeout SC -> Find the move -> Review documents -> Approve all the documents.
Go to Move history tab and you should see a row with Status: PAYMENT APPROVED. Check the uploaded screenshots below for reference.

Screenshots
SC completes counseling:

Closeout SC approves a PPM:

verify rpt:
B18753-12205.verify_rpt.txt
A few diffs.

verify rpt: B18753-12205.verify_rpt.txt A few diffs.

Thank you. I verified the files and it looks like they are showing as diffs on your report because file itself is not the same while my changes are the same.

verify rpt: B18753-12205.verify_rpt.txt A few diffs.

Thank you. I verified the files and it looks like they are showing as diffs on your report because file itself is not the same while my changes are the same.

Ok.  So, diffs can be disregarded.


Support staging

There are development and live stage at the v1 API.
We need to be able to specify the stage as an option or configration.

@marcy-terui my team and I are very interested in the ability to deploy to specific stages. Do you have an ETA on when this might be available?
Also, will this allow for rolling back a stage to a previous version in the case where integration tests fail?


Add japanese translation submodule

FYI @kotet @alphaKAI @simdnyan - with this PR the japanese submodule will be linked to the main tour :)

two-letter ISO 639-1 shortform is used (as for the other languages)

In case someone is interested, it's simply:
git submodule add https://github.com/dlang-tour/japanese public/content/ja

(also documented in the wiki)

@stonemaster I just merge this as I am pretty sure you don't mind - and after all it allows the Japanese translation team to preview their status


Remove default BETA tag on Terra pages [BW-545]

Tested locally.
Before:

After:

This tag is intentionally there. I'll close the PR and delete the branch.


Add geo field to Courses

Add geo property using the Point type in CosmosDB to enable geo searches for courses

See https://docs.microsoft.com/en-us/azure/cosmos-db/sql/sql-query-geospatial-intro for examples of using the Point type for geo data.  This would enable searches for "courses near me"


upload image failed

I have a problem uploading images to the website, it creates this error:
put: /home/pi/allsky/tmp/image-20220210231341.jpg: Errore fatale: Certificate verification: certificate common name doesn't match requested host name ‘ftp.astrofilipisani.it’ (D8:83:D7:51:A5:6B:BD:E7:90:BF:F5:B7:EB:CD:8C:BB:43:65:43:7A)
put of /home/pi/allsky/tmp/image-20220210231341.jpg failed!

@Kilis71 please take a look at the Wiki page on troubleshooting uploads.  If that fixes your Issue, please close it.
Eric

@Kilis71  What steps in the Wiki did you try, and what was in the lftp_commands.txt file afterwards?
The step for fixing the "certificate common name doesn't match requested host name" message should have worked.

I solved it by inserting the string "set ssl: verify-certificate false" I had also made another mistake, I had entered the password of the site encrypted in base 64 instead of in clear text. now everything works, thanks for your interest, I spent a few sleepless nights there before solving :)

@Kilis71 Great!  Glad to hear the Wiki worked.
Would you please close this Issue now that it's been resolved?  Thanks


Naming

These scripts only interact with xtp and not the other modules so far, so PyVOTCA might be a bit of a too generic name.

Do you anticipate that anyone might be interested in interaction with other modules? Then we could keep it generic for future purposes. Otherwise we make this PyXTP or something.

Do you anticipate that anyone might be interested in interaction with other modules? Then we could keep it generic for future purposes. Otherwise we make this PyXTP or something.

It's on the list for a decade (see https://github.com/votca/csg/issues/43) ;-)
PyXTP seem a bit too specific as well.
Maybe having a PyVOTCA.xtp subclass? Which would leave some space to add PyVOTCA.tools and PyVOTCA.csg later.

It's on the list for a decade (see https://github.com/votca/csg/issues/43) ;-)
PyXTP seem a bit too specific as well.
Maybe having a PyVOTCA.xtp subclass? Which would leave some space to add PyVOTCA.tools and PyVOTCA.csg later.

Well, the wrapper.py is actually providing a class called XTP and I am
using it as
From PyVOTCA import xtp
We can rename wrapper.py to xtp.py for clarity.
On Wed, 27 Jan 2021 at 18:01, Christoph Junghans<EMAIL_ADDRESS>wrote:

It's on the list for a decade (see votca/csg#43
https://github.com/votca/csg/issues/43) ;-)
PyXTP seem a bit too specific as well.
Maybe having a PyVOTCA.xtp subclass? Which would leave some space to add
PyVOTCA.tools and PyVOTCA.csg later.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/votca/PyVOTCA/issues/17#issuecomment-768427082, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC326AVSTEYRN5FOIAPDYLTS4BBE3ANCNFSM4WVLHUEA
.

Well, the wrapper.py is actually providing a class called XTP and I am
using it as
From PyVOTCA import xtp
We can rename wrapper.py to xtp.py for clarity.
On Wed, 27 Jan 2021 at 18:01, Christoph Junghans<EMAIL_ADDRESS>wrote:

It's on the list for a decade (see votca/csg#43
https://github.com/votca/csg/issues/43) ;-)
PyXTP seem a bit too specific as well.
Maybe having a PyVOTCA.xtp subclass? Which would leave some space to add
PyVOTCA.tools and PyVOTCA.csg later.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/votca/PyVOTCA/issues/17#issuecomment-768427082, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC326AVSTEYRN5FOIAPDYLTS4BBE3ANCNFSM4WVLHUEA
.

Fixed by #20

Fixed by #20


python312Packages.hcs-utils: fix build

ZHF: https://github.com/NixOS/nixpkgs/issues/352882
Only source on gitlab have test.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@fabaff Done.

@ofborg build python311Packages.hcs-utils python312Packages.hcs-utils

@ofborg build python311Packages.hcs-utils python312Packages.hcs-utils

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359237

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.hcs-utils
python311Packages.hcs-utils.dist
python312Packages.hcs-utils
python312Packages.hcs-utils.dist


Unbalanced dataset

My dataset is 98% positive and 2% negative.
Upsampling and downsampling can ruin the graph.
Any suggestions?

My friend!
I have the same problem.
Have you solved the problem？
Can you give me a suggestion？
Thank you!


Find loops

Some digit spaces don't only have Kaprekar's numbers, but also loops.

Solution Algorithm:
1. find when two subsequent iterations have same number of prototypes/find when source and target have same cardinality
2. look which elements map unto themselves.
        2.a If every element maps unto themself, done.
        2.b Else
                2.b.1 go depth first, create loop consisting of all subsequent mappings of element until you're back at the element itself
                2.b.2 meanwhile scrap every element you encounter from your set.
                2.b.3 iterate over every remaining element of your set until it is empty
                => what you are left with is the last mapping with a set of Kaprekar's numbers and a set of loops

@WilliamMauclet Solving this in new branch TreeBuilder


svscan: add sigterm handling

This replaces PR#44, rebasing from current master and squashing commits. Also dropped the whitespace tidy. I'll do that in a separate PR.

Pulled (and tweaked a few details) in 07806c35818efff8a067f5bbce3fdfbadcb2dc48


TRANSPARENT BACKGROUND

how can I set the bar_progress_backround to have some transparency (alpha)
I want to change this vertical seek bar background

To something like this

If you look closely the background color is have some transparency
Hope you understand what I mean,
Thanks

@Usman-Click have you got the solution for making it transparent ?
@lukelorusso can you let us known ?


feat: function creation timestamp

Changes

:gift: function creation timestamp

It is becoming clear that a timestamp of when a Function successfully completed the creation process will be valuable.  In particular this will help with a few forthcoming PRs currently WIP, I'm separating this into its own PR to solicit feedback such as consequences unanticipated.

/lgtm
/approve


Regression: FSI.EXE is no longer 32-bit

This is a significant regression. The FSI.EXE we now build in the master branch is no longer a prefer-32-bit exe.
> "C:\USERS\DSYME\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\15.0_D5B059C1ROSLYNDEV\EXTENSIONS\MICROSOFT.VISUALFSHARPTOOLS\VISUAL F# TOOLS\<IP_ADDRESS>\fsi.exe"

> sizeof<nativeint>;;
val it : int = 8

Current produce behaviour:
> fsi.exe

> sizeof<nativeint>;;
val it : int = 4

@brettfo Here is the relevant line that was lost in the project file conversion: https://github.com/fsharp/fsharp/blob/master/src/fsharp/fsi/Fsi.fsproj#L17
Can we review that work again please to see if there are any other flags that we lost? thanks

@cartermp asked on Slack about .NET Core and compat for F# Interactive

We don't expect full compat.  There are observable differences - one runs as a netcoreapp2.1 and the other as a net46 - and many things can observe that difference.

For 32-v-64-bit: The F# Interactive in the .NET Core tooling is 64-bit by default (i.e. it's AnuCPU).  That's ok I think.  I personally don't even think it's essential to have a 32-bit F# Interactive in the .NET Core tooling at all but people may want to chime in.  Perhaps we should have both.

For VS integration: Currently the fsi.exe that runs by default in VS (and from the VS command prompt) is the desktop one, 32-bit by default.  We have an F# option in VS Enable 64-bit F# Interactive  which runs fsi.exe when false and fsiAnyCpu.exe when true.  (The bug above means that this option is not being respected - it's always 64-bit!)

Going forward into dev16 - especially when the VS integration is done for .NET Core F# Interactive - you will need to decide

VS command prompt - whether NET Core or .NET Desktop fsi.exe is default when running fsi from the VS dev command prompt.

VS - whether NET Core or .NET Desktop fsi.exe is default when running fsi inside VS, and is there a way to declare this in scripts

Options - whether you support "F# Options" in Visual Studio to select Desktop FSI v. ,NET Core FSI and if so 32-bit/64-bit

Once the VS Integration is done I assume that .NET Core F# Interactive will eventually be the default on both the command prompt and from inside VS.  That wlll sort of be a breaking change.  But people can live with that if there's a way to run the old one.
Note you could consider changing the name of F# Interactive for .NET Core, e.g. fsci or something to get the .NET Core one, that might make some things clearer.

In summary - I think we should address most of this when we do the VS integration for .NET Core scripting.
At that point, it would make sense to just rethink how we really want F# scripting from inside VS to be.  From package references to better visuals to debugging etc. etc.
I'd love to see the community being much more active at making F# data scripting in VS great as well.

@dsyme what sort of things do you have in mind regarding data scripting in VS?

@isaacabraham If I had carte-blanche, I would say "make data scripting with F# in Visual Studio look and feel more like other data-centric environments such as R Studio, Julia or the Python equivalents".
Concretely this would be

package references in scripts

colorize the output of FSI

make the REPL window read-only so people no longer think it's a space to type into.  If they try to type into it show a message saying "Send code to this window from F# scripts using Alt-Enter!". Or else implement intellisense in that window.  One or the other (the former is much cheaper!)

a dedicated space (or set of tabs) for rich visual outputs coming from FSI.EXE (HTML surface area for tables, charts and any other visual data) and a specific standard way to get content to show there.  The way used by most F# tooling is an fsi.AddHtmlPrinter method - if Visual Studio supported this we could make that a standard.

Have a parameters window somewhat like FsEye showing top-level bindings in scripts in a typical VS object-inspector way.  Plus be able to modify these parameters in-situ

Have better interactions for things like load-a-script-until-the-place-where-the-cursor-is.  i.e. make it much faster to get going again restarting a script

Consider in-editing completion of path names

Basically anything that makes the act of cranking out data scripts better and faster.

Regarding the list:

IntelliSense in FSI is completely possible without a terrible amount of work. We'd have to rewrite the VS integration to use the Roslyn InteractiveWorkspace, but that does give us a full workspace where colorization and IntelliSense would simply work once it's plugged into our providers in FSharp.Editor
Completion of path names exists with #r today, are you referring to other contexts?

I'd rather make the window read-only and use it as a chance to instruct people how to send-to-interactive.  Every time a user types into the REPL window  in VS a puppy dies.  (I've always had strong feelings about this - and wanted F# to be document-focused - so just ignore my rants if you're going to keep it a console window :) )

nuget package name and version completion

Completion of path names exists with #r today, are you referring to other contexts?

Yes, I suppose opportunistically completing on @"c:..." or "/" would be examples.  Perhaps there are others. Anything that makes it easier to get the names of data files right.

@dsyme whilst we're on the wish list - something like a playground / lighttable mode would be great, where you could see the results of expressions alongside them.
But yes agree with all of those that you've suggested.

I remember that there used to be some extension from some open source project that managed to get colorization and context help. Not sure what happened with that project or whether it'd be worthwhile researching if we can reuse that here.
My 2p on the read only suggestion, I use the repl a lot and apparently kill a lot of puppies. I find the send to interactive mostly useless, because it doesn't respect existing opens and as a result I can hardly ever use it in larger projects than the most trivial ones

As for read-only REPL, I think we should take a look at IDE of other data focused languages. My experience in MATLAB, RStudio and Spyder all allows both sending script to REPL and type in code in REPL directly. However, REPL in the three IDES I listed all supports intellisense. That gave researcher a choice to explore further after sending majority of script to REPL.

An extension like FsEye is a prerequisite if we ever want to expand use cases of F# in data related field. Researchers in Python, R and MATLAB are all used to work while monitoring the change of data. Sometimes just copy paste intermediate data frame into spreadsheet for presentation and plotting.

FSI in Visual Studio for Mac has colourisation and completion:


Added users in users.json according to issue #1037

Pull Request Type
I Have added JSON file data of users in users.json file it was the easy json issue no. #1037 and Completed Sum.js program from the #948
[x] Solved an issue/task
[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

Yeah I will try to contribute in your web repositories thanks !!


Application should be returned when Bevy runner terminate

What problem does this solve or what need does it fill?
Bevy can be run in headless mode, where you often want to introspect the state of the world (ressource, query, ...) and assert something for test and debugging. Some usefull data are present in Bevy, like time since startup, the whole world state, ...
When an application is constructed and App::run() is called, the application never terminate unless :

The runner is set to "run once".
The application emit an event called AppExit.
The user have setup a custom runner with his own rule.

When the application terminate, App::run() return nothing and you have no way to introspect the final state because the application is now empty due to std::mem::replace.
// impl App
pub fn run(&mut self) {
    #[cfg(feature = "trace")]
    let bevy_app_run_span = info_span!("bevy_app");
    #[cfg(feature = "trace")]
    let _bevy_app_run_guard = bevy_app_run_span.enter();

    let mut app = std::mem::replace(self, App::empty());
    let runner = std::mem::replace(&mut app.runner, Box::new(run_once));
    (runner)(app);
}

// App
pub struct App {
    pub world: World,
    pub runner: Box<dyn Fn(App)>, // Desugar into ---> Box<Dyn Fn(App) -> ()>
    pub schedule: Schedule,
}

What solution would you like?
Since there's a clear owner of the Application (the runner), the runner should be able to return the Application and borrow checker should not complain about that.
We can either :

Replace self with the returned application (should be favored in my opinion, since we are mutating the world when we run the application).
Return the application and let the empty application like that.

What alternative(s) have you considered?
Don't return the Application and let the user with an empty application. If user don't have any background with std::mem::replace, confusion can happen. The user expect the application to be in final state, they don't expect an empty application.
Additional context
/

Sorry, got confused with what you wanted. The runner consumes the App, so it can't be returned from App::run. It isn't possible to return any value from the runner without making the entire App generic over the return type of the runner. This would be an ergonomics loss. You could do the assertions and printings inside the runner after you are done running all schedules. Or you could re-implement App::run yourself to not use the runner stored inside it and return the App afterwards.

I end up doing this :

I wrap my Application with my own "Engine" struct with a "on_exit" fn pointer.
Since I'm using a custom runner, when I handle AppExit and break the main loop, before I return I call my fn pointer with an owned access to the App.

Work perfectly, but it's a bit weird to have to do all this dance. Anyway, thanks for the information.

Related to #2896 and #1057.


Field dropdown not rendering correctly

When editing a page with a Shopify Product field selector in it, the dropdown menu for the field does not render correctly.  It appears more as a multi-select field that is open, with an extraneous arrow icon in the bar on the right (please see attached).

Hello @joegra ,
which OS + browser (-version) are you using to reproduce this behaviour? Does this happen with usual craft multiselect fields as well? Because then I think this might be due to an issue from craft itself.
Greetings.

Hi @nmaier95 ,
I've been working in Chrome on Windows 10.  I tried adding a standard dropdown field, which renders correctly.  Looking at the rendered field, it looks like the 'multiple' attribute is being added to the select tag -- is this intentional?  If so, would make sense why it's rendering this way... although the stray arrow seems a bit odd (perhaps a bit of stray css from the standard dropdown styling?)...

Fix has been deployed with version 1.0.3

@nmaier95 I'm using version 1.0.3 of the plugin and the select field is still broken.

Hello @chadspencer,
actually it should be possible to select multiple products. Unfortunately I do not have an active shopify-account at the moment to retest it myself. May you confirm it still not working for you to select multiple products with version 1.0.3? If so, please let me know the browser + version you are using.
Thanks in advance!

Hmm, interesting. I'm using the latest version of both Chrome and Safari on a Mac. The field itself is a multi select field but when I save only the last option I've selected is saved. I assumed you could only choose one product at a time. I've accounted for this by have the selection in a matrix field.

Should be resolved by PR #9


[6.x] Fix testing with unencrypted cookies

This PR provide a way to specify cookies will be encrypted before sending with the request. It works well with unencrypted cookies.
$this->withCookie('bar', 'qux')
     ->withEncryptableCookie('foo', 'bar')
     ->get('/');

$this->withCookies($cookies) // cookies will not be encrypted
     ->withEncryptableCookies($encryptableCookies) // cookies will be encrypted
     ->get('/');

Fixes #31282

This feels like a pretty big breaking change to make withCookies no longer encrypted? Why not make the method withUnencryptedCookie so we don't have to have that breaking change?

@taylorotwell It's a great idea.


[FLINK-18545][table-api-java] Add a api for JobName set, executeSql(S…

…tring statement, String jobName)
What is the purpose of the change
This pull request add a api that user can set a job name for flink job. I think this feature really matters for some users.
Brief change log

Use can set a job name after a SQL parameter
The web ui will display the Job Name.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (no)
The runtime per-record code paths (performance sensitive): ( no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (not documented)

Hi @leslieyuan, thanks for the contribution. However, the community decided to shift the "backpressure" from pull requests to Jira, by requiring contributors to get consensus (indicated by being assigned to the ticket) before opening a pull request. See more https://flink.apache.org/contributing/contribute-code.html
Besides, there is some concerns about your approach raised in the JIRA discussion.

@wuchong ok, thanks for your remind. I will follwer the guide next time.


[BUG] Settings Sub-Menus Not Displaying Correctly in Safari or Firefox

Currently, if we go to the 'Settings' (i.e., 'cog') menu, and try to use the 'Save As', 'Export' or 'CSS Preset' sub-menus, strange UI glitches happen on both Safari and Firefox.
SAFARI
The sub-menus display for about 0.25 second, and then they appear to get 'clipped' by the main menu, looking like this:

FIREFOX
The 'Save As' menu seems to display OK, but the 'Export' and 'CSS Preset' menus appear "split", with commands shown in 2 different locations in the viewport:

I confirm I can reproduce the described behavior.
thank you for reporting

This bug has now been fixed by #207
you may test it on this preview URL or on development build
It has been tested on chrome, firefox and safari
it should be available on livecodes.io with the next release.
@iocouto thank you for reporting and please let me know if you have any comments


Refactor CUDA Container file

Changes
Which issue is resolved by this Pull Request:
Resolves #899
Resolves #932
Description of your changes:
Modify the Containerfile for NVIDIA CUDA to:

use multi-stage build with CUDA runtime image for the final stage
update to CUDA 12.4.1
install the Python packages in a virtualenv that is copied in the final container
mimic the layout and behavior of ubi9/python-311 container
make the final container rootless
install flash-attn and bitesandbytes

Propose a shell alias that should simplify the user experience when using the container image, avoiding using long podman run commands.
Modify the containerization documentation to explain this and provide steps for the user.
Update the cuda target in the Makefile to reflect the changes above.
The changeset is co-authored by Fabien Dupont and is built on top of previous work by Charlie Doern and Fabien Dupont.

@tiran FYI, I also needed this package nvidia-driver-cuda-libs ... not sure if that's accounted for here.

@stefwalter In the final image or on the host system?

@stefwalter In the final image or on the host system?

In the image. Without nvidia-driver-cuda-libs
[root@8a706bc26838 instructlab]# podman3.11
bash: podman3.11: command not found
[root@8a706bc26838 instructlab]# python3.11
Python 3.11.5 (main, Sep  7 2023, 00:00:00) [GCC 11.4.1 20230605 (Red Hat 11.4.1-2)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
torc>>> torch.cuda.device_count()
1
>>> torch.cuda.is_available()
False

With the library installed then is_available() returns True.

@tiran does this still only have the capability to only run 1 cmd per container run? if so, I would really vote to add back the old workflow of exec'ing into a running ctr with ilab installed.
I may have lost context here so feel free to correct me :)

Fabien is taking care of CUDA container. Closing this stale PR.


Testing higher-order Observables

I was implementing the window() operator and I realized I've encountered a situation that wasn't tested before. That's higher-order Observables and in particular operators that emit Observables where I need to test that these Observables emit correct items themselves.
This PR lets me write tests for window() operator like the following:
$xs = $this->createHotObservable([
    onNext(225, 1),
    onNext(250, 2),
    onNext(300, 3),
    ...
]);

$results = $this->scheduler->startWithCreate(function() use ($xs, $window) {
    return $xs->window($window);
});

$window = $this->createHotObservable([
    onNext(325, 1),
   ...
]);

$this->assertMessages([
    onNext(200, $this->createColdObservable([
        onNext(25, 1),
        onNext(50, 2),
        onNext(100, 3),
        onCompleted(125),
    ])),
    ...

https://github.com/martinsik/RxPHP/blob/window-operator/test/Rx/Functional/Operator/WindowTest.php
The most important part is this:
onNext(200, $this->createColdObservable([
    onNext(25, 1),
    onNext(50, 2),
    onNext(100, 3),

There's a new OnNextObservableNotification that automatically subscribes to an Observable and all items are recorded with timestamps relative to its parent. Then these automatic subscriptions are ignored by the ColdObservable.
I've actually spent quite some time scratching my head around how to implement this in the most comfortable and easy to use way. Ideally if I didn't need to think about it at all and use Observables just like any other values.
If I didn't miss anything this should allow fluent porting from RxJS 5 marble tests (eg. window-spec.ts where they treat Observables like values. For example this should work in RxPHP as well:
const expected =     'x------------y------------z------------|    ';
const x = cold(      '---a---b---c-|                              ');
const y = cold(                   '--d---e---f--|                 ');
const z = cold(                                '-g---h---i---|    ');
const expectedValues = { x: x, y: y, z: z };

Using this with ReactiveX/RxPHP#133 shouldn't be any problem.
Also, I didn't need to modify any existing tests including those that use higher-order Observables as input such as MergeAllTest.php.

Coverage increased (+0.1%) to 95.992% when pulling 0a0a691a5e88cdf40ada2d18aaf7fb621588c6d2 on martinsik:testing-higher-order-observables into 84bfbd05e79d924b3d2597eaeef6156475e2a514 on ReactiveX:master.

As a proof of concept I cherry picked commits from #133 and my window() operator and made marble tests for window() operator just to see whether it really works the way I think it should.
https://github.com/martinsik/RxPHP/blob/marble-tests-window-operator/test/Rx/Functional/Operator/WindowTest.php
I had to make a few small changes to FunctionalTestCase class in the way it handles marbles and I also added parsing subscriptions. I'll make appropriate comments into #133.
For example this test is based on window-spec.ts and is passing:
/**
 * @test
 */
public function should_emit_windows_that_close_and_reopen()
{
    $source = $this->createHot( '---a---b---c---d---e---f---g---h---i---|');
    $sourceSubs =               '^                                      !';
    $window = $this->createHot( '-------------w------------w------------|');
    $windowSub =                '^                                      !';
    $expected =                 'x------------y------------z------------|';
    $x      = $this->createCold('---a---b---c-|                          ');
    $y      = $this->createCold(             '--d---e---f--|             ');
    $z      = $this->createCold(                          '-g---h---i---|');
    $expectedValues = [ 'x' => $x, 'y' => $y, 'z' => $z ];

    $results = $this->scheduler->startWithCreate(function() use ($source, $window) {
        return $source->window($window);
    });

    $expectedMessages = $this->convertMarblesToMessages($expected, $expectedValues, null, TestScheduler::SUBSCRIBED);
    $this->assertMessages($expectedMessages, $results->getMessages());

    $this->assertSubscriptions($sourceSubs, $source->getSubscriptions(), TestScheduler::SUBSCRIBED);
    $this->assertSubscriptions($windowSub, $window->getSubscriptions(), TestScheduler::SUBSCRIBED);
}


The default terminal setting for a new pty on linux(unix98) has +ONLCR, on containerd-shim we create a net pty, resulting in \n writes by a container process to be converted to \r\n for the output.
Should we make a PR like https://github.com/opencontainers/runc/commit/eea28f480db435dbef4a275de9776b9934818b8c?

Reopening this, because the version of containerd that's used has not been bumped yet;
https://github.com/docker/docker/blob/36ed7d58bb19e46445c81b6a00a7b75a6280e654/hack/dockerfile/binaries-commits#L5

@mlaventure can containerd be bumped, or should that go in sync with RunC?

containerd alone should be enough, the shim is the one creating the console.
runC master isn't compatible with containerd at the moment, so it would prove  problematic to sync them.

opened https://github.com/docker/docker/pull/30226 to bump containerd version

Thinking about this more, I think we should probably revert that change from containerd.
The issue is actually more complex than I first thought:

The container was created with a tty via -t/--tty, so a new console is created for it and put into raw mode
The content of the above console is sent via a pipe as is to dockerd which itself just transfers it to the docker client

Everything works fine if the docker client is run from within a terminal
If the docker client is piped into another program, it doesn't enable raw mode (which is the correct behavior), but the data it received is already "raw" hence the behavior you are seeing.

Note that the logs created by the daemon will also record the output of a raw terminal (which is the expected behavior AFAIC).
So really the solution for the client side would be to have it filter all the terminal escape characters when it is receiving a terminal output but is not outputing to one.
However, I'm not sure it is worth the effort.

/cc @crosbymichael maybe you have a different POV on this.

Also see the discussion on https://github.com/docker/docker/issues/8513#issuecomment-216191236. Is -t needed in this case? i.e., if you want to pipe the output? I'm not sure either if the fix is correct, given that it's standard behavior of a pty

@mlaventure If the receiver is not a terminal, then it should not use -t to create container at all, I doubt this is a real issue now, as long as we have the precondition that process output from a raw terminal would need a raw terminal on the client side to have the right output view.
The case in this issue:
$ docker run -ti --rm ubuntu echo hello | cat -v
hello^M

I think it's invalid because the cat is out of container. If it's in container, everything works right.
qhuang@ubuntu-25:~/tools/runc$ docker run -ti --rm ubuntu bash
root@1b86097ad770:/# echo hello | cat -v
hello

or:
qhuang@ubuntu-25:~/tools/runc$ docker run -ti --rm ubuntu bash -c 'echo hello | cat -v'
hello

If you want to print the output out of docker client (some terminal that hasn't been setup to raw mode), you just shouldn't use -t:
qhuang@ubuntu-25:~/tools/runc$ docker run --rm ubuntu echo hello | cat -v
hello

Which also works well.
All of these also apply to docker exec.


Rabbimq: Firehose mentrics is not picking the value

Please find the below mentioned firehose mentrics is not picking the value in our environment, we need this to be monitored in prometheus. please suggest any methods to get this issue closed.
firehose_value_metric_p_rabbitmq_num_cpus
firehose_value_metric_p_rabbitmq_memory_stats_num_frees
firehose_value_metric_p_rabbitmq_memory_stats_num_mallocs
firehose_value_metric_p_rabbitmq_memory_stats_last_gc_pause_time_ns
firehose_value_metric_p_rabbitmq_memory_stats_num_bytes_allocated_heap
firehose_value_metric_p_rabbitmq_memory_stats_num_bytes_allocated_stack
firehose_value_metric_p_rabbitmq_memory_stats_num_bytes_allocated
firehose_value_metric_p_rabbitmq_num_go_routines

Closed due to inactivity; Please feel free to re-open if issue still persists


[Rendering] Add IBL back

Background
Now that we've got some more texture bandwidth to play with, let's add some sweet looking IBLs.
TODO

[x] Add back fragment shader code
[x] Wire up descriptors
[x] Load static IBL assets

Further reading

https://github.com/KhronosGroup/3DC-Certification/tree/main/documents

Current update: Loading cubemaps is annoying.

Bad:

Good (but technically wrong):


⚠ Bofrost.at has degraded performance

In 7987fd6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1735 ms

Resolved: Bofrost.at performance has improved in 34d6a14 after 1 hour, 18 minutes.


Linux Support

It's not clear in the documentation. But this does not support linux right?

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

ID: ff3ca71d-bc0f-f021-7eda-ed522edfd51e
Version Independent ID: 88d3f691-7358-e1ef-9763-c191d4f42e1a
Content: Network Performance Monitor solution in Azure
Content Source: articles/azure-monitor/insights/network-performance-monitor.md
Service: log-analytics
GitHub Login: @abshamsft
Microsoft Alias: abshamsft

Closing this for now since the initial question has been answered but reaching out to @vinynigam offline to share additional details on preview status.

Over a year later and the document hasn't been updated, but Linux is supported now (as far as I can tell, as the documentation is old).


[CLI] Incorrectly-set AZCOPY env variable causes confusing errors

If the AZCOPY environment variable is set to a directory containing the AzCopy executable instead of the executable itself, then the CLI produces the error:
ERROR:cli:command failed: 13 Access is denied None 5 None

This is confusing and not helpful. I propose that if the AZCOPY variable is set to a directory, then we look in that directory for the executable.
AB#156895

https://github.com/microsoft/onefuzz/pull/3344


Fix router and pug

Removes loginRouter because we don't need it
Fixed paths in lots of places :)
Pages are now properly linked to css and js
Added some basic css. Form looks like this:

I love you?


proof of concept for renaming proposal (#273)

This is a little proof of concept for what I've proposed in #273

rename invokeUni() to call()
rename then() to chain()
add nullary-function overloads for invoke() and call()

Superseded by the work in #287


Add E.M.E.F Jardim Monte Belo

@jaocs50 I have to close this request without merging, because you requested to add a non-existent domain to this repository: ;; connection timed out; no servers could be reached Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Vertical stacked terminals

Great extension!
It would be cool if the open terminals could be opened in a stacked fashion, maybe setting up a parameter in the json,

FWIW If you move your terminal pane from the bottom to the right, you get vertical panes. I have an ultrawide monitor, so that was a better use of space for me than having the panel at the bottom.

@DaveSanders thanks, I knew that, and currently I'm doing it manually; what I'd like to happen is the terminals to be automatically stacked vertically

Seconded. The default VSCode behaviour is clunky and unhelpful for those of us (the majority!) whose screens are wider than they are tall. However, apparently the VSCode devs all love having their terminals at the bottom, because there's no "default terminal location" setting incoming as far as I can see.
So it would really be helpful if restore-terminals-vscode could do this automatically.


Using mdoc:silent more liberally throughout docs

This PR does a quick once over all our docs using mdoc to see if there are easy clean up wins by using mdoc:silent.
This goal of this PR is to reduce unhelpful mdoc output.
So only minor modifications are being made to serve that goal.
There's certainly more work to do here, this is just a first small attempt to clean up low hanging fruit.

[x] docs/docs/auth.md
[x] docs/docs/client.md
[x] docs/docs/cors.md **
[x] docs/docs/csrf.md **
[x] docs/docs/deployment.md
[x] docs/docs/dsl.md **
[x] docs/docs/entity.md
[x] docs/docs/error-handling.md
[x] docs/docs/gzip.md
[x] docs/docs/hsts.md
[x] docs/docs/integrations.md
[x] docs/docs/json.md
[x] docs/docs/methods.md
[x] docs/docs/middleware.md
[x] docs/docs/quickstart.md
[x] docs/docs/service.md
[x] docs/docs/static.md
[x] docs/docs/streaming.md
[x] docs/docs/testing.md
[x] docs/docs/upgrading.md
[x] docs/docs/uri.md

** still lots of mdoc output we could perhaps trim or better direct attention to the important parts

+1 But Anton is working on a complementary PR, not sure if we should wait to see how they interact before merging

As discussed on discord, I think we should not wait on Anton's work around mdoc-effect.
This PR fixes a few other things unrelated to silencing output from IO values:

Fix CIRCE_VERSION ref in streaming.md
Remove old ContextShift mention in dsl.md

As well as reducing the output on non-IO values where I thought it made sense.
I'd like to see this PR evaluated on it's own, and then later we can consider how mdoc-effect may improve things further.


Cluster can not explose markers when markers are too near each other

I also get an error when I press the Cluster.
https://github.com/JiriHoffmann/react-native-clusterer/assets/28485486/b4ccc54a-8c43-49a0-915b-75fa86447bc6
The example geojson;
[       {         "type": "Feature",         "properties": {           "id": 3560,           "lat_y": 38.257204,           "long_x": -121.3739         },         "geometry": {           "type": "Point",           "coordinates": [             -121.3739,             38.257204           ]         }       },       {         "type": "Feature",         "properties": {           "id": 1949,           "lat_y": 38.257204,           "long_x": -121.373203         },         "geometry": {           "type": "Point",           "coordinates": [             -121.373203,             38.257204           ]         }       },     ]
radius of Clusterer is 18
"react-native": "0.72.4",
"react-native-clusterer": "^1.3.0",
"react-native-maps": "^1.8.0",
Can you please help? @JiriHoffmann

I am unable to reproduce the error with the example points you provided. However, if you have multiple points with the exact same coordinate (in this case both have 38.257204 latitude), the expansion Region will have a delta of 0 resulting in react-native-maps not animating the zoom and just centering the cluster. I would suggest replacing the latitudeDelta with a small value such as 0.001 and the camera will zoom in during the animation. You can adjust at what zoom all clusters turn into points with the minZoom options property.

Hi, @JiriHoffmann
Thank you for the answer!
I changed the initialRegion's latitudeDelta to 0.001 and played with minZoom but It did not work!
Is there anything else that can affect this problem?

In this case, you would use maxZoom, because you are zooming in and thus the zoom value is higher. There was a bug with maxZoom, but it should be fixed in v2.0.0. Let me know if that resolves the issue.


Added Huddle Landing Page

Description
Huddle Landing Page Added. It is just a concept based landing page from which anyone can take his inspiration
Fixes:  #722

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@arpit456jain Please Review this Landing Page PR

@Abh1shekSingh fix this

@DEEPIKA-SUK  please please, don't see responsiveness using console log

Bro console always give error in responsiveness. Always check by moving the actual browser


tear down my world

Hello,
Thank you for your library.
I'm starting to use it, and I have this use case where the given clause builds something, which needs to be destroyed.
I initialy thought I'd implement Drop on MyWorld, but the function I need to call in there is async. And I can't get myself a runtime, so I'd like to know if you have any suggestion.
Thank you

Investigating the question a bit further, I see there are hooks, @after and @before, which could be used for that purpose, but they don't seem to be implemented.

v0.9.0 has this now, but is largely undocumented.
You can see an example in the examples repo.


Camera selector overflows on small display sizes

What happens?
The dropdown for camera selection falls outside the bounds of the view when the height is not large enough to contain all options. Because ".video-container" has overflow disabled, the rest of the options are hidden
What should happen?
The dropdown should expand outside the bounds of the container, or the dropdown should scroll if it is too long.

Fixed in v1.2.8. It now goes into a more compact mode when the container is less than 400px.
This means that the camera list should scroll before it is obscured by the clipping required to force the video preview to a aspect ratio.


Add missing OpenMP dependency for non-monolith tests

Non-monolithic build fails using default OSX compiler. While this is clearly a bug on our part, I like to blame the accessory manufacturer (the one selling monitor stands for 1k USD) for not shipping OpenMP ;)

LGTM.


In how to use fix capital S in Scrollama

In your How to use readme.
const scroller = Scrollama();
Using capitcal S for Scrollama gives me an error saying Scrollama not found.

good catch - it is scrollama();, just updated readme, thanks!


Add SBOM using CycloneDX

We should add an SBOM to the client module and the server module so that we can better document what versions of dependencies goes into each release and the artifacts that are built.
https://github.com/CycloneDX/cyclonedx-gradle-plugin

I might come back to this in the future. We can use the changes in 4bbea3912bfa31ff519119aee202cc93c3312f97 if we want, but it's not really useful until we have CI/CD upload the bom.json


Remove improper handling for the refresh command

Currently, typing help refresh does not work as expected. These lines of code improperly intercept the keyword refresh and alter the inputted command in undesirable ways for all other commands as well such that any command of the form command refresh will attempt to run the refresh command instead.
Currently:
> help refresh

help cannot be refreshed.

> genie refresh

genie cannot be refreshed.

With this change:
> help refresh

refresh all | [status | effects] | [gear | equip | outfit] | inv | camp | storage | [familiar | terarrium] | stickers | quests | shop - resynchronize with KoL.

> refresh genie

genie cannot be refreshed.

> genie refresh

(no output)

Presumably this meant you could do status refresh instead of refresh status.
I agree that is silly and should go away. Let's merge this. Can you add a regression test please?


Add UTF-8 encode step for Py3 compat

Fixes https://github.com/dropbox/pygerduty/issues/34

Really sorry for the delay here! Thanks a lot for the fix.


getting-started:: General improvements for new users

getting-started:: Add information on token scopes for new user
getting-started:: Add information to illustrate the first update process
getting-started:: Add information on Targets

Docs for e3d58699163c65611e3354cd8f1b4b2a55fd3b40 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/784/docs/artifacts/html/index.html

Docs for 1032c95788f994f9bd2ea2d80fea4825cab97cda are browesable at: https://ci.foundries.io/projects/fio-docs/builds/785/docs/artifacts/html/index.html

Docs for c22e2aa177397524ead7795b74cf2a37c64a3dc9 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/786/docs/artifacts/html/index.html

Docs for 0b67a5db70066b44a38b4e47307cdfd73a84b7ab are browesable at: https://ci.foundries.io/projects/fio-docs/builds/792/docs/artifacts/html/index.html


Indexing not implemented on keywordQuery["EnableMultiGeoSearch"]

keywordQuery["EnableMultiGeoSearch"] = true; this line errors out saying KeywordQuery cannot be indexed. This has to be changed to keywordQuery.Properties["EnableMultiGeoSearch"] = true;

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

ID: 42ae5faa-8153-2236-7df4-a648388c5952
Version Independent ID: 9c9a95de-76d6-1581-0c01-7d8a653acfa1
Content: Configure search for Microsoft 365 Multi-Geo - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/configure-search-for-multi-geo.md
Service: o365-solutions
GitHub Login: @tklarsen
Microsoft Alias: tlarsen

@himasusan90 Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5219
Thanks
Sri

closed


Rework caching layers in ODSP driver

Follow up to https://github.com/microsoft/FluidFramework/pull/4872
Due to evicting blobs from cache, we force summarizer to read most of the blobs from storage without hitting driver cache
As result, SPO starts to throttle requests and app, i.e. it results in self-made DDOS attack.
Reworking cache layer and disabling cache eviction for now.

Ping

Ping


Accessibility: frameborder="0" with vimeo

Hi.
An accessibility check of pages that use react-player and vimeo-background videos gives an accessibility error, "1.3.1 HTML is used to format content". This is caused by the resulting vimeo iframe containing a frameborder="0" attribute.
I'm trying to understand where the frameborder attribute is being added so that I can eliminate it. Is it being added by react-player? If it is can you tell me where in the code this happens? Thank you!
Here is how I'm using the react-player component:
<ReactPlayer
  url='https://vimeo.com/235408320'
  config={{
    vimeo: {
      playerOptions: {
        background: true
      }
    }
  }}
/>

The resulting iframe:
<iframe
  src="https://player.vimeo.com/video/235408320?title=0&byline=0&portrait=0&autopause=0&loop=0&background=1&app_id=122963"
  title="Untitled"
  allow="autoplay; fullscreen" allowfullscreen=""
  data-ready="true"
  style="width: 100%; height: 100%;"
  width="640"
  height="360"
  frameborder="0">
</iframe>

Unfortunately Vimeo uses oembed (called here) to build the iframe that gets rendered. There's not much that can be done, apart from perhaps manually removing the attribute from the iframe after it renders?


Add TabularEditor to winget

It would be convenient if TabularEditor 2.x could be added to winget Windows Package Manager Community Repository
, so it can be installed and updated with a single command.
There will have to made a simple manifest file representing this project. The manifest can be generated using the wingetcreate tool. Then the manifest should be deployed in a pull request over at the winget community repository.
This entire process is documented in the Submitting a package section in the winget-pkgs project.

If it would be appreciated, I could give it a shot and create the manifest?

Would appreciate this feature as well!


fix(batcher): send correct responses to each client

Up to now, the batcher responded with the most recent processed batch merkle root to all the connected clients. This was not a correct behaviour because clients should only receive responses from batches where their verification data was included.
To test it:

start anvil with make anvil_start_with_block_time so that a new block is submitted every 3 seconds.
start aggregator and operator.
start batcher
send a burst of 15 proofs with one of make batcher_send_groth16_burst, make batcher_send_plonk_bls12_381_burst, make batcher_send_plonk_bn254_burst or make batcher_send_sp1_burst. You can try this with one or more terminals at the same time. For every message sent by the client, there should also be one response. The responses will be logged as the merkle root of the batch the proof was included in and the hash of the proof. Once all the responses are received, the client will close the connection. If you find that some connection hangs and doesn't close, it may be that the batch was left with only 1 proof. If this happens, try sending an individual proof from another terminal using make batcher_send_plonk_bn254_task. The batch should be finalized and a response will arrive for both clients, closing the connection

NOTE: For the moment the responses are sent once the batch is processed by the batcher. In a future PR this should be handled in such a way so that it is responded once the full flow on aligned has been done (proofs confirmed in Ethereum)

Logic to handle batches should be on is_batch_ready, not in finalize


add stable tag

Looks like everything is working great with retry, why not add a 0.1.0 or 1.0.0 tag?

:+1:

+1 currently can't use this package cuz of that :(

I made a fork with a tag - https://packagist.org/packages/schmunk42/retry
Same namespace, just a different package name.

:+1:

:+1:  I would say it's stable ;-) One of my favorite libs. It's so tiny :heart:

@igorw, could you consider this issue?
I also think this package requires a stable tag :-).


Race condition? VASTClient.getVASTAd.validateAd

FlashTester.js has a probable race condition.
When I run my site in Chrome, about 40% of the time I receive this:
AD ERROR: VAST Error: on VASTClient.getVASTAd.validateAd, could not find MediaFile that is supported by this video player VASTError Array[1]

However, if I step through the constructor of FlashTester.js, the SWF loads successfully 100% of the time.
Here are the actual results of a recent test:
no step through

1: works
2: fails
3: works
4: fails
5: works
6: works
7: fails
8: works
9: fails
10: works

step through

1: works
2: works
3: works
4: works
5: works
6: works
7: works
8: works
9: works
10: works

How are you testing if the FlashTester has or not a race condition?
Is your video auto playing?

Hey!
Yes, it is autoplaying.
Race condition symptoms:

Brittle pass//works sometimes doesn't work other times
Works consistently when I step through the code, indicating that time is a factor

Reading through the code, it looks like:

the default is to false at creation, and then
asynchronously set to true (via a callback and a number of functions wrapped in timeouts).

The async nature of this makes it tricky, but I'm guessing this requires some sort of promise implementation.

Why the flashtester?
Because browsers are deprecating flash (and some big security issues with old versions of flash), Firefox validates the flash player version and if is old for security reason he blocks it by default. So sadly all swfobject validations to check if the user has flash player will still give false positive (because yes the user has flashplayer, and yes the minimum flash player version necessary for the player).
Why is async
So to test if is supported, the test will load, VPAIDFlash (only once for all the videoplayers in the page) and that flash will try to communicate with the JS handler (this is done using ExternalInterface AS3). If this communication is successful. The we assume that flash is supported.

I see. Yes, flash is on the out and outs 👎
It would also be quite tricky to rewrite this method with an asynchronous promise or callback implementation as it has many downstream dependencies that would also have to be updated.
That said, it doesn't feel particularly sound design to have it only fail in a very very edge cases (Firefox, bad flash version, autoplay, race condition).
What if we were to simply require a higher version of flash if the user has Firefox installed??

Hi @Fetz I am having a similar problem and what I am trying to do is hook into the asyn and find where the communication is successful / unsuccessful.
So far when the communication is successful, the _handshake function gets called and I can see a value, so thats great.
The problem however is I don't see any feedback when the communication has failed, most likely because flash is disabled / not installed. So is there a hook for this? A callback that happens when communication failed?


README should include instructions on use and a screenshot or gif

The README should include instructions on use and a screenshot or gif


Map Page

Create a map page where users can see all the reported incidents at one place.
Also provide filtering by date and category.

Merged by commit #beb280837dd9ed226e8ec275b51f6d0c44dd751a


DOC: Better docs for jnp.fft.hfft and jnp.fft.ihfft

Part of #21461

Looks good - thanks! Can you squash the commits?

Thanks! Squashed into single commit


Add Accordion and AccordionGroup components

This PR adds two new components:

Accordion: a collapsible content container, operated via a button
Accordion Group: a wrapper container that aggregates and labels some number of accordions, passed as children

Accordion supports these props:

label: populates the label text in the button used to open and close an accordion
children: generic slot, via which accordion content is populated

Accordion Group supports these props:

title: sets a text label displayed above the accordion group
titleElement: sets the type of heading used for the title (h1 to h6)

If no titleElement is provided, the title will render in a bolded <span>.
Note: These components are based on RAC Disclosure and DisclosureGroup, introduced in RAC v1.4.1. These components are currently considered 'alpha', and some refactoring may be required with subsequent RAC releases.

Just flagging that #500 is blocking to releasing these components, as they rely on features introduced in RAC 1.4.x.

Holding on merging until #500 is resolved. I'll revert changes in b219152 and 31cab58 before merging, so this PR isn't touching package.json or package-lock.json.


Wording of Jedis description.

I haven't used Jedis but it does look quite good.  However I did want to point out one small thing about your description.  "Blazingly" isn't really an adjective one would associate with being small.
From Dictionary.com

blaz·ing   [bley-zing]
adjective

burning brightly and with great heat, force, etc.
of tremendous intensity or fervor: a performance of blazing ferocity.

I might suggest "very small" or even "exceedingly small" instead.
That being said it is your project, I just thought I would pass this on.
All the best,
Jock

@jockm thanks for the feedback I believe "blazing small" can be used as a compound from to say that something is "really small" the same way as "blazing fast". However as you correctly mentioned "blazingly small" is not appropriately used.
We'll change the description accordingly.


Fix missing Lightning Bolt rarity in spoiler

The MTGS spoiler doesn't have a rarity on Lightning Bolt, so it doesn't get imported when you make spoiler.
Fixes issue #122.

too hacky

i might accept something that was more modular - a separate function that does hacks, like the before and after from make cards.


Issues with extremely short control ramps

There are some issues with extremely short ramps (< 1 sample frame, likely), possibly also affected by subsample ramp start time.

Really short ramps fall through the logic in a2_SetRamper(), so the target isn't set instantly as it should, nor does the ramping calculation in a2_PrepareRamper() work properly. Those functions don't seem to agree on how to handle these situations.
With slightly longer ramps (still < 1 sample frame), ramping is applied "correctly," but the accuracy is low, resulting in the ramps sometimes landing way off target.
These two issues are probably closely related, and both would likely be eliminated if all ramps that end within the next sample frame are handled as "set", and not just some of them.

This example demonstrates both issues:
export Song(P V=1 L=0)
{
	struct {
		wtosc
		panmix
	}
	!decay .5
	for {
		debug decay
		w triangle
		a .5; d decay
		a 0; d 500
		*decay .9
	}
}

It appears that for extremely short ramps, the control register write callbacks aren't even called. VM bug?

Well, DUH! a2_RTApply() was done after 'if(!dt) continue;', which is of course incorrect.


mbed_app.json -> mbed_lib.json

Should the sd-driver define a mbed_lib.json instead of the app example?
No one wants contaminate their shorter mbed_app.json with this many pin definitions, those should come either via here (or better yet, have the mbed os pin define stuff sorted out).

See https://github.com/ARMmbed/sd-driver/pull/13

@JanneKiiskila Can we close this?

Yes.


Feature Request - Add Pressure Trend

Only sensor I am missing from the SmartWeather integration.  TIA for considering the feature.

Have you considered a trend or derivative sensor for HA?
I used the derivative sensor for pressure and graphed it out to see the trend over time.
The derivative will show you the rate of change which is slightly more useful than trend in my opinion.
This being in my sensor.yaml which is an include in configuration.yaml
- platform: derivative   source: sensor.purpleair_pressure_2   name: Barometric Pressure Change   unit_time: h   time_window: "06:00:00"   round: 2
For the trend sensor, you would be under binary_sensor or things like the custom-bar-card will do the trend for you (not always pretty thou)

Glenn is right that this can be done in HA, by creating a sensor, but if it has to be done in this program, I will need to store the pressure values for at least the last three hours, as the way WeatherFlow has defined this is The Pressure Trend description is determined by the rate of change over the past 3 hours.
To accomplish this, and maybe future trends and sensors (High Sensor Value for the day, Low Sensor value for the day, etc.) I think I will convert the simple storage system I have today, to a SQLite Database, which makes this easier to implement and faster to to retrieve the right results.
Thoughts?

Your call on including in the calculated sensor.  I am totally fine either way.  It does get into a bit of a grey area if you need to add additional infrastructure to what is a relatively simple and clean translator/repeater.  There is a good argument to keep the number of moving parts small so that it is as reliable as possible.  After all, one of the main reasons to go with this approach over the web version is reliability in the case that the internet or the rest endpoints are down.  So from that perspective I would say just leave that up to an HA template sensor.
Not sure what you have planned for the dBase, but If you do decide to include it for completeness, I would maybe suggest just keeping the running total and times in the local storage vs. all of the individual observation history.  If the program dies or you lose readings for an extended period, you will have to start the sum all over again anyway.  If it is a short outage, or just a few dropped readings, you are no worse off without the detail.  If it is just the i/o that is the concern, then back to just keeping it simple.
Anyway, just my 2 cents.
Glenn, thanks for the tip on the derivative platform.  I didn't know that existed till you pointed it out.  Very handy, I have been doing things the hard way!  Always learning something new.

I'm torn...I see the benefits & drawbacks of both.  This will be much more simple than the current condition logic.
I posted in the HA forum about my attempt to mimic the WeatherFlow App inside Home Assistant.

That was too easy.  Took Glenn's tip and created my first derivative sensor:
  - platform: derivative
    source: sensor.sea_level_pressure
    name: pressure_trend_value
    round: 3
    unit_time: h
    time_window: "03:00:00"

Then just a simple template sensor to translate into the WeatherFlow output format...
      current_weather_pressure_trend:
        friendly_name: Pressure Trend
        value_template:  "{% if states('sensor.pressure_trend_value')|float > 0.0295 %} rising
                          {%- elif states('sensor.pressure_trend_value')|float < -0.0295 -%} falling
                          {%- else -%} steady
                          {% endif %}"

That was too easy. Took Glenn's tip and created my first derivative sensor:

There you go. 😁 I have spend the day re-writing the storage modules, so it will now use a SQLite database, instead of two text files. I did this for more than this reason, and SQLite is simple to use, and even simple to backup.
I have not changed the way the program works, I basically just re-wrote the read and write modules to use SQLite instead of flat text files.
And while I was doing this, I have also created the Pressure Trend functions, so as soon as I have time, I will add this sensor - even though you don't need it anymore - but now it is done.
I will let you know when this is ready to test.

You say you have every other sensor....
Are you calculating these are am I missing where they are?  (yes, I realize the app was just updated to display some of these easier)
Where are you getting Wet Bulb temperature?
Delta-T (Which I'm not sure what difference it is measuring...Air Temp is 60F, DewPoint is 58F, Wet Bulb is 59F but Delta-T is 33F.
I noticed that Air Density is not tracking between App and the calculated.  App = 0.07578 lbs/ft^3 and HA = 0.09 lb/ft^3.  It is not limited to a rounding issue.

Just stumbled on this:
https://weatherflow.github.io/Tempest/api/derived-metric-formulas.html
Something is not right in the backend for WeatherFlows calculations on Delta-T

Are you calculating these are am I missing where they are? (yes, I realize the app was just updated to display some of these easier)

I am not sure I said I have all the sensors, but eventually, I can make some more calculated Sensors, based on the formulas that WeatherFlow describes in the section you mention. I take the formulas from that link and try and convert them to Python.
If Air density is off for you, then there must be something with my conversion to imperial units, as it is pretty much spot on for me. But I will look at the formula again.

I have now released V2.0, where this is included. See the CHANGELOG.md for more info.


finish some client examples

b2
//TODO: download
//TODO: download/upload of full dir (sync)
//TODO: see how we can show progress when stdout chosen
//TODO: create/delete bucket
dagu
implement config mgmt: server addr/port & secret (user/passwd)
tfrobot
implement nemonic tfgrid, and network
mail client
check mail,upgrade to new format
gitea client
implement, add repo, add sshkey, see repos, ..

branch: development_config

https://github.com/freeflowuniverse/crystallib/pull/349
pr is ready
for gitea, @timurgordon is already handling it in another issue

kristof need to fix the base classes first

base classes are fixed, kristof needs to make example


Cannot register plugin with options when using TypeScript

Issue
When trying to register the HapiSwagger plugin with options while using TypeScript I get a type error.
Environment
npx envinfo --npmPackages '*hapi*' --binaries

npmPackages:
hapi-swagger: ^10.2.0 => 10.2.0
@hapi/hapi: ^18.4.0 => 18.4.0
@hapi/inert: ^5.2.2 => 5.2.2
@hapi/vision: ^5.5.4 => 5.5.4
Steps to Reproduce
Create a new Hapi server instance, call server.register just like in the example:
import * as Hapi from "@hapi/hapi";
import * as Inert from "@hapi/inert";
import * as Vision from "@hapi/vision";
import HapiSwagger from "hapi-swagger";

const server = new Hapi.Server({ port, host });

const swaggerOptions = {
  info: {
    title: "Test API Documentation",
  },
};

await server.register([
  Inert,
  Vision,
  {
    plugin: HapiSwagger, // This line is where the error is
    options: swaggerOptions
  }
]);

Expected Behavior
I would expect to not get an error from TypeScript since this seems to work without using TypeScript. To test whether this works without the type checking of TypeScript I casted the server object to the any type so that TypeScript can not check the type of the server object. This way I was able to test whether the register call (including the swaggerOptions) would work and it did.
Registering the plugin without providing the swaggerOptions works without a problem:
await server.register([
  Inert,
  Vision,
  HapiSwagger,
]);

Actual Behavior
TypeScript reports an error for the line "plugin: HapiSwagger":
No overload matches this call.
  The last overload gave the following error.
    Argument of type '((PluginBase<OptionalRegistrationOptions> & PluginNameVersion) | (PluginBase<OptionalRegistrationOptions> & PluginPackage) | (PluginBase<ServerViewsConfiguration> & PluginNameVersion) | (PluginBase<...> & PluginPackage) | { ...; })[]' is not assignable to parameter of type '(PluginBase<any> & PluginNameVersion) | (PluginBase<any> & PluginPackage) | Plugin<any>[]'.
      Type '((PluginBase<OptionalRegistrationOptions> & PluginNameVersion) | (PluginBase<OptionalRegistrationOptions> & PluginPackage) | (PluginBase<ServerViewsConfiguration> & PluginNameVersion) | (PluginBase<...> & PluginPackage) | { ...; })[]' is not assignable to type 'Plugin<any>[]'.
        Type '(PluginBase<OptionalRegistrationOptions> & PluginNameVersion) | (PluginBase<OptionalRegistrationOptions> & PluginPackage) | (PluginBase<ServerViewsConfiguration> & PluginNameVersion) | (PluginBase<...> & PluginPackage) | { ...; }' is not assignable to type 'Plugin<any>'.
          Type '{ plugin: Plugin<RegisterOptions>; options: { info: { title: string; }; }; }' is not assignable to type 'Plugin<any>'.
            Object literal may only specify known properties, and 'plugin' does not exist in type 'Plugin<any>'.ts(2769)

@nitrixx any chance you can create a repo that I can clone to reproduce? I don't use typescript but do use hapi-swagger across microservices without issue.

@robmcguinness thanks for your reply, I just created a repo for you to clone:
https://github.com/nitrixx/hapi-ts-test

thanks. i see the error but not quite sure how to debug.

I just ran into the problem. A quick solution until the types are fixed is to do this:
await server.register([Inert, Vision]);
await server.register(
            {
                plugin: HapiSwagger,
                options: swaggerOptions,
            },
        );

@nitrixx
the @types/hapi__hapi typings have use overload methods to determine which register function to call when initializing hapi plugins.
register<T>(plugin: ServerRegisterPluginObject<T>, options?: ServerRegisterOptions): Promise<void>;
register<T, U, V, W, X, Y, Z>(plugins: ServerRegisterPluginObjectArray<T, U, V, W, X, Y, Z>, options?: ServerRegisterOptions): Promise<void>;
register(plugins: Array<ServerRegisterPluginObject<any>>, options?: ServerRegisterOptions): Promise<void>;
register(plugins: Plugin<any> | Array<Plugin<any>>, options?: ServerRegisterOptions): Promise<void>;

The sample project https://github.com/nitrixx/hapi-ts-test error was stating that none of the plugin register calls were matching the signatures above.  Changing the sample project to below fixed the error.
const swaggerOptions: HapiSwagger.RegisterOptions = {
  info: {
    title: "Test API Documentation"
  }
};

const plugins: Array<Hapi.ServerRegisterPluginObject<any>> = [
  {
    plugin: Inert
  },
  {
    plugin: Vision
  },
  {
    plugin: HapiSwagger,
    options: swaggerOptions
  }
];

I'm not Typescript expert so please let me know if that doesn't resolve your issue.

I found the same problem too but now I know the reason for this. This issue does not relate to hapi-swagger at all.
Typescript need to have correct typed value and from this example. Code from issue owner.
const swaggerOptions = {
  info: {
    title: "Test API Documentation",
  },
};

await server.register([
  Inert,
  Vision,
  {
    plugin: HapiSwagger, // This line is where the error is
    options: swaggerOptions
  }
]);

What type of array that pass to register method?
Answer is Array<Plugin<any> | ServerRegisterPluginObject<any>> but type in DefinitielyTyped project is Array<Plugin<any>
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/827e5dac5982b9889ecbbd2d99807efa58059bcc/types/hapi__hapi/index.d.ts#L3883
This is reason why it's error and solution. As you can guess this, we can create PR by change that part to have type like I said but I don't think it's good idea. This is bad habit from normal JS coding style and we just want to add any into array that we want. I don't like that.
Another solution without chancing type is coding like this.
const swaggerOptions = {
    info: {
        title: "Test API Documentation",
    },
};

await server.register([
    {
        plugin: Inert
    },
    {
        plugin: Inert
    },
    {
        plugin: HapiSwagger, // This line is where the error is
        options: swaggerOptions
    }
]);

so type of array will be Array<ServerRegisterPluginObject<any>>. This one is better and solve problem too.


operators [CI] hive-operator

Sync with current team members.

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your submission signed?

what about me? do i get an entry in there?

gdi, you were the whole reason I started these :(

what about me? do i get an entry in there?

fixed

/merge possible


Adding initial script for search by keyword

Description
This is a very basic (and slightly scrappy!) script for running a keyword search - the goal is just to give us data to work through in a structured way, to start improving (not meant as an end product).
Fixes # 14
You can test it runs by running from your project directory:
python dap_job_quality/pipeline/keyword_search.py
I can separately send the link to where I've uploaded the output, to work through together.
Checklist:

[x] I have refactored my code out from notebooks/
[x] I have checked the code runs
[ ] I have tested the code
[x] I have run pre-commit and addressed any issues not automatically fixed
[x] I have merged any new changes from dev
[x] I have documented the code

[ ] Major functions have docstrings
[ ] Appropriate information has been added to READMEs

[x] I have explained this PR above
[x] I have requested a code review

@RFOxbury thanks heaps for these, I've now incorporated your comments! Take a look, and let me know if OK to merge


Fix the error handling in ERR_get_state

Ignoring the return code of ossl_init_thread_start created a memory leak.
master & 1.1.0

In the test case 04-test_bioprint.t the threadstopkey was 0 in CRYPTO_THREAD_set_local
but it was 2 when the OPENSSL_cleanup was done.

merged, thanks!

@richsalz please also merge to 1.1.0

done, both commits to 1.1.0


default to tunnel without ABISupport tag

When compiling a Linux binary without ABISupport, default to use the
tunnel.  The behaviour is expected in podman-remote.
Also set a default for the remote flag so podman-remote works OOB.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

LGTM once the question from @rhatdan is addressed

LGTM
I'm fine with merging this now as long as there's an issue/jira card spun to answer @rhatdan's question.


[Feature Request] Back Button inside de Key-Value Modal

Hello @lijyze !!!!
Would be amazing to have a Back <- in the last line of the Key-Value modal .
Sometimes I made a mistake to select the wrong map and I have to type ESC and my hotkey to open the Modal again to select the right map.
This image is from the QuickAdd plugin that has a back button inside a Modal

Thanks reading this and have a great day!!!!

Finished

Finished

Working on version 1.0.2 Obsidian 0.14.6 :)
Thank you !


Add REST endpoint for token

          It might be worth adding a REST endpoint to return a token as a future enhancement.

Originally posted by @aceade in https://github.com/aceade/express-chat-backend/issues/10#issuecomment-1748415653
Instead of hard-coding into the .env file, generate random ones for each client.

Tokens are randomly generated, but don't expire until the service goes down. That's fine for a test app, but it would be better if I could remove them anyway.

Tokens will now expire in an hour.


Consider turning on github discussions for this repository

I.e.:
https://docs.github.com/en/discussions
As far as I can tell, there isn't yet an established forum for Saturn.

Closing as these are now enabled