Lots of log WARNings when using apt cookbook ("Deprecation class overwrites LWRP resource apt_preference from cookbook apt")

I recently noticed that I'm getting lots of these warnings when using the apt cookbook:
[2015-09-22T21:35:22+00:00] WARN: You declared a new resource #<Class:0x0000000641b418> for resource apt_preference, but it comes alphabetically after LWRP resource apt_preference from cookbook apt and has the same filters ({}), so it will not be used. Use override: true if you want to use it for apt_preference.
[2015-09-22T21:35:22+00:00] WARN: AptPreference already exists!  Deprecation class overwrites LWRP resource apt_preference from cookbook apt
[2015-09-22T21:35:22+00:00] WARN: You declared a new resource #<Class:0x00000006412368> for resource apt_repository, but it comes alphabetically after LWRP resource apt_repository from cookbook apt and has the same filters ({}), so it will not be used. Use override: true if you want to use it for apt_repository.
[2015-09-22T21:35:22+00:00] WARN: AptRepository already exists!  Deprecation class overwrites LWRP resource apt_repository from cookbook apt

This is using Chef 12.4.1 with chef zero provisioner, happening during a chefspec run

Googling doesn't help too much, the only stuff I'm finding are logs from travis-ci:
www.google.com/search?q="AptRepository already exists! Deprecation class overwrites LWRP resource apt_repository from cookbook apt"

This appears to be coming from Chef::Platform::HandlerMap in 12.4.1, though it isn't obvious why ChefSpec is triggering these warnings.  FWIW, I see similar errors using the sudo cookbook.
@jkeiser, can you shed any light on why we've begun to see these messages?
Thanks!

I'm getting similar warning for a custom LWRP
[2015-10-01T10:16:47+01:00] WARN: You declared a new resource #<Class:0x007fa901bac690> for resource #{resource_name}, but it comes alphabetically after LWRP resource #{resource_name} from cookbook #{cookbook_name} and has the same filters ({}), so it will not be used. Use override: true if you want to use it for #{resource_name}.
[2015-10-01T10:16:47+01:00] WARN: #{resource_name} already exists!  Deprecation class overwrites LWRP resource #{resource_name} from cookbook #{cookbook_name}

I've also noticed that this warning only comes when I use ChefSpec::Runner
runner = ChefSpec::ServerRunner.new do |node, server|

ChefSpec::SoloRunner doesn't go around whining about this.
Hope this helps to narrow down the issue a bit.

Is this still present with the recently released Chefspec 4.4.0 version?
Am 01.10.2015 11:46 vorm. schrieb "Deepu Mohan Puthrote" <
<EMAIL_ADDRESS>
I'm getting similar warning for a custom LWRP
[2015-10-01T10:16:47+01:00] WARN: You declared a new resource #Class:0x007fa901bac690 for resource #{resource_name}, but it comes alphabetically after LWRP resource #{resource_name} from cookbook #{cookbook_name} and has the same filters ({}), so it will not be used. Use override: true if you want to use it for #{resource_name}.
[2015-10-01T10:16:47+01:00] WARN: #{resource_name} already exists!  Deprecation class overwrites LWRP resource #{resource_name} from cookbook #{cookbook_name}
I've also noticed that this warning only comes when I use ChefSpec::Runner
runner = ChefSpec::ServerRunner.new do |node, server|
ChefSpec::SoloRunner doesn't go around whining about this.
Hope this helps to narrow down the issue a bit.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/apt/issues/163#issuecomment-144679318.

@tknerr, yes I can confirm I'm still seeing this with ChefSpec 4.4.0

(Posted in issue 642 above, reposting here) Hey all, a hack workaround for this is to redirect stdout during the chefspec converge, and restore it afterwards.  Code:
  let (:chef_run) do
    # Redirecting stdout to suppress 'Deprecation class overwrites LWRP' noise.
    # (ref https://github.com/sethvargo/chefspec/issues/642)
    old_std_out = $stdout.clone
    $stdout.reopen('tmp_std_out.txt', 'w')
    result = chef_runner.converge(described_recipe)
    $stdout.reopen(old_std_out)
    File.read('tmp_std_out.txt').each_line do |lin|
      puts lin unless lin =~ /Deprecation class overwrites LWRP resource/
    end
    File.delete('tmp_std_out.txt')
    result
  end

We'll be solving this soon by using compat_resource to provide the update and repository functionality. This aligns the code base with core chef and eliminates double code loading

We've removed the sources from this cookbook so you shouldn't see this warnings in the 6.0 release now.


[0613] Migrate courses course show page

Context
Course show and details page
Changes proposed in this pull request
Ported across

the course show page
the course details page
Degree component

https://teacher-training-api-pr-2491.london.cloudapps.digital/view_components/degree_row_content_component/view

GCSE component

https://teacher-training-api-pr-2491.london.cloudapps.digital/view_components/gcse_row_content_component/view

date presentation (ie short/long date)
money presentation (ie pound sign and thousand denominator )

Also fixed
DEPRECATION WARNING: This manually engine loading is deprecated and will be removed in v3.0.0. Remove require "view_component/engine".
Guidance to review
Best to compare like for like between
https://teacher-training-api-pr-2491.london.cloudapps.digital/publish/organisations/{provider_code}/2022/courses/{course_code}
vs
https://qa.publish-teacher-training-courses.service.gov.uk/organisations/{provider_code}/2022/courses/{course_code}
Best to view per commit
Items omitted

items to be covered in as another piece of work

Change/action links
course show page status panel

Recruitment cycle 2021and previous

UCAS GCSE implementations

Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Migrate Courses - Course show page

the text in the degree component preview seem to be missing styles https://teacher-training-api-pr-2491.london.cloudapps.digital/view_components/degree_row_content_component/view/degree_grade_is_not_required not sure if that will have an impact when used?

that component itself was originally poorly componentise as it needed it parents from govuk-summary-list to fulfil it styling


New Report: ML Production System For Detecting Covid-19 From Coughs

We included our report and added all relevant media into the assets/img/covid-19 folder.
Thank you so much for this amazing quarter!
Best,
Dilara Soylu, John Spencer, Lukas Haas

Hello! Was just reviewing the report and it seems like the images might not be showing up properly in this report? It could be that it corrects itself once it goes live.  Just wanted to suggest making sure the images in a markdown file were tagged with this syntax:

If so then it should be good to go!

Thanks for reviewing the pull request. The above image link, however, does not belong to our report but to a different one. Our report is the one called: "ML Production System For Detecting Covid-19 From Coughs". Since we didn't change any report except adding ours, it should all work as expected :)

Awesome! Yeah that was just for example purposes.
On Sat, Mar 27, 2021, 3:32 PM Lukas Haas @.***> wrote:

Thanks for reviewing the pull request. The above image link, however, does
not belong to our report but to a different one. Our report is the one
called: "ML Production System For Detecting Covid-19 From Coughs". Since we
didn't change any report except adding ours, it should all work as expected
:)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stanford-cs329s/reports/pull/13#issuecomment-808798531,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOPNPXAWPWALPK3L4R7TG3TFY6EDANCNFSM4ZSCXKXQ
.


Seg faulting MPI test

Running with OpenMPI 3.1.3 or HPE-MPI/MPT 2.17 or 2.20 under Slurm, get seg fault at cycle 900.
[cchang@el3 mpi]$ srun --ntasks 2 --time=5:00 --account=hpcapps --partition=debug --gres=gpu:2 ./jacobi
srun: job 1368607 queued and waiting for resources
srun: job 1368607 has been allocated resources
Single GPU jacobi relaxation: 1000 iterations on 7168 x 7168 mesh with norm check every 1 iterations
0, 21.164557
100, 0.593927
200, 0.354291
300, 0.261674
400, 0.211003
500, 0.178542
600, 0.155754
700, 0.138766
800, 0.125551
900, 0.114949
MPT ERROR: Rank 0(g:0) received signal SIGSEGV(11).
Backtrace for OpenMPI 3.1.3 run with single rank:
[r104u33:4212 :0] Caught signal 11 (Segmentation fault)
==== backtrace ====
2 0x000000000006858c mxm_handle_error()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/util/debug/debug.c:641
3 0x0000000000068adc mxm_error_signal_handler()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/util/debug/debug.c:616
4 0x0000000000035270 killpg()  ??:0
5 0x000000000014ad89 __memcpy_ssse3_back()  :0
6 0x000000000005b690 mxm_proto_set_data_buf_long()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/proto/proto_ops.c:315
7 0x00000000000659e7 mxm_self_channel_progress()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/tl/self/self_tl.c:183
8 0x000000000005629b mxm_proto_conn_switch_to_next_channel_finalize()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/proto/proto_conn.c:168
9 0x00000000000563b9 mxm_proto_conn_connect_loopback_invoked()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/proto/proto_conn.c:407
10 0x0000000000053d4c mxm_invoke_dispatcher()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/core/mxm.c:256
11 0x00000000000544ca mxm_notifier_chain_call()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/./mxm/util/datatype/callback.h:74
12 0x00000000001b0d07 mca_pml_yalla_progress()  ??:0
13 0x000000000005a91c opal_progress()  ??:0
14 0x00000000000547ec mxm_wait()  /var/tmp/OFED_topdir/BUILD/mxm-3.7.3111/src/mxm/core/mxm.c:369
15 0x00000000001b3311 mca_pml_yalla_send()  ??:0
16 0x00000000000b09fe PMPI_Sendrecv()  ??:0
17 0x000000000040a792 main()  ??:0
18 0x0000000000021c05 __libc_start_main()  ??:0
19 0x0000000000409849 _start()  ??:0
srun: error: r104u33: task 0: Segmentation fault (core dumped)

@chchang6 it looks like that your MPI is not cuda-aware? For example, OpenMPI needs to be build with --with-cuda option.

Should the OpenMPI example have been able to get to iteration 900 without being CUDA aware? Our OpenMPI 2.1.5 and 1.10.7 builds seg fault immediately, so that may well be the issue.
I'll check with HPE MPI, it appears an environment variable may need to be set. Thanks!

The Jacobi program first runs single gpu version (the output corresponds to this) that does not use MPI. After that, it runs the multi-gpu version and the program seg faults immediately.

That must be it. And I just tested MPT with the MPI_USE_CUDA=true environment setting, and it worked perfectly. So I think you nailed the cause, thank you!
From: Akhil Langer<EMAIL_ADDRESS>Sent: Monday, September 16, 2019 11:54 AM
To: NVIDIA/multi-gpu-programming-models<EMAIL_ADDRESS>Cc: Chang, Christopher<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [NVIDIA/multi-gpu-programming-models] Seg faulting MPI test (#3)
The Jacobi program first runs single gpu version (the output corresponds to this) that does not use MPI. After that, it runs the multi-gpu version and the program seg faults immediately.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NVIDIA/multi-gpu-programming-models/issues/3?email_source=notifications&email_token=ACX6ZLJIRI7TNROXUNDNNATQJ7B35A5CNFSM4IXE745KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Z7BOI#issuecomment-531886265, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACX6ZLOIWFQAPJI5HQJJDFTQJ7B35ANCNFSM4IXE745A.

Good to know that it works now. Also, try the nvshmem_opt version in that repo. It gives superior performance over mpi version. You can get nvshmem here: https://developer.nvidia.com/nvshmem

Hi Akhil--Actually, I double-checked and all the OpenMPI builds we're using (1.10.7, 2.1.5, 3.1.3) were built CUDA-aware. Still generating seg faults though. Some of the ompi_info cuda options follow. Not sure how mpi_built_with_cuda_support is true but mpi_cuda_support is false.
mca:mpi:base:param:mpi_built_with_cuda_support:value:true
mca:mpi:base:param:mpi_built_with_cuda_support:source:default
mca:mpi:base:param:mpi_built_with_cuda_support:status:read-only
mca:mpi:base:param:mpi_built_with_cuda_support:level:4
mca:mpi:base:param:mpi_built_with_cuda_support:help:Whether CUDA GPU buffer support is built into library or not
mca:mpi:base:param:mpi_built_with_cuda_support:enumerator:value:0:false
mca:mpi:base:param:mpi_built_with_cuda_support:enumerator:value:1:true
mca:mpi:base:param:mpi_built_with_cuda_support:deprecated:no
mca:mpi:base:param:mpi_built_with_cuda_support:type:bool
mca:mpi:base:param:mpi_built_with_cuda_support:disabled:false
mca:mpi:base:param:mpi_cuda_support:value:false
mca:mpi:base:param:mpi_cuda_support:source:environment
mca:mpi:base:param:mpi_cuda_support:status:writeable
mca:mpi:base:param:mpi_cuda_support:level:4
mca:mpi:base:param:mpi_cuda_support:help:Whether CUDA GPU buffer support is enabled or not

@Akshay-Venkatesh - any thoughts?

@chchang6 You may want to check with system admin if mca param opal_cuda_support has been set to false. The other thing is that UCX is the preferred way to use OpenMPI for CUDA-Aware MPI. UCX sections in the following links should help:
https://www.open-mpi.org/faq/?category=buildcuda
https://www.open-mpi.org/faq/?category=runcuda

@Akshay-Venkatesh Thank you very much, you hit exactly on 2 of our issues. opal_cuda_support is false, and OpenMPI was built without UCX.

Just wanted to wrap this thread by reporting I built OpenMPI 3.1.3 with UCX and CUDA support, and was able to get the tests running over multiple GPUs on single and multiple nodes. Thanks again for your help!

Awesome! Thanks for the update.


test: add error descriptions / narration to kvstore test

This gives more context when the test fails.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>I did this when I noticed during #5773 that the test failure logs were not conducive for debugging.

This change is

Holding off testing until #5775 is merged.

test-me-please


app:cp_itemTextColor causes crash

How to reproduce:
In xml layout, set
app:cp_itemTextColor="@android:color/black"
Runtime Exception shows that CollectionPicking is trying to interpret a resolved color (0xFF000000) as a color id.
I think the issue is that
this.mTextColor = typeArray.getColor(R.styleable.CollectionPicker_cp_itemTextColor, mTextColor);
gives you a resolved color int, not an id int, if passed in via xml. Fixable by passing resolved color to View, and setting private int mTextColor = 0xFFFFFFFF;

Hi was there a fix for this? Having the same issue


[INLONG-114] Support consumers to adjust consumption targets without restarting

Users have reported a requirement that when the system uses TubeMQ, it will frequently modify the consumption topics or filter items. Can the system increase the consumption theme or filter items without restarting? it is very good for the business experience if If this function completed
1. The consumer only needs to fill in the target server, consumer group, user name, and password to consume directly; during the consumption process, consumers are allowed to adjust the consumption range, such as increasing and decreasing Topic, increasing and decreasing filtering tid, without restarting the customer Terminal program
JIRA link - [INLONG-114] created by gosonzhang

Closed due to long periods of inactivity
Please reopen it if needed


ELB response gives empty list for missing load balancer instead of thrown exception

Boto behaviour:
In [9]: conn.get_all_load_balancers()
Out[9]: [LoadBalancer:STICKYLB]
In [10]: conn.get_all_load_balancers(load_balancer_names='aaa')
BotoServerError: BotoServerError: 400 Bad Request
Cannot find Load Balancer aaa
moto behaviour:
In [14]: conn.get_all_load_balancers()
Out[14]: [LoadBalancer:STICKYLB]
In [14]: conn.get_all_load_balancers(load_balancer_names='aaa')
Out[14]: []

Thanks for opening!
Fixed with https://github.com/spulec/moto/commit/5d421dc343046bda58220b047133d5b418248ee8


Add support to add new extra pod labels

What should the feature do:
This feature must be add support to add new pod labels in /spec/template/metadata/labels in deployment.
What is use case behind this feature:
There are cases that we need add pod labels in /spec/template/metadata/labels and at the moment is not possible add new pod labels.

I want to work on this

https://github.com/topolvm/pvc-autoresizer/pull/208

Resolved in PR: https://github.com/topolvm/pvc-autoresizer/pull/208


upgrade to v1.2.11

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@ghisvail would you mind merging this please? currently the conda distrib is broken, and I need it to install PETPVC on some machines...
thanks!

Hi Kris, sorry for the late reply.
I believe this issue has already been taken care of automatically by #6.
Feel free to update yours if that's not the case.
I'll ping the conda-forge admin team to add yourself as maintainer.
Best regards.
Le sam. 4 mars 2023, 09:52, Kris Thielemans @.***> a
écrit :

@ghisvail https://github.com/ghisvail would you mind merging this
please? currently the conda distrib is broken, and I need it to install
PETPVC on some machines...
thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/petpvc-feedstock/pull/5#issuecomment-1454667976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO7U35E2RJVDWEO2ET4WF3W2L7DRANCNFSM6AAAAAAVNASW3U
.
You are receiving this because you were mentioned.Message ID:
@.***>

indeed


Dagger 2 cannot inject on static methods?? Is there any way we can get this done

@Inject
public static ExampleInterceptor get() {
if (sInterceptor == null) {
sInterceptor = new ExampleInterceptor();
}
return sInterceptor;
}

Same issue, any comment


cut new release with build.zig.zon and mem leak fixes

should include #10 #11 #7 and #8 so zig fetch works.

Hi, 0.2.0 has been released.


[Enhancement] Limit the Number of Delete Rowsets in Compaction to Prevent Version Accumulation Errors

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
In the current compaction process, delete rowsets must be merged during the base compaction phase. If there are too many delete rowsets, the system must wait for the base compaction to merge them. Since base compaction runs infrequently, an excessive number of delete rowsets can delay compaction, resulting in too many versions waiting for compaction and eventually causing errors.
Solution

Implement a check during every delete operation to verify if the tablet already contains too many delete rowsets.
The threshold for the number of delete rowsets should be configurable via a setting in config.
If the number of delete rowsets exceeds this threshold, return an error to prevent further accumulation.

This solution aims to ensure that the compaction process is performed in a timely manner and prevent excessive versions from causing errors due to delayed compaction.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi! I'd like to try out this issue. Could you assign it to me?

please assign to me


fix: Updated sec fix to Github workflows to pr commit sha

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Security recommendation fix for github workflows to run plan-examples

This is the SHA (${{github.event.pull_request.head.sha}}) of the latest commit on the head branch of the pull request. It's a unique identifier that always points to the same, specific commit.

It's immutable and will not change, even if the PR is updated with new commits.

Motivation

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
[ ] Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
[x] Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

LGTM 🚢


DHT sensor not working

Home Assistant release with the issue:
0.73.1
Last working Home Assistant release (if known):
0.72
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
Pi
Description of problem:
Since update DHT sensor attached to Pi has stopped working.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Same problem here. HA claims that:
2018-07-15 01:28:17 ERROR (SyncWorker_12) [homeassistant.util.package] Unable to install package Adafruit_Python_DHT==1.3.2: Command "/srv/homeassistant/bin/python3.6 -u -c "import setuptools, tokenize;file='/tmp/pip-install-_z4tai3t/Adafruit-Python-DHT/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-c_o9iewz/install-record.txt --single-version-externally-managed --compile --install-headers /srv/homeassistant/include/site/python3.6/Adafruit-Python-DHT" failed with error code 1 in /tmp/pip-install-_z4tai3t/Adafruit-Python-DHT/

Good job writing this informativ bug report! Maybe same issue like https://github.com/home-assistant/home-assistant/issues/15333

Duplicate as #15333


Skip named types used in Widget State class declarations

Added a check in visitNamedType to skip named types if they are used in Widget State class declarations. This prevents these specific named types from being recorded as used.

@rubenlop88 thanks for your contribution!!!


[FIX]: Search bar selection error.

Fix issue #83

@nepalivai Kindly resolve the conflicts.

@singodiyashubham87 conflict resolved

@nepalivai You have merged the main branch into your working branch and removed the changes you have made, add the classes again.
Merging this PR now will not make any effect as there are 0 files changed.

Hey @singodiyashubham87, very sorry for the inconvenience. you can check it out now.

@nepalivai LGTM!


Upgrade clap to latest RC, fix imports

Quick fix to some imports that changed since the last beta. I'm ok sitting on an rc release as we were on beta before anyway.
I think this breakage might have been caused by Cargo's versioning/semver rules picking a later beta than the one specified.

Thanks!


[BUG] no Longer works

Steps to reproduce:
install TamperMonkey or similar
install from https://github.com/avallete/yt-playlists-delete-enhancer/raw/gh-pages/yt-playlists-delete-enhancer.user.js
go to https://www.youtube.com/playlist?list=WL
Expected results:
every video has a delete button on its row
Actual results:
none
Notes:
Firefox 101. used to work before (pretty sure it was this userscript)

Hi there,
There is only a global remove button, in the screenshot the cross and circles are only here to show which videos would be deleted / kept in the playlist depending on the "percent of viewing" parameter.
Could be worth to have some kind of visulatization with the plugin itself tough.


Animation desync between arms and legs

The arms and legs are not moving at the same frequency, resulting in the right arm sometimes swinging forward together with the right leg, and sometimes together with the left leg, and vice versa for the left arm. Example where I synced the animation through video software

Hope they get around to fixing this. It's the only reason I don't use this mod.

I did some extensive testing, and I figured out what to change.
A fork of this resourcepack was made by @erinsc here https://github.com/erinsc/Fresh-Moves, which updates the resource pack to 1.21.3 (works on .4 as well), and does some other smaller updates. Their version is called 3.1.0
I then made a fork of that fork, and added the fix for the arms and legs sync issue here https://github.com/ClaraTheRed/Fresh-Moves. I call this version 3.2.0. The download for the folder is here https://github.com/ClaraTheRed/Fresh-Moves/archive/refs/heads/main.zip. Extract the folder, and take out the "Expressive Fresh Moves v3.2.0" folder or the "Eyeless Fresh Moves v3.2.0" and put them in your resourcepack folder
I also made a pull request to the repository owned by @erinsc, and I hope they will create a pull request to this main repository after mine is merged.


Fix redirects with anchor links

To redirect to urls with an anchor we need to force a reload

Wait a minute @jonathan-neugber @iamqqv
The comment says it is for redirects with anchor, yet there is no condition whatsoever, so it is reloaded in every case. Is this really a desirable behavior?

@felixkempf this forces a reload if none happens. If window.location triggers a page change no JS the reload(true) does nothing (at least according to specification). We tested it anyways and it worked so far.

Oh, so it's for the case that the redirect action is the same as the original, only the anchor changes?

Depending on browser and version any url that contains a # will not trigger a redirect on setting window.location. So using the reload(true) is for those cases otherwise the browser will happily ignore it.


The bars in the graphs which are having the exact values included in the tooltips are not accessible with keyboard keys.

Expected behavior
The bars in the graphs which are having the exact values included in the tooltips should be accessible with keyboard keys.
Current behavior
The bars in the graphs which are having the exact values included in the tooltips are not accessible with keyboard keys.
Reproducible sample
https://codepen.io/Roopesh-T/pen/zYMvVqE
Optional extra steps/info to reproduce
Test Environment:
Edge Version 115.0.1901.203 (Official build) (64-bit)
Windows 11 Enterprise 22H2 22621.1702
Steps to Reproduce:

Hit enter on this link https://codepen.io/Roopesh-T/pen/zYMvVqE
Tab to the graph present in the Code pen.
check if the individual bars present in the graph are accessible with keyboard.

Possible solution
No response
Context
No response
chart.js version
v3.7.16
Browser name and version
Edge Version 115.0.1901.203 (Official build) (64-bit)
Link to your project
No response

CanvasJs is another library than chart.js so you will need to file this issue by them. We can't do anything about this
https://canvasjs.com/


[resolves #283] Usage of camel-cxf depends on TCCL

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/189/
Test PASSed.


Add option for Jupyter Notebook / Lab

For early development stages and testing, it would be good to be able to run Jupyter Notebooks inside the container.
This will of course require additional privileges, namely write-access to the working directory and exposing the HTTP server to the host.
There should be a warning if the current directory is not */notebooks, because one could otherwise expose a critical directory to write-access.

Jupytext and other useful packages should also be added

Done via #14.


Add support for Windows

Blocked waiting for release of v0.0.2 of https://github.com/discordjs/voice/

Can use dshow for Windows machines instead of pulse. Requires a fix in the latest prism-media (released) and a new feature in @discordjs/voice and dependency upgrade (unreleased as of now)

Done!


Gitignore cached folder & npm logs

nice timing heheh https://github.com/moose-team/friends/commit/a133558784b0d2fc4a7eb41a7b5ddafc9aec24d1


Crash when installed on client only

message(1).txt

Seems to be duplicated with #1
Again, I can't reproduce this crash in both develop and production environment with only Forge and the mod installed.
I need a smaller and simpler test environment to solve the problem, instead of being given some random 100+ mods to find the one to blame.

I had this crash as well on 1.18.2.
So, I spent a couple weeks play testing my modpack in single player with this mod installed and never once had a crash. However, within 15-30 minutes of playing on a dedicated server, with this mod only on the client and not the server, I experienced this same crash.
I updated to the 1.0 version, but also put the mod on the sever and have not had a crash since. So not sure if it was the update that fixed it or putting it on the server, but maybe something for you to explore. I know this is supposed to be an entirely client side mod, but maybe something is acting funny there.
Looking at both this issue and #1, both are also on dedicated servers too I believe.

Looking at both this issue and #1, both are also on dedicated servers too I believe.

After testing on dedicated server, I find this could be caused by Forge's default behavior of forcibly syncing registries between server and client, causing any registry cannot be done only on client side.
This, however, is actually unfixable, its Forge's nature, and Visuality can't work without custom particles.
So, I'm gonna close this and claim the fact that Visuality: Reforge is not a client-side mod anymore.

Fixed in version 2.0 :)


Adapt singleuser Docker image to use tini

Wonder if it should just be migrated to be one of the docker-stacks images.
/cc @parente

https://github.com/jupyter/dockerspawner/blob/master/singleuser/Dockerfile is already FROM jupyter/scipy-notebook which is one of the docker-stacks images.

D'oh.


Make search scroll to the nearest match

It would be nice if the app automatically scrolled to the nearest match in the word list as you entered a search term. It's kind of painful to scroll through the word list manually because it's so long, but this would make navigating the it a lot easier. If you did it this way you could probably retire the search drop-down as well.

Thanks for the suggestion! It would definitely be nice to make navigating the lexicon easier.


New workflow submission: UML State Machines

PR: https://github.com/aws-samples/step-functions-workflows-collection/pull/36
To submit a workflow to the Step Functions Workflows Collection, submit an issue with the following information.
To learn more about submitting a workflow, read the publishing guidelines page.

Use the model template located at https://github.com/aws-samples/step-functions-workflows-collection/tree/main/_workflow-mode to set up a README, template and any associated code.

All the information below must be provided in the "example-workflow.json" file cloned from the model **

Note the following information for the model:

Description (intro.text) should be a 300-500 word explanation of how the pattern works.
Simplicity: must be 1 of (1 - Fundamental, 2 -  Pattern, 3 - Application )
Diagram: This must link to an Exported PNG of the workflow that shows any service integrations, you can export this from Workflow studio.
Type: Must be one of (Standard, Express)
Resources should link to AWS documentation and AWS blogs related to the post (1-5 maximum).
Framework: currently, we support SAM or CDK.
Author bio may include a LinkedIn and/or Twitter reference and a 1-sentence bio.

You must ensure that the sections of the model README.md are completed in full.

Published.


Update deps to latest versions

Let's see what this does to the tests :shipit:

Lets not do this blindly.


[feat] Add configuration to ignore redirecting to next url

Fixes #320
Added new settings HIJACK_IGNORE_NEXT_URL to control the behavior of redirection.
It defaults to False to maintain backward compatibility.
When HIJACK_IGNORE_NEXT_URL is set to True, both AcquireUserView and ReleaseUserView will always redirect to their predefined success_url, regardless of whether a next URL is provided by the template or not.

Hi @BinDruid,
Thank you for reaching out. I'd recommend starting a discussion before submitting new features. Generally, we avoid adding settings or configuration, to keep the complexity of this package low. In tern, low complexity enables us to maintain a high security standard.
That being said, I would encourage you to simply overwrite the hijack/notification.html template and exclude the next field in your project to alter the behavior.
Please don't hesitate to bring this up again, in a new discussion.
Best,
Joe


cmd version has no version

observed behavior:
cmd version command is showing empty version when git clone repo.
expected behavior:
cmd version shows version information when git clone.
AC1: it does shows version when cmd version is called
AC2: ldflags still works when new release

there is a flag experimental to help work on development mode.
Although, the LD Flags is the expected path:
go build -ldflags="-X github.com/kubefirst/kubefirst/configs.K1Version=1.8.6" .

If used --experimental-mode on init, that will make main the brach to be cloned, preventing issues with the lack of version.


Fix: Preserve input dtype in Dropout layer output

Modified Dropout implementation to ensure that the output dtype matches the input dtype.
This resolves the issue #1321

Proposed changes
I re-ordered the equation that calculated Dropout to preserve the input dtype. The underlying problem in Issue #1321 mentioned https://github.com/ml-explore/mlx/issues/1321#issuecomment-2285606325
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

Thanks for the fix! Two comments:

Could you add a test to https://github.com/ml-explore/mlx/blob/main/python/tests/test_nn.py#L962
I would use parenthesis to be extra explicit here. The python order makes sense but it might not be as obvious to people reading the code that the order shouldn't be changed.

Hi @awni , I found a serious bug in the complete testing directory.
https://github.com/ml-explore/mlx/blob/1086dc4db070d4f7d211f2bb760f560b98f969f7/python/tests/test_nn.py#L1002
While I had already tested before submission, I realized something is wrong and thus read the mlx_test.py code.
Here you are not overriding the assertTrue in any other form.
Thus many of the test cases written in python/tests with self.assertTrue  like
https://github.com/ml-explore/mlx/blob/1086dc4db070d4f7d211f2bb760f560b98f969f7/python/tests/test_nn.py#L1002
https://github.com/ml-explore/mlx/blob/1086dc4db070d4f7d211f2bb760f560b98f969f7/python/tests/test_nn.py#L960
assertTrue(x,y) would treat x as expression and y as message.
I think the correct function to use is assertEqual or we can use assertTrue( x==y) .
If you agree, I can open another PR regarding these changes.

I think the correct function to use is assertEqual or we can use assertTrue( x==y) .

Those are indeed bugs. The right function is assertEqual. Would be great if you could send a PR to fix it.

Yeah, I'll add them in this PR itself. There were less than I anticipated.

I added the changes, let me know if you have any suggestions. Thanks for the review !!


Tree-sitter compatibility with stable and beta

A hurdle to writing Tree-sitter grammars for Atom (that I've hit at least) is versioning of everything. What I've gathered is that, at this point in time,

Stable Atom uses tree-sitter-cli: "^0.12.5" , and
Beta Atom uses tree-sitter-cli: "^0.13.5"

Just now, if I built the parser for one then it would not work in the other. Building it for beta caused stable to refuse to open the file at all; it just effectively ignored any attempt to do so. Building for stable gave a broken parse tree in beta.
(I already say build it locally with node version 8.9.3 to avoid other version issues besides dependencies.)
Is there a guide or best practice here? If I were writing a grammar for use in Atom, what should I do to make it compatible with whatever version of Atom the user has? I'm trying to write a beginner's guide for this, so any tips are appreciated.
The goal is to supplement the official docs with a "from scratch" guide for anyone who wants to make a grammar for use in Atom. It's started here.
/cc @maxbrunsfeld ?

Yeah, sorry this has been a bumpy ride. I'm hopeful that soon, I'll stop having to make changes to Tree-sitter's parser ABI.

What I've gathered is that, at this point in time, stable Atom uses tree-sitter-cli: "^0.12.5" , and beta Atom uses tree-sitter-cli: "^0.13.5"

Yeah, my approach for now is to use the npm modules' minor version numbers to indicate the Tree-sitter ABI version that they use. So for the tree-sitter and tree-sitter-cli modules, as well as every parser, 0.13.x is the latest ABI version.

Building it for beta caused stable to refuse to open the file at all

Yeah, that is due to an a bug in Atom that was fixed in https://github.com/atom/atom/pull/17424.

Building for stable gave a broken parse tree in beta.

What did you see in this case? Hopefully you got an error in the console and it failed to load the grammar? That's the current expected behavior.

The goal is to supplement the official docs with a "from scratch" guide for anyone who wants to make a grammar for use in Atom.

That would be so great! I don't have a great plan for dealing with this other than to stop changing the ABI version. Hopefully there will be no more changes for a while so that once Tree-sitter is enabled by default, people don't have to think about versioning.
For now, since this is an experimental feature, I would just advise building with the latest tree-sitter-cli and targeting beta only.

Also, in case you hadn't seen them, the existing docs for creating grammars are at http://tree-sitter.github.io/tree-sitter/creating-parsers. These docs aren't focused on Atom specifically though.

Hopefully you got an error in the console and it failed to load the grammar?

I got a couple of errors, but it did try to apply something to the file. Those stars kept multiplying too; there were none when I first checked the scope, then I checked other places and came back to find three. It also says it's using the grammar in the status bar (this is v1.30.0-beta1)

I'm hopeful that soon, I'll stop having to make changes to Tree-sitter's parser ABI.

Yeah, I figured things would settle down eventually. Would it still be an issue if you ever update the ABI when Tree-sitter becomes enabled by default? Or would that not need to happen to still make updates?
And wouldn't there also be issues when the Nodejs version itself is ungraded? I noted that I build with node 8.9.3 installed because I ran into NODE_MODULE_VERSION errors a lot when starting out.
I don't know how much of this can be automated by Atom, because I don't actually know much about the generated files (especially how the src files are supposed to be used to write external rules). Maybe the language package on Atom's side can specify specific tree-sitter parser versions for different Atom version ranges? It would mean updates can be safely released without breaking stuff for half the people.


fix config file error

we found an error in openimages config file: parameters "iou_thr" and "ioa_thr" in OpenImagesMetric  should actually be ""iou_thrs" and "ioa_thrs" according to it's defination.

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

Hi @wufan-tb
Thanks for your kind PR. It seems that CLA is not signed. Could you sign the CLA so that eventually we could merge this PR after review? You can check the contents and follow the instruction in the communication box shown as below

Seems the lint has failed, please follow https://github.com/open-mmlab/mmcv/blob/2.x/CONTRIBUTING.md to install the pre-commit hook.
Also, this PR should merge in dev-3.x, so the PR should base on dev-3.x branch.

The failure of lint is not caused by the code, so this PR is merged.


Sliding map up on opening keyboard.

I have a screen where I am rendering the following components:

Mapview
TextInput
Text                                                                   -- all of them placed in column-wise fashion.

The textInput and Text components are enclosed in a AvoidKeyboardView style.
All of these components have StyleSheet.absoluteFillObject styling attribute set on them.
When I click on the TextInput component, the keyboard pops up but overlaps over the TextInput and Text component.
I found that this was because of the StyleSheet.absoluteFillObject styling attribute which was set to these components.
Once I removed this attribute, both of these components were moving up on clicking on the TextInput component.
But I found out that the map component was not moving up on opening up the keyboard.
So I removed the StyleSheet.absoluteFillObject attribute on the MapView component and found that the map disappeared completely. Later I came to know that this attribute is needed to render map.
My question now is, how do I get the MapView to move up along with the rest of the components on opening up the keyboard ?

Hello, I have the same problem, could you solve it?

Hi, did you find a solution to this?

Hi, i have the same problem , please help

Hi, i have the same problem , please help

Hi, could you show me your code, I left the project I was working on a few months ago, but I remember the problem was with the styles.

This is exactly my issue at the moment on Android with react-native-maps 0.28.1.  Working on it since 3 days, still no solution.

+1 same


HADOOP-17786. Parallelize stages in Jenkins

We now build Hadoop on multiple platforms
for validation. We need to parallelize them
for faster validation.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 31s

Maven dependency ordering for branch

+1 :green_heart:
shadedclient
15m 26s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 8 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
15m 39s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

47m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3166

Optional Tests
dupname asflicense codespell shellcheck shelldocs

uname
Linux e05c3d46624a 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d20f84a6956c5e4c3c4c3d9e7edc43585f8133e6

Max. process+thread count
524 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/2/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
37m 55s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  1s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
43m 59s

trunk passed

+1 :green_heart:
compile
5m 43s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
6m 16s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
mvnsite
0m 33s

trunk passed

+1 :green_heart:
shadedclient
20m 55s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 31s

the patch passed

+1 :green_heart:
compile
5m 42s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
cc
5m 42s

the patch passed

+1 :green_heart:
golang
5m 42s

the patch passed

+1 :green_heart:
javac
5m 42s

the patch passed

+1 :green_heart:
compile
6m 52s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
cc
6m 52s

the patch passed

+1 :green_heart:
golang
6m 52s

the patch passed

+1 :green_heart:
javac
6m 52s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
21m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
43m 46s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
1m 24s

The patch does not generate ASF License warnings.

201m 14s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_ops_hdfs_static

test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_test_native_mini_dfs

test_libhdfs_threaded_hdfspp_test_shim_static

test_hdfspp_mini_dfs_smoke_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3166

Optional Tests
dupname asflicense codespell shellcheck shelldocs compile cc mvnsite javac unit golang

uname
Linux aeab8e924c32 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 16ebf88db8bfbc0f8ec60f5c5c1c739dca4baa38

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/testReport/

Max. process+thread count
520 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
48m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 26s

trunk passed

+1 :green_heart:
compile
6m 31s

trunk passed

+1 :green_heart:
mvnsite
1m 24s

trunk passed

+1 :green_heart:
shadedclient
66m  3s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s

the patch passed

+1 :green_heart:
compile
4m 48s

the patch passed

+1 :green_heart:
cc
4m 48s

the patch passed

+1 :green_heart:
golang
4m 48s

the patch passed

+1 :green_heart:
javac
4m 48s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 53s

the patch passed

+1 :green_heart:
shadedclient
26m 39s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
51m 56s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
1m 45s

The patch does not generate ASF License warnings.

203m 57s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_test_native_mini_dfs

test_libhdfs_threaded_hdfspp_test_shim_static

test_hdfspp_mini_dfs_smoke_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3166

Optional Tests
dupname asflicense codespell shellcheck shelldocs compile cc mvnsite javac unit golang

uname
Linux d4c936a36643 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 16ebf88db8bfbc0f8ec60f5c5c1c739dca4baa38

Default Java
Red Hat, Inc.-1.8.0_302-b08

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/testReport/

Max. process+thread count
615 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/console

versions
git=2.27.0 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
34m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
50m 52s

trunk passed

+1 :green_heart:
compile
6m 24s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
shadedclient
28m 31s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 25s

the patch passed

+1 :green_heart:
compile
5m 54s

the patch passed

+1 :green_heart:
cc
5m 54s

the patch passed

+1 :green_heart:
golang
5m 54s

the patch passed

+1 :green_heart:
javac
5m 54s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
1m 12s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
26m 54s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
113m  5s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 58s

The patch does not generate ASF License warnings.

275m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3166

Optional Tests
dupname asflicense codespell shellcheck shelldocs compile cc mvnsite javac unit golang

uname
Linux b43ef5bce072 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 16ebf88db8bfbc0f8ec60f5c5c1c739dca4baa38

Default Java
Debian-11.0.11+9-post-Debian-1

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/testReport/

Max. process+thread count
532 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/4/console

versions
git=2.30.2 maven=3.6.3 shellcheck=0.7.1

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
46m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 51s

trunk passed

+1 :green_heart:
compile
5m 18s

trunk passed

+1 :green_heart:
mvnsite
0m 48s

trunk passed

+1 :green_heart:
shadedclient
66m 55s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 22s

the patch passed

+1 :green_heart:
compile
3m  2s

the patch passed

+1 :green_heart:
cc
3m  2s

the patch passed

+1 :green_heart:
golang
3m  2s

the patch passed

+1 :green_heart:
javac
3m  2s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 23s

the patch passed

+1 :green_heart:
shadedclient
18m  3s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
84m 48s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
1m 33s

The patch does not generate ASF License warnings.

224m 50s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_ops_hdfs_static

test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_test_native_mini_dfs

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3166

Optional Tests
dupname asflicense codespell shellcheck shelldocs compile cc mvnsite javac unit golang

uname
Linux c9fc6c9774f1 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 26529d07f8139a392e246f7068dea98ad13a93fc

Default Java
Red Hat, Inc.-1.8.0_302-b08

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/6/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/6/testReport/

Max. process+thread count
601 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3166/6/console

versions
git=2.27.0 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


C67: crash in resource_coordinator::TabManager::SetTabAutoDiscardableState

Chromium 67 is refactoring resource_coordinator::TabManager: https://bugs.chromium.org/p/chromium/issues/detail?id=775644. We have a work-in-progress commits here https://github.com/brave/muon/commit/4db5e9232d16e962db4a615957fdb4107722119f and here https://github.com/brave/muon/commit/06917c6c9a70450048693f0a8463310ea80eaa66
Thread 1 "brave" received signal SIGSEGV, Segmentation fault.
0x0000000002f45390 in resource_coordinator::TabManager::SetTabAutoDiscardableState (
    this=<optimized out>, contents=<optimized out>, state=true)
    at ../../chrome/browser/resource_coordinator/tab_manager.cc:348

Fixed at https://github.com/brave/muon/pull/596/commits/12393d073b6b2afe7e965d64b231e03c62a5b420


Migrate from jsr305 to checker framework

Signed-off-by: liach<EMAIL_ADDRESS>Fixes https://github.com/SpongePowered/SpongeAPI/pull/1995#issuecomment-490771299
Some immutable and threadsafe annotations are dumped; they should be replaced by proper "nolock" "locking" annotations instead.

@Xakep_SDK Requesting a review from you as well.

Looks good for me.
I request removing jsr305 from here too: https://github.com/SpongePowered/plugin-meta

Big :+1: from me.

Mind sharing the reason for this change?
What are the benefits from using the checkerframework vs jsr305? Is it because jsr305 is dormant?

JSR305 never was standard
Doesn't support java 8 features, e.g. you can't do List<@Nullable String> s
Has compatibility issues with java modules
JSR305 works with modules, but you need to know how to deal with split packages, while checkerframework just works

Reasons for @ST-DDT:

jsr305 breaks with Java 9+ module system;
checker framework has type use annotations, e.g. Supplier<@NonNull T> cannot supply null while Predicate<@Nullable T> can test null.
checker framework is more complete: it has annotations for calls to methods in constructors, locking conditions, optional presence, taint/no taint, etc., compared to jetbrains annotations or jsr305.
if we want to verify the validity, we can add checker framework's non-qual part to our test dependencies so that we can use checker itself to test the validity of our annotations.

I don't see a specific issue with this in general.
I'm not familiar with checkerframework so I'll ask, is there a way to use meta-annotations on NonnullByDefault to alias @org.checkerframework.framework.qual.DefaultQualifier(org.checkerframework.checker.nullness.qual.NonNull.class) like was done with @NonNull such the checkerframework can still work with it? I know we're breaking things left right and centre for 8 but keeping this annotation, if possible, doesn't really cost anything, is arguably more readable and it does make the diff a lot smaller making it easier to port any changes we might have to make on top. It would also help if we have to make a wholesale change across all packages in the future for whatever reason and we can just change the meta-annotation on our annotation.
If not, sure, no problem, but I figured I'd ask.

Nah. I don't think checker framework allows annotations to be an alias for other annotations, hence even if we keep @NonnullByDefault, it would no longer be effective.

On a side note, we might consider adding a qualifier annotation set for server thread access, similar to that for gui access check. Opinions? https://checkerframework.org/manual/#guieffect-checker

Manually merged into api-8. Thanks @liach !

thanks zidane!


Consume-api

Highlights

[x] Consume api
[x] ensure all linters pass
[x]  add functionality for the Check status button click

The license issue has been resolved as seen in the image below


Add view for remove liquidity

When a user exits their liquidity, they need to be able to see what they currently have, and what they will get after they have exited.

Designs can be found here; https://miro.com/app/board/uXjVOynDXW4=/


[Code] Linear Regression Metrics Review

A peer-review of the linear regression model metric is needed. Review MAE, MSE, Root MSE, R^2-score. It seems there is an issue with R^2-score.

Fixed with the  64e1b03d50b6945063a971c70a37649c4a0138d7  commit.


duplicate information in the initiate negotiation api request

Feature Request
Currently in the POST /v2/contractnegotiations request the ContractRequest body has this structure:
{
  "@context": {
    "edc": "https://w3id.org/edc/v0.0.1/ns/",
    "odrl": "http://www.w3.org/ns/odrl/2/"
  },
  "@type": "ContractRequest",
  "connectorId": "provider",
  "connectorAddress": "http://localhost:19194/protocol",
  "consumerId": "consumer",
  "providerId": "provider",
  "protocol": "dataspace-protocol-http",
  "offer": {
    "offerId": "MQ==:YXNzZXRJZA==:YTc4OGEwYjMtODRlZi00NWYwLTgwOWQtMGZjZTMwMGM3Y2Ey",
    "assetId": "assetId",
    "policy": {
      "@id": "MQ==:YXNzZXRJZA==:YTc4OGEwYjMtODRlZi00NWYwLTgwOWQtMGZjZTMwMGM3Y2Ey",
      "@type": "use",
      "odrl:permission": [],
      "odrl:prohibition": [],
      "odrl:obligation": [],
      "odrl:target": "assetId"
    }
  }
}

As you can see, the offerId and the policy/@id have the same value, because they're representing the same information, so there's no point in offerId, as the policy is mandatory anyway.
The proposal would be to remove offerId, and maybe inline the offer object and have assetId and policy at the root level, to have something like:
{
  "@context": {
    "edc": "https://w3id.org/edc/v0.0.1/ns/",
    "odrl": "http://www.w3.org/ns/odrl/2/"
  },
  "@type": "ContractRequest",
  "connectorId": "provider",
  "connectorAddress": "http://localhost:19194/protocol",
  "consumerId": "consumer",
  "providerId": "provider",
  "protocol": "dataspace-protocol-http",
  "assetId": "assetId",
  "policy": {
    "@id": "MQ==:YXNzZXRJZA==:YTc4OGEwYjMtODRlZi00NWYwLTgwOWQtMGZjZTMwMGM3Y2Ey",
    "@type": "use",
    "odrl:permission": [],
    "odrl:prohibition": [],
    "odrl:obligation": [],
    "odrl:target": "assetId"
  }
}

Which Areas Would Be Affected?
api
Why Is the Feature Desired?
simplify
Solution Proposal
this shouldn't be a breaking change, deprecation model should be used.

+1


[PATCH] Add semantic pr github action

Codecov Report

Merging #15 (3a60de6) into main (add9ba0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   97.56%   97.56%
=======================================
  Files           7        7
  Lines         369      369
=======================================
  Hits          360      360
  Misses          9        9

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Strip dependencies from REST client

:mag: Description
This PR removes two dependencies from the kyuubi-rest-client module

commons-collections - has CVE Cx78f40514-81ff and is only used in one place, just rewrite to remove the dependency
javax.servlet-api - only used for UT, correct the scope from compile to test

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Pass GHA

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (5623ead) to head (c24af70).

Files
Patch %
Lines

...main/java/org/apache/kyuubi/client/RestClient.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6457   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         675     675
  Lines       41641   41641
  Branches     5685    5685
======================================
  Misses      41641   41641

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

I believe dep check script reports a false negative result, could you please confirm that? @cfmcgrady

Thanks, merged to master/1.9


[organization] dragging document into stack from another space

dragging a document from another space into a stack will duplicate the item in the originating space as opposed to moving/copying it into the target space

@zhenyasav would it be desirable for this to create a cross-space reference?

#7003

resolved:

[ ] first lets just fix the bug so the default experience is cheapest and unbroken
[ ] add space-reference option by default
[ ] add user-choice infrastructure

possible to just "disallow dragging from another space into a stack" as a cheaper solution for step 1 above


Add optional create collection params

Closes #27
Follows the same pattern as in #20

@rsjethani in case you are fine with my changes, you can approve it directly.
I will squash and merge then with a proper commit message 🙂


Add favicons and logo

Fixes https://github.com/jupyter/jupyter_server/issues/283
It creates a favicons subfolder in the static folder, and also adds the logo.png.
A default favicon.ico is present in the root static folder, and the more custom ones (including the default one) are present in that favicons folder./

Released as jupyter_server-1.0.0rc7

Brilliant! Thanks, @echarles 🚀


Can't add memory

🐛 Describe the bug

New memories can't be added or can't be searched.
Code:
import os
from mem0 import Memory

config = {
    "vector_store": {
        "provider": "qdrant",
        "config": {
            "collection_name": "test",
            "host": "localhost",
            "port": 6333,
            "embedding_model_dims": 768,  # Change this according to your local model's dimensions
        },
    },
    "llm": {
        "provider": "ollama",
        "config": {
            "model": "llama3.1:latest",
            "temperature": 0,
            "max_tokens": 8000,
            "ollama_base_url": "http://localhost:11434",  # Ensure this URL is correct
        },
    },
    "embedder": {
        "provider": "ollama",
        "config": {
            "model": "mxbai-embed-large:latest",
            # Alternatively, you can use "snowflake-arctic-embed:latest"
            "ollama_base_url": "http://localhost:11434",
        },
    },
}

# Initialize Memory with the configuration
m = Memory.from_config(config)
print("loaded\n")
# Add a memory
print(m.add("I'm visiting Paris", user_id="john"), end="\n\n")
# Retrieve memories
print(m.search("Paris", user_id="john"), end="\n\n")
print(m.get_all(user_id="john"), end="\n\n")

Not sure if it's a bug. Not everything is saved to memory so in the context of a chat conversation you might need to have a few back and forth chats before something is saved to memory. I might be wrong though 😅

You are right. This is not a bug. I tested it with a lot more messages, and it does add stuff. It just that it depends a lot on the capability of the LLM


Prompt design polish

prevent cropping on characters on 2nd line
Ensure theres spacing between text and button
Secondary title
Survey description

🤩the design update with animation.
https://github.com/bcc-code/bcc-media-platform/assets/88234679/f4d7c254-6136-4c69-8bd3-adb0d6c79c9d
https://github.com/bcc-code/bcc-media-platform/assets/88234679/b6320482-6bd7-4111-a5d5-6f2d517d15c0
5.1.3+2300113  ios17.2
Found 2 bug:

When I click close survey after completing a survey, the app goes blank. Unable to navigate anywhere. Had to quit app to solve this
After quitting, the quiz is still available. Tried reproducing multiple times and it either gives an error message or to the state described in bug 1


Full-Stack-Capstone-Backend

Hello reviewer ,
When we started this Project we were group of 5 partners but now we are group of three partners so we have implemented ( requirements.
Link to front-end PR : https://github.com/bhushan354/Full-Stack-Capstone-Frontend/pull/21
Project Requirements : -

The user logs in to the website, only by typing the username (a proper authenticated login is a requirement if group is made of 5 people).

In the navigation panel, the user can see links to:

Motorcycles/doctors/classes/items that you selected as a theme.
"Reserve" form.
"My reservations".
"Add motorcycle/doctor/class/item that you selected as a theme" (the link is visible to everybody).
"Delete motorcycle/doctor/class/item that you selected as a theme" (the link is visible to everybody).

On the main page, the user can see a Vehicles.

When the user selects a specific item, they can see the details page with its full description (skip the "Rotate image" button).

In the details page, the user can click the "Reserve" button .

When the user clicks the "Add item" link in the navigation panel they can see a form for adding a new item.

Make the app responsive, creating both mobile and desktop versions.

When the user clicks the "Delete item" link in the navigation panel they can see a list of all items with title and "Delete" button.

When the user clicks the "Delete" button, the selected item is marked as removed and does not show on the main list anymore.

To reserve an appointment, the user has to select a date and city (username and selected item are autofilled).

When the user clicks the "My reservations" link in the navigation panel they can see a list of their reservations (with information about item name, date and city).
Add full documentation for your API.

Thank you ,
Bhushan , Umair, Eugene .

Hello air ,
if you found any bugs then please give a hint about how we can solve that particular error . it will be very helpful as we have very little time for project deadline .
Thank you !
Have a good day .

Hello Sir/Mam ,
if you found any bugs then please give a hint about how we can solve that particular error . it will be very helpful as we have very little time for project deadline .
Thank you !
Have a good day .

Hello Dear reviewer,
Now if you follow the README instructions carefully you will get a running app on your localmachine and still if you get stuck anywhere you can reach out to us on zoom or slack .
Thank you ,
Bhushan , Umair , Eugine .


[BUG?] Bar graph showing one dataset's bars in wrong column

I'm totally stumped with this one. Here's the data being sent to chartjs:
{
  "labels": [
    "12\/11\/2016","12\/13\/2016","12\/15\/2016","12\/16\/2016","12\/18\/2016",
    "12\/20\/2016","12\/22\/2016", "12\/27\/2016","12\/29\/2016","12\/30\/2016"
  ],
  "datasets": [
    {
      "data": [0, 7, 0, 9, 0, 8, 0, 5, 0, 5],
      "label": "December 2016",
      "backgroundColor": "rgb(0,149,218)"
    },
    {
      "data": [11, 0, 8, 0, 8, 0, 5, 0, 4, 0],
      "label": "November 2016 Comparison",
      "backgroundColor": "rgb(0,167,124)"
    }
  ]
}

As far as I can tell this absolutely abides by the required structure. However, when the chart renders, it looks like this:

(This screenshot is with a barValueSpacing of 20, but I've tried several configurations and it never seems to help)
The first green bar has a value of 11, and it should be displayed in the 12/11/2016 column alongside the 0 value for the December 2016 dataset. What is going on here?

Are you using a time axis as the x axis? If so, this is a known issue. See #3263, #2415.

I'm not using the type: "time" setting. My x-axis label array is being fed straight into the plugin. Is the time axis something that is automatically set? I don't think that's the problem; I'm pretty sure I tried overriding the label array with random strings (not dates) and it still didn't render properly.
I should note that when the bars are hovered over, they display the correct dataset. They're just rendering too far to the right for some reason.

The time axis is not automatically set. Could you put this in a jsfiddle for debugging?

How confusing...the jsfiddle works exactly as expected: https://jsfiddle.net/4yhpfpn2/1/
Is there anything you could think of that could interfere with chartjs's ability to draw bars in the correct location?

That's interesting. I don't know what could cause that to happen. Are you able to share the original case at all?

Closing since there is no test case


Optimize the style of documents on the mobile

Feature request 🚀
Expected:

All documents adapt to mobile

Here are some screenshots of how it looks on mobile (thanks to Edge's responsive devtools)

Thanks 😃, I will refer to this design & layout.

:)


[Question] Will inventory Panels be ported in the future

So i asked a question previously and it was closed before I could get more information. I'll restate here.
Yes, i know inventory panels are not currently ported. They're not in the latest release (5.0.24) so yeah I get that. My question is, is their currently work being done on porting inventory panels, if not will there be in the future, or has the development team decided to remove Inventory Panels all together. A great many changes have been made to EnderIO so it's unsure what the development looks like going forward.

I honestly think this is a poor way of handling user questions, as it doesn't let other people see answers already given. I recommend adding a "I have questions about..." option on your issue thingy, and just have it direct to a separate issue tracker or forum or something. That way you can build up a searchable repository of answered questions.

Well that's not really what alxpettit was talking about. It is a poor way of handling user questions. Discord isn't really a repository,  it's a chat service. So you'll have repeated questions a lot. If answered questions were done as a github or something similar then users could see answered and unanswered questions. Other mods have done a similar thing. True there will still be duplicate questions, but it will be one step toward not having too many and having a place where people can easily see duplicate questions. Or you know, keep doing what you're doing eithers fine.

Discord has just as many ways of dealing with this problem as github does. We have chosen to do it this way because more people communicate on our discord so it just makes sense. I have no issue with answering questions, heck on our discord you can even see progress updates for inventory panel, so it just makes githubess practical overall for us if nothing else.

Hmm. Apparently Discord does have a searchable history. I'm impressed! I can see how it works for this use case. If it was open source, I might consider using it on a regular basis!

We also pin messages that are common and we have a bot that can be queried for answers.

I looked at your README.MD for this repository, and couldn't find anything about where to post questions to and search for answered questions. Maybe you should add a link to your Discord and make sure people know to direct them there?
I personally spent like 20 minutes wandering around random EnderIO stuff online because I didn't know Discord had search history and such -- so it might be useful to point people there and be like "no really, try it" on the README.MD.


Re-enable skipped client test

As of #503, the "doesn't return after version negotiation is established if no ConnState is defined" test is disabled.

Why's that? Can we fix that before merging?

Sorry, missed this comment. The tests basically asserts that Dial doesn't return, but I don't see a way of getting it to return during shutdown.


refactor template for performance

avoid some memory allocation
early return instead of always process all input

Codecov Report

Merging #327 (dd25964) into main (332a230) will decrease coverage by 0.16%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##             main     #327      +/-   ##
==========================================
- Coverage   80.48%   80.32%   -0.17%
==========================================
  Files          54       54
  Lines        6217     6202      -15
==========================================
- Hits         5004     4982      -22
- Misses        947      954       +7
  Partials      266      266

Impacted Files
Coverage Δ

pkg/util/texttemplate/texttemplate.go
88.83% <86.66%> (-2.91%)
:arrow_down:

pkg/cluster/syncer.go
76.28% <0.00%> (-1.29%)
:arrow_down:

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 332a230...dd25964. Read the comment docs.

I'm fine with this change, but along with the new pipeline jumping in this PR is useless, so for stability, we could suspend it.


400 error Invalid type. mail_settings.sandbox_mode

$mail_settings->setBccSettings($bcc_settings);
$sandbox_mode = new SandBoxMode();
$sandbox_mode->setEnable(false);
$mail_settings->setSandboxMode($sandbox_mode);
$bypass_list_management = new BypassListManagement();
$bypass_list_management->setEnable(true);
$mail_settings->setBypassListManagement($bypass_list_management);
$footer = new Footer();
$footer->setEnable(true);
$footer->setText("Footer Text");

this code is not working

Hello @azar1,
The following code is working for me:
<?php
namespace SendGrid;
// If you are using Composer (recommended)
require 'vendor/autoload.php';

// If you are not using Composer
// require("path/to/sendgrid-php/sendgrid-php.php");

$from = new Email(null, "dx@sendgrid.com");
$subject = "Hello World from the SendGrid PHP Library!";
$to = new Email(null, "elmer.thomas@sendgrid.com");
$content = new Content("text/plain", "Hello, Email!");
$mail = new Mail($from, $subject, $to, $content);

$apiKey = getenv('SENDGRID_API_KEY');
$sg = new \SendGrid($apiKey);

$mail_settings = new MailSettings();
$sandbox_mode = new SandBoxMode();
$sandbox_mode->setEnable(false);
$mail_settings->setSandboxMode($sandbox_mode);
$mail->setMailSettings($mail_settings);

$response = $sg->client->mail()->send()->post($mail);
echo $response->statusCode();

It looks like you are missing $mail_settings = new MailSettings();
With Best Regards,
Elmer

Thank you for your reply,
but,
showing this error when i make $sandbox_mode->setEnable(false);
400{"errors":[{"message":"Invalid type. Expected: object, given: array.","field":"mail_settings.sandbox_mode","help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.mail_settings.sandbox_mode"}]}

Can you please provide me with the output to:
echo json_encode($mail, JSON_PRETTY_PRINT), "\n";

Please place that right before:
$response = $sg->client->mail()->send()->post($mail);

Thanks!


Add button "Get it on F-Droid"

Please add a "Get it on F-Droid" button from a PNG file available at https://commons.wikimedia.org/wiki/File:Get_it_on_F-Droid.svg on your website http://connectbot.vx.sk/ and in the README.md on GitHub. Both buttons please with the appropriate link to the page of your app on F-Droid.

Is this app still maintained?


Custom HTTP Header

We should make HTTP Header fields customisable when Kitchen requests TVML on Network.
Workaround for now is to send network request by yourself, then pass the response XML string to Kitchen.

I think we need to introduce these to archive this goal.

Pass HTTP Header parameter via Cookbook object.
Pass Response object handler (type should be NSHTTPURLResponse -> Bool) via Cookbook object. Devs can return false if response is invalid, and don't want to proceed to xml parsing.

IMO, we should not let TVJS to send network requests (by TVJS's evaluateScripts) anymore. So the custom configuration above would affect every network requests in Kitchen.
Therefore, template URL should not be path for js file anymore, but for xml file.

Done in #44


Adding variable for customizing ansible inventory group name

My organization has a substantial ansible inventory and the existing group name in this role (monitoring-servers) is already in use elsewhere and can not be changed.
I needed to be able to customize this, and I am sure that others would like to customize it as well.
I've added in the variable to defaults/main.yml and updated the README to reflect the change as well!

Hi Zachary,
Those look like good features.
Some feedback:

In order to support both Redhat and Ubuntu, the nagios.conf template file destination should be variabilized, rather than hard-coded,  Destination "{{ nagios_with_httpd_conf }}/nagios.conf" .
nagios.conf is a template, why not templatize it? That is to say, the web auth logic is choosing between "AuthType basic" and "AuthType none".  That could be an "if" statement inside the template. Then, install the file every time, not conditionally.
Add documentation with the new variable in defaults/main.yml :

#This should match your top-level ansible playbook, such as "- hosts: monitoring-servers"
nagios_monitoring_servers_group_name: "monitoring-servers"

Hey there! Thank you for reviewing my pull requests! :D
I really appreciate the feedback and fully agree. This was a simple change I put in place for my specific use case and as I iterate over my changes, I will incorporate your recommendations to make this usable in different circumstances.
I'll submit another pull request once I have made the changes you suggested.
Thanks again!
P.S. This was my very first pull request ever. Thanks for being so quick to respond!! :D :D

Probably what happened was you submitted the pull request with one feature, and then github automatically included every commit afterwards.   The general solution is to use a feature branch instead: http://blog.jasonmeridth.com/posts/do-not-issue-pull-requests-from-your-master-branch/

Ahh, ok. I will re-submit the pull request from a feature branch so that my work isn't polluting our work. :D


Proposal: Handle multiple versioned WinRT packages loaded side-by-side in a process.

Versioned WinRT components side-by-side
This feature provides conventions for framework package authors to enabled loading multiple versions of a WinRT component side-by-side within a single process.
Background
When WinRT types were shipped as part of the OS, the versioning largely consisted of putting new functionality into a new interface, and not changing the previously shipped interfaces. When it came time to activate a runtimeclass, there was only one choice: the version of the class supplied by the OS.
As Project Reunion grows and evolves, more WinRT-based functionality will become available and consumed from framework packages shipped separately from the OS. In some ways, this can make versioning simpler. Because framework packages use a scheme whereby a different major version of a package is an entirely different package, I don't need to ensure that Widgets3 is ABI-compatible with Widgets2. (Gratuitous breaking changes are still hostile to developers, but updating your app to consume a newer version involves a recompile).
In other ways, however, this complicates the versioning story. In particular, MyApp might be consuming multiple components, each of which depend on a different version of a framework package. In short, something that looks like this:
MyApp.exe
|
+-SomeComponent.dll
| |
| +-Widgets2.dll (version 2 of Widgets)
|
+-OtherComponent.dll
  |
  +-Widgets3.dll (version 3 of Widgets)

Axiom 1: Framework packages will ship, make breaking changes, and ship again with a newer major version.
Axiom 2: It will sometimes be infeasible, if not impossible, for an app to update its dependencies so that all components can agree upon a single major version of a package.
If the types in different versions of a WinRT component have the same fully qualified names (i.e. namespace + type name), this will lead to ambiguities in various parts of the runtime.
All WinRT type activation goes through RoGetActivationFactory, and that API accepts a string holding the name of the activatable class - there is no way to supply the version or filename of an assembly or dll. This will introduce ambiguitiy to activation.
If C#/.NET attempts to load multiple versions of identically-named types from multiple assemblies, I've been told the developer is going to Have A Bad Time.
If a package author wanted to perform a hard ABI break between versions by changing the interface UUIDs (ensuring that a incompatible versions of a type can't be inadvertently converted to each other), parameterized interfaces (pinterfaces) will still generate the same UUIDs, because the UUID generation algorithm uses the type name. For example, even if a version 2 Widgets.Doodad and version 3 Widgets.Doodad use different UUIDs, versions 2 and 3 of Windows.Foundation.Collections.IVector<Widgets.Doodad> will have the exact same UUID, undermining the package author's ability to prevent interoperability.
Description
A package author can resolve these ambiguities and issues by adopting a versioning convention for their type names. This can either be done manually, or simplified with enlightened tooling.
The crux of the approach is to suffix a type's namespace with a string containing the major version number.
This approach resolves ambiguities with activation and pinterface identity, because the type names involved are now unique. A big advantage is that this can work with existing tooling, today. But we can enlighten our tools to improve the developer experience.
We can enlighten the MIDL compiler to use this versioning scheme via  a new command line option, so that it appends the namespace automatically using the value supplied to the ContractVersionAttribute or VersionAttribute.
Similarly, we can enlighten projection tools (cppwinrt.exe, abi.exe) to recognize this versioning scheme and reduce developer friction by eliminating the need to spell out the versioned namespaces.
Examples
Englightened toolchain
With an enlightened toolchain, a package author can use the Version (or ContractVersion) attribute to specify the package version.
namespace Widgets
{
    [version(3.0)]
    runtimeclass Doodad // Puts Doodad into the _v3_ namespace
    {
        // Methods
    }
}

An enlightened projection tool can then use its knowledge of this versioning scheme to improve the developer experience. For example, a C++ projection could use inline namespaces to "hoist" the latest version into the top-level namespace.
// C++/WinRT projection
namespace winrt::Widgets
{
    inline namespace _v3_
    {
        struct Doodad;
    }

    namespace _v2_
    {
        struct Doodad;
    }
}

winrt::Widgets::Doodad b; // Uses _v3_::Doodad
winrt::Widgets::_v2_::Doodad b2; // _v2_::Doodad is still reachable
winrt::Widgets::_v3_::Doodad b3; // _v3_::Doodad is also reachable

Unenlightened toolchain
Even with an unenlightened MIDL compiler, an author can manually add the namespace versioners.
namespace Widgets._v3_ // Version 3.x of Widgets
{
    runtimeclass Doodad
    {
        // Methods
    }
}

An unenlightened projection tool wouldn't be able to perform any namespace hoisting, but types would still be visible, and most languages of interest have mechanisms to remove some of the friction manually.
// C++/WinRT projection
namespace winrt::Widgets
{
    namespace _v3_
    {
        struct Doodad;
    }

    namespace _v2_
    {
        struct Doodad;
    }
}

// No projection magic, so add a "using namespace"
using namespace winrt::Widgets::_v3_;

winrt::Widgets::Doodad b; // Uses _v3_::Doodad
winrt::Widgets::_v2_::Doodad b2; // _v2_::Doodad is still reachable
winrt::Widgets::_v3_::Doodad b3; // _v3_::Doodad is also reachable

Other benefits
A feature worth noting is that if MIDL3 syntax is used so that the MIDL compiler automatically generates the interface UUIDs, the different namespace will force different UUIDs to be generated, preventing consumers from accidentally performing invalid conversions between the two versions.
winrt::Widgets::_v2_::Doodad f();
winrt::Widgets::_v3_::Doodad obj = f(); // Error

None of the above, however, precludes a package author from opting in and providing consumers the ability to convert between versioned types. This could take different forms, depending on the degree of interoperability desired by the author.
One approach would be for a newer version of a runtimeclass to implement the older versions of its interfaces, so that it responds to QueryInterface requests.
Another approach would be to provide an overloaded constructor or static method that could convert a newer versioned object (or wrapper) around an older object.
Remarks
Alternative approaches
Explicitly supply the desired DLL to activation
One considered approach would be for versioned WinRT types to use the same namespace between versions, and detour/augment RoGetActivationFactory so that callers would supply the desired version of the DLL. Something like:
HRESULT hr = RoGetActivationFactory(L"Widgets3.dll!Widgets.Doodad", iid, ppResult);

An appealing aspect of this approach is the apparent simplicity.However, this approach was rejected, because putting all the versioned WinRT types into the same namespace created many ambiguities:

C#/.NET present serious hurdles to get this to work. Even if it got "working", it lays plenty of traps and pitfalls to catch non-expert developers, who will doubtless wonder why their compiler says they can't convert from Widget.Doodad to Widget.Doodad.
Even if the package author changed the types' UUIDs to prevent accidental conversion between incompatible versioned types, paramterized interfaces generate the UUIDs based on the type names. Having two different versions of Widget.Doodad that are incompatible, but two different versions of IVector<Widget.Doodad> that are compatible, is bound to turn into a bug farm.
If versioned types have the same name and namespace, things get very ugly whenever both types need to coexist in the source code for the same module. This is a situation that's easy to create if an app's components expose any APIs that use the versioned type:

// Component1.h
Widgets::Doodad foo(); // Uses Widgets 2.0

// Component2.h
Widgets::Doodad bar(); // Uses Widgets 3.0

// I've got a bad feeling about this...

What type is the object under the hood of the Doodad object? Is it v2 or v3? How would we even get this to compile without encountering "type redefinition" errors. Even if we did compile successfully, we'd be in a fragile state of affairs, flirting with runtime Undefined Behavior caused by violations of the "One Definition Rule".

Let's discuss concerns about namespace changes driving code changes. There is going to be tension between keeping the names the same, and having type collisions.

Forcing consumers to rename types may be a bridge too far, and hamper adoption to an unacceptable degree.

Here's our highest priorities for Xaml and IXP:

It must work with C#, especially with .NET Native for UWP apps until either Cs/WinRT can be supported for .NET Native, or UWP can support .NET 5.
It must not require any C# code changes to use, but it can involve updating my tool chain to refer to different metadata references. C# doesn't have the "using namespace" inlining support or other language features that's being proposed for C++.
It doesn't need to support a single DLL that refers to both Muffin4 and Muffin5. It's actually good if we don't allow this, as it prevents completely unsupported interop between different versions.

@jeffstall Agreed on 1+2. 3 is unclear

It doesn't need to support a single DLL that refers to both Muffin4 and Muffin5

I'm not following
As in, I the component author don't need to make 1 dll providing both Muffin4 and Muffin5 objects?
Or, I the component consumer don't need to make 1 dll consuming both Muffin4 and Muffin5 objects?
If the latter, is it I don't need to write a dll that directly consumes both Muffin4 and Muffin5 objects? e.g. I don't need to write
var m4 = new Foo._v4_.Muffin();
var m5 = new Foo._v5_.Muffin();

Or is it I don't need to write a dll that directly or indirectly consumes both Muffin4 and Muffin5 objects? e.g. I don't need to write
fee.DoThis(); //calls code that calls code that eventually does stuff with Muffin4
fie.DoThat(); //calls code that calls code that eventually does stuff with Muffin5

Please clarify

First, I'm not convinced this is a problem that needs to be solved. In particular in the recommended developer scenario where packages are consumed through nuget and version dependencies are expressed through nuget then the scenario outlined occurs when the developer of "MyApp" updates the nuget version of "OtherComponent" to the version where it now depends on "Widgets.3.0.0" but it hasn't updated "SomeComponent" and "SomeComponent" still depends on "Widgets.2.0.0". If SomeComponent requires exactly Widgets.2.0.0 then "MyApp" will fail to compile. If SomeComponent says it requires [2.0, *) then MyApp compiles and all nuget dependencies resolve to Widgets.3.0.0. (and SomeComponent should only do that if it's able to be recompiled from source ... which maybe we can do for .NET things that are less ABI-dependent).
Ignoring that, there's still more things I worry about. For example, I believe that the activatable class entries list simply the dll name and not the full path. So if both Widgets framework packages say their implementation dll is "Widgets.dll" then LoadLibrary will just pick the first one. We would need to change the dll names too, in addition to the namespace.
And then in practice, how many of our libraries would reasonably work side-by-side like this? Interop is going to come up where I want to pass a "Muffin" output from SomeComponent into OtherComponent and I'll get weird errors like "Muffin is not a Muffin".
Is there a concrete scenario from Reunion that's driving this requirement?

@jeffstall Agreed on 1+2. 3 is unclear

It doesn't need to support a single DLL that refers to both Muffin4 and Muffin5

I'm not following
As in, I the component author don't need to make 1 dll providing both Muffin4 and Muffin5 objects?
Or, I the component consumer don't need to make 1 dll consuming both Muffin4 and Muffin5 objects?
If the latter, is it I don't need to write a dll that directly consumes both Muffin4 and Muffin5 objects? e.g. I don't need to write
var m4 = new Foo._v4_.Muffin();
var m5 = new Foo._v5_.Muffin();

Or is it I don't need to write a dll that directly or indirectly consumes both Muffin4 and Muffin5 objects? e.g. I don't need to write
fee.DoThis(); //calls code that calls code that eventually does stuff with Muffin4
fie.DoThat(); //calls code that calls code that eventually does stuff with Muffin5

Please clarify

@DrusTheAxe -- It applies to authoring a single dll (or exe) that produces or consumes both Muffin4 and Muffin5.

@jevansaks I'll leave it to @jeffstall to chime in and clarify the need and driving scenarios, as he's my primary (sole?) customer of this proposal.
Regarding your versioning scenario, I've been informed that the convention for framework packages making a breaking major version change is to incorporate the major version number into the package name. So, in you scenario, Widgets.2.0.0 and Widgets.3.0.0 are entirely different packages. In this case, I'm not aware of anything blocking compilation currently, but I wouldn't expect any activation to work.
For requirement 2 stated by @jeffstall , I was trying to figure out what happens if we get a situation where two different assemblies name the same fully-qualified type, and I learned about the extern alias C# feature. So even if the types were to collide, there are ways to mitigate it.

So if both Widgets framework packages say their implementation dll is "Widgets.dll"
Correct. For multi-version access to work you need to rename ALL identifiers. What that means varies depending on tech:

Flat-C DLL exports -- unique DLL filenames e.g. Muffins4.dll vs Muffings5.dll (1)
InProc COM -- unique DLL filenames and unique coclass and (esp) interface symbol names in IDL (2)
InProc WinRT -- unique DLL filenames and unique ACIDs
OOP COM -- unique coclass and (esp) interface symbol names in IDL (2)
OOP WinRT -- unique ACIDs

Visual C++'s solved this for decades by including a version identifier in the CRT's filenames e.g. MSVCRT42.dll (yeah, I'm old :P)
(1) You can get around the same-dll-filename-doesn't-load-twice issue using SxS Fusion manifests, in some cases. That doesn't work for UWP apps as SxS's DLL redirector isn't part of the DLL Search Order for Universal packaged processes. [It is for PackagedClassicApp aka DesktopBridge processes, and of course non-packaged processes]. But this is a weird game to begin with. SxS is good for RegFreeCOM, RegFreeWinRT and some oddballs settings (elevation and HighDPI support come to mind) but the DLL Redirector is generally unpopular. Comctrl32 is the primary case I know of its use. VC2005+2008 CRTs relied on it too (and VS found the net experience sufficiently unrewarding they backed away from it in later releases)
(2) Technically interfaces are uniquely identified by IID, but it's hard to write source code with identical symbols for different things, e.g. when IMuffin v4 and v5 both say "interface IMuffin" in Muffin.idl...

convention for framework packages making a breaking major version change is to incorporate the major version number into the package name

Yup. Common technique since waaay back in Win8 when MSIX (aka APPX) was invented. WinJS used to consider every release (include previews) a breaking change so they even had package names like microsoft.winjs.1.0.rc1. (One concern they had was monkey patching so implementation changes were effectively breaking changes)
Unique source names are necessary-but-insufficient to concurrently reference multiple versions

I've started a pull request in the xlang repo with a more detailed specification and specific design recommendations for the various tools & projections that contribute to the experience.
Let's continue the discussion here: https://github.com/microsoft/xlang/pull/697

I would like to be able to run the Minecraft Windows 10 app alongside the Beta version - at the moment this is not possible.

@mdtauk, that's feedback best delivered through feedback hub. This issue & proposal here is specific to components within an application, and won't have any meaningful impact on that scenario.

@BenJKuhn  ah I misunderstood the request then. 🙂