Impro 176 recursive filter

Adds the capability to run a recursive filter to convert a square neighbourhood into a Gaussian-like kernel or simply to smooth over short distances. The recursive filter uses an "alpha" parameter that controls what proportion of stuff (probability) is passed along to the next grid square.
Implementation  allows the alpha parameter to be set on a grid square by grid square basis (e.g. an array of alpha parameters equivalent in dimensions to the domain). Each grid square has a pair of alpha parameters to allow for orthogonally discrete functionality, e.g. one to act in the N-S direction, and another to act in the E-W direction.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

This fits the bill. Good work Paul.


Difference between paddlecloud  cp and paddlecloud file put ?

What's the difference between paddlecloud  cp and paddlecloud file put?

paddlecloud file put will be deprecated. It was a simple version of file uploading. Will be removed. Check this out: https://github.com/PaddlePaddle/cloud/issues/283


Misc Bugfixes

Pull Request Test Coverage Report for Build 38

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 75.258%

Totals

Change from base Build 34:
0.09%

Covered Lines:
219

Relevant Lines:
291

💛  - Coveralls


Fix rendering of git commits with bodies

Summary
Fix rendering of git commits with bodies
Changes Made
Fix rendering of git commits with bodies
TODO
None
Motivation
Did fail on commits with newlines
Testing
None
Screenshots/GIFs
None
Checklist
Please ensure all of the following are completed before submitting the PR:

[x] Code has been tested and verified.
[x] Documentation has been updated to reflect the changes.
[x] All tests pass successfully.
[x] Code follows the project's coding guidelines and style.
[x] The branch is up-to-date with the latest changes from the main branch.
[x] Reviewed by at least one other contributor.

Related Issues
This PR addresses the following issue(s): None
Additional Notes
None

Thanks for submitting a pull request!
We will review it as soon as possible.

Hey @0xWDG,
Thanks for your contribution.
Your PR has been merged!
Your name will appear on https://auroraeditor.com/#contributors in a few moments, if you have contributed to the editor.
Thanks again for your contribution!
Kind Regards,
Aurora Editor Team.


Add pagination to show posts

Is there a way to enable pagination for this template?
Having 20 blogposts will make a list 20 posts appear on the first page.
It would be nice to have be able to show  for example 5 per page.

Documentation does not tell you where (what file) file should I put these options.
Where is this modifyBlogPluginOptions() defined?
I tried this in .vuepress/config.js, but modifyBlogPluginOptions is undefined. Setting directories -tag inside themeConfig does not work either.
module.exports = themeConfig => {
	const { modifyBlogPluginOptions } = themeConfig
	console.log('modifyBlogPluginOptions', modifyBlogPluginOptions)

Great, thanks! My bet, it's even in the README.


add notes about how to submit an app to the homepage list

Hopefully this will help reduce the work required by the team to manage incoming submissions.
What do you think, @jlord?

Awesome! Looks good 🐑


DropDownMenu.Trigger fires the first "asChild (as button)" item's function with keyboard activation.

Bug report
Current Behavior
When setting asChild to a DropDownMenu item, with the child being a button, using keyboard enter key on the trigger will fire that child's onClick function instead of opening the menu.
Expected behavior
Pressing the enter key on the trigger should open the menu.
Reproducible example
Use keyboard to navigate on the trigger, then press enter key.
CodeSandbox Template
Sample of the code that causes the issue :
          <DropdownMenuItem asChild>
            <button onClick={() => alert("this will fire on keyboard")}>
              This is a button
            </button>
          </DropdownMenuItem>

Suggested solution
DropDownMenu items should be either anchors or buttons at all time, and built with those in mind. asChild seems to cause a lot of issues in this component and could be removed by having correct and accessible default semantics on the menu item itself. It is important that onClick events are never bound to a div, as users can have specific needs requiring them to style, announce and present buttons, anchors and possible interactivity in specific ways.
Your environment

Software
Name(s)
Version

Radix Package(s)

latest

Browser
Chrome
100

Assistive tech
keyboard navigation

Hi @rlacorne,
This is a duplicate of #1268. Essentially this is because of the focus management, this is because focus is moved during keydown so the enter keyup is firing on your button which triggers the button click.
A simple way to prevent this if you need asChild would be to use a div instead of a button (like the item we provide) because the component converts it to a role="menuitem", so it will be losing button semantics anyway.
In other words:

DropDownMenu items should be either anchors or buttons at all time, and built with those in mind. asChild seems to cause a lot of issues in this component and could be removed by having correct and accessible default semantics on the menu item itself. It is important that onClick events are never bound to a div, as users can have specific needs requiring them to style, announce and present buttons, anchors and possible interactivity in specific ways.

It doesn't have to be as we handle the accessibility for your anyway, so relying on semantics isn't necessary.

Essentially this is because of the focus management, this is because focus is moved during keydown so the enter keyup is firing on your button which triggers the button click.

Is there a way to prevent this event from propagating, maybe stopPropagation during the capture phase? Just spitballing here as I encountered the scenario with using a button as the child.


Enforce non-use of advanced features

When an advanced feature is not announced to be supported by a client, the router should not use it in conversation with that client.

I'm not sure it's worth. it's tedious to implement and comes with the checking overhead for .. what gain?

migrated to https://github.com/crossbario/crossbar/issues/442


Add a tooltip for profile avatar and online status icon

Details
Tooltip added for profile avatar and online status/offline dot
Fixed Issues

$ https://github.com/Expensify/App/issues/5973
Tests

Navgiate to New Expensify
Hover over the avatar profile icon and the online dot

QA Steps

Navigate to New Expensify
Hover over the avatar profile icon and the online dot
Make sure there is a tooltip over the avatar with name of the user
And overing over the online dot, you can see tooltip describing your status

Tested On

[x] Mobile Web
[x] Desktop

Screenshots

Well, there was not many opinions shared in the thread, but we will keep it as it is here and was originally in the issue description! @kakajann Thank you for your patience 🙇

🚀 Deployed to staging by @mountiny in version: 1.1.11-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.1.12-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


OpenJS Foundation Security Collab Space Meeting 2023-05-23

Time
UTC Tue 23-May-2023 17:00 (05:00 PM):

Timezone
Date/Time

US / Pacific
Tue 23-May-2023 10:00 (10:00 AM)

US / Mountain
Tue 23-May-2023 11:00 (11:00 AM)

US / Central
Tue 23-May-2023 12:00 (12:00 PM)

US / Eastern
Tue 23-May-2023 13:00 (01:00 PM)

EU / Western
Tue 23-May-2023 18:00 (06:00 PM)

EU / Central
Tue 23-May-2023 19:00 (07:00 PM)

EU / Eastern
Tue 23-May-2023 20:00 (08:00 PM)

Moscow
Tue 23-May-2023 20:00 (08:00 PM)

Chennai
Tue 23-May-2023 22:30 (10:30 PM)

Hangzhou
Wed 24-May-2023 01:00 (01:00 AM)

Tokyo
Wed 24-May-2023 02:00 (02:00 AM)

Sydney
Wed 24-May-2023 03:00 (03:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Security Collab Space+Meeting+2023-05-23&iso=20230523T1700
or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+May+23%2C+2023+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1eV-dmH0tAAl0Lj-9DIqLA13zwzjv5VC6NYITusP-A7A/edit

Agenda
Extracted from security-agenda labelled issues and pull requests from the openjs-foundation org prior to the meeting.
openjs-foundation/security-collab-space

Onboard OpenJS projects to LFX Security Dashboard #5
Top 10 things for a JS open source project should do from a security perspective #4
Curate a list of high value security-focused training courses for the JS community #2
Curate a list of high value security-focused learning resources for the JS community #1

Invited

OpenJS Foundation Security Collab Space Members
OpenJS Foundation Cross Project Council
OpenJS Foundation Project Maintainers
OpenJS Foundation Board of Directors
All are welcome

Observers/Guests
Notes
The agenda comes from issues labelled with security-agenda across all of the repositories in the openjs-foundation org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
link for participants: Zoom link: https://zoom.us/j/93954555387

For those who just want to watch: https://livestream.openjsf.org

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

Closing. Meeting happened. No minutes/notes.


Unable to add a new colour light if in temperature mode

Describe the bug
After installing the HA-Hive-Custom-Component, when the component was finding my lights. It kept crashing when trying to add my 2 colourtuneablelights.
2021-02-14 13:59:20 ERROR (MainThread) [homeassistant.components.light] hive: Error on device update!
Traceback (most recent call last):
  File "/opt/homeassistant/lib64/python3.9/site-packages/homeassistant/helpers/entity_platform.py", line 358, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/opt/homeassistant/lib64/python3.9/site-packages/homeassistant/helpers/entity.py", line 466, in async_device_update
    await task
  File "/home/homeassistant/.homeassistant/custom_components/hive/light.py", line 160, in async_update
    self.device = await self.hive.light.get_light(self.device)
  File "/opt/homeassistant/lib64/python3.9/site-packages/pyhiveapi/light.py", line 59, in get_light
    "hs_color": await self.get_color(device),
  File "/opt/homeassistant/lib64/python3.9/site-packages/pyhiveapi/light.py", line 156, in get_color
    (data["state"]["hue"]) / 360,
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int

We've found if a colourtuneablelight does not have a colour, but a temperature selected. When it gets to this part in light.py
 if device["hiveType"] == "colourtuneablelight":
                dev_data["status"].update(
                    {
                        "hs_color": await self.get_color(device),
                        "mode": await self.getColourMode(device),
                    }
                )

self.get_color(device), returns nothing.
This can be seen after the lights have been added in Developer Tools
Temperature selected
min_mireds: 153
max_mireds: 370
brightness: 127.5
color_temp: 332
available: true
mode: MANUAL
friendly_name: Left lamp
supported_features: 19

vs colour selected
min_mireds: 153
max_mireds: 370
brightness: 255
color_temp: 370
hs_color:
  - 285
  - 28.235
rgb_color:
  - 237
  - 183
  - 255
xy_color:
  - 0.329
  - 0.25
available: true
mode: MANUAL
friendly_name: Right lamp
supported_features: 19

Expected behavior
Colour light will be added, even when in temperature mode.
Additional context
Once the light are in HA, they seem to be fine after restarting the HA service and reloading the Hive integration.
Cheers

https://github.com/Pyhive/Pyhiveapi/pull/13

@ad5665
thanks for raising this it will be fixed in the next version of the custom component.


Add self-renewing procedure for the Letsencrypt certifcate

Use the ManagementAPI.

https://github.com/runeasymail/easymail/commit/c188c61861e581947412bb6c5ac4865d82960cda


Downloading problem?

When I ran the code finetune.sh, it began to download from jtxie.com while it's too slow. So I decided to use BaiduYun. However,  I got the following problem:
Start finetuning! Namespace(arch='mpncovresnet101', batch_size=10, benchmark='CUB', classifier_factor=5, data='/path/to/the/data/CUB', dist_backend='gloo', dist_url='tcp://<IP_ADDRESS>:23456', epochs=100, evaluate=False, freezed_layer=0, gpu=1, lr=0.0012, lr_method='step', lr_params=[[100.0]], modeldir='Results/Finetune-CUB-mpncovresnet101-MPNCOV-reproduce-lr1.2e-3-bs10', momentum=0.9, num_classes=200, pretrained=True, print_freq=100, representation='MPNCOV', resume='Results/Finetune-CUB-mpncovresnet101-MPNCOV-reproduce-lr1.2e-3-bs10/mpncovresnet101-ade9737a.pth.tar', seed=None, start_epoch=0, store_model_everyepoch=False, weight_decay=0.0001, workers=8, world_size=1) main.py:127: UserWarning: You have chosen a specific GPU. This will completely disable data parallelism.   warnings.warn('You have chosen a specific GPU. This will completely ' => loading checkpoint 'Results/Finetune-CUB-mpncovresnet101-MPNCOV-reproduce-lr1.2e-3-bs10/mpncovresnet101-ade9737a.pth.tar' Traceback (most recent call last):   File "main.py", line 503, in <module>     main()   File "main.py", line 206, in main     checkpoint = torch.load(args.resume)   File "/home/yzzc/.local/lib/python3.5/site-packages/torch/serialization.py", line 358, in load     return _load(f, map_location, pickle_module)   File "/home/yzzc/.local/lib/python3.5/site-packages/torch/serialization.py", line 527, in _load     return legacy_load(f)   File "/home/yzzc/.local/lib/python3.5/site-packages/torch/serialization.py", line 441, in legacy_load     tar.extract('storages', path=tmpdir)   File "/usr/lib/python3.5/tarfile.py", line 2027, in extract     tarinfo = self.getmember(member)   File "/usr/lib/python3.5/tarfile.py", line 1738, in getmember     raise KeyError("filename %r not found" % name) KeyError: "filename 'storages' not found"
How can I solve this problem?

The mpnconvresnet50-15991845.pth is ok but resnet101 one still has the problem.

mpncovresnet101-ade9737a.pth is not checkpoint file. Please put the model into ~/.torch/models/ and try it again.

mpncovresnet101-ade9737a.pth is not checkpoint file. Please put the model into ~/.torch/models/ and try it again.

I did so. I did the same operation to resnet50 model and it worked. But it is not fit for the resnet101 one.

@abcdvzz I didn't reproduce this problem. I uploaded a new model, you can try it, code: rurg
Please fell free if you want to reopen this issue.

I am unable to download mpncovresnet50-15991845.pth from http://jtxie.com/models/mpncovresnet50-15991845.pth because the web-site does not work.
Is anybody able to send me that pth file?

@OrkhanHI Hi, you can download it in this path Google Drive

@jiangtaoxie thank you!

Is there anywhere we can get mpncovresnet101-ade9737a.pth that's not from baidu? I'm having difficulties creating an account from overseas. Thank you!


Create site for Relaton

Relaton is the interoperable data model for citations, based on the international standard for citations, ISO 690.

Relaton models: https://github.com/riboseinc/relaton-models
Relaton CLI gem: https://github.com/riboseinc/relaton-cli
Relaton core gem: https://github.com/riboseinc/relaton

Relaton supports multiple bibliographic sources (all of them from standards bodies, for now)

Relaton for ISO: https://github.com/riboseinc/relaton-iso
Relaton for IETF: https://github.com/riboseinc/relaton-ietf
Relaton for CalConnect: https://github.com/riboseinc/relaton-calconnect
Relaton for GB: https://github.com/riboseinc/relaton-gb

The Relaton system is used to power the official CalConnect document registry.

@strogonoff we can copy the Metanorma site structure over since the structure is also similar. However we need to think about how we can synchronize the structure as we improve them...

IETFBib https://github.com/riboseinc/ietfbib
ISOBib https://github.com/riboseinc/isobib
IECBib https://github.com/riboseinc/iecbib
GBBib https://github.com/riboseinc/gbbib

I don’t think we should go out of our way to perfectly synchronize structure just for the sake of it, these are different projects with their own separate homes. As we improve the Open Project framework, sites using it get the same new features as they bump to newer version (and as for features that don’t make it into OPF because they’re are too specific, some divergence is not a crime).

Good point, diversity is not a crime. Yet the structured nature of Relaton (bibliography for standards) and Metanorma (documents for standards) are so similar that the same site structure will help.

The structure is ultimately similar across the board: some software, some specs, and project-wide getting-started docs & tutorials… I think I get your point though!

Why would I want to use Relaton if I’m authoring let’s say a CalConnect document?

Relaton is used in Metanorma to auto-fetch bibliographic references. Bibliographic references contain the document ID, title, authors, edition year, copyright information, etc.
Usually when you write a document, you have to Google search for the number/title and manually copy/paste them in your document.
With Relaton, it's all automatic.
Relaton also allows you to interchange bibliographic data, for example, you can have a set of references stored in a Relaton local cache. Such as via the relaton fetch command.
In addition, we are developing a "Relaton registry" function that serves up Relaton bibItem collections and Relaton bibItems. That is useful for the automatic retrieval of bibliographic information.

I’m not sure what causes the build error, configuration and Rakefile used is identical to Metanorma but the output says:
JEKYLL_ENV=production jekyll build --config=_config.yml
Configuration file: /home/travis/build/riboseinc/relaton.com/_config.yml
Configuration file: _config.yml
 Theme Config file: /home/travis/.rvm/gems/ruby-2.5.1/gems/jekyll-theme-open-project-1.1.25/_config.yml
            Source: /home/travis/build/riboseinc/relaton.com
       Destination: /home/travis/build/riboseinc/relaton.com/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
Invalid theme folder: _data
                    done in 2.683 seconds.
 Auto-regeneration: disabled. Use --watch to enable.
rake aborted!
ArgumentError: ./output does not exist
/home/travis/.rvm/gems/ruby-2.5.1/gems/html-proofer-3.9.3/lib/html-proofer.rb:30:in `check_directory'
/home/travis/build/riboseinc/relaton.com/Rakefile:86:in `block (2 levels) in <top (required)>'
/home/travis/.rvm/gems/ruby-2.5.1/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
/home/travis/.rvm/gems/ruby-2.5.1/bin/ruby_executable_hooks:24:in `eval'
/home/travis/.rvm/gems/ruby-2.5.1/bin/ruby_executable_hooks:24:in `<main>'
Tasks: TOP => test:production
(See full trace by running task with --trace)
The command "bundle exec rake test:production && rake build:production" exited with 1.

@ronaldtse could you help take a look as to what may be causing the missing output directory during CI build?

It's still failing due to lack of /output. I think the $outputDir variable in Rakefile is wrong, it probably should point to _site because the output resides there. Not sure why it's not failing at metanorma.com...
When I manually create output/, the code runs correctly.

Not sure why it's not failing at metanorma.com

That is indeed what I find strange, I thought perhaps it could be configured somewhere in the login-protuected Travis dashboard

I've set the site variables at Travis properly, but if this issue persists it is due to the code...

I can verify that jekyll build works locally, so it must be the logic in Rakefile, .travis-ci.yml, or settings in Travis or GitHub

The Travis command of “rake test:production” shows the same error on my machine. So it’s a real error that can be reproduced.

I never doubted the error is real! :D
Looks like there’s been a breaking change in the API of html-proofer.

https://github.com/riboseinc/jekyll-theme-open-project/commit/7991698d9e559ac575d8cd956535a35f42f034a1

I've deployed the site by disabling the HTML proof test. The problem is that the proof test was never actually run properly, so it never did anything. We need to configure it to actually work and resolve links 😉

@ronaldtse wait so the fix I pushed was not enough? Setting the version for html-proofer fixed the issue for me.

Let me know, if html proofing causes breakage I’ll update the setup docs

The issue is that the htmlproofer has never worked. When the tests are run, the proofer actually tests the pages and the links it tests cannot be resolved (esp since it’s looking to resolve links to “relaton.com). If you can make the proofer work, that’ll be great and we can re-enable the tests.
There are other failures like pages missing, favicon missing (because they are really missing!).

@ronaldtse OK I see that fixing html-proofer version fixed the build, but you disabled proofing in an unrelated feature to speed up generation.
I think failures are good, why disable them? We get to them eventually! Where can I see them, Travis log?

I believe what blocked the first deploy was the way new html-proofer version started treating output directory flag after a backwards-incompatible change (fixing that gem’s version eliminated that error for me). That said, I have no objection on other points.


Transition with appear hook set at component level

Version
2.5.2
Reproduction link
https://jsfiddle.net/Twinpix/sfjhLcxw/
Steps to reproduce
Click on showA or showB button to see which transition hooks is fired
What is expected?
When clicking on showA or showB button, appear hooks should be fired first on the first time the component is loaded
What is actually happening?
On transition, enter hooks are the only ones fired

I need this feature because for my projects I need a different animation/transition when a component is first loaded. I'm using vue-router to load component so I put the issue for vue-router, but now I realized it-s more a vue issue. thanks for help.

Do not open the same issue in both repos please.
Duplicate of vuejs/vue-router#1839

You could save somewhere the state about is it the first time this component has appeared to trigger different transitions. You can even put that into a custom component that uses a transition component


Fallback to Default Config When OPENAI_CONFIG_HOME is Set and YAML Configuration is missing.

When the environment variable OPENAI_CONFIG_HOME is set, and the corresponding YAML configuration file does not exist, the chatgpt-cli application falls back to its default configuration silently without throwing an error. This behavior can lead to confusion as users may expect an error to be raised when the specified configuration is not found.
I know this sounds silly, but out of habit, I name all my yaml files with the extension .yml. It took me more than an hour to realize that that was the problem. I decided to build, log and everything in order to find that it was my fault. In any case, since I'm biased, I think that if somebody sets the variable OPENAI_CONFIG_HOME, it's because he/she wishes to use that directory, and it should not fallback to the default configuration file.
Nice library btw.

Thank you! I'm wondering if it would make sense to just create the file for a user if it doesn't exist. Including any new keys that may be introduced in future versions.
Because right now the CLI works perfectly fine without the config file. But it is kinda error prone as you point out to leave this up to the user.

In my case, I set explicitly the environmental variable. I really think that an error code should be fine. Or as you mentioned, if you create the file, maybe you can put a warning. However, I strongly believe that if the person is trying to do that, it's because he/she knows what he/she's doing.
In a side comment, I actually created another configuration because I wanted to pass another role. However, I strongly believe that if you have some kind of storage and select, it could be really nice. I can imagine even an extension to select the type of response you want, either specific to your user or generated some crowdsource (like: https://github.com/f/awesome-chatgpt-prompts/blob/main/prompts.csv). Again, in my case, I wanted with the variable, to play the role of a programmer, because most of the time I don't need the explanations in the code.
In any case, it's not my call, and unfortunately, I do not have the time to contribute to your code. Kudos again to you 😉

@silgon That's fair. I will implement something. Printing a warning should be sufficient indeed.
Sorry, I have been busy rolling out other features. Including the prompt flag. You should give it a go! :)
git diff | ./bin/chatgpt -n -p ../prompts/write_pull-request.md

or
cat README.md | chatgpt -n --prompt ../prompts/summarize.md

More info here: https://github.com/kardolus/chatgpt-cli?tab=readme-ov-file#prompt-support

I implement something :)
See the test below:
 2024-10-12 08:13:53 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → mkdir -p /tmp/confighome

 2024-10-12 08:14:17 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → export OPENAI_CONFIG_HOME=/tmp/confighome

 2024-10-12 08:14:36 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → ./bin/chatgpt hi
Warning: config.yaml doesn't exist in /tmp/confighome, create it
Hello again! How can I assist you today?

 2024-10-12 08:14:42 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → unset OPENAI_CONFIG_HOME

 2024-10-12 08:14:55 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → ./bin/chatgpt hi
Hello! How can I assist you today?

 2024-10-12 08:14:59 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → export OPENAI_CONFIG_HOME=/tmp/confighome

 2024-10-12 08:15:07 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → touch /tmp/confighome/config.yaml

 2024-10-12 08:15:16 ⌚ (☸ |kind:N/A) Guillermos-MacBook-Pro in ~/workspace/chatgpt-cli
± |main {6} U:1 ✗| → ./bin/chatgpt hi
Hello! How can I assist you today?

You can find the commit here: https://github.com/kardolus/chatgpt-cli/commit/412ef254ed39c37dee00aba4fa0794c57f7a5769
I expect to cut a new release somewhere within the next two weeks.

Nice. It's really nice work you are doing =). Concerning the prompt, I think it is really cool. I personally use a lot the pipe command to pass a context.
Thanks again! 🎉

You got it! Thank's for the kind words. Glad you are enjoying the CLI.


Fix error message comparison

Follows-up #5749
NumPy 1.18
AttributeError: incompatible shape for a non-contiguous array

NumPy 1.19
AttributeError: Incompatible shape for in-place modification. Use `.reshape()` to make a copy with the desired shape.

Jenkins test this please.

/test

Jenkins CI test (for commit 8287e616429de35d07d32d231b87f642a1804f34, target branch master) failed with status FAILURE.

Let me merge this as the Jenkins failure is unrelated, and cupy.linux.cuda114 pass at https://ci.preferred.jp/cupy.linux.cuda114/79840/.


more noticeable focus color

The on focus color is currently yellow, which is a little hard to see against a white background (see below). Maybe pick a color which is a little easier to see?

changed to red


Update for JupyterLab 3, Router, Settings, etc.

Sorry for the monster PR.

References:

fixes #7
fixes #12
fixes #3

Changes:

supports JupyterLab

this eschews jupyter-packaging and build-system with some simpler stuff...

i don't like npm stuff running inside of pip install, much less webpack

reworks the package metadata

the only version number is package.json/version

reworks CI

build the whl, tar.gz and tgz in one linux job, add a SHA256SUM file
test against a matrix vs installing the .whl or .tar.gz
still building the npm tarball because...

hoists the Meet instance to a new VideoChatManager exposed as the token that other plugins can use in activate

this will allow other extensions to do... things with the current Meeting. Not sure what, but i'm excited about:

being able to replace the chat with real (markdown) cells
breakout rooms (#5)

adds settings for

user display name and email
configOverwrite (adds disableThirdPartyRequests to defaults)
interfaceConfigOverwrite (also hides the google/office 365 extension banner)
hiding public room UI (true by default)

allows for creating public rooms
reworks the DOM structure some, especially on the room list

tries to use more accessible/semantic HTML, remove lots of classes
some icons

loads external_api.js directly from the jitsi domain (via gross <script> injection, but what can you do) instead of bundling

questions on compatibility between notebook & jupyter_server packages

What's the flavor of concern? The nbclassic route works... but I don't know for how long. I could see issues arising prior to the hard cut at lab 4.x, but haven't been keeping track of the various lifecycle pieces.
A thing I'd really like to see is this working with voila (likely as a separate package), which is already jupyter_server-only.
As for integration with other UIs... I don't think the design constraints of jupyterlab-classic lend itself very well to this extension, as a dialog would be extremely unsatisfying, and if you start slamming more dom in the page... that might be resizable... and tabbed... well, sure sound like Lab at that point.

CR the labextension

Yeah, we had some events to run and needed some of the capability, so that initial PR kinda just kept going. Of course, shame on me for not having added better tests, but Always Be Demoing...
 I'll do another look over it, and re-request review... doing the binder shakedown i noticed some stuff, as it's the only hub-like-thing i have to test open source stuff. If you had any notes from it (not) working in your required hub setup, that would be rad. You can grab the tarballs from the dist asset.

questions on compatibility between notebook & jupyter_server packages

What's the flavor of concern? The nbclassic route works... but I don't know for how long. I could see issues arising prior to the hard cut at lab 4.x, but haven't been keeping track of the various lifecycle pieces.
A thing I'd really like to see is this working with voila (likely as a separate package), which is already jupyter_server-only.
As for integration with other UIs... I don't think the design constraints of jupyterlab-classic lend itself very well to this extension, as a dialog would be extremely unsatisfying, and if you start slamming more dom in the page... that might be resizable... and tabbed... well, sure sound like Lab at that point.

CR the labextension

Yeah, we had some events to run and needed some of the capability, so that initial PR kinda just kept going. Of course, shame on me for not having added better tests, but Always Be Demoing...
 I'll do another look over it, and re-request review... doing the binder shakedown i noticed some stuff, as it's the only hub-like-thing i have to test open source stuff. If you had any notes from it (not) working in your required hub setup, that would be rad. You can grab the tarballs from the dist asset.

Alright, there are still some lingering issues with restoring a particular video chat after refreshing the browser... I think i messed up the commands somehow. Otherwise, shook down everything I found that was bothering me. I guess give it a spin and let me know what's missing from a functionality perspective. While working on it, had some ideas I'll hoist to follow-on issues.

Alright, there are still some lingering issues with restoring a particular video chat after refreshing the browser... I think i messed up the commands somehow. Otherwise, shook down everything I found that was bothering me. I guess give it a spin and let me know what's missing from a functionality perspective. While working on it, had some ideas I'll hoist to follow-on issues.

@yuvipanda thoughts?

@yuvipanda thoughts?

@bollwyvl I've hit the merge button :D Will you be able to do appropriate releases? <3

@bollwyvl I've hit the merge button :D Will you be able to do appropriate releases? <3

:heart_eyes_cat: on it. I'll start a release ticket, and start shaking it down.

:heart_eyes_cat: on it. I'll start a release ticket, and start shaking it down.


Set up a CI/presubmit for gcc

GCC (system compilers) are used for all distributable artifacts on Linux (esp since things like Python source builds can't make the compiler assumption). We don't have a CI for it and should.

Some notes for implementation:
To leverage our existing Docker images + CI pipelines, we'd have to override what we set in the base Docker image:
https://github.com/google/iree/blob/accc5230038a55a02584239478a2addaf7b462cc/build_tools/docker/base/Dockerfile#L9-L11
I'd suggest putting another entry in the "build configurations" pipeline for organization (I wouldn't expect the gcc build to have major differences in test coverage or runtime behavior, so just running a build with no tests should provide enough coverage):
https://github.com/google/iree/blob/accc5230038a55a02584239478a2addaf7b462cc/build_tools/buildkite/cmake/build_configurations.yml#L8-L15
using a script like one of these:

https://github.com/google/iree/blob/main/build_tools/cmake/build_tracing.sh
https://github.com/google/iree/blob/main/build_tools/cmake/rebuild.sh
https://github.com/google/iree/blob/main/build_tools/cmake/build_host_install.sh

Seems like we must be using a docker image for the release pipeline, so should be able to use that.

It's a manylinux image with rhel patched dev set. You're welcome to use it

but it is a pita to extend and patch with modern tools.

Why not just use the regular docker container and set either the cmake
compiler flags to GCC or set the env vars in whatever script kicks off the
build?
On Tue, Sep 21, 2021, 4:43 PM Geoffrey Martin-Noble <
@.***> wrote:

Seems like we must be using a docker image for the release pipeline, so
should be able to use that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/iree/issues/6959#issuecomment-924466764, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADYVAEQFSHSZ4IW6EBMJXTUDEKCBANCNFSM5DMDOBOA
.

Well the thing we actually care about is being able to build the release, so it seems like we should just build in the same image. But we can also use whatever gcc is in the base ubuntu18.04 that our docker images are based on

And with that approach we have a failure:
/usr/bin/g++    -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -w -fdiagnostics-color -ffunction-sections -fdata-sections -DC
XX_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR -fPIE   -Werror -Werror=global-constructors -std=c++14 -o CMakeFiles/cmTC_ee7d9.dir/src.cxx.o -c src.cxx
cc1plus: error: -Werror=global-constructors: no option -Wglobal-constructors

Apparently the image has gcc 7, whereas your manylinux image has gcc 9. OTOH when I try to run with your manylinux image it's all upset about being unable to find Python3, which we apparently need for the compiler :grimacing: I don't really feel like supporting old GCC versions for no reason or debugging cmake python detection. I'll make a new image

They keep updating the devtoolset in the upstream manylinux... I think it
is in 10 now but that is not pinned. In any case, a moving target. The
manylinux image has all python versions installed under /opt/python. One
needs to be selected and added to the path.
I feel like at this point, gcc9 is as far back as we should go.
On Tue, Sep 21, 2021, 5:32 PM Geoffrey Martin-Noble <
@.***> wrote:

And with that approach we have a failure:
/usr/bin/g++    -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -w -fdiagnostics-color -ffunction-sections -fdata-sections -DC
XX_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR -fPIE   -Werror -Werror=global-constructors -std=c++14 -o CMakeFiles/cmTC_ee7d9.dir/src.cxx.o -c src.cxx
cc1plus: error: -Werror=global-constructors: no option -Wglobal-constructors
Apparently the image has gcc 7, whereas your manylinux image has gcc 9.
OTOH when I try to run with your manylinux image it's all upset about being
unable to find Python3, which we apparently need for the compiler 😬 I
don't really feel like supporting old GCC versions for no reason or
debugging cmake python detection. I'll make a new image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/iree/issues/6959#issuecomment-924487565, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADYVAADF6II36KZOZQX5ZDUDEPZJANCNFSM5DMDOBOA
.


TAJO-1479: NPE during startup AbstractMySQLMariaDBStore

I succeed to startup MySQLStore on my local cluster. For the reference, I fixed some typos about partition tables.

+1
ship it!

Thanks @jihoonson
I'll ship it soon. :)

@jihoonson
I've just fixed other typos for postgresql.
Could you check it again?

+1
The patch LGTM.


Backward compatibility for json layout without extension as data

Changelog Description
This PR is to add backward compatibility for json layout to avoid the error from the missing data of "extension" in the old published layout.
Additional review information
n/a.
Testing notes:

Launch Unreal
Load Layout with both old/new published layout
Should be working

@moonyuet I will test it now....just wait for a while with merge pls

and here is the JSON layout file...for you to check:
QD_sh010_layoutMain_v001.json.txt


Bug : editorNode.firstChild is not an HTMLElement

When i select the draftJS editor in Chrome, the following error  shows up in the console.  Firefox is working just fine.
https://youtu.be/cp8sbRX1tfo
Editor issues, and console log notification >
Uncaught Error: editorNode.firstChild is not an HTMLElement
i'm using a Meteor based infrastructure with
"draft-js": "^0.10.1",
"react": "^15.6.1",
"react-router": "^4.1.1",
node : 6.11.0
npm : 5.2.0
I'm loading the module on an empty page.
import React from 'react';
import ReactDOM from 'react-dom';
import {Editor, EditorState} from 'draft-js';

export default class MyEditor extends React.Component {
  constructor(props) {
    super(props);
    this.state = {editorState: EditorState.createEmpty()};
    this.onChange = (editorState) => this.setState({editorState});
  }
  render() {
    return (

        <Editor editorState={this.state.editorState} onChange={this.onChange} />

    )
  }
}

Solution to the above was removing an react create circle package. It was creating a conflict with draftJS somehow

Sounds good!

I am not using react create circle package still I am getting this error.


light blue and hover link blue are very similar

Is it worth having two very slightly different light blues? Or just have one?
@markhurrell

The :active state colour is the same as the :hover one.
https://github.com/alphagov/govuk_frontend_toolkit/blob/fbe3ce944b7ebd22e3e965d6f19265c4035354a3/stylesheets/_colours.scss#L94-L95

The colour change on hover is a good indicator that the cursor is in the right place. I think that is reason enough to have two blues, but they might benefit from being more different so the effect is clearer.

sorry, thats not what I meant - the link colour is "GDS blue" - clearly darker. "light blue" is the colour I'm referring to.

Ah, sorry, that makes more sense. Those two blues are almost the same, I agree there should be one colour.
$light-blue: #2b8cc4;
…
$link-active-colour: #2e8aca;
$link-hover-colour: #2e8aca;

:+1:

Is there a preference for either of these two blues?
We can either set $light-blue to be #2e8aca, removing #2b8cc4 or set $link-active-colour and $link-hover-colour to be $light-blue.

I think we should set $link-active-colour and $link-hover-colour to be $light-blue.

+1 to what @alextea says, as long as they have the same colour contrast

@markhurrell contrast to what?

@joelanman To the white background I'm guessing.

right - could be to the normal link or body text colours


allow starting variables with an underscore

This allows the named resources identifiers to start with an underscore
Mongo ids are useful as a named resource in a route, but they are usually named _id and are excluded by the current regex
If this isn't an acceptable change, then the documentation should imo be updated to specify what is an acceptable route identifier ([a-zA-Z][_a-zA-Z0-9]* currently)

Current coverage is 98.78% (diff: 100%)

Merging #1379 into master will not change coverage

@@             master      #1379   diff @@
==========================================
  Files            29         29
  Lines          6762       6762
  Methods           0          0
  Messages          0          0
  Branches       1123       1123
==========================================
  Hits           6680       6680
  Misses           38         38
  Partials         44         44

Powered by Codecov. Last update 4ff21c2...abfa1be

The change is good to me.
The idea is: route variable names should accept everything that is good for python variables themselves.
Thus I'm ok even with adding non-ascii names on first demand :)

Thanks

Thanks, and good to know for the non-ascii names. I'll have a go a that too if I ever need it
For reference, if anyone stumble here, python identifiers are:
identifier   ::=  xid_start xid_continue*
id_start     ::=  <all characters in general categories Lu, Ll, Lt, Lm, Lo, Nl, the underscore, and characters with the Other_ID_Start property>
id_continue  ::=  <all characters in id_start, plus characters in the categories Mn, Mc, Nd, Pc and others with the Other_ID_Continue property>
xid_start    ::=  <all characters in id_start whose NFKC normalization is in "id_start xid_continue*">
xid_continue ::=  <all characters in id_continue whose NFKC normalization is in "id_continue*">


Call for PyPI (pip) installation pre-release Test

Hi TensorBoard fans,
The PyPI TensorBoard is available in both macos and linux varients.
Just try
pip install tensorboard

We now support scalar, histogram and image and we're working on more types and even embedding later.
tensorboard-distro repo for PyPI version.
@piiswrong @kernel8liang @austingg @luoyetx could you please try this and give me some feedback? Thank you!

@zihaolucky Many thanks to the package. I test the package (install by pip) on CentOS7 and Ubuntu16.04 with Python2.7. It's pretty good. I also run the scripts under tests/python. They works fine. I take some images from tensorboard with logdir is experiment. I suppose the result is correct.
SCALARS

IMAGES

DISTRIBUTIONS

HISTOGRAMS

Thank you for your feedback! @luoyetx

Is there any plans to add windows support?

@ahmedezzateasa thanks for your feedback, I'm not familiar with this, is it possible to build PyPI installer in windows? @piiswrong @szha
@ahmedezzateasa BTW, have you try the installer.sh script? Does it work?

@zihaolucky  Thanks for your fast response.
I am not expert at building python packages for PyPI.
I am asking if there will be a python wheel for windows in the future (besides mac and linux)?
I am using mxnet on windows and I would like to use tensorboard with it (if it would be possible).
Previously, I tried building from source, but I stucked at bazel building for tensorboard (on windows) and I gave up.

on Windows, anaconda is usually used for installing python packages.

@austingg I am actually using anaconda. But, when a package is not found in conda, pip install works.

@ahmedezzateasa If the installer script works in windows, I think it might be possible to make a PyPI for windows. So I encourage you to fix the bazel issue and I'd love to help you, though I'm not a windows user.

@zihaolucky OK.
Thanks.

@ahmedezzateasa I guess the tensorflow/tensorboard works in windows, so technically the standalone version we provide could work. But I haven't tested the script in windows yet.

pip install tensorboard does not work for me on Mac OS
pip install tensorboard
Collecting tensorboard
Could not find a version that satisfies the requirement tensorboard (from versions: )
No matching distribution found for tensorboard

@an-kumar please tell me the version of your os, xcode and python.

uname -a:
Darwin 14.0.0 Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
xcodebuild -version:
Xcode 6.4
Build version 6E35b
python version:
2.7.11
also tried with python version:
3.6

@an-kumar Currently there are only versions for OSX10.11-10.12

Can you provide source code for this?  I am attempting to use this with the image_classification examples and I don't get graphs as one would expect.
I used the pypi to install tensorboard:

$pip freeze | grep tensorboard
tensorboard==1.0.0a6

I added/changed this to common/fit.py in image classification to get a dummy test running.
(FYI there is an error in the doc string for LogMetricsCallback, mx.tensorboard should be mx.contrib.tensorboard. lines)
    # starting around line 170 in image_classification/common/fit.py
    evaluation_log = 'logs/eval'
    training_log = 'logs/train'
    eval_end_callbacks = [mx.contrib.tensorboard.LogMetricsCallback(evaluation_log)]
    batch_end_callbacks += [mx.contrib.tensorboard.LogMetricsCallback(training_log)]
    # run
    model.fit(train,
        begin_epoch        = args.load_epoch if args.load_epoch else 0,
        num_epoch          = args.num_epochs,
        eval_data          = val,
        eval_metric        = eval_metrics,
        kvstore            = kv,
        optimizer          = args.optimizer,
        optimizer_params   = optimizer_params,
        initializer        = initializer,
        arg_params         = arg_params,
        aux_params         = aux_params,
        batch_end_callback = batch_end_callbacks, # This was updated
        eval_end_callback  = eval_end_callbacks, # This was added
        epoch_end_callback = checkpoint,
        allow_missing      = True,
        monitor            = monitor)

It appears that 'Step' is not being recorded properly.  Attached are some screen shots.

if you look at the relative graph it becomes more clear what's happening:

I am having issues.  Please see my comment on your PR.

i have successfully installed tensorboard, but when i run tensorboard.py.
:python tensorflow/tensorflow/tensorboard/tensorboard.py --logdir=path/to/log-directory
Traceback (most recent call last):
File "tensorflow/tensorflow/tensorboard/tensorboard.py", line 36, in
from tensorflow.tensorboard.plugins.text import text_plugin
ImportError: No module named text
no text module? can you help me to get it?

when can  i install on windows machine ?

Dear TensorBoard fans,
We're currently working with a member of the TensorBoard dev team, try to make this project more robust and maintainable, also trying to push the direction to a pure standalone tool. It might take some time.

"pip install tensorboard" dosn't work for me ? ubuntu 14.04 and python2.7
Downloading/unpacking tensorboard
Could not find any downloads that satisfy the requirement tensorboard
Cleaning up...
No distributions at all found for tensorboard


Added ability to access IOpipe object and use labels

I added a bit more to the example in that I added the use of our label feature, which requires accessing the IOpipe object from the context.

We do not but I will look into this (pardon any delay, I'm new to TypeScript)

Sounds good. If you have a pointer to the API docs for this it’s likely easy to add as part of finishing up the work on #4.


VPNGuard crashing my server

My PM hosting company VirtualGladiators just told me to stop using VPN Guard that it's crashing my server.

Don't use VPN Guard. It crashes your server. I've removed it:

Error: Call to a member function close() on null
File: /VPNGuard_v1.0.4.phar/src/basprohop/libraries/Async
Line: 53
Type: notice
THIS CRASH WAS CAUSED BY A PLUGIN
æ¤æ¬¡åºéç±æä»¶å¼èµ·
BAD PLUGIN : VPNGuard v1.0.4
Please fix this so I can start using it again.

Hi, I see your using an outdated version, try with the newer one https://github.com/HiddenMotives/VPNGuard/tree/master/releases also what server software are you using? And verify if your host allows connection to tools.xioax.com

Thanks, I'll give that a try.

Still getting crashes on my Virtual Gladiators server.
Genisys Crash Dump Wed Jun 15 20:25:55 MDT 2016
Error: Call to a member function close() on null
File: /VPNGuard-1.0.5.phar/src/basprohop/libraries/Async
Line: 53
Type: notice
THIS CRASH WAS CAUSED BY A PLUGIN

VG sent me this message when I opened a ticket with them for a unrelated issue.
Don't use VPN Guard. It crashes your server. I've removed it:
VPNGuard is kind of a pain. If you don't buy their subscription, the server will either not start up or crash because of the limitations they have programmed into the plugin. With SimpleAuth or similar program, there should be no need for VPNGuard. We have hundreds of people running Pocketmine servers and very few use VPNGuard.

Hi, I would like to point out couple things, this particular version of VPNGuard has been developed for PocketMine and was not specifically created for it's forks.
Secondly, although your specific error is an easy fix (i will push an update out to address the null pointer issue), it seems that your host is disallowing connections to the API server, or that your host's IP address has been previously blacklisted https://github.com/HiddenMotives/VPNGuard/blob/master/src/basprohop/libraries/Async.php#L53 there is a definite connection error from your VG server to the API server.
And as to address your hosts response, you can't have client sided limitations, as they can be removed. Which I assume they are referring to https://github.com/HiddenMotives/VPNGuard/blob/master/src/basprohop/libraries/Async.php#L112

Thanks

Just wondering when you will push out the update you mentioned above.
Thanks

I would Ideally like to bundle the update with couple of the other changes im working on, so it could take a couple

Sounds good thanks

Just curious when you will be releasing an update?

I know its been awhile but the release date is still unknown, just stay tuned

Is there going to be an update to VPNGuard to take advantage of XIOAX's new Professional tier?
Maybe support for IP Geo Location with the ability to filter countries?

Of course country or city whitelist / blacklist  . Ability to lookup IP address or Player in-game etc.

Great, I'm looking forward to the updates.


add F-P link to GO:0008897 holo-[acyl-carrier-protein] synthase activity -> GO:0042967 acyl-carrier-protein biosynthetic process

GO:0042967 acyl-carrier-protein biosynthetic process
has no annotations, but it would if the F-P link
GO:0008897 holo-[acyl-carrier-protein] synthase activity -> GO:0042967 acyl-carrier-protein biosynthetic process
was added.

The enzyme activity is defined as the bidirectional in the ontology. Does it ever go in both directions? If we don't know, we would make a has_part and it would still require co-annotation. Otherwise we would have to change the definition to make it only one direction.

Hi David,
This one isn't urgent for me (not matrix). I just saw it as I spotted other stuff, and thought it would be a quick way  to improve annotation.
However, at the moment it wouldn't because at least PomBase and SGD have the fatty acid synthase annotated to the "acyl carrier synthase" terms.
I'll take this ticket and come back to it later when the primary annotations have been checked.


Add test cases for inservice upgrade using rancher-compose

@alena1108 , can you review?

@sangeethah we have to exercise different values for batchSize/interval parameters. Just pass them with random values in several tests.

@alena1108 , I am now passing different values for batchSize/interval parameters to upgrade command in existing test cases.

LGTM


Fix authentication on IP change

This fixes #68
The problem was the the AuthInfoMap stores an AuthInfo for a server's InetSocketAddress. Unfortunately, the InetSocketAddress hash is based on the resolved IP which can change. For this reason I changed the AuthInfoMap to store the AuthInfo based on the servers (hostname:port) string.
Note, I tried to fix this problem without changing any public interface but I don't like it. I could also change the MemcachedClient.getAuthInfoMap() from public Map<InetSocketAddress, AuthInfo> getAuthInfoMap(); to public Map<String, AuthInfo> getAuthInfoMap(); instead. This would be a bit nicer but change the interface. What do you think?
Review by commit. The first commit only removes trailing whitespaces. The code changes are all in the second commit.

Thank you!

@killme2008 Is it possible to make a release to the Maven repo of version 2.4.3 containing this fix?

@killme2008 Thanks a lot!

@saschat
I released 2.4.3, it may take sometime to be synced into maven central repository.
https://github.com/killme2008/xmemcached/releases/tag/xmemcached-2.4.3


Theres a way to watch/reload changes made over the template file ("html-webpack-plugin")

Hi!
There's only one thing I can't achieve right, and that's refresh the browser every time there is a change in the "index.html" template. Seems that Webpack plays well for the files defined in the "entry" property but not for this "index.html" template file outside the entry ones. Here is an extract from my config file:
var pluginHtml = require('html-webpack-plugin');

...
  plugins:[
    new pluginHtml({
      title: 'Angular Starter',
      template: './src/index.html'
    })
  ]

Thanks in advance!

Maybe webpack-service would work for this purpose.

This issue belongs at the html-webpack-plugin issue tracker. It doesn't reload your page because the current version doesn't use webpack's loaders. At the moment there is a PR that fixes this issue.

Closing. Please track https://github.com/ampedandwired/html-webpack-plugin/pull/41 .


Uncaught ReferenceError: proxy is not defined

The most recent commit seems to break things in Chrome:

The version before this commit (i.e. https://rawcdn.githack.com/flackr/scroll-timeline/9c04dfcd4a9038f3659cae7af0d95c98e7bd17b6/dist/scroll-timeline.js) does not have this issue.

Investigating.

Didn't have time myself to investigate, so thanks for this very fast intervention.


refactor(v2): change the label for docs introduction

Motivation
Rename the docs sidebar label, for me sounds weird the route docs/docs in  docs introduction

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
go to /docs/docs
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

This doesn't change the path though, it's still v2.docusaurus.io/docs/docs

@yangshun see https://deploy-preview-2716--docusaurus-2.netlify.app/docs/next/docs-introduction

My bad, of course it wouldn't show, I was looking at the stable version.


Adding a cask for Grisbi

I don't know if I was suppose to present it checking boxes in the template but here it is ;)
Adding a new cask

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

@vitorgalvao Done, you were right.

Thank you for the contribution. It needed some fixes, so they were made in f6a7fcf74b3c198612d371602fa5b125ef4d9f38. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Revert "Fix ReorderableListView's use of child keys (#41334)"

Reverts flutter/flutter#41338
This PR causes the reorderable demo in the Flutter Gallery to fail; see comment thread in #41338.

LGTM
CC @darrenaustin


Upgrade to net5.0

Description

Add net5.0 support
Upgrade System.CommandLine to v2
Fix integration tests

Checklist

[x] All tests are passing
[x] New tests were created to address changes in pr (and tests are passing)
[x] Updated README and/or documentation, if necessary

Hi Eddie! Hope you're doing well. What's your current plans for certes?

Hey @webprofusion-chrisc , working on to fix the CI test/deployment, and will see what is needed next.
Apologize for my negligence, the CLI has been served me well so far, but I think it’s time to do some refresh now. :blush:

@fszlin no problem, I maintain quite a few projects and I know sometimes other things have to take priority and also sometimes you just won't feel like working on a particular project. It's nice to see you picking it up again.


Build TF wheel in another project which depends on TF

System information

OS Platform and Distribution: (Linux Ubuntu 20.04)
TensorFlow installed from (source or binary): source
TensorFlow version: 2.8.0
Python version: 3.8.0
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source): 4.2.1
GCC/Compiler version (if compiling from source): gcc version 9.4.0
CUDA/cuDNN version: CUDA 11.2/ cuDNN 8
GPU model and memory: V100

Describe the problem
I have a bazel project which depends on org_tensorflow.  My project's .bazelrc is copied from TF project
In my project, I can successfully build TF build_pip_package target by:
bazel build --config=native_arch_linux --config=cuda @org_tensorflow//tensorflow/tools/pip_package:build_pip_package

However, the following error occurs when generating the wheel
./bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

Wed Apr 6 10:41:47 CST 2022 : === Preparing sources in dir: /tmp/tmp.C0MooMsKIF
Could not find bazel-bin.  Did you run from the root of the build tree?

The prompt is very intuitive. I also checked ./bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package
The script assumes that TF is not an external dependency.
In this situation. How can I generate the TF wheel?
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel build --config=native_arch_linux --config=cuda @org_tensorflow//tensorflow/tools/pip_package:build_pip_package

./bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

Hello @372046933 ,
It seems there is no symlink for bazel-bin being created.The idea is to create the bazel-bin symlink is that the TensorFlow build_pip_package script expects to exist.
Can you try manually creating it and copying all files from users/XXXXXXXXXXXXXXXXXX/org_tensorflow/bazel-out/x64_windows-opt/bin/tensorflow/tools/pip_package/build_pip_package.exe into \tmp\tensorflow\bazel-bin
If that doesn't work, can you please try building on a different directory, not C:\tmp. Most of times tmp is mismanaged.
If possible, move your workspace to a filesystem that supports symlinks and re-run bazel build there.

@tilakrayal  Thanks. The reason for no bazel-bin is that I am building TF as an external dependency. By the way, I'm building on Linux. C:\tmp does not exist.

The key output of bazel build --config=native_arch_linux --config=cuda @org_tensorflow//tensorflow/tools/pip_package:build_pip_package:
INFO: Found 1 target...
Target @org_tensorflow//tensorflow/tools/pip_package:build_pip_package up-to-date:
  bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package
INFO: Elapsed time: 211.970s, Critical Path: 98.34s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action

@372046933 ,
Could you please confirm if the installation issue is resolved? Thanks!

@tilakrayal No, it's not resolved. Cannot execute
./bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

@372046933,
Bazel wasn't able to create the symlinks for bazel-bin, try workaround bazel build --symlink_prefix=/ when you run Bazel. This will tell Bazel to not create the symlink so it will hopefully work. Thanks!

@gadagashwini  Added --symlink_prefix=/ to bazel build. But nothing changed. My build command is
bazel build --config=native_arch_linux --config=cuda  --symlink_prefix=/ @org_tensorflow//tensorflow/tools/pip_package:build_pip_package

By the way, did you notice that I am building TF as an external dependency. i.e. @org_tensorflow//tensorflow/tools/pip_package:build_pip_package  not //tensorflow/tools/pip_package:build_pip_package

@372046933,
Can you try the workaround mention on similar thread #21461.Let us know if that helps. Thanks!

@372046933, Once you build the Tensorflow wheel. you need to install the wheel package with pip.
bazel build [--config=option] //tensorflow/tools/pip_package:build_pip_package

./bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

pip install /tmp/tensorflow_pkg/tensorflow-version-tags.whl

@gadagashwini . Yes, here is what I executed:
./bazel-bin/external/org_tensorflow/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg

The following error occurred
Wed Apr 6 10:41:47 CST 2022 : === Preparing sources in dir: /tmp/tmp.C0MooMsKIF
Could not find bazel-bin.  Did you run from the root of the build tree?

Do you have a minimal example of your repo and how are you referring to TF's wheel?
You'll need a bazel genrule that would depend on the build_pip_package target and then builds the wheel. Use this as the base rule in your repo

If you are building a target from an external repo you have to use @ syntax.
I think this is more and more becoming an issue for Bazel, not TF. There's no breakage that can be root caused to TF itself.

Did we come to a conclusion that it's not possible to build TF wheel in an external repo currently?

No, it is possible to build it. See recommendation in https://github.com/tensorflow/tensorflow/issues/55505#issuecomment-1112731813

Could you give an example? Found that genrule does not have deps attribute. I did not know how to  depend on build_pip_package and then build a wheel

Yes, genrule does not have deps but has tools which is the list of deps needed to run the genrule.
Try something like
genrule(
    name = "tf_wheel",
    outs = ["tensorflow.whl"],
    cmd = "$(location build_pip_package) >$@",
    tools = ["@org_tensorflow//tensorflow/tools/pip_package:build_pip_package"],
)

Seems that @org_tensorflow//tensorflow/tools/pip_package:build_pip_package is not visible from external project.
ERROR: /xxx/yyy/BUILD:330:8: in genrule rule //:tf_wheel: target '@org_tensorflow//tensorflow/tools/pip_package:build_pip_package' is not visible from target '//:tf_wheel'. Check the visibility declaration of the former target if you think the dependency is legitimate
ERROR: Analysis of target '//:tf_wheel' failed; build aborted: Analysis of target '//:tf_wheel' failed

Will send a patch to make it visible

Can you try now, after syncing to the above commit?

Copy genrule from  the above comment. https://github.com/tensorflow/tensorflow/issues/55505#issuecomment-1114333283
Build results in the following error.
ERROR: /xxx/yyy/BUILD:330:8: in cmd attribute of genrule rule //:tf_wheel: label '//:build_pip_package' in $(location) expression is not a declared prerequisite of this rule
ERROR: /xxx/yyy/BUILD:330:8: Analysis of target '//:tf_wheel' failed
ERROR: Analysis of target '//:tf_wheel' failed; build aborted:

You shouldn't have //:build_pip_package anywhere in your code.

My workspace does not have build_pip_package target.
genrule:
genrule(
    name = "tf_wheel",
    outs = ["tensorflow.whl"],
    cmd = "$(location build_pip_package) >$@",
    tools = ["@org_tensorflow//tensorflow/tools/pip_package:build_pip_package"],
)

Build command:
bazel build --config=native_arch_linux --config=cuda :tf_wheel

I didn't understand the following error message
ERROR: /xxx/yyy/BUILD:330:8: in cmd attribute of genrule rule //:tf_wheel: label '//:build_pip_package' in $(location) expression is not a declared prerequisite of this rule

I think this might be a Bazel bug, not TF. So, maybe try to simplify all of this and open a bug on Bazel repo, as they might have much more context.
Or, let's step a step back. Why do you want to build the wheel from within Bazel?

Why do you want to build the wheel from within Bazel?

Did you mean build the wheel within TF? Because I did build the wheel with bazel. When it comes to why I build TF wheel outside of TF repository, because my project directly depends on org_tensorflow. If TF wheel can be build inside my project. It's more convenient.

Unassigning since as of this week I no longer work within TF.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


disconnect from APRS server if connection hangs

Previously a hanging TCP connection (i.e. on an intermittent network) would cause the APRS client to hang indefinitely. Now, it'll disconnect after a minute of hearing nothing. The APRS-IS servers send heartbeats regularly so this shouldn't cause any false disconnects

Looks good. Can you bump the version to 0.3.2 and then I'll merge and release.

Done!


HMR does not run application entry point when using setStatefulModules()

I'm customizing HMR like this:
import {setStatefulModules} from "fuse-box/modules/fuse-hmr"

setStatefulModules(moduleName => {
    // I'd like to specify it like this, but it does not seem to work. The module is reloaded,
    // but the main path is not executed.
    // return !/view/.test(moduleName)

    // Instead we have to list all stateful components explicitly (only stores for now)
    return /store/.test(moduleName)
})

I'd like to treat all modules except my views as stateful. So I'd like to use the commented away, negative condition. But when I use that, the module is replaced just fine upon HMR, but the main path is never executed. Hence nothing is updated.

@koffmoff
Please check this module here
It might be easier to implement your own HMR logic which is described here this

Thanks for the hint. Looking at the code was helpful. The default implementation flushes all non stateful modules and since my main module (index.tsx) was considered stateful, it wasn't flushed, and thus not executed again when reloaded.
This did it:
setStatefulModules(moduleName => {
    return !/view|index/.test(moduleName)
})


fixes for changes feed

+1

@sreeix please not remove your sreeix-cradle from npm, because I'm using this in production.
Thanks

All: I've updated Cradle to use the changes library from IrisCouch: follow.
It will go live in<EMAIL_ADDRESS>which I hope to have out tonight.


"validateResponse: true" returns unexpected 400

import { Hono } from "hono";
import { describeRoute } from "hono-openapi";
import z from "zod";
import { resolver } from "hono-openapi/zod";

// For extending the Zod schema with OpenAPI properties
import "zod-openapi/extend";

const ProjectSchema = z.object({
  id: z.string(),
}).openapi({ ref: "Project" });

export const projectsRoutes = new Hono().get(
  "/:id",
  describeRoute({
    validateResponse: true,
    description: "Get a project by id",
    responses: {
      "200": {
        description: "Project found",
        content: {
          "application/json": {
            schema: resolver(ProjectSchema),
          },
        },
      },
    },
  }),
  (c) => {
    const { id } = c.req.param();
    return c.json({ id });
  },
);

export type ProjectsRoutes = typeof projectsRoutes;

Test code:
import { expect } from "@std/expect";
import { testingRPC } from "../../../testing/testingRPC.ts";
import { projectsRoutes } from "./routes.ts";
import { testClient } from 'hono/testing'

Deno.test("Projects Routes", async (t) => {
  const client = testClient<typeof projectRoutes>(projectsRoutes);

  await t.step("GET /:id", async (t) => {
    await t.step("returns a project when given a valid ID", async () => {
      const id = "123";
      const res = await client[":id"].$get({
        param: {
          id,
        },
      });

      const data = await res.json();
      expect(res.status).toEqual(200);
      expect(data).toEqual({ id });
    });
  });
});

Running deno test --allow-all --no-check, the response is:
{
  res: Response {
    body: ReadableStream { locked: false },
    bodyUsed: false,
    headers: Headers { "content-type": "text/plain;charset=UTF-8" },
    ok: false,
    redirected: false,
    status: 400,
    statusText: "",
    url: ""
  }
}

As a side question: are there any plans to add TypeScript enforcement on c.json / c.text responses to ensure the correct payload is being specified?

As a side question: are there any plans to add TypeScript enforcement on c.json / c.text responses to ensure the correct payload is being specified?

I'm not sure how we can do that in hono; if you have any ideas, let me know.


Twipsies for IE doesn't hide default tooltips

As the title says. I'm using IE9 and when i hover any twipsy-enabled link
it shows the twipsy, and also shows the default tooltip overlapping the twipsy tooltip.

It's fixed for me now. Issue closed.

How did you solve it? I have the same problem

I'm not really sure what, but I think "it will" by default, it just needs to completely load the plug-in for some time.


Bump nixpkgs to 94035b482

This bumps us to Arrow 16.0.0 and spdlog 3.9.1.

@tobim looks like your nushell script broke with an update.


Merge PerceptionErrorCode to common ErrorCode

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

@ycool


isAsyncModeSupported false for AbstractSelectForUpdateBasedProxyManager

Hello,
I notice that AbstractSelectForUpdateBasedProxyManager.isAsyncModeSupported returns false for MySQLSelectForUpdateBasedProxyManager. Am I missing something? Does this mean that I cannot consume tokens asynchronously if I'm using MySQL as the persistent bucket store?

Hello @amin2718
Async mode is not supported for MySQL because JDBC does not provide asynchronous functionality.

Thanks for the explanation. One thing I noticed about the API is that tryConsume returns a boolean, whereas consumeIgnoringRateLimits returns an additional piece of information, which is the amount of rate limit violation.
If tryConsume did the same thing: return a 0 if consumption was successful, and > 0 to describe the amount of violation that would have occurred, it would be quite useful for building a distributed rate limiter where high accuracy is not needed. The reason is because we can store the nanoseconds locally and automatically deny requests for a period without making any remote request.
There are many cases where the tradeoff is quite acceptable. Is such a thing possible with the current API?

There is "tryConsumeAndReturnRemaining" for such cases. This method return ConsumptionProbe object that in case of reject provides time in nanos which need to wait until requested amount of tokens will be refilled via getNanosToWaitForRefill method.

Thank you, I hadn't seen that. Thank you for your time and help.


Fix Plugin Config Daemon node selector

When node selectors are added via "configDaemonNodeSelector" via the sriovoperatorconfigs CRD then completely removed, the previous node selectors would remain for the plugin config daemons (sriov-device-plugin). This was not cleaned up, because the function "syncPluginDaemonSet" bails out when "configDaemonNodeSelector" is empty. For example:
Step 1) Create 3 labels in node selector:
configDaemonNodeSelector = {"labelA": "", "labelB": "", "labelC": ""} device-plugin DS NodeSelector = {"labelA": "", "labelB": "", "labelC": ""}
Step 2) Remove all labels in node selector:
configDaemonNodeSelector = {}
device-plugin DS NodeSelector = {"labelA": "", "labelB": "", "labelC": ""}

The expectation is that the device plugin will revert to the default node selectors (e.g. {"node-role.kubernetes.io/worker": "", "kubernetes.io/os": "linux"})
This change will make sure that the default values are taken from the rendered plugin daemonset when "configDaemonNodeSelector" is empty.

/cc @SchSeba
/cc @zeeke
/cc @e0ne
/cc @adrianchiris
/cc @zshi-redhat

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 44 (2.27%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 24.39%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

controllers/sriovnetworknodepolicy_controller.go
0
1
0.0%

controllers/helper.go
0
7
0.0%

controllers/sriovoperatorconfig_controller.go
1
36
2.78%

Files with Coverage Reduction
New Missed Lines
%

controllers/sriovibnetwork_controller.go
2
64.15%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
2080

Relevant Lines:
8528

💛  - Coveralls

@bn222

@adrianchiris @e0ne  Please take a look when you have a chance. Thanks!

Hi @adrianchiris,
by default the config-daemon have node selector on workers you can check in the bin/data folder


[MINOR][DOC] Fix a typo in ResolveReferencesInUpdate scaladoc

What changes were proposed in this pull request?
Fixed a typo in the ResolveReferencesInUpdate documentation.
Why are the changes needed?
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI

@srowen FYI

It's fine, just see if rerunning tests succeeds

@sdruzkin enable github action on yours fork https://github.com/apache/spark/pull/42322/checks?check_run_id=15597116732

Tests are green.

Merged to master/3.5


core: Add item testing

This is a step towards achieving #2280 and related issues. It adds two functions that bridge authors can override:

getTestParameters: This should return a list of inputs to be tested on the bridge. By default returns default values of each context.
checkItems: This function checks if bridge items are valid. Currently, the default is just to check that any items exist, but we can make this more strict, for example testing that items exist AND they all have titles.

These functions are accessible through the ConnectivityAction when check_items is passed.
Things to do:

[ ] Document all of this
[ ] Add this the javascript UI. For now, it can be accessed through the same way (passing check_items), but in future PRs, this UI can be improved to allow the user/instance maintainer to select a subset of bridges to test.
[ ] Future PRs can work on implementing these functions for each bridge
[ ] Please review and/or test this if you can :)

Don't do this. Bridges are complex enough. The responsibility of testing should not be container inside bridges.


[SD] Add cli option to web

With this we can ideally start phasing out the duplication of code between the web and cli versions.

@qedawkins This is a good idea. It needs few more updates in main.py as web main script does not include profiling and debugging stuff as of now.
I am working on refactoring of main.py in some better way to get rid of this duplication, but this can be a good temp solution with other changes as specified.

Sure, if your refactor handles this then I can close this PR. Just wanted to push along the consolidation effort.

Closing this one as this is handled here #694.


Performance cops moving to own gem

Per  rubocop PR #6890, performance cops will be moved to the rubocop-performance gem.
Analysis is currently breaking due to this change:
/usr/local/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:122:in `require': cannot load such file -- rubocop-performance (LoadError)

@agirling I think your configuration is using the stable channel of our RuboCop plugin, which is runs RuboCop 0.52.1, so the performance cops are still built-in. I suspect you added a require: rubocop-performance to your .rubocop.yml, but you don't need that for Code Climate and it's inclusion is causing the problem. I'd suggest removing that from your .rubocop.yml for now.
RuboCop only just made this change, and haven't released a version including this change yet. When we release a new channel of our plugin for that eventual RuboCop version we'll include the new rubocop-performance gem in the build and then it'll be available if you switch to that channel after it's released.

@wfleming spot on, I did add the require to my .rubocop.yml.  I'll remove that for the time being.  Thank you for the background and detail.

Closing for now since this doesn't impact any currently released versions of our plugin. It'll come up when we need to release a new channel for a later rubocop release.

I'm getting the same issue, now that rubocop 0.68 was released, any news on this ?

We haven't released a channel supporting 0.68 yet (when we do #167 would be the issue to watch).
We do have a channel for 0.67 (see #164), and that channel does support the gem, so you could use that in the meantime.

Any updates on this?

Can we get an update on this, please? @wfleming

gem install rubocop-performance?

What about for later versions like 1-19 and 1-18-3?


station: init at 1.51.1

Motivation for this change
This PR adds station package.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

@mmahut station has been updated to 1.51.1 recently. Should I update this PR before merge or open another PR after merge?

i would just update this pr, you can also edit the title

Updated to 1.51.1.

What is the state of this PR? I've been using station at work without any problems. Is there anything I can do?


port to VS Code?

Hi @troydraws - Atrium is my favorite Atom theme of all time - just beautiful and so readable and easy on the eyes. I use Atom mostly, but do use VS Code for some things that it does better. I wondered if you would have any interest in porting Atrium to VS Code, or if not, would object to my doing so (giving you full credit for the design, of course).

Hello Rob - glad that you liked Atrium!  Similar to atrium it’s a dark theme based off warm earthy tones. I’ll let you know when I am happy enough with it!

Fantastic! Thanks.

Fantastic! Thanks.

Hi Robert, Just published the VS theme here: https://marketplace.visualstudio.com/items?itemName=yile-ou.paddy-color-theme
Atrium is a lot lower in contrast in comparison - I might add a medium grey version to Paddy some time later. I find a higher contrast easier to read. The general colour schema is pretty much a successor of Atrium though :) Hope you like it. Suggestions welcome!
I've used italics quite a bit here and there as I find the italics of IBM Plex Mono pretty enjoyable.
If you strongly prefer Atrium feel free to port it to VS Code yourself, no issues there! 😄
Yile


[common]: fix duplicated init container

What this PR does:
According to sprig documentation, our merge was used wrong way.
Sprig documentation: https://github.com/Masterminds/sprig/blob/master/docs/dicts.md#merge-mustmerge
Which issue this PR fixes
With this merge, we fix issues resulting from InitContainer being merged into Containers (ie. InitContainers appear twice)
fixes #123
Notes for Reviewer:
Checklist:

[ ] Pull Request title in format [chart]: Changed Something
[ ] Updated documentation in the  README.md.gotmpl file and executed helm-docs
[ ] Chart Version bumped
[ ] All commits are signed-off

Sign-off missing


fix: add generics for cursor method

Thanks!

Thank you.
Maybe we could have a test for each method.

Thank you.


[CWS] fix CWS related errors in markdown link check job

What does this PR do?
For some reasons this job started failing on CWS links. This PR fixes those.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Provide possibility to specify codec (lossless cut)

Hi,
I would like to be able to cut video (using ConvertAsync) but with lossless codec (-codec copy).
I know I can use prepare the full, custom path and call ExecuteAsync but it would be nice ConvertAsync also supports custom parameters (or at least codec specification).  Or maybe it is possible already somehow?
greetings
Bartek

Hello,
A little add to the FFmpegArgumentBuilder.cs could be :
if (conversionOptions.BaselineProfile)
commandBuilder.Append(" -profile:v baseline ");
if (conversionOptions.CopyVideo)
commandBuilder.Append(" -c copy ");
In order to switch between 2 modes  : .BaselineProfile or .CopyVideo
Thanks for your work, I love and use SVC !

I added some parameters in ConversionOptions. For this case use VideoCodec parameter that sets the Encoder to be used
This should be available when #42 pull request is accepted

PR has been merged


Update README.md

Added steps to clone partial repo (aka modern dir only)

This is not really a necessary part to run the web app, so I don't want to overcomplicate readme doc with it.

This is not really a necessary part to run the web app, so I don't want to overcomplicate readme doc with it.

I do understand your point. Just wanted to let as much people able to test it including the not so technical abble. since this is the development dir it could be replaced with the proper readme when pushed as release.

Yeah, but even with development I don't really see any good reason for it. What problem does it solve?

None whatsoever,
Your looking at it from programming perspective and then yes it has no value. But to help a user it allows quick testing which in turn adds to feedback and bug reporting.
Like myself for example I consider myself in between programmer/user. It took me a while to figure this out, I don't work daily with git etc.
Now i have it running i can add basic options to the template. and contribute even though it's a little.
I get your point though leaving it up to you ofc.

Why do you want to partially clone repo instead of full repo? I still don't understand it.


Add PrestoQueryRunner Document

@mbasmanova @kgpai Could you please help to review this PrestoQueryRunner doc?

@kgpai Hi Krishna, thanks for your review, I've resolved all the comments except for this one, I may not get your point precisely. Could you help take another look?

maybe we can provide which to use as source of truth / Duckdb or Presto .

I added this note to highlight that Presto would be the only source of truth, and DuckDB would be removed, according to this comment (https://github.com/facebookincubator/velox/pull/7628#discussion_r1400563473) of the PrestoQueryRunner PR.


Cells_V in CAN publication message

https://github.com/LibreSolar/bms-firmware/blob/be7f58af9ec26121123eeffc57ef76564c7741cf/src/data_nodes.cpp#L211-L212
What would be the better solution to publish the individual cell voltages over CAN

create a DataObject for every cell voltage
create a CBOR array with all voltages (one array is implemented in text mode) and expand the publication message for multi frame messages?

This is a very good question.
Don't really like to generate a dedicated DataObject for each cell voltage, as the objects are created at compile time and a BMS should be able to detect the actual number of cells at runtime. So the array is much cleaner in my opinion.
However, 8 bytes for classic CAN is definitely too small for up to 15 voltages, no matter how good the compression of the data is...
A previous version of the ThingSet spec had something called TinyTP for splitting longer publication messages. But it was never actually implemented, so I abandoned it to make the protocol not too complex.
At the moment the only good option to retrieve the cell voltages via CAN would be polling. With request/response messaging the maximum message size is 4095 bytes, which should be plenty.

I will consider polling over ISO-TP also. At the moment i am not mastering ISO-TP at all. But that could be a solution. The goal for the next year is, to replace an existing logging facility from volkszaehler-OBIS-messages (over isolated UART) to CAN, because one CAN could serve all chargers/bms at once. To use publication messages would be more straight forward because the host computer needs to listen only, and there could be multiple listeners for redundancy. Maybe thats a subject for [(https://learn.libre.solar/system/)], because it adresses not the component but the whole system.

Yeah, makes sense to use CAN for that. If you're familiar with the ESP32: Quite a bit of that functionality is already implemented in https://github.com/LibreSolar/esp32-edge-firmware, including ISO-TP implementation and a web interface running on the ESP32 itself. It even supports over-the-air firmware upgrades for some STM32 microcontrollers.
I'm currently using it to push data to an MQTT broker, store it in an InfluxDB or VictoriaMetrics database and visualize it with Grafana.
It will need a bit more documentation, though.

This is a proposal for binaray data node Cells_V which does not break current implementation, CBOR-conform and fits in 8 Byte payload of CAN:

NodeID 0x80 is  kept
every cell voltage is published at the same NodeID
data payload is a CBOR-array with two entries:

Byte 0: Mayor type CBOR-List, two elements (0x82)
Byte 1: Mayor type unsigend integer (cell number)
Byte 2..6: Mayor type float (cell voltage)

The complete CAN telegram for Cell 2, Voltage 3.502V, Cell 3, Voltage 4.00V would look like:
can0  1F00800A  [7]  82 02 FA 40 60 2E 9A
can0  1F00800A [7]  82 03 FA 40 80 00 00]

Decoded payload with cbor2.loads():
[2, 3.5028443336486816]
[3, 4.0]

It should be possible to calculate number of cells at runtime, and should be easy to implement at controller side.

Mhh, I think this would kind of break the current implementation, as the data representation would be different depending on whether the ThingSet library is fed with a request in text mode or in binary mode. Or the data would have to be generated outside the ThingSet library and just for this particular CAN message, which is also not ideal.
I think such a problem has to be solved on a lower layer of the protocol stack, i.e. the transport layer. As ISO-TP is not suitable for broadcasting, one solution would be to get back above mentioned TinyTP and create a dedicated CAN ID for multi-frame publications.
Previously the DP and EDP bits (25 and 24) were chosen to avoid ID conflicts with SAE-J1939. However, the ThingSet bitrate is set to 500 kbit/s instead of 250 kbit/s, so both protocols can't run on the same bus anyway. So we might just want to use bit 25 set to 0 for multi-frame publication messages and use bits 8-23 of the ID for packet numbers etc..
What do you think?

So we might just want to use bit 25 set to 0 for multi-frame publication messages and use bits 8-23 of the ID for packet numbers etc..

If we use Bit 8-23 for packet number, we need to set the NodeId inside the payload? So we will need a CBOR-array which consists of: [ NodeID, data_value0, data_value1, data value2, ....]. Number of data_values is (CBOR_array_length -1)?

Are there any current developments underway?

Yes, there are :)
We have recently added a new packetized report format to the spec and to the implementation. See the pull requests below for further information:
https://github.com/ThingSet/thingset.github.io/pull/24
https://github.com/ThingSet/thingset-zephyr-sdk/pull/4
It's just a matter of updating to a new ThingSet SDK revision in west.yml to pull that into the BMS code.

@martinjaeger, https://github.com/LibreSolar/bms-firmware/pull/37 pulls your mentioned changes from thingset-zephyr-sdk,  so I think this issue is resolved?

Yes, true. We can close this issue.


Improper behaviour when saving/restoring Strings with LV2:State interface

When trying to store multiple strings:
/scene/object/4/material/sound_speed
/scene/object/4/material/transparency/inner
/scene/object/4/material/dissipation/inner
/scene/object/4/material/dispersion/inner
/scene/object/4/material/absorption/inner

with same key: "http://lsp-plug.in/kvt#keys" we get the following result:
        state:state [
                <http://lsp-plug.in/kvt#keys> "/scene/object/4/material/sound_speed" ,
                        "/scene/object/4/material/transparency/inner" ,
                        "/scene/object/4/material/dissipation/inner" ,
                        "/scene/object/4/material/dispersion/inner" ,
                        "/scene/object/4/material/absorption/inner";
        ]

When reading LV2 state, we get only one random parameter, all other string parts are omitted:
[TRC][/home/vsadovnikov/eclipse/lsp-plugins/include/container/lv2/extensions.h: 569] retrieve_value: retrieve(57 (http://lsp-plug.in/kvt#keys))
[TRC][/home/vsadovnikov/eclipse/lsp-plugins/include/container/lv2/extensions.h: 571] retrieve_value: retrieved ptr = 0x9a959c0, size=44, type=41, flags=0x3
Received KVT key set:
00000000: 2f 73 63 65 6e 65 2f 6f 62 6a 65 63 74 2f 32 2f    /scene/object/2/
00000010: 6d 61 74 65 72 69 61 6c 2f 74 72 61 6e 73 70 61    material/transpa
00000020: 72 65 6e 63 79 2f 6f 75 74 65 72 00                rency/outer.

There is currently no way to fetch all the strings with same key while the LV2:State interface allows to store multiple values associated with the same key.

The short answer, I'm afraid, is: don't do that.  While you can have several values for a single property in RDF in general (as you do here), it generally makes everything massively more of a pain to work with (such as anything with a getter like this), so for the most part we just don't in LV2 things.  People tend to get confused about "order" (which is not a thing) when this is present as well.  Even if the interface supported it, I wouldn't recommend doing it.
The solution/workaround is to use a list.

Is there any way to protect host from such usage? For example, to ignore the second and more values and to write the proper message to stderr?

It could return an error if the key is already set, I suppose.
There's only really 3 options that I can see:

Write them all, only allow access to one (as a consequence of the state API, current behaviour).
Write the first, return error on any other store calls that attempt to write it again.
Overwrite the current value (act like a setter).

1 is pretty crap, either of 2 or 3 seem reasonable.  2 seems least confusing, though is a bit more limiting than 3.

I think 2 is the best option.

6d09956


[3.5.rc6] Viewport HDR Warning can't go away when rendering usage is set to 2D

Godot version
3.5.rc6
System information
Windows
Issue description
Setting the Viewport rendering usage to 2D or 2D Without Sampling generates a Warning about HDR being used but ignored, although HDR is disabled in the project settings (Rendering Depth HDR is off). Can't get rid of that warning. The 2D buffer usage is desired as it is the best speed/space tradeoff for 2D games without advanced effects.
Steps to reproduce
Create a scene tree and add a Viewport node. Change its usage to 2D or 2D Without Sampling

Minimal reproduction project
Viewport_HDR_Warning.zip

The HDR project setting only affects the root viewport if I'm not mistaken. However, if the root viewport doesn't use HDR, then I suppose enabling HDR in subviewports is useless in most situations.

While I agree with this, the question about HDR being used selectively in viewports remains debatable. We don’t use it, but people might.
The problem here is more that the HDR setting is not exported in the side panel interface of the editor in order to be able to shut the (legitimate) warning. So the easy way out is to export that property together with the buffer usage in the side panel without entering the HDR usage debate across viewports.

The other thing that makes sense is to make all viewports follow the HDR setting of the root viewport at init time. Thus by adjusting the HDR in the projet settings one forgets about configuring other viewports, unless it is done by script explicitly. This is orthogonal to the idea of exposing the HDR setting in the editor. In any case this warning is annoying both ways :-)

The other thing that makes sense is to make all viewports follow the HDR setting of the root viewport at init time.

Unfortunately, doing so will waste memory and decrease performance in a lot of scenarios.

OK this is fixed in 3.5.1.rc1 by (https://github.com/godotengine/godot/pull/65063)


SAK-29549 Now able to hide connections in roster

A new sakai.property has been added, roster_view_connections,
which when false will hide the Connections button in the roster
view. The property's default is true, though it will be false
if profile2.connections.enabled is also false (also see
SAK-29267 & SAK-29408).
Jira ticket: https://jira.sakaiproject.org/browse/SAK-29549

A coupling between Profile2 and Roster2 all ready exists. Roster2 uses org.sakaiproject.profile2.logic.ProfileConnectionsLogic.
I added a null check before using the Profile2 SakaiProxy, which is how the ProfileConnectionsLogic is used.
If this is not acceptable, let me know and I will read in the Profile2 properties directly.

I'd prefer it if you just pulled the prop in Roster2's sakaiProxy.
Profile2's sakaiProxy doesn't do anything with the property so it just
seems a bit heavy to wire it in just for that purpose. I don't think you're
wrong or anything, I just know that I'll probably do it myself later just
to take some cruft out of the Spring wiring.
Thanks for adding the switch - it is a useful feature. Do you like the
handlebars clientside stuff?
Cheers,
Adrian.
On 22 June 2015 at 14:58, Leonardo Canessa<EMAIL_ADDRESS>wrote:

A coupling between Profile2 and Roster2 all ready exists. Roster2 uses
org.sakaiproject.profile2.logic.ProfileConnectionsLogic.
I added a null check before using the Profile2 SakaiProxy, which is how
the ProfileConnectionsLogic is used.
If this is not acceptable, let me know and I will read in the Profile2
properties directly.
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/701#issuecomment-114112569.

The changes you requested are in place.
The template changes are nice; it definitely makes for a much cleaner product.

Good one on the ProfileConstants. Go ahead and merge it in.
Cheers,
Adrian.
On 22 June 2015 at 19:55, Leonardo Canessa<EMAIL_ADDRESS>wrote:

The changes you requested are in place.
The template changes are nice; it definitely makes for a much cleaner
product.
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/701#issuecomment-114220896.

What's the hold up on merging this?