Function should support Message<T>

Is your feature request related to a problem? Please describe.
The message metadata is lost in source/function. People can not use these information for their computation.
Describe the solution you'd like
Similar as what was discussed in #4093, we should support using Message<T> as the input for a source or a function.
public class MessageFunction implements Function<Message<String>, String>> {
...
}

Describe alternatives you've considered
N/A

@sijie aren't we using the Context object to expose these items?
More specifically:
public Record<?> getCurrentRecord() {
        return record;
    }

Which will return a PulsarRecord
https://github.com/apache/pulsar/blob/master/pulsar-functions/instance/src/main/java/org/apache/pulsar/functions/source/PulsarRecord.java
that contains the information about the input message

@jerrypeng yes. there is already a getCurrentRecord. However the Record interface doesn't catch up the Message interface, hence there are a few fields are not added. e.g. publish time, schema version and redelivery count. As I mentioned in the discussion in #4093 , the problem of having two interfaces is that it is really hard to make them consistent with each other.
There are a couple of options here:

we catch up the interface in Record api. but the problem still exists since anytime people make changes to Message api. The metadata will be first lost at Record api until someone add it.

we add getCurrentMessage to return the current message.

the proposal here.

I don't have any strong opinion with any approach here. However if we take 3), we might be able to support Message<T> in java native function.

@sijie I am open for having inputs as Message, my only concern is for users to only have one way to get the contextual information about the input whatever that might be and not duplicating functionality in different parts of the functions code base. It just gets confusing not only for the user of functions but also developers when you can get the same info via different methods.
Alternatively, we could also add a getActualMessage() method to PulsarRecord.

Alternatively, we could also add a getActualMessage() method to PulsarRecord.

I am fine with this approach.

@jerrypeng If you hadn't started, could I try to take a hack at it?

@ConcurrencyPractitioner sounds good!  Thanks for taking this up!

@jerrypeng Cool, thanks!
Just to clarify one thing, are we just adding this new method or is there something else that needs to be done?

@ConcurrencyPractitioner just add this new method to PulsarRecord class for now.

Closed this issue since it has been supported in a different manner.


fix wrapper docs for background-url

background-image property was mistakenly used instead of background-url when describing Outlook issue.

I think it should be background image instead of background-image it makes a bit more sense than an url what do you think ?

Nvm i'll merge that thanks !


Remove API only mention ?

Unless I'm missing something, the feature can be configured using the Cloudflare Dashboard. API is still available but it's not "required" as the only way to configure Custom Error Response. Right ?

Hi @wolruf
I just checked and the feature is still API only. Are you referring to the error pages you can configure via Custom Pages?
Custom Pages is a different feature, less powerful than custom error responses -- it only depends on the status code returned by the origin server, and you cannot set up an expression to configure an error response for a subset of your traffic.
As stated in the custom error responses documentation, if you configure both, custom error responses will override Custom Pages.

Hi @pedrosousa I'm referring to custom error response (beta), that, I believe, is what is seen in WAF Custom Rule configuration

Hi @pedrosousa where can we document that a custom response for Block actions is a great way to have a maintenance page when such a maintenance is happening on the Origin server (in lieu of using the Origin server) ?

Let's track this internally first — I need to check with PMs what's our best recommendation for this use case.
I created PCX-5140 for this purpose.


Empty transaction list

Version 1.0.4+3123
FF v6.1.16
where
Add Transaction
action
Adding a transaction
expected
I expect the app to add the transaction and show it in the transaction list.
current
error (the entry is added though)
There are no transactions in the transaction list (white screen). The browser shows all transactions fine.

debuglog.txt

Yes, thank you!


[Feature request] Allow to set permission of package folder

Idea
If JD2 creates an folder for a package in the download folder, the permission is 770. It would be good if I the permission could be modified.
In my case, the output folder is a samba folder. I run the image in a rootless podmain container. The user, who is running the container is not a samba user. Therefore the folder needs ether the permission 775 or needs to be owned by my samba share group. I think setting the permission is much more easy.

You can use the UMASK environment variable to change the permissions of files/folders created by the container.  See https://github.com/jlesage/docker-jdownloader-2#environment-variables for more details.

@jlesage Thanks for the fast answer and sorry for the long reply.
I played around with the UMASK and it solves my problem. But I'm still a little bit confused. I set the UMASK variable to 0000 which means folders created via download packages or archive extraction have the permission drwxrwxrwx. But the files (direct downloaded or extracted from archive) have still permission -rw-rw-rw-. Before I used the UMASK=003 and the folders had permission drwxrwxr-- and the files had permission -rw-rw-rw-.
Is this behavior correct? The documentation is talking about files.

With a umask of 0003, created directories should have drwxrwxr--, but created files should have -rw-rw-r--, not -rw-rw-rw- as you mentioned.
umask applies to created files and folders.  I will update the documentation to clarify this.

Update: I need also to set the variable

With a umask of 0003, created directories should have drwxrwxr--, but created files should have -rw-rw-r--, not -rw-rw-rw- as you mentioned.
umask applies to created files and folders. I will update the documentation to clarify this.

Your are right. Submask 003 creates file permission -rw-rw-r-- and 000 creates file permission -rw-rw-rw-. It was my mistake.

Yes. I was only confused that folders are executable and files not. That makes sense, because folders needs to be executable that you can use cd. But for the first moment, it was confusing. I think, if you update the documentation the problem should be also solved for upcoming new user :-)


feat(select): add component

fixes https://github.com/material-components/material-components-web-react/issues/128

Codecov Report

Merging #169 into master will increase coverage by 0.47%.
The diff coverage is 99.15%.

@@            Coverage Diff             @@
##           master     #169      +/-   ##
==========================================
+ Coverage   95.82%   96.29%   +0.47%
==========================================
  Files          21       23       +2
  Lines         718      836     +118
  Branches       65       73       +8
==========================================
+ Hits          688      805     +117
- Misses         30       31       +1

Impacted Files
Coverage Δ

packages/select/NativeControl.js
100% <100%> (ø)

packages/select/index.js
98.71% <98.71%> (ø)

Continue to review full report at Codecov.

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

this might also be an issue: https://github.com/material-components/material-components-web-react/issues/165

TODO: Update main readme table of info


add seq data transfer tutorial notebook

Jira Ticket: MIDRC-146

New Features
Breaking Changes
Bug Fixes
Improvements
Dependency updates
Deployment changes

@m0nhawk to honor your request: LOL

I believe you were saying "necessary to make the output available".

Unless it's absolutely necessary to have the output available, I'd ask to remove it from the notebook.

removed output from the notebook 👍


Update release process documentation.

Summary
Update our documentation of our release process to better reflect what we do and what needs to be done.
Problem Definition
Our release process documentation was copied from the Cosmos-SDK and doesn't fully reflect our own process. It is also a little hard to follow.
The current process can be found in here: https://github.com/provenance-io/provenance/blob/main/CONTRIBUTING.md#release-procedure
Proposal
Provide more details about our release process, branches used, and their purposes.
Provide steps/checklists for various things that need to be done during a release.
Create an issue template that can be used to easily create a release checklist issue.
Consider writing scripts to help automate some of the steps. The scripts would need to only be helpers though. We'd need to be able to do those steps without the scripts if needed.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Some pre-release checklist items:

A new Upgrade handler has been created.
The Upgrade handler calls RunMigrations.
Third-party protos updated.
Swagger docs updated.

There's definitely more to add, but I just wanted to not forget those ones.


RFC: Modular testing

This change encapsulates tests into their own files. Each yaml section
in the configuration file corresponds to a module in the tests/
directory. This has the following advantages:

The logic of individual tests can be contained within its own
module/class.
The ovn_tester.py file can be made smaller, allowing for it to be the
orchestrator of tests, rather than holding test logic.
New tests can be defined without needing to modify ovn_tester.py. Just
add the new module to tests/ and as long as the configuration is
present, the new test will be run.
This allows for customized ordering of test scenarios.
This allows for test scenarios to be skipped if desired.

In this change, the cluster bringup test is handled in a special way. It
is run directly in ovn_tester.py since it must be run as the first test.
This could be made a bit less awkward by changing the config file
schema, but I sought to make this change not break things for people if
possible.
Signed-off-by: Mark Michelson<EMAIL_ADDRESS>

@putnopvut Could you, please, reopen this and target the master branch instead?  Thanks!


Fix IssueCopyCommandTest logic about the target adapter

Hello,
As discussed in the #546 PR, there is a problem with the destination adapter test logic.
Indeed, in the unit test, we start with the idea that the issue tracker to test is the one linked to the Application. With the recent updates it's not the case anymore. If the copy destination is not the same as source, we must create an adapter.
I think that we must need to allow retrieving the destination adapter when it's necessary to test directly on it.
To be discussed :smile:.

Basically what we need is a mocked storage (not kept in the TestAdapter) which keeps track of the issues.

Nice idea, it'll help check all the things easily.


Start to use the upgrade-hooks pkg

Put the work together from https://github.com/istio/operator/pull/385 and https://github.com/istio/operator/pull/348.
Using the new upgrade-hooks pkg in upgrade command, remove the old one.

@elfinhe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
c503f2f4f2f5055bb1773213a145c426acbfbb67
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
6fbc477d3677a4badde49a266c97843473a57e3d
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
1b3c9271e37bd2caf16220743b90f3931fdcf3dd
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/cherrypick release-1.4

@elfinhe: new pull request created: #405

In response to this:

/cherrypick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Running the current scene (instead of the default scene) is impossible in the Android editor

Godot version
4.0.2
System information
Xiaomi Pad 5, Adreno 640, Compatibility mode
Issue description
Good evening,
As the issue's title says, It doesn't seem possible to run a current scene in Godot's android editor. When trying to do so, it'll run the main scene that I've set for the project
Here's a video for a more visual representation:
https://user-images.githubusercontent.com/34092413/236132988-b8ddccf6-d5cc-4dd0-9126-83325483a565.mp4
Steps to reproduce
1-Make project
2-Set a main scene for the project
3-Ruin main scene, should start it right away
4-Make another scene and try to run it with the 'Run Current Scene' button
Minimal reproduction project
N/A

Did you try starting the game with that current scene again after it did not work the first time?
The Editor has known issues where the editor scene selection does not update the scene started with the "current scene" function correctly. Somehow it sticks to old and wrong scene but when you close it and use it again it works the second time.
If it behaves like that it is not an android specific issue but a general issue that exists rightnow.

Just tried, and yeah, it does after a restart.
I've also realized that the debug settings (like the Show Collisions thing) also doesn't apply except after a restart. Is this related in some way?

I've also realized that the debug settings (like the Show Collisions thing) also doesn't apply except after a restart. Is this related in some way?

This is expected. The parameter is a command line argument that is only sent when the project is run, not continuously.

But I'm guessing that this isn't the intended behavior, right? To my knowledge, the 3.x branch has the ability to do that (correct me if I'm wrong)

No, it was always like that.

No i am preety sure on desktop you can enable show collision in the editor without restarting.


feat: Adds Greeting PR workflows

[x] Have you renamed the PR title to something meaningful?

Related Issue

Closes #224

Description

adds:

PR Raise message pr_raise.yaml
PR merge message pr_merge.yaml

How Has This Been Tested?

Screenshots (if applicable)

Type of Change

[ ] Bug fix
[x] New feature
[ ] Code style update
[ ] Breaking change
[ ] Documentation update

LGTM


Stale token in cloud-init-settings/kube-system-hetzner-kubelet-bootstrap-config

Just installed OSM creates a secret cloud-init-settings/kube-system-hetzner-kubelet-bootstrap-config, all working fine, but after an hour cloud machines cant add to cluster due to token in /etc/kubernetes/bootstrap-kubelet.conf is wrong
I found that bootstrap token (that creates by OSM) with TTL=1hour

root@us-west2-master4:~# kubeadm token list
TOKEN                     TTL         EXPIRES                USAGES                   DESCRIPTION                                                EXTRA GROUPS
j5s48n.sthmG832vjrfdxlr   59m         2023-11-21T15:11:00Z   authentication,signing   bootstrap token for kube-system-hetzner                  system:bootstrappers:machine-controller:default-node-token

This token OSM pod writes to cloud-init-settings/kube-system-hetzner-kubelet-bootstrap-config
First hour everything goes fine, cloud machines creartes and working fine
After this first hour cloud machines stopped add to cluster due to kubeadm token is stale and OSM pod couldnt write new token to cloud-init-settings/kube-system-hetzner-kubelet-bootstrap-config
I see such error in OSM pod log:

{"level":"error","ts":1700571426.160011,"caller":"osc/osc_controller.go:167","msg":"Reconciling failed","error":"failed to reconcile operating system config: failed to create bootstrap kubeconfig: secrets "kube-system-hetzner-kubelet-bootstrap-config" is forbidden: User "system:serviceaccount:kube-system:operating-system-manager" cannot update resource "secrets" in API group "" in the namespace "cloud-init-settings"","stacktrace":"k8c.io/operating-system-manager/pkg/controllers/osc.(*Reconciler).Reconcile\n\tk8c.io/operating-system-manager/pkg/controllers/osc/osc_controller.go:167\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\tsigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235"}

I found that there are no permissions to update this token: https://github.com/kubermatic/machine-controller/blob/main/examples/operating-system-manager.yaml#L1154-L1158
After I added an update verb cloud-init-settings/operating-system-manager role the secret cloud-init-settings/kube-system-hetzner-kubelet-bootstrap-config going to be updated and fixed this issue
Is it a bug? I think you need to add an update verb to role "cloud-init-settings/operating-system-manager"

That looks like a bug indeed in the example manifests indeed. Would you be interested in submitting the change, as you correctly identified what needs to be changed?

/remove-lifecycle rotten


Search improvements

Fastpages provides search features built with lunr.js, thanks @hamelsmu!
Following up on the initial version, Hamel asked if there's a way to improve it, and provided Just the Docs repo as an example. Here are a few things that would be great to improve:

[ ] Make sure site load speeds stay fast by decoupling search indexing from the layout.

Just the Docs, interestingly, doesn't build the index on every page, but provides a JSON with the site content that the site front-end can grab when the user say focuses the search field: https://github.com/pmarsceill/just-the-docs/blob/master/assets/js/search-data.json

[ ] Add excerpts highlighting in the search results page.

Here's the Just the Docs version of this, it's pretty sophisticated. We don't need it to be that fancy, but we want each search result to have the matched post title, and the paragraph (or part) with the matched words highlighted, rendered in the search results. If something in the code block got matched — than the corresponding code block, or it's reasonable part (indent-based?) should be rendered.
Bonus points:

[ ] Clean up, vendor, and make a clear guide on JS dependency management.

What libraries is fastpages using, how do we bundle them up, and should we maybe introduce a minimal JS bundler (parcel?) to manage the front-end deps?

Here are 2 examples: Jekyll theme with instant full text search and have keyword highlighting and context. Hope this is useful.
https://simpleyyt.com/ ,search "is" for example.
https://github.com/simpleyyt/jekyll-theme-next
https://blog.tmaize.net/pages/search.html ,search "ssh" for example.
https://github.com/TMaize/tmaize-blog

@Briy09 Thos examples are great, but would need some help with english translation as I don't know what to put in some places.  Would you be up for attempting a PR on this?

@Briy09 : after some exploration, I don't think we can use those examples, because they involve idiosyncratic code that I don't understand, and would be hard to maintain.  It would be safer to build something on an open source framework for longevity, like lunr.js
Here are some resources on more robust lunr.js resoruces:
https://dnoneill.github.io/jekyll-lunr-js-custom-search/docs/quickstart/frontend.html
and This example https://pmarsceill.github.io/just-the-docs/docs/search/  (which is linked above)

This has been closed by https://github.com/fastai/fastpages/pull/164


Long division broken on AVR 8-bit

Long division is at the moment broken on the AVR 8-bit target. The error is in an unknown location in the Knuth division algorithm and the benchmark test fails on the embedded controller. Other platforms such as PC and ARM do not seem to be influenced by this issue.

This was actually a stack overflow problem on the little 8-bit target that had a 768 byte stack. Re-organization of some static constant values from character strings to 32-bit integer arrays solved the problem.
Although division and remainder did not have any problen in the first place, added tests have been added for the modulus function as well as division.


Tabline color broken after revision 3d667c3

environment

vim: nvim 0.1.4
vim-airline: 5ee2cd9
OS: osx

if you are using terminal:

terminal: iterm
$TERM variable: screen-256color
color configuration (:set t_Co?):

when does that happen?

I've noted broken revision

vim-airline: 5ee2cd9

Oh, it happens on startup right away.

I did read that, but cannot verify it. That's why, I'd like to see some more information, e.g. your configuration

does it happen in Vim?

I don't know, I use neovim only.

" Airline settings {{{
let g:airline#extensions#whitespace#checks = []
let g:airline#extensions#hunks#enabled = 1
let g:airline#extensions#hunks#non_zero_only = 1
let g:airline#extensions#branch#displayed_head_limit = 13
let g:airline_section_warning = ''
let g:airline_section_error = ''
let g:airline#extensions#branch#format = 2
let g:airline#extensions#branch#enabled = 1
let g:airline#extensions#tabline#show_close_button = 0
let g:airline#extensions#tabline#buffer_nr_show = 0
let g:airline_skip_empty_sections = 1
let g:airline#extensions#tabline#fnamemod = ':t'
let g:airline#extensions#disable_rtp_load = 0
" let g:airline#extensions#syntastic#enabled = 0
let g:airline_detect_iminsert=1
let g:airline#extensions#tmuxline#enabled = 0
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#show_tabs = 1
let g:airline#extensions#tabline#show_buffers = 0
let g:airline#extensions#tabline#show_tab_nr = 0
let g:airline#extensions#tabline#show_splits = 1
let g:airline#extensions#wordcount#enabled = 0
let g:airline_powerline_fonts = 1
let g:airline_theme='bubblegum'
" }}}

and I use Plug 'chriskempson/base16-vim' as my vim color scheme.

does it work if you set let g:airline_skip_empty_sections = 0

No, the same issue.

That is interesting, because the change that you bisected, depends on the fact that this setting is set to 1. Well, it would be nice, if you could check, whether this happens in vim as well.

The last good revision was 513afd2. My bisect says that this is the first bad commit 3d667c3.

you said that before. That does not help. Please check with Vim.
Commit 3d667c3 should only affect you if g:airline_skip_empty_sections is 1. That's why, I am surprised this does not change, if you reset that option.

I see that this var is 1 when I echo it, and your setting does nothing. Does this help?

no

Why let g:airline_skip_empty_sections = 0 has no effect?

yes

okay, i am going to close this as not reproducable.

please check #1276

@chrisbra Now I get this error message in vim
The airline statusline funcref function('airline#extensions#neomake#apply') has already been added.

Hi yevhen-m!
On Di, 27 Sep 2016, yevhen-m wrote:

@chrisbra Now I get this error message in vim The airline statusline funcref function('airline#extensions#neomake#apply') has already been added.

That is a different error and has nothing to do with this issue.
I suppose you need an update to neomake


[Feature request] Improve documentation for MlsGroup

Is your feature request related to a problem? Please describe.
The documentation for MlsGroup is almost non-existent.
Describe the solution you'd like
More docs!
Describe alternatives you've considered
None
Additional context
None

This was related to CoreGroup, so it is no longer needed.


Rails 5

Updates the existing rails5 branch to pass the test suite.
I added an extra Gemfile and modified the travis.yml to run tests against the previous major versions of rack (1.x.x) and actionpack (4.x.x) in addition to the latest versions (rack 2.x.x / actionpack 5.x.x), to ensure compatibility with both sets of dependencies.

@thejamespinto LGTM and you?

superseded by #150

Closed in favor of #150

Closed in favor of #150


Write tests

Do you have a preferred CI service? If not I would just start with Travis and Coveralls. Is this ok for you?

@Art4 Yes, that would be fantastic! :+1:

Resolved in #8


./said must bu root ??!!

**go version 1.10.2
**go get ..
And then
./siad -M cgtwe -d /data/Sia --api-addr "xxx:9900" --authenticate-api --disable-api-security
~$ Enter API password
Sia Daemon v1.3.2
WARN: compiled without build commit or version. To compile correctly, please use the makefile
Loading...
listen tcp xxx:9900: bind: cannot assign requested address
xxx is my IP
And, If I use sudo ./siad ....
This is OK . why??

That port might already be in use by another application.

which port must be unused？No application use port 9980

You specified the custom port 9900 in your description.


Get Mapillary Detections under a poweruser feature flag

Description
After speaking with Said about the object detections feature branch, we'll put it under a 'power user' feature and enable it in Rapid v2.

This work needs to be rebased on top of main, as it currently lives in the 2.0-derived branched called mly_objects_v2.

It would be a much nicer experience for the user if we could constrain the display of imagery points to ONLY those images that show a particular detection. This would greatly cut down on the visual clutter for mappers.
Bonus points: While an object is selected, the forward / backward < / > Buttons in the UI should go through the images that spot the object, not just advance the current road sequence.  This would allow mappers to get a really quick contextual understanding of the feature and its alignment/correctness.

Conulted with @cbeddow about this, he did some research on the topic of 'only showing images that contain a detection', which would allow us to filter the images we display when an object is clicked.
According to his notes:

https://graph.mapillary.com/$MAP_FEATURE_ID?access_token=$TOKEN&fields=images

^ gives list of image IDs for that object, API Docs here: https://www.mapillary.com/developer/api-documentation#map-feature

Also:
https://graph.mapillary.com/$MAP_FEATURE_ID/detections?fields=value,image,geometry

For a map feature, this API call gives each image and detection geom, which I think is best displayed as a bbox of the detection in a bright color and not the unsimplified outline
^ right now I think we display too many detections (all of the outlines) and it would be better to get the bbox


Twim: Implicitly copy buffer into RAM if needed when using embedded hal traits

Issue #150

Could you be so kind and run cargo fmt such that the CI is happy?


Brain cropping fails with dynamic datasets

The following error occurred after using Moose with dynamic datasets of Vision lung cancer patients. All other segmentations and SUV extraction properly worked. No error occurred after re-running Moose with the corresponding static dataset.
Brain found in field-of-view of PET/CT data...
- Cropping brain from PET image using the aligned CT brain mask
Traceback (most recent call last):
  File "/usr/local/bin/moose", line 215, in <module>
    cropped_pet_brain = iop.crop_image_using_mask(image_to_crop=pet_file[0],
  File "/home/mz/Documents/Softwares/MOOSE/src/imageOp.py", line 237, in crop_image_using_mask
    out_of_bounds = upper_bounds >= img_dim
ValueError: operands could not be broadcast together with shapes (3,) (4,)

It looks like the error occurs due to the dimension mismatch with the PET image. Just discarding the fourth dimension should resolve that issue if 4D data is a legit input for MOOSE.

Guys, this is a duplicate issue. Closing it. Refer the previous issue here: https://github.com/QIMP-Team/MOOSE/issues/30


Change None to Fan for Purifier and add Favorite levels

Is is possible to change preset mode None to Favorite and   add Favorite Levels for Purifiers (0 to 14 for 3H) as per official miio integration.
During the last month the scan interval for official Miio integration was increased from 10s to 60s making it unusable for the community lovelace card. So MIoT is a valid alternative to replace the official integration.
Also we have noticed a lot of unavailable periods with the official integration that are not noticed in MIoT
https://community.home-assistant.io/t/lovelace-xiaomi-mi-air-purifier-3h-card/192100/187

Hello,
I've checked your device (zhimi.airpurifier.mb3), it is a native MIoT device and it exposes all its properties. It has 4 modes and the component shows them as-is. There is already a Favorite mode and how does None mode work? Additionally, since I don't have this device, what does Favorite Levels for Purifiers (0 to 14 for 3H) mean? Could you please describe how does this option work?

Hi. here are some screenshots from the Mi Home app.  Indeed there are 4  modes: Auto, Night (renamed Silent or Sleep depending on the integration), 3 levels of ventilator (could be found under Fan option in Miio or None in MIoT) and finally Favorite. For Favorite in the native android app Mi Home you have a sliding bar with 14 covrage options. Those coverage options were translated in Miio into 15 levels and for each value correspond a certain ventilator speed and fan level.
Coverage
0   - 2-4 m²
1   - 5-9 m²
2   - 7-12 m²
3   - 12-22 m²
4   - 14-24 m²
5   - 14-25 m²
6   - 16-27 m²
7   - 17-30 m²
8   - 18-32 m²
9   - 19-33 m²
10   - 20-34 m²
11    - 22-38 m²
12    - 23-40 m²
13    - 26-45 m²
14    - 28-49 m²


vep-1416: Address feedback and update proposal

This change addresses feedback received during previous reviews of vep-1416, and updates diagrams and document sections. More details about the vdk-jobs-troubleshooting plugin are added, as well as a section describing the HTTP server used by the thread-dump utility.
Testing done: N/A
Signed-off-by: Andon Andonov<EMAIL_ADDRESS>

Thank you for the reviews, @murphp15 @duyguHsnHsn


BruteForce protection

Hello,
I was wondering if it would be possible to block IPs/users that fail to login X times within a specific period. Also maybe store that info somewhere so the admin is aware of the attack?
Thank you!

This feature is not yet implemented but I plan to add an optional 2 factors authentication.

@jsmith000 using http://www.fail2ban.org
Example with wordpress:  http://serverfault.com/questions/614599/fail2ban-to-block-wordpress-brute-force-attacks-on-wp-login-php

There is now a bruteforce protection into the development version see
https://github.com/fguillot/kanboard/blob/master/docs/bruteforce-protection.markdown


[BACKPORT] add stm32h755II chip

Summary
Impact
Testing
@jfbblue0922 - Here is the backport. The PX4 test to bring it in is here https://github.com/PX4/PX4-Autopilot/pull/23265

@julianoes - Would you please on the HW you brought https://github.com/PX4/NuttX/pull/214 with?

I have verified it on V6X that the value written to STM32_PWR_CR3 is on changed from before this PR.

@davids5 so this needs testing with CubeOrange+, right? I don't have one with me at the moment.

cubepilot_cubeorangeplus_default.zip
Here is a .px4 file inside a zip to test this with @bugobliterator.

cubepilot_cubeorangeplus_default.zip
Here is a .px4 file inside a zip to test this with @bugobliterator.

Tested working.

@davids5
Thank you for your response.
I've tested it and found some issues, so I'll create another PR.


Bug: clone student-repos --page flag doesn't work for pages other than 1.

Cloning some large repos all together in the same command often fails due to a timeout from Githubs API.
Using the classroom CLI's built in page functionality could work, but specifying a page other than 1 results in the creation of an empty directory and nothing else.
Some screenshots redacted to prevent student information from being visible.
Cloning the first page of 5 assignments:
gh classroom clone student-repos -a 555555 --page 1 --per-page 5

Requesting the next page:
gh classroom clone student-repos -a 555555 --page 2 --per-page 5

The solution mentioned in issues https://github.com/github/gh-classroom/issues/13 https://github.com/github/gh-classroom/issues/12 will not work because github API times out the clone command after about 20 of these repos are cloned.
The offending call appears to be this one to the API: https://github.com/github/gh-classroom/blob/main/pkg/classroom/http.go#L36
It may be that the page parameter is actually asking the API to get the second page of assignments, instead of the second page of the submissions?

The comment that I made in the beginning of the post "Cloning some large repos all together in the same command often fails due to a timeout from Githubs API." does not appear to be true, but rather, network specific. On different networks, this command downloads all repositories fine.
Simply making the comment, that isn't the main point of this bug report, but important to clarify that it isn't the bug being identified.

I can confirm that the page argument doesn't seem to do anything past page 1. I have a new feature that I would like to contribute but am blocked due to this bug. This is also a show stopper for classes who have more than 100 students, so it would be awesome if  this could be prioritized
I think that this is the same issue identified in #13

Thanks for the report! We've opened an issue internally to fix it. @shanep, I'll make sure you get tagged in the PR that fixes it so you can open your PR for the "clone all" functionality (thanks for that, by the way, it will definitely alleviate pagination confusion!)

Hey folks! Turns out this was a bug in our pagination logic in our API -- we've since merged the fix and pagination should work properly!
cc @shanep

Fantastic, thanks for the quick attention!

Still getting a 500 error when i clone assignment and run "--per-page 70"


The 0.4 release

This issue is to track the work that we should get in as part of the 0.4 release. I'd appreciate it if responsible parties could chime in on when they expect to complete the work. This isn't intended to put pressure on anybody but will let me know if I should take over or push back some of these to the next major version bump. Thank you!
From me:

[ ] #108
[ ] #107
[ ] #101

The metric traits PR needs some reviews but I believe all work is (more or less) ready for merge.
From @Andlon :

[ ] LU rewrite ( #94 ).

I suspect we will need to push this one back to a 0.5 release later. Included in case you have some time to work on it soon.
From @c410-f3r :

[ ] #82
[ ] #78

I'd like a minor doc change on #82 but it can be merged without it. And there are some merge conflicts on #78 that needs resolving.

About #94: Yeah, you're right. I've been way too busy lately to finish this up any time soon. Hopefully I'll have time to finish it before 0.5 (ideally along with a reworking of the remaining decompositions too)!

@Andlon that's totally fine. I start my PhD program in January so I suspect I will be very busy too. That's why I want to try and get 0.4 out before then.
I'll note in the description that this one will be pushed to 0.5 .

All the major points are ready now for the 0.4 release. I still want to try and split out the slice module before merging. I'll handle impl_ops after. The reason for this is that I am moving the BaseMatrix traits into a new base module which is a breaking change (though I imagine most people use the reexport in matrix.
I need to fix conflicts with that and then will be looking to release! Thanks for your help all, in particular @Andlon and @c410-f3r .


Log OOMs

it checks the exit code of the process to know if it was OOM or a job that errored out and crashed

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (49a55cc) 90.58% compared to head (fb3eeaf) 92.45%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1862      +/-   ##
==========================================
+ Coverage   90.58%   92.45%   +1.86%
==========================================
  Files         234       83     -151
  Lines       14559     5948    -8611
==========================================
- Hits        13188     5499    -7689
+ Misses       1371      449     -922

Flag
Coverage Δ

jobs_cache_maintenance
?

jobs_mongodb_migration
?

libs_libapi
?

libs_libcommon
?

services_admin
?

services_api
?

services_rows
?

services_search
?

services_sse-api
?

services_worker
92.45% <84.61%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

services/worker/src/worker/executor.py
94.16% <84.61%> (-1.25%)
:arrow_down:

... and 151 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update to v0.14.0-rc3

Backlinking to purescript/purescript#3942

I'm not sure why CI is failing here...

I'm pretty sure it's because https://github.com/garyb/purescript-debug is not updated for 0.14. However, I don't see it used in the project, so I've dropped the dependency.


HMM model 2 broken

model 2 in the hmm example crashes with no error message when calling train_loss = elbo.loss(model, guide, sequences, lengths, args, include_prior=False) on cpu. the other models seem to work fine.

Can you please add steps to reproduce? It surprises me since all models should be tested via tests/test_examples.py

python examples/hmm.py --model 2 [-n 1]
@neerajprad verified that it works on pytorch master but breaks on release for both python 2 and 3.

The reason the tests do not fail is that the tests run truncated versions --truncate 10 and the error is not triggered when truncating. Reasons we run tests truncated include:

truncated tests run faster
until #1521 is merged, non-truncated tests will only pass on PyTorch 0.4 CPU (fail 0.4 GPU, 1.0 CPU, and 1.0 GPU)


Access nth element of an array

I couldn't find a mailing list, so here goes:
I'm trying to access only the first element of an array in my template:
{#people.0}
  Hello, {name}
{/people.0}

However, that gives me a syntax error. Is it possible to access only the first element, or do I need to write a function for this?
Thanks for a great lib!

+1


Fix Build Cake

Expected Behavior / New Feature
New PR are passing CircleCI
It seems https://github.com/ThreeMammals/Ocelot/pull/1436 can fix this
Actual Behavior / Motivation for New Feature
CircleCI fail with errors - new PR checks are failed

Steps to Reproduce the Problem
Just add new PR
Specifications
Github

Everything is fine with our build script.


[react-aria] FocusScope with contain doesn't show focus ring on nested focusable elements

Provide a general summary of the issue here
I've run into this issue (which may be similar to #4288) wherein the focus ring does not show for elements nested within a tabindex="0"
Works fine within Firefox.
🤔 Expected Behavior?
Both the elements with tabindex="0" and nested elements which are keyboard-focusable should have a visible difference when focused via keyboard
😯 Current Behavior
Only the element with tabindex="0" is visible focused
💁 Possible Solution
No response
🔦 Context
I'm making an error summary within a modal, because of this issue it's failing accessibility tests, as there is no visible focus state.
🖥 Steps to Reproduce
I have a minimal reproduction here
import { FocusScope } from 'react-aria'

export default () => (
  <FocusScope contain>

Try clicking on me, then pressing tab

      I'm focusable, but I won't have a focus ring

  </FocusScope>
)

Version
3.33.1
What browsers are you seeing the problem on?
Chrome, Safari
If other, please specify.
No response
What operating system are you using?
MacOS
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Adding tabindex="0" in the link in my example seems to fix the issue for me


Page cant be loaded when using on FB or Messenger android

running this while on the fb native app
html2pdf().from(element).set(opt).toPdf().save().then(function(pdf){
says Page cant be loaded.

is there a way to open default browser, before we run html2dpf?


security/acme-client: add support for Domeneshop DNS API

Please add support for Domeneshop. Link below to acmesh-official.
https://github.com/acmesh-official/acme.sh/wiki/dnsapi#85-use-domeneshop-dns-api-to-automatically-issue-a-cert
https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_domeneshop.sh
Thank you!

Hi. Any progress on this?
I use domeneshop  as my registrar and I am using this on pfsense at the moment.
I cannot contribute codewise but I can test this implementation of needed as I am transitioning to opnsense.

This will be available in the upcoming release 2.6 of os-acme-client.


Design & UI Issues - October 2022

Remaining legacy issues from the last thread:

[ ] https://github.com/OdyseeTeam/odysee-frontend/issues/1608#issuecomment-1149065058
grid + wild west = uneven tiles (at least on 6 wide)

[ ] Button overflow

A combination of button being too verbose + general i18n problem :(

[ ] Mobile header title

[ ] chat goes to 2 lines when moment rolls over

[ ] Share Modal > Embed > Light Theme -- copy button text color incorrect

[ ] Need padding on the comment filters in various layouts

p/s: Is the filter in mobile slightly too high (w.r.t. it's font size)?

Livestream incognito ... need padding

Google mobile report
https://odysee.com/$/search?q=VINCENT REYNOUARD

[ ] Truncate channel name in selector

[ ] On Auto, the p of the 1024p is moved the the next line on this claim

https://odysee.com/$/top?name=blah

Unbalanced border radius between left and right  side?
Close if intentional -- probably to account for the rounded pin.

Ad placeholder exposed when localized text wraps

Weird LBC icon placement on mobile / my res.

[ ] Last line of longer text gets cut on the membership cards, tested on both Firefox and Chrome.

Tier selection margins in mobile

join button alignment

in full screen mode, chat disabled

[ ] The three dots on syncs (claim page card) are a little bit too left, padding is missing?
Happens on both Chrome and Firefox

[ ] The stickers and emojis are shifted in the community tab on both Firefox and Chrome

[ ] There is a space missing in the "another livestream is running" notification

[ ] Tags are hard to read while creating a new channel:


Revert "Update dagger to v2.43.2"

Codecov Report

Merging #484 (2edcd9e) into main (c82c65d) will increase coverage by 0.03%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main     #484      +/-   ##
==========================================
+ Coverage   73.73%   73.77%   +0.03%
==========================================
  Files          83       83
  Lines        4356     4354       -2
  Branches     1030     1029       -1
==========================================
  Hits         3212     3212
  Misses        393      393
+ Partials      751      749       -2

Impacted Files
Coverage Δ

...kotlin/com/alexvanyo/composelife/ui/theme/Theme.kt
56.41% <ø> (+1.41%)
:arrow_up:

...n/kotlin/com/alexvanyo/composelife/MainActivity.kt
57.14% <80.00%> (+1.58%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Extension: Refactor routed message types

We need to refactor the messages that are handled by ExtensionRouter and Router. Currently, the type of message is a bit unclear to the developer, and should be consolidated into a strongly typed class.
TODO

Refactor Router, ExtensionRouter, Message, and MessageRegistry so that all messages can be both strongly-typed and still provide the same functionality in all cases. This will requiring defining a type to replace what is currently used (See notes below)
Move Message.type() => string to a field, assigned to a MessageType enum defining all possible, valid message types
Clean up message handling, and reduce complexity wherever possible (current implementation feels a bit scattered)
Ensure that yarn lint passes with no errors or warnings. Currently, the few instances where any is used and generating a warning are disabled to track new linting errors - these are marked TODO in the source
Ensure that in cases where unknown is required, that types resolve properly before compilation
Introduce generic type arguments where necessary
PushEventDataMsg should be refactored to more closely follow what other Message classes are accepting as arguments

We could introduce a Props<T = string | number> Record<string, T> type for arguments, which may make for a better experience with varying types of arguments passed to Message constructors
Alternatively, PushEventDataMsg could be updated to accept arguments as other Message instances are (where (...args: unknown[]): Message<unknown> would be valid - currently, this doesn't work in this particular case)

Notes

The message should be able to be passed into the Router.registerMessage() method without needing any

Look at PushEventDataMsg, which accepts an object - TS will complain if passing a type of unknown to the constructor with this requirement, so we  may need to use Generic type arguments to handle this case
In MessageRegistry we have msgCls: { new (...args: T[]): Message<unknown> } & { type(): string } - This should be a strongly-typed, shared interface

One thing that is quite confusing to the developer is the distinction between a Message<unknown> (which could be of any type of message as defined in the background services), and the messages handled by the Router and ExtensionRouter, where a Message is wrapped in the following structure:
// apps/extension/src/router/types/router.ts
export type RoutedMessage<T = Message<unknown>> = {
  meta: {
    routerId: number;
  };
  msg: Message<T>;
  port: string;
  type: string;
};

I think this makes sense for now, but as a part of this task should be check that it is used in all cases where appropriate, and accounts for all scenarios (and such scenarios should be simplified so that something like the above works!) Also, see if we can't be more type-safe by providing an argument (currently, this generic defaults to Message<unknown>)

Closing


Don't fetch dev versions to render search result page.

lgtm - maybe we should have a golden file for the rendered search results page as well. wdyt?

maybe we should have a golden file for the rendered search results page as well. wdyt?

We do have that, but it isn't effected by this change:
https://github.com/dart-lang/pub-dartlang-dart/blob/master/app/test/frontend/golden/search_page.html


Phoenix script/css tags don't work

The following error is produced:
== Compilation error on file web/views/layout_view.ex ==
** (ArgumentError) cannot set attribute @conn inside function/macro
    (elixir) lib/kernel.ex:2189: Kernel.do_at/4
    (elixir) expanding macro: Kernel.@/1
    (ww) web/templates/layout/app.html.haml:1

From converting the script and link tags over to haml:
%script{src: "#{static_path(@conn, "/js/app.js")}" }
-# Also tried
%script{src: static_path(@conn, "/js/app.js") }

Is this a calliope bug?

Is this a calliope bug?

Yup. Needs to be handled on the calliope side. Thanks!


Draw Text inverting background video pixels?

I have a flutter widget with a Stack consisting a background video player and some flutter widgets (Text, etc) on top of it.
The text is white and looks good when the video is dart, however sometimes video is light and the text gets lost.
I realize that I can put a semi-transparent rectangle under the text, however it would be much nicer to invert background pixels when drawing text itself.
I think Canvas's blend operations can't be used here as the video is a separate widget.

Hi @duzenko, This issue doesn't seem to describe a bug or a feature request in the flutter framework. if You need help with your code please try using one of out forums at https://flutter.dev/community.
Closing as this isn't an issue with flutter if you disagree feel free to write in the comments and I will reopen it.
Thank you.


Implement AsRef and AsMut for str, [T] and some other unsized types

As discussed in #28
I've also made tests to make sure that we are getting what we really want to. On the other hand the functionality and implementation is so simple and straightforward, while the tests are a little bit clumsy (especially for AsMut<str>), so I'm hesitating on whether or not we should keep them.

Hi @cuviper ! Could you pls have a look at the PR?
I'm not really sure whom to invite to make a review (apart from you), maybe you have an idea whom else to ping?
Thanks!

Oh, now I see you already improved the "clumsy" tests.  I was thinking about the problem since you posted the PR, but hadn't checked to see that you updated it.  That definitely looks nicer.
Now I guess it's just a question of what unsized types we really want.
@bluss, any opinions?  In case you missed it, in #28 we found that going fully ?Sized would technically be a breaking change -- though it would probably not affect anyone in practice...

Omg, I've completely forgotten about other unsized types! xD
Do you think I should put implementations for them either?.. If yes, then I'd rather let people who need it for some specific standard types to make pull requests than to introduce another ton of copy-paste code into the library, taking into consideration that everything can be easily implemented with just a single question mark... and a breaking release :)

Macros can ease the copy-paste aspect of this, at least.

Added a couple of macros and implemented the traits in question for str, Path, OsStr and CStr

I'd love to do the ?Sized change, that's an oversight, but it's hard to see if it's possible to do. Generic is better than specific here.
Only PR comment is to update it so that it compiles with --no-default-features. Also an oversight that travis doesn't test that.

Will do later today, thanks for the hint!

Done!
Btw is it ok that I'm overwriting the same commit again and again? I can split the commits using my reflog if anybody finds it useful..

Just as a side question, why to maintain compatibility with rust-1.12?...

It's an open question in the Rust community.  Some consider it fine to only support the latest-stable rustc, and some think increasing the rustc requirement should be a breaking change.  This crate has chosen the more conservative position to maintain compatibility.

... yet another point to roll out 2.0 :))
(just kidding)
So, it there anything else to amend in the PR?

Hi @cuviper, @bluss
Do you think I can improve the patch somehow so it gets merged? :)

Sorry for neglecting this. I've just merged and published it as either 1.5.1.

No problem, there was no hurry or anything :) Thanks!


initial commit

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I believe this wasn't meant for this repo.


Spellchecking Readme.md

Proof-read the readme with thehelp of Grammarly.

Thank you for your contribution. Fixed in e80cc5d.


Update summary manifest to match content change

The label for one of the filters was changed in https://github.com/alphagov/digitalmarketplace-frameworks/commit/881734dc27cc5430267512142c72390193dc13e0
This was causing 500s in production because users were able to filter by something
that was not defined in the manifest.
This is an immediate fix. There is probably a longer-term solution that makes this more
robust

:+1: to this and :+1: to doing a longer term fix


Added missing _REGION substitution for Cloud Build Triggers

The deploy.yaml file uses the _REGION substitution for setting the region in various steps. When the build-containers trigger is pulled and doesn't have _REGION set, it errors out. This adds the missing _REGION substitution to the trigger with the value set by var.region
Fixes GH-403

/ok-to-test
needs CLA

Hi @krazykid. Please visit https://cla.developers.google.com/ to sign our CLA. If you have already done so, please respond @googlebot I signed it.

Hi @krazykid
It looks like you signed the CLA, but your commit is not tied to your email in GitHub. Please add your email address to your GitHub account and make sure you use that same email in your commits. Fortunately you only have to do this one time. Please let me know if you have any questions.

@sethvargo I guess I created the commit with my work email, but from my personal github account. I've updated my personal github account to include my work email address as a backup, but if you need me to flip it to the primary for this PR, and re-sign the CLA, I can do that too.

@googlebot I signed it!

@sethvargo I believe I've made @googlebot happy and the CLA is properly signed with my work email address now too.

/lgtm

/approve


Fix timeout handling (non-lazy handler)

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff          @@
##           master    #80   +/-   ##
=====================================
  Coverage       0%     0%
=====================================
  Files         106    106
  Lines        1412   1413    +1
  Branches       90     92    +2
=====================================
- Misses       1412   1413    +1

Impacted Files
Coverage Δ

.../rdbc/pgsql/transport/netty/JdkScheduledTask.scala
0% <ø> (ø)
:arrow_up:

...pgsql/core/internal/scheduler/TimeoutHandler.scala
0% <ø> (ø)
:arrow_up:

...sql/transport/netty/NettyPgConnectionFactory.scala
0% <0%> (ø)
:arrow_up:

...a/io/rdbc/pgsql/transport/netty/JdkScheduler.scala
0% <0%> (ø)

...cala/io/rdbc/pgsql/core/AbstractPgConnection.scala
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Automated] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

/cc we don't use Prow
/assign we don't use Prow

Codecov Report

Merging #93 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #93   +/-   ##
=======================================
  Coverage   96.18%   96.18%
=======================================
  Files          16       16
  Lines         446      446
=======================================
  Hits          429      429
  Misses         15       15
  Partials        2        2

Continue to review full report at Codecov.

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

/lgtm
/approve


Audio not getting recorded while trying medooze demo apllication

Hi Team,
I was trying medooze-media-server node demo for recording on server. I am able to record the video of both the incoming and outgoing stream but Audio is not getting recorded.Please note that, I made slight changes with the video codec and file format. Video codec i changed form vp9 to V_VP90 and chaged the format from .mp4 to .webm, however audio codec is unchanged and it is opus only.
The recording is saved onto the server once the connection is closed but only video track is saved and there is no audio track for the media file.
Kindly help me with the issue.
Regards,
Kshitij

The issue got resolved after  I updated the VLC media player to latest version.


Remove images from core library

From what I can tell, this library (buttercup-core) is intended to be the backbone of the Buttercup application. Therefore, I'm not entirely sure if the images in the /resources/ folder actually belong in this library. The folder is almost 70kb in total, which would be quite a considerable amount to take off the size of the library.

You're right. This could be moved to an external project. The resources (images) will be for visual assets in the GUIs (desktop/mobile/web).


etl-translate-varmap fails when having a dictionary of only one variable

I was executing etl-translate-varmap to translate the variables of a dataset from staging to live, with:
etl-translate-varmap -e1 ./.env.staging -e2 ./.env.live -m1 /Users/prosado/Desktop/staging_mapping.json -m2 /Users/prosado/Desktop/live_mapping.json

This is what I got:
  File "/Users/prosado/Documents/owid/repos/etl/etl/variable_mapping_translate.py", line 83, in main_cli
    mapping_2 = var_translator.translate()
  File "/Users/prosado/Documents/owid/repos/etl/etl/variable_mapping_translate.py", line 111, in translate
    mapping_2 = variable_mapping_translate(eng_1, eng_2, self.mapping_1)
  File "/Users/prosado/Documents/owid/repos/etl/etl/variable_mapping_translate.py", line 166, in variable_mapping_translate
    mapping_new = build_mapping_from_df(sql_2, df)
  File "/Users/prosado/Documents/owid/repos/etl/etl/variable_mapping_translate.py", line 252, in build_mapping_from_df
    dix: Dict[str, str] = df.set_index("id_old")["id_new"].squeeze().to_dict()
AttributeError: 'str' object has no attribute 'to_dict'

My intuition is that the squeeze returns a different type of object if the array has 1 or more elements. So, while
pd.Series([1, 2]).squeeze().to_dict()

works,
pd.Series([1]).squeeze().to_dict()

fails.

Should be fixed now

Thanks a lot @lucasrodes!


Change the gallery banner color to be higher contrast

Right now it's blue on blue:

Not sure what the color should be, but we control this in package.json here: https://github.com/Microsoft/vscode-cosmosdb/blob/master/package.json#L12

Here's what the service page  uses 🤷♀

@fiveisprime Are you handling this one?

Sure, I'll figure something out.


feat: enable razor icon for .razor extension in jetbrains-icons

Small change to enable .razor extension files to show the already existing razor file icon in jetbrains-icons. The .razor extension is used in Blazor projects.
Before:

After:

Let me know if I need to do anything to bump the change onto jetbrains-icons :)

Hi @igotinfected,
I know I just approved this PR but I will be closing this as not planned due to the PR I just raised https://github.com/catppuccin/jetbrains-icons/pull/133 which should enable support for the icon in our JB plugin.


Accessing rawRequest from CallableContext

Hi, I would like to access the context.rawRequest['ip'] from a callable but it appears that you're not exposing the rawRequest in CallableContext.
I realise I could get the IP by switching to callable but ideally I'd use callable for the authentication.
Would it be something you'd consider? I would be happy to submit a PR if you let me know how you would want it implementing?

Hey @pulyaevskiy, hope you're doing alright over there? Don't suppose you had chance to consider this?
Thanks


can't get details of the sink in the sinkmapper

Description:
can't get details of the sink inside the sinkmapper.

need to get the type of the sink (sinkname) and the "publisher.url" and "receiver.url"  annotations from the sink


Simple Sourcing (event sourced) actions that take input from an arbitrary topic

Having action processors not return a value (apart from effectively a success or failure) is a conscious design choice.
However there is still a need to communicate between saga actions. However this is better left to the action processors, keeping the saga coordinator clean.
The following use cases stand out:
For Simple Sourcing (event sourced) actions, create a variation that takes (topic, key) pair, with serde for the value. This is treated as an input topic of key/value pairs, passed in to the command create function when the saga action gets invoked. This allows a Simple Sourcing command to be a function of the latest value in a topic for a particular key.
An analogous issue exists for async action processors, to allow them to be a function of input from an arbitrary topic (https://github.com/simplesourcing/simplesagas/issues/16)

Should this be a separate interface?
The new Spec would be something like this:
public final class CommandSpec<A, D, IK, I, AK, C> {
    public final String actionType;
    public final Function<A, Result<Throwable, D>> decode;
    public final BiFunction<D, I, C> commandMapper;
    public final Function<D, AK> aggregateKeyMapper;
    public final Function<D, IK> inputKeyMapper;
    public final Function<D, Sequence> sequenceMapper;
    public final InputSerdes<IK, I> inputKeySerdes;
    public final CommandSerdes<AK, C> commandSerdes;
    public final long timeOutMillis;
}

It's not a difficult implementation, but the interface gets a lot busier.
Recommend holding off on this one until a concrete need arises.


cv2.imshow unable to display image

The test code is as follows.
import cv2
from pyskl.apis import init_recognizer  # No error will be reported if this line of code is commented.
def main():
    vid = cv2.VideoCapture("rtsp://admin:lgl---616@<IP_ADDRESS>:554/media/video2")
    flag, frame = vid.read()

    cv2.imshow("test", frame)
    print("over")
if __name__ == '__main__':
    main()

The error is ‘Process finished with exit code 139(interrupted by signal 11:SIGSEGV)’.
Error is mainly caused by 'from pyskl.apis import init_recognizer'.
I specially created a new environment for testing.
#120 It should be the same question as mine.

You can try the new installation guide to reinstall pyskl and see if the problem has been fixed now.
Sorry for the late fix.

import numpy as np
import cv2

from pyskl.apis import init_recognizer
from pyskl.datasets import GestureDataset
from pyskl.datasets.pipelines import Compose
from pyskl.smp import h2r

arr = np.random.randint(0, 256, (200, 200, 3), dtype=np.uint8)
cv2.imshow('output', arr)
cv2.waitKey(5)
input()

Running this minimal code still causes a segmentation fault when trying to execute cv2.imshow.
The import statements at lines 4 to 7 are the import required in the demo_gesture.py and if I comment them, cv2.imshow works.
I have already tried to install pyskl following the new installation guide.
I also tried to install different versions of opencv.
I'm running this code on Ubuntu 20.04.

Hi, nunziati,
My Windows laptop can run your minimal examples bug-free. This weekend I can have a try with a clean Ubuntu 22.04 linux desktop and I will provide more updates then.

Thank you, I found out that the "import decord" statement in smp.py caused cv2.imshow to stop with a segmentation fault.
For the moment I just commented that line, since it is not strictly required.
I have decord 0.6.0 and I've not tried different versions.

Thank you, I found out that the "import decord" statement in smp.py caused cv2.imshow to stop with a segmentation fault. For the moment I just commented that line, since it is not strictly required. I have decord 0.6.0 and I've not tried different versions.

thanks！！I solved it by your method!


{Network} Bump to azure-mgmt-network 9.0.0

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[Component Name 1] (BREAKING CHANGE:) (az command:) make some customer-facing change.
[Component Name 2] (BREAKING CHANGE:) (az command:) make some customer-facing change.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S165.

/azp run

@haroldrandom excellent work! I'd reconmend support CMv1 in this PR too so that we can keep our dev branch still functionalable.


There shouldn't a difference between product and documentation feedback.

If something doesn't work, as a user how am I supposed to know if its a bug in the product or its documentation?
Also, I'm inevitably going to put something in the "wrong" bucket and it will get closed with a "this is for the other feedback, open it there".

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

ID: 0193ed76-3eec-18ac-512f-45f8118dde34
Version Independent ID: 8e693833-3e45-2bb8-ddc2-d0c54936c3c1
Content
Content Source
Service: unspecified

I disagree. In the old system, you could only provide feedback on the documentation, i.e. you could only attach your feedback to a specific web page of the documentation. It was far from obvious how (and on which specific documentation page) to provide feedback about a product defect that is not related to a specific page of the documentation. Spreading product feedback across documentation web pages makes it more difficult for others interested in the same issue to quickly find the discussion thread. Keeping them separate makes it much easier to categorize product issues by subsystem and assign them to the relevant developer (who may not be in charge of any particular page of the documentation).

Perhaps part of the error is in thinking the old system was or was not only for documentation feedback.
Docs has always been easier to find, and as I dont work at/for MSFT or have an "in", its historically about the only place I could get help outside of stackoverflow (SO has been invaluable, but its generally still outsiders like me, postulating and speculating). If I'm having a problem with the program/product, I'm going to be on the doc pages already. Finding a discussion there about the problem would be awesome. Also, the new/recent option of devcommunity is not working out so great for me either with only 54 issues out of the 223 I've opened resolved to some degree of satisfaction (one of the open ones has been in "triaged" status for 340 days).
If you do work for on the producer side of the discussion, I can see how having the work neatly pre-organized would be appealing, but I could never ask my customers to effectively "sorry, call a different helpdesk number" when they are stuck with a problem and are already on the phone. Resentment kills any relationship, not just personal ones.
I don't see what's to really be gained when most of the time users are just going to flip a coin most times and pick one of the two, and the producer will just have to move the issue around anyway.

Yeah, I have to agree with StingyJack, at least on the last point. I knew that if there was something in the documentation that should be changed, I would make a GitHub issue for it. But, if I had some question about how a feature of the product the documentation was for was supposed to work, that's when I would usually post the comment using LiveFyre. I didn't realize that the comments on the documentation pages were meant to be used for documentation feedback. For me it was usually a way to clarify what should be happening with the product.
I can tell that having just a single, unanimous comments thread led to there being feedback on there on documentation alongside product feedback, so I agree it is good to separate them, but why move the product feedback to a different system entirely? Why not use GitHub for that too?
I guess what I really want to know is in the future where should I go if I need help with how to use the product, or if there is an issue with the product itself, and is it easy for me to get there?

I'm finding all the product feedback links I've seen at the bottom of docs pages are sending me to the corresponding uservoice or ideas site for the product which are intended for Product Suggestions, not Product Feedback.
We've lost a place to often get direct clarifications on product usage/licensing/roadmaps from the product owner themselves, and to point out bugs and issues with that software.
They really needed to introduce three links to the bottom of Docs pages:

Documentation Feedback (hosted on GitHub)
Product Suggestions (pointing to the corresponding Microsoft UserVoice/Ideas/Experience site for the product)
Product Feedback (hosted on GitHub)

uservoice is broken, or rather the way MSFT uses it is broken
https://developercommunity.visualstudio.com/content/problem/165853/the-vs-ide-uservoice-still-runs-out-of-votes.html
https://developercommunity.visualstudio.com/content/problem/56328/get-rid-of-uservoice.html

@StingyJack Thanks for taking the time to give us your feedback.
We've worked to improve the feedback mechanisms since your original post.
Within Git, use the edit option to suggest changes to pages you feel are in error, and use the feedback option to ask questions to either doc or product owners. Both are answered.
If a page doesn't have a feedback option, you can use the Is this page helpful vote to add your comment or feedback.
Appreciate your contribution to our community!

@mlottner - thanks, I'm aware of how to try to fix docs pages that need it (though some page authors/page owners seem to be awol).
I'm going to have to disagree that product feedback are answered. In my experience, I'm at least 5x more likely to get a "sorry, nobody from the assigned product team could look at it in after being opened for > 90 days" closure than to get a response from a product owner or product team member. Last time i tallied up my reported feedback, only about 1 out of 20 problems I had reported was handled satisfactorily.
That aside, I still see two buttons on every page, and this is the crux of my complaint. Users should have a single place to request information or assistance from Microsoft. How you triage and route that request and respond/resolve it is up to you.
The multiple week lag of docs behind the product delivery is a great example of the wasted effort created by this two button system. Product not working the same as the day before and this is causing some production issue. Support Engineer consults docs, docs don't reflect this change. What button should one click?
I pick docs first given the success rate with product feedback. 3 days later the item is closed with a note saying "it looks like you are having a product problem, kindly go ask them". Usually at that point I have to argue with or remind whomever closed the issue that the docs page still doesn't match the current reality. Sometimes this takes multiple exchanges. All this is wasted time when there could be a streamlined experience with a single point of entry for users.

We've worked to improve the feedback mechanisms since your original post.

I don't see that. I still have the same problems with this system. Nothing has been materially changed in that, so I don't feel that this being closed is legit.

@StingyJack Thanks for your fast response.
While I can't speak for every content developer, product or every product owner, we all do our best to answer and respond to customer issues as fast as we can.
While I can appreciate your desire for a single point of contact, and have flagged your suggestion to the relevant infrastructure related parties, leaving this specific blog feedback issue open (or re-opening) will not change the current structure. I can attest that your feedback on this feature has been noted and recorded and flagged to all relevant parties.
Again, we do appreciate your contribution to our community and suggestions for feedback improvement.

@Stingray I think you may be going down a dangerous path here when you try to conflate product assistance with feedback. A feedback channel is aimed at expert users who have found a bug or want an efficient way to communicate a product-improvement suggestion directly to developers. Product assistance is for less experienced users who are struggling with understanding the product and require some hand holding from documentation and help desk staff. If you encourage a software company to lump both together, then you will invariable end up everything being routed to the product-assistance folks, and as a result you cut off a valuable route for experienced users to provide direct feedback to developers. The problem is that there are always two orders of magnitude more people seeking product assistance than being able to provide actionable technical high-quality product feedback. Therefore software companies will always want to protect the productivity of their developers by shielding them from product-assistance tasks.
I think Microsoft has done the right thing here already by learning from Github's open-source community of how to provide an easy feedback mechanism for experienced developers, and you might well end up killing that if you confuse it with a customer support function, which is something with very different requirements. Github issues are brilliant for getting expert users in touch with developers, but they are absolutely not the right tool for the far more repetitive task of regular end-user support.

@mgkuhn - you mean me?

@mlottner - can I get your opinion on things like this https://github.com/MicrosoftDocs/vsts-docs/issues/5375
This was just the first one I happened to come across that wasn't my own issue. The closer on it has done the same to me several times, and all but one or two were done incorrectly. The closer relented only after getting a response in kind, and then only to pacify/defuse.
If you really think the system is right, and you value the customer experience, I think that it would be wise to review anything closed by a canned first response message. Those sharp responses are actually examples of the damages the two-option system brings with it.

@StingyJack I fully appreciate your passion about this feedback issue. Thanks you for continuing the conversation.
While I can't speak to how every person responds to GitIssues, I can tell you that our singular goal is the be helpful. Your feedback allows us to understand your perspective, fix issues when they are raised and offer you (and the thousands of other users that "talk" to us via multiple feedback channels) on a continual basis, the very best service and support that we can.
We want you to be as successful as possible using our products.
However, we are human and we do make mistakes. That is the perhaps the "cost" in any feedback workflow when not talking to a bot.
I will raise the issues you've mentioned here to a larger forum, and again, we sincerely appreciate your taking the time to share both your concerns and suggestions.


BEGONIA-119: Add product information in the assessment report

Fixes ISSUE #
BEGONIA-119: Add product information in the assessment report
Description
Enrich the Image Scanner Assessment report with VAC product assessment info
Tests
Before fix
"containers": [
                          {
                            "name": "apache",
                            "id": "docker://775fa09e82e3d3110a2cbfb43d2ede4a52efa0bd3b25c12617e8b0d3a13acc81",
                            "image": "harbor.int.app-catalog.vmware.com/catalog_governor/containers/debian-11/apache:2.4.56-debian-11-r22",
                            "imageID": "docker-pullable://harbor.int.app-catalog.vmware.com/catalog_governor/containers/debian-11/apache@sha256:086606d412ac04b75ddfecb606421cfb9046b7a063b848494b88e40f9523d7c8",
                            "isInit": false,
                          }
                        ]

After fix
"containers": [
                          {
                            "name": "apache",
                            "id": "docker://775fa09e82e3d3110a2cbfb43d2ede4a52efa0bd3b25c12617e8b0d3a13acc81",
                            "image": "harbor.int.app-catalog.vmware.com/catalog_governor/containers/debian-11/apache:2.4.56-debian-11-r22",
                            "imageID": "docker-pullable://harbor.int.app-catalog.vmware.com/catalog_governor/containers/debian-11/apache@sha256:086606d412ac04b75ddfecb606421cfb9046b7a063b848494b88e40f9523d7c8",
                            "isInit": false,
                            "vacAccessment": {
                              "trusted": true,
                              "name": "Apache",
                              "branch": "2.4",
                              "version": "2.4.56",
                              "revision": "22",
                              "releasedAt": "2023-03-31T16:13:25Z",
                              "lastVersionReleased": "2.4.56-r25",
                              "status": "ACTIVE"
                            }
                          }
                        ]

@bgubbala, I could see go-client and mocks files path changes from governor to lib folder is changed. Did we decide to do like this?

It makes more sense for them to be part of lib/ rather than in exporter.
Now it will be used by both cnsi-exporter & cnsi-inspector.

It makes more sense for them to be part of lib/ rather than in exporter. Now it will be used by both cnsi-exporter & cnsi-inspector.

Great, Add in description as well.

Codecov Report

Merging #232 (16deeec) into main (4efea85) will increase coverage by 0.28%.
The diff coverage is n/a.

:exclamation: Current head 16deeec differs from pull request most recent head bb7cafc. Consider uploading reports for the commit bb7cafc to get more accurate results

@@            Coverage Diff             @@
##             main     #232      +/-   ##
==========================================
+ Coverage   57.74%   58.03%   +0.28%
==========================================
  Files          17       17
  Lines        1233     1239       +6
==========================================
+ Hits          712      719       +7
+ Misses        475      474       -1
  Partials       46       46

Flag
Coverage Δ

unittests
58.03% <ø> (+0.28%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Export objects to text should not depend on creating CSide

I use an external to to explore exported objects. E.g. where is an object used, what events and functions does an object have, etc.
But why is exporting objects linked to the parameter includeCSide? I don't need CSide, I just want the exported objects. :-)
It isn't clear that the parameter doNotExportObjectsToText is linked to includeCSide. Wouldn't it be an idea to turn it into exportObjectsToText as a separate and individual parameter? Ok, that's breaking change, but still it would make much more sense to me.

It probably would make a lot more sense. I will put that on the wish-list

If I may add one more wish to that list: please don't remove the full export file after the split. The tool I use is way faster with importing a full text export instead of importing a folder with 7000 files.
You also might consider to use a different export path, e.g. navcontainerhelper\objects instead of mixing them up with the container folders in the navcontainerhelper\extensions folder.

BTW. I am not going to move the folders as this would be a breaking change for everybody using this.


Update API gene index response to include new target safety data

Given the changes to the pipeline proposed in #904 - specifically around the availability of experimental toxicity data - we will need to ensure that the API returns the new data in a format that the front-end can use in #906 and #907.
Can we please update the API to return the experimental toxicity data in the existing safety entry? See below for a proposed JSON schema (feedback welcome and much appreciated!):
"safety": {
  "adverse_effects": [ ... ],
  "safety_risk_info": [ ... ],
  "experimental_toxicity":[
    {
      "data_source": "Tox21",
      "data_source_reference_link": "http://www.tox21.co.uk",
      "experiment_details": {
        "tissue" : "liver"
        "cell_format": "cell line",
        "assay_format_type": "cell-based"
        "cell_short_name": "T47D"
        "assay_description": "CLD_24hr is a cell-based, multiplexed-readout assay that uses hepatocyte, a human liver primary cell, with measurements taken at 24 hours after chemical dosing in a 96-well plate"
      },
    },
    {
      "data_source": "ETOX",
      "data_source_reference_link": "http://www.etox.co.uk",
      "experiment_details": {
        "tissue" : "pancreas, intestine, kidney"
        "cell_format": "tissue-based cell-free",
        "assay_format_type": ""
        "cell_short_name": ""
        "assay_description": "Preclinical safety data for 1214 small molecule drugs and drug candidates extracted from 3970 reports donated by thirteen pharmaceutical companies for the eTOX project (www.etoxproject.eu)",
      },
    },
  ]
}

As discussed with @PruMM,  the minimum fields for the JSON schema are:

data_source
data_source_reference_link
experiment_details.cell_format
experiment_details.assay_description

Proposed JSON schema has been updated to reflect data available in experimental toxicity .tsv file

Proposed JSON schema has been updated and flattened to reflect inclusion of assay_type and assay_system columns in the toxicity .tsv file.

Proposed JSON schema has been updated to reflect changes to data file - see #904 for more information

Thank you @cmalangone - the QC API returns the data as agreed and can be used by the front-end team! :-)

QC API response for ENSG00000085563


DMP-2623 Issue fixes

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DMP-2623
Change description
fixed some little issues found in the generation of the case document

null createdDateTime and lastModifiedDateTime CaseDocument fields
null createdBy and lastModifiedBy CaseDocument fields
removed "Entity" suffix from some case document fields
renamed id to caseId
renamed package from ...casedocument.template to ...casedocument.model

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

CourtCaseDocumentMapperIntTest

it's a valid question. The case document mapper is different from the existing mappers you listed, because is a complex mapper that relies on 2 other mappers. Therefore we must have an integration test which verifies the correct integration of the 3 mappers that constitute the case document mapper.
At this point, it seemed pointless to me writing 3 separate unite tests for the 3 individual mappers, it would be a lot of effort to basically test the same things already tested by the integration test. So I've skipped them


iOS 15.4 (15.2+?) Unauthorized access: client does not have valid TCC authorization after granting permission

The sample code does not (currently) work for the latest iOS, from my testing and research.  It appears that in 15.2, changes were made so that the logic flow has to begin after permission grant instead of allowing it beforehand: https://developer.apple.com/forums/thread/696804
Either as a result or as a separate issue, Permissions.photos.request() always returned denied / permanently denied when used per the example without prompting for permission, however when removing the photos.request() logic, THEN the prompt appears, and after granting, the following error(s) occur:

[GatekeeperXPC] XPC connection error to assetsd getLibraryServiceWithReply: : Error Domain=com.apple.photos.error Code=41011 "Unauthorized access: client does not have valid TCC authorization" UserInfo={NSLocalizedDescription=Unauthorized access: client does not have valid TCC authorization}
[Backend] Swallowing proxy invocation: <NSInvocation: 0x2836f6ac0> getLibraryServiceWithReply:
[Backend] openPhotoLibraryDatabaseWithPostOpenProgress:options:error: Error Domain=com.apple.photos.error Code=41011 "Unauthorized access: client does not have valid TCC authorization" UserInfo={NSLocalizedDescription=Unauthorized access: client does not have valid TCC authorization}
[Backend] Failed to load library: Error Domain=com.apple.photos.error Code=41011 "Unauthorized access: client does not have valid TCC authorization" UserInfo={NSLocalizedDescription=Unauthorized access: client does not have valid TCC authorization}
[Backend] failed to load photo library PHPhotoLibraryMainQueueQoS with url file:///var/mobile/Media/, Error Domain=com.apple.photos.error Code=41011 "Unauthorized access: client does not have valid TCC authorization" UserInfo={NSLocalizedDescription=Unauthorized access: client does not have valid TCC authorization}

@clayharris have you found the solution for this yet?

@Jayvd I tried to track down what I did to address the issues 6 months ago, and I wasn't able to identify it.  My code looks pretty similar to the example, but have included logic to ensure the permissions are completely resolved prior to relevant app logic.
The issue was specifically about the example code, so I didn't follow up with working examples at the time.


Model initialization from server call

I am initializing the model fields and default values from a server call in the created lifestyle hook. If I statically set the models before entering the component, it works E.g. model : {FirstName : '', LastName: ''}
But if I set this in the created function dynamically, there is no binding for my formly forms.
created: function() {
     axios.get('http://localhost/scadservices/api/tablesv2/' + this.TableId + '/minmetadata2.json?ViewId=' + this.ViewId, {crossdomain:true, withCredentials: true})
        .then((resp) => {
                this.metadata = resp.data
                console.log(JSON.parse(this.metadata.Form))
                var cols = this.metadata.Columns
                for (var key in cols) {
                    var obj = cols[key];
                    var colname = obj["ColumnName"]
                    this.model[colname] = ""
                }

                 this.fields = JSON.parse(this.metadata.Form)
        })
        .catch((err) => {
            console.log(err)
        })
  }

hmm, this should work. What happens if you explicity set them, e.g. this.$set(this.model, colName, '') ?

Hi, If I explicitly set it like you did, it works, but not by this.model.FirstName = ''.  I will use it like proposed for now.  Thanks


mariadb: update build configuration.

Motivation for this change
In release-notes marked deprecated TokuDB plugin.
Added options withStorageRocks and withStorageToku. It is necessary to be able to build MariaDB with jemalloc 5 library. For this, we need to disable TokuDB plugin.
Added zstd compression.
cc @flokli @aanderse @Mic92
Things done

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

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

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

Please backport to 20.03.

This fails evaluation.

error - Failed during the setup of executing nix-env: Os { code: 2, kind: NotFound, message: "No such file or directory" }

I'm personally fine backporting this to 20.03 - both TokuDB and RocksDB are enabled, and having this in 20.03 (and in the release notes) gives users some time to migrate.

@GrahamcOfBorg build mariadb.client

@GrahamcOfBorg build mariadb.client

@GrahamcOfBorg eval

@GrahamcOfBorg build mariadb.server

@GrahamcOfBorg build mariadb.server

@GrahamcOfBorg build mariadb.client

@GrahamcOfBorg eval

@GrahamcOfBorg test mysql

@Izorkin this doesn't seem to apply cleanly on 20.03, even not when I git cherry-pick -x 4b8d66aa7266ab55f08d53271df36832d9c055d2 before. Can you prepare a PR targetet against 20.03 cherry-picking these commits?


typos in tutorial.py

'achived', should be achieved, I'll send a PR shortly.

closing, code is due for deletion soon: https://github.com/pydata/xarray/commit/d6e15cc1647909cebde734a5d6b92f262b234112


Windows flake -<EMAIL_ADDRESS>

E1202 19:38:30.874000000  4144 src/core/ext/transport/chttp2/server/insecure/server_chttp2.cc:40] {"created":"@1575315510.873000000","description":"No address added out of total 2 resolved","file":"src/core/ext/transport/chttp2/server/chttp2_server.cc","file_line":395,"referenced_errors":[{"created":"@1575315510.873000000","description":"Failed to add port to server","file":"src/core/lib/iomgr/tcp_server_windows.cc","file_line":512,"referenced_errors":[{"created":"@1575315510.873000000","description":"OS Error","file":"src/core/lib/iomgr/tcp_server_windows.cc","file_line":203,"os_error":"An attempt was made to access a socket in a way forbidden by its access permissions.\r\n","syscall":"bind","wsa_error":10013}]},{"created":"@1575315510.873000000","description":"Failed to add port to server","file":"src/core/lib/iomgr/tcp_server_windows.cc","file_line":512,"referenced_errors":[{"created":"@1575315510.873000000","description":"OS Error","file":"src/core/lib/iomgr/tcp_server_windows.cc","file_line":203,"os_error":"An attempt was made to access a socket in a way forbidden by its access permissions.\r\n","syscall":"bind","wsa_error":10013}]}]}
E1202 19:38:30.876000000  4144 test/core/end2end/fixtures/h2_full+workarounds.cc:88] assertion failed: grpc_server_add_insecure_http2_port(f->server, ffd->localaddr.get())
Abort handler called.
*** 0: 00007FF770CBA5B9  -<PHONE_NUMBER>000000
*** 1: 00007FF770CBAA47  -<PHONE_NUMBER>000000
*** 2: 00007FFEC47FD09B raise - 00007FFEC47FCEC0
*** 3: 00007FFEC47FE131 abort - 00007FFEC47FE100
*** 4: 00007FF770A41FEC abort - 00007FFEC47FE100
*** 5: 00007FF770A7644C abort - 00007FFEC47FE100
*** 6: 00007FF770A77452 abort - 00007FFEC47FE100
*** 7: 00007FF770A775D8 abort - 00007FFEC47FE100
*** 8: 00007FF770A58AF5 abort - 00007FFEC47FE100
*** 9: 00007FF770A42128 abort - 00007FFEC47FE100
*** 10: 00007FF770DFB629 abort - 00007FFEC47FE100
*** 11: 00007FFED2734034 BaseThreadInitThunk - 00007FFED2734020
*** 12: 00007FFEDCB03691 RtlUserThreadStart - 00007FFEDCB03670

https://source.cloud.google.com/results/invocations/099fd60c-0aff-4d51-92b8-f5f96d8b0f45/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_full%2Bworkarounds_nosec_test@hpack_size/log

Hopefully this will be fixed by https://github.com/grpc/grpc/pull/22363.

#22363 was merged.


Store the DB in JSON, not pickle format.

The server is now running this PR and the data is migrated.

Already done!


Regular expression is invalid error when certificates-relation-changed

This error was discovered by @gatici here. I'm linking it here because this issue is most likely in the interface.

Bug in Juju.
Fix in Juju 3.4.


animated login page

connect with me -
Github : https://github.com/Durgesh4993
LinkedIn : https://www.linkedin.com/in/durgesh4993/
And don't forget to star


Company Auto Billing Requirement

When new user type anything in scheduler text box, please show Create New Scheduler Button

when a new client wants to auto-billing and if he did not have any scheduler then create a
new scheduler does not appear, so this is needed


Turn off multiple buttons

Because there is a button , I can not see the file name.
Please add the option to turn off the button.

next version..... :+1:

I made sure that can be turned off in version 5.1.4.
Great Thanks!!


recordings and config root ownership

I observe that both config and recording files/folders are taken ownership by root once, viseron docker runs. Even I include my user to docker group and run the container, the config files/folder ownership turns to root.

That is correct, the recordings/config folders permission is set to match the running user.
If you want to change the running user, you can do so by following these instructions: https://viseron.netlify.app/docs/documentation/installation#user-and-group-identifiers

From my experience so far, I haven't specified -e options but run one in systemd service (root) and the other on command line by my account user (for testing parameters). The result was both approaches turned the config folder and files into root. It didn't quite seem to follow the running user.
From your advise, I explicitly specified -e option and it turned out fine now.
Thanks.


Update mnist_data_handler.py

refactor with fstring to format string to make code more Pythonic.

Thank you for your pull request. I agree with the intention, so I did the conversion to f-string formatting on the whole project instead of this single file via flynt. Closing your pull request as redundant.


Remove auto setting data aspect for geo

This setting actually caused issues
Before:
https://github.com/holoviz/hvplot/assets/15331990/d4004c88-f90c-42fa-a57d-34b32ae46a4a
After:
https://github.com/holoviz/hvplot/assets/15331990/0ba3b2e0-647c-4591-874d-ae54cd166b73
Closes https://github.com/holoviz/hvplot/issues/1105

I suppose I could dig deeper and see if the underlying bug can be fixed; if not I'd still say this PR is worth merging because it's practically unusable right now.

I suppose it's not a geo/hvplot specific issue, rather, a HoloViews issue.
Going to close this and if I figure it out, open a PR in holoviews.
import holoviews as hv
from holoviews.operation.datashader import rasterize
hv.extension("bokeh")

rasterize(hv.Curve([0, 1, 2])).opts(data_aspect=1)

Resolving here instead: https://github.com/holoviz/holoviews/pull/6189


Protocols to push data

Really cool project @alwitt
the way it’s designed is very well done.
The management and dataplane distinction is exactly what I need for the Open Science project. - on my GitHub .
I only saw the curl post example for where a client subscribes.
i was wondering if the SSE protocol could be also used so that clients can subscribe over SSE ?
This would allow browsers to easily subscribe. There is also a golang SSE lib floating around so that it can be used for native client written in golang .

Hi @gedw99, thanks for the interest.
In my original design, I wanted the client to server communication to be over the same request stream as the SSE. I had the following demo code working locally.
However, when I started testing in Kubernetes, I was not able to get this working through my Ingress controller (Traefik in my case); I had validated through kubectl portforward that the connection still worked correctly. I have not tested other ingress controller yet.
I am also not sure where this full duplex would work without HTTP 2, as some proxies I use don't support that. So I decided to split the client to server communication from the server to client stream.
I don't have much experience using SSE between front-end and back-end; I have always used Websockets. So I am curious how other people use SSE.

Server Request Handler
fullDuplexHandler := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
	// First flash response headers
	if f, ok := w.(http.Flusher); ok {
		f.Flush()
	}
	// Copy from the request body to the response writer and flush
	// (send to client)
	if _, err := io.Copy(flushWriter{w: w}, r.Body); err != nil {
		log.WithError(err).Error("Full-Duplex")
		w.WriteHeader(500)
	}
})

Client Side
// Create a pipe - an object that implements `io.Reader` and `io.Writer`.
// Whatever is written to the writer part will be read by the reader part.
pr, pw := io.Pipe()

client := http.Client{}

// Create an `http.Request` and set its body as the reader part of the
// pipe - after sending the request, whatever will be written to the pipe,
// will be sent as the request body.
// This makes the request content dynamic, so we don't need to define it
// before sending the request.

resp, err := client.Post(args.URL, "text", ioutil.NopCloser(pr))
// Send the request
log.Infof("Send POST to %s", args.URL)
if err != nil {
	return (err)
}
log.Infof("POST Got: %d", resp.StatusCode)

// Run a loop which writes every second to the writer part of the pipe
// the current time.
go func() {
	for {
		log.Info("Writing to server")
		time.Sleep(time.Second)
		fmt.Fprintf(pw, "It is now %v\n", time.Now())
	}
}()

// Copy the server's response to stdout.
_, err = io.Copy(os.Stdout, resp.Body)

I have used SSE . Pocketbase a popular golang project used them. Can probably look at that later if we want to give it another try .
Do you currently use web sockets instead over http2 ?

PocketBase looks like a very interesting project. I will take a look later.
I use websockets in my other projects. This project uses HTTP1.1 / HTTP2.

So there is no push currently
Mhh . Best to use nats

Unfortunately, there is no plans to transition to web-sockets at the moment.
I am using this project as apart of another project, so the design decision is partly driven by the needs of that project.

Ok thanks
I think I can extend it without forking to incorporate nats.

Sounds good. Let me know if you have any other questions about the project.

Unfortunately, there is no plans to transition to web-sockets at the moment.
I am using this project as apart of another project, so the design decision is partly driven by the needs of that project.

I meant the inherent websockets of NATS Jetstream.
For the Control plane it's just a matter of turning it on.
I currently use this for Web clients, Desktops and Servers. The Web cleit is the nats.go compiled to wasm. Call me nuts but i wants the Web and Non web clients to use the same code..

Unfortunately, there is no plans to transition to web-sockets at the moment.
I am using this project as apart of another project, so the design decision is partly driven by the needs of that project.

I meant the inherent websockets of NATS Jetstream.
For the Control plane it's just a matter of turning it on.
I currently use this for Web clients, Desktops and Servers. The Web cleit is the nats.go compiled to wasm. Call me nuts but i wants the Web and Non web clients to use the same code..


Remove no-resolution flag and add --exclude-entrypoints when running are-the-types-wrong during CI

@arethetypeswrong/cli now has an --exclude-entrypoints flag which we can use to exclude the alternate-renderers entrypoint from the check since it will fail under the Node10 module resolution as Node10 looks at actual files on disk and we don't have a file named alternate-renderers.

Oh good! This was bugging me as a false positive. Thanks!