Trigger word issues: Microphone sensitivity / Word recognition

Hi,
I've finally got AlexaPi working after a few separate attempts due to various reasons.
It all works but I literally have to shout at my microphone to get the keyphrase to be detected. How exactly do I change the sensitivity of my microphone? It's a decent microphone and I don't normally have any issues like this.
I realise this isn't directly related to AlexaPi but I have no idea what AlexaPi uses and how I'd change the settings for it...
Interestingly it seems much more responsive when I run it directly and not the always on service, but maybe thats just coincidence.

EDIT *

Just to add to this... It actually appears to be only having a problem with the keyword. When I'm giving the actual Alexa commands it all appears to work fine. Does anyone else find that the keyword detection is a little dodgy? Or could it just be my northern English accent combined with a cold? haha.

Interestingly it seems much more responsive when I run it directly and not the always on service, but maybe thats just coincidence.

I don't see a reason for this to happen.
You can adjust the microphone sensitivity with the alsamixer program. If you're experiencing the issue only with the wake word, it's something we have to solve. We'll be adding some more configuration options regarding audio and support for snowboy, which should work better than pocketsphinx. We'll see how it goes.

Thanks for all the work on this... installed and still tweaking it myself.
On a side I'm working with led strips to simulate the Echo activation light at the moment.
But in regards to microphone settings, I am using the PS3 Eye and trying to get it working with AlexaPi.
I seen it in Mason Stone's build... so I bought one on eBay for £5... works ok but am struggling to get it working with the array in .asoundrc adding up the 4 mics. Am sure that this will be something it will need to get working so it'll be better with far field voice recognition.

@willsmithdev Try changing the hotword in /etc/opt/AlexaPi/config.yaml. I had temporarily changed it from "Alexa" to "Max" and it had stopped dropping the hotword. Interesting to know that Alexa has 3 syllables (https://www.howmanysyllables.com/words/alexa) while Max has only 1 (https://www.howmanysyllables.com/words/max). Hence 3 times more error prone? ;)

Keep in mind that changing the trigger word might violate Amazon's ToS (#14).

The most recent changes to AVS terms are as follows:
Changes posted August 23, 2016.
"We’ve updated the Alexa Agreement to remove the requirement that you obtain Amazon’s written approval prior to implementing far-field voice recognition or use of a spoken word to trigger the activation of the Alexa Service in Your Products, and to make other updates. Please review the full text of the updated Alexa Agreement carefully."
from https://developer.amazon.com/public/solutions/alexa/alexa-voice-service/support/terms-and-agreements#changes

@illperipherals That's voice activation. This is the wake word used for it.

(p) you will not use or allow the use of any wake word or other trigger word as part of accessing the Alexa Service in Your Products other than the wake or trigger words authorized by Amazon (such as “Alexa”) without Amazon’s prior written approval;

Read the thing.

No need to be rude. I was just outlining the most recent changes. The guys over at Kitt were very careful with their release as well. Some of that conversation was on flooie's branch, I believe.

Sorry if that came out too strong. I merely wanted to suggest reading the whole document.

I think the interesting word here is "Your Product". It's not really a Product, is it (esp when it's unfinished)?

De nada, man.

I'm actually not sure at all as I have suggested in #14. We left it at "we're developers, tinkers and we're just playing and if Amazon didn't like it, they would probably tell us".

Also, Amazon helped fund Kitt, so those guys probably have some insight here.

I am actually having the same issue as the original poster.
The wake word hardly ever works, however in the very odd occasion that it does, my speech is recognised perfectly.
I think it may be too do with accents. I am also from the UK. I was watching a video of someone  with an American accent demonstrate alexa and every time they said alexa on the video it triggered.

Same issue here, wake word "Alexa" or "Computer" rarely works. I changed the keyword to "Bob" and it seems to work much better.

I'm having trigger word issues running this on a CHIP using a mic in the 3.5mm jack.  If I start talking and speak a random sentence or two and then say "Alexa", the trigger word registers.  However, if I start with silence and then say "Alexa" or "Hey Alexa", it doesn't register.  It's like there has to be some amount of speech before the trigger word in order for it to trigger.  Has anyone else experienced this?  Any ideas how I can debug this further?

This issue should be addressed soon (tweaking pocketsphinx's threshold & adding snowboy support). Stay tuned.

hi!
this worked for me - voice recognition is now better, also with the Playstation Eye: At the website from kitt.ai - the makers of a wakeword-detector for alexa (also for ok google) I found an tutorial for the microphone-issue. Gave that a try - and: Now its really better.
See information on that page: http://docs.kitt.ai/snowboy/#set-up-audio
I changed the ~/.asoundrc file as they described and then the rec-command worked out fine.

Version 1.4 has been released today, where PocketSphinx's threshold is configurable.

How can we set the pocketspinx threshold? Is there a config file?

There is.  Look in /etc/opt/AlexaPi/config.yaml

Like now threshold is configurable, I think I can close this issue.
Emerick


Capturing wifi using hcxdumptools says invalid option help

Writing hcxdumptools -i wlan0 -o test1.pcapng -- enable_status=1 says invalid option --'o' can anyone help on how to solve this problem

Please use the latest version of the hcxdumptool
https://github.com/ZerBea/hcxdumptool/discussions/330

Sorry but I am a real beginner at this stuff so what should I use instead of -o

hcxdumptool has built-in help.
Just type "hcxdumptool -h" and press Enter
Also read here, please
https://github.com/ZerBea/hcxdumptool/issues/342
https://github.com/ZerBea/hcxdumptool/issues/347
https://github.com/ZerBea/hcxdumptool/issues/355
https://github.com/ZerBea/hcxdumptool/issues/356
hcxdumptool is not for beginners. You have to know Linux.
If it is too complicated for you, start with wifite
https://null-byte.wonderhowto.com/how-to/automate-wi-fi-hacking-with-wifite2-0191739/

As mentioned by @v74863 it is always a good idea to read --help, README.md and the changelog to get some information.
In your case, the simplest command line is:
$ hcxdumptool -i INTERFACE_NAME -w dump.pcapng -F --rds=1

By this options hcxdumptool use the interface named by "INTERFACE_NAME", store all information to a dump file named dump.pcapng, scan all available frequencies (frequencies supported by the driver and allowed by wireless regulatory domain) and sort the status display by successful attacks.
Please notice:
It is mandatory that all services that take access to the device are stopped before you run hcxdumptool.
I close this report, because it is more a discussion and not a bug.


@preact/signals-core v1.3.x fails on Fresh

I write my website in Fresh, recently I upgraded Fresh to v1.3, along with all the Preact dependencies, including @preact/signals to v1.1.5 and @preact/signals-core to v1.3.1.
Then I noticed the signals in my website is not working anymore. After trying downgrade @preact/signals and @preact/signals-core, I found out that @preact/signals-core version upto v1.2.3 would work.
I also noticed the data for hydrations changed too:
v1.2.3
<script id="__FRSH_STATE" type="application/json">
{"v":[[{"requestURL":{"_f":"s","v":""}},{"requestURL":0},{}],[["responsive_container","old_logo","go-to-top","mainsearch","selector_english","searchfield","searchfield_input","oup_icons","responsive_hide_on_smartphone","responsive_hide_on_tablet","inputSuggestions","suggestionRow","suggestionCategory","suggestionDic","suggestionList"]]],"r":[[["0","0","requestURL"],["0","1","requestURL"]]]}
</script>

v1.3.1
<script id="__FRSH_STATE" type="application/json">
{"v":[[{"requestURL":{"_f":"s","v":""}},{"requestURL":{"_f":"s","v":""}},{}],[["responsive_container","old_logo","go-to-top","mainsearch","selector_english","searchfield","searchfield_input","oup_icons","responsive_hide_on_smartphone","responsive_hide_on_tablet","inputSuggestions","suggestionRow","suggestionCategory","suggestionDic","suggestionList"]]]}
</script>

As I compare the two JSON outputs, I think v1.3.x makes requestURL signal two different objects, while v1.2.3 make it one.

Hmm, this might be related to adding Signal.prototype.toJSON, mind trying something like the following in the server-entrypoint of your application:
import { Signal } from '@preact/signals-core'

Signal.prototype.toJSON = undefined

@JoviDeCroock
I added the code you said, and it worked!
But for your information, I'm using Fresh v1.3.0 which is just released yesterday, the PR was merged a month ago.

@osddeitf I know that that PR got merged a month ago, I was mainly hinting at that maybe the detection there is running into an issue. The issue might be more appropriate on their repo 😅

If you think so, I'll ask there

Closing in favour of #1499 because it's an issue in Fresh and not with Preact Signals.


Feature/test json

support for test json/yaml files

[x] Check that you pass the basic compilation and unit tests by running grunt

Coverage decreased (-0.05%) to 8.257% when pulling 4e4f803d23ea5146633736cbcf00cc2f76ac94f1 on feature/test_json into cb30b7fabb481c0ec8e9d71573bff321eebca956 on develop.

That's a lot of fail

Coverage increased (+0.05%) to 8.352% when pulling af0fcfeae666e539ebe63623940ecf0d551c3e5f on feature/test_json into cb30b7fabb481c0ec8e9d71573bff321eebca956 on develop.

Coverage increased (+0.05%) to 8.352% when pulling fec3b100fa239dc71dd48d6a9952b4f8d0d80b64 on feature/test_json into cb30b7fabb481c0ec8e9d71573bff321eebca956 on develop.


Add NusaX Bitext Mining (MINERS)

NusaX is a parallel dataset for machine translation and sentiment analysis on 11 Indonesian languages
Checklist

[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

Adding datasets checklist

Reason for dataset addition: ...

[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] If the dataset is too big (e.g. >2048 examples), considering using self.stratified_subsampling() under dataset_transform()
[x] I have filled out the metadata object in the dataset file (find documentation on it here).
[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.

Thank you for the review. I have addressed your suggestion. @KennethEnevoldsen
I found two issues:

when running make test

===================================================== short test summary info =====================================================
FAILED tests/test_RerankingEvaluator.py::TestRerankingEvaluator::test_nAUC - assert 0.9406528189910982 == 0.86943 ± 8.7e-05

It seemed unrelated to my change. I also got the error when running the command from the main branch.

And, I could not run intfloat/multilingual-e5-small model.

ValueError: Model None not found for model intfloat/multilingual-e5-small

I have completed the checklist.
I have addressed your comments @KennethEnevoldsen. I could not run intfloat/multilingual-e5-base since I got this error ValueError: Model None not found for model intfloat/multilingual-e5-small so as a replacement I evaluated the dataset on sentence-transformers/LaBSE.

I could not run intfloat/multilingual-e5-base since I got this error ValueError: Model None not found for model intfloat/multilingual-e5-small so as a replacement I evaluated the dataset on sentence-transformers/LaBSE.

@gentaiscool will you add the results to the PR as well.

ValueError: Model None not found for model intfloat/multilingual-e5-small'

Addressed in #888 so merging from main should fix this
Will you add the points as well?

thank you @KennethEnevoldsen for the review and now the evaluation on e5 model works :). I have updated the metadata (avg num of characters -- previously I put the avg of char per word, now should be correct) and add the model results.

Points sounds reasonable. set tests to run and enable auto-merge if they pass


Invalid container name when using non-privileged

When the enforcer is set to use non-privileged mode by uncommenting the capabilities in values.yaml, line 18 becomes true, and the AppArmor annotation is added.  However the annotation was referring to "aqua-agent" instead of "enforcer", causing the deployment to fail.  (Invalid container name)

Verified and Approved by @xB-2048


Explore creating visualisation with CytoscapeJS

Currently we are using jsPlumb Community Edition to render nodes and edges for the visualisation. We want to experiment with other libraries and compare capabilities and suitability long term. CytoscapeJS is a good graph theory library for visualisation.

Totally agree on the pros/cons breakdown. It's actually the layouting ability we want to investigate. Originally it wasnt clear how to achieve automatic layouting (making sure everything is spaced out) with jsPlumb without having to manually manipulate physics. We have discovered some docs that we will explore to see if its possible with jsPlumb so this exploration should be a useful fallback in case


[ERROR] could not determine kind of name for C.XXX while Docker build

I was facing the following issue while docker build. Please, can anyone give me any solution?
# github.com/ceph/go-ceph/rbd
/go/pkg/mod/github.com/ceph/go-ceph@v0.2.0/rbd/rbd_nautilus.go:38:8: could not determine kind of name for C.rbd_image_spec_list_cleanup
/go/pkg/mod/github.com/ceph/go-ceph@v0.2.0/rbd/rbd_nautilus.go:33:19: could not determine kind of name for C.rbd_image_spec_t
/go/pkg/mod/github.com/ceph/go-ceph@v0.2.0/rbd/rbd_nautilus.go:23:9: could not determine kind of name for C.rbd_list2

This is my Dockerfile
FROM golang:latest as builder
RUN apt-get update && \
  apt-get install -y ceph libcephfs-dev librados-dev librbd-dev && \
  apt-get install librados2 && \
  apt-get install curl && \
  apt-get install gcc g++

WORKDIR /app
COPY go.mod go.sum ./

RUN go mod download
COPY . .
RUN go build -o /app/bin/go-ceph .

FROM golang:latest
RUN apt-get update && \
  apt-get install -y ceph libcephfs-dev librados-dev librbd-dev && \
  apt-get install librados2 && \
  apt-get install curl && \
  apt-get install gcc g++

WORKDIR /app
COPY --from=builder /app/bin /app
COPY --from=builder /app/ceph.conf /app/ceph.conf

# Run the executable
CMD ["./go-ceph"]

Without digging into your base container I'm going to guess that whatever debian or ubuntu version that golang:latest is based on ships an onlder version of ceph than nautilus.
If that's the case you have a few choices I can think of off the top of my head:

Use build tags (example here) to choose either luminous or mimic
Install ceph packages from one of the ceph repos rather than debian/ubuntu
Use a different base container image (you don't have to use the "golang" image just because you are building go code)

Without digging into your base container I'm going to guess that whatever debian or ubuntu version that golang:latest is based on ships an older version of ceph than nautilus.
If that's the case you have a few choices I can think of off the top of my head:

Use build tags (example here) to choose either luminous or mimic
Install ceph packages from one of the ceph repos rather than debian/ubuntu
Use a different base container image (you don't have to use the "golang" image just because you are building go code)

Thank you so much @phlogistonjohn  for your suggestion. Yes, it worked after changing the base container from golang to ceph/daemon-base.

Good to hear. Sounds like we can close this issue.

can i ask which image tag of ceph/daemon-base you use? when i use the latest tag, i receive the error 'rados/librados.h no such file or directory'. Also i can't yun install librados-dev package.

We no longer use ceph/daemon-base directly. The images we use are either quay.io/ceph/ceph or quay.ceph.io/ceph-ci/ceph depending if we're testing against a released or unreleased version of ceph (respectively).
You're replying to an issue that was closed three years ago. I request that if you want to continue this conversation and/or need help with building with go-ceph, please start a new issue or discussion. I will not reply further in this thread.


Module build failed: Error: write EOFat exports._errnoException at WriteWrap.afterWrite

"webpack": "^4.4.1",   "extract-text-webpack-plugin": "2.1.0",
// index.js
import './index.less';
.app-wrapper{
position: absolute;
top:0px;
left: 0px;
width:100% ;
height:100%;
z-index:10;
background-image: url(./assets/images/bg.jpg);
background-size: cover;
}
webpack.config.js  less config
{test: /.less/,
exclude:  /^node_modules$/,
use: extractLESS.extract({
fallback: "style-loader",
use: [
{ loader: 'css-loader', options: { importLoaders: 1 }},
{
loader: 'postcss-loader',
options: {
plugins: function () {
return [
require('autoprefixer')
]
}
}
},
{loader: 'less-loader'}
]
}),
},

I believe you need to use extract-text-webpack-plugin v4.0.0-beta.0 if you want to use Webpack 4

I use is extract-text-webpack-plugin v4.0.0-beta.0， That's the mistake.
------------------ 原始邮件 ------------------
发件人: "Bastien<EMAIL_ADDRESS>发送时间: 2018年4月20日(星期五) 下午4:39
收件人<EMAIL_ADDRESS>抄送: "Traveling<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [webpack-contrib/extract-text-webpack-plugin] Module buildfailed: Error: write EOFat exports._errnoException at WriteWrap.afterWrite(#779)
I believe you need to use extract-text-webpack-plugin v4.0.0-beta.0 if you want to use Webpack 4
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

DEPRECATED
Please use: https://github.com/webpack-contrib/mini-css-extract-plugin


JSON error in Integrator RNN Tutorial

Hello,
Thank you all for making this, I am very excited about applying these methods.
I just wanted to report a small error formatting error in the Integrator RNN Tutorial.ipynb file. This file is missing a single comma between lines 55 and 56 that threw a JSON error for me when I first downloaded it. I underline this missing comma below:
"import sys\n",     "import time\n" _,_     "from importlib import reload"    ]
Best wishes and thanks again,
Josh

Fixed as suggested. Thanks!


Change landing URI for pull secret

Till now we are using the https://cloud.redhat.com/openshift/install/crc/installer-provisioned for downloading the release crc bits and also pull secret, which is now changed to https://cloud.redhat.com/openshift/create/local one.

Fixed via https://github.com/code-ready/crc/pull/1982


Async call not await - potential cause of issue in DataGrid

Scenario:  when Settings is bound, plus Filter is bound, the filter value gets overwritten.  The async call to OnFilter at ApplyFilter(RadzenDataGridColumn<TItem> column, bool closePopup = false), in RadzenDataGrid.razor.cs is not awaited.
           OnFilter(new ChangeEventArgs() { Value = column.GetFilterValue() }, column, true);
What happens is that a filter is applied then immediately removed by a second call.  Overall I'm just trying to save and restore settings per the guidance, as well as trap what a person is filtering, so i can go to the db and filter it there first.  The combination of Filter and bound settings is how to recreate it.
When i remove the Filter event callback, there's no issue, but now I dont have my filter.  The lack of an await, while not 100%, it looking to be a potential cause.
https://forum.radzen.com/t/sort-order-not-loading/13988

I've merged your pull request: https://github.com/radzenhq/radzen-blazor/pull/959

@enchev - I tried this with the new version 4.10.4 and it's still an issue.  The crux of the issue is as follows:  when a handler has been added to catch setting changed (bind-Settings) as well as the filter, the filter is overwritten and returns to empty.
The entire reason for this process is to capture the filter so the data can be filtered in a backend api.  Second, we want to store the settings in local storage.  But there is something about the Filter handler that causes the grid to fire twice and overwrite the filter set.


[Optimization] Code editor key binding event optimization.

What is this PR for?
zeppelin custom key binding event optimization for Ace Code editor
What type of PR is it?
Improvement
Todos

[x] optimization for key binding and check logic

How should this be tested?
For many in the code editor and typing quickly.
The effect is greater when there are many Paragraph.
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Sorry, i found bug.

Bug fixes completed.
I will wait for the reviews.

Thanks for the patch.
Could you create two paragraphs and write multiple lines of text (more than 3 lines) in the code editor and try move focus by up/down key?
Cursor skips top/bottom line of text in the code editor.

@Leemoonsoo
Thank you for your opinion.
I'll check

@Leemoonsoo

This modification has been completed.
If you have any other opinion or find a bug. , please post a comment.
Thank you, have a nice day.

Tested and LGTM.
Merge to maste and branch-0.6 if there're no more discussions


Populate FunctionsToExport with explicit list of commands

Hi,
thanks for the awesome project! I've got a small feature request:
Could you - going forward - update your PSPKI.psd1 on release to no longer include FunctionsToExport = '*' and instead list each command individually?
The wildcard is convenient as you develop, but it has some problems when trying to run the module in a hardened environment and it makes discovery a pain.
For example, I can search for all modules on the gallery that contain a given command:
Find-Module -Command Revoke-Certificate

As of now, there's one module that's not going to be found ...

The module determines exported commands in runtime depending on client capabilities to avoid exporting functions that technically cannot be executed in a particular session. As the result, the list of exported functions is dynamic and cannot be statically populated in .psd1 file.

Would it not be more useful then to publish all commands and fail the ones whose requirements are not met?
As of now, running a command on a incompatible client would result in a "Command not found" error, rather than a "Bad Client, do XYZ to fix" error.
I can't count the number of times I've had to help an admin with Exchange Tooling where they were looking for the correct version when it was just a matter of insufficient permissions (EX/EXO only give you the commands you have permissions to use).

Exporting functions with an '*' in the manifest file will cause PowerShell not recognize the function if PowerShell is running in constrained language mode. Each function must be explicitly listed as is currently being done.

Would it not be more useful then to publish all commands and fail the ones whose requirements are not met?

That's what I wanted to avoid. Otherwise, I will have to write platform/dependency support check in every function and this will add confusion: the command exist, but cannot run.

I'd argue on the confusion part - not whether it will happen, but which of the two possible points of confusion are worse (since you don't get to pick an option that is 100% confusion free for everybody).

Command Exists but cannot run: The problem is in the environment, something an admin is likely to understand (can't manage AD-based CA without AD is understandable)
Command exists not: PowerShell specific issue, nothing about CA

Given that the target audience is likely to be CA admins rather than PowerShell experts, I believe that the "Command cannot be used" problem is a lot easier to explain or understand.
As for the implementation headache - I strongly recommend implementing assertions for that kind of situation:

One internal function per environment condition:

function Assert-Something {
	<#
        .SYNOPSIS
                Assert that something is true.

        .DESCRIPTION
                Assert that something is true.

        .PARAMETER Cmdlet
                The $PSCmdlet variable of the calling command.

        .EXAMPLE
                PS C:\> Assert-Something -Cmdlet $PSCmdlet

                Assert that something is true.
#>
	[CmdletBinding()]
	param (
		[Parameter(Mandatory = $true)]
		$Cmdlet
	)

	process {
		if ("Something" -is $true) {
			return
		}

		$exception = [System.InvalidOperationException]::new("Invalid environment! This command can only run if XYZ is true!")
		$record = [System.Management.Automation.ErrorRecord]::new($exception, "InvalidEnvironment", [System.Management.Automation.ErrorCategory]::InvalidOperation, $null)
		$Cmdlet.ThrowTerminatingError($record)
	}
}

First statement in the begin block of each function thus constrained:

Assert-Something -Cmdlet $PSCmdlet

With that you have one central place where you implement both code and error message, the actual impact on your individual commands' complexity is minimal. The internas are hidden from the user and you can use the error message to usefully complain what is the issue, so the confusion should be minimal.
Thank you for taking the time on this issue, whether I managed to convince you or not (it is a matter of perspectives and priorities, so I'm hardly going to judge either way).
Your work on this project is appreciated :)


Make the basic business logic

Add billing period.
Add daily billing.
Add quotums
Add crud ability for billing data
Make PoC Wpf app

Just added abstracts.


Accessory information settings are not working

Pretty minor stuff but adding itemManufacturer, itemModel, itemSerialNumber in config.json is not doing anything. I still get Default-Manufacturer, etc. in the accessory information service.

I've noticed the same thing. The only value that passes into my HomeKit apps (Eve, Home) is the value for ItemName.
Also, ContactItem isn't listed in the README as a valid value for itemType but appears in the Items .js files. I'm not sure what it's supposed to do as I don't see any difference in the HomeKit app when I set it.

I was able to get the manufacturer, model, and serial number to work by adding the some lines to items/AbstractItem.js .
In the first function which starts off with:
    var AbstractItem = function(widget,platform,homebridge) {

I added the following lines after the initial variable declarations:
    this.manufacturer = widget.manufacturer;
    this.model = widget.model;
    this.serialNumber = widget.serialNumber;

After restarting HomeBridge, I immediately saw all of my manufacturer, model, and serial number customAttrs which I had defined in my config.json .


Update sourceDesc in headers of guideline chapters

This PR adds minimal source description and resolves #877.
Another thing that could (and probably) should be updated is the license information kept in these files. It still says "Copyright (c) 2018".

concerning license information, we probably should update the copyright on build?

Merged at ODD meeting (July 2022). Thank you @rettinghaus.


Parametrize DPI setting

Hey @delfes ... this is a great addition! Would you mind adding it to the readme and also to the tests?

@luchiniatwork good call, done


[INLONG-2331] Introduce sort-connectors module

Title Name: [INLONG-XYZ][component] Title of the pull request
where XYZ should be replaced by the actual issue number.
Fixes #2331
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #2332 (3640b47) into master (256ebf9) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2332      +/-   ##
============================================
+ Coverage     12.53%   12.54%   +0.01%
- Complexity     1215     1218       +3
============================================
  Files           420      420
  Lines         36240    36240
  Branches       5670     5670
============================================
+ Hits           4541     4546       +5
+ Misses        30893    30886       -7
- Partials        806      808       +2

Impacted Files
Coverage Δ

...ong/tubemq/manager/service/ClusterServiceImpl.java
52.94% <0.00%> (+2.94%)
:arrow_up:

...inlong/tubemq/manager/service/TaskServiceImpl.java
8.53% <0.00%> (+4.87%)
:arrow_up:

Continue to review full report at Codecov.

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

@ifndef-SleePy


[Bug]: theme dev command does not run with fresh theme init

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
shopify theme dev should upload my current project (theme) and run a preview window.
Actual behavior
First using shopify theme init to install a fresh version of Dawn then running shopify theme dev throws a ton of errors about color_scheme and color_schemes and prevents theme from uploading. The preview url load with a 404 error.
Verbose output
shopify theme dev                                                                                2404ms  Wed 13:24
╭─ success ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Preview your theme                                                                                │
│    • http://<IP_ADDRESS>:9292                                                                                │
│                                                                                │
│  Next steps                                                                                │
│    • Customize your theme at the theme editor                                                                                │
│    • Share your theme preview                                                                                │
│                                                                                │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

* Syncing theme #136600781052 on akt-web-dev-playground.myshopify.com
                                                                                100%
sections/video.liquid: Invalid schema: setting color_scheme type is invalid.
sections/collage.liquid: Invalid schema: setting color_scheme type is invalid.
sections/collapsible-content.liquid: Invalid schema: setting color_scheme type is invalid.
sections/collection-list.liquid: Invalid schema: setting color_scheme type is invalid.
sections/contact-form.liquid: Invalid schema: setting color_scheme type is invalid.
sections/custom-liquid.liquid: Invalid schema: setting color_scheme type is invalid.
sections/email-signup-banner.liquid: Invalid schema: setting color_scheme type is invalid.
sections/featured-blog.liquid: Invalid schema: setting color_scheme type is invalid.
sections/featured-collection.liquid: Invalid schema: setting color_scheme type is invalid.
sections/featured-product.liquid: Invalid schema: setting color_scheme type is invalid.
sections/footer.liquid: Invalid schema: setting color_scheme type is invalid.
sections/header.liquid: Invalid schema: setting color_scheme type is invalid.
sections/image-banner.liquid: Invalid schema: setting color_scheme type is invalid.
sections/image-with-text.liquid: Invalid schema: setting color_scheme type is invalid.
sections/main-collection-banner.liquid: Invalid schema: setting color_scheme type is invalid.
sections/announcement-bar.liquid: Invalid schema: setting color_scheme type is invalid.
sections/main-password-footer.liquid: Invalid schema: setting color_scheme type is invalid.
sections/main-password-header.liquid: Invalid schema: setting color_scheme type is invalid.
sections/multicolumn.liquid: Invalid schema: setting color_scheme type is invalid.
sections/multirow.liquid: Invalid schema: setting color_scheme type is invalid.
sections/newsletter.liquid: Invalid schema: setting color_scheme type is invalid.
sections/page.liquid: Invalid schema: setting color_scheme type is invalid.
sections/related-products.liquid: Invalid schema: setting color_scheme type is invalid.
sections/rich-text.liquid: Invalid schema: setting color_scheme type is invalid.
sections/slideshow.liquid: Invalid block 'slide': setting color_scheme type is invalid.
templates/cart.json: Section type 'featured-collection' does not refer to an existing section file
templates/collection.json: Section type 'main-collection-banner' does not refer to an existing section file
templates/index.json: Section type 'image-banner' does not refer to an existing section file
templates/index.json: Section type 'rich-text' does not refer to an existing section file
templates/index.json: Section type 'featured-collection' does not refer to an existing section file
templates/index.json: Section type 'collage' does not refer to an existing section file
templates/index.json: Section type 'video' does not refer to an existing section file
templates/index.json: Section type 'multicolumn' does not refer to an existing section file
templates/page.contact.json: Section type 'contact-form' does not refer to an existing section file
templates/password.json: Section type 'email-signup-banner' does not refer to an existing section file
templates/product.json: Section type 'image-with-text' does not refer to an existing section file
templates/product.json: Section type 'multicolumn' does not refer to an existing section file
templates/product.json: Section type 'related-products' does not refer to an existing section file
config/settings_schema.json: Section 3: setting with id="color_schemes" invalid setting type

Reproduction steps

Run shopify theme init
Navigate to new theme directory.
Run shopify theme dev

Operating System
Mac OS Monterey (12.6.2)
Shopify CLI version (check your project's package.json if you're not sure)
3.45.3
Shell
iTerm 2 via FishShell
Node version (run node -v if you're not sure)
v14.21.3
What language and version are you using in your application?
No response

I was able to reproduce and the relevant team has been notified. We'll investigate and post an update. Thanks for reporting!

Hey there, @cstudioakt! Thanks a lot for bringing this to our attention. We really appreciate it!
We're experiencing a temporary issue with some of the features that were recently introduced on shopify/dawn, as they are not currently supported by our theme library.
But no worries, we're already on it! We've reached out to the Dawn folks to make sure we can get this fixed as soon as possible.
In the meantime, we do have a workaround that you can use. If you initialize your theme using the --latest tag instead of using the main branch of Dawn, it will initialize the latest release of Dawn and should help you avoid this issue:
shopify theme init --latest

Once again, thank you for reporting this to us!


Failed to import entry-server

When I try to build with<EMAIL_ADDRESS>I get the following error:

I understood that this commit had an effect, but I didn't know how to fix it, so I created an issue.

Yeah my bad this was a slip up: can u bump to 0.2.3, it should be fixed


migrate away from gulp-util

Can you please dependencies on gulp-util as it is getting deprecated? this is the article I found for migration
https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5

I have created a forked package with gulp-util removed in case this repo is no longer supported:
https://www.npmjs.com/package/@elamping/gulp-regex-rename


homework 6

https://github.com/brahm-kickdrum/kdu-coursework/assets/156001450/2f3ab882-82a6-4043-8a90-e492794079e4

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
2

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


Remove Python 3.7 support

Removes Python 3.7 support, as Prefect just did (see PrefectHQ/prefect#10156), making the template compatible with Python 3.8+.
This should fix the (nightly) tests actions, which try to run tests again Prefect's main branch.

Thanks for the contribution @giorgiobasile !

@bunchesofdonald my pleasure, FYI just noticed that automatic merge is not working as my PR removes the 3.7 run of the tests action

@bunchesofdonald my pleasure, FYI just noticed that automatic merge is not working as my PR removes the 3.7 run of the Tests action

@bunchesofdonald anything I can do on my side to get it merged?

Thanks for calling this out @giorgiobasile! I don't think there's anything you or I can do, I'll see if I can get an admin to merge this or turn off the check constraint.


Design new bye-bye page when user deletes his/her account

cc @carlostallon @saleiva @piensaenpixel

Following design for this: https://github.com/CartoDB/cartodb/issues/4428

<3

Should we place it in "website" instead of the editor?
cc @juanignaciosl

@javisantana, what do you think?

Not a priority.
On Sep 8, 2015 12:49 PM, "Javier Álvarez Medina"<EMAIL_ADDRESS>wrote:

@javisantana https://github.com/javisantana, what do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/2706#issuecomment-138630196.

if it's account management should be in central, right?

I think Central is the place, just as creation is there as well.


Bug - CSD - cannot save VerbatimTypeStatus: data attribute value taken

Steps to reproduce the bug
1. I am adding type data into a CO in a CSD.
2. TW provided the correct taxon name (see screenshot 2)
3. I get an error stating that the data attribute value has already been taken (see screenshot 1)
...

Screenshot
screenshot 1

screenshot 2

screenshot 3

Expected behavior
I would like to save the data attribute in the VerbatimTypeStatus field.
If the error is due to the attribute being taken for another paratype of the same taxon name, multiple paratypes of the same taxon should be allowed. BUT, when I filter for COs with that VerbatimTypeStatus, the result is that same CO with the incorrect VerbatimTypeStatus (see screenshot 3).
I was having saving issues yesterday so perhaps this glitch is connected.
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
v0.37.1
Browser Used
Chrome Version 120.0.6099.200

I deleted and repasted the data into the field and it saved without the error prompt.
Please let me know if I should continue to submit tickets for issues such as these or if there is another route to take.
Thanks

@AntWeb-org I'm almost positive this commit will fix this issue, you will see these changes on the next update.
If the problem persist, please reopen this issue


Bug: Multiple Tax Classes can be created with the same name

What are you trying to achieve?
Multiple Tax Classes can be created with the same name, even though Tax Classes should have unique names.
Steps to reproduce the problem

Open Saleor GraphQL playground or POSTMAN. Use TokenCreate API to create Token.
Use the token generated to call TaxClassCreate API.
Create a new Tax Class with a specific name (e.g., "New tax class") and provide other details.
Verify the tax class got created with name "New tax class".
Repeat the process and attempt to create another Tax Class with the same name ("New tax class").

What did you expect to happen?
Tax Class names should be unique, and attempting to create a duplicate should result in an error or some form of prevention to ensure data integrity.
Logs
Please find below TaxClassCreate mutation and input variables,
mutation TaxClassCreate($input: TaxClassCreateInput!) {
taxClassCreate(input: $input) {
errors {
...TaxClassCreateError
__typename
}
taxClass {
...TaxClass
__typename
}
__typename
}
}
fragment TaxClassCreateError on TaxClassCreateError {
field
code
message
__typename
}
fragment TaxClass on TaxClass {
...TaxClassBase
countries {
...TaxRate
__typename
}
...Metadata
__typename
}
fragment TaxClassBase on TaxClass {
id
name
__typename
}
fragment TaxRate on TaxClassCountryRate {
country {
...CountryWithCode
__typename
}
rate
__typename
}
fragment CountryWithCode on CountryDisplay {
country
code
__typename
}
fragment Metadata on ObjectWithMetadata {
metadata {
...MetadataItem
__typename
}
privateMetadata {
...MetadataItem
__typename
}
__typename
}
fragment MetadataItem on MetadataItem {
key
value
__typename
}
{
"input": {
"name": "New tax class",
"createCountryRates": []
}
}
Output of TaxClassesList query
{
"data": {
"taxClasses": {
"edges": [
{
"node": {
"id": "VGF4Q2xhc3M6MQ==",
"name": "Books",
"__typename": "TaxClass",
"countries": [],
"metadata": [],
"privateMetadata": []
},
"__typename": "TaxClassCountableEdge"
},
{
"node": {
"id": "VGF4Q2xhc3M6MQ==",
"name": "Groceries",
"__typename": "TaxClass",
"countries": [],
"metadata": [],
"privateMetadata": []
},
"__typename": "TaxClassCountableEdge"
},
{
"node": {
"id": "VGF4Q2xhc3M6Mg==",
"name": "New tax class",
"__typename": "TaxClass",
"countries": [],
"metadata": [],
"privateMetadata": []
},
"__typename": "TaxClassCountableEdge"
},
{
"node": {
"id": "VGF4Q2xhc3M6Mw==",
"name": "New tax class",
"__typename": "TaxClass",
"countries": [],
"metadata": [],
"privateMetadata": []
},
"__typename": "TaxClassCountableEdge"
}
],
"__typename": "TaxClassCountableConnection"
}
},
"extensions": {
"cost": {
"requestedQueryCost": 200,
"maximumAvailable": 50000
}
}
}
Environment
Saleor : 3.18.10
Operating System: Ubuntu 22.04.3 LTS
Python Version: 3.9.18

Hi Team, please let me know if any further details are required regarding this issue or to recreate the issue.

Hi Team, please let me know if any further details are required regarding this issue or to recreate the issue.


migrate pre-commit configs from deprecated stage names

hook id isort uses deprecated stage names (commit, push) which will be removed in a future version.  run: pre-commit migrate-config to automatically fix this.

Close #2094  as completed too as well?

yes, duplication, thanks!


rebase

A major confusion in the .dockerignore documentation was recently fixed by #14095.  But there is further opportunity for clarifying the semantics of this file.  This patch attempts to do that.  Some details of the semantics were determined by trial and error rather than studying the source code, so this patch could still be wrong in some edge cases.
Signed-off-by: Grant Reaber<EMAIL_ADDRESS>

Sorry, I think to rebase I need to force push to the branch the original pull request was on but instead I made a new pull request on a different branch.


test ci

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #4819 (ea3b468) into develop (15add9a) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #4819      +/-   ##
=============================================
- Coverage      49.21%   49.20%   -0.02%
+ Complexity      4091     4089       -2
=============================================
  Files            736      736
  Lines          25723    25723
  Branches        3177     3177
=============================================
- Hits           12659    12656       -3
- Misses         11715    11720       +5
+ Partials        1349     1347       -2

Impacted Files
Coverage Δ

...er/src/main/java/io/seata/server/ServerRunner.java
50.00% <0.00%> (-15.39%)
:arrow_down:

...very/registry/zk/ZookeeperRegisterServiceImpl.java
61.02% <0.00%> (-0.74%)
:arrow_down:

...erver/storage/file/session/FileSessionManager.java
47.77% <0.00%> (-0.64%)
:arrow_down:

...n/src/main/java/io/seata/common/util/IdWorker.java
83.33% <0.00%> (+6.25%)
:arrow_up:


ImuFactorExample notebook

This PR adds a new notebook for the ImuFactorExample script.
Note that I have decided to eschew the use of the PreintegrationExample class in favor of clarity and first principles.

Okay, now that this is off my plate, I can go back to focusing on more pressing matters. :slightly_smiling_face:

@dellaert I cannot merge, so please do the honors.

Thanks !!!!


Send Push to iOS, Android and Other [Multiple Platforms]

Hi,
Currently when sending Push through API we have to specify the app_id which is a platform specific but this this is not the case when you mostly sending Push because usually you'll send to all users of your app regardless of the platform.
I suggest you add an option to Send to all platforms AND another option to send to multiple platforms without having to call the API multiple times
Thanks,
Jassim

@jrahma thanks for the suggestion, yes, we have this in our plans, see my response to #605

@jrahma Thank you very much for your feedback on App Center Push. We announced yesterday in a blog post that we’re retiring the Push service later this year and recommending customers transition to Azure Notification Hubs instead. The good news is that the same team operates both App Center Push and Azure Notification Hubs, so all customer feedback and feature requests have been transferred to the Azure Notification Hubs roadmap.


Consume latest proto file

heads up: host will be updated to use latest proto file from https://github.com/Azure/azure-functions-language-worker-protobuf soon.
Please update python worker to use the latest and let us know if there are any blockers.

headers field in RpcHttp is updated to <string, object> pairs instead of <string, string>. This is going to be breaking change.

Funtions Runtime artifacts with latest protobuf changes: 2.0.11782-tkfwfyhd artifacts.
Let me know if you cannot access it.


Question about SIM114, adding comment causes issue not to be detected

This testcase does not trigger SIM114:
x = "x"
y = "y"

if x == "x":
    pass
elif x == "y":
    # Comment
    pass
elif y == "y":
    pass

However, removing the comment causes ruff to detect SIM114 as expected:
x = "x"
y = "y"

if x == "x":
    pass
elif x == "y":
    pass
elif y == "y":
    pass

test.py:4:1: SIM114 Combine `if` branches using logical `or` operator
test.py:6:1: SIM114 Combine `if` branches using logical `or` operator

May I know if this is expected?
$ ruff --version
ruff 0.0.285

This is intentional. If the branches have their own comments, it's typically seen as a sign that it's intentional and should not be flagged.

Got it, thanks!


[BUG] Starrocks can't synchronize iceberg schema changes

Steps to reproduce the behavior (Required)

create iceberg table in starrocks

    CREATE TABLE iceberg_db.ice_table01 (
  `id` bigint(20) DEFAULT NULL COMMENT "unique id",
  `data` varchar(1048576) DEFAULT NULL
)
PROPERTIES (
"file_format"="parquet"
)

alter table in spark
    alter table ice_table01 add column col2 bigint;

Expected behavior (Required)
show create table in starrocks and find new column in table schema.
Real behavior (Required)
show create table in starrocks and the schema is not changed.
starrocks can't load the latest schema.
StarRocks version (Required)

3.1.5

Did you try creating the table in spark-sql and connecting via apache iceberg external catalog?

Did you try creating the table in spark-sql and connecting via apache iceberg external catalog?

No，but I think there is no difference, maybe iceberg metadata is cached in fe memory I guess. table schema is always the latest in spark.


Fixing a random seed with srand() does not work on ubuntu 18.04

Hi there,
I recently wanted to seed Libsvm with a random seed. I followed the directions mentionned here and called srand() function right before calling svm_train().
So my code basically looks like this:
srand(42);
svm_model *model = svm_train(state->problem, &params);

This works fine on Windows, but on Ubuntu, I get varying results... Here's an example of the model after calling train with the exact same parameters and dataset twice in a row:

Also, I use datasets with l < 200. So its not that big.
Should I try different random number generators? If so, I can fork this repo and change only the calls to rand()...
Am I missing something?
Thank you in advance for any help,
François

I replaced all usage of rand and srand by std::mt19937 of package <random> and it solved all my problems.
François

Please see the following faq:
https://www.csie.ntu.edu.tw/~cjlin/libsvm/faq.html#f503
Q: On some systems CV accuracy is the same in several runs. How could I
use different data partitions? In other words, how do I set random seed
in LIBSVM?
If you use GNU C library, the default seed 1 is considered. Thus you
always get the same result of running svm-train -v. To have different
seeds, you can add the following code in svm-train.c:
#include <time.h>
and in the beginning of main(),
srand(time(0));
Alternatively, if you are not using GNU C library and would like to use
a fixed seed, you can have
srand(1);
For Java, the random number generator is initialized using the time
information. So results of two CV runs are different. To fix the seed,
after version 3.1 (released in mid 2011), you can add
svm.rand.setSeed(0);
in the main() function of svm_train.java.
If you use CV to select parameters, it is recommended to use identical
folds under different parameters. In this case, you can consider fixing
the seed.
On 2020-07-01 04:45, François Levasseur wrote:

I replaced all usage of rand and srand by std::mt19937 of package
 and it solved all my problems.
François
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2]. [ { "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target":
"https://github.com/cjlin1/libsvm/issues/171#issuecomment-652033219",
"url":
"https://github.com/cjlin1/libsvm/issues/171#issuecomment-652033219",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url":
"https://github.com" } } ]
Links:
[1] https://github.com/cjlin1/libsvm/issues/171#issuecomment-652033219
[2]
https://github.com/notifications/unsubscribe-auth/ABI3BHQQQFVKKV5FPRPTO7LRZJFFLANCNFSM4OMOE4QQ

@cjlin1
Yeah I know! That's exactly the first thing I tried...
Still, I don't know why, rand() was producing different results on two different runs with the same seed (srand(42))...
I forked your repo and solved my problem here.
Now that I use std::mt19937, I not only have consistent results on Linux Ubuntu, but I also have consistent results accross plateforms (Windows 10).
You should check it out.
François


[BUG] Unable to install nor compile TSDuck on Ubuntu 16.04 Xenial

Hi @lelegard
Bug description:
I'm unable to install nor compile TSDuck on Ubuntu 16.04 Xenial
How to reproduce:
Use Ubuntu 16.04.6 LTS Xenial, and try to install and/or compile TSDuck.
Expected behavior:
TSDuck should be installed and/or compiled.
Errors and logs:
install -m 644 tsduck-completion.bash /root/Downloads/tsduck/installers/tmp/usr/share/bash-completion/completions/_tsduck
for cmd in tsanalyze tsbitrate tscharset tscmp tsdate tsdektec tsdump tsecmg tseit tsemmg tsfclean tsfixcc tsftrunc tsgenecm tshides tslsdvb tsp tspacketize tspcap tspcontrol tspsi tsresync tsscan tssmartcard tsstuff tsswitch tstabcomp tstabdump tstables tsterinfo tsversion tsxml; do ln -sf _tsduck /root/Downloads/tsduck/installers/tmp/usr/share/bash-completion/completions/$cmd; done
make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
install -d -m 755 /root/Downloads/tsduck/installers/tmp/usr/bin /root/Downloads/tsduck/installers/tmp/usr/share/bash-completion/completions
install -m 755 tsconfig /root/Downloads/tsduck/installers/tmp/usr/bin
install -m 644 tsconfig-completion.bash /root/Downloads/tsduck/installers/tmp/usr/share/bash-completion/completions/tsconfig
install -d -m 755 /root/Downloads/tsduck/installers/tmp/usr/share/doc/tsduck
install -m 644 CHANGELOG.txt LICENSE.txt OTHERS.txt doc/tsduck.pdf /root/Downloads/tsduck/installers/tmp/usr/share/doc/tsduck
mkdir /root/Downloads/tsduck/installers/tmp/DEBIAN
sed -e 's/{{VERSION}}/3.31-2751.ubuntu16/g' \
    -e 's/{{ARCH}}/amd64/g' \
    -e '/libsrt/d' \
    -e '/librist/d' \
     \
     \
     \
    /root/Downloads/tsduck/scripts/tsduck.control >/root/Downloads/tsduck/installers/tmp/DEBIAN/control
dpkg-deb --build --root-owner-group /root/Downloads/tsduck/installers/tmp /root/Downloads/tsduck/installers
dpkg-deb: error: unknown option --root-owner-group

Type dpkg-deb --help for help about manipulating *.deb files;
Type dpkg --help for help about installing and deinstalling packages.
Makefile:231: recipe for target 'deb-tools' failed
make: *** [deb-tools] Error 2
root@ubuntu:~/Downloads/tsduck#

Environment:

OS: Linux
OS version:

root@ubuntu:~/Downloads/tsduck# uname -r
4.15.0-142-generic
root@ubuntu:~/Downloads/tsduck# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial

TSDuck full version: 3.31-2751
Installation type: Official binary

Additional information:

Hi @moving-digital
Ubuntu 16 is too old, current version is 22. The error message is clear: the current build script uses the dpkg-deb with option --root-owner-group, an option which did not exist in the version of dpkg-deb which came with Ubuntu 16.
There was a version of TSDuck which used to build on Ubuntu 16. I do not recall exactly which one it is, you need to try two or three versions back.
Taking advantage of new tools or options in new versions of the OS is necessary to keep the TSDuck code base clean. In that specific case, for instance, it removes the requirements for post-installation scripts.
With old versions of the OS, you need to use old versions of TSDuck.
As a free open source project with limited resource, I do not guarantee backward compatibility of new versions with old OS versions. I simply do not have the resources to maintain and test an exponentially growing matrix of compatibility. I only make required modifications to support new versions of the OS.


Added remaining two channels of PWM_AUX_DIS disarm parameter sets to rc.interface.

Hi,
This PR adds the remaining two channels (channels 7 and 8) to the PWM_AUX_DIS# disarm lines of the rc.interface , removes trailing whitespace from pwm_params_aux.c and pwm_params_main.c, gps/params.c and adds block comments to separate sections instead of the current whitespace separation.
This PR primarily addresses the git complaints about trailing whitespace in pwm_params_aux.c, pwm_params_main.c, and  gpq/params.c.  The changes to rc.interface simply tie up any potential issues with not setting those values.
Let me know if you have any questions or comments on this PR!
-Mark

Needs to be checked on a board with an IO.

@bkueng , do you have hardware you could test this on and would you be willing to?  Many thanks if you would be, I appreciate it a great deal.

I gave this a quick test on a pixhawk 3 (8 MAIN, 6 AUX) and the pixhawk 4 (8 MAIN, 8 AUX).
The only minor issue is that AUX 7 and 8 params are marked active (synced and visible in a GCS) even on a board where they don't exist. We'll have to come up with a better solution for that later.

Thank you for your testing @dagar !

Pixhawk 3 boot output:


Latest VSCode built-in git not work

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T21:19:36.079Z)
OS Version: Windows_NT ia32 10.0.16299
Extensions:

Extension
Author (truncated)
Version

language-x86-64-assembly
13x
2.2.11

php-debug
fel
1.11.1

php-intellisense
fel
1.5.4

language-haskell
jus
2.4.0

cpptools
ms-
0.14.0

csharp
ms-
1.13.0

PowerShell
ms-
1.5.0

debugger-for-chrome
msj
3.5.0

Disable all extension

End all bash

run vscode

click sync button ( icon rotated but no other response)

or run git pull command (no response too)

vs code run 3 bash instance

exit vs code

but bash not exit

Reproduces without extensions: Yes

I change the integrated shell to default(PowerShell), but VSCode still execute bash to run git command.

@Deliay What git authentication mechanism are you using in that repository?
Can you do git pull from the command line easily?
Do you have a credential manager installed?

@joaomoreno
Just HTTPS authentication.
I test git pull command in VSCode terminal then get error. But exectue in MinGW is work properly.
May Windows Cerdential Manager? I don't knwon , I used not install this kind of software

Can you try using the Windows Command Prompt?


Update sbt to 1.4.4

Updates org.scala-sbt:sbt from 1.4.3 to 1.4.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch

Codecov Report

Merging #899 (6af187f) into develop (1842f73) will increase coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #899      +/-   ##
===========================================
+ Coverage    89.56%   89.65%   +0.09%
===========================================
  Files          119      119
  Lines         9869     9869
  Branches       494      494
===========================================
+ Hits          8839     8848       +9
+ Misses        1030     1021       -9

Impacted Files
Coverage Δ

.../main/scala/com/twitter/algebird/Applicative.scala
51.72% <0.00%> (-3.45%)
:arrow_down:

.../main/scala/com/twitter/algebird/BloomFilter.scala
93.80% <0.00%> (-0.45%)
:arrow_down:

.../scala/com/twitter/algebird/immutable/BitSet.scala
96.14% <0.00%> (-0.22%)
:arrow_down:

...a/com/twitter/algebird/immutable/BloomFilter.scala
95.90% <0.00%> (+0.81%)
:arrow_up:

.../main/scala/com/twitter/algebird/Approximate.scala
90.32% <0.00%> (+1.61%)
:arrow_up:

...main/scala/com/twitter/algebird/monad/Reader.scala
58.82% <0.00%> (+5.88%)
:arrow_up:

...src/main/scala/com/twitter/algebird/Interval.scala
83.47% <0.00%> (+7.82%)
:arrow_up:

Continue to review full report at Codecov.

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


Cursor does not respect textContainerInset when it's set

When I set textContainerInset of the textView, the cursor does not respect it

@jackguo709 Thanks for reporting! I'll look into it tomorrow morning.

@jackguo709 One question at the moment, does it affect all languages or only RTL?

@jackguo709 Could you check if the changes made in the master branch work for you?

Fixed in version 6.0.3.


GitHub action for Grype scan

Not urgent - just experimenting as an alternative to Trivy scan.

Codecov Report
Patch and project coverage have no change.

Comparison is base (2e09752) 0.00% compared to head (4ada5c2) 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@          Coverage Diff           @@
##           master     #92   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files           1       1
  Lines         664     664
======================================
  Misses        664     664

Impacted Files
Coverage Δ

controllers/networkplugins_controller.go
0.00% <ø> (ø)

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


Loopring recognizes balance on "account" but not on "trade"

Loopring DEX recognizes balance on "account" but not on "trade"
That means that when clicking on "account", it appears all the balances related to my eth account (thru metamask), but when trading it says I have no balance on anything

Do you have open orders for that trading pair? If, for example, you have 1000 OGN tokens and have an open sell order for 1000 OGN tokens, your balance will reflect as 0 for that token, because you have zero 'available' tokens to trade with.


Update faqs.md

Added 4 FAQ's to General CD FAQ
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 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.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://666accf0ac27dee02411dabd--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://666be77c633cce6075169462--harness-developer.netlify.app


Saving Visualizations as GIFs?

Is there a straight forward way of saving the guide trace visualizations like first_person.gif? I imagine we could use three.js to do this, but any hints or code would be appreciated!

From memory I think this was converted to gif from a video screen capture.
If you just need the camera view (not the text) it is relatively easy to capture and download a webm video from the canvas element that is rendering the first person view. An example can be found in this older R2R annotation tool.

Thanks, that does the trick!


[OverflowMenu] support nesting, grouping, line breaks

Summary
From @lukefirth via Internal Watson-IoT/pal-tracking#142

Is this an extension to an existing component, pattern, or a brand new asset?
Item from the EDS.
What is the rationale for this contribution.

This covers an advanced version of the overflow to enable something similar to what is seen in some common operating systems, namely with extensions in capability to support:

Nesting of level in the overflow
Line breaks to separate groups/categories of option within the menu.

Detail the intended behavior
The menu is incurred either from a button, or linked text. Once incurred the content will appear below the selection and present options that can be selected (assume styling for hover, disabled options etc takes reference from dropdowns). These may be grouped by some categorisation strategy by the design team.
For nesting, hovering over or otherwise applying focus to an option with a right pointing carat will open a subsequent menu of nested options directly to the right of the open one.
Clicking an action in the menu, or outside of the menu will close all levels of the menu.
Inspiration from other products
(Optional - remove this is you don't have any)
OS, eg:

Lots of a11y concerns with placing focus appropriately between keyboard and mouse interactions.
High level implementation notes:

provide a new OverflowMenuItem, OverflowMenuItemGroup to handle grouping
provide a new OverflowMenuItem, OverflowMenuItemNest to handle nesting
use existing handleOverflowMenuItemFocus prop from OverflowMenu to place focus in the intial list. Focus inside groups or nests will need to be handled ourselves with custom logic.

Need this (Nesting, Separators/grouping) for IBM Engineering. Add Engineering tag & increase to Val 1.

Need this (Nesting, Separators/grouping) for IBM Engineering. Add Engineering tag & increase to Val 1.

Here's an example of nested menus (cascading menus) and separators from ELM's DOORS Next application:

Here's an example of nested menus (cascading menus) and separators from ELM's DOORS Next application:

I noted in https://github.com/carbon-design-system/carbon-addons-iot-react/issues/1821#issuecomment-807117772 that ELM has a use case where we need support for tooltips on menu items, including disabled menu items.
FYI @davidicus @lorelei-ngooi


Chromebook sudden crash/reboot when out of memory

chronos@localhost / $ more /var/spool/crash/kernel.20171005.150059.0.meta
sig=kernel-Out of memory and no killable processes.-40122954
exec_name=kernel
ver=9592.96.0
payload=/var/spool/crash/kernel.20171005.150059.0.kcrash
payload_size=108985
done=1
chronos@localhost / $ sudo edit-chroot -all
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20170901092920~master:0216f9d1
release: xenial
architecture: amd64
xmethod: xiwi
targets: xiwi,cli-extra,touch,xfce,keyboard
host: version 9592.96.0 (Official Build) stable-channel samus
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Sat Sep 16 09:51:02 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Please describe your issue:
Doing some memory intensive data work in xenial crouton and when hitting memory constraints the chromebook reboots.  Crash report above.  Running on a Pixel 2015 LS.
If known, describe the steps to reproduce the issue:
Running some statistical analysis in RStudio server and see memory usage and CPU usage spike.  System slows down to a halt and then reboots.

Yes this happens a lot to be sure you wont use your memory to fast use kde,xfce,lxde unity is a bit too big to run on a small laptop so dont push it to far

I'm actually not using any window manager, just command-line.  I also have
Pixel LS with 16GB of ram.  Is there a way to prevent the reboot?  Use swap
memory?  It doesn't seem like expected behavior in Linux or any modern OS
to reboot when memory runs out.
On Sun, Oct 8, 2017 at 2:23 AM Ender<EMAIL_ADDRESS>wrote:

Yes this happens a lot to be sure you wont use your memory to fast use
kde,xfce,lxde unity is a bit too big to run on a small laptop so dont push
it to far
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3445#issuecomment-334986223,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFy0y-fN6Sbi8qoBRzr7GJfdj-eq7KImks5sqGppgaJpZM4PvkQf
.

I'm not sure about the Pixel LS, but all other Chromebooks don't have a SWAP partition and only rely on zram.  If you have a very memory intense application you could simply run out of memory completely and the linux kernel has to kill applications. It seems that in your case it kills some important chromeos processes which cause a reboot (not sure why it doesn't simply kill your memory intense application, as this would be the expected behavior). As a workaround you could create a SWAP file on your internal memory (if you have enough space) or on the sd card (which will cause extrem slowdowns). This should solve your reboots.


PDF release wanted

Can there be a PDF too in the release?

Good point!
Added the PDF to the release. 😊


Bug 🐞 | Gcast_Py

Gcast.py is not working i just shows "starting gcast" only plz fix it

soon these days busy af

soon these days busy af
Oh noooo

N


PIXI {.name} props ?

I ask myself an existential question.
Why the property .name existe and why is such empty.
For my part, I use it specifically to identify resources and easily debug them.
Does it have another logical feature?
if not , Why not include the ability to directly name sprites or a container in the constructor with a arg ?
It's just a question because I find myself add names for most of my Objects, and I always use this proprety at the second degree.

Occam razor.

ok thank for answer, so I can use it without fear of future problem.


Run tests on Netty for WebFlux

WebFlux doesn't require jetty or tomcat.
It uses netty.
Is it possible to get rid of jetty from WebFlux integration tests?

Is this causing problems for you for some reason?

yes, it looks like TracingSubscriber.onComplete() is never called, therefore span is not finished:
https://github.com/opentracing-contrib/java-spring-web/blob/master/opentracing-spring-web/src/main/java/io/opentracing/contrib/spring/web/webfilter/TracingSubscriber.java#L77

So I might be missing something here... Is this tied to another issue perhaps?

If I use in my app tomcat then I see that TracingSubscriber.onComplete() is called.
But if I don't use tomcat and rely on netty which comes with spring-webflux I don't see calling TracingSubscriber.onComplete().
That's why I'm curious why integration test for WebFlux is based on jetty.
I use the latest version of spring.

@csabakos can you shed some light on this perhaps since you were the one that added those tests?
Thanks

@geoand WebFlux should work equally over any runtime (Tomcat, Jetty, Netty, etc.), so there was no reason to switch away from the runtime that was already used in other tests.
If the observed behavior is different on Netty, then I think it would make sense to add Netty-based integration tests to make sure that all cases are covered.

So you just added like that for convenience, thanks that's good to know.
@malafeev Would you like to take a stab at it? If you are unavailable, I can take a look but it will probably be a while...

@geoand it would be great if you take a look even in a while. Currently I don't have enough time.

Same here :).
I'll take a look as soon as I can

I want to upgrade to Opentracing 0.33 first. Then I'll look into this


Added tags/worldgen

Added tags/worldgen.
Before merging, tell me if I should update stuff like tags/items to tags/item. Pucki said most people are still on releases, but I'll add another commit in case you want the changes to be added immediately. I'm also going to put an idea for /folderstructure versions: <version> in suggestions if we want that.

I was sitting here for ages thinking why this didn't get merged then I realised that tags/worldgen probably isn't a thing and what Pucki meant was like to add tags/structures or something mb lol.


AllowClear event

Good day!
How can I tell the allowClear event?
Thanks!

It is not clear what you are asking.  Documentation for the allowClear event is available here: https://select2.org/selections#clearable-selections, and for events is available here: https://select2.org/programmatic-control/events

The clear event is now available as of v4.0.6-rc.0.


fix 'NoSuchUpload' when upload part

Signed-off-by: changlin.shi<EMAIL_ADDRESS>What problem are we solving?
fix #3967
How are we solving the problem?
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

@chrislusf I made a mistake here yesterday, no need to divide by object.


[Tenderly] Verification + Deployment

Issue Overview
Add Deployment on Devnet Tenderly for testing purposes for contracts.

You can check it here : https://www.youtube.com/watch?v=CVRSMYGXOrQ&t=13s&ab_channel=Tenderly|Full-StackWeb3Infrastructure


update jackson dependency version

Signed-off-by: Amit Galitzky<EMAIL_ADDRESS>Description
bump jackson version
Issues Resolved
#676
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #678 (12584e9) into main (fd71844) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #678      +/-   ##
============================================
- Coverage     79.03%   79.02%   -0.02%
+ Complexity     4241     4238       -3
============================================
  Files           301      301
  Lines         17871    17872       +1
  Branches       1897     1897
============================================
- Hits          14125    14124       -1
- Misses         2841     2842       +1
- Partials        905      906       +1

Flag
Coverage Δ

plugin
79.02% <ø> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ansport/handler/AnomalyResultBulkIndexHandler.java
83.87% <0.00%> (-3.23%)
:arrow_down:

...java/org/opensearch/ad/task/ADBatchTaskRunner.java
81.45% <0.00%> (-0.31%)
:arrow_down:

...ava/org/opensearch/ad/model/TimeConfiguration.java
100.00% <0.00%> (ø)

...rch/ad/transport/AnomalyResultTransportAction.java
80.18% <0.00%> (+0.23%)
:arrow_up:

...ain/java/org/opensearch/ad/model/ModelProfile.java
72.72% <0.00%> (+1.81%)
:arrow_up:


Can't access the web app

Hello there,
I was very happy to stumble on your repo. This is exactly what I wanted for my Inkplate. Thank you very much!
Unfortunately, I have no real experience with esp32 and for some reason I can't get web app to load. Both commands (uploadfs and upload) are passing succesfully and I'm able to get to the the setup screen.

But after connecting to the network and visiting the web address (<IP_ADDRESS>) I'm getting a simple "Not found" message. I've checked IP address, and it is good. So, I'm stuck and I'm not sure how to debug it to see if the filesystem is properly populated.
I would appreciate if you have any idea how to get it up and running.
Cheers!
EDIT: I actually managed to find logs and I can see this one:
E (36265) webapp: File not found: /spiffs/index.html
W (36265) httpd_txrx: httpd_resp_send_err: 404 Not Found - Not found.

I made it, not sure what I was doing from but after rebuilding it and re-burning it, it started working!
Thank you and sorry for the false alarm!


Support for Publishing "Slim" Packages

I wanted to kick start a discussion of adding support for slim packages. Currently, on the unofficial AdoptOpenJDK Docker images we are producing slim builds for JDKs and hopefully soon we will also publish slim JRE builds as well.
Slim builds are currently being produced by running this script, slim-java.sh. In running the script we are modifying the builds we get from adoptopenjdk.net. From my understand, this modification is what will block us from publish these slim builds into the official Docker images.
You can see more information given by @dinogun about the why this modification will be blocked here, https://github.com/AdoptOpenJDK/openjdk-docker/issues/125#issuecomment-534999866.
To get these slim builds in the official Docker images, we would need AdopOpenJDK to build and publish these slims packages.

Serious question: What makes the same script running on the same Jenkins in a different job less official? And what is the exact definition of bar that needs to be cleared to make things "official"?
If AdoptOpenJDK declares something to be official and supported, this should be sufficient for any other project. Otherwise, things can get out of hand pretty quickly.

@aahlenst the bar that needs to be cleared is set by the maintainers of the Official Image repo in the Docker Library organization.
In particular the issues raised in this PR, https://github.com/docker-library/official-images/pull/5710, need to be addressed. The comments from @tianon shine some light on what their concerns were with slim images. See comments, https://github.com/docker-library/official-images/pull/5710#issuecomment-484301121, https://github.com/docker-library/official-images/pull/5710#issuecomment-484377859 and https://github.com/docker-library/official-images/pull/5710#issuecomment-486018064.
I think there is some discrepancies with what the maintainers of the Official Image repo wanted as the discussion went on as more facts got introduced.
At first it looked like they wanted slim builds to be distributed by AdoptOpenJDK and given their stamp of approval. But as the conversation moved on, they mentioned:

The plan at AdoptOpenJDK is to make the slim script as part of the build itself (and generate slim builds).

Honestly, if that's the case I'd prefer to add slim variants until that happens -- it's quite a bit of additional complexity that I think makes a ton more sense to have in AdoptOpenJDK itself (and thus have more eyes reviewing, maintaining, and ultimately supporting).

@tianon you seemed like the main reviewer for the PR, could you clarify what we need from Adopt to get the slim builds in the official images?

My biggest concern with the script that's specific-to-the-Docker-images vs being part of an official "AdoptOpenJDK build process" is in the testing of it.
My understanding is that official AdoptOpenJDK builds undergo testing that's at least in spirit similar to something like the TCK, and the Docker images most certainly do not (we do some basic surface level testing, but nothing more advanced than "does javac work?" and "does this basic program run?").
If these are going to be officially-released artifacts of the AdoptOpenJDK project, then IMO it seems prudent for them to actually be officially-released artifacts on the same level as any others, undergoing the same testing and scrutiny as any others.
If the AdoptOpenJDK project doesn't agree that the resulting "slim" artifacts should be released as such, then perhaps the minimization script itself could be part of the tarballs that currently are distributed?  I think there's a lot of value in having a standard way to "slimify" a given release, and I don't think there's anything inherently "Docker-specific" about doing so.
In that way, they would be part of the AdoptOpenJDK review/release process instead of being a Docker-specific script which I think would end up only being lightly reviewed (I'm certainly not an expert in which bits of any given AdoptOpenJDK release are reasonably "safe" to trim for a slimmer build, so my review of those scripts as part of the official images "dockerization" review is not going to be particularly helpful, and I believe I can also speak for @yosifkit in that regard).

To put things another way, if "end-users are supposed to use the JRE or a jlinked image," I don't see what makes Docker fundamentally different?  What makes the Slim image more interesting to Docker users than non-Docker users?  Why aren't Docker users encouraged to use the same JRE / jlink methods as non-Docker users?

@tianon Thanks for explaining and layout what is needed/wanted.

My biggest concern with the script that's specific-to-the-Docker-images vs being part of an official "AdoptOpenJDK build process" is in the testing of it.

My understanding is that official AdoptOpenJDK builds undergo testing that's at least in spirit similar to something like the TCK, and the Docker images most certainly do not (we do some basic surface level testing, but nothing more advanced than "does javac work?" and "does this basic program run?").

The currently plan is all nightly images, which includes slim images, produced by AdoptOpenJDK will go through a certain set of tests. You can see some of the progress of connecting the AdoptOpenJDK Docker Build pipeline and the AdoptOpenJDK Test pipeline, https://github.com/AdoptOpenJDK/openjdk-docker/issues/328. Myself, @smlambert, and a couple others are working on connecting these pipelines.
@smlambert could you elaborate on the set of tasks we will be running and give @tianon a little background on what these tests should be verifying?
As for the questions on packaging and officially-released artifacts, the build team can hopefully address some of the questions. @karianna @sxa

@tianon Requiring something to be fully tested and requiring some sort of standalone release are two separate things. Having the slim images tested is something that I endorse.
If I read the script correctly, the jmods are removed. In turn, jlink becomes non-functional. This might make sense for people that need more than a JRE for their applications in Docker, for example because they want to use OpenJFX or because they know they need javac but do not need jlink. Putting a partially broken JDK on the front page is something that I do not want, especially because this is very hard to communicate, a non-standard thing and regular users are expected to use jlink. That’s why Jigsaw (the JPMS) was forced upon the ecosystem, after all. Size is at a premium in a container image, but not on a regular computer, and because container images are harder to create and host, I can see the value in the slim image. Besides, I‘m not sure if it would pass the full test suite without jmods.

re: https://github.com/AdoptOpenJDK/openjdk-build/issues/1777#issuecomment-634214597, initially we had planned to run some system tests, but given there are slim images included in the set, it may be the wiser course of action to focus on a subset of the functional/openjdk tests.  This would allow us to verify functional correctness of the core set of APIs, and not worry about varying the set of tests depending on the image under test.
As we see how those tests do, we can increase the level of testing for the full images, if we decide it is important to do so, or audit particular pieces of functionality based on support issues that arise.

The objective of this issue is not sufficiently clear and as it stands, it isn't actionable.

If this is about testing of the Docker images, especially of the slim variants, please create an issue in https://github.com/AdoptOpenJDK/openjdk-docker/. Test coverage of downstream artifacts needs to be dealt with downstream.
If this is a genuine request to add "slim" binary builds of the JDK, please demonstrate that such a variant is useful on its own to our end users (not Docker-specific) and warrants the additional burden (resources, support) on the project. If this information is provided, I'm happy to reopen the issue.


[Skeleton 1st Edition] Link and Name Update

Changes / Comments
Added links to linktree for ease of access to materials.
Changed a few names and fixed a few errors, also fixed names to preserve data (hopefully)
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[x] Does this add or change functional aesthetics (such as layout or color scheme) ?
[x] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Improve test-documentation to be less flaky in CI

Right now, tools/test-documentation checks for two types of issues with links in our documentation:

Internal links, e.g. to ReadTheDocs or parts of the zulipchat.com site.  These we want to check are good in CI.
External link errors, e.g. that third-parts sites are 500ing.  These we don't want to enforce being good in CI, because they often fail due to the third-party sites having operational errors (E.g., today http://citizencodeofconduct.org/ 500s, and it's unclear when it will be fixed).

I'd like to add an option to tools/test-documentation that we can use in CI that only sets exit status to a nonzero value if the first category of links are broken.  Those checks are important, and have often been broken in refactorings in the past, so I really would like to run those checks in CI...

@zulipbot claim

Hi, a quick clarification on how to go about.
Do you want to add an option like --skip-external-links to tools/test-documentation ?
I'm thinking of doing a check whether the url starts with appropriate name like "http://zulip.readthedocs.io" or  "http://zulipchat.com" in  /tools/documentation_crawler/documentation_crawler/spiders/common/spiders.py and handle it there itself. Is this okay? Please tell me if there is any other approach.
Thank you


Apply on start?

How to apply on component render? only works when resizing, thanks <3

@Maadtin The constraints are applied on render and then listens for further changes. Can you post an example of your code?

@contra Yes sure look:
function Index() {

    const [selectedType, setSelectedType] = useState('animes');
    const isTabletOrDesktop = useMediaQuery({minWidth: 1000});

    return (
            <Content />
            {isTabletOrDesktop && <Sidebar />
    )
}

When I reload the page <Sdiebar /> is visible but If I resize the mediaquery applies and It disappear just as I would expect but the problem is then I reload the page above 1000px It should appear but It doesn't...

Could you make a codepen/jsfiddle/etc. that reproduces the issue?

Closing since I haven't gotten a response. Will reopen if you have a reproduction available.


Add a linter, make existing code conform to the style

It's a pretty minimal set of style rules, but the idea is to have something that enforces some kind of style, and catches the most significant causes of error or eye irritation.
This PR installs eslint locally, so VSC will pick it up and use it automatically, which is a nice win. Free lint! @intersim @glebec @tmkelly28 @omriBernstein

I'm traveling today but I will probably be able to take a look this evening. Something I'd like to see is to fuse this linting config / style with the linting process / scripts from glebec/bones (see https://github.com/glebec/bones/blob/master/package.json#L18), which watches and fits into the über dev script (https://github.com/glebec/bones/blob/master/package.json#L23). I had intended on opening a PR for some of the changes in glebec/bones earlier but this works as a reminder. ;-)

PTAL.
 I moved it into its own file, dev.js. This means you can also run node dev to start everything, which seems nice.
Since it's now easy to run the tests along with everything else, I did that.
I don't know why the tests are failing. :( They work for me and on my CI, and I can't see this Codeship.

I ended up not turning my computer on today (yay). From my phone I just checked the codeship:
  1) /api/auth "before all" hook: Await database sync:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

I'll see if I can add you to the codeship somehow. I'm not sure why you don't already just have access, I thought it was tied to our organization so if you're using a GH account in the FS org you'd see it. Maybe not though.

It looks like we have to add members manually, Codeship doesn't integrate with GitHub orgs / permissions? Lame. Anyway I sent you an invite.


[AutoPR consumption/resource-manager] Added schema spec for cost allocation tags

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2742

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2158


fix minor SQL syntax problem in V271__accounting_for_client_charges.sql

upgrading flyway-gradle-plugin from 3.0 to 5.2.4 required this


Update from props doesn't reflect in Date or Time fields

Hi,
Not sure if I'm missing something essential here, but here's my use case.
I have a parent component which contains the Formsy forms with a custom form element for array fields.  handleOnChange updates rows with a new array:
<Formsy.Form>
    <ArrayFields rows={rows} onChange={handleOnChange} />
</Formsy.Form>

ArrayFields has a render that looks a bit like:
doChange() {
  const {rows, onChange} = this.props;
  // update rows with changes
  onChange(newRows);
}

render() {
    const {rows} = this.props;
    console.log(rows);
    return(
        <div>
            {rows.map((field, i) => (
                <FormsyDate defaultDate={field.date} onChange={doChange} />
                <Input type="date" value={field.date ? moment(field.date).format('YYYY-MM-DD') : null}
 onChange={onChange} />
            ))}
        </div>
    );
}

There are also add and remove buttons to manipulate the rows.  And I have added Input date to compare behaviours.
On first render, this populates the values correctly.  Adding rows and updating the fields works as expected.  But removing fields has an interesting problem:
If you have 3 rows, and remove row 2, console.log correctly dumps the remaining row 1 and 3, the Input fields correctly shows the appropriate values for 1 and 3, but the FormsyDate field shows the values for 1 and 2.
For further confirmation, updating the value using the FormsyDate picker reflects in the Input, but not vice versa.  So it appears as though FormsyDate doesn't reflect value updates unless you go through the picker mechanism.
I have also tried using defaultDate, defaultValue and value for these fields separately and in combination, but it doesn't seem to update the display value for the Date (or Time) field.
Do you have any suggestions for how I can get the change in value to reflect?
Thanks

I have decided against using package for my purposes, but in case anyone else is stuck with this issue, this stackoverflow response provides a clumsy but sort of usable workaround: http://stackoverflow.com/questions/37019778/how-to-clear-the-text-field-in-formsy-material-ui-react


Ghost shows up in Chrome, but not Safari

Using master: ✅
Love Sortable, always works great. I'm having an issue that I have tried to debug for hours but no luck. With Safari, I don't see a dragging ghost. With Chrome, I do. This is the first time I am using Sortable in a React view, I do not have this issue in my application on non-react views, but it is working in Chrome fine, just not safari.
Here is an attached video: https://www.dropbox.com/s/wekhiw9zwtv3wsm/Sortable Ghost Missing.mov?dl=0
I have also tried forceFallback: true. If I do this, the ghost does show up but this is not an option I can use because I have that trash can button inside the drag element, and with forceFallback, I get an error when I click that element inside because of something about "passive".
Any idea why this might be working in Chrome but not Safari?
I have tried to get a look at the DOM ghost that Sortable but creates but I can't figure out how to look at it while making it show up, it always disappears after drop.

Hi,
have you found any solution for this? I'm having same problem.
In my case, on Safari, when I'm moving item from one list to another, dragged ghost item is not visible. I dragging within one list (sorting only), it displays OK.
forceFallback: true kind of works, but destroys messes items layout, don't know why exactly.

what is the fix for safari @sahandnayebaziz


[BugFix] when do join reorder we only need to check the column statistics available of the reorder scope

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

we only need to check the reorder join related column statistics not all the plan.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/join/ReorderJoinRule.java
1
1
100.00%
[]

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4

@Mergifyio backport branch-2.3


Change webcam icon to point in the direction the webcam is facing

I think it's very useful to see on the map already what direction a webcam is facing, and this data is often available.
To this end I changed the icon to be more directional (svg taken from https://de.wikipedia.org/wiki/Datei:Video_camera_icon_svg.svg) and rotated it appropriately.

Hello,
Thanks for creating this merge request. The idea is good, and I would like to add it. I have a few requests before we can merge the changes.
First, the good. I like the extra information it brings to the map. I also like the way it uses multiple tags to determine the direction.
Here is a list of things that need to be fixed before I can merge it.

[ ] Remove the brownish outline on the icon
[ ] fix the eslint error
[ ] @ts-expect-error the ts error WITH explanation about why
[ ] add thanks for the new icon to the read me file
[ ] resolve the code comments

Thanks again for supplying this PR, and I look forward to the fixes and merging it.

First of all, thank you for making this.
Sorry for the mess I've made of the PR. I wanted to rebase and had some git mishaps along the way.
I also put some finishing touches on the code myself. You can find them in 49bb94e.
Thank you for having this idea and taking the time to implement it.

Very nice. I love the new "grouping" feature on zoom out. Thank for starting this project.