make repository name available in context

Is there an existing issue or pull request for this?

[X] I have searched the existing issues and pull requests

Feature description
I am creating a consolidated changelog for multiple repositories building a monolith using the --repository flag with three repos. The changelog gets generated but theres no reference which changelog refers to which repo, just the repos most current tags.
In the current context there's just details about commits but not about the repo name or url.
Desired solution
It would be nice to have the repo name (and url?) available in the context to have something like this:
config: [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }} -- {{ repo.name }}
which would look like this:
[1.2.3] - 2024-06-07 - orhun/git-cliff
changes ...
[4.5.6] - 2024-06-07 - another/repo
changes...
Alternatives considered
The closes thing I currently see to achieve this are commit parsers which allow me to run commands on the OS. But I am not sure how to use that in the body heading to call git and get the repo name. I tried putting a placeholder in the body
## [unreleased] - REPO_URL and then tried a postprocessor:
postprocessors = [
{ pattern = 'REPO_URL', replace_command = "basename -s .git git config --get remote.origin.url" },
]
this leads to the entire changelog dissappering and setting the reponame where the CI runs three times and not the individual ones :(
Additional context
No response

Hello!
You can do something like this:
git cliff --github-repo orhun/git-cliff

Then in the template:
{{ remote.github.owner }}/{{ remote.github.repo }}

See the following links for more information:

https://git-cliff.org/docs/configuration/remote
https://git-cliff.org/docs/integration/github

that sounds good but i am using a selfhosted Gitlab. Do i have to compile cliff to be able to use it? and does it work for multiple repos or just one?

Similarly, you can do the same for GitLab:
GITLAB_API_URL="<your self hosted url>" git cliff --gitlab-repo orhun/git-cliff

Then in the template:
{{ remote.gitlab.owner }}/{{ remote.gitlab.repo }}

See the following links for more information:

https://git-cliff.org/docs/configuration/remote
https://git-cliff.org/docs/integration/gitlab

Thanks a lot for the idea and docs links but this is still not working.
When I use three repos, the one with changes and the CI and two other ones with their changes.
If I run git cliff with API URL, token and --gitlab-repo path1/repo1 --repository= ./ path2/repo2 path3/repo3
In the result changelog all repos have the reponame repo1 when using {{ remote.gitlab.repo }}

Oh, it's expected that it might not work with multiple repos. I didn't try it out like that before and it's fetching the commits for only one repo...

ohh, ok, thanks a lot for checking! But could you make it possible to read the repos in the base implementation as part of the --repository flag and independent of the gitlab/github/... integrations?
In the individual repo folders you got all the info present about the repos and its not so useful to aggregate changes and not not knowing where they come from :(
this is an awesome project and this addition would make it a very valuable tool

ohh, ok, thanks a lot for checking! But could you make it possible to read the repos in the base implementation as part of the --repository flag and independent of the gitlab/github/... integrations?

Do you mean making e.g. the directory name available in context?

Yes the directory name would work

Okay, I just checked and I'm not sure where in context we can add the repository path.
The context is currently an array of releases, updating that structure will be a breaking change.

Thank you very much for your effort, I have no experience in Rust yet and can't make a code suggestion myself :(
Can't you append the repo name at the same position where you keep the repos tag version number? Or is that not a kind of list/array?

You can take a look at https://git-cliff.org/docs/templating/context for getting an idea.
To oversimplify it:
[
  {
    "version": "v0.1.0-rc.21"
  },
  {
    "version": "v0.1.0-rc.20"
  }
]

We can add the repo path to each item here, but it would be really redundant :/

If theres just a changelog created for the current repo its not really needed, I agree. But when using the --repository flag and multiple repos it should be a good addition in my opinion.
I also tried it with a postporcessor and some git commands and a replace of a placeholder, but that made the whole changelog disappear and just header and footer were left. I am at a different computer this week and can't access the snippet currently

Second thought: this actually sounds useful!
Implemented in #721 - any chance that you could test it? 😊

awesome thank you so much. I will be able to test it it on sunday or monday and will let you know!

I tried to build the branch in a container based on rust:alpine following your docs with the command
apk add git zlib libgit2 && \
git clone -b feat/add_repository_to_context https://github.com/orhun/git-cliff && \
cd git-cliff/ && \
CARGO_TARGET_DIR=target cargo build --release

But it fails with ther error
error occurred: Command "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "include" "-I" "/git-cliff/target/release/build/ring-b443f8a0fdd469dc/out" "-Wall" "-Wextra" "-fvisibility=hidden" "-std=c1x" "-Wall" "-Wbad-function-cast" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wnested-externs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wstrict-prototypes" "-Wundef" "-Wuninitialized" "-g3" "-DNDEBUG" "-o" "/git-cliff/target/release/build/ring-b443f8a0fdd469dc/out/a9af75d892b04b75-p256-nistz.o" "-c" "crypto/fipsmodule/ec/p256-nistz.c" with args cc did not execute successfully (status code exit status: 1).

Is there something missing in the branch or docs?

I build myself a modified Docker image derived from your multistage build. The chaneglog looks way better now
All notable changes to this project will be documented in this file.

## [4.5.6] - 2024-06-23 - git-cloned-dep-repos/git-cliff-sub-b

### 🚀 Features

- Big feature in repo B

## [1.2.3] - 2024-06-23 - git-cloned-dep-repos/git-cliff-sub-a

### 🚀 Features

- Some change in repo A

## [0.0.6] - 2024-06-23 - ./

### 🚀 Features

- Add basename cmd

I am currently processing the current repo and two more which i clone into the CI and then run git cliff --output CHANGELOG.md --repository ./ git-cloned-dep-repos/git-cliff-sub-a git-cloned-dep-repos/git-cliff-sub-b . The base repos name is just mentioned as ./ which is not so helpful.
Could it be possible to get the repo name via the command
basename -s .git `git config --get remote.origin.url`

into the context?

Thanks for testing!

Could it be possible to get the repo name via the command

That would mean that we will be executing OS commands which might change across different platforms + we will be depending on basename & git commands. I'm not very positive with that :)
What's wrong with using the raw paths that are provided via args again?

Thats a good point, i get you. With the current implementation I get a little too much in the path. In case of the cloned external repos I also get the temporary folder I created in the CI and in case of the current repo the CI its running in I dont get the repo name :(
For the first part it would help to leave out all path folders except the last. For the second looking into the repo git config is a good solution. I think assuming that git is present should be ok when using your tool?

For the first part it would help to leave out all path folders except the last.

Can you elaborate this? I didn't get it fully.

For the second looking into the repo git config is a good solution. I think assuming that git is present should be ok when using your tool?

Sorry I don't want to shell out and call git, but if there is a way to do it with git2 or any other Rust crate then I might be up for it.

Sure no problem. In my CI I created a folder git-cloned-dep-repos and cloned the remote repos into it to process them via the --repository flag. This lead to the result that the {{ repository }} placeholder then filled in the repo name as git-cloned-dep-repos/git-cliff-sub-a and git-cloned-dep-repos/git-cliff-sub-b. It used the full path from the workspace root and not just the repo name which is the last folder in the path.
To the second part regarding calling git, could it be a solution to parse the git config (.git/config) which should always be present as plain text? Then you don't need other binarys and just test file parsing :)

It used the full path from the workspace root and not just the repo name which is the last folder in the path.

This might be a preference based on different use cases - someone else might want it to see the full path so I will leave that up to the user to process it via template functions :)

which should always be present as plain text? Then you don't need other binarys and just test file parsing :)

If the purpose is just to get the value of git config --get remote.origin.url then it is already available as {{ remote.gitlab.repo }} . The only issue that needs fixing is that it won't work with multiple repos yet.. which I might fix in the future.
The requirements are not super clear and I'm not fully convinced that we need to parse .git/config yet :)
Btw I will merge #721 - it should be good to go as is 🐻

Fair point, thank you for your work and taking the time for this lengthly discussion with me. This is a very cool project of yours 🤙


Added typings...

Added some basic typings. Most should be covered except for what happened in my latest PR.

As v2 is now pushed, typings will have to be updated. However merging this with dev anyway.
Note: typings for v2 will mostly be re organising already existing typings.
Since v2 adds a new layer of abstraction, we can even expect it to be slightly easier (and more convenient)


Issue when we try running using elm reactor on Main.elm

How to reproduce
It works fine if you click on index.html but if you want to make see the elm debugger in action, then it is a little problematic:

Clone the repo.

Run elm reactor

Click on Main.elm.

The following error comes up:
Initialization Error

Error: Problem with the flags given to your Elm program on initialization.

Json.Decode.oneOf failed in the following 2 ways:

(1) Problem with the given value:

    undefined

    Expecting null

(2) Problem with the given value:

    undefined

    Expecting an OBJECT with a field named `visibility`

I managed to get it working by manually modifying the index.html file generated by elm make... command.

I added flags with the value null:
var app = Elm.Main.init({ node: document.getElementById("elm"), flags: null});
The object that is passed to flags is going to be the input argument for the init function. Since the init function expects a Maybe Model, you can pass in a JSON object representing an entire model:
{ entries: [{description:"Hello!", completed:true, editing:false, id:13}], visibility: "All", field: "", uid: 0}

I added an html link reference in the header to the included style.css file:
<link rel="stylesheet" type="text/css" href="style.css">


Restore unavailable LIFX lights on startup

Description:
Unavailable LIFX lights are now represented by a separate class. Such lights are generated on startup for all entries in the entity registry. This ensures that an entity exists even if the bulb is switched off at the wall switch during a restart.
To handle the switching between available/unavailable objects, a wrapper class is introduced.
Related issue (if applicable): mentioned in forum
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox.
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

If the code communicates with devices, web services, or third-party tools:

[X] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[X] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[X] Untested files have been added to .coveragerc.

I don't think we should restore or use HA as a source for the interface to generate entity they are not seen by the represented interface. Please open an architecture issue about this

Hmm @balloob seems to endorse that in the forum thread.
I can open an architecture issue but it will be some days before I have the time for that.

Yeah, for kind of device tracker.
I think for interface based integration it has other terms. Normally the Hub/Library solves the issue i.e. hue, deconz or HomeAssistant they discovery sticky devices too and later if they are available again, it exists already.
Another good example is sonos. They also not restore devices from Core cache. If there is a box again available or a new speaker is around, it makes a new discovery and enters the new device.
I think the best solution for an lvl1 integration like LIFX is that use a discovery and search all x min for new devices and add this if they are available. Or the manufacturer can give you an API call to become all devices.

(Aah, just found this reply in a tab, I never hit send)
For a good user experience, we should restore devices that are currently offline. Devices not being online causes a bunch of problems, like yellow banners in Lovelace and makes it very difficult to get them synchronized to Google, because it requires all devices to be online.
Because each integration works differently, it will be impossible for Home Assistant to automatically know which entities to restore, and to what state. We should leave this up to the integrations.
Now here is where I am a bit mixed. The approach in this PR is what I consider the current best practice, it is however not perfect. Like Pascal points out, how do know a device no longer exists? We wouldn't want to require the user to directly interact with the device/entity registry, and then have LIFX listen to that. That creates a type of two-way data binding (LIFX creates entities that fill registries, registry mutation impacts how LIFX behaves) that will cause a lot of problems down the line if this gets into all available integrations.
If a hub/lib solves it, it means that it is cached outside of Home Assistant. Not ideal either, but at least it is no longer our responsibility 😅.
So yeah, I don't know. I am fine with having this PR move on for now, because it's better than nothing, and it's going to be a better experience.

We wouldn't want to require the user to directly interact with the device/entity registry, and then have LIFX listen to that.

Why would LIFX need to listen? If an entity is removed from the registry, it will not be recreated.
I am not sure where to go from here. Should we make the architecture issue to get more developer opinion? Should we merge this to get more user opinion? Both?

Well, my issue on all is the dummy light. So we had now 80 lights integration. Most of that solve the issue on there control system/API/library. So we end up in maybe 10-15 light integration they are not robust to handle device they are currently offline.
Well, we have other components and more integration. But if every of this integration need create a dummy entity to handle a not available and controllable light, it blow the code and we need maintain this kind of entity too.
I'm fine to make a helper for integration, but that need more code in our core. I would love that the entity_register can handle that as well with a dummy entity from component self. Later if the Integration have found this light, he can replace the dummy entity object with this from core.
This current approach is some things that are fine for 1 integration, but if we have 100 integration they handle this problem like this code, it will be a burden and end up in a many solution for same problem.

@pvizeli I actually agree with you about reusability but @balloob already rejected core support in Discord and suggested this approach instead. So I am still not sure how to proceed :)
For the record, the approach in this PR does have some issues in that the friendly name and supported_features are lost until the entity becomes available again.

The reason LIFX would need to listen to the registry is that it might be a real device that is being removed, and it would need to respond.
So automatically restoring some entities could be something that we can offer. In that case I would expect it to become a part of the restore entity helper. When the HOME_ASSISTANT_START event fires, the restore helper will check which entities marked for always restoration don't exist in the state machine, and write those to the state machine. And as entities become available, LIFX will override the state.
We can't do this from the entity registry, because of all the things that we include in the state regardless if it is available or not. We cannot currently restore that from the entity registry (I would want to, but that is a story for another day maybe?*)

I think that we should have the entity registry store the things that describe the entity and it's capabilities like device class, supported features, name, unit_of_measurement. That way it will be possible to easily sync Google and Alexa with HA without requiring all LIFX lights to be restored.

The reason LIFX would need to listen to the registry is that it might be a real device that is being removed, and it would need to respond.

Okay, but that seems true with or without this PR. Is this something that I should already have implemented?

So automatically restoring some entities could be something that we can offer.

Awesome. So I will close this PR and make an architecture issue (when time allows).

Ok. Sorry for the incorrect guidance.

No sweat ... that wasn't incorrect guidance, we are still brainstorming 😁


Use window/door sensors that are not binary_sensor

My alarm system (HikVision AX Pro) has magnet sensors attached on every door and window. I can get them to show up in HA like sensor.ax_pro_home_magnet_6 with status "Off" or "On". Versatile Thermostat only shows binary_sensors for open window management.

As a workaround, you could create a binary sensor and an automation that updates the binary sensor whenever the magnet sensors detect a change.

As a workaround, you could create a binary sensor and an automation that updates the binary sensor whenever the magnet sensors detect a change.

As a workaround, I created a binary sensor throut template:
- platform: template   sensors:     open_garage:         friendly_name: "Garage door open"         value_template: "{{ states('sensor.ax_pro_home_magnet_6')}}"         device_class: garage_door

Good point. Will try that.
Next up - could we define multiple windows/doors here? Or should I use a group helper.

You should use a group. For temperature sensor also if needed. A group can be done directly from "Entry" menu (near devices).

Brilliant. Thank you for the comments.


Add grpc client generation config

This PR adds grpc_client as the framework for generating GRPC client code.

Included in https://github.com/helium/helium-packet-router/pull/49


About RGB-Posec3d

Hi, it's really an amazing job! But I didn't find the config about using SlowFast network (there is only SlowOnly network configuration). So could you offer a script about that? Thank you so much

Hi, mxy-699699, I'm working on adding it to PYSKL recently, will release it once ready.

Finally, I have implemented RGBPoseConv3D in PYSKL 🤣 . The implementation is in PR https://github.com/kennymckormick/pyskl/pull/116 and has been merged to the main branch.

Finally, I have implemented RGBPoseConv3D in PYSKL 🤣 . The implementation is in PR #116 and has been merged to the main branch.

That's great. Thank you so much for all your work.


Unexpected identifier async _initialize()

I'm getting the below error when using this package. Is there anyway to fix this?
I'm using node 8.9.3. And it has worked locally... and had worked when I deployed it to Google's Firebase functions, but all of a sudden today I'm trying to deploy to firebase functions again, and I get this error. I hadn't run any npm install / update so not sure why this happened today.
Detailed stack trace: /user_code/node_modules/keras-js/lib/Model.js:107
  async _initialize() {
        ^^^^^^^^^^^

SyntaxError: Unexpected identifier
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/user_code/node_modules/keras-js/lib/index.js:22:37)

The runtime of Google Cloud Functions is Node v6.11.5, which does not support async/await.
https://cloud.google.com/functions/docs/writing/#the_cloud_functions_runtime
A possible workaround is using babel-register to transpile async/await on runtime, though I think keras-js should not use async/await (or at least transpile them before releasing) until Node.js v6.x comes to the end of life (April 2019).

I found that keras-js does not even support the latest LTS (Node v8.x).
https://github.com/transcranial/keras-js/blob/df999159284abc5de0b92bc0f801375c08bf9008/.babelrc.js#L4
Is there any reason for that?

Run this
npm uninstall  ember-cli
npm cache clean && bower cache clean
npm install<EMAIL_ADDRESS>


Remove apparently-unnecessary model_rebuild

Partially addresses the performance issues noted in #5351

I'll note here that this doesn't have as dramatic of an effect on overall pytest runtime as it does on hot-loop generic model creation.
I ran pytest tests/test_generics.py --durations 20 on this branch and on the pre-refactor commit af73124e, and it seems to attribute most of the difference in runtime to the "setup" of the tests:
# Pre-refactor:
0.46s call     tests/test_generics.py::test_generics_work_with_many_parametrized_base_models
0.10s call     tests/test_generics.py::test_caches_get_cleaned_up
0.02s setup    tests/test_generics.py::test_generic_config
0.02s setup    tests/test_generics.py::test_classvar
0.01s setup    tests/test_generics.py::test_enum_generic
0.01s call     tests/test_generics.py::test_caches_get_cleaned_up_with_aliased_parametrized_bases
0.01s call     tests/test_generics.py::test_generic_name
0.01s call     tests/test_generics.py::test_generic_recursive_models_complicated
0.01s call     tests/test_generics.py::test_generic_recursive_models_triple
0.01s setup    tests/test_generics.py::test_generic_recursive_models_with_a_concrete_parameter
0.01s setup    tests/test_generics.py::test_generic_recursive_models_in_container
0.01s setup    tests/test_generics.py::test_generic_with_user_defined_generic_field
0.01s setup    tests/test_generics.py::test_construct_other_generic_model_with_validation
0.01s setup    tests/test_generics.py::test_multilevel_generic_binding
0.01s setup    tests/test_generics.py::test_generic_subclass
0.01s setup    tests/test_generics.py::test_generic_model_as_parameter_to_generic_type_alias
0.01s setup    tests/test_generics.py::test_generic_recursive_models_complicated
0.01s setup    tests/test_generics.py::test_generic_recursive_models_triple
0.01s setup    tests/test_generics.py::test_multi_inheritance_generic_defaults
0.01s setup    tests/test_generics.py::test_double_typevar_substitution

# This branch:
0.56s call     tests/test_generics.py::test_generics_work_with_many_parametrized_base_models
0.09s call     tests/test_generics.py::test_caches_get_cleaned_up
0.03s setup    tests/test_generics.py::test_generic_enum
0.03s setup    tests/test_generics.py::test_generic_annotated
0.03s setup    tests/test_generics.py::test_parent_field_parametrization
0.03s setup    tests/test_generics.py::test_nested
0.03s setup    tests/test_generics.py::test_optional_value
0.03s setup    tests/test_generics.py::test_construct_generic_model_with_validation
0.03s setup    tests/test_generics.py::test_multilevel_generic_binding
0.03s setup    tests/test_generics.py::test_generic_recursive_models
0.03s setup    tests/test_generics.py::test_generic_recursion_contextvar
0.03s setup    tests/test_generics.py::test_generic_enums
0.03s setup    tests/test_generics.py::test_partial_specification_instantiation
0.03s setup    tests/test_generics.py::test_generic_subclass_with_extra_type
0.03s setup    tests/test_generics.py::test_custom_generic_naming
0.03s setup    tests/test_generics.py::test_schema_is_valid
0.03s setup    tests/test_generics.py::test_construct_other_generic_model_with_validation
0.03s setup    tests/test_generics.py::test_generic_recursive_models_triple
0.03s setup    tests/test_generics.py::test_generic_recursive_models_in_container
0.03s setup    tests/test_generics.py::test_double_typevar_substitution

I also checked and there doesn't seem to be any meaningful changes to fixtures in test_generics.py or conftest.py, so I'm not sure where the extra setup time is coming from, or how to profile it.
I also checked, adding time.sleep(0.02) as a fixture brings the runtimes in line, so it at least seems consistent with something slow happening in a fixture or similar, but it would still be nice to confirm/resolve that.

Some profiling for the record
from typing import Generic, List, Type, TypeVar

from pydantic import BaseModel

T = TypeVar('T')
C = TypeVar('C')

class A(BaseModel, Generic[T, C]):
    x: T
    y: C

class B(A[int, C], BaseModel, Generic[C]):
    pass

models: List[Type[BaseModel]] = []
for i in range(1_000):
    models.append(type(f'M{i}', (BaseModel,), {}))

for m in models:
    B[m]

A pyinstrument report:
report.html.zip
JSON data for https://www.speedscope.app/:
CPU_profile_for_test.speedscope.json.zip

It turns out the garbage collection fixture was the one that had increased in runtime from ~10ms to ~30ms. Perhaps worth looking into more, but removing from most tests, the runtime becomes much more similar pre- and post-refactor.

@samuelcolvin I think unless this change seems suspicious to you we should merge this, and if the garbage collection stuff concerns you at all let's just create a separate issue for that.
Given the massive simplifications I realized were possible in #5361 I just think that the improvements to model creation eliminated the need for some of the hacks that I had to use to get it working in the first place.

Amazing, thank you.


mola_lidar_odometry: 0.3.2-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository mola_lidar_odometry to 0.3.2-1:

upstream repository: https://github.com/MOLAorg/mola_lidar_odometry.git
release repository: https://github.com/ros2-gbp/mola_lidar_odometry-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.3.1-1

mola_lidar_odometry
* Support input dataset directories for split bags
* Contributors: Jose Luis Blanco-Claraco

Holding for Humble sync


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/654 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit 66f4ce9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-11-18-06-21-11 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-11-18-06-21-11

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


error: [Errno 32] Broken pipe

content = self.si.RetrieveContent()
File "/usr/local/lib/python2.7/dist-packages/pyVmomi/VmomiSupport.py", line 580, in
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pyVmomi/VmomiSupport.py", line 386, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/usr/local/lib/python2.7/dist-packages/pyVmomi/SoapAdapter.py", line 1323, in InvokeMethod
conn.request('POST', self.path, req, headers)
File "/usr/lib/python2.7/httplib.py", line 1057, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python2.7/httplib.py", line 1097, in _send_request
self.endheaders(body)
File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
self.send(msg)
File "/usr/lib/python2.7/httplib.py", line 873, in send
self.sock.sendall(data)
File "/usr/lib/python2.7/ssl.py", line 743, in sendall
v = self.send(data[count:])
File "/usr/lib/python2.7/ssl.py", line 709, in send
v = self._sslobj.write(data)
error: [Errno 32] Broken pipe

exact same issue and I cant find a fix

Do you guys have solution for this issue?


Added FCAlertview (Objective-C) to Alert category

Added FCAlertview (Objective-C) to Alert category
Project URL

https://github.com/nimati/FCAlertView
Description

FCAlertView is a Flat Customizable AlertView for iOS written in Objective-C
Why it should be included to awesome-ios (optional)
It's equally awesome as its Swift counterpart
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 or later
[ ] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hey @yoha, thanks for also including the Objective-C version! 😃 👍


kwarg for Categorical.fillna should be value instead of fill_value

It seems inconsistent that all the other fillna() methods (DataFrame.fillna, Series.fillna, etc) have value as the first kwarg but Categorical has fill_value instead

Looks good to me

@mortada thanks!


Use BLE implementation in DeviceLayer in CHIP Device Controller Python Binding

Problem
Sorry by device I mean an iOS device. chip-tool simulates a controller, like the iOS device controller. And on iOS, src/platform/darwin is the used BLE stack.
-- Yep, agree, for python device controller, we should replace ChipCoreBluetoothMgr.py with the same implementation as iOS app has.
Originally posted in #4334 (comment)

Summary of Changes
Use BLE implementation in DeviceLayer in CHIP Device Controller Python Binding, this does not remove the BLEManager classes, they are used for commands like "ble-scan" now.
There are verbose output in device controller, and some cleanup is required as follow up.
This PR also does similar things with Linux.

Fixes #4399

@erjiaqing Can you take a peek at the conflict here please?
@jelderton @saurabhst can you take a peek man?

@erjiaqing Can you take a peek at the conflict here please?
@jelderton @saurabhst can you take a peek man?


Fix a few bugs and add aggregate build.

Fix a few issues:

Random string generator had a broken condition;
Forgot to add Service Locator to the list of exported headers.

Added a target to create a release build of the framework.

👍


Image manipulation before caching

Hi,
not exactly an issue but more a feature request.
Where would it be the right place to do some offscreen (and possibily non in the main thread) image manipulation before storing to memcache and disk?

I'm also interested in doing this.
I think the main conceptual problem is that images are cached by their URL. If you allow image manipulation before caching, the cached image might not necessarily be the same image represented by its URL, which is a problem if that URL is requested again from a part of the code that doesn't need the manipulation. AFNetworking solves this by allowing the developer to specify a cache name with each request. The URL and cache name are concatenated to form the cache key for the post-manipulation image. I think a combination of this and a new delegate method (or block) that accepts the downloaded image and returns the manipulated image would solve the problem.
Should the new delegate method go in SDWebImageDownloader? I'd like to have access to the manipulation code in the UIImage category, but if that's not possible to do cleanly, then I can always create my own category with the necessary bits. If @rs can provide some feedback, I can write the code. I'm just not that familiar with the SDWebImage architecture yet.


train error

Excellent work. I installed the corresponding packages and attempted to train with a different dataset,  resizing the images into 256-sized blocks, and then encountered the following issue. Could you please tell me if there is any problem here:
#----------Creating logger----------#
#----------GPU init----------#
#----------Preparing dataset----------#
#----------Prepareing Models----------#
SC_Att_Bridge was used
#----------Prepareing loss, opt, sch and amp----------#
#----------Set other params----------#
#----------Training----------#
torch.Size([8, 3, 256, 256])
x: torch.Size([8, 24, 32, 32])
x1: torch.Size([8, 1024, 6])
Traceback (most recent call last):
File "train.py", line 189, in
main(config)
File "train.py", line 132, in main
train_one_epoch(
File "/root/UltraLight-VM-UNet-main/engine.py", line 39, in train_one_epoch
out = model(images)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/parallel/data_parallel.py", line 183, in forward
return self.module(*inputs[0], **module_kwargs[0])
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/UltraLight-VM-UNet-main/models/UltraLight_VM_UNet.py", line 221, in forward
out = F.gelu(F.max_pool2d(self.ebn4(self.encoder4(out)),2,2))
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/container.py", line 215, in forward
input = module(input)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/UltraLight-VM-UNet-main/models/UltraLight_VM_UNet.py", line 38, in forward
x_mamba1 = self.mamba(x1) + self.skip_scale * x1
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/mamba_ssm/modules/mamba_simple.py", line 146, in forward
out = mamba_inner_fn(
File "/root/miniconda3/lib/python3.8/site-packages/mamba_ssm/ops/selective_scan_interface.py", line 317, in mamba_inner_fn
return MambaInnerFn.apply(xz, conv1d_weight, conv1d_bias, x_proj_weight, delta_proj_weight,
File "/root/miniconda3/lib/python3.8/site-packages/torch/autograd/function.py", line 539, in apply
return super().apply(*args, **kwargs)  # type: ignore[misc]
File "/root/miniconda3/lib/python3.8/site-packages/torch/cuda/amp/autocast_mode.py", line 113, in decorate_fwd
return fwd(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/mamba_ssm/ops/selective_scan_interface.py", line 187, in forward
conv1d_out = causal_conv1d_cuda.causal_conv1d_fwd(
TypeError: causal_conv1d_fwd(): incompatible function arguments. The following argument types are supported:
1. (arg0: torch.Tensor, arg1: torch.Tensor, arg2: Optional[torch.Tensor], arg3: bool) -> torch.Tensor
Invoked with: tensor([[[-3.6921e-02, -2.2584e-02, -2.5043e-02,  ..., -5.4228e-02,
-5.4027e-02, -5.1787e-02],
[-6.3227e-02, -3.2376e-02, -3.7078e-02,  ..., -8.5041e-02,
-8.5496e-02, -8.1049e-02],
[-4.1870e-03, -8.7852e-03, -8.0635e-03,  ..., -4.1606e-02,
-4.0918e-02, -4.1173e-02],
...,
     [ 1.3810e-01,  1.2920e-01,  1.2920e-01,  ...,  1.4433e-01,
       1.4433e-01,  1.6126e-01],
     [ 1.4266e-02,  1.4064e-02,  1.4064e-02,  ...,  1.1132e-02,
       1.1132e-02,  9.8532e-03],
     [-7.0302e-02, -6.6612e-02, -6.6612e-02,  ..., -7.2660e-02,
      -7.2660e-02, -7.9289e-02]]], device='cuda:0', requires_grad=True), tensor([[-0.2176, -0.1239, -0.0767, -0.1056],
    [-0.0190, -0.1246,  0.3363, -0.1871],
    [ 0.1523, -0.0473,  0.0405, -0.5286],
    [ 0.0705, -0.1187,  0.0597,  0.0934],
    [-0.2788,  0.0680, -0.1250, -0.1106],
    [ 0.3183, -0.1641,  0.3027,  0.0206],
    [ 0.3087, -0.3258, -0.2065,  0.2467],
    [ 0.3808,  0.1227, -0.1961, -0.4432],
    [-0.4132, -0.0891, -0.0532,  0.0154],
    [ 0.0185, -0.1335, -0.2039,  0.0383],
    [ 0.1164,  0.0900, -0.0019, -0.1997],
    [ 0.0422, -0.3562, -0.0239, -0.1291]], device='cuda:0',
   requires_grad=True), Parameter containing:

tensor([-0.0774,  0.0933,  0.1647, -0.1945,  0.3946, -0.0037,  0.0410, -0.4760,
0.0619,  0.1716,  0.0697, -0.0496], device='cuda:0',
requires_grad=True), None, None, None, True

Hi, based on your error message and past questions asked, this is mostly an issue with data preparation, resulting in the data not being entered correctly into the '.npy' file. We recommend that you preprocess your data according to the 'Prepare your own dataset' section.
Alternatively, it is recommended that you first try to reproduce it on the ISIC2017 dataset (2000 images), which will allow you to rule out whether it is a matching issue with the environment and hardware.

Thank you for your feedback. The issue was resolved after I reinstalled mamba_ssm==1.0.1; the previous version was 1.2.0. I have modified the loader.py to read a different dataset according to the task, but I am currently somewhat puzzled because, after training for multiple epochs on my task, the loss hardly decreases.

Try to check the output and the DSC of the final result in the 'Output' folder. Also, try to check if the masks of the modified loader.py final output model are normalized.

Thank you for your feedback. The issue was resolved after I reinstalled mamba_ssm==1.0.1; the previous version was 1.2.0. I have modified the loader.py to read a different dataset according to the task, but I am currently somewhat puzzled because, after training for multiple epochs on my task, the loss hardly decreases.

Hello, have you solved the problem of loss not decreasing? If you use a custom dataset, how should you process the data to achieve the purpose of training?


autodiff documentation outdated

Since setadbackend and setrdcache  are depricated, the documentation found in https://turing.ml/dev/docs/using-turing/autodiff is outdated and gives misinformation.

The webpage is rebuilt every day around midnight (IIRC), so since the tutorial was updated I assume the changes should show up by tomorrow.


Cosmos DB Change Feed reliability/availability

It is planned to leverage Change Feed for tracking changes in mission-critical company data. It is unacceptable that some updates to underlying Cosmos collection are lost.
I assume Change Feed has the same SLA as Cosmos DB (99.999%) and I understand it is practically impossible for it to break, but what will happen in hypothetical situation when collection is updated, but change event is not issued? Information on how Change Feed works internally would be also great.
We plan to use Functions as Change Feed consumers. What is the recommended way to resolve a case when Change Feed sent update but Function was down for some reason?

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

ID: fdcc897a-d6df-3305-e9cb-01889a3c5d4f
Version Independent ID: 739a9fc7-3782-a860-ac6d-4194fd1ce2e8
Content: Working with the change feed support in Azure Cosmos DB
Content Source: articles/cosmos-db/change-feed.md
Service: cosmos-db
GitHub Login: @TheovanKraay
Microsoft Alias: thvankra

@ealsur Thanks for valuable information. Today I've re-ran my tests from scratch and all the consumers received the same number of document updates. I was doing only inserts and re-creating leases prior to running tests previously though, so maybe there is something else that skewed the results. Also I've did not manage to reproduce function error (the whole processing is just putting the whole received document to Event Hub).
Given the assumption we'll handle all the retry in our custom Processor and consume Change Feed directly in our services, are there any drawbacks other than additional ~2% RU added per consumer per collection? So far we tried to execute recommended architecture referenced in bunch of samples,  Jet.com customer success story, etc. that uses Event Hub as intermediate storage for updated documents (Change Feed -> Azure Function -> Event Hub -> Consumer), but it does not look feasible now. We don't expect millions requests per second and just want to have updates in order and have ability to get arbitrary update upon request.

If I understand correctly from:

Given the assumption we'll handle all the retry in our custom Processor and consume Change Feed directly in our services, are there any drawbacks other than additional ~2% RU added per consumer per collection?

This means you will use your own compute to run Change Feed Processor instead of Functions? Drawbacks really subjective, Functions uses the same Change Feed Processor, so the drawback is tied to billing and time. Using your own compute does give you a higher degree of customization at the expense of having to manage and maintain it.
I'm not sure where that ~2% RU per consumer comes from, each instance consuming the Change Feed will consume RUs based on frequency of operations and volume of data, so it totally depends on your data size, volume of operations, and data distribution across partitions.
Regarding using Event Hub, I'm not sure why it does not look feasible, care to elaborate?

Using your own compute does give you a higher degree of customization at the expense of having to manage and maintain it.
Right, we may need for implementing complex errors processing. Despite transient errors like network problems we may have a whole class of data-bound issues since we are joining information from various sources. There is a case where data consumer would need to access some "previous" update (the one that was marked as successfully processed). I'm currently still investigating this, but off-the-cuff that's not possible with Functions. To rephrase - get single document from CF instead of moving feed cursor back in time and reprocess everything after it.
Regarding using Event Hub, I'm not sure why it does not look feasible, care to elaborate?
It adds complexity and costs. Initially we thought about it as a reliable event history source where we can potentially locate arbitrary changed document. That works like a charm actually, I'm persisting just the document offset and partition in Event Hub info and it's sufficient for Dead Letter handling.
Also we were thinking about Event Capture (+3x throughput costs additionally) to store raw or processed documents. Now if we can use CF directly, it looks more robust. Also, if needed, we can still do our own "Events Capture" via Function in literally no time.
My numbers on RUs are indeed synthetic, but it does not look there would be much costs saving for single CF consumer writing to EH and then everybody consuming EH vs. every consumer consuming CF directly. As @TheovanKraay absolutely nailed above, Cosmos our only source for events. If we had multiple source it would make more sense to use EH as an aggregate storage.
From a consumer standpoint there is also no much difference developing a consumer for Change Feed vs. Event Hub too.


Service object doesn't seem to be returned unless full path specified

curl -X GET "http://<IP_ADDRESS>:9000"
{
  "detail": "The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.",
  "status": 404,
  "title": "Not Found",
  "type": "about:blank"
}

@thomasyu888 Here's how to update the date annotator on the ec2.
cd ~/nlpsandbox/date-annotator-example
docker-compose stop
git pull
docker-compose up --build

This will deploy the version that we have on the branch develop.

Thanks, didn't realize the annotator hasn't been updated.


Few edits to freeze note

Is 'freeze' and 'lock to' the same idea?

Yes freeze / lock is the sma.e


Support logging to /dev/log (Linux) or /var/run/syslog (Mac OS X)

I work for Justin.TV, we use this to handle our syslog but we log to the unix socket and then configure syslog to route our messages to various different parts of our infrastructure. We find this is a better way to handle our logging concerns. I've patched ain to have the arguments to set to be an object, I chose to do this because I was adding the transport option, I felt it was a nicer API. Transport can be either 'UDP' or 'file', logging is then appropriately handled.

ping! :)

Sorry haven't found the time yet. We had release week.


OpenCensus representation of Histogram in Prometheus exporter differs from Prometheus representation

Please answer these questions before submitting a bug report.
What version of OpenCensus are you using?
0.15.0
What JVM are you using (java -version)?
java version "9"
Java(TM) SE Runtime Environment (build 9+181)
Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
What did you do?
Using the Prometheus exporter to export histogram measurements the representation of data is not following Prometheus normal practice. In Prometheus normally a sample would be represented in multiple buckets this is not the case in the data exported from OpenCensus Prometheus exporter.
If possible, provide a recipe for reproducing the error.
What did you expect to see?
I would expect the OpenCensus Prometheus exporter to export histograms that can be used as normally in Prometheus expressions.
What did you see instead?
I see OpenCensus only representing the sample in on bucket whereas Prometheus clients normally would represent in it multiple buckets.
Following code can reproduce the problem.
        PrometheusStatsCollector.createAndRegister();

        Measure.MeasureLong measure = Measure.MeasureLong.create("measurement", "to test", "ms");
        double[] buckets = {0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 8.0, 10.0, 13.0, 16.0, 20.0, 25.0, 30.0,
                40.0, 50.0, 65.0, 80.0, 100.0, 130.0, 160.0, 200.0, 250.0, 300.0, 400.0,
                500.0, 650.0, 800.0, 1000.0, 2000.0, 5000.0, 10000.0, 20000.0, 50000.0,
                100000.0};
        Stats.getViewManager()
                .registerView(
                        View.create(View.Name.create("opencensus/histogram"),
                                "Histogram exported by OpenCensus",
                                measure,
                                Aggregation.Distribution.create(
                                        BucketBoundaries.create(Arrays.stream(buckets).mapToObj(d -> Double.valueOf(d)).collect(Collectors.toList()))),
                                Collections.emptyList()
                        ));

        Stats.getStatsRecorder().newMeasureMap().put(measure, 120).record();

        Histogram histogram = Histogram.build("prometheus_histogram", "Histogram exported by Prometheus")
                .buckets(buckets)
                .register();
        histogram.observe(120);

        Collections.list(CollectorRegistry.defaultRegistry.metricFamilySamples()).stream()
                .forEach(f -> {
                    System.out.println("Sample: " + f.name);
                    f.samples.forEach(s -> {
                        s.labelNames.forEach(name -> {
                            System.out.println(name + "=" + s.labelValues.get(s.labelNames.indexOf(name)) + " " + s.value);
                        });
                    });
                    System.out.println();
                });

This yields the following output:
Sample: opencensus_histogram
le=0.0 0.0
le=1.0 0.0
le=2.0 0.0
le=3.0 0.0
le=4.0 0.0
le=5.0 0.0
le=6.0 0.0
le=8.0 0.0
le=10.0 0.0
le=13.0 0.0
le=16.0 0.0
le=20.0 0.0
le=25.0 0.0
le=30.0 0.0
le=40.0 0.0
le=50.0 0.0
le=65.0 0.0
le=80.0 0.0
le=100.0 0.0
le=130.0 1.0
le=160.0 0.0
le=200.0 0.0
le=250.0 0.0
le=300.0 0.0
le=400.0 0.0
le=500.0 0.0
le=650.0 0.0
le=800.0 0.0
le=1000.0 0.0
le=2000.0 0.0
le=5000.0 0.0
le=10000.0 0.0
le=20000.0 0.0
le=50000.0 0.0
le=100000.0 0.0
le=+Inf 0.0

Sample: prometheus_histogram
le=0.0 0.0
le=1.0 0.0
le=2.0 0.0
le=3.0 0.0
le=4.0 0.0
le=5.0 0.0
le=6.0 0.0
le=8.0 0.0
le=10.0 0.0
le=13.0 0.0
le=16.0 0.0
le=20.0 0.0
le=25.0 0.0
le=30.0 0.0
le=40.0 0.0
le=50.0 0.0
le=65.0 0.0
le=80.0 0.0
le=100.0 0.0
le=130.0 1.0
le=160.0 1.0
le=200.0 1.0
le=250.0 1.0
le=300.0 1.0
le=400.0 1.0
le=500.0 1.0
le=650.0 1.0
le=800.0 1.0
le=1000.0 1.0
le=2000.0 1.0
le=5000.0 1.0
le=10000.0 1.0
le=20000.0 1.0
le=50000.0 1.0
le=100000.0 1.0
le=+Inf 1.0

I am looking at doing a PR on this one - I guess it could be fixed in the PrometheusExporterUtils.getSamples()

Thanks for reporting, it would be great if you can send a PR to fix.
Interesting, so in Prometheus the histogram bucket count is actually a cumulative count, which is different from OpenCensus histogram (where the bucket count only represents the count in current bucket).

Fixed by https://github.com/census-instrumentation/opencensus-java/pull/1309.


build: bump tzdata version to 2023b

2023a:
The 2023a release of the tz code and data is available.

This release contains the following changes:

   Briefly:
     Egypt now uses DST again, from April through October.
     This year Morocco springs forward April 23, not April 30.
     Palestine delays the start of DST this year.
     Much of Greenland still uses DST from 2024 on.
     America/Yellowknife now links to America/Edmonton.
     tzselect can now use current time to help infer timezone.
     The code now defaults to C99 or later.
     Fix use of C23 attributes.

   Changes to future timestamps

     Starting in 2023, Egypt will observe DST from April's last Friday
     through October's last Thursday.  (Thanks to Ahmad ElDardiry.)
     Assume the transition times are 00:00 and 24:00, respectively.

     In 2023 Morocco's spring-forward transition after Ramadan
     will occur April 23, not April 30.  (Thanks to Milamber.)
     Adjust predictions for future years accordingly.  This affects
     predictions for 2023, 2031, 2038, and later years.

     This year Palestine will delay its spring forward from
     March 25 to April 29 due to Ramadan.  (Thanks to Heba Hamad.)
     Make guesses for future Ramadans too.

     Much of Greenland, represented by America/Nuuk, will continue to
     observe DST using European Union rules.  When combined with
     Greenland's decision not to change the clocks in fall 2023,
     America/Nuuk therefore changes from -03/-02 to -02/-01 effective
     2023-10-29 at 01:00 UTC.  (Thanks to Thomas M. Steenholdt.)
     This change from 2022g doesn't affect timestamps until 2024-03-30,
     and doesn't affect tm_isdst until 2023-03-25.

   Changes to past timestamps

     America/Yellowknife has changed from a Zone to a backward
     compatibility Link, as it no longer differs from America/Edmonton
     since 1970.  (Thanks to Almaz Mingaleev.)  This affects some
     pre-1948 timestamps.  The old data are now in 'backzone'.

   Changes to past time zone abbreviations

     When observing Moscow time, Europe/Kirov and Europe/Volgograd now
     use the abbreviations MSK/MSD instead of numeric abbreviations,
     for consistency with other timezones observing Moscow time.

   Changes to code

     You can now tell tzselect local time, to simplify later choices.
     Select the 'time' option in its first prompt.

     You can now compile with -DTZNAME_MAXIMUM=N to limit time zone
     abbreviations to N bytes (default 255).  The reference runtime
     library now rejects POSIX-style TZ strings that contain longer
     abbreviations, treating them as UTC.  Previously the limit was
     platform dependent and abbreviations were silently truncated to
     16 bytes even when the limit was greater than 16.

     The code by default is now designed for C99 or later.  To build in
     a C89 environment, compile with -DPORT_TO_C89.  To support C89
     callers of the tzcode library, compile with -DSUPPORT_C89.  The
     two new macros are transitional aids planned to be removed in a
     future version, when C99 or later will be required.

     The code now builds again on pre-C99 platforms, if you compile
     with -DPORT_TO_C89.  This fixes a bug introduced in 2022f.

     On C23-compatible platforms tzcode no longer uses syntax like
     'static [[noreturn]] void usage(void);'.  Instead, it uses
     '[[noreturn]] static void usage(void);' as strict C23 requires.
     (Problem reported by Houge Langley.)

     The code's functions now constrain their arguments with the C
     'restrict' keyword consistently with their documentation.
     This may allow future optimizations.

     zdump again builds standalone with ckdadd and without setenv,
     fixing a bug introduced in 2022g.  (Problem reported by panic.)

     leapseconds.awk can now process a leap seconds file that never
     expires; this might be useful if leap seconds are discontinued.

   Changes to commentary

     tz-link.html has a new section "Coordinating with governments and
     distributors".  (Thanks to Neil Fuller for some of the text.)

     To improve tzselect diagnostics, zone1970.tab's comments column is
     now limited to countries that have multiple timezones.

     Note that leap seconds are planned to be discontinued by 2035.

2023b:
The 2023b release of the tz code and data is available. It follows so
closely on the 2023a release because Lebanon's government announced that
Lebanon's spring-forward transition previously scheduled for the end of
this week has been delayed until April 20.

This release contains the following change:

   Briefly:
     Lebanon delays the start of DST this year.

   Changes to future timestamps

     This year Lebanon springs forward April 20/21 not March 25/26.
     (Thanks to Saadallah Itani.)

Codecov Report
Patch and project coverage have no change.

Comparison is base (f44632e) 67.78% compared to head (c6e6c4b) 67.78%.

:exclamation: Current head c6e6c4b differs from pull request most recent head 7dd7d65. Consider uploading reports for the commit 7dd7d65 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #65   +/-   ##
=======================================
  Coverage   67.78%   67.78%
=======================================
  Files           6        6
  Lines         832      832
=======================================
  Hits          564      564
  Misses        230      230
  Partials       38       38

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Enable Github Enterprise

this PR is to enable the library to work on GHE

@elsayed-atef Awesome :smile: I would like to confirm with GHE, is there any way to do for free?

@sotayamashita There's no fees from GHE side , once you create a github App and make your standalone deployment , you can use it

@elsayed-atef Sorry to be late. I will confirm how it works on GHE on this weekend.


Support Parent Tag Grouping

Is your feature request related to a problem?
No

Describe the solution you'd like
Today, we can group by tag for multiple spec files within the same directory. It would be nice to have the ability to group a set of those spec files together in one parent category instead of having to define separate APIs in the config.
The idea:
Add a x-parent-category option to the spec file(s) that includes a Summary (display in the sidebar) . With that option, a sidebar category would be created and the items of that sidebar category would be a concatenation of the sidebar categories for each tag in each spec file that shares the x-parent-category.
A simplified example:
I have spec files for my shop named Apple, Banana, Double Shot, Latte, Cortado . In Apple, all endpoints are tagged Apple, in Banana all are tagged Banana, etc... I would create a x-parent-category: "Fruits" which would be added to the Apple and Banana spec files. The generated Sidebar would then have a top level category: Fruits with items that is an array of the Apple sidebar category and Banana sidebar category. The same thing would happen for x-parent-category of Espresso Drinks
We'd See on the sidebar:
Fruits ▼

Apple ▼

buy apple
clean apple
eat apple

Banana ▼

buy banana
clean banana
eat banana

Espresso Drinks ▼

Double Shot ▼

buy double shot
drink double shot

Double Shot ▼

buy latte
drink latte

Cortado ▼

buy cortado
drink cortado

The main difference between what is there today would be that if x-parent-category was specified the generated sidebar would add the higher level category. If no x-parent-category is specified, there would be no difference in the output.

Describe alternatives you've considered

Additional context

Thanks @csestito!
Have you considered perhaps going a step further to define Docusaurus vendor extensions? Also, perhaps we could swap parent with root (since it would be the top-most category)?
For example:

x-docusaurus-root-category string
x-docusaurus-root-category-description string (could also contain MDX/MD)

Note that the description could be rendered as the categoryLinkSource along with the generated index

Update: Not going to fix this use case.
The parent grouping/groubBySpec is accomplishable with proper tagging and division of the spec files. This is a narrow use case and shouldn't cause us to rewrite the logic. It is best to keep the base groupByTags and allow the user to organize their specs or customize the sidebar in a way they'd like it to display.
If you'd like to group spec files together, put them in a directory together and use the sidebar to create the top level categories. If you'd like to group by spec file, make sure the spec file has all operations tagged with the same tag first in their tag array.
In the future we can look into grouping tags together, but for now it is best to leave it as is.


Monospaced font for text/plain long_description

Don't you think that would be nice to wrap project descriptions in text/plain with pre tag?
Close if duplicate. I'm really sorry, looking through over 400 issues of production system is beyond of my capabilities.

Hi, thanks for the issue. I think it makes sense, and I don't think we have an existing issue about this yet.
I've added the 'good first issue' label here.

Thanks! This would keep ASCII art intact.

Division of responsibility question:
Since the rendering task in warehouse will prefer the html column of a Release's Description, should readme_renderer return a text/plain object with
 tags wrapping the entire block over here, or should warehouse use Description's content_type and wrap during display, something like this?
diff --git a/warehouse/packaging/views.py b/warehouse/packaging/views.py
index c9ea1bc2..3ea3b731 100644
--- a/warehouse/packaging/views.py
+++ b/warehouse/packaging/views.py
@@ -90,6 +90,9 @@ def release_detail(release, request):
     #       already rendered content.
     if release.description.html:
         description = release.description.html
+        if release.description.content_type == "text/plain":
+            # Wrap as preformatted text to preserve whitespace.
+            description = f"
{description}
"
     else:
         description = readme.render(
             release.description.raw, release.description.content_type

My preference leans towards implementing in readme_renderer, but that does change the current output behavior for the readme_renderer.txt.render()

I would expect readme_renderer to continue 'rendering' plaintext as plaintext with no HTML -- I think it's up to the consumer (Warehouse) to determine what to do with that rendered output and if it needs to be wrapped.
So I think something like the diff you have here would be sufficient.

continue 'rendering' plaintext as plaintext with no HTML

The only transformations we perform on plaintext today in readme_renderer is replacing \n with HTML
 tags, so we're not not transforming it already over there. :grin:
Hence my preference for adding the
 prefixing over in the library vs warehouse, since we're already doing a little to make the content prepared for warehouse.

I think it's up to the consumer (Warehouse) to determine what to do with that rendered output and if it needs to be wrapped.

That makes sense in the grand scheme of how things work today, since the rendered output gets inserted into the html column that we're reading from, vs raw.
If we want to encourage the notion of: "plaintext gets non-transformed by the library and then transformed on warehouse", and still accomplish something like this cleanly, I've thought of a few things to make the overall behavior consistent:
alternative 1

change the library to not transform plaintext at all (a slightly breaking change to the .txt renderer)
continue to store the output in the html column like it does today (which is only slightly wrong)
apply proposed diff to wrap the plaintext-from-html column with
 - should automatically handle the \n newlines in the source content (adds a small cost to request-time)

alternative 2

change the warehouse to look at the raw description column for plaintext content and transform to
 on display (slightly different from my proposed diff, adds small cost to request-time)
only store raw for plaintext entries (would need to clear out older plaintext html column entries to make accurate)
tell the warehouse to not run plaintext through the library (no change to the library, leaving "incorrect" txt render behavior alone, could mark deprecated, but might have impact on other users like twine check, would need to verify.)

Both alternatives have tradeoffs and add a small amount of runtime cost, since instead of fetching fully-rendered HTML from a column, there's a bit of extra transformation needed to the raw.
I'm leaning towards alternative 2 since it ends up the most "correct" overall - curious to know what you think!
data
For fun, can we see how many descriptions are actually affected today? Something like:
select count(*) from release_descriptions where content_type = 'text/plain';

warehouse=> select count(*) from release_descriptions where content_type = 'text/plain';

 count
-------
  6328
(1 row)

Thanks @di!
With that low amount of descriptions, I'm even more leaning towards alternative 2, since while it adds runtime cost, it's for so few items.

I'm not sure I totally follow the approach, in my mind we could just add a case statement to the Jinja template here that takes into account the content type.

@di I tried to make it clearer in #12408 - let me know if that makes sense, or if you see a better place to make this kind of change. After seeing the low count of plain descriptions, I'm inclined to leave the other steps  from "alternative 2" above alone.

This has been implemented. Due to the nature of how our description rendering works, these won't actually get updated until a new version of readme_renderer is released (although it's unrelated), we update the version of the dependency here, and we re-render all descriptions with that new version (which takes several days).


Failed to get chip id using getscom tool

getscom tool failed to identify the Chip ID on garrrison system, with the latest code
System Info:
bmc --> g68.aus.stglabs.ibm.com
lpar --> g68L.aus.stglabs.ibm.com
Build Level: 20151211n
from BMC:
cat /proc/ractrends/Helper/FwInfo
FW_VERSION=2.13.85625
FW_DATE=Dec 10 2015
FW_BUILDTIME=15:32:56 CDT
FW_DESC=8335-GTB SRC BUILD RR9 12102015
FW_PRODUCTID=1
FW_RELEASEID=RR9
FW_CODEBASEVERSION=2.X
tyan@g68L:~$ sudo /home/tyan/skiboot/external/xscom-utils/getscom -l

Chip ID
Rev
Chip type

80000015
DD2.0
Centaur memory buffer

80000014
DD2.0
Centaur memory buffer

80000005
DD2.0
Centaur memory buffer

80000004
DD2.0
Centaur memory buffer

00000001
DD1.0
Unknown ID 0xd3                         <--- Failed to identify chip type

00000000
DD1.0
Unknown ID 0xd3                         <--- Failed to identify chip type

msglog.txt

Should be closed as not updated for nearly 18 months. Please reopen if needed.


Current used Basemap is not going to be avaliable from 31. October

Feature description
Currently used basemap (Stamen Terrain) is not going to be avaliable from 31. October 2023 (see attached image).

Suggested solution
It should be used other basemap which is supported. Possible configuration could be found here.
Code snippets
No response

It is an upstream issue:

posted here

The issue is solved here

Fixed in #50


[WIP] Add option to client for SDK specific identifier

This is a WIP to propose an alternative approach to #710. I have to add a lot of stuff (tests, same stuff in the client builder) before proceeding, but I would like to ask if this approach seems good.

Hmm, I am not sure about this.
I don't really want that the user is able to overwrite the sdk identifer when initalizing a Client, it seems odd. Also we need to be able to change the version.
What about if we do something similiar like in #710 but instead of changing ClientBuilder so deeply
we are able to pass a ClientClass into ClientBuilder::create()->getClient($class)?
I really don't want that the sdk identifer / version is a option the user can set.
I am not seeing any other simple way than inheritance of Clients.

I think we can close this right?


AttributeError: 'csamtools.AlignedRead' object has no attribute 'tlen'

Hi,
I am using speedseq and an error occured:
Traceback (most recent call last):
File "/risapps/src6/speedseq//bin/svtyper", line 1044, in
sys.exit(main())
File "/risapps/src6/speedseq//bin/svtyper", line 1036, in main
args.debug)
File "/risapps/src6/speedseq//bin/svtyper", line 735, in sv_genotype
ins_hist_list[lib] = insert_hist(bam, lib_to_rg[lib])
File "/risapps/src6/speedseq//bin/svtyper", line 658, in insert_hist
or read.tlen <= 0
AttributeError: 'csamtools.AlignedRead' object has no attribute 'tlen'
Do you have an idea what's wrong?
Thanks!
Ming

This appears to be related to a pysam update that renamed several variables and removed backwards compatibility: http://pysam.readthedocs.org/en/latest/release.html?highlight=tlen#release-0-8-1
Could you tell me what version of pysam you're running? (The following should tell you:)
$ python
>>> import pkg_resources
>>> pkg_resources.get_distribution("pysam").version
'0.8.0'

`>>> import pkg_resources

pkg_resources.get_distribution("pysam").version
'0.5'`

It looks like I am using 0.5

Gotcha. I think this is due to old version of pysam lacking the "tlen" tag, which was added in v0.6:
http://pysam.readthedocs.org/en/latest/release.html?highlight=tlen#release-0-6

it looks like starting from version 0.8.1, several variable names are changed also:
http://pysam.readthedocs.org/en/latest/release.html?highlight=tlen#release-0-8-1

yeah, although the new versions have been backward compatible with legacy variable names so I have not encountered issues with newer pysam versions

pysam in our HPC is updated to 0.8.3 and when I run speedseq realign, it throws me same error
as here https://github.com/hall-lab/speedseq/issues/30
Because of this since 0.8.1? http://pysam.readthedocs.org/en/latest/release.html?highlight=tlen#release-0-8-1
Empty cigar now returns None (instead of [])

Traceback (most recent call last):
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 157, in
sys.exit(main())
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 153, in main
args.header)
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 64, in bamtofastq
if 5 in [x[0] for x in al.cigar]:
TypeError: 'NoneType' object is not iterable
samblaster: Version 0.1.21
samblaster: Inputting from stdin
samblaster: Outputting to stdout
samblaster: Opening temp/disc_pipe for write.
samblaster: Opening temp/spl_pipe for write.
[gzclose] buffer error
samblaster: Loaded 84 header sequence entries.
Traceback (most recent call last):
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 157, in
sys.exit(main())
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 153, in main
args.header)
File "/risapps/src6/speedseq//bin/bamtofastq.py", line 64, in bamtofastq
if 5 in [x[0] for x in al.cigar]:
TypeError: 'NoneType' object is not iterable
[mtang1@cnode338 bin]$ /risapps/rhel6/python/2.7.6/anaconda/bin/python2.7
Python 2.7.6 |Anaconda 2.0.0 (64-bit)| (default, May 27 2014, 14:50:58)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io and https://binstar.org
>>> import pkg_resources
>>> pkg_resources.get_distribution("pysam").version
'0.8.3'

ah right. someone else emailed me about this issue as well. I'll try to fix it

appreciate that!

Is this fixed? I am still having the same problem. My pysam is 0.8.4.

this should be fixed with https://github.com/hall-lab/svtyper/commit/33db6d3d7c3bc9b5ff83978581bbabe60d5d1df9, let me know if it doesn't work now


Scipy version update causes error importing 'bmat'

Hi, When importing imgaug i get the error cannot  import 'bmat' from 'scipy.sparse.sputils'. Looking at the traceback error shows that the file /opt/anaconda3/envs/deep_learning/lib/python3.8/site-packages/scipy/sparse/linalg/eigen/lobpcg/lobpcg.py is attempting to import bmat from ---> 24 from scipy.sparse.sputils import bmat.
bmat has apparently been moved to scipy.sparse.bmat.  Changing this line in the above file solved the error.
scipy = 1.5.4
python = 3.8.0
imgaug = 0.4.0

I have the same question, so how do you solve this problem?

Hey guys, any solutions ? I ran into this recently. Did not find any solutions elsewhere.

I just ran into the same issue after upgrading my scipy version.   I got
ImportError: cannot import name 'bmat' from 'scipy.sparse.sputils'
It turns out that this commit renamed scipy/sparse/linalg/eigen -> scipy/sparse/linalg/_eigen  When I upgraded the, old directory did not get deleted. I ended up with both _eigen and eigen.  Python was loading the the old version
I just renamed site-packages/scipy/sparse/linalg/eigen -> site-packages/scipy/sparse/linalg/eigenDeprecated in my installation which fixed the issue

the error happens because 'bmat' is moved to 'numpy'.
solution:  open 'scipy/sparse/linalg/eigen/lobpcg/lobpcg.py' and change 'import bmat from 'scipy.sparse.sputils' to 'import bmat from numpy'


memory.js: avoid creating a "cat" process

using a cat process to read a file just not makes any sense, changed to avoid the forking overhead.

@nahuel I now fixed it on several spots. In your pull request you used ascii in the fs.readFile() which actually was not clear to me (and I guess not necessary, right?)

@sebhildebrandt  /proc/meminfo is in ascii format, but ascii is a subset of utf-8, so is not really necesarry, it only makes the input format explicit.

@nahuel ok, understand ...


Cannot decrypt from env variable

Hello,
Can I use it to decrpyt value from Environment Variable?
I tried something like this:
spring.datasource.password=ENC(${DB_PASSWORD})
and I got an error : org.jasypt.exceptions.EncryptionOperationNotPossibleException: null
Thank you.

you could. Any property from any property source could be encrypted. I think you're passing the property the wrong way. you gotta do:
spring.datasource.password=${DB_PASSWORD}

And DB_PASSWORD should contain the "ENC()".
Another thing you could do is to just use SPRING_DATASOURCE_PASSWORD as your environment variable since Spring Boot will convert _ to . automatically.

Thank you so much, I have wrapped my value in the environment with ENC() and it's work as charm.
And for SPRING_DATASOURCE_PASSWORD, I'm running multiple spring application on my development machine, with different credential on each apps.


[WIP] Allow the use of an Arena for allocating Docs

This PR changes the way documents are created to allow them to be created with an Arena from typed_arena. By using an Arena instead of Box pretty printing (creation of Docs + writing the Docs) can get a speedup of up to 2x (see benchmarks).
Some bug fixes and ergonomic improvements are also included, see individual commits for details.

Already got merge access (thanks @freebroccolo) so I will merge myself when I am happy with it. Posting as a PR in any case to show the changes beforehand for anyone interested.
 Probably there should be no changes necessary for users of earlier versions but given the extent of the changes (and my relative unfamiliarity with the library) I'd rather be safe than sorry.

Awesome. Thanks for the improvements!


Different output compared to the Shadertoy website

The output of this code is different between the website and extension:
vec4 Circle(vec2 uv, vec2 pos, float radius, float blur) {
    vec4 col = vec4(.9, .65, .1, 1.);

    float dist = length(uv - pos);
    col.a = smoothstep(radius, radius - blur, dist);

    return col;
}

void mainImage(out vec4 fragColor, in vec2 fragCoord)
{
    // Move (0, 0) to the center of the screen.
    vec2 uv = fragCoord.xy / iResolution.xy;
    uv -= .5;
    uv.x *= iResolution.x / iResolution.y;

    // Draw the image.
    vec4 col = vec4(0.);

    vec4 circleTop = Circle(uv, vec2(0.,  .1), .2, .01);
    vec4 circleBot = Circle(uv, vec2(0., -.1), .2, .01);

    col = mix(col, circleTop, circleTop.a);
    col = mix(col, circleBot, circleBot.a);

    // Return the color of this pixel.
    fragColor = col;
}

Website:

Extension:

We blend the shader output into the webview that's opened, so the output alpha matters. What's happening here is that the alpha on the border between the two cirlces ends up being smaller than 1.0 thus the output will be blended. You have to fix this on your end, for example by adjusting your code like this
// Initialize to a background color
vec4 col = vec4(0,0,0,1);
// ...
// Mix only the color components, leave alpha untouched
col.rgb = mix(col.rgb, circleTop.rgb, circleTop.a);
col.rgb = mix(col.rgb, circleBot.rgb, circleBot.a);

Closing this since this is not an issue with the extension.


Support typescript files in the CLI

We should try to leverage typescript wherever we can and I'm seeing areas in the CLI that would benefit from it.  Since it supports gradual typing we don't have to convert it all at once - I'd like to just start writing new modules in typescript

This was implemented in #638


Added a new kotlin course

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
Add resources
For resources
Description - I added a new Kotlin course from the official Kotlin website
Why is this valuable (or not)? I believe the makers of the language, know how to teach it better.
How do we know it's really free? It is from the official Kotlin website.
For book lists, is it a book? For course lists, is it a course? etc. It is a course
Checklist:

[x ] Read our contributing guidelines.
[x ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Check for the linter errors.

Please follow the alphabetical ordering in order to pass the test cases.

@raj007-star Done!

Don't invent titles! Use the title given by the resource.

@eshellman I ddn't invent a title.

@eshellman Click the link and see that I did not invent a title

Thanks, and welcome to free-programming-books!


bug(windows): Plugging in my Ethernet adapter while on Wi-Fi still breaks it

Describe the bug
Even after #3335 merged, plugging in Ethernet messes something up.
To Reproduce

Connect Wi-Fi only
Start Firezone
curl https://ifconfig.net/ip, it works
Connect Ethernet
Curl again, doesn't work anymore

Expected behavior
Expected adding a 2nd connection to not disrupt Firezone
Screenshots / Logs
Log on internal Slack: https://firezonehq.slack.com/archives/C067DSY7TFX/p1706030258161169
On lines 127 ("time":"2024-01-23T17:16:11.4607156Z") and 131 haveInternet changes to false and then back to true when I connect the Ethernet. So we can detect that something happens, but we aren't automatically recovering.
Platform (please complete the following information):

Firezone Version 42a05e86e
OS: Windows 11

Additional context
Add any other context about the problem here.

refs #3343

Closing in favor of #3343

Not seeing this replicate on 127b97e after the big snownet merge 🥳


Caravel no data returned exception

Hi there,
Not sure if you are interested by I've changed a bit the way "No results" is managed.
I've kept as an exception but created new one NoResultsException, excpetion is returned in a custom header.
Changed the way visualizations notifies error, now they are passing the error object instead only the message.
Finally message is render with another class.

I think you need to rebase

Rebased.
Re ran npm run lint seems not to be working properly on my machine, trying to fix and enabling at PyCharm
I apology for the inconveniences.

Coverage decreased (-1.6%) to 70.714% when pulling 0c0b6f221a446cdeac5239742b7c76ceb93f18fc on gbrian:caravel_no_data_returned into da421bb9afd02b5919b1a30dac18840bc7ec02ad on airbnb:master.

This PR isn't right (attempting to delete files) reopen it when it's cleaned up

Ouch! Seems I did something wrong during "re-base" operation.
Now fixing and adding a test case.


fix: change URL for License Settings page, remove unused parameter fr…

Description
Change URL for License Settings page to /settings/license from /settings/billing, remove unused parameter from RestartPoll.
PR fixes following issue(s)
Fixes #https://github.com/appsmithorg/cloud-services/issues/1413
Type of change

Please delete options that are not relevant.

Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test


Fix PEP440 warnings in TravisCI

This was happening due to bad normalization of the package name in setup.py

Nope, that didn't fix it :(

@t8y8 are you referring to these errors?
/home/travis/virtualenv/python2.7.9/lib/python2.7/site-packages/pkg_resources/__init__.py:2510:
PEP440Warning: 'pbr (<IP_ADDRESS>.g5b3e942)' is being parsed as a legacy, non PEP 440, version. You
may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is
recommend to migrate to PEP 440 compatible versions.

  PEP440Warning,

These are coming from dependencies being installed by requests-mock, not from the way we are referring to it, from what I can tell.  In this example, it's complaining about pbr being versioned as <IP_ADDRESS>.g5b3e942, which, arguably, is a not so nice version number.

Since this cannot be fixed by us, I shall squint when I see those warnings.
Goodbye PR, I hardly knew ye.


Increase Efficiency: Use MPPT mode more often

The dcdc_control now better controls which mode (boost vs. buck) is being
used when: If configured in Buck mode, boost mode is never used.
The _dcdc_control function now "knows" if it is in boost or buck mode (dcdc_dir)
The no load condition now uses the dcdc transfer power as measure, not the out current
which is not reflecting the "no dcdc load" condition correctly if a load is connected
See #48

Sorry, took a bit longer to respond to this PR as I was on vacation.
Thanks for the PR. I thought about a slightly different approach introducing another DcBus type, but this seems to be the easiest solution for now.


Add alpha-3 listing to output

In addition to the alpha-2 listing for each country it would be nice to also have the alpha-3 listing.
This would be useful for drop-down lists using something like Select2 that allows for filtering.

Is this even possible with the CLDR or ICU sources? A quick perusal and I don't see alpha-3 at all. Would you have to separately query ISO 3166-1 to add that functionality?

@bsweeney Maybe there is a way. See https://github.com/symfony/symfony/issues/8492.
As for this project, I am not sure if we will ever support alpha-3.
I will check if there is a way to fetch it, feel free to suggest if you find a way.
Currently, I am working on a new version which will drop CLDR support.
Thanks.

What is CLDR support, and what does it mean to support it? I can get it in the dumps with the fips data where applicable.

@EvanCarroll This is CLDR, we currently only fetch data from ICU.

I'll look at getting this done.


CLA Manager is not able to view th company in V1 When CLA is signed from LFX portal or when CLA manager is added from LFX portal

Launch LFX portal
Login as contributor
Start the CLA process for the project that has not signed CLA
Complete the signing process
Login to V1 corporate console with the user details used in step2
Observed that company is not displayed for the user
In LFX portal for the project signed in Step4 add CLA Manager
Login as the added CLA Manager to V1 corporate console
Observed that company is not displayed for the user

@dealako
Could you please look into this issue as initial CLA Manager and CLA Managers added from LFX portal are not able to add approved list.

Observed that the initial CLA Manager who signed CLA from LFX portal is not able to see company in V1 Corporate Console

However the CLA Manager added from LFX portal is able to see the company

Blocked due to #1462

Verified that initial CLA Manager who signed CLA is able to see the company in V1 Corporate Console after signing CLA from V2 LFX Corporate Console

Verified that CLA Managed added from V2 LFX Corporate Console is able to see the company in V1 Corporate Console


Content no scrolls after switching tabs

Overview (Required)
Steps To Reproduce

Go to 'blog tab'
Click on 'home tab'
Scroll
can't scroll

Expected behavior
Can scroll
Screenshots
https://user-images.githubusercontent.com/1386930/110193863-e3079680-7e79-11eb-9412-ae829415d81f.mp4
Env:

Device: Pixel3
OS: 11.0
App Version or the branch main

Additional context

Probably, it may be related to this issue. 🙄
https://issuetracker.google.com/issues/176089198

This is working for me.

Thank you for reporting! I will close this issue 👍


Fix document path error

The origin path result in a 404 page:

please visit: https://www.streamxhub.com/zh-CN/


execCommand not needed in Firefox.

Hey,
I noticed you still have this code:
document.execCommand('enableObjectResizing', false, 'false');
document.execCommand('enableInlineTableEditing', false, 'false');

For some years now, Firefox should have changed its code to not require this any longer.

Thanks, I've removed it.


OpenAI-DotNet 8.2.1

Fixed a typo in the Azure OpenAI URL base endpoint

Thanks @sibbl !
Can you please buml the version to 8.2.1 and add the change notes the fix?

Unit tests pass locally. Should be good to merge.


Maintenance job - make maintenance operation for source provider independent on build directory clean up time interval

Currently maintenance operation is not being called if "Days to keep unused working directories" parameter is set as 0 (meaning that it should be kept forever)
Although removal of stale build directories and source folders maintenance are different routines - and maintenance of source folders should run even if removal of stale build directories is disabled.
Related issue - https://github.com/microsoft/azure-pipelines-agent/issues/3805
Testing/unit tests - in progress

changes were combined with unit tests in other PR: #3880


Request 'all environments' (aggregated) view of all nodes in PuppetDB

I am a heavy user of puppetboard and am testing out the new version with puppet4/puppetdb3. A 'feature' of older puppetdb/puppetboard is that all puppet nodes--from all environments--all show up. From what little I have read and observe, PuppetDB3 heavily classifies nodes by their environment, which may explain the puppetboard requirement to select an environment.
Could a new drop-down, like Environments --> All Environments, be added that would provide a view that shows nodes/facts/reports for all nodes in PuppetDB? This would be quite helpful in providing both technical and non-technical (ie management) people who use puppetboard answers to questions the older puppetboard provided. Thanks.

This request has been implemented with https://github.com/puppet-community/puppetboard/pull/185/files. It awaits the 0.1.2 release.

Excellent! I looked at open/closed issues and wasn't able to see a similar request. Thanks much for your work on puppetboard, it is extremely useful.


Passt with libvirt

What this PR does / why we need it:
Introduce follow up fixes to https://github.com/kubevirt/kubevirt/pull/10326
This change includes:

Use strconv.Itoa instead of fmt.Sprintf.
Use the calculated pod iface name.
Drop the attempt to redirect passt logs to virt-launcher log

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
This PR depends on #10326 and should be taken in only after than one gets merged.
Only the last 3 commits are relevant for review.
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:
NONE

/uncc kbidarkar  mhenriks phoracek
/cc AlonaKaplan ormergi

Original PR has been adjusted, closing this one.


feature request: ability to remove a template definition

Did you check existing requests?

[X] I have searched the existing issues

Describe the feature
A method to remove a template definition.
Or should we directly remove the definitions from the overseer.template.registry?
Provide background
I am trying to write my own project management and I don't want to keep my active template definitions when I switch a project.
What is the significance of this feature?
nice to have
Additional details
No response

It would be nice if there were a way to do this. They way I've handled it thus far is by adding a dir condition (seen here: https://github.com/stevearc/overseer.nvim/blob/master/doc/recipes.md#directory-local-tasks-with-exrc)
One note: this may not matter for your workflow, but it can get a little tricky because vim can set working directories per-tab or even per-window, making it more difficult to determine when you have "left" a directory.

I'd prefer to use plain templates, if that where possible. That would make the whole template management easier in my case.


Upgrade to Angular 6

It works with Angular 6, but I get these warnings:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Thanks for the report. I hadn't looked at Angular v6 yet. I will try to get to running tests with v6 and get a new release out soon


Wrong gradient for normals?

Hi,
In the paper the predicted normal is supervised with the gradient of the sigma MLP wrt the warped point x'

However, in the code, the gradient is computed wrt the input point x, instead of the warped point x'. Is this the correct behaviour?

Thank you for your question.
The gradient used to supervise the norm prediction is controlled using model.norm_supervision_type.
When its value is 'direct', the gradient wrt x is used.
When its value is 'canonical', the gradient wrt x' is used.


--preview, --preview-if-missing result in copy errors if item with same name exists

Did the upgrade, thank you.
tried download missing and got this error for every photo. Two videos did come through though. Very weird.
This was repeated for over 1000 photos. I ended up downloading the previews, which worked. I guess the iCloud is probably the main culprit
Error exporting photo (C82DF29C-E0E5-42E2-93E8-43A5872F1DF5: IMG_3310.HEIC) as IMG_3310.HEIC: Error Domain=NSCocoaErrorDomain Code=516 "“C82DF29C-E0E5-42E2-93E8-43A5872F1DF5_1_105_c.jpeg” couldn’t be copied to “photos” because an item with the same name already exists." UserInfo={NSSourceFilePathErrorKey=/Volumes/STORAGE/Editor/Photos Library.photoslibrary/resources/derivatives/C/C82DF29C-E0E5-42E2-93E8-43A5872F1DF5_1_105_c.jpeg, NSUserStringVariant=(
Copy
), NSDestinationFilePath=/Users/j****/desktop/photos/IMG_3310_preview.jpeg, NSFilePath=/Volumes/STORAGE/Editor/Photos Library.photoslibrary/resources/derivatives/C/C82DF29C-E0E5-42E2-93E8-43A5872F1DF5_1_105_c.jpeg, NSUnderlyingError=0x7fbda9b3e600 {Error Domain=NSPOSIXErrorDomain Code=17 "File exists"}}
Originally posted by @digital821 in https://github.com/RhetTbull/osxphotos/discussions/435#discussioncomment-1360870

This only happens if the original is missing

If original is missing, the logic to increment the filename never increments because the original file is missing:
https://github.com/RhetTbull/osxphotos/blob/c429a860b1ebeb77f3c3e36e9660fc9153d85d11/osxphotos/photoinfo/_photoinfo_export.py#L687-L697
But when the code gets to here, the preview file does exist and name never got incremented:
https://github.com/RhetTbull/osxphotos/blob/c429a860b1ebeb77f3c3e36e9660fc9153d85d11/osxphotos/photoinfo/_photoinfo_export.py#L936-L958
The code should check to see if a preview is needed (and if the original is missing and download_missing isn't true) as part of the increment check.  If so and preview is present, increment the file name.


运行错误

Please describe what you were doing when this error happened.
Specifications

OS: win32
IPFS Desktop Version: 0.9.7
Electron Version: 6.0.12
Chrome Version: 76.0.3809.146

Error
Error: net::ERR_CONNECTION_RESET

Please upgrade to v0.13.2, feel free to reopen if the problem still occurs.